Check the source barcode or GTIN shape first: length, check digit, Shopify variant barcode, feed app override, and whether SKU is being reused as a manufacturer identifier.
Google Merchant Center Identifier Error Checker
Upload a Google Merchant Center affected-products CSV, a Shopify or WooCommerce product CSV, or paste a feed URL note. The checker groups invalid GTIN, missing MPN + brand, Shopify barcode, duplicate GTIN, and identifier_exists problems into a product-level fix list.
If affected-products rows, Shopify barcodes, feed app mappings, and Merchant Center diagnostics disagree, route the case to the Feed/GMC owner map before changing hundreds of GTIN, MPN, brand, or identifier_exists values.
Compare the affected-products CSV with Shopify or WooCommerce product rows before setting identifier_exists=false or rewriting Merchant Center rules.
Treat it as a Feed/GMC evidence problem. Use product export, feed mapping, diagnostics screenshots, and public product URLs before bulk edits.
Use this for issue title, affected attribute, severity, destination, offer ID, GTIN, MPN, brand, and identifier_exists rows Google already grouped.
Use this for source catalog evidence: product ID, variant ID, SKU, barcode, vendor or brand, MPN, price, availability, and product URL.
Use this when a generated XML, Content API, feed app, or supplemental feed may be transforming correct source fields before Merchant Center receives them.
One issue group, source CSV is obvious, and Shopify barcode/vendor/MPN fields match Merchant Center rows.
Copy the action list, fix the product or feed field, and wait for the next Merchant Center fetch.Affected-products CSV, product export, feed app mapping, diagnostics timing, or public product URLs disagree.
Prefill the request with checker counts before bulk edits so the repair owner is decided from evidence.Many variants, repeat diagnostics, suspension or Shopping visibility risk, or feed rules can change hundreds of products.
Use the reviewed snapshot as the repair map, then scope implementation only for the confirmed source owner.Private affected-products CSVs can wait for the reply thread. The request carries the current checker counts, issue type, next evidence, and repair-source question into the reviewed snapshot form without asking for every feed file first.
Barcode, vendor/brand, MPN, SKU, product status, and channel inclusion are wrong or blank in the catalog export.
Fix the source field before changing Merchant Center rules.Catalog rows contain identifiers, but the affected-products CSV receives blanks, transformed values, or SKU-as-MPN output.
Inspect app field mapping, supplemental feeds, and last fetch timing.identifier_exists or identifier fields are overwritten after fetch, especially across many unrelated products.
Review the rule before bulk edits that can suppress valid identifiers.The product URL shows a different brand, title, variant fact, or manufacturer claim than the feed row.
Align buyer-visible evidence before requesting a reviewed snapshot.What the checker returns before you upload private CSVs.
The output is a source ownership scorecard: every issue group gets a repair owner, the evidence that proves it, and the point where a reviewed snapshot is worth requesting.
Review only if a feed app or supplemental feed overwrites the Shopify barcode.Request reviewed snapshot when ownership is unclear across product export and feed mapping.Review before changing rules that affect many products.Request reviewed snapshot when ownership is unclear between feed data and public proof.Use this sample after the Shopify-to-GMC feed truth report points to GTIN, MPN, brand, or identifier_exists repair. It loads matching Merchant Center affected rows and Shopify product rows so the checker can group identifier fixes immediately.
Rows from Merchant Center diagnostics or affected item exports.
Rows from Shopify, WooCommerce, feed app, or pasted product CSV.
Add the Merchant Center affected-products CSV or diagnostics screenshot so the checker can match store fields to Google's issue groups.
The checker found affected rows, but review should wait until Merchant Center diagnostics and product catalog evidence can be compared side by side.
Rows with a non-numeric GTIN, unsupported GTIN length, or failed check digit.
1 row(s). Fix source: Fix the source barcode/GTIN field in Shopify variant barcode, product vendor/brand, the Google & YouTube app, or your feed app mapping.Rows where MPN equals SKU or looks like an internal store code.
2 row(s). Fix source: Use the manufacturer part number when one exists. Do not automatically map Shopify SKU to MPN.Use this after the free checker groups the rows. The reviewed snapshot tells you whether the fix should start in Shopify product data, a feed app, Merchant Center rules, or public product evidence.
- One-page GTIN, MPN, brand, and identifier_exists repair map.
- Affected row grouping by likely source: Shopify product data, feed app, Merchant Center rule, or visible product page.
- Priority list for invalid GTIN, missing identifiers, SKU-as-MPN, duplicate barcode, and identifier_exists mismatch.
No listing approval, ranking, policy recovery, or GS1 ownership outcome is guaranteed. The deliverable is a repair map and evidence gap review.
Reserve reviewed snapshot $79Prepare the CSV evidence kit before bulk identifier fixes.
Do not edit GTIN, MPN, brand, or identifier_exists rules from one Merchant Center warning alone. Pair the affected-products export with Shopify product rows, diagnostics timing, feed app mapping, and public product evidence so the checker can point to the likely repair source.
Request review when the same issue appears across many variants or product types.Request review when Shopify has data but Merchant Center receives blank or transformed fields.Request review when product counts, diagnostics, and feed fetch timing do not agree.Request review before changing rules that affect hundreds of products.Request review when feed identifiers conflict with what shoppers can verify on the product page.Decide whether GTIN, MPN, brand, or identifier_exists is actually the repair source.
Product identifier warnings look similar in Merchant Center, but the fix can belong to Shopify product data, a feed app mapping, a Merchant Center feed rule, public product evidence, or a broader Google Feed Truth workflow. Use this map before editing hundreds of rows.
Fix the source barcode or GTIN mapping before overriding Merchant Center rules.Add the manufacturer GTIN where it exists, or provide MPN + brand when no GTIN exists.Set false only when the product truly has no manufacturer-assigned GTIN, MPN, or brand identifier.Choose whether the repair starts in Shopify product data, the feed app, a supplemental feed, or a GMC feed rule.Upload Merchant Center affected-products CSV and Shopify product rows, then group invalid GTIN, missing identifiers, duplicate barcode, and identifier_exists issues.
Start checkerProducts missing in Google?Send store URL for a Feed/GMC owner map when item counts, diagnostics, fetch timing, feed app ownership, or Google channel state may be the real blocker.
Send store URL for Feed/GMC owner mapFix invalid GTIN rowsUse this when Merchant Center flags invalid GTIN values, bad check digits, SKU misuse, or Shopify barcode source problems.
Open GTIN fixFix missing identifier rowsUse this when Google needs a GTIN, MPN + brand, or a defensible identifier_exists=false decision.
Open missing identifiers fixUse this before rewriting feed rules.
Product identifier errors often start in the source catalog: Shopify barcode, WooCommerce GTIN fields, brand mapping, or a feed app override. The checker groups the problem before you touch Merchant Center rules.
Keep the boundary clean.
This validates field shape and likely repair source. It does not confirm GS1 ownership, policy compliance, account status, or final Google approval.
Questions before uploading product identifier data.
No. It is a field-level diagnostic for product identifiers. It does not inspect your Merchant Center account or guarantee approval.
No. The checker validates GTIN length and check digit only. It does not verify official GS1 ownership or brand assignment.
GTIN is the global trade item number family, including UPC and EAN. MPN is the manufacturer part number. SKU is usually an internal store code. Brand identifies the maker or brand owner.
Only when the product truly has no manufacturer-assigned GTIN, MPN, or brand identifier. Do not use false just to suppress Merchant Center errors.
The issue is usually in variant barcode data, the Google & YouTube app, a feed app mapping, or a Merchant Center feed rule that overrides the source value.
Yes. The checker is designed for affected-products CSV exports and product catalog CSVs. The data is processed in the browser.
Start with variant SKU, barcode, vendor or brand, product title, handle, product status, Google channel inclusion, and any feed app GTIN, MPN, brand, or identifier_exists mapping fields.
No. It helps identify where the field problem likely starts. The actual repair still happens in Shopify, WooCommerce, a feed app, or Merchant Center rules.
Yes. Agencies can use it as a first-pass triage before producing a client fix list or ordering a deeper feed identifier audit.