Skip to main content

Merchant Center issue

Fix an incorrect or mismatched GTIN

"Incorrect GTIN", often called a mismatched GTIN, is harder to spot than a format error. The number passes every check, but it belongs to a different product than the one in your listing. This page explains how Google detects that, how to find where the wrong number came from, and how it relates to the separate "Incorrect product identifier" issue.

Diego Nijboer · WISEPIMLast updated:

Short answer

Check the GTIN against the barcode on the packaging or the manufacturer's data, and make sure the image, title and description describe that same product. Correct one product with Edit product, or download the affected list and fix it in bulk. If the product or account was disapproved, request a review once the fix is live.

What this issue means

Google compares your GTIN with what it knows about the product behind that number. When the GTIN is properly formatted but does not correspond to the product you describe, Merchant Center shows Incorrect GTIN. The most common cause is a GTIN from another product that was reused by accident, for example when a listing was copied to create a new variant.

A related issue works the other way around. Incorrect product identifier appears when identifier_exists is set to false or no for a product that Google believes has a GTIN, based on similar offers. The offer stays disapproved until you provide accurate identifiers. If your problem is a GTIN that fails the format check, see Invalid GTIN in unsupported format instead.

DetailValue
Issue in Merchant CenterIncorrect GTIN
Attributegtin [gtin]
EffectGoogle matches the offer to the wrong product, and a disapproved product or account stays that way until the GTIN is corrected.
CheckedAgainst Google Merchant Center Help on 11 October 2026

Common causes

  • A GTIN from another product was reused, often when a listing or variant was duplicated.
  • Variants share one GTIN, while each size or color has its own barcode.
  • Columns shifted during an import, so GTINs landed on the wrong rows.
  • The title, image or description does not match the product the GTIN belongs to.
  • identifier_exists is set to no for a branded product that has a GTIN (shown as Incorrect product identifier).

How to fix it, step by step

  1. In Merchant Center, open Products, go to the Needs attention tab and filter on this issue.
  2. For each product, confirm the gtin matches the manufacturer's number, using the barcode on the packaging or the supplier's data.
  3. Check that the image, title and description are accurate and describe the same product as the GTIN.
  4. For a few products, use Edit product and save. For many, download the affected products as a CSV file, correct the GTINs and upload them with your usual method.
  5. If you see Incorrect product identifier, remove identifier_exists or set it to true or yes, and add the manufacturer's valid GTIN. Google suggests GS1 GEPIR to verify who owns a GTIN.
  6. If the product or account was disapproved, request a review once the fix is live, or appeal. A small edit or an appeal starts a new crawl.
  7. Allow time: review crawls usually finish within 24 to 48 hours after the fixes are live.

Free tool

Check a product against Google Shopping rules

Enter one product's title, description, price, GTIN and image link. The checker lists the errors and warnings Merchant Center's core requirements would raise, before you upload.

Open the full tool
Loading the tool

How to prevent it

  • Only use GTINs from the manufacturer; never create or make up a GTIN.
  • Check the barcode on the packaging when a new product comes in, and validate it against the GS1 GTIN guidelines.
  • Give every variant its own GTIN and clear the GTIN field whenever you duplicate a product.
  • Provide a GTIN for every product that has one, so identifier_exists is never set to no by mistake.

How WISEPIM helps

WISEPIM cannot tell whether a valid GTIN belongs to the right product: it does not look numbers up in the GS1 registry. What it does catch is the most common source of this issue. The general rule packs in Quality Guard flag a GTIN that is used twice in the same project, which is what happens when a listing or variant is copied with its barcode.

WISEPIM stores the EAN, UPC, brand and MPN per variant, and the Merchant Center connection does not send identifier_exists, so it cannot set it to no by mistake. If you publish through Feed Hub, its Google Shopping feed writes no only when GTIN, MPN and brand are all empty.

Sources

Vendor documentation we read for this guide, as of October 2026. Features and names change, so check the current documentation before you decide.

Frequently asked questions

An invalid GTIN fails the format check: wrong length, letters or a bad check digit. An incorrect GTIN is properly formatted but belongs to a different product. A validator catches the first problem, but only checking the packaging or the manufacturer's data catches the second.

No. If Google believes the product has a GTIN, setting identifier_exists to no leads to Incorrect product identifier, and the offer stays disapproved until you provide accurate identifiers.

Google says review crawls usually finish within 24 to 48 hours after your fixes are live. A small edit to the product or an appeal starts a new crawl.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

Catch feed problems before Google does

WISEPIM checks every product against the Google Shopping rules in Quality Guard and sends clean data to Merchant Center or a Feed Hub feed. Free for up to 100 products.

Start free
Check a product

Keep reading

Keep exploring

Hand-picked next steps to go deeper.