Can WooCommerce products be submitted without a GTIN?
Can WooCommerce products be submitted to Google Merchant Center without a GTIN?
WooCommerce products can be submitted to Google Merchant Center without a GTIN only when the product genuinely has no manufacturer-assigned GTIN and its other product identifiers are represented accurately.
The absence of a GTIN does not automatically make a product unsuitable for Merchant Center.
However, leaving the GTIN field empty is not enough.
The merchant must first determine which of the following situations applies:
The product has a manufacturer-assigned GTIN.
The product has no GTIN but has an established brand and MPN.
The merchant manufactures or privately labels the product.
The product is genuinely unbranded and has no assigned identifiers.
The product is handmade, one of a kind, antique or from a period before GTINs were introduced.
The product is a customized version of an existing branded product.
The product is a variation, bundle or multipack that requires its own identifier treatment.
The GTIN exists but has not yet been entered in WooCommerce.
These situations must not be treated as interchangeable.
A merchant cannot make a GTIN requirement disappear merely by selecting identifier_exists as false.
Google may recognise that an identifier normally exists for the product and report an incorrect product identifier, missing GTIN or related product-data issue.
The correct decision therefore depends on the product’s real identity, manufacturer, packaging and commercial history—not on which field is easiest to complete.
The short answer
Yes, some WooCommerce products can be submitted to Google Merchant Center without a GTIN.
Use the following decision order:
Check whether the manufacturer assigned a GTIN.
Check the product and retail packaging.
Check the manufacturer’s official product information.
Check whether each variation has its own GTIN.
Check whether an established brand and MPN are available.
Determine whether the merchant is the manufacturer or private-label brand owner.
Determine whether the item is genuinely custom, handmade, unique, antique or produced before GTINs were introduced.
Use the real GTIN whenever one exists.
Use the genuine brand and MPN when those identifiers exist.
Use identifier_exists as false only when the product genuinely has no applicable GTIN, MPN or brand identifiers.
Do not invent a GTIN.
Do not copy another product’s GTIN.
Do not automatically use the WooCommerce SKU as a GTIN.
Do not mark an entire catalogue as having no identifiers.
Submit the same identity consistently through WooCommerce, structured data and the active Merchant data source.
Inspect the processed product in Merchant Center after submission.
The central question is not:
Can I leave the GTIN field empty?
The correct question is:
Does this exact product or variation have a genuine identifier assigned by its manufacturer or recognised brand owner?
What is a GTIN?
A Global Trade Item Number, or GTIN, is a standardised product identifier assigned to a trade item.
Depending on the product and market, a GTIN may appear through formats commonly associated with:
EAN
UPC
JAN
ISBN
ITF-14
Other GS1-based product identification structures
Google uses the GTIN [gtin] attribute to identify products more accurately and connect merchant offers representing the same genuine product.
According to Google’s GTIN attribute guidance, merchants should submit the GTIN assigned to the product rather than creating or estimating one.
A GTIN can normally be found on:
Retail packaging
A product label
A barcode
Manufacturer documentation
An authorised supplier record
A product database maintained by the brand
A book’s ISBN information
An official product catalogue
A barcode and a GTIN are related, but the visible bars are not the value that should be entered.
The numeric identifier encoded by the barcode is the relevant product information.
A QR code, warehouse label, shipping label or internal stock barcode is not automatically a valid GTIN.
GTIN is not the same as a WooCommerce product ID
WooCommerce assigns an internal database ID to each product and variation.
That ID helps WordPress and WooCommerce manage the product inside the website.
For example:
WooCommerce product ID: 2417
WooCommerce variation ID: 2421
Merchant offer ID: shop-2417-blue-large
SKU: TSHIRT-BLU-L
MPN: TS-BL-L-2026
GTIN: a genuine manufacturer-assigned global identifier
These values can all refer to the same commercial item while serving different purposes.
A WooCommerce product ID should not be submitted as a GTIN merely because it is unique inside the store.
It has no global meaning outside that WooCommerce installation.
GTIN is not automatically the same as SKU
A WooCommerce SKU is normally an internal stock-keeping code used by the merchant.
It can help the store:
Locate products
Manage inventory
Match warehouse records
Connect variations
Reconcile orders
Identify products in internal reports
A SKU can look similar to an MPN or GTIN, but visual similarity does not make the values equivalent.
For example:
SKU: STORE-4581
Manufacturer MPN: AXR-840-BLK
GTIN: manufacturer-assigned global trade number
A reseller should not place STORE-4581 in the GTIN field.
A reseller should also avoid submitting its private SKU as the manufacturer’s MPN unless the merchant genuinely manufactures or owns the private-label product and uses that value as the product’s manufacturer part number.
Understand the four identifier attributes
Google product identification commonly involves:
GTIN [gtin]
Brand [brand]
MPN [mpn]
Identifier exists [identifier_exists]
These attributes work together.
They should not be completed independently without considering the product’s actual identity.
GTIN [gtin]
Use the genuine GTIN assigned to the exact product.
Do not:
Add spaces or explanatory text.
Enter the barcode image URL.
Enter the WooCommerce product ID.
Enter a Merchant offer ID.
Enter an order number.
Enter a random sequence.
Reuse another product’s GTIN.
Use a shortened GTIN because a form rejects the full value.
Add leading or trailing text.
Use the parent product’s identifier for every variation without verification.
Brand [brand]
The brand identifies the recognised manufacturer or brand associated with the product.
Google’s brand attribute requirements advise merchants to provide a brand only when they are confident that it is correct.
The store name should not automatically replace the manufacturer’s brand.
Use the store name as the brand when the merchant genuinely manufactures the item or owns the private-label product.
Do not use the store name merely because the product is being sold by that store.
MPN [mpn]
The Manufacturer Part Number identifies a specific product among products from the same manufacturer.
Google’s MPN guidance distinguishes the manufacturer’s product code from a retailer’s internal stock code.
Use:
The manufacturer’s real part number for branded retail products.
A stable merchant-assigned manufacturer number when the merchant genuinely manufactures or privately labels the product.
Do not use:
A temporary import number
A WooCommerce database ID
A supplier order number
A category code
A warehouse location
A random value created only to remove a warning
Identifier exists [identifier_exists]
This Boolean attribute tells Google whether applicable unique product identifiers exist.
Google’s identifier exists documentation explains that false should be used only when the product genuinely does not have available unique product identifiers.
For Merchant API product attributes, identifierExists is a Boolean field. Google’s current Merchant API product attribute reference also notes that it defaults to true when it is not provided.
This creates an important distinction:
An empty GTIN with identifierExists omitted does not necessarily tell Google that no identifiers exist.
identifierExists: false is a specific declaration that applicable identifiers genuinely do not exist.
That declaration should not be used simply because the merchant has not yet researched the product.
The correct product identifier decision
The safest way to classify a WooCommerce product is to follow a product-by-product decision process.
Situation 1: The product has a genuine manufacturer GTIN
Submit:
GTIN
Brand
MPN where available
identifier_exists as true or allow the integration’s correct default behaviour
This applies even when:
The GTIN is not currently entered in WooCommerce.
The supplier did not include it in an import file.
The product was manually created.
The barcode is not visible in the product images.
The product is used or refurbished.
The merchant prefers its internal SKU.
A previous product source omitted the identifier.
The fact that the WooCommerce record is incomplete does not mean that the real product lacks a GTIN.
Situation 2: The product has no GTIN but has a genuine brand and MPN
Submit:
Correct brand
Correct MPN
No invented GTIN
Appropriate identifier_exists treatment based on the actual identifiers and integration
Google’s current missing or incorrect GTIN guidance says the affected product should contain either an accurate GTIN or both an MPN and brand where applicable.
The exact eligibility result can still depend on:
Product category
Target country
Product condition
Google programme
Product type
Available manufacturer information
The absence of a GTIN should not be hidden by removing genuine brand and MPN information.
Situation 3: The merchant manufactures or privately labels the product
A merchant-manufactured or private-label product may not initially have a GTIN.
However, that does not always mean identifier_exists: false is the best representation.
Google’s brand guidance recommends using:
The merchant’s genuine brand or store brand
A unique MPN assigned to the product
This approach can be appropriate when the merchant:
Manufactures the product
Controls the brand
Is the only seller of that product
Produces a stable catalogue item
Can maintain a permanent MPN
Uses the same identifier for the same product over time
The MPN should remain stable.
Do not generate a new MPN every time the product is synchronized.
Do not change it when:
The price changes
The stock changes
The product description changes
The image changes
A sale starts
The product is resubmitted
A new API operation is created
A manufacturer part number identifies the product, not the current submission event.
Situation 4: The product genuinely has no identifiers
Some products may genuinely have no:
GTIN
Manufacturer part number
Recognised brand
Examples can include:
One-of-a-kind artwork
Individual handmade objects
Truly unbranded custom items
Certain antiques
Products made before GTINs existed
Certain old books or collectibles
Unique commissioned products
For qualifying products:
Leave GTIN empty.
Leave MPN empty when none exists.
Do not invent a brand.
Submit identifier_exists as false.
Describe the product accurately.
Use a stable Merchant offer ID.
Provide accurate price, condition, availability and landing-page information.
identifier_exists: false is not an exemption request.
It is product data describing a factual condition.
Google can still evaluate whether the statement appears credible for that product.
A practical decision table
Use this classification before submitting a WooCommerce product.
Product situation
GTIN
Brand
MPN
identifier_exists
Branded retail product with assigned GTIN
Submit exact GTIN
Submit real brand
Submit if available
true
Product with no GTIN but established brand and MPN
Leave GTIN empty
Submit real brand
Submit genuine MPN
Do not incorrectly declare that no identifiers exist
Merchant-manufactured stable catalogue product
Do not invent
Submit merchant/private-label brand
Assign and retain a genuine unique MPN
Usually represented through brand and MPN
Truly unbranded one-of-a-kind product
Leave empty
Leave empty if no brand exists
Leave empty
false
Branded product whose GTIN has not been researched
Research first
Submit real brand
Submit if known
Do not use false merely because data is missing
Customized version of an existing branded product
Use applicable manufacturer GTIN
Use original manufacturer brand
Use applicable manufacturer MPN
Normally identifiers exist
Antique or pre-GTIN product with no identifiers
Leave empty
Submit only if genuinely known
Submit only if genuinely known
false when no applicable identifiers exist
Variable product
Use exact variation GTIN
Submit real brand
Use exact variation MPN where applicable
Determined per variation
The decision should be made for the exact offer, not merely for the WooCommerce parent product.
Branded retail products normally require research
A product sold under a recognised manufacturer’s brand probably should not be classified as having no identifiers merely because the store owner cannot immediately find the barcode.
Before using identifier_exists: false, check:
Outer retail packaging
Inner product label
Manufacturer website
Authorised distributor portal
Supplier invoice or catalogue
Product manual
Existing stock database
Brand support
The exact model and variation
GS1-related verification resources
Google’s incorrect identifier guidance states that a product believed to have a GTIN can remain affected until the correct identifier is supplied.
The correct response is to locate the genuine identifier—not to manufacture a substitute.
Do not buy or generate a replacement number for an existing branded product
A merchant should not obtain an unrelated barcode and apply it to a product already identified by another manufacturer.
The GTIN must describe the actual trade item.
A number that belongs to:
Another manufacturer
Another colour
Another size
Another pack quantity
Another condition
Another bundle
Another product revision
does not become valid merely because it passes a numeric format check.
Technical validity and product identity are different.
A number can have a valid length and check digit while still belonging to the wrong product.
A WooCommerce variable product can contain several separately purchasable variations.
Variations can differ by:
Colour
Size
Material
Pattern
Capacity
Flavour
Pack quantity
Model
Age group
Gender
Each variation submitted as a separate Merchant offer should use the identifiers that belong to that exact variation.
Do not assume that all variations share one GTIN.
Google’s duplicate GTIN guidance advises merchants to submit a unique GTIN for each applicable variant and use item_group_id to group variations.
For example:
Red, size small: GTIN A
Red, size medium: GTIN B
Blue, size small: GTIN C
Blue, size medium: GTIN D
The variations may share:
Brand
Parent product
Item group ID
General description
They may have different:
Offer IDs
GTINs
MPNs
Prices
Stock quantities
Images
Colour and size values
If a manufacturer assigned only one GTIN to a product configuration, confirm exactly what that GTIN represents before reusing it across variations.
A parent SKU does not replace variation GTINs
WooCommerce allows a parent product and its variations to have different SKU arrangements.
A store may use:
One parent SKU with no variation SKUs
One parent SKU plus separate variation SKUs
Only separate variation SKUs
Imported warehouse codes
Automatically generated identifiers
None of these configurations automatically determines the correct GTIN.
The Merchant offer representing a variation should use the real identifier assigned to that variation.
If the exact variation genuinely has no identifiers, make the classification for that variation rather than copying another variation’s GTIN.
Used and refurbished products can still have GTINs
A product does not lose its manufacturer identity because it is sold as used or refurbished.
For example, a used branded smartphone can still have the GTIN assigned to that model and variation.
The product condition should be represented separately through the condition attribute.
Do not use identifier_exists: false merely because:
The packaging is missing.
The product is second-hand.
The barcode label is damaged.
The item has been refurbished.
The merchant acquired it through a customer trade-in.
Research the original product identity.
The condition and the identifier describe different aspects of the offer.
Books and media require particular care
Books commonly use ISBN-based identification.
A modern book may have an ISBN-13 that functions as the applicable GTIN.
Do not classify a modern book as identifier-free merely because the WooCommerce product was entered using:
The book title
An author name
A publisher code
An internal library code
An older ISBN format that was not mapped correctly
Some older books, media items or collectibles may genuinely predate modern identifiers.
Those cases should be investigated individually.
Do not apply one identifier rule to an entire books or media category.
Handmade products are not all the same
The word “handmade” does not automatically mean “no identifiers.”
Consider three different cases.
One-of-a-kind handmade item
An artist creates one unique ceramic object with no brand, MPN or GTIN.
Possible representation:
No GTIN
No MPN
No invented brand
identifier_exists: false
Repeatable branded handmade product
A workshop sells the same candle model repeatedly under its own brand.
Possible representation:
Workshop brand
Stable merchant-assigned MPN
No invented GTIN
Identifier treatment reflecting the existing brand and MPN
Customized branded base product
A merchant engraves a branded watch produced by another manufacturer.
Google’s customized product guidance advises using the identifiers of the product before customization where applicable and indicating that the final offer is customized.
Possible representation:
Original manufacturer GTIN
Original manufacturer brand
Original manufacturer MPN
is_bundle where applicable
Customization explained in the title and description
Price and image representing the final customized offer
These three products should not receive the same identifier configuration merely because manual work is involved.
Customisation does not erase an existing GTIN
A merchant may:
Engrave a product
Print a name on it
Add embroidery
Apply a custom colour
Add accessories
Personalise the packaging
Assemble a gift presentation
If the base product has genuine manufacturer identifiers, the customization does not automatically justify removing them.
The product data should describe both:
The identity of the underlying product
The customization being sold
Do not use identifier_exists: false merely to avoid researching the base product.
Private-label products need a stable identity
Private-label products are manufactured for sale under the merchant’s own brand.
They should be distinguished from unbranded one-off items.
For a private-label catalogue:
Use the genuine private-label brand.
Assign stable MPNs.
Keep one MPN attached to one defined product.
Define variation-level MPNs where necessary.
Document the internal identifier policy.
Avoid recycling identifiers.
Do not change identifiers during routine synchronisation.
Use GTINs when officially assigned.
A stable identifier policy also improves internal WooCommerce management.
It can help with:
Inventory
Returns
Supplier records
Product updates
Variation matching
Merchant operations
Structured data
Support investigations
Bundles and multipacks require separate identity checks
A bundle combines different products into one offer.
A multipack contains multiple identical products sold together.
The identifier depends on who created the commercial configuration.
For example:
A manufacturer-created bundle may have its own GTIN.
A manufacturer-created multipack may have its own GTIN.
A merchant-created bundle may use the main product’s applicable identifiers together with bundle information.
A merchant-created multipack should not automatically use a single unit’s GTIN without the correct multipack representation.
Do not assign identifier_exists: false to a bundle merely because the merchant assembled it.
First determine:
Whether the manufacturer assigned a bundle GTIN
Whether the individual products have GTINs
Which product is the main item
Whether is_bundle applies
Whether multipack applies
Whether the landing page accurately describes the configuration
This subject should be reviewed independently for complex bundles and multipacks.
Why invented GTINs are dangerous
An invented GTIN can create more problems than an honestly absent identifier.
It can cause:
Incorrect product matching
Association with another manufacturer
Association with another product
Duplicate GTIN issues
Incorrect price comparisons
Incorrect product information
Misleading Shopping results
Product warnings
Product disapproval
Repeated correction cycles
Conflicts between data sources
Loss of trust in catalogue information
Do not create a number by:
Padding the SKU with zeros
Removing letters from the SKU
Using a WooCommerce product ID
Combining brand and model digits
Copying a competitor’s product page
Using a random barcode generator
Reusing the supplier’s order number
Reusing one GTIN for an entire category
Reusing the parent product GTIN for every variation
A fabricated identifier is not improved product data.
It is inaccurate product data.
Why setting identifier_exists to false for every product fails
Some merchants apply identifier_exists: false globally because many WooCommerce products have empty GTIN fields.
This confuses two different situations:
The identifiers genuinely do not exist.
The identifiers are missing from WooCommerce.
Google may recognise common branded products and determine that a GTIN should exist.
Google’s incorrect product identifier guidance explains that offers may be affected when identifier_exists is submitted as false for a product Google believes has a unique identifier.
A global rule can therefore damage products that were previously eligible.
Classify products individually or by a carefully verified product group.
Do not use a catalogue-wide shortcut without confirming that every affected product genuinely meets the same conditions.
Audit the source of the WooCommerce product
Before changing identifier fields, determine how the product was created.
Possible sources include:
Manual product entry
CSV import
Supplier integration
ERP synchronisation
Marketplace import
Dropshipping catalogue
Previous feed plugin
Custom product importer
Product migration
WooCommerce REST API
Duplicate-product function
Ask:
Did the source contain GTIN?
Was the source field ignored?
Was GTIN imported into the wrong custom field?
Did the importer place EAN in an attribute instead of product metadata?
Did variation identifiers remain on the parent?
Was the GTIN removed during migration?
Is another plugin using a different field?
Does the supplier provide GTIN in a separate catalogue?
Is the current SKU actually a supplier code rather than an MPN?
Are old values still being submitted by another data source?
Correcting the field mapping can recover genuine identifiers without manually editing every product.
Create a product identifier inventory
For a large WooCommerce catalogue, prepare an internal identifier inventory containing:
WooCommerce product ID
Variation ID
SKU
Product title
Product type
Brand
Manufacturer
MPN
GTIN
GTIN source
Identifier verification status
Identifier exists decision
Product condition
Item group ID
Bundle status
Multipack quantity
Merchant offer ID
Data source
Last verification date
Useful verification statuses can include:
Verified from packaging
Verified from manufacturer
Verified from authorised supplier
Requires research
No identifiers confirmed
Merchant-manufactured
Private label
One of a kind
Antique or pre-GTIN
Conflicting identifier
Variation mapping required
This prevents “empty field” from being treated as a product classification.
Check the exact product variation
When researching a GTIN, compare:
Brand
Model
Colour
Size
Capacity
Material
Pack count
Target gender
Age group
Condition
Region where relevant
Included accessories
Product revision
A GTIN belonging to a 128 GB phone should not be assigned to the 256 GB version.
A GTIN belonging to one shoe size should not automatically be assigned to every size.
A GTIN belonging to a single unit should not automatically be assigned to a six-pack.
Match the complete commercial configuration.
Keep WooCommerce and structured data consistent
The product’s public structured data may include:
Brand
SKU
MPN
GTIN
Price
Currency
Availability
Condition
Variation information
Review whether:
The product page exposes one GTIN.
Merchant data submits another GTIN.
The parent structured data is shown on every variation.
The MPN changes after variation selection.
An SEO plugin generates placeholder identifier values.
The theme duplicates Product schema.
A previous product plugin still injects outdated data.
The landing page represents the submitted variation.
Structured data does not replace the Merchant product submission, but conflicting identity signals can make diagnosis more difficult.
Use one accurate product identity across the systems that describe the offer.
Review every active Merchant data source
A corrected WooCommerce field can be overwritten or contradicted by another active source.
Review:
Merchant API source
Scheduled feed
Uploaded file
Google Sheets source
Platform integration
Automatic website source
Supplemental data source
Previous WooCommerce plugin
Manual Merchant edits
For each source, determine:
Which offer IDs it controls
Whether it submits GTIN
Whether it submits brand
Whether it submits MPN
Whether it sets identifier_exists
Whether it updates automatically
Which source has priority
Whether it can restore an old value
Do not correct only one source while another continues to submit the inaccurate identifier.
Merchant API requires a Boolean decision
When product information is submitted through Merchant API, identifierExists is a Boolean field.
It should be represented as:
true
false
It should not be submitted as an explanatory sentence such as:
No GTIN
Not applicable
Custom product
None
N/A
Does not exist
The product’s title and description can explain that it is handmade or customized where appropriate.
The API attribute must use the supported data type.
Do not confuse technical acceptance with product eligibility
A Merchant API operation may accept product data containing no GTIN.
That does not prove that Google agrees the product has no identifiers.
The sequence is:
WooCommerce stores the product information.
The integration prepares the product resource.
Merchant API receives the operation.
Google processes the product.
Product identity and policy checks are applied.
Merchant Center displays the processed result.
Issues may appear after processing.
An accepted API response confirms that the request was received in an acceptable technical form.
It does not guarantee:
Product approval
Identifier correctness
Free-listing eligibility
Shopping-ad eligibility
Impressions
Clicks
Sales
Permanent acceptance
Inspect the processed product rather than relying only on the submission result.
How to review the product in Merchant Center
After submitting the product:
Open the correct Merchant Center account.
Open Products.
Review the Needs attention area.
Search for the exact offer ID.
Open the processed product.
Confirm the product source.
Confirm the GTIN value.
Confirm the brand.
Confirm the MPN.
Confirm the identifier-exists result.
Confirm the condition.
Confirm the item group ID for variations.
Review affected countries.
Review applicable marketing methods.
Record warnings or disapprovals.
Compare the processed values with WooCommerce.
Correct the authoritative source if necessary.
Resubmit the corrected product.
Allow processing time.
Review the result again.
Do not change unrelated fields until the identifier problem is understood.
What PW Merchant API can support
PW Merchant API provides an API-oriented workflow between WooCommerce and Google Merchant Center.
Depending on the installed version, settings and connected account, it can help merchants:
Review WooCommerce products.
Work with simple and variable products.
Inspect applicable product information.
Identify incomplete product records.
Prepare supported Merchant attributes.
Submit supported product operations.
Maintain controlled offer IDs.
Review operation results.
Display applicable Merchant product issues.
Synchronise supported product changes.
Compare WooCommerce and processed Merchant information.
This can help merchants determine whether a product record contains:
GTIN
Brand
MPN
Variation identity
Product condition
Offer ID
Applicable supporting attributes
PW Merchant API cannot independently determine the genuine manufacturer identifier when the source product information is incomplete.
It cannot:
Invent a valid GTIN.
Assign a manufacturer’s identifier.
Confirm unidentified packaging remotely.
Decide that a branded product has no GTIN without evidence.
Convert every WooCommerce SKU into an MPN.
Guarantee that Google accepts identifier_exists: false.
Override Google’s product-data requirements.
Guarantee product approval.
Guarantee Shopping visibility.
Guarantee clicks or sales.
Correct identifiers continuously supplied by another active data source.
Replace manufacturer or supplier verification.
WooCommerce should contain the most accurate available product information before the product is submitted.
Common mistakes
Using the SKU as GTIN
A WooCommerce SKU is not automatically a globally assigned product identifier.
Using the product ID as GTIN
A WordPress database ID has meaning only within that website.
Creating a random number
Passing a length or check-digit validation does not prove that the number belongs to the product.
Copying a competitor’s identifier
The competitor may sell another variation, pack quantity, region or product revision.
Using the same GTIN for all variations
Applicable variants can have different identifiers.
Marking all products as identifier-free
Some catalogue items may have GTINs even when others genuinely do not.
Removing brand to avoid GTIN requirements
A genuine brand should not be hidden or replaced with an inaccurate value.
Using the store name as every product’s brand
The merchant is not necessarily the manufacturer.
Submitting identifier_exists: false because the field is empty
Missing WooCommerce data is not proof that the real identifier does not exist.
Changing MPN during every update
An MPN should identify the product consistently.
Using one identifier for different pack quantities
A single item and manufacturer-defined multipack can represent different trade items.
Removing identifiers from used products
Product condition does not automatically remove the original manufacturer identity.
Stopping after an accepted API response
The processed product and its Merchant issues still need to be reviewed.
Frequently asked questions
Can I submit a WooCommerce product without a GTIN?
Yes, when the exact product genuinely has no manufacturer-assigned GTIN. Other applicable identifiers and identifier_exists must still be represented accurately.
Will Google automatically approve a product without GTIN?
No. Google independently evaluates the product, identifiers, website, account and applicable programme requirements.
Does an empty GTIN field mean I should use identifier_exists: false?
No. An empty field can indicate missing WooCommerce data. Research whether the real product has an identifier before declaring that none exists.
Can I use the WooCommerce SKU as a GTIN?
Not unless that value is genuinely the GTIN assigned to the product. A merchant-created SKU is normally an internal identifier.
Can I use the WooCommerce SKU as an MPN?
A reseller should use the real manufacturer part number. A merchant that genuinely manufactures or privately labels the product can maintain a stable manufacturer part number, but it should not be a temporary value created only for Merchant Center.
Do handmade products need GTINs?
Some genuinely unique handmade products may have no GTIN. Repeatable branded handmade products can instead use the merchant’s brand and stable MPN. Classify the actual product rather than relying only on the word “handmade.”
Can I set identifier_exists to false for custom products?
Only when applicable unique product identifiers genuinely do not exist. A customized version of an existing branded product may still need the original product’s identifiers.
Can I invent a GTIN for my product?
No. Use only a GTIN legitimately assigned to the product.
What if my supplier did not provide a GTIN?
Check the product packaging, manufacturer, authorised distributor information and the exact variation. Supplier data can be incomplete.
What if the product has a brand and MPN but no GTIN?
Submit the genuine brand and MPN. Do not invent a GTIN or incorrectly state that no identifiers exist.
Should private-label products use the store name as brand?
The store or private-label name can be used when it is genuinely the product’s brand and the merchant manufactures or owns the private-label product.
Does every variation need a separate GTIN?
Use the GTIN assigned to each exact variation. Do not copy one variation’s GTIN to others without manufacturer evidence.
Can used products keep their original GTIN?
Yes. Condition and product identity are separate attributes. A used product can retain the GTIN assigned to its model and variation.
Does changing the price require a new GTIN?
No. A price change does not create a new product identity.
Does changing the product image require a new MPN?
No. Routine image changes do not require a new manufacturer part number.
Does a successful API submission prove that the GTIN configuration is correct?
No. It confirms technical receipt of the operation. Review the processed product and Merchant Center issues.
Can PW Merchant API find a GTIN that the manufacturer did not provide?
It can work with product information available in WooCommerce and supported Merchant results, but it cannot invent or independently assign a manufacturer identifier.
Should I remove a GTIN to clear a duplicate-value warning?
Not automatically. Confirm whether the offers are duplicate records, variations, multipacks or genuinely different products. Correct the product identity and grouping rather than deleting accurate information without investigation.
Can a product without GTIN appear in free listings or Shopping ads?
Some genuinely identifier-free products can be eligible when their product data is accurate and all applicable requirements are met. No particular product placement or performance is guaranteed.
Final product identifier checklist
Before submitting a WooCommerce product without a GTIN, confirm that:
The exact WooCommerce product was identified.
The exact variation was identified.
The product ID was recorded.
The variation ID was recorded.
The SKU was recorded.
The Merchant offer ID was recorded.
The manufacturer was identified.
The genuine brand was identified where applicable.
The retail packaging was checked.
The barcode label was checked.
The manufacturer’s information was checked.
The authorised supplier’s information was checked.
The exact colour was checked.
The exact size was checked.
The exact capacity was checked.
The exact material was checked.
The exact pack quantity was checked.
The exact product revision was checked.
The product condition was checked.
The GTIN source was recorded.
The MPN source was recorded.
The WooCommerce SKU was not assumed to be a GTIN.
The WooCommerce product ID was not used as a GTIN.
The Merchant offer ID was not used as a GTIN.
No random number was generated.
No competitor identifier was copied.
No identifier from another variation was copied.
No single-unit identifier was incorrectly applied to a multipack.
No base-product identifier was removed merely because customization was added.
Used or refurbished condition was not mistaken for missing identity.
Books and media were checked for applicable ISBN information.
The merchant’s role as reseller, manufacturer or private-label owner was determined.
Private-label products received a stable identity.
Merchant-manufactured products received a stable MPN where appropriate.
One-of-a-kind products were classified individually.
Antique or pre-GTIN status was supported by the product’s real history.
identifier_exists was not set to false merely because WooCommerce was incomplete.
identifier_exists used the supported Boolean value.
Genuine brand information was retained.
Genuine MPN information was retained.
The GTIN field was left empty rather than filled with a placeholder.
The identifier decision was made per product or variation.
Structured Product data was reviewed.
WooCommerce and structured data used consistent identifiers.
Every active Merchant data source was identified.
Old feeds were checked for conflicting values.
Supplemental sources were checked.
Automatic website sources were checked.
Another plugin could not restore inaccurate identifiers.
The corrected WooCommerce product was saved.
The correct product was submitted.
The API operation result was recorded.
The processed Merchant product was opened.
Processed GTIN was checked.
Processed brand was checked.
Processed MPN was checked.
Processed identifier-exists status was checked.
Processed condition was checked.
Item group ID was checked for variations.
Bundle information was checked where applicable.
Multipack information was checked where applicable.
Target-country status was reviewed.
Marketing-method status was reviewed.
Needs attention issues were reviewed.
The authoritative source was corrected when necessary.
The product was resubmitted after correction.
Processing time was allowed.
The result was reviewed again.
No approval or performance guarantee was assumed.
A WooCommerce product does not become identifier-free simply because its GTIN field is empty.
The merchant should first determine whether the exact product, variation, condition and pack configuration has a genuine manufacturer-assigned GTIN.
When a GTIN exists, submit it accurately.
When no GTIN exists but the product has a genuine brand and MPN, submit those identifiers rather than inventing a GTIN or claiming that no product identity exists.
When the merchant manufactures or privately labels a repeatable product, a stable merchant brand and manufacturer part number can provide an appropriate identity.
When a product genuinely has no GTIN, brand or MPN—such as certain one-of-a-kind, handmade, antique or pre-GTIN products—identifier_exists can accurately communicate that condition.
The decision must remain factual.
Random numbers, copied identifiers, WooCommerce database IDs and internal SKUs cannot replace genuine manufacturer information.
PW Merchant API can support the WooCommerce-to-Merchant workflow, product review, supported attribute preparation, operation results and applicable issue visibility. It cannot assign genuine manufacturer identifiers or guarantee Google approval.
Accurate product identity begins with the real item.
Merchant Center should receive the same product identity represented by its packaging, manufacturer, WooCommerce record, variation, landing page and active product data source.
