Product Identifiers: GTIN, MPN & Brand for Shopping Feeds

TL;DR — Product identifiersProduct identifiers are the standardized values — GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand — that shopping feeds like Google Merchant Center and Microsoft Merchant Center use to match a product listing to the correct item in their catalog. A GTIN alone is usually enough; without one, brand + MPN is the fallback; products with none declare that with the identifier_exists attribute. are three standard values a shopping feed uses to figure out exactly which product you’re selling: the GTIN (the number in the barcode), the MPN (the manufacturer’s part number), and the brand. If your product has a GTIN, use it — that alone is usually enough. If it doesn’t, submit brand + MPN instead. And if it genuinely has none of them (custom, handmade, vintage), you tell Google that on purpose with an attribute called identifier_exists.

What GTIN, MPN, and brand actually are

When you list products through Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. or Microsoft/Bing’s equivalent, the engine needs to know which specific product each row in your feed is. It does that with three identifiers:

• GTIN — the Global Trade Item Number. This is the number encoded in a product’s barcode. You’ll also hear it called a UPC (the 12-digit version common in North America) or an EAN (the 13-digit version common in Europe) — those are just regional flavors of the same thing. Books use an ISBN, which is also a GTIN.
• MPN — the Manufacturer Part Number. This is the code the manufacturer uses to identify one specific product among everything they make.
• Brand — the brand name the product is sold under.

The one rule that matters most

Here’s the whole thing in one sentence: if your product has a GTIN, submit it — and never, ever make one up.

Google says this over and over across its documentation: “Don’t make up, guess, or include values from similar products. If you provide incorrect identifiers, your product(s) may be disapproved.” (source). The best place to find the right GTIN is right on the box: “The most accurate source of GTINs is always from the product packaging or the product’s manufacturer.” (source).

What if my product doesn’t have a GTIN?

Not every product has one. Store-brand goods, replacement parts, and especially custom or handmade items often don’t. That’s fine — you have two options:

1. Submit brand + MPN instead. Together they identify the product when there’s no GTIN.
2. If it has none of the three (a one-of-a-kind painting, a hand-knitted scarf, a pre-barcode antique), set identifier_exists to false. That’s you honestly telling Google “this product genuinely has no identifiers,” which is completely allowed.

What you must not do is set identifier_exists: false just to skip the work of finding a GTIN on a product that actually has one. Google cross-checks that claim against what it already knows, and it’ll flag the mismatch.

The thing most people get wrong

Missing a GTIN and having a wrong GTIN are treated very differently. If your product simply lacks a GTIN, you’re mostly looking at reduced visibility — your products can rank lower than competitors who do provide correct identifiers. But submitting a GTIN that’s wrong for that product — usually because it was copied from another listing — can get the product disapproved. Missing = weaker; wrong = broken.

Want the deep version — the exact identifier_exists mismatch mechanism, how to verify a GTIN actually belongs to your product, the restricted prefix ranges to avoid, and how Bing differs? Switch to the Advanced tab.

TL;DR — GTIN is the strong identifier; brand + MPN is the legitimate fallback; identifier_exists: false is the honest declaration for products with none. Nearly every warning or disapproval in this space is one of: (a) a valid-format GTIN that’s wrong for the product (reused/borrowed), (b) a missing GTIN on a product that has one, or (c) an identifier_exists: false claim contradicted by Google’s catalog. Google repeats “don’t invent, guess, or reuse a GTIN” across four separate docs — a mathematically valid checksum is necessary but not sufficient, because a real GTIN can belong to someone else’s product. The enforcement history is the missing context: 2019 made missing identifiers a priority penalty rather than an auto-disapproval, 2021 extended enforcement to free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts. and began disapproving duplicate GTINs, and December 2023 changed some identifier_exists handling. Microsoft uses similar fields, but its validation and enforcement should be treated as a separate system.

The core mental model

Three identifiers, one decision tree:

