What is a GTIN?

GTIN stands for Global Trade Item Number, the standard identifier that GS1 (the international organisation that manages barcode systems) assigns to a product to distinguish it from every other product on the market. It is the number encoded under the barcode, commonly known as a UPC or an EAN depending on the region and the format.

Each variant of a product, such as the same model in a different colour, size or fill volume, needs its own GTIN. A GTIN does not describe the product in text: it does not say whether it is a blue T-shirt or a 50 ml face cream. What it does is give that specific product a number that any system, from a checkout till to the Google Shopping catalogue, can read and recognise without ambiguity.

It is worth distinguishing the GTIN from the SKU. The SKU is an internal code each store invents for its own inventory, and it can repeat or change from one store to another. The GTIN is assigned by GS1, or by the manufacturer under licence from GS1, and it stays the same in every store worldwide that sells that product. One is private, the other is universal.

The same GTIN travels with the product throughout its entire commercial life: it appears on the manufacturer's invoice, on the warehouse delivery note, and on the checkout receipt, always as the same number. That persistence is what lets systems run by different companies, which never coordinated with each other, refer to the same product without ambiguity.

The GTIN relies on the GS1 system, the same organisation that manages barcodes and shipping labels across the supply chain. A company becomes a member of a local GS1 organisation, receives its own company prefix, and from then on can generate its own GTINs for each product, with the guarantee that two companies will never assign the same number. The code ends with a check digit, calculated from the preceding digits, which detects whether the number was mistyped before it causes an error further down the catalogue.

That number travels with the product in three places that are, in practice, distinct even though they all reference the same GTIN: the physical barcode printed on the packaging, the product data sheet a manufacturer or distributor publishes, and the data feed a store submits to platforms such as Google Merchant Center. Google uses the gtin attribute from the feed to match each item against the information it already holds about that product in its database, something it describes in its own documentation as helping match user searches with the corresponding products.

Whether a GTIN is valid and which company it's licensed to can be checked in a public database, Verified by GS1. That check differs from the one Google runs: GS1 confirms the number exists and who owns it; Google additionally checks whether it matches the advertised product.

When the GTIN is missing on a product that was assigned one, or when the number is mistyped, Google cannot make that match reliably. The documented result is limited visibility for the product in Shopping, and if the number is clearly wrong, the item can be disapproved.

The GTIN determines whether a product enters Google Shopping's structured catalogue reliably or gets pushed aside. It is not a bureaucratic checkbox: it is the piece that connects a store's feed with the product database that Google, and increasingly AI-driven shopping assistants, use to answer what to buy, where, and at what price.

An incorrect GTIN is different from a missing one, and each is penalised differently. If the manufacturer never assigned a GTIN to the product, Google Merchant Center accepts that the field stays empty. If the product does have a GTIN and the store omits it or gets it wrong when copying it, the documented consequence is reduced visibility, and in clearer cases, the item gets disapproved.

The same data point is also used outside paid ads: Schema.org's Product markup includes a field for the GTIN, which search engines and AI-driven shopping assistants can rely on to confirm which product is meant, instead of relying only on the free-text name.

For any business that depends on Shopping, Google's price comparison surfaces, or a well-built product feed, the GTIN is a technical requirement with direct commercial consequences: a catalogue with correct GTINs shows up where it should; one with badly loaded GTINs competes at a disadvantage even if the rest of the listing is flawless.

• Ask the manufacturer for the GTIN instead of making one up: an invented number gets flagged as incorrect and can get the product disapproved.
• Check every GTIN against GS1's public database (Verified by GS1) before uploading the feed, especially when the data comes from a third-party supplier.
• Assign a distinct GTIN to each real product variant, such as colour, size or fill volume, never the same number for the whole product family.
• If the product has no assigned GTIN, leave the field empty instead of filling it with the store's internal SKU.
• Check the check digit before uploading the feed: a single mistyped digit invalidates the whole code.
• Audit Google Merchant Center's diagnostics report periodically to catch products flagged with an incorrect or restricted GTIN.

• Using the same GTIN for different variants of the same product, for example every size of a T-shirt, which leaves Google unable to tell which variant is which.
• Copying the GTIN from another seller advertising a similar product, instead of using the one from your own manufacturer.
• Confusing the GTIN with the internal SKU and submitting the SKU in the feed's gtin field.
• Submitting a GTIN from a restricted number range, meaning prefixes GS1 reserves for coupons or other uses, which triggers automatic rejection of the product.
• Assuming every product must have a GTIN: some categories, such as books or music recordings, have their own rules and exceptions documented by Google.