Product Identifiers: GTIN, MPN & Brand pour Shopping Feeds

TL;DR — Product identifiers are three standard valeurs a shopping feed uses to figure out exactly qui product you’re selling: the GTIN (the number in the barcode), the MPN (the manufacturer’s partie number), and the brand. Si votre product has a GTIN, utiliser it — que alone is usually suffisant. Si it doesn’t, submit brand + MPN à la place. And si it genuinely has none of les (custom, handmade, vintage), vous tell Google que on objectif with an attribute appelé identifier_exists.

Ce que GTIN, MPN, and brand en réalité are

Quand vous liste products via Google Merchant Center or Microsoft/Bing’s equivalent, the engine nécessite to know qui spécifique product chaque row in votre feed is. It fait que with three identifiers:

• GTIN — the Global Trade Item Number. Ce is the number encoded in a product’s barcode. You’ll aussi hear it appelé a UPC (the 12-digit version courant in North America) or an EAN (the 13-digit version courant in Europe) — ceux are simplement regional flavors of the même chose. Books utiliser an ISBN, qui is aussi a GTIN.
• MPN — the Manufacturer Partie Number. Ce is le code the manufacturer uses to identifier un spécifique product among everything ils faire.
• Brand — the brand nom the product is sold sous.

The un rule que matters la plupart

Here’s the whole chose in un sentence: si votre product has a GTIN, submit it — and jamais, ever faire un up.

Google dit ce over and over à travers its documentation: “Don’t faire up, guess, or inclure valeurs from similaire products. Si vous provide incorrect identifiers, votre product(s) may be disapproved.” (source). The meilleur placer to trouver the correct GTIN is correct on the box: “The la plupart accurate source of GTINs is toujours from the product packaging or the product’s manufacturer.” (source).

Ce que si my product doesn’t have a GTIN?

Pas every product has un. Store-brand goods, replacement parts, and surtout custom or handmade items souvent don’t. That’s fine — vous have two options:

1. Submit brand + MPN à la place. Ensemble ils identifier the product quand there’s aucun GTIN.
2. Si it has none of the three (a one-of-a-kind painting, a hand-knitted scarf, a pre-barcode antique), définir identifier_exists to false. That’s vous honestly telling Google “this product genuinely has no identifiers,” qui is complètement allowed.

Ce que vous doit pas do is définir identifier_exists: false simplement to skip the fonctionner of finding a GTIN on a product que en réalité has un. Google cross-checks que claim contre ce que it déjà knows, and it’ll flag the mismatch.

The chose la plupart personnes obtenir incorrect

Manquant a GTIN and having a incorrect GTIN are treated very differently. Si votre product simply lacks a GTIN, you’re mostly looking at reduced visibility — votre products peut rank lower que competitors who do provide correct identifiers. But submitting a GTIN that’s incorrect pour que product — usually parce que it was copied from un autre listing — peut obtenir the product disapproved. Manquant = weaker; incorrect = broken.

Vouloir the deep version — the exact identifier_exists mismatch mechanism, how to vérifier a GTIN en réalité belongs to votre product, the restricted prefix ranges to éviter, and how Bing differs? Switch to the Avancé tab.

TL;DR — GTIN is the strong identifier; brand + MPN is the legitimate fallback; identifier_exists: false is the honest declaration pour products with none. Nearly every warning or disapproval in ce space is un of: (a) a valid-format GTIN that’s incorrect pour the product (reused/borrowed), (b) a manquant GTIN on a product que has un, or (c) an identifier_exists: false claim contradicted by Google’s catalog. Google repeats “don’t invent, guess, or reuse a GTIN” à travers four separate docs — a mathematically valid checksum is necessary but pas sufficient, parce que a réel GTIN peut belong to someone else’s product. The enforcement history is the manquant context: 2019 made manquant identifiers a priority penalty plutôt que an auto-disapproval, 2021 extended enforcement to free listings and began disapproving duplicate GTINs, and December 2023 modifié some identifier_exists handling. Microsoft uses similaire fields, but its validation and enforcement devrait be treated as a separate system.

The core mental model

Three identifiers, un decision tree:

• GTIN présent? Submit it. A correct GTIN alone is usually suffisant to identifier the product — that’s a matching claim, pas a complet compliance un. Brand is encore a separately requis attribute pour la plupart categories même quand a GTIN is présent. Per Google’s propre product données specification, GTIN is “It Depends (strongly recommended if available)” — the softest-sounding of the three requirements, but the un with the la plupart teeth, parce que a product Google knows has a GTIN obtient penalized pour omitting it: “Products with an assigned GTIN, but submitted sans un, may have limited visibility.” (source).
• Aucun 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. “Si votre products don’t have assigned unique product identifiers: Don’t inclure the GTIN, brand, or MPN attributes pour the product” (source), and définir identifier_exists to false.