• GTIN present? Submit it. A correct GTIN alone is usually enough to identify the product — that’s a matching claim, not a full compliance one. Brand is still a separately required attribute for most categories even when a GTIN is present. Per Google’s own product data specification, GTIN is “It Depends (strongly recommended if available)” — the softest-sounding of the three requirements, but the one with the most teeth, because a product Google knows has a GTIN gets penalized for omitting it: “Products with an assigned GTIN, but submitted without one, may have limited visibility.” (source).
• No GTIN? Brand + MPN is the fallback. Per Google’s MPN spec, MPN is “Required for all products without a manufacturer-assigned GTIN.” (source).
• None of the three? Declare it. “If your products don’t have assigned unique product identifiersProduct identifiers are the standardized values — GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand — that shopping feeds like Google Merchant Center and Microsoft Merchant Center use to match a product listing to the correct item in their catalog. A GTIN alone is usually enough; without one, brand + MPN is the fallback; products with none declare that with the identifier_exists attribute.: Don’t include the GTIN, brand, or MPN attributes for the product” (source), and set identifier_exists to false.

When each identifier is actually required

The nuance most guides flatten is that these three attributes have genuinely different requirement logic in the product data specification:

• Brand is required for all new products except movies, books, and musical recordings (categories where there’s often no clearly associated brand), and optional otherwise. Google is blunt about accuracy: “Only provide a brand if you’re sure it’s correct. When in doubt don’t provide a brand (for example, do not guess or make up a value).” (source). Note the trap: for homemade or custom goods where you are the manufacturer, brand isn’t optional — you use your own store name as the brand.
• GTIN is strongly recommended whenever the manufacturer assigned one, per the spec’s “It Depends” language.
• MPN is required only when the product has no manufacturer-assigned GTIN, and optional otherwise.

Two attribute mechanics worth knowing because they cause silent errors: each product variant (a different color or size) typically has its own MPN — copying one MPN across a whole variant group is a common oversight — and bundle/multipack brand logic is non-obvious. For a manufacturer-created bundle, use the bundle’s brand; for a bundle you assembled, use the main product’s brand (Google’s example is a camera + lens + bag kit — you’d use the camera’s brand). For compatible or aftermarket parts, use the brand of whoever actually made the compatible part, not the brand it’s compatible with. These are Google’s instructions for what to submit in the feed — the underlying GTIN itself (which number a given variant or bundle actually gets) is allocated separately by GS1’s own numbering system. Don’t infer one from the other.

The GTIN attribute spec also pins down valid formats: lengths of 8, 12, 13, or 14 digits (UPC, EAN, JAN, or ISBN). Spaces and dashes are ignored, and you can submit up to 10 GTINs per product. 8-digit UPC-E should be converted to 12-digit UPC-A, and ISBN-10 to ISBN-13.

The identifier_exists exemption — and its trap

identifier_exists is the honest escape hatch. Google’s spec is explicit: “Use the identifier exists [identifier_exists] attribute to indicate that unique product identifiers (UPIs) aren’t available for your product” (source), and “Use for products that don’t have a GTIN, MPN, or brand” (source). Legitimate cases: custom T-shirts, art, handmade goods, and products made before GTINs existed — vintage items, antiques, books published before 1970.

None of those category labels is a blanket exemption on its own, though. A specific vintage or handmade item can still carry a manufacturer-assigned GTIN — resold original-packaging stock, for instance — so check the actual item, not just which category it falls into, before declaring identifier_exists: false.

Here’s the trap that generates most identifier_exists errors. This attribute isn’t a free on/off toggle — Google cross-validates it against catalog evidence:

“Products for which the identifier exists [identifier_exists] attribute is incorrectly set to no or false and for which there is evidence that a unique product identifier exists, will receive a warning.” (source).

