Export the affected-products list
In Merchant Center, open Products → Needs attention, filter for Invalid value [gtin], and download the affected-products CSV. Keep the product ID column unchanged.
Invalid value [gtin]
Trace every invalid GTIN back to its source row.
Cross-reference Google’s affected-products CSV with the feed that generated it, validate file-level GTIN problems, and repair the source without guessing across thousands of products.
Open the source feed locally
Choose the CSV or TSV that generated those offers. FeedPatch keeps the file in your browser, validates GTIN length and check digits, and records the original source row.
Match Google IDs to exact rows
Add the affected-products CSV in the ID-list slot. FeedPatch joins Google’s IDs to the source id column and produces matched and unmatched rows instead of forcing you to search the catalog manually.
Verify the real identifier
Confirm the GTIN on the manufacturer packaging or authoritative product record. Google accepts supported GTIN lengths but also requires a valid check digit and the correct identifier for that exact product or variant.
Do not invent a replacement
A store SKU, another variant’s barcode, or a guessed number is not a safe GTIN. If the product truly has no assigned GTIN, follow Google’s identifier rules and provide applicable brand and MPN data rather than fabricating a code.
Correct the source and re-upload once
Update the source of truth, inspect the exported repair map, and submit the corrected data again. Google notes that Needs attention may take 24–72 hours to reflect the change.
Product boundary
Validate the file. Verify the product identity at its source.
FeedPatch can flag invalid GTIN length or check digits and locate affected rows. It cannot query GS1, inspect packaging, see every Merchant Center data source, or decide whether a barcode belongs to the product you sell.
Run the free feed auditOptional repair export
Locate GTIN problems free. Upgrade for the corrected full-feed download.
FeedPatch Pro applies safe, reviewable formatting normalizations after you identify the correct source rows. It never invents or substitutes product identifiers.
$79USD
per year
per year
- Free GTIN and affected-row checks
- Full-feed safe normalization export
- Source feeds up to 100 MB
- 14-day refund policy
Frequently asked
Before changing a barcode.
What does Invalid value [gtin] mean?
Merchant Center received a GTIN that does not meet Google’s requirements. Common causes include the wrong length, a failed check digit, restricted ranges, or a valid barcode that belongs to a different product or variant.
Can FeedPatch find the affected source rows?
Yes, when the affected-products export and the source file share the same product IDs. The free matcher returns exact source-row numbers and an unmatched-ID list.
Can FeedPatch confirm that a barcode belongs to my product?
No. FeedPatch validates file structure, supported GTIN lengths, and check digits. Manufacturer or GS1 records and Merchant Center remain the authority for product identity.
Should I set identifier_exists to no?
Only when the product genuinely has no assigned unique product identifiers and Google’s rules allow it. Do not use identifier_exists=no to hide a missing or incorrect GTIN for a product that actually has one.
Official references
Use Merchant Center and manufacturer data as the final authority.
Google: Fix Invalid value [gtin]Affected-products download, cross-reference, and re-upload workflow.Google: GTIN [gtin] specificationSupported lengths, check digits, restricted ranges, variants, and identifier requirements.Google: identifier_existsWhen a product genuinely lacks unique product identifiers.
Published by the FeedPatch team, the developer of the tool described here. Checked against Google Merchant Center Help on September 3, 2026. FeedPatch is independent and is not affiliated with Google.