Invalid value: GTIN

Google found a value in your gtin field, but it doesn't pass Google's validation — either the format is wrong or the check digit fails.

The most common cause is a check-digit mismatch. GTINs include a final calculated digit that validates the rest of the number. If even one digit is off, the whole code is rejected. Other common causes: leading zeros stripped by Excel, GTINs from restricted ranges (e.g., starting with 04 or 05), or pasting an MPN where a GTIN belonged.

1. Run every GTIN in your feed through a check-digit validator before publish. There are free online tools and most feed platforms (including GoDataFeed) will do this automatically.
2. If you store GTINs in a spreadsheet, format the column as Text — never General — to prevent leading-zero stripping.
3. Verify the GTIN against an authoritative source (GS1, the manufacturer, the physical barcode). Don't trust user-supplied or scraped values.
4. For products in restricted GTIN ranges (often given out by retailers like Amazon for FBA), get a real GS1-issued GTIN.
5. Resubmit and wait for re-approval (24–72 hours).

• Excel stripping the leading 0 from a 12-digit UPC, turning it into an invalid 11-digit number
• Submitting Amazon-issued ASINs in the gtin field — ASINs aren't GTINs
• Re-using a single GTIN across multiple variants