So if you flip identifier_exists to false on a mass-produced branded product just to skip finding its GTIN, and Google’s Shopping GraphThe Shopping Graph is Google's machine-learning-powered, real-time database of the world's products and sellers — the commerce equivalent of the Knowledge Graph. Built from Merchant Center feeds, crawled Product structured data, StoreBot verification, and broad web signals, it powers Shopping results, AI Overviews, AI Mode, and Gemini shopping answers. already knows that product has a GTIN, you get flagged. Values are yes/true or no/false (English only); the Merchant API uses true/false.

How to find or verify the correct GTIN

The order of operations:

1. Check the physical barcode/packaging first. It’s the authoritative source, per Google.
2. Ask the manufacturer if the packaging isn’t at hand.
3. Register with GS1 if you’re the brand owner and your product genuinely has no assigned GTIN — GS1 issues the number (a single GTIN or a company prefix for many). Don’t self-invent one.
4. Verify — two different checks. A GTIN can be mathematically valid and still be the wrong product’s number. The GS1 Check Digit Calculator confirms the checksum math is right. But that only proves the number is well-formed, not that it’s yours. To confirm ownership, use GS1’s official lookup — Verified by GS1 / GEPIR — which tells you which company a GTIN actually belongs to. This is the check that catches a valid-checksum number copied from someone else’s product.

Avoid the restricted and coupon prefix ranges. Merchants generating placeholder GTINs often stumble into ranges Google explicitly disallows: prefixes 02, 04, and 2 are restricted ranges, and 05, 98, 99 are coupon ranges that are never valid product GTINs. If a “GTIN” starts with one of those, it’s not a real product identifier.

Common mismatches that trigger warnings and disapprovals

These are current, specific Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. issues — check the exact issue name in your account. (The enforcement history behind why some of these are warnings rather than disapprovals today is its own section, below.) Almost every problem here is one of five failure modes:

• Reused / borrowed GTIN — a valid-checksum number that belongs to a different product, usually copy-pasted or auto-generated. This is the Incorrect GTIN error: the value is valid but incorrect for this product, commonly because a GTIN from another product was accidentally re-used. The fix is to use only the manufacturer-provided GTIN and never create new ones. This is the number-one concrete disapproval trigger for established sellers with real catalogs — and the reason a check-digit calculator isn’t enough; you need the ownership check.
• Missing GTIN on a product that has one — see Missing or incorrect GTIN. The fix is to give the product either an accurate GTIN, or both an MPN and a brand; if it’s genuinely one-of-a-kind or vintage, use identifier_exists: false instead.
• identifier_exists: false contradicted by catalog evidence — the inverse mismatch, documented as Incorrect product identifier: you submitted false for a product Google believes has a GTIN. The fix is to add the correct GTIN and set identifier_exists back to true.
• Duplicate GTINs across your own catalog — since 2021, different products sharing one GTIN with the same variant attributes are treated as ambiguous and can be disapproved (more on this below).
• Submitting an internal SKU as the GTIN — SKUs are merchant-internal and meaningless outside your own system. They aren’t globally unique and aren’t GTINs.

Google also runs an interactive troubleshooter for GTIN/UPI issues that walks you through the specific disapproval you’re seeing.

A short history of enforcement — why the advice you find online conflicts

If you’ve read older blog posts that say “no GTIN = instant disapproval,” they’re describing a regime that no longer exists. The rules have shifted materially three times, and the direction is consistent: harder catalog-truth requirements, softer individual penalties.

• September 2019 — Google moved from automatically disapproving identifier-less products to a priority-based system: products missing UPIs stay eligible but rank below competitors with correct identifiers, especially in competitive categories (Search Engine Land).
• September 2021 — Google extended UPI enforcement to free (organic) product listings, not just paid Shopping ads, and introduced duplicate-GTIN disapprovals: different products sharing a GTIN with matching variant attributes are treated as ambiguous, and among a group flagged as duplicates only one stays active (Search Engine Land).
• December 2023 — Google softened the penalty: identifier_exists mismatches no longer trigger an outright disapproval — they surface as a warning first. As Barry Schwartz reported it: “After this change the offers with the Item issue Incorrect value: identifier exists [identifier_exists] will receive a warning instead of a disapproval. If product identifier requirements are not met, then your item’s performance may be limited.” (Search Engine Roundtable).

