How to Fix “Invalid value [gtin]” in Google Merchant Center

Products disapproved for Shopping listings, or a yellow warning that appeared out of nowhere? Here is what Google actually checks, and the fastest order to check it yourself.

A GTIN problem in Google Merchant Center usually shows up one of two ways: items land in the Needs attention tab with a hard disapproval such as Invalid value [gtin], or they keep serving but carry the softer Limited performance due to missing value: GTIN [gtin] warning. The reassuring part: these are mechanical issues. Google runs structural checks on a number, and you can reproduce every one of them before re-uploading.

What this error actually means

Merchant Center validates the gtin attribute against the GTIN standard. Google's product data specification requires a value that is 8, 12, 13, or 14 digits long — the lengths of GTIN-8, UPC-A, EAN/JAN and ISBN-13, and GTIN-14 — with a correct check digit in the final position, and it excludes numbers in restricted ranges (prefixes 2, 02, 04) and coupon ranges (prefixes starting 05, 99, or 981–984).

“Invalid value [gtin]” means the number you submitted failed that structural test — it says nothing about your account or product quality. The usual causes:

• A digit lost or gained — most often a leading zero stripped by a spreadsheet, leaving 11 digits instead of 12.
• A number exported in scientific notation, like 8.85909E+11.
• One mistyped digit, which breaks the check digit.
• An internal SKU or MPN pasted into the gtin column.

Invalid, incorrect, unsupported, missing — which one do you have?

Google splits GTIN problems into distinct issues with different fixes, so read the exact wording in your diagnostics first:

• Invalid value [gtin] — the number is structurally broken: wrong digit count, stray characters (Google ignores spaces and dashes, but nothing else), or a failed check digit. Fix the number itself.
• Incorrect value [gtin] — the number is well-formed, but Google's data says it identifies a different product — often one manufacturer GTIN reused across colors or sizes. Each variant needs its own manufacturer-assigned GTIN.
• Unsupported or restricted GTIN — the number sits in a range that is not globally valid: restricted-distribution and variable-measure prefixes (2, 02, 04) or coupon prefixes (05, 99, 981–984). These are typically in-store codes that were never meant for global listings.
• Limited performance due to missing value [gtin] — a warning, not a disapproval. No GTIN was submitted; the item can still serve, but may see limited visibility if the product actually has an assigned GTIN.

The fix path, in order

Work through these checks in sequence — each one only matters if the previous one passes.

1. First, confirm the raw value survived your export. Open the feed file itself, not your platform's admin screen. The value must contain 8, 12, 13, or 14 digits — Google's spec ignores spaces and dashes, but any other character fails validation. If UPCs arrive as 11 digits, your spreadsheet ate the leading zero; if you see E+ notation, the export mangled the column. Our guide to Excel leading zeros and barcodes fixes both.
2. If the length passes, verify the check digit. Paste the number into the GTIN check digit calculator. A failure means at least one digit is wrong — go back to the physical packaging or the manufacturer's spec sheet and re-read it. Do not simply recalculate a new check digit onto the mistyped body: that produces a well-formed number belonging to nobody — or to someone else's product — and trades an invalid-value error for an incorrect-value one. (See how check digits work for the math.)
3. If the check digit passes, look at the prefix. Numbers beginning 2, 02, or 04 are restricted ranges, and 05, 99, or 981–984 are coupon ranges. A code in these ranges is not a globally valid GTIN, however correct its checksum. Get the real GTIN from the manufacturer — or if the product genuinely has none, see step 5.
4. If the number is clean, confirm it matches the exact product and variant. A navy medium and a navy large are different GTINs. Books use the ISBN-13 as their GTIN — if you only have the older 10-digit form, run it through the ISBN converter rather than typing 978 in front, because the check digit changes.
5. If the product truly has no GTIN, say so honestly. Set identifier_exists to false for custom or handmade goods, one-of-a-kind items, and products made before GTINs existed (Google's examples include books published before 1970). It is not an escape hatch for ordinary branded stock — Google states such products are flagged when there is evidence an identifier does exist.
6. Fix the data at its source, then re-upload. In Merchant Center, go to Products → Needs attention, filter by the issue, and either edit items individually or download the CSV of affected products to work through in bulk. Correct the value wherever the feed originates — platform, feed file, or API — or the next scheduled fetch will reintroduce it. Google says changes can take roughly 24–72 hours to show in diagnostics, so batch all corrections into one pass.

Before re-uploading, check the entire column at once instead of waiting three days to discover stragglers. The bulk barcode validator takes a pasted list of GTINs and flags wrong lengths and failed check digits line by line, so the feed you send is the feed that passes. If your data mixes 12-digit UPCs and 13-digit EANs, the UPC to EAN converter handles the padding correctly.

What to send support if nothing works

If every check above passes and the disapproval persists after a re-crawl, contact Merchant Center support through your account's help panel with a tight, factual package:

• The exact issue name from your diagnostics (“Invalid value [gtin]” vs. “Incorrect value [gtin]” matters).
• Three to five affected offer IDs with the GTINs you submitted for them.
• Where each GTIN came from — manufacturer packaging, a GS1 license certificate, or distributor data. A photo of the physical barcode is strong evidence.
• What you have ruled out: length, checksum, and restricted ranges.
• When you last re-uploaded corrected data, since reviews lag 24–72 hours behind changes.

What won't work

A few tempting shortcuts reliably fail. Re-submitting the identical feed produces the identical verdict. Inventing sequential GTINs, or borrowing a plausible-looking one, converts a fixable format error into a data-quality problem. And a pass in any checksum tool — ours included — proves only that the number is internally consistent; it does not prove the GTIN is licensed to your brand in the GS1 registry. Google and other marketplaces increasingly cross-check submitted identifiers against manufacturer and product-catalog data — that is exactly what the “Incorrect value” issue is — which is why the only durable fix is the number the manufacturer actually assigned. The same principle applies on other channels: Amazon error 5665, eBay's invalid UPC error, Shopify's invalid GTIN warning, and our broader guide to fixing invalid GTIN errors on Amazon.

FAQ

What does “Invalid value [gtin]” mean in Google Merchant Center?

The value in the gtin attribute failed structural validation: it does not contain 8, 12, 13, or 14 digits, contains stray characters (Google ignores spaces and dashes, but accepts nothing else), or its check digit does not match the GS1 mod-10 calculation. It is a data-format problem, fixed by correcting the number in your feed.

Is “Limited performance due to missing value [gtin]” the same as a disapproval?

No — it is a warning. The product can still appear, but Google notes that products with an assigned GTIN submitted without one may get limited visibility. If your product has a GTIN, add it; if it genuinely has none, set identifier_exists to false instead.

Can I set identifier_exists to false to make the GTIN error go away?

Only if the product genuinely has no GTIN — for example custom or handmade goods, one-of-a-kind items, or products made before GTINs existed, such as books published before 1970. Google states that products marked this way are flagged when there is evidence that an identifier actually exists, so it will not rescue ordinary branded stock.

How long does Merchant Center take to recheck a fixed GTIN?

Google's help pages say changes can take roughly 24 to 72 hours to appear in product diagnostics after you re-upload corrected data, so fix everything in one pass rather than one field at a time.

General information only; CodeClassify is not affiliated with Google, and requirements change — confirm current rules in Google's help documentation. Checksum validation confirms internal consistency, not GS1 registration; GTIN licensing is managed by GS1 member organizations.