How a GTIN works
A GTIN is the number underneath a product’s barcode, assigned by whoever brings the product to market rather than by the shop selling it. The familiar formats are all GTINs under different names: the UPC used in North America, the EAN used across Europe and much of Asia, the JAN in Japan, the ISBN on books. They differ in length, not in purpose.
That purpose is matching. When you submit a product with its GTIN, a shopping platform can recognise that your listing and many other listings describe the same physical item. Comparison, product panels and shopping results are all assembled on that basis — the identifier does the joining, not your product title.
Why GTINs matter
For anyone advertising products, a correct GTIN is often the difference between a listing that competes and one that is quietly ignored. Google Merchant Center expects it for products that have one, and feeds that omit it or supply a wrong one can see items disapproved or shown less often. Matching also lends your listing the platform’s own knowledge of the product — specifications, category understanding, reviews — which you did not have to supply yourself.
There is an organic benefit as well. Product structured data on your own pages can carry the GTIN, helping search engines connect your page to the same item elsewhere. That matters most for shops reselling well-known brands, where the identifier is the only strong signal that two very different-looking pages describe one product.
Where GTINs go wrong
Inventing them is the serious error. The codes are issued through a central registry, so a made-up or reused number either fails validation or, worse, matches somebody else’s product. Copying the code from a similar item does the same damage, and so does using one code across a whole range: each sellable product variant needs its own identifier.
The everyday errors are duller but just as costly. Leading zeros stripped by a spreadsheet, a code stored in scientific notation, a check digit lost in an export, or the shop’s own stock keeping unit dropped into the GTIN field. Genuinely own-brand products with no barcode are a separate case: declare that the identifier does not exist rather than filling the gap with something invented.
How to act on it
Take the codes from the source — the manufacturer, the distributor, or the barcode on the packaging — and store them as text in your product data so nothing reformats them. Validate them before they reach a feed. The final digit is a check digit calculated from the rest of the number, so an invalid code can be caught automatically without asking anyone.
If you manufacture your own products and want them on shopping platforms and marketplaces, obtaining codes through the official registry is the durable answer. Then keep the identifier consistent everywhere it appears — your structured data, your product feed and any marketplace listing — because contradictions between those sources are what trigger disapprovals.