The net: the bar for correctness went up (no shared GTINs, no false exemption claims), but the cliff-edge penalty for a single mistake went down (warning and reduced performance rather than instant ineligibility). Worth stating plainly so you don’t act on outdated instant-disapproval advice.

For the broader “why not invent a GTIN” framing, Google’s Search Central blog post Providing better product information for shoppers is the single best official explainer — it tells manufacturers not to reuse identifiers across products, and tells retailers to provide a GTIN when one exists and to rely on brand and manufacturer part numbers when it doesn’t.

Bing / Microsoft Merchant Center: same model, one difference

Bing inherits Google’s attribute vocabulary by design, so the model is functionally identical — GTIN preferred, brand + MPN fallback, an identifier-exists flag for genuine exemptions. The Microsoft Shopping Content API docs spell it out: brand, gtin, and mpn are “required if the manufacturer assigned values” and “You must specify the values if known” (source).

The one difference is where enforcement bites. Microsoft’s identifierExists field defaults to true, and the requirement is mechanical: “If you do not specify any of them, you must set the identifierExists field to false. The default is true.” (source). And Bing has the same “we know this product has identifiers” cross-check as Google: “If the product is known to have these identifiers and you do not specify them, MMC accepts the product for now but the Product object in the response includes the warnings field. You should always check if the warnings field exists and fix all identified issues.” (source). So the practical takeaway: Bing enforces the same truth, but more mechanically at the API insert level, versus Google’s graduated warning system.

Quick reference: what to submit

This article is a deep dive on the identifiers themselves; for how they fit into the wider feed — titles, images, feed rules, diagnostics — see Merchant Center feed optimizationGoogle Merchant Center feed optimization is the process of improving the quality, accuracy, and completeness of the product data you submit to Google Merchant Center — titles, identifiers, images, and attributes — so your products show up more often and in more relevant places across Shopping ads, free listings, and AI shopping surfaces., and for the platform overview, the Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. hub.

AI summary

A condensed take on the Advanced version:

• Three identifiers: GTIN (barcode number — UPC/EAN/JAN/ISBN/ITF-14), MPN (manufacturer part number), brand. A correct GTIN alone usually identifies a product — but brand is still a separately required attribute for most categories.
• Requirement logic differs per attribute: GTIN is “strongly recommended if available”; MPN is required only when there’s no manufacturer GTIN; brand is required except for movies/books/music, and required (as your store name) for homemade goods.
• No GTIN? Fallback is brand + MPN. None of the three? Set identifier_exists: false.
• The one rule: never invent, guess, borrow, or reuse a GTIN — Google repeats this across four separate docs. A valid checksum ≠ a correct GTIN; the number can belong to a different product.
• Verify twice: GS1 Check Digit Calculator (format) and Verified by GS1 / GEPIR (ownership). Avoid restricted/coupon prefixes 02, 04, 2, 05, 98, 99.
• Five failure modes: reused/borrowed GTIN, missing GTIN on a product that has one, identifier_exists: false contradicted by catalog evidence, duplicate GTINs across your own catalog, and submitting an internal SKU as a GTIN.
• Enforcement history: 2019 = missing UPIs became a priority/visibility penalty, not auto-disapproval; 2021 = extended to free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts. + duplicate-GTIN disapprovals; Dec 2023 = identifier_exists mismatches downgraded from disapproval to warning. Bar for correctness up, penalty for one mistake down.
• Bing: same model (identifierExists defaults to true), enforced more mechanically at the API insert level.

Official documentation

Primary-source documentation from Google and Microsoft.

Google — attribute specs

