What is a GTIN (Global Trade Item Number)? Ecommerce product identifiers, explained
A GTIN, or Global Trade Item Number, is a globally unique number used to identify a trade item. In commerce, that usually means a specific product, variant, case, pack, or service that can be priced, ordered, sold, shipped, scanned, or listed.
GTINs are managed through the GS1 standards system. They are often encoded in barcodes, stored in product catalogs, submitted in product feeds, added to marketplace listings, and exposed in product structured data so systems can recognize the same item across channels.
The short version: a GTIN is the product identifier. A barcode is one way to carry that identifier.
What a GTIN is used for
A GTIN gives different systems a shared way to talk about the same item. Product names can change. SKUs can be internal. Marketplace IDs can be platform-specific. A GTIN is meant to be a stable product identifier that works across organizations.
For merchants, merchandising teams, and builders, GTINs show up in several common workflows. The GS1 GTIN standard is the source for the identifier family, while channel-specific rules such as Google Merchant Center's gtin attribute define how a destination expects merchants to submit it.
| Use case | How the GTIN helps |
|---|---|
| Barcode scanning | The GTIN can be encoded in a barcode so stores, warehouses, and logistics systems can scan the item |
| Product catalogs | The GTIN helps deduplicate records, connect variants, and distinguish similar products |
| Product feeds | Feed destinations use GTINs to identify products, match listings, validate records, and reduce ambiguity |
| Marketplace listings | Marketplaces can use GTINs to match offers to existing product detail pages or product catalogs |
| Google Merchant Center | Google Merchant Center uses the gtin attribute as a product identifier when a product has a valid GTIN |
| Product schema | Product structured data can expose GTIN values so search engines and machine readers understand the product more clearly |
| Retail and supply chain | Trading partners use GTINs for ordering, invoicing, shipping, inventory, GDSN records, and point-of-sale data capture |
| Search and AI commerce | Product identifiers help search, comparison, recommendation, and AI-shopping systems connect facts about the same item |
A GTIN does not make weak product data strong by itself. It works best when it sits beside clean product names, brands, categories, attributes, variants, images, prices, availability, and page data.
GTIN formats
GTIN is an umbrella term for several numeric structures. The structure depends on the product, region, barcode carrier, and packaging level.
| Format | Digits | Common use |
|---|---|---|
| GTIN-8 | 8 | Small items, often outside North America |
| GTIN-12 | 12 | UPC-based product identification, common in North America |
| GTIN-13 | 13 | EAN-based product identification, common outside North America; ISBN-13 also uses a 13-digit structure for books |
| GTIN-14 | 14 | Trade item groupings such as cases, cartons, and packs that can be ordered, priced, or traded as their own item |
A product may need more than one identifier if it is sold at different packaging levels. A single bottle, a 6-pack, and a shipping case can each need their own GTIN because each one is a different trade item.
GTINs should usually be stored as text, not ordinary numbers, because some valid identifiers can contain leading zeros. If a spreadsheet or database strips those zeros, the value can become invalid or fail to match the correct product.
GTIN vs related identifiers
GTINs are easy to confuse with the labels, codes, and carriers around them. The difference matters because channels often validate these fields separately.
| Term | What it means | How it relates to GTIN |
|---|---|---|
| GTIN | The Global Trade Item Number that identifies a trade item | The core identifier |
| Barcode | A scannable data carrier printed or displayed on a product, label, case, or package | A barcode can encode a GTIN, but it is not the GTIN itself |
| UPC | Universal Product Code, often used for retail products in North America | A UPC-A barcode commonly carries a GTIN-12 |
| EAN | International Article Number, formerly European Article Number, common outside North America | An EAN-13 barcode commonly carries a GTIN-13 |
| SKU | Stock keeping unit used internally by a merchant, retailer, or system | Useful internally, but not globally unique across businesses |
| MPN | Manufacturer part number | Identifies a manufacturer's part, but it is not the same as a GS1 GTIN |
| ASIN | Amazon Standard Identification Number | Amazon-specific product identifier, not a universal product identifier |
| Product ID | A product identifier used inside a storefront, database, API, feed, or marketplace | May be internal, channel-specific, or mapped to GTIN depending on the system |
| Item group ID | A feed field that groups variants, such as colors or sizes | Helps connect related variants; it does not replace the GTIN for each sellable item |
The practical rule: use the right identifier for the right job. A SKU may help your team manage inventory. A GTIN helps outside systems recognize the same product.
Practical GTIN examples
Apparel variant
An apparel brand sells one cotton T-shirt in three colors and five sizes. The product family may share one parent product record, but each sellable color and size variant needs its own identifier.
The navy medium T-shirt, navy large T-shirt, black medium T-shirt, and white small T-shirt should not all reuse the same GTIN. If they do, a marketplace, feed, or search system may collapse variants incorrectly, show the wrong image, mix reviews, or match a shopper to the wrong item.
Marketplace or shopping feed
A merchant sends a product feed to a shopping ads platform or marketplace. The feed includes product ID, title, description, brand, image, price, availability, condition, category, and GTIN.
The GTIN helps the destination understand which exact product is being sold. It can support product matching, richer listings, duplicate detection, and eligibility checks. If a product has a valid GTIN and the feed omits it, the destination may have less confidence in the listing.
Product schema on a product page
A product page can include product schema that labels the product name, image, brand, SKU, offer, price, availability, and GTIN. Schema.org Product supports GTIN-related properties, and Google uses product structured data to understand product pages and rich-result eligibility.
The markup should match the visible product page and the rest of the product data. If the page says one product, the feed sends another identifier, and the schema exposes a third value, search systems and AI tools receive conflicting signals.
Packaging level
A beverage company may sell one can, a 6-pack, a 24-pack case, and a display pack. Each level can be a different trade item because retailers and distributors can order, price, stock, and scan them differently.
Using the unit GTIN for the case can create inventory and fulfillment problems. A channel may think it is receiving one item when the merchant meant a case.
AI shopping and product comparison
AI-shopping systems need to connect product facts from pages, feeds, APIs, reviews, specifications, and merchant catalogs. A GTIN gives those systems a stronger clue that two records describe the same item, even if the title, image, or seller differs.
AI systems still need accurate attributes, variants, compatibility, policies, price, availability, images, and fresh source data to answer product questions reliably.
Why GTINs matter
Product data quality
GTINs make product records easier to validate and match. They help teams spot duplicates, missing identifiers, invalid values, variant mistakes, and records that represent the wrong packaging level.
That makes GTINs part of product data quality, not just barcode administration. A clean GTIN field is most useful when the surrounding product data is accurate, complete, current, and consistent.
Channel readiness
Many commerce destinations expect valid product identifiers when products have them. A retailer portal, marketplace, shopping ads platform, distributor, or product-feed destination may reject a listing, reduce eligibility, or require a manual exception when a required GTIN is missing or invalid.
Channel readiness means knowing which products have GTINs, which are exempt, which variants need separate values, and which records are ready to publish.
Search and discovery
Product discovery systems work better when product identity is explicit. GTINs can help a channel match a merchant's offer to an existing product, combine product facts from trusted records, deduplicate similar listings, and reduce confusion between lookalike products.
That can support better product classification, product snippets, merchant listings, comparison experiences, onsite search, and marketplace matching. It does not guarantee rankings or visibility; it gives systems a cleaner product identity signal.
AI commerce
AI commerce depends on product data that machines can retrieve, compare, and trust. GTINs help AI systems resolve product identity, but they do not answer buyer questions by themselves.
A product record with a GTIN, clean attributes, accurate variants, compatibility data, current availability, and structured policies is much more useful than a record with only a title and image.
Operations and supply chain
GTINs connect digital product data to physical commerce. They help products move through scanning, ordering, receiving, inventory, replenishment, invoices, shipments, and trading partner data exchange.
When ecommerce data, warehouse data, retailer data, and marketplace data use the same identifier correctly, teams spend less time reconciling mismatched product records.
Common GTIN mistakes
Treating the barcode as the GTIN
The barcode is the carrier. The GTIN is the identifier inside it. Product data systems should store the GTIN value clearly instead of treating a barcode image, barcode file, or scan label as the source product identifier.
Reusing one GTIN across variants
Each sellable variant usually needs its own GTIN. Color, size, pack size, count, flavor, configuration, and other variant differences can represent different trade items. Reusing one GTIN across different variants can break product matching, reviews, inventory, recommendations, and marketplace grouping.
Inventing or guessing GTINs
A GTIN should come from the valid identifier assigned to the product. Do not create fake GTINs to satisfy a feed requirement. Invalid identifiers can cause listing disapprovals, mismatches, and trust problems with channels. If a product genuinely does not have a GTIN, use the destination's rules for products without identifiers instead of making one up.
Confusing GTINs with SKUs, MPNs, or ASINs
SKUs are internal. MPNs are manufacturer part numbers. ASINs are Amazon-specific. They can all be useful, but they should not be dropped into a GTIN field unless the destination explicitly says they are valid for that field.
Losing leading zeros
GTIN fields should be stored as strings. Spreadsheet tools, CSV imports, and databases can strip leading zeros when they treat identifiers as ordinary numbers. That small formatting error can turn a valid identifier into a different value.
Using the wrong packaging level
A unit, multipack, case, and display pack can each be separate trade items when each one is ordered, priced, or traded as its own item. Using a unit GTIN for a case, or a case GTIN for a unit, can create errors in inventory, shipping, marketplace listings, and retailer data.
Fixing GTINs only in the feed
If the feed has one GTIN, the product page has another, the product schema has a third, and the internal catalog has no value at all, the business still has a product-data problem. Fix durable product identity upstream, then let feeds, pages, schema, APIs, and channel exports pull from the same trusted record.
Leaving ownership unclear
GTIN problems can involve merchandising, ecommerce, marketplace operations, supply chain, suppliers, engineering, and data teams. Before scaling channels, define who owns missing identifiers, invalid identifiers, variant rules, exemptions, and source-of-truth corrections.
Where Catalog fits with GTINs
Catalog does not issue GTINs, replace GS1, or act as a barcode licensing authority. Merchants still need valid identifiers from the right source and still need to follow each channel's rules.
Catalog fits at the structured product-data layer. It helps teams turn scattered product information into normalized, enriched, machine-readable product objects where identifiers such as GTIN, SKU, MPN, brand, variant ID, and item group ID can sit beside the attributes, media, prices, availability, categories, and relationships that give those identifiers context.
| Layer | Job |
|---|---|
| Identifier source | Assign or provide valid product identifiers such as GTINs, SKUs, MPNs, and variant IDs |
| Source systems | Store product information in ecommerce platforms, supplier files, PIMs, ERPs, DAMs, spreadsheets, websites, and internal databases |
| Catalog | Normalize, enrich, structure, and expose product facts as machine-readable product objects, including identifiers and variant relationships |
| Feed and channel tools | Map records to Google Merchant Center, marketplaces, retailer portals, schema, APIs, search indexes, and other destinations |
| Outputs | Power product pages, product feeds, marketplace listings, product schema, APIs, search, recommendations, and AI-shopping tools |
That distinction matters for merchants and builders. A GTIN helps identify the item. Catalog helps make the rest of the product record understandable enough for software to use.
For adjacent concepts, read the glossary entries for product feeds, data feeds, product schema, structured data, and product catalogs.
For deeper context, read Catalog's guides to product data quality, product data enrichment for AI commerce, and making products show up in ChatGPT.
Related terms
FAQ
What is a GTIN in simple terms?
A GTIN is a globally unique product identifier. It tells retailers, marketplaces, feeds, search systems, and supply chain tools which exact trade item a record describes.
Is a GTIN the same as a UPC?
Not exactly. UPC is a common North American barcode and identifier term. A UPC-A barcode carries a GTIN-12, which is one type of GTIN. GTIN is the broader family that also includes GTIN-8, GTIN-13, and GTIN-14.
Is a GTIN the same as a barcode?
No. The GTIN is the number that identifies the trade item. The barcode is the scannable symbol or data carrier that can encode that number.
How many digits are in a GTIN?
A GTIN can have 8, 12, 13, or 14 digits. The common structures are GTIN-8, GTIN-12, GTIN-13, and GTIN-14.
Does every product need a GTIN?
Many branded and manufactured products have GTINs, and many commerce channels expect valid identifiers when they exist. Some custom, handmade, private-label, replacement, or one-of-a-kind products may follow exemption rules. Always follow the destination's product identifier requirements instead of making up a value.
Does each variant need a different GTIN?
Usually, yes. If a variant is a distinct sellable trade item, such as a different size, color, flavor, count, or packaging level, it usually needs its own GTIN.
Where should a merchant store GTINs?
Store GTINs in the source product-data record as text, then reuse that trusted value in product feeds, product pages, marketplace listings, product schema, APIs, and internal tools.
Can Catalog create GTINs?
No. Catalog does not issue GTINs or replace GS1. Catalog helps merchants and builders structure, enrich, and expose product data so identifiers such as GTINs can be used consistently across feeds, APIs, schema, search, recommendations, and AI-commerce workflows.