Quand chaque identifier is en réalité requis

The nuance la plupart guides flatten is que ces three attributes have genuinely différent requirement logic in the product données specification:

• Brand is requis pour tout nouveau products except movies, books, and musical recordings (categories où there’s souvent aucun clearly associated brand), and optional sinon. Google is blunt à propos de accuracy: “Seulement provide a brand si you’re certain it’s correct. Quand in doubt don’t provide a brand (Par exemple, ne faites pas guess or faire up a valeur).” (source). Remarque the trap: pour homemade or custom goods où vous are the manufacturer, brand isn’t optional — vous utiliser votre propre store nom as the brand.
• GTIN is strongly recommended whenever the manufacturer assigned un, per the spec’s “It Depends” language.
• MPN is requis seulement quand the product has aucun manufacturer-assigned GTIN, and optional sinon.

Two attribute mechanics worth knowing parce que ils causer silent errors: chaque product variant (a différent color or size) typically has its propre MPN — copying un MPN à travers a whole variant groupe is a courant oversight — and bundle/multipack brand logic is non-obvious. Pour a manufacturer-created bundle, utiliser the bundle’s brand; pour a bundle vous assembled, utiliser the principal product’s brand (Google’s exemple is a camera + lens + bag kit — you’d utiliser the camera’s brand). Pour compatible or aftermarket parts, utiliser the brand of whoever en réalité made the compatible partie, pas the brand it’s compatible with. Ces are Google’s instructions pour ce que to submit in the feed — the underlying GTIN itself (qui number a donné variant or bundle en réalité obtient) is allocated separately by GS1’s propre numbering system. Don’t infer un from the autre.

The GTIN attribute spec aussi pins bas valid formats: lengths of 8, 12, 13, or 14 digits (UPC, EAN, JAN, or ISBN). Spaces and dashes are ignored, and vous pouvez submit up to 10 GTINs per product. 8-digit UPC-E devrait 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: “Utiliser the identifier exists [identifier_exists] attribute to indicate que unique product identifiers (UPIs) aren’t disponible pour votre product” (source), and “Use for products that don’t have a GTIN, MPN, or brand” (source). Legitimate cas: custom T-shirts, art, handmade goods, and products made avant GTINs existed — vintage items, antiques, books publié avant 1970.

None of ceux category étiquettes is a blanket exemption on its propre, though. A spécifique vintage or handmade item peut encore carry a manufacturer-assigned GTIN — resold original-packaging stock, pour instance — so vérifier the réel item, pas simplement qui category it falls into, avant declaring identifier_exists: false.

Here’s the trap que generates la plupart identifier_exists errors. Ce attribute isn’t a free on/off toggle — Google cross-validates it contre catalog evidence:

“Products pour qui the identifier exists [identifier_exists] attribute is incorrectly définir to no or false and pour qui là is evidence que a unique product identifier exists, va recevoir a warning.” (source).

So si vous flip identifier_exists to false on a mass-produced branded product simplement to skip finding its GTIN, and Google’s Shopping Graph déjà knows que product has a GTIN, vous obtenir flagged. Valeurs are yes/true or no/false (English seulement); the Merchant API uses true/false.

How to trouver or vérifier the correct GTIN

The order of operations:

1. Vérifier the physical barcode/packaging premier. It’s the authoritative source, per Google.
2. Demander the manufacturer si the packaging isn’t at hand.
3. Register with GS1 si you’re the brand owner and votre product genuinely has aucun assigned GTIN — GS1 problèmes the number (a unique GTIN or a company prefix pour nombreux). Don’t self-invent un.
4. Vérifier — two différent checks. A GTIN peut be mathematically valid and encore be the incorrect product’s number. The GS1 Vérifier Digit Calculator confirms the checksum math is correct. But que seulement proves the number is well-formed, pas que it’s yours. To confirmer ownership, utiliser GS1’s official lookup — Verified by GS1 / GEPIR — qui indique vous qui company a GTIN en réalité belongs to. Ce is the vérifier que catches a valid-checksum number copied from someone else’s product.