• About unique product identifiers — the canonical policy page: when GTIN/MPN/brand are required, and the “don’t make up, guess, or reuse” rule.
• GTIN [gtin] — valid lengths and formats (UPC/EAN/JAN/ISBN/ITF-14), spaces/dashes, up to 10 GTINs per product.
• MPN [mpn] — required for products without a manufacturer-assigned GTIN; per-variant MPNs.
• Brand [brand] — brand requirements, bundle/multipack logic, compatible-product rules.
• Identifier exists [identifier_exists] — the exemption attribute and the catalog-evidence cross-check.
• Product data specification — the full attribute requirement matrix.
• Find a GTIN — Google’s definition and how to locate a GTIN.

Google — troubleshooting

• How to fix: Incorrect GTIN — the reused/wrong-product GTIN error.
• How to fix: Missing or incorrect GTIN — missing or unrecognized UPI values.
• How to fix: Incorrect product identifier — the inverse identifier_exists: false mismatch.
• Fix issues with a GTIN or unique product identifier (troubleshooter) — interactive fix-it flow.
• Providing better product information for shoppers (Search Central blog, Feb 2021) — the “why you must not invent or reuse a GTIN” explainer.

Microsoft / Bing

• Managing your Products — Microsoft Advertising Content API — brand/gtin/mpn requirements and the identifierExists default-true rule.
• Unique identifiers for your product ads — Microsoft Advertising Help — the human-readable version of the above.

GTIN verification (GS1)

• GS1 Check Digit Calculator — confirms a GTIN’s checksum is well-formed.
• Verified by GS1 — ownership/validity lookup: which company a GTIN actually belongs to.

Quotes from the source

On-the-record statements from Google and Microsoft. Each link is a deep link that jumps to the quoted passage on the source page.

Google — the core rules

• “Products with an assigned GTIN, but submitted without one, may have limited visibility.” — Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. Help, About unique product identifiersProduct identifiers are the standardized values — GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand — that shopping feeds like Google Merchant Center and Microsoft Merchant Center use to match a product listing to the correct item in their catalog. A GTIN alone is usually enough; without one, brand + MPN is the fallback; products with none declare that with the identifier_exists attribute.. Jump to quote
• “Don’t make up, guess, or include values from similar products.” — Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. Help, About unique product identifiers. Jump to quote
• “The most accurate source of GTINs is always from the product packaging or the product’s manufacturer.” — Google Merchant Center Help, About unique product identifiers. Jump to quote
• “If your products don’t have assigned unique product identifiers: Don’t include the GTIN, brand, or MPN attributes for the product.” — Google Merchant Center Help, About unique product identifiers. Jump to quote

Google — the attribute specs

• “Required for all products without a manufacturer-assigned GTIN.” — Google Merchant Center Help, MPN [mpn]. Jump to quote
• “Only provide a brand if you’re sure it’s correct.” — Google Merchant Center Help, Brand [brand]. Jump to quote
• “Use the identifier exists [identifier_exists] attribute to indicate that unique product identifiers (UPIs) aren’t available for your product.” — Google Merchant Center Help, Identifier exists. Jump to quote
• “Products for which the identifier exists [identifier_exists] attribute is incorrectly set to no or false and for which there is evidence that a unique product identifier exists, will receive a warning.” — Google Merchant Center Help, Identifier exists. Jump to quote

Microsoft / Bing

• “The following fields are also required if the manufacturer assigned values… You must specify the values if known.” (brand, gtin, mpn) — Microsoft Advertising, Managing your Products. Jump to quote
• “If you do not specify any of them, you must set the identifierExists field to false. The default is true.” — Microsoft Advertising, Managing your Products. Jump to quote
• “If the product is known to have these identifiers and you do not specify them, MMC accepts the product for now but the Product object in the response includes the warnings field.” — Microsoft Advertising, Managing your Products. Jump to quote

Industry coverage — the Dec 2023 policy change

• “After this change the offers with the Item issue Incorrect value: identifier exists [identifier_exists] will receive a warning instead of a disapproval. If product identifier requirements are not met, then your item’s performance may be limited.” — Barry Schwartz, Search Engine Roundtable, reporting Google’s December 2023 change. Jump to quote

