Skip to content
Published Authored byBilly Reiner

Glossary · Defined term

GTIN (Global Trade Item Number) on Shopify

GTIN (Global Trade Item Number) is the GS1-standard numeric product identifier2. UPC (North America, 12 digits), EAN (Europe/global, 13 digits), ISBN (books, 13 digits), and JAN (Japan, 13 digits) are all GTIN variants. On Shopify, GTIN lives in the product Barcode field, which Shopify renders as "Barcode (ISBN, UPC, GTIN, etc.)" and lists explicitly as a field AI platforms consider1.

For a Shopify merchant, GTIN matters in three places at once: Shopify Catalog (AI channels read the Barcode field directly), Schema.org Product output (theme-emitted JSON-LD includes gtin when populated3), and Google Merchant Center (GTIN is a required field for branded products with manufacturer assignment).

Definition

GTIN (Global Trade Item Number) is the GS1 standard product identifier. UPC, EAN, ISBN, and JAN are all GTIN variants. On Shopify, GTIN lives in the product Barcode field, which Shopify lists as a field AI platforms consider.

GTIN is governed by GS12, 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.

GTIN variants and their lengths

GTIN-8 (8 digits, small package goods), GTIN-12 (12 digits, the North American UPC), GTIN-13 (13 digits, the European EAN, including ISBNs for books and JANs for Japan), and GTIN-14 (14 digits, case-level packaging). All four are valid GTINs and Schema.org accepts any of them on the gtin property.

Which variant applies to a given product is covered in Barcode, GTIN, UPC on Shopify, and which schema property that length maps to is covered in GTIN in Product JSON-LD.

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.

Where GTIN comes from

GTIN was formalised by GS1 in the early 2000s as the unified naming framework that subsumed the previously regional schemes (UPC from the US, EAN from Europe, JAN from Japan). The underlying barcode is older — UPC dates to 1974 — but the unified GTIN brand and numbering structure is a 2000s consolidation.

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.

Adoption status in 2026

Universal among branded products. Manufacturers in apparel, beauty, supplements, food, electronics, and books all assign GTINs to every SKU as a matter of course. The merchant's job is to populate the Barcode field with the manufacturer-assigned GTIN, not to invent one.

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.

GTIN on Shopify specifically: the Barcode field

On Shopify, GTIN lives in the per-variant Barcode field. The field is labelled 'Barcode (ISBN, UPC, GTIN, etc.)' in Shopify's documentation. It is a per-variant field — not per-product — because variants of the same product carry different GTINs (different sizes, colours, packs each have their own barcode).

For sourcing the manufacturer-assigned GTIN and populating the Barcode field across variants, see Barcode, GTIN, UPC on Shopify. For getting that stored value into the correct Schema.org property in your theme's Product JSON-LD, see GTIN in Product JSON-LD.

If you'd rather we do the Barcode-field population audit, ShopifyRanked does it in 7 days for $499.

GTIN sits at the intersection of Shopify Catalog and Schema.org Product structured data.

Keep reading