Éviter the restricted and coupon prefix ranges. Merchants generating placeholder GTINs souvent stumble into ranges Google explicitly disallows: prefixes 02, 04, and 2 are restricted ranges, and 05, 98, 99 are coupon ranges que are jamais valid product GTINs. Si a “GTIN” starts with un of ceux, it’s pas a réel product identifier.

Courant mismatches que trigger warnings and disapprovals

Ces are current, spécifique Merchant Center problèmes — vérifier the exact problème nom in votre account. (The enforcement history behind pourquoi some of ces are warnings plutôt que disapprovals today is its propre section, ci-dessous.) Almost every problem ici is un of five échec modes:

• Reused / borrowed GTIN — a valid-checksum number que belongs to a différent product, usually copy-pasted or auto-generated. Ce is the Incorrect GTIN error: the valeur is valid but incorrect pour ce product, commonly parce que a GTIN from un autre product was accidentally re-used. The fix is to utiliser seulement the manufacturer-provided GTIN and jamais créer nouveau ones. Ce is the number-one concrete disapproval trigger pour established sellers with réel catalogs — and the raison a check-digit calculator isn’t suffisant; vous besoin the ownership vérifier.
• Manquant GTIN on a product que has un — voir Manquant or incorrect GTIN. The fix is to give the product soit an accurate GTIN, or les deux an MPN and a brand; si it’s genuinely one-of-a-kind or vintage, utiliser identifier_exists: false à la place.
• identifier_exists: false contradicted by catalog evidence — the inverse mismatch, documented as Incorrect product identifier: vous submitted false pour a product Google believes has a GTIN. The fix is to ajouter the correct GTIN and définir identifier_exists back to true.
• Duplicate GTINs à travers votre propre catalog — since 2021, différent products sharing un GTIN with the même variant attributes are treated as ambiguous and peut be disapproved (plus on ce ci-dessous).
• Submitting an internal SKU as the GTIN — SKUs are merchant-internal and meaningless outside votre propre system. Ils aren’t globally unique and aren’t GTINs.

Google aussi runs an interactive troubleshooter pour GTIN/UPI problèmes que walks vous via the spécifique disapproval you’re seeing.

A short history of enforcement — pourquoi the advice vous trouver online conflicts

Si you’ve lire older blog posts que dire “no GTIN = instant disapproval,” they’re describing a regime que ne … plus exists. The rules have shifted materially three times, and the direction is consistent: harder catalog-truth requirements, softer individual penalties.

• September 2019 — Google déplacé from automatically disapproving identifier-less products to a priority-based system: products manquant UPIs stay eligible but rank ci-dessous competitors with correct identifiers, surtout in competitive categories (Moteur de recherche Land).
• September 2021 — Google extended UPI enforcement to free (organic) product listings, pas simplement paid Shopping ads, and introduced duplicate-GTIN disapprovals: différent products sharing a GTIN with matching variant attributes are treated as ambiguous, and among a groupe flagged as duplicates seulement un stays active (Moteur de recherche Land).
• December 2023 — Google softened the penalty: identifier_exists mismatches ne … plus trigger an outright disapproval — ils surface as a warning premier. As Barry Schwartz reported it: “Après ce modifier the offers with the Item problème Incorrect valeur: identifier exists [identifier_exists] va recevoir a warning à la place of a disapproval. Si product identifier requirements ne sont pas met, alors votre item’s performances may be limited.” (Moteur de recherche Roundtable).

The net: the bar pour correctness went up (aucun shared GTINs, aucun faux exemption claims), but the cliff-edge penalty pour a unique mistake went bas (warning and reduced performances plutôt que instant ineligibility). Worth stating plainly so vous don’t act on outdated instant-disapproval advice.

Pour the broader “why not invent a GTIN” framing, Google’s Search Central blog post Providing meilleur product information pour shoppers is the unique meilleur official explainer — it indique manufacturers pas to reuse identifiers à travers products, and indique retailers to provide a GTIN quand un exists and to rely on brand and manufacturer partie numbers quand it doesn’t.

Bing / Microsoft Merchant Center: même model, un difference

Bing inherits Google’s attribute vocabulary by design, so the model is functionally identical — GTIN preferred, brand + MPN fallback, an identifier-exists flag pour 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 un difference is où enforcement bites. Microsoft’s identifierExists field defaults to true, and the requirement is mechanical: “Si vous ne faites pas specify quelconque of les, vous doit définir the identifierExists field to faux. The par défaut is vrai.” (source). And Bing has the même “we know this product has identifiers” cross-check as Google: “Si the product is connu to have ces identifiers and vous ne faites pas specify les, MMC accepts the product pour now but the Product object in la réponse inclut the warnings field. Vous devez toujours vérifier si the warnings field exists and fix tout identified problèmes.” (source). So the practical takeaway: Bing enforces the même truth, but plus mechanically at the API insert level, versus Google’s graduated warning system.

