Skip to content
Published Authored byBilly Reiner

Schema · How-to

Shopify GTIN, UPC, EAN, ISBN schema

Current Shopify themes such as Dawn print the variant's barcode as the generic gtin property when the Barcode field is filled6. Google accepts that, but recommends the most specific GTIN property that applies7. Older themes print no GTIN at all, so the length-based mapping is still the merchant's job. Shopify keeps every identifier in one field, Barcode (Admin > Products > [product] > Inventory > Barcode (ISBN, UPC, GTIN, etc.))2, while Schema.org Product exposes five separate ones: gtin (generic), gtin8, gtin12, gtin13, and gtin141. This page is the mapping between them.

Shopify's own Catalog optimisation doc names Barcode among the seven product fields AI platforms read. Google Merchant Center requires GTIN for most product categories. The 2026 install: emit the GTIN value to the schema property that matches its length — gtin12 for 12-digit UPCs, gtin13 for 13-digit EANs, gtin8 for 8-digit EANs, gtin14 for 14-digit cases.

What GTIN is

GTIN is the GS1 standard global identifier for trade items, and Schema.org Product accepts it through five properties: the generic gtin plus the length-specific gtin8, gtin12, gtin13 and gtin14. Google's Product documentation recommends the length-specific property whenever the merchant knows which one applies.

Mental model: GTIN is the universal product ID that lets Amazon, Google, ChatGPT, and every distributor refer to the same product across systems. A Shopify merchant assigning GTINs to their own products contributes their catalog to the global trade graph; a Shopify merchant reselling third-party products inherits the manufacturer's GTINs and should emit them verbatim. For the standard itself — GS1 governance, the check-digit structure, and which identifier a given product needs — see the GTIN glossary entry.

Shopify's Barcode field

Shopify exposes the GTIN as a single Barcode field on every product variant: Admin > Products > [product] > Variants > [variant] > Inventory > Barcode (ISBN, UPC, GTIN, etc.). The Liquid object is product.selected_or_first_available_variant.barcode (or variant.barcode in variant loops). Shopify does not validate the format — you can store any string. The validation happens downstream at Merchant Center, in the schema validator, and at Catalog ingestion.

Which gtin property to use

The decision tree per Schema.org and Google's recommendation: 8-character barcode emits gtin8, 12-character emits gtin12, 13-character emits gtin13, 14-character emits gtin14, ISBN-10 (10 chars) emits isbn AND gtin (Book subtype only), ISBN-13 (13 chars, starts with 978 or 979) emits gtin13 (it IS an EAN-13). Anything else (custom internal codes, MPNs) goes in mpn, not gtin.

  • 8 digits — gtin8 (small-product EAN-8).
  • 12 digits — gtin12 (UPC-A — US and Canada retail).
  • 13 digits — gtin13 (EAN-13 — international, including ISBN-13 for books).
  • 14 digits — gtin14 (ITF-14 — cases, cartons).
  • 10 digits (ISBN-10) — isbn on Book subtype. Schema.org does not have a gtin10 property; ISBN-10 is book-specific.
  • Other (MPN, internal SKU stored in Barcode) — do not emit gtin. If it's a Manufacturer Part Number, use mpn instead.

JSON-LD example — length-aware gtin mapping

The block below detects the Barcode field's length and emits the correct gtin property. Paste inside main-product.liquid as part of your Product block (the one that replaces the theme's structured_data line), in place of a plain gtin line. The Liquid case statement handles the four GTIN lengths; any other length falls through with no gtin emission. The barcode goes through | json, which adds the quotes.

JSON-LD Length-aware GTIN mapping from product.barcode 
{%- assign barcode = product.selected_or_first_available_variant.barcode -%}
{%- assign len = barcode | size -%}
{%- if barcode != blank -%}
  {%- case len -%}
  {%- when 8 -%}
  "gtin8": {{ barcode | json }},
  {%- when 12 -%}
  "gtin12": {{ barcode | json }},
  {%- when 13 -%}
  "gtin13": {{ barcode | json }},
  {%- when 14 -%}
  "gtin14": {{ barcode | json }},
  {%- endcase -%}
{%- endif -%}

Merchant Center alignment

Google Merchant Center requires GTIN for most retail product categories (apparel exempted in some markets; handmade and vintage exempted globally). When Merchant Center has a GTIN in the feed and the storefront's Product JSON-LD emits a different GTIN — or no GTIN at all — the product gets flagged in Merchant Center diagnostics, and the listing can be suspended. The fix is consistency: same GTIN, same length-property, same product.

For Shopify stores using Shopify's official Google & YouTube channel (or a third-party Merchant Center sync app), the feed pulls each variant's barcode and maps it to Merchant Center's gtin attribute. Verify the feed in Merchant Center diagnostics; verify the schema in Rich Results Test; they must agree.

Validation

Rich Results Test against a PDP with gtin emitted should report Product detected, the gtin property parsed, zero errors. If the Barcode field holds something that isn't a GTIN (letters, spaces, hyphens, the wrong length), expect the test to flag the value as invalid; Google requires GTINs in numeric form. The Schema.org Markup Validator parses every gtin property as plain text and won't catch a bad value.

A subtle gotcha: Shopify allows Barcode to contain spaces or hyphens (sometimes manufacturers ship product packaging with formatted barcodes like '5012345-678900'). The schema property expects unformatted digits only. Pass through | remove: '-' | remove: ' ' in Liquid to strip formatting characters before emitting.

Shopify gotchas on GTIN

Four gotchas. First: storing internal SKUs in the Barcode field — these are NOT GTINs and should not be emitted to a gtin schema property. Use mpn for manufacturer codes, sku for internal codes. Second: hard-coding gtin13 when some products have UPC-A (12-digit). Use the length-aware branch. Third: forgetting that the barcode belongs to the variant. The product object has no barcode property. Use product.selected_or_first_available_variant.barcode (or variant.barcode in a variant loop). Fourth: leaving Barcode empty on handmade/vintage products and then emitting an empty gtin field — wrap the emission in a Liquid conditional.

A fifth gotcha for multi-variant products: each variant can have its own barcode. Schema.org Product accepts one gtin per Product object, which means the JSON-LD reflects only the selected variant's barcode at any given page load. For products with five sizes each with distinct GTINs, the complete representation is a ProductGroup with hasVariant where each variant Product carries its own gtin. The full pattern is in Google's variant documentation.

Keep reading