Underwing · Explainers · September 15, 2026

A made-up GTIN is worse than none: how product identifiers decide whether Google’s AI shopping finds you

If you sell through Google’s AI shopping surfaces, AI Mode in Search and the Gemini app, the field that decides whether Google can find your product for a shopper is your product identifier: the GTIN. It is not a ranking bolt-on you add to climb higher. It is the key Google uses to understand what you are selling and to line your offer up against the same product from other sellers. In Google’s own words, “Accurate matching to products can’t be assured when GTIN is missing.”

Watch this explainer (3 min).

That makes two opposite mistakes both expensive. The first is inventing a GTIN to fill an empty field, which can get the product disapproved outright. The second is leaving the field blank on a product that genuinely has no identifier, when Google gives you a specific flag to declare exactly that. The docs tell you which move to make in each case. Most of the “optimize your feed for AI” advice I read gets the emphasis backwards, so here is the version straight from the source.

How your catalog reaches Google’s AI answers

Google’s AI shopping does not read your website live. It reads a product database. “Our new AI Mode shopping experience brings together Gemini capabilities with our Shopping Graph,” Google says. The Shopping Graph is the 50-billion-listing catalog behind AI Mode, Gemini and the Shopping tab, and it is built from what merchants send in: product info arrives “either through information retailers share directly via Google Merchant Center or from what retailers and brands post across the web.” So your Merchant Center feed is the raw material, and the identifier on each row is how Google files it.

How your catalog reaches Google’s AI shopping answersYour product feed(Google Merchant Center)GTINmatch keyShopping Graphmatches + groups your offerwith the same productAI Mode + Geminishopping answers

What the GTIN actually does

A GTIN, the barcode number a manufacturer assigns, is not decoration. Google is explicit about its job: “A GTIN helps us make your ad or unpaid listing easier for your customers to find,” and “When you submit these product identifiers, we can better understand what you’re selling. When we understand what you’re selling, we can make your ads and unpaid listings richer and help connect customers to your products.” When several sellers list the same manufactured item, the identifier is how Google knows it is the same item. Without it, “Accurate matching to products can’t be assured,” and “Products with missing or incorrect GTIN [gtin] attributes may have limited visibility.” In an AI Mode answer that compares options side by side, being unmatched means being left out of the comparison.

Mistake one: inventing a number to fill the field

Because merchants hear “GTINs help,” a common reflex, and something several feed apps do automatically, is to put something in the field. That is the worst move. Google’s instruction could not be plainer: “Only provide a GTIN if you’re sure it’s correct. When in doubt don’t provide a GTIN (for example, don’t guess or make up a value).” A wrong identifier does not sit there harmlessly. It triggers the “Incorrect product identifier” error, and “Offers without accurate identifiers will remain disapproved until that information is provided.” Google also draws the line on where a valid number comes from: “You must only use GTIN numbers that have been assigned by the manufacturers of these products.” A guessed or recycled barcode is not safer than an empty field. It is a disapproval waiting to happen.

Mistake two: a blank field when you legitimately have none

Plenty of real products have no GTIN at all. Google names them: “Custom goods or one-of-a-kind products, like custom T-shirts, art, or handmade goods,” and “Products produced before GTINs were introduced, like vintage products, antiques, books published before 1970.” For these, the answer is not to leave the field blank and hope, and definitely not to invent one. Google provides a flag for exactly this situation: “Use the identifier exists [identifier_exists] attribute to indicate that unique product identifiers (UPIs) aren’t available for your product.” Set it to false, and your product stays eligible without a GTIN. Unique product identifiers, for the record, are the GTIN, MPN and brand attributes together.

Does this product have a manufacturer-assigned GTIN?Has a real GTINSubmit the exact number.Never guess or reuse.Matched to the productGenuinely has noneCustom, handmade, vintage,books before 1970.Set identifier_exists = falseEligible without a GTINGuessed or made upA value typed in justto fill the field.Disapproved until fixed

The self-check, and one honest caveat

You can see all of this in Merchant Center itself. Open the Products diagnostics and look for two things: the “Incorrect product identifier” error, and the “Limited performance due to missing value: GTIN” notice. The fix follows the diagram above: supply the correct manufacturer number, or declare identifier_exists false where the product truly has none.

The honest caveat: identifier_exists false is not an escape hatch for a whole catalog. If Google believes a product should have a GTIN, based on other sellers listing the same item, it will reject the false flag and ask for the real number. The flag is for genuinely identifier-less goods, not a way to skip the work on branded ones.

None of this is an AI-era trick. It is the same product-data discipline Google has documented for years, and AI Mode simply raised the stakes: the identifier is now what decides whether you enter the comparison at all. If you want to see what your store is actually sending to these surfaces, the free scan at pollen.elytron.in reads it from the outside, no signup.

Written by Aman, founder of Elytron Labs: Pollen (agent commerce readiness) and DripSync (AI product image sync).

Leave a comment

Your email stays private. First-time comments are held for review.