Référence rapide: ce que to submit

Ce article is a deep dive on the identifiers themselves; pour how ils fit into the wider feed — titles, images, feed rules, diagnostics — voir Merchant Center feed optimization, and pour the platform overview, the Google Merchant Center hub.

AI summary

A condensed prendre on the Avancé version:

• Three identifiers: GTIN (barcode number — UPC/EAN/JAN/ISBN/ITF-14), MPN (manufacturer partie number), brand. A correct GTIN alone usually identifies a product — but brand is encore a separately requis attribute pour la plupart categories.
• Requirement logic differs per attribute: GTIN is “strongly recommended si disponible”; MPN is requis seulement quand there’s aucun manufacturer GTIN; brand is requis except pour movies/books/music, and requis (as votre store nom) pour homemade goods.
• Aucun GTIN? Fallback is brand + MPN. None of the three? Définir identifier_exists: false.
• The un rule: jamais invent, guess, borrow, or reuse a GTIN — Google repeats ce à travers four separate docs. A valid checksum ≠ a correct GTIN; the number peut belong to a différent product.
• Vérifier twice: GS1 Vérifier Digit Calculator (format) and Verified by GS1 / GEPIR (ownership). Éviter restricted/coupon prefixes 02, 04, 2, 05, 98, 99.
• Five échec modes: reused/borrowed GTIN, manquant GTIN on a product que has un, identifier_exists: false contradicted by catalog evidence, duplicate GTINs à travers votre propre catalog, and submitting an internal SKU as a GTIN.
• Enforcement history: 2019 = manquant UPIs became a priority/visibility penalty, pas auto-disapproval; 2021 = extended to free listings + duplicate-GTIN disapprovals; Dec 2023 = identifier_exists mismatches downgraded from disapproval to warning. Bar pour correctness up, penalty pour un mistake bas.
• Bing: même model (identifierExists defaults to true), enforced plus mechanically at the API insert level.

Documentation officielle

Primary-source documentation from Google and Microsoft.

Google — attribute specs

• À propos de unique product identifiers — the canonical policy page: quand GTIN/MPN/brand are requis, 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] — requis pour products sans 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 données specification — the complet attribute requirement matrix.
• Trouver a GTIN — Google’s definition and how to locate a GTIN.

Google — troubleshooting

• Comment corriger: Incorrect GTIN — the reused/wrong-product GTIN error.
• Comment corriger: Manquant or incorrect GTIN — manquant or unrecognized UPI valeurs.
• Comment corriger: Incorrect product identifier — the inverse identifier_exists: false mismatch.
• Fix problèmes with a GTIN or unique product identifier (troubleshooter) — interactive fix-it flow.
• Providing meilleur product information pour shoppers (Search Central blog, Feb 2021) — the “why you must not invent or reuse a GTIN” explainer.

Microsoft / Bing

• Managing votre Products — Microsoft Advertising Content API — brand/gtin/mpn requirements and the identifierExists par défaut-true rule.
• Unique identifiers pour votre product ads — Microsoft Advertising Aider — the human-readable version of the ci-dessus.

GTIN verification (GS1)

• GS1 Vérifier Digit Calculator — confirms a GTIN’s checksum is well-formed.
• Verified by GS1 — ownership/validity lookup: qui company a GTIN en réalité belongs to.

Quotes from the source

On-the-record statements from Google and Microsoft. Chaque lien is a deep lien que 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 Center Aider, À propos de unique product identifiers. Jump to quote
• “Don’t make up, guess, or include values from similar products.” — Google Merchant Center Aider, À propos de 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 Aider, À propos de 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 Aider, À propos de unique product identifiers. Jump to quote

Google — the attribute specs

• “Required for all products without a manufacturer-assigned GTIN.” — Google Merchant Center Aider, MPN [mpn]. Jump to quote
• “Only provide a brand if you’re sure it’s correct.” — Google Merchant Center Aider, 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 Aider, 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 Aider, 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 votre 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 votre 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 votre Products. Jump to quote

Industry coverage — the Dec 2023 policy modifier

• “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, Moteur de recherche Roundtable, reporting Google’s December 2023 modifier. Jump to quote

Qui identifiers devrait I submit pour ce product?

