Fixing “Invalid value: gtin” in Merchant Center

What Google is actually complaining about

Google validates gtin as a real barcode, not just a string of digits. It must be a UPC (12), EAN (13), JAN (8 or 13) or ITF-14 (14) — and the final digit is a check digit computed from the others. If that maths doesn't work out, the value is rejected no matter how legitimate it looks.

The usual culprits:

• Spreadsheet stripped the leading zero. Excel turns 0012345678905 into 12345678905 and the length is now wrong.
• Scientific notation. A long barcode saved from Excel comes out as 8.71E+12.
• Your own SKU in the GTIN field. SKU-4471 is not a barcode — that belongs in mpn.
• Hyphens or spaces — 012-345-678905.
• A made-up placeholder like 000000000000.

How to fix it

1. Format the GTIN column as Text before pasting, or edit the feed in a plain-text editor. This alone fixes most cases.
2. Strip every non-digit character.
3. Re-pad the leading zeros back to a valid length (8, 12, 13 or 14).
4. Verify the check digit. If it fails, the barcode is genuinely wrong — get the real one from the manufacturer.
5. If you don't have a GTIN, don't invent one. Remove the attribute entirely and send identifier_exists = no plus a valid brand and mpn. Custom-made and vintage goods are legitimately exempt.

A fake GTIN is worse than none: repeated invalid identifiers can escalate from item disapproval to an account-level warning.

What a correct row looks like

id,title,brand,gtin,mpn,identifier_exists
SKU-4471,Cast Iron Skillet 10in,Fieldstone,0012345678905,FS-CI-10,yes
SKU-4472,Hand-thrown Mug,Fieldstone,,FS-MUG-01,no

How long until the disapproval clears

Merchant Center re-crawls a scheduled feed on its normal cadence, so a fix can sit invisible for up to 24 hours. To force it: Products → Feeds → your feed → Fetch now, then re-check Diagnostics the following day. Items usually flip back to Active within one or two crawls once the attribute validates.

Other common disapproval causes