Which identifiers should I submit for this product?

Work through it product-by-product. The whole thing hinges on one question: does a manufacturer-assigned GTIN actually exist for this item?

Mistakes that get products flagged

Concrete errors from the field, why they’re wrong, and what to do instead.

Making up, guessing, or borrowing a GTIN. Why it’s wrong: Google explicitly forbids it, and a GTIN copied from a similar product is valid-format but wrong-product — the exact mechanism behind the Incorrect GTIN disapproval. Do instead: pull the GTIN from the packaging or the manufacturer, and verify ownership before submitting.

Treating a valid check digit as proof the GTIN is correct. Why it’s wrong: the GS1 Check Digit Calculator only confirms the number is well-formed. A real, checksum-valid GTIN belonging to someone else’s product will pass the math and still be wrong for you. Do instead: add an ownership check (Verified by GS1 / GEPIR), not just a format check.

Flipping identifier_exists to false to skip finding a GTIN. Why it’s wrong: Google cross-validates the claim against its catalog — “Products for which the identifier exists attribute is incorrectly set to no or false and for which there is evidence that a unique product identifier exists, will receive a warning” (source). It’s a warning since December 2023, not an instant disapproval — but performance is still limited. Do instead: only set it to false for products that genuinely have no GTIN, MPN, or brand; otherwise find and submit the real identifiers.

Submitting your internal SKU as the GTIN. Why it’s wrong: SKUs are merchant-internal and not globally unique — they’re meaningless to Google’s catalog and aren’t GTINs. Do instead: submit the real GTIN, or brand + MPN if there’s no GTIN; keep your SKU in the id attribute where it belongs.

Copying one MPN across a whole variant group. Why it’s wrong: each product variant (color/size) typically has its own MPN; a shared MPN can cause the variants to be treated as the same product. Do instead: give each variant its own manufacturer-assigned MPN.

Assuming brand is optional/cosmetic. Why it’s wrong: brand is required for any product with a clearly associated brand or manufacturer — and required (as your store name) even for homemade/custom goods. It’s only truly optional for brand-less categories like movies, books, and music. Do instead: always supply an accurate brand unless the product is genuinely brand-less.

Trusting old blog posts that say “no GTIN = instant disapproval.” Why it’s wrong: that was closer to true before the September 2019 shift to a priority-based system. Today, missing identifiers reduce visibility; incorrect identifiers are what risk disapproval. Do instead: treat missing and wrong as different problems — missing weakens visibility, wrong can break the listing.

Product identifiers — cheat sheet

Requirement at a glance

GTIN formats (valid lengths: 8, 12, 13, 14 digits)

• UPC / GTIN-12 — 12 digits (North America); convert 8-digit UPC-E to UPC-A.
• EAN / GTIN-13 — 13 digits (Europe and elsewhere).
• JAN / GTIN-13 — 8 or 13 digits (Japan).
• ISBN — books, 13 digits; convert ISBN-10 to ISBN-13.
• ITF-14 / GTIN-14 — 14 digits (multipacks).
• Spaces and dashes are ignored; up to 10 GTINs per product.

Prefixes that are NEVER valid product GTINs

• Restricted ranges: 02, 04, 2.
• Coupon ranges: 05, 98, 99.

The five mismatches that trigger warnings/disapprovals

1. Reused/borrowed GTIN (valid checksum, wrong product) → disapproval risk.
2. Missing GTIN on a product that has one → limited visibility.
3. identifier_exists: false contradicted by catalog evidence → warning.
4. Duplicate GTINs across your own catalog → ambiguous, one survives.
5. Internal SKU submitted as a GTIN → invalid.

Verify in two steps

• Format → GS1 Check Digit Calculator.
• Ownership → Verified by GS1 / GEPIR.

Enforcement timeline