Fonctionner via it product-by-product. The whole chose hinges on un question: fait a manufacturer-assigned GTIN en réalité exist pour ce item?

Mistakes que obtenir products flagged

Concrete errors from the field, pourquoi they’re incorrect, and Que faire à la place.

Making up, guessing, or borrowing a GTIN. Pourquoi it’s incorrect: Google explicitly forbids it, and a GTIN copied from a similaire product is valid-format but wrong-product — the exact mechanism behind the Incorrect GTIN disapproval. Do à la place: pull the GTIN from the packaging or the manufacturer, and vérifier ownership avant submitting.

Treating a valid vérifier digit as proof the GTIN is correct. Pourquoi it’s incorrect: the GS1 Vérifier Digit Calculator seulement confirms the number is well-formed. A réel, checksum-valid GTIN belonging to someone else’s product va réussir the math and encore be incorrect pour vous. Do à la place: ajouter an ownership vérifier (Verified by GS1 / GEPIR), pas simplement a format vérifier.

Flipping identifier_exists to faux to skip finding a GTIN. Pourquoi it’s incorrect: Google cross-validates the claim contre its catalog — “Products pour qui the identifier exists attribute is incorrectly définir to aucun or faux and pour qui là is evidence que a unique product identifier exists, va recevoir a warning” (source). It’s a warning since December 2023, pas an instant disapproval — but performances is encore limited. Do à la place: seulement définir it to false pour products que genuinely have aucun GTIN, MPN, or brand; sinon trouver and submit the réel identifiers.

Submitting votre internal SKU as the GTIN. Pourquoi it’s incorrect: SKUs are merchant-internal and pas globally unique — they’re meaningless to Google’s catalog and aren’t GTINs. Do à la place: submit the réel GTIN, or brand + MPN si there’s aucun GTIN; garder votre SKU in the id attribute où it belongs.

Copying un MPN à travers a whole variant groupe. Pourquoi it’s incorrect: chaque product variant (color/size) typically has its propre MPN; a shared MPN peut causer the variants to be treated as the même product. Do à la place: give chaque variant its propre manufacturer-assigned MPN.

Assuming brand is optional/cosmetic. Pourquoi it’s incorrect: brand is requis pour quelconque product with a clearly associated brand or manufacturer — and requis (as votre store nom) même pour homemade/custom goods. It’s seulement truly optional pour brand-less categories comme movies, books, and music. Do à la place: toujours supply an accurate brand unless the product is genuinely brand-less.

Trusting old blog posts que dire “no GTIN = instant disapproval.” Pourquoi it’s incorrect: que was closer to vrai avant the September 2019 shift to a priority-based system. Today, manquant identifiers reduce visibility; incorrect identifiers are ce que risk disapproval. Do à la place: treat manquant and incorrect as différent problems — manquant weakens visibility, incorrect peut break the listing.

Product identifiers — cheat sheet

Requirement En un coup d’œil

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 que are JAMAIS valid product GTINs

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

The five mismatches que trigger warnings/disapprovals

1. Reused/borrowed GTIN (valid checksum, incorrect product) → disapproval risk.
2. Manquant GTIN on a product que has un → limited visibility.
3. identifier_exists: false contradicted by catalog evidence → warning.
4. Duplicate GTINs à travers votre propre catalog → ambiguous, un survives.
5. Internal SKU submitted as a GTIN → invalid.

Vérifier in two steps

• Format → GS1 Vérifier Digit Calculator.
• Ownership → Verified by GS1 / GEPIR.

Enforcement timeline

• 2019 → manquant UPIs = priority/visibility penalty (pas auto-disapproval).
• 2021 → extended to free listings + duplicate-GTIN disapprovals.
• Dec 2023 → identifier_exists mismatches = warning, pas disapproval.

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

“Incorrect GTIN” même though the number passes a checksum

Symptom: Merchant Center rejects a GTIN que has a valid length and vérifier digit. Probable causer: The number is well-formed but belongs to un autre product or company. Fix: Comparer it with the physical packaging or manufacturer record, alors confirmer ownership via Verified by GS1. Replace borrowed or generated valeurs; confirmer the problème clears après reprocessing.

Missing-GTIN warning on a product que has a barcode

Symptom: A mass-produced product remains eligible with limited visibility or reports a manquant identifier. Probable causer: The assigned manufacturer GTIN was omitted, mapped to the incorrect variant, or placed in an internal-SKU field. Fix: Submit the exact product/variant GTIN from packaging or the manufacturer. Garder the merchant SKU in id, pas gtin, and confirmer the processed item montre the identifier.

