GTIN (Global Trade Item Number)

GTIN is governed by GS1², the global standards body that issues company prefixes and the resulting product identifiers. The numeric structure is the same across all GTIN variants — a company prefix, a product reference number, and a check digit — with the variants distinguished only by total length. The underlying purpose is global product disambiguation: two different products in two different countries should never share the same GTIN, and the same product should carry the same GTIN everywhere it sells.

The variant a merchant uses is determined by where the GTIN was assigned. A US-based brand selling US-only typically uses GTIN-12 (UPC). A European brand or a global brand selling internationally typically uses GTIN-13 (EAN). A book publisher uses GTIN-13 (ISBN with the 978 or 979 prefix). The merchant does not pick the variant; the manufacturer's GS1 registration determined it.

What a Shopify merchant should never do: invent a GTIN. The check-digit math means random 12-digit strings are not valid GTINs, AI channels and Merchant Center validate them, and an invalid GTIN is worse than a missing one — it signals the field is unreliable rather than just unpopulated.

The point of consolidation was to make ecommerce, supply chain, and retail systems interoperable across borders. By 2010 GTIN was the de facto product identifier for ecommerce on Amazon (where it's mandatory in most categories), Google Shopping (where it's required in many categories), and the general AI-shopping infrastructure that emerged in 2024 - 2026.

Where GTIN is optional: DTC brands whose products have no external manufacturer (you make them yourself, you sell them yourself, no retail distribution) can self-assign a GTIN via GS1 membership, or skip the field entirely. For these brands the Brand schema and clean Product schema do most of the disambiguation work. For everyone else — resellers, distributors, brands sold elsewhere — GTIN should be populated.

Install order: (1) for each product, locate the manufacturer-assigned GTIN (the printed barcode on the package); (2) for each variant, populate the Barcode field with the GTIN for that specific variant; (3) verify the resulting Schema.org Product output emits the gtin property (use Google's Rich Results Test); (4) verify the product shows up in Shopify Catalog with a populated barcode.

The full install lives in Barcode, GTIN, UPC on Shopify, which covers which GTIN variant to use, how to populate variants efficiently, and how to debug missing GTINs in Catalog. If you'd rather we do the Barcode-field population audit, ShopifyRanked does it in 7 days for $499.

• Shopify Catalog: the data layer GTIN feeds into.
• Structured data: where GTIN emits as a Schema.org Product property.
• JSON-LD: the syntax Shopify themes use to emit Product schema including GTIN.
• Barcode field article: the Shopify-specific install.