• 2019 → missing UPIs = priority/visibility penalty (not auto-disapproval).
• 2021 → extended to free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts. + duplicate-GTIN disapprovals.
• Dec 2023 → identifier_exists mismatches = warning, not disapproval.

Bing → same model; identifierExists defaults to true; enforced mechanically at the API insert level.

“Incorrect GTIN” even though the number passes a checksum

Symptom: Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. rejects a GTIN that has a valid length and check digit. Likely cause: The number is well-formed but belongs to another product or company. Fix: Compare it with the physical packaging or manufacturer record, then confirm ownership through Verified by GS1. Replace borrowed or generated values; confirm the issue clears after reprocessing.

Missing-GTIN warning on a product that has a barcode

Symptom: A mass-produced product remains eligible with limited visibility or reports a missing identifier. Likely cause: The assigned manufacturer GTIN was omitted, mapped to the wrong variant, or placed in an internal-SKU field. Fix: Submit the exact product/variant GTIN from packaging or the manufacturer. Keep the merchant SKU in id, not gtin, and confirm the processed item shows the identifier.

identifier_exists warning

Symptom: The feed says identifier_exists: false, but the platform reports that an identifier appears to exist. Likely cause: The exemption was used for a branded catalog product that has a GTIN or brand-plus-MPN. Fix: Find and submit the assigned identifier, then restore identifier_exists to true. Use false only when the product genuinely has no GTIN, MPN, or applicable brand.

Duplicate-GTIN disapproval across separate products

Symptom: Different catalog items are grouped or disapproved because they share one GTIN. Likely cause: A parent, sibling variant, placeholder, or copied value was mapped across multiple distinct products. Fix: Reconcile each item and variant against manufacturer records. Remove the bad value until the correct one is verified, then confirm distinct products no longer share the GTIN.

SKU rejected as a product identifier

Symptom: A value that works inside the commerce platform fails GTIN checks. Likely cause: An internal SKU was submitted as a globally standardized identifier. Fix: Keep the SKU as the feed id; submit the real GTIN, or brand plus manufacturer MPN when no GTIN was assigned. If the product genuinely has no identifiers, use the documented exemption instead of relabeling the SKU.

GTIN ownership check

Test to run: Compare the proposed GTIN with the exact product packaging or manufacturer record, then look it up in Verified by GS1; use the check-digit calculator only as a separate format check. Expected result: The number is valid and the ownership/product evidence agrees with the item being submitted. Failure interpretation: The GTIN may be borrowed, generated, or mapped to the wrong variant. Monitoring window: Before the identifier is added or changed. Rollback trigger: Do not submit any GTIN whose ownership or exact-product relationship cannot be verified.

Identifier-field consistency test

Test to run: Validate a cohort representing manufacturer-GTIN products, brand-plus-MPN products, and genuinely identifier-less products. Expected result: GTIN products submit the real GTIN; no-GTIN branded products submit brand plus MPN; genuine exemptions omit unavailable identifiers and set identifier_exists to false. Failure interpretation: The feed mapping applies one identifier rule to unlike product types. Monitoring window: Before upload and after any catalog-mapping change. Rollback trigger: Stop the mapping rollout if it guesses values, labels SKUs as GTINs, or applies the exemption to known branded products.

Duplicate-identifier check

Test to run: Group the final feed by normalized GTIN and review every value assigned to more than one item, including variants. Expected result: Repeated GTINs represent the same legitimate product relationship; distinct products and distinct assigned variants do not share a copied identifier. Failure interpretation: A parent-level field or placeholder has propagated across multiple offers. Monitoring window: Immediately before each full feed publish. Rollback trigger: Hold affected offers when a shared GTIN cannot be justified from manufacturer data.

Test yourself: Product Identifiers

Five quick questions on GTIN, MPN, brand, and the identifier_exists exemption. Pick an answer for each, then check.

Resources worth your time

Related on this site