identifier_exists warning

Symptom: The feed dit identifier_exists: false, but the platform reports que an identifier apparaît to exist. Probable causer: The exemption was utilisé pour a branded catalog product que has a GTIN or brand-plus-MPN. Fix: Trouver and submit the assigned identifier, alors restore identifier_exists to true. Utiliser false seulement quand the product genuinely has aucun GTIN, MPN, or applicable brand.

Duplicate-GTIN disapproval à travers separate products

Symptom: Différent catalog items are grouped or disapproved parce que ils share un GTIN. Probable causer: A parent, sibling variant, placeholder, or copied valeur was mapped à travers multiple distinct products. Fix: Reconcile chaque item and variant contre manufacturer records. Supprimer the bad valeur jusqu’à the correct un is verified, alors confirmer distinct products ne … plus share the GTIN.

SKU rejected as a product identifier

Symptom: A valeur que fonctionne à l’intérieur the commerce platform fails GTIN checks. Probable causer: An internal SKU was submitted as a globally standardized identifier. Fix: Garder the SKU as the feed id; submit the réel GTIN, or brand plus manufacturer MPN quand aucun GTIN was assigned. Si the product genuinely has aucun identifiers, utiliser the documented exemption au lieu de relabeling the SKU.

GTIN ownership vérifier

Tester to run: Comparer the proposed GTIN with the exact product packaging or manufacturer record, alors regarder it up in Verified by GS1; utiliser the check-digit calculator seulement as a separate format vérifier. Attendu result: The number is valid and the ownership/product evidence agrees with the item being submitted. Échec interpretation: The GTIN may be borrowed, generated, or mapped to the incorrect variant. Monitoring window: Avant the identifier is ajouté or modifié. Rollback trigger: Ne faites pas submit quelconque GTIN whose ownership or exact-product relationship ne peut pas be verified.

Identifier-field consistency tester

Tester to run: Validate a cohort representing manufacturer-GTIN products, brand-plus-MPN products, and genuinely identifier-less products. Attendu result: GTIN products submit the réel GTIN; no-GTIN branded products submit brand plus MPN; genuine exemptions omit unavailable identifiers and définir identifier_exists to false. Échec interpretation: The feed mapping s’applique un identifier rule to unlike product types. Monitoring window: Avant upload and après quelconque catalog-mapping modifier. Rollback trigger: Arrêter the mapping rollout si it guesses valeurs, étiquettes SKUs as GTINs, or s’applique the exemption to connu branded products.

Duplicate-identifier vérifier

Tester to run: Groupe the final feed by normalized GTIN and examiner every valeur assigned to plus que un item, notamment variants. Attendu result: Repeated GTINs represent the même legitimate product relationship; distinct products and distinct assigned variants ne faites pas share a copied identifier. Échec interpretation: A parent-level field or placeholder has propagated à travers multiple offers. Monitoring window: Immédiatement avant chaque complet feed publish. Rollback trigger: Hold affected offers quand a shared GTIN ne peut pas be justified from manufacturer données.

Testez vos connaissances: Product Identifiers

Five rapide questions on GTIN, MPN, brand, and the identifier_exists exemption. Pick an réponse pour chaque, alors vérifier.

Ressources utiles

Connexe on ce site

• Google Merchant Center — the hub: free product listings, Product schema vs. feeds, the srsltid parameter.
• Merchant Center feed optimization — où identifiers fit alongside titles, images, feed rules, and diagnostics.

From autour the industry

• Google Merchant Center Identifier Exists Va Ne … plus Lead To Disapprovals — Barry Schwartz, Moteur de recherche Roundtable (Dec 2023): the warning-not-disapproval modifier, with Google’s wording.
• Google to enforce unique product identifiers on free merchant listings — Moteur de recherche Land (2021): the extension of UPI enforcement to free listings and duplicate-GTIN disapprovals.
• Ce que vous devez know à propos de Google Merchant Center identifier enforcement updates — Moteur de recherche Land (2019): the shift from auto-disapproval to a priority-based system.
• Unique product identifiers: Comment utiliser Brand, MPN, and GTINs — DataFeedWatch: a practical walkthrough of tout three attributes.
• Finding GTINs Pour Votre Products — DataFeedWatch: où to regarder quand vous don’t have a GTIN on hand.
• Ce que Is a GTIN and Pourquoi Do Vous Besoin Un? — Store Growers: a beginner-friendly GTIN primer.

Journal des modifications