How to Fix Missing GTIN Errors in Google Merchant Center

if you're running google shopping from a shopify store, you've probably seen one of these in merchant center: "limited performance due to missing value [gtin]", or worse, products disapproved outright. it's one of the most common feed problems we see - and one of the most quietly expensive, because the products affected simply stop showing up where buyers are looking.

here's what's actually going on, and how to fix it.

first, what a gtin is

a gtin - global trade item number - is the unique identifier behind a product's barcode. depending on where the product comes from it might be a upc, an ean or an isbn. google uses it to recognise exactly what you're selling, match it to relevant searches, and group it against the same item sold elsewhere. when a gtin is present and correct, your listing is richer and easier to surface. when it's missing or wrong, google struggles to classify the product - and limits how often it appears.

why the error shows up

there are really only a handful of root causes, and the fix depends on which one you've got:

the gtin exists but you haven't submitted it. google can often tell a product has an assigned gtin. if you leave it blank, it flags limited performance.
the gtin is invalid. wrong length, a failed check digit, or a value from a restricted range. google rejects these.
identifier_exists is set incorrectly. people often set this to false just because they don't have the gtin to hand - but if google has evidence one exists, the product gets disapproved.
the same gtin is reused across different products. google reads that as ambiguous and suppresses the listings.
variants aren't mapped. each size, colour or configuration usually has its own gtin. one value across all variants causes errors.

how to fix it in shopify

in shopify, the gtin lives in the barcode field, under inventory on each product or variant. for a handful of products you can edit them by hand. for a real catalogue, that's hours of work and a lot of room for error - so a bulk import (via a tool like matrixify) is far safer, letting you update every barcode from a single sheet.

the order of operations that actually works:

source the correct gtins - from the product packaging, the manufacturer, or your supplier. don't invent them; made-up values get you disapproved.
validate them before import - correct length and a valid check digit - so you're not importing errors at scale.
map them at variant level, not just product level.
re-submit the feed and watch merchant center clear the flags over the next day or two.

what if your products genuinely don't have gtins?

plenty don't. handmade pieces, own-brand products and bespoke items often have no manufacturer gtin at all. the correct fix here is not to leave things blank and hope - it's to set identifier_exists to false and supply brand and mpn instead. done properly, those products stay eligible and perform; done carelessly, they get disapproved alongside the rest.

how to know it worked

merchant center diagnostics will show the affected product count dropping as the corrected feed is processed. it's worth confirming the fix held after a couple of feed refreshes rather than assuming - and checking that your analytics are actually tracking the shopping traffic, so you can see the difference in revenue, not just approvals.

the honest version

none of this is conceptually hard. but across a few hundred products, with variants, mixed gtin availability and complex logistics, it's fiddly, repetitive work where small mistakes get expensive. that's exactly the kind of thing worth getting right once and then forgetting about.

if you'd rather not spend your week in a barcode spreadsheet, that's what we do. we run a gtin & feed fix - isolating exactly what's wrong through an audit first, then fixing it across your whole catalogue. you can book an audit to see what your feed is costing you before committing to anything.