Guide · Google Merchant Center

How to Fix Missing and Invalid GTIN Errors in Merchant Center

"Missing value [gtin]" and "Invalid value [gtin]" quietly cap your Shopping reach. Here is how to fix each variant properly – and when the right fix is no GTIN at all.

The short version: A GTIN is the barcode number issued by GS1 for a product – nothing else qualifies. If your products have real GTINs, submit them exactly as printed (12 to 14 digits). If they do not, set identifier_exists to "no" and supply brand plus MPN instead. Never invent, guess, or reuse numbers: invalid GTINs disapprove faster than missing ones.

1. Know which error you actually have

Merchant Center reports several distinct identifier problems, and each has a different fix. "Missing value [gtin]" means Google expects a GTIN for this product category and the field is empty. "Invalid value [gtin]" means a number is present but fails validation – wrong length, bad check digit, or a number that is not a GTIN at all. "Restricted GTIN" means the number belongs to a range Google will not accept. Read the exact wording in Diagnostics before changing anything.

2. Where real GTINs come from

A genuine GTIN comes from the product's manufacturer via GS1, and it is printed under the barcode on the packaging. It is 12 digits (UPC, common in North America), 13 digits (EAN, common elsewhere), or 14 digits for multipacks. If you manufacture the product yourself, you license your own GTINs from GS1. If you resell, the GTIN belongs to the brand – get it from the supplier's data sheet or the physical packaging, not from a competitor's listing.

3. The usual causes of "invalid GTIN"

In feed audits, the same patterns repeat: internal SKUs pasted into the GTIN field, placeholder sequences, ISBNs used for non-book products, numbers with spaces or dashes copied from spreadsheets, and one GTIN reused across variants that each have their own barcode. Excel is a frequent culprit – it strips leading zeros and converts long numbers to scientific notation, corrupting the value before it ever reaches the feed. Store GTINs as text.

4. When the correct fix is no GTIN

Plenty of legitimate products have no GTIN: handmade goods, custom and configurable products, vintage items, store-brand products never assigned one, and replacement parts sold without retail packaging. For these, submit brand and MPN and set the identifier_exists attribute to "no". That is a complete, policy-compliant answer. What triggers disapprovals is leaving the field blank on products Google believes have GTINs, or filling it with a fabricated number.

5. Fix it at the source, not in the feed file

If your feed is generated from WooCommerce, Shopify, or a PIM, correct the identifier data in the platform – a hand-edit to an exported CSV lasts until the next scheduled fetch overwrites it. Map the fields properly: GTIN to gtin, manufacturer part number to mpn, and the actual brand to brand. Then let one full feed cycle run and re-check Diagnostics; identifier fixes usually clear within a processing cycle or two.

6. What good looks like afterwards

Products with valid GTINs become eligible for richer placements and better matching, because Google can tie your listing to its product catalog with confidence. Track the disapproved and limited-performance counts weekly for a month after the fix. If identifier errors creep back, the cause is upstream – usually new products being added without an identifier check at intake.

Identifier errors capping your reach?

We run structured Merchant Center feed diagnostics: audit, root-cause mapping, remediation, and verification – identifiers included.

Related: Diagnosing Merchant Center feed errors · Fixing price mismatch errors · Merchant Center feed diagnostics

WhatsApp Us
WhatsApp Us Discuss Your Requirements