Google Merchant Center: Fix Invalid GTINs

Identify what Merchant Center is rejecting

Start from the item-level diagnostics in Merchant Center, not from a guess about the check digit. A GTIN can be mathematically valid and still be the wrong identifier for a particular product. Google recommends supplying the genuine manufacturer-assigned GTIN when one exists. Do not invent a number merely to pass validation.

Check format and the final check digit

Google accepts GTIN structures of 8, 12, 13 and 14 digits according to its product data specification. A GTIN-12 is commonly used with UPC-A, while GTIN-13 is commonly used with EAN-13. An eight-digit UPC-E must be expanded into GTIN-12 before being supplied as UPC. Keep the original complete identifier intact.

The final GTIN digit is determined by the GS1 modulo-10 algorithm. Use the GTIN Validator for a single value or the bulk CSV checker for an entire exported feed. These tools check mathematical structure only; they do not access Google’s diagnostics or GS1 ownership records.

When a checksum fails, verify the complete identifier from the manufacturer. Simply replacing the final digit could disguise an error elsewhere in the number.

Google-specific restrictions are separate from GS1 arithmetic

Merchant Center publishes requirements beyond the checksum, including restrictions on particular prefix ranges, such as values beginning with 02, 04 or 2. Consult the current Google GTIN attribute policy for the applicable restrictions and exceptions.

A valid check digit does not prove that the identifier was licensed to a company or assigned to the item being sold. ProductPassKit does not claim that a positive structural validation result makes a product listing eligible or approved.

Prevent spreadsheets from removing leading zeroes

GTINs are strings of digits, not ordinary numeric quantities. When importing or exporting a Merchant Center feed, keep GTIN fields formatted as text. Spreadsheet software can strip leading zeroes and silently change a GTIN-12 into an unsupported 11-character value.

For systems requiring exactly 14 characters, shorter GTINs can be represented with filler zeroes on the left. That storage representation is not a new GTIN allocation. Read the GTIN guide before changing the identifier format your feed expects.

What if the product has no assigned GTIN?

Not every product has a GTIN. Google describes cases such as private-label and store-brand products where a GTIN may not exist. Never create a pretend GTIN to make a form accept a value. Follow Google’s current unique-identifier guidance, including any applicable brand, MPN and identifier fields, based on the actual product.

A safe CSV troubleshooting workflow

1. Export the affected item identifiers from your own product catalogue or feed without altering their text formatting.
2. Use Bulk GTIN Validator to identify bad lengths, checksum errors and repeated values.
3. Match each flagged row back to your manufacturer’s or supplier’s authentic product records before changing anything.
4. Review Google-specific restrictions and assignment problems directly in Merchant Center.
5. Correct the source feed, reprocess it through your normal workflow and confirm the diagnostics are resolved.

For isolated math errors, consult the step-by-step check digit calculation. ProductPassKit cannot submit feeds, request Merchant Center reviews or verify licence ownership for you.