Google Merchant Center invalid GTIN warnings often point to one of three distinct problems: the number does not meet GTIN formatting rules, the number belongs to a different product or variant, or Google expects an identifier that the submitted data does not contain. The right repair depends on which problem you actually have. Replacing every blank barcode with a random number is not a fix.
Independent troubleshooting guide · US-first examples · Reviewed October 31, 2026. Google requirements can vary by product category and destination country; use the exact notice in your Merchant Center account as your starting point.
Quick verdict: prove the identity of the item before changing the feed
Start with one affected offer in Merchant Center → Products → Needs attention. Record its item ID, exact diagnostic, target country and current GTIN, MPN, brand and identifier_exists values. Then compare those values with the manufacturer’s own information for that exact sellable item. Correct the original product record or feed mapping, trigger the normal synchronization, and check whether Google receives the new data. Do not repeatedly edit Merchant Center if Shopify or WooCommerce is going to overwrite that manual change.
The first decision is whether a manufacturer-assigned GTIN actually exists. If one exists, use that exact number; if none exists, do not invent one. Google recommends submitting a real GTIN where assigned and recognizes that some goods genuinely have none. The consequence of omitting an assigned GTIN may be limited performance; an inaccurate GTIN can produce a product-level issue or disapproval. See Google’s GTIN specification and unique product identifier guidance.
This is a product identity problem, not necessarily a sitewide policy suspension. If your account has an actual policy enforcement notice, follow the separate Merchant Center misrepresentation suspension guide. Shipping-policy gaps belong in our missing shipping information diagnostic; conflicting landing-page prices belong in the price mismatch troubleshooting guide.
1. Read the precise diagnostic before choosing a remedy
Several Merchant Center messages sound similar but require different work. Google distinguishes invalid value GTIN, incorrect GTIN, missing or incorrect GTIN, and limited performance due to missing GTIN. The labels may appear differently depending on your source, country and interface.
| Issue displayed | What it often means | First evidence to check | Wrong shortcut |
|---|---|---|---|
Invalid value [gtin] | Number has an invalid format, check digit or other restricted characteristic | Exact digits, GTIN length, check digit, prefix | Adding or dropping a digit at random |
| Incorrect GTIN / incorrect product identifier | Number may be structurally valid but identifies another item | Supplier catalog, package, brand, variant | Reusing a sibling product’s barcode |
| Missing or incorrect GTIN | Required identifier combination is absent or unrecognized | Does the item have an assigned GTIN? What brand/MPN exists? | Filling the field with an internal SKU |
| Limited performance: missing GTIN | Google suspects a manufacturer GTIN exists but none was supplied | Manufacturer’s barcode and product category | Assuming every warning means disapproval |
Incorrect identifier_exists | Product is marked as identifier-free although Google has evidence otherwise | Manufacturer identifiers and source mapping | Setting false across all products |
What to capture: diagnostic wording, number of affected offers, affected countries, product IDs and variations, data source name, last successful source update and one representative product URL. A spreadsheet with those fields is more useful than screenshots of a warning alone.
Google notes that a data source can successfully process while products still show attribute or policy problems. The source-processing report is not a substitute for Needs attention. Its data source troubleshooting instructions distinguish processing from broader product diagnostics.
2. Understand GTIN, MPN, brand, SKU and item ID
Merchants often use these terms interchangeably; Google does not. A GTIN is intended to identify a globally traded product. An MPN is a manufacturer’s part number, generally unique within that brand. A SKU is a merchant’s own stock-control code, while the Merchant Center id attribute identifies the submitted offer in that merchant’s feed. Those last two are not automatically GTINs.
| Identifier | Purpose | Who assigns it | Can you invent one to fix a GTIN error? |
|---|---|---|---|
GTIN [gtin] | Global product identity: UPC/EAN/JAN/ISBN/GTIN-14 | GS1 identification system / manufacturer or authorized owner | No |
MPN [mpn] | Distinguishes a model or item from the same manufacturer | Manufacturer | No for someone else’s branded item; special owner-manufacturer cases differ |
Brand [brand] | Identifies the marketed brand | Brand/manufacturer | Use the genuine product brand, not a placeholder |
| SKU | Internal stock management | Merchant | You may create a SKU, but it is not thereby a GTIN |
Item ID [id] | Stable offer key in your submitted data | Merchant/feed system | It may be internally assigned, but don’t casually change it to repair GTIN |
identifier_exists | Declares whether assigned identifiers are available | Feed provides true/false | false only when justified by the actual item |
A practical example: a merchant’s SKU might be BLUE-SHIRT-M, but that text is not a GTIN. The GTIN is the verified numeric identifier on the manufacturer packaging for the medium blue shirt. The same shirt in another color may have a different number. Assigning the same GTIN to every variant makes different offers appear identical when they are not.
There is one nuance worth treating carefully. Google allows a business that manufactures and is the only seller of a product without an assigned MPN to create its own stable MPN, and to use its store brand appropriately. That exception does not authorize a reseller to fabricate a manufacturer’s part number for an established brand. Follow the MPN documentation and brand requirements, not a generic bulk rule.
3. Run a 20-minute one-product diagnostic
Choose a representative affected product, ideally a simple single-variant item before tackling bundles or complex apparel. This sequence is a recommended workflow, not a guaranteed time-to-resolution or a claim that Google has a twenty-minute review cycle.
- Identify the exact offer. In Products → Needs attention, filter by the precise diagnostic and open a single affected item. Record country, language and item ID. Don’t confuse the variant record with the parent product.
- Trace the source. Is the offer fed by the Shopify Google & YouTube app, Google for WooCommerce, another plugin, a scheduled file, a Merchant API integration or a supplemental source? Note which system actually controls the value.
- Inspect the submitted attributes. Record the GTIN exactly as transmitted, preserving leading zeros. Also capture brand, MPN, item ID, variant attributes, and
identifier_existswhere present. - Find manufacturer evidence. Check the packaging, authorized manufacturer catalog or distributor information. A barcode printed by your warehouse for internal picking is not automatically a GTIN.
- Classify the defect. Is the GTIN absent, structurally invalid, valid but assigned to a different product, duplicated across variants, or correctly absent because the item genuinely has no identifier?
- Correct the authoritative record. Fix the source product/variant or mapping. Avoid applying conflicting edits in several systems at once.
- Resync and compare. Confirm the integration has submitted the corrected value, inspect what Merchant Center now shows, and monitor the affected item’s diagnostic rather than assuming success after pressing Save.
If multiple products exhibit the same problem, sample a small set across brands and categories before bulk editing. Ten errors caused by one field mapping can be solved centrally; ten errors caused by ten incorrect manufacturer barcodes require item-level research. A bulk overwrite is efficient only after you know which situation you have.
4. Validate a GTIN without confusing a valid number with a correct number
Google accepts common GTIN formats including 8, 12, 13 and 14 digits, with specific treatment for UPC-E and ISBNs. Product data fields can contain multiple valid identifiers under Google’s specification; most ordinary variants still require the appropriate identifier for that actual sellable unit. Check current details in Google’s GTIN attribute guide.
First check the length. Is the number truly a GTIN rather than an internal stock number? Preserve leading zeros when exporting into spreadsheets. If Excel interprets a barcode as a number, it may remove a leading zero and damage the value. Store GTINs as text in your product data process.
Next check the check digit using an official GS1 method. A valid check digit helps detect transcription errors; it cannot prove that the identifier belongs to the product being offered. A mathematically valid number borrowed from another item’s package is still the wrong number. The same is true of a number that belongs to an individual unit when your offer actually represents a manufacturer-defined pack with its own assigned GTIN.
Then check restricted or coupon ranges and the relevant GTIN formatting restrictions. Google documents excluded ranges and references the official GS1 validation guidance. Do not attempt to fix a prohibited value by changing its first digits. Return to the manufacturer and identify the proper item code instead.
Finally, verify identity: product name, brand, size, color, model, packaging configuration and whether the item is retail, used or refurbished. A retailer that sells multiple products from a single brand should not copy the first barcode into every line simply because the brand matches. An incorrect GTIN may be syntactically well formed and still wrong.
5. Shopify: fix the variant data, then inspect Google & YouTube sync
For Shopify stores, the first place to look is the product or variant barcode field, not a Merchant Center override. Shopify’s barcode help explains that barcode values can be entered per product or variant, including through bulk editing or CSV import. The interface and supported barcode types can change, so use the current admin labels.
- Open Shopify admin → Products and select the affected product. If it has variants, select the exact variant flagged by Google rather than the product title alone.
- In the relevant Inventory / Barcodes field, compare the existing value with manufacturer evidence. Correct a transcription error, insert the genuine assigned GTIN, or leave the GTIN field blank if none exists.
- Confirm the field is using the appropriate barcode type where Shopify makes that distinction. Shopify also supports custom barcodes, which are useful operationally but must not be mistaken for GTINs merely because they are scannable.
- Open the Google & YouTube channel and inspect the affected product’s synchronization or required fields. For a product without a GTIN, Shopify’s Google channel guidance says to provide applicable brand and MPN information through the channel.
- Save, allow synchronization, then open Merchant Center to confirm the expected value arrived. A cleared Shopify form field is not sufficient evidence if the channel continues transmitting a different mapped value.
Common Shopify failure: apparel sizes have correct individual SKUs but a shared product-level barcode has been copied into all variants. Google may distinguish those variants by size/color and expects the corresponding real GTIN for each sellable variation. Fix the variant records individually or via a controlled import. The Shopify syncing guide also describes missing GTIN/MPN diagnostics and the brand-plus-MPN alternative for products without barcodes.
Another failure occurs when a merchant exports CSV data, edits it in a spreadsheet, and reimports a shortened GTIN after leading zeros were lost. Before a broad import, export two rows and verify the identifiers as text. Keep a backup of the original file and confirm that the SKU-to-variant relationship did not change. The same catalog hygiene helps prevent related product-page issues; see StackScale’s Shopify product page optimization guide for a broader audit of product presentation consistency.
6. WooCommerce: check the Global Unique ID and the active integration
WooCommerce has more possible storage and mapping arrangements. Google for WooCommerce now supports the built-in Global Unique ID / GTIN field added to WooCommerce core, and WooCommerce recommends using that core field for synchronization. Older stores may instead have identifier data held in legacy plugin fields or custom metadata; the current extension includes a migration path. See its GTIN documentation.
- In Products, inspect the affected simple product or variation, including its Inventory section and any Global Unique ID field available in your installed version.
- Determine which Google integration is active. Don’t assume that a plugin called Google Product Feed and the official Google for WooCommerce integration read identical fields or use the same sync mechanism.
- Check Google for WooCommerce product issues and the attribute mapping settings. Its product feed guide explains where to find feed problems and how unique identifiers are handled.
- For existing installations with legacy GTIN storage, review the official migration workflow and back up first. Avoid running an identifier migration during a live catalog import or while multiple feed providers are writing changes.
- Update the authoritative field, allow the scheduled/API sync to execute, then confirm the item data in Merchant Center.
If your site uses a different WooCommerce feed extension, consult that extension’s own GTIN, MPN and brand mapping rules. For example, WooCommerce’s separate Google Product Feed extension has product-level and variation-level metadata and a different configuration model. Its setting product data instructions describe those fields. A merchant can waste hours editing core WooCommerce product fields that a legacy feed mapping does not actually read.
For stores with multiple feed plugins, first establish one authoritative product feed. Two sources pushing inconsistent product data can create changes that appear to reverse themselves. This is analogous to other integration risks discussed in our Shopify to WooCommerce migration guide: the transfer path matters as much as the presence of the information in the store database.
7. What to submit when a product genuinely has no GTIN
Not every product requires a GTIN. Google lists examples including custom-made, handmade, one-of-a-kind and some vintage or store-brand goods. For relevant cases, submit the identifiers that genuinely exist and use identifier_exists appropriately. The governing rule is factual: do not say an identifier does not exist just because you cannot find it today. Google’s identifier_exists documentation warns against setting it to false when evidence of an identifier exists.
A handmade item with no assigned GTIN, MPN or brand may legitimately use identifier_exists=false where appropriate. A private-label product that your business manufactures and sells under its own brand can instead have your real brand and a stable self-assigned manufacturer part number where Google’s special manufacturer-owner guidance permits that. Different categories, conditions and jurisdictions have different identifier requirements; check the product-specific rules before choosing a blanket approach.
A reseller of a known branded item should try to obtain the manufacturer’s assigned barcode or part number. Do not classify the product as handmade because your store uses custom packaging. Do not convert a vendor’s arbitrary SKU into an MPN unless that value genuinely represents the manufacturer’s part number.
Example: you sell original hand-painted ceramics with no official identifiers. That differs fundamentally from reselling a commercially manufactured branded mug whose GTIN was omitted from a supplier spreadsheet. The ceramic may qualify for an identifier-free submission; the mug should be matched to its proper assigned identifier. They should not receive the same bulk-feed rule.
8. Handle variants, multipacks, bundles and books deliberately
Complex offers are where reasonable-looking GTIN fixes often fail. The rule is to identify the sellable unit and follow the product-type guidance rather than copying codes between related items.
| Product situation | Recommended check | Potential mistake |
|---|---|---|
| Shirt offered in blue/red and S/M/L | Confirm manufacturer GTIN for each distinct retail variant | Applying one parent barcode to every variation |
| Manufacturer-created multipack | Confirm GTIN assigned to the manufacturer’s actual pack | Using the single-unit code for the pack |
| Merchant-created bundle | Follow Google’s bundle rules for the main product and related bundle attributes | Inventing a new GTIN for an in-house kit |
| Used branded product | Supply original manufacturer GTIN where available and correct condition | Pretending a used item is unbranded |
| Unique antique | Verify whether reliable identifying codes exist and whether identifier_exists applies | Marking every older item identifier-free by default |
| Book with ISBN | Use the accepted book identifier, normally ISBN-13, in the relevant Google format | Treating an Amazon ASIN as a substitute GTIN |
Google’s GTIN guidelines and product identifier overview contain the specific provisions for variants, bundles, store-brand items, books and used goods. One selling context can change which identifier should be attached to an offer even when the physical components appear similar.
Illustrative case: a retailer sells a branded water bottle individually and in a manufacturer-sealed two-pack. The single bottle’s code does not automatically identify the two-pack. Before publishing both offers, verify whether the manufacturer assigned a separate GTIN to the retail multipack. If the retailer creates a custom kit with accessories, use Google’s merchant-created bundle guidance instead of manufacturing a fictitious GTIN.
9. Correct at scale without corrupting the next feed update
When hundreds of offers are affected, classify them by brand, product type, feed source and error code. A single platform mapping defect deserves a mapping fix; a scattered set of wrong manufacturer barcodes deserves row-by-row validation. Begin with a five-item pilot across your most common cases before importing an entire catalog.
Use a simple worksheet with columns for: Merchant Center offer ID; parent/variant ID; issue label; country; old GTIN; verified GTIN or reason none exists; brand; MPN; identifier_exists; source field and integration; person approving the data; update timestamp; and result after sync. Preserve a copy of the pre-change export. Mark the manufacturer evidence and the synchronization outcome separately so the team can distinguish a corrected source record from a confirmed Google-side update.
If a supplemental data source is part of your setup, remember that it updates items already represented in a primary source rather than creating standalone products. Google’s source creation guide also notes that supplemental sources require the advanced data source management add-on. Most small stores should first repair their primary platform data rather than introduce another synchronization layer merely to silence GTIN errors.
A bulk repair can also create merchandising risk: a GTIN mapping that belongs to one product may accidentally flow into titles or variant groups of another. Validate the data and inspect representative landing pages after importing. For mixed-store platform operations, our Shopify vs WooCommerce comparison discusses the broader trade-off between simpler managed workflows and more configurable extension stacks; neither platform removes the need for sound item-level data.
10. Verify the fix: product data, source processing and visibility
After saving the original product or integration configuration, give the connected source time to transmit new data. For a file source, look at the latest update and whether the file was successfully processed; for an API-connected source, review its synchronization status. Then inspect the affected offer in Merchant Center to confirm the expected identifier is present.
Use Products → Needs attention to see whether the issue remains. A clean source-processing report alone is insufficient; Google explicitly separates the processing view from product-level diagnostics. Updates may take time to propagate and eligibility can be affected by unrelated requirements. See Google’s check-product-data instructions and data source troubleshooting.
For verification, record three outcomes rather than one binary “fixed” status: source corrected, Merchant Center received, and diagnostic resolved or next issue identified. If the same incorrect GTIN reappears after the scheduled sync, investigate competing sources or data transformation rules. If the correct GTIN appears but the item remains disapproved, open the new diagnostic and check whether the remaining problem is a different attribute or policy.
Do not confuse a cleared GTIN error with guaranteed ad delivery or increased traffic. Campaign eligibility, bidding, competing offers, category restrictions and account compliance are separate. Our Merchant Center misrepresentation troubleshooting guide covers the different case of account-level policy issues.
11. FAQ: questions merchants ask after seeing a GTIN warning
Can I use my Shopify SKU as the GTIN?
No, unless the SKU happens to be the actual correctly assigned GTIN and has been verified as such. A stock code does not become a global product identifier because it fits in the barcode field. Keep SKU and GTIN distinct in your data process.
Do handmade products need a barcode for Google Shopping?
Some genuinely handmade or one-of-a-kind goods have no assigned GTIN, and Google provides an identifier-free path for appropriate products. You still need to meet other data and category rules. Don’t use this exception for commercially manufactured items merely because the supplier omitted the barcode.
What if a GTIN passes the check digit but Google still says incorrect?
The number may identify a different product or variation. Recheck brand, packaging level, color, size and model against manufacturer evidence. A check digit tests form, not ownership or product match. Also inspect whether the correct value reached the feed at all.
Should every variation have a separate GTIN?
When manufacturers assign different GTINs to different sellable variations, use the specific number for each. Google’s GTIN guidance explicitly covers distinct colors and sizes. Verify the source SKU/variant mapping so that one parent value is not blindly repeated.
Can I set identifier_exists=false for every product without a barcode in my database?
No. Missing data in your database is not proof that the manufacturer never assigned an identifier. First investigate manufacturer and category requirements. Google cautions that a false declaration for a product with an existing identifier can trigger warnings or disapproval.
Does fixing GTIN guarantee approval or rankings?
No. It removes one potential product-data defect. Other product or account issues may remain, and a valid feed does not guarantee ad impressions or improved organic placement. Evaluate the actual post-sync diagnostic, not just the form field.
StackScale verdict: fix identity at the source, then prove receipt
Most stores do not need a new product-feed subscription to solve an invalid GTIN. They need an authoritative record of which item each code belongs to, consistent variant mappings and a repeatable source-to-Merchant-Center verification process. Repair one representative item; confirm the integration reads the corrected field; then scale only the fixes supported by evidence.
For continued troubleshooting, use our focused guides on Google Merchant Center shipping information, price mismatch and misrepresentation suspensions. They diagnose different failure classes and should not be treated as interchangeable.
Methodology and primary sources
This guide was prepared from the current public Google, Shopify and WooCommerce documentation, checked October 31, 2026. It does not claim hands-on access to a merchant’s Merchant Center account, manufacturer barcode registry or live product feed. Vendor rules and dashboards may change; always use the precise issue notice and current integration version.
- Google: GTIN
[gtin]attribute - Google: About unique product identifiers
- Google: Invalid value
[gtin] - Google: Incorrect GTIN
- Google: Identifier exists
[identifier_exists] - Google: Brand and MPN rules
- Shopify: Barcodes
- Shopify: Google & YouTube requirements
- WooCommerce: Google for WooCommerce GTIN
- WooCommerce: Google for WooCommerce product feed
Editorial disclosure: StackScale is an independent ecommerce software research publisher. This article contains no affiliate links; no software purchase is necessary to perform the described diagnosis.