• Google Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads. — the hub: free product listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts., Product schemaProduct schema (schema.org/Product) is structured data that tells search engines a page's product name, price, availability, and reviews so it can appear in Shopping-style rich results. It's separate from a Google Merchant Center feed, though Google reconciles the two. vs. feeds, the srsltid parameter.
• Merchant Center feed optimizationGoogle Merchant Center feed optimization is the process of improving the quality, accuracy, and completeness of the product data you submit to Google Merchant Center — titles, identifiers, images, and attributes — so your products show up more often and in more relevant places across Shopping ads, free listings, and AI shopping surfaces. — where identifiers fit alongside titles, images, feed rules, and diagnostics.

From around the industry

• Google Merchant Center Identifier Exists Will No Longer Lead To Disapprovals — Barry Schwartz, Search Engine Roundtable (Dec 2023): the warning-not-disapproval change, with Google’s wording.
• Google to enforce unique product identifiers on free merchant listings — Search Engine Land (2021): the extension of UPI enforcement to free listingsFree product listings (originally launched as \"Surfaces across Google\" in 2020) are unpaid, organic product placements Google generates from your Merchant Center feed or on-page Product structured data. There's no bid and no CPC — Google matches your product data to a query and decides whether and where to show it — across the Shopping tab, Google Search (Popular Products grids), Images, Lens, Maps/Business Profile, YouTube, and Gemini; AI Mode and AI Overviews aren't on Google's official surfaces list, though practitioner reporting links them to the same eligibility pool. They're enabled by default in most cases for new Merchant Center accounts. and duplicate-GTIN disapprovals.
• What you need to know about Google Merchant Center identifier enforcement updates — Search Engine Land (2019): the shift from auto-disapproval to a priority-based system.
• Unique product identifiers: How to Use Brand, MPN, and GTINs — DataFeedWatch: a practical walkthrough of all three attributes.
• Finding GTINs For Your Products — DataFeedWatch: where to look when you don’t have a GTIN on hand.
• What Is a GTIN and Why Do You Need One? — Store Growers: a beginner-friendly GTIN primer.

Product Identifiers

Product identifiers are the standardized values — GTIN (Global Trade Item Number), MPN (Manufacturer Part Number), and brand — that shopping feeds like Google Merchant Center and Microsoft Merchant Center use to match a product listing to the correct item in their catalog. A GTIN alone is usually enough; without one, brand + MPN is the fallback; products with none declare that with the identifier_exists attribute.

Related: Google Merchant Center, Google Merchant Center Feed Optimization, Ecommerce SEO

Product Identifiers

Product identifiers are the standardized values a shopping feed uses to uniquely match your listing to the correct product in a search engine’s catalog — Google calls its catalog the Shopping GraphThe Shopping Graph is Google's machine-learning-powered, real-time database of the world's products and sellers — the commerce equivalent of the Knowledge Graph. Built from Merchant Center feeds, crawled Product structured data, StoreBot verification, and broad web signals, it powers Shopping results, AI Overviews, AI Mode, and Gemini shopping answers.. There are three: the GTIN (Global Trade Item Number — the number encoded in a product’s barcode, submitted as UPC, EAN, JAN, ISBN, or ITF-14), the MPN (Manufacturer Part Number), and the brand.

The rule of thumb is simple: a correct GTIN alone is usually sufficient to identify a product. When a product has no manufacturer-assigned GTIN, the combination of brand + MPN serves as the fallback. And products that genuinely have none of these — custom, handmade, or vintage/pre-barcode goods — declare that fact with the identifier_exists attribute (Google) or identifierExists (Microsoft) set to false. Anything else — a guessed GTIN, a reused number, or a false “no identifier” claim on a product that has one — risks a warning or disapproval in Merchant CenterGoogle Merchant Center (GMC) is a free platform where retailers upload and manage product data so their products can appear across Google — Shopping, organic Search product grids, Images, Lens, and AI surfaces. Since 2020 it powers free (organic) product listings, not just paid Shopping ads..

Related: Google Merchant Center, Google Merchant Center Feed Optimization, Ecommerce SEO

Changelog