Download the affected-products CSV
In Merchant Center, open Products → Needs attention, filter for the missing GTIN issue, and download the affected-product list. Keep Google’s product ID values unchanged.
Missing value [gtin]
Cross-reference Google’s affected-products CSV with the feed that generated it, then verify the real identifiers at their source before changing product data.
In Merchant Center, open Products → Needs attention, filter for the missing GTIN issue, and download the affected-product list. Keep Google’s product ID values unchanged.
Choose the CSV or TSV that generated the affected products. FeedPatch audits the file locally and records original source-row numbers; it does not upload your catalog.
Add Google’s affected-products CSV to the ID-list slot. The free matcher produces matched and unmatched IDs so you can investigate the exact rows instead of searching the catalog one item at a time.
Check manufacturer packaging or an authoritative manufacturer record for the exact product and variant. Google says submitted GTINs must be allocated by the manufacturer. A store SKU, another variant’s barcode, or an invented number is not a substitute.
If a product genuinely has no assigned unique product identifier, follow Google’s identifier rules for that product. Do not use identifier_exists=no merely to suppress a warning for a product that actually has a GTIN.
Update the original data source, review the affected-row map, and upload the corrected product data once. Then monitor Needs attention; Merchant Center may not reflect the change immediately.
Product boundary
FeedPatch can flag a missing identifier combination and match Google IDs to source rows. It cannot query GS1, inspect packaging, see every Merchant Center data source, or decide whether a product should have a GTIN.
Run the free feed auditOptional repair export
FeedPatch Pro applies safe, reviewable formatting normalizations after you identify the correct source rows. It never invents or substitutes product identifiers.
Frequently asked
Google suspects the product normally has a manufacturer-assigned GTIN, but the submitted product data did not include one. Products with an assigned GTIN but no submitted value can have limited visibility.
No. FeedPatch can locate affected source rows and flag file-level identifier gaps. Manufacturer records, packaging, and Merchant Center remain the authority for the product’s identity.
When the affected-products export and source feed share product IDs, it returns exact source-row numbers, matched and unmatched counts, and a downloadable match map.
No. Each variant that has its own GTIN needs the identifier assigned to that exact variant. Reusing or inventing a GTIN can create a different identifier problem.
Official references
Published by the FeedPatch team, the developer of the tool described here. Checked against Google Merchant Center Help on September 4, 2026. FeedPatch is independent and is not affiliated with Google.