GTINGlobal Trade Item Number

A Global Trade Item Number is GS1's globally unique identifier for a specific tradable product configuration. Two products are considered different for GTIN purposes if they differ in any way that the trade or consumer would treat as distinct — pack size, flavour, formulation, count, even regional packaging artwork that carries different regulatory claims.

GTIN is the product key. It does not identify a specific lot, batch, serial, or pallet — those are separate identifiers carried alongside the GTIN. "Cherry-flavour 500 ml bottle" has one GTIN; "cherry-flavour 750 ml bottle" has a different GTIN; "lot 12345 of cherry-flavour 500 ml" is the GTIN plus AI 10 lot code; "serial 0001 of lot 12345" adds AI 21.

The point of a globally unique product identifier is interoperability. When a retailer scans your product at the till, when a distributor receives a pallet of it, when a regulator traces back a recall, and when your own ERP posts a goods receipt, all four systems must agree on what "the product" is. GTIN is the only language all of them speak.

The first product scanned at a supermarket till was a pack of Wrigley's chewing gum at a Marsh Supermarket in Troy, Ohio on 26 June 1974. The number on it was a UPC-A — twelve digits, the original product identifier created by the Uniform Code Council in the US.

Europe followed in 1976 with the EAN — European Article Number — a thirteen-digit superset of UPC. For decades the two coexisted: US POS systems read 12 digits, European ones read 13. In 2005 GS1 (the merged successor of UCC and EAN International) declared the "Sunrise" — every US retailer had to handle 13-digit codes. From that point on, UPC, EAN, ITF and all later variants were unified under one umbrella: the Global Trade Item Number.

Today, GTIN is the foundation of the GS1 system of standards: a product-identifier vocabulary used across roughly 150 countries by more than two million companies. Every retail barcode, every medical-device UDI, every food traceability lot code, every pharmaceutical serialisation scheme, and most EDI transactions traceable through retail and distribution channels resolve back to a GTIN.

All four formats are stored internally as a 14-digit number with leading zeros where necessary. When you persist a GTIN in your database, always store it as the 14-digit "GTIN-14" form. This keeps packaging-level math simple, makes joins between systems trivial, and avoids the entire family of bugs where a 12-digit US UPC and the same product's 14-digit case code refuse to match each other.

A GTIN is made up of four positional parts:

• Indicator digit (GTIN-14 only) — packaging level. 0 = base unit, 1–8 = packaging levels (inner / case / pallet layer), 9 = variable measure.
• Company prefix — assigned by GS1, identifies the brand owner. Length varies (6 to 11 digits depending on the licence).
• Item reference — assigned by the brand owner within their prefix, identifies the specific product.
• Check digit — single digit calculated from the preceding 13 using the standard GS1 mod-10 algorithm.

The company-prefix length is set when GS1 issues your licence. A larger prefix licence (more SKUs you can allocate) leaves a shorter item-reference field, and vice versa. You do not get to choose which digits are yours mid-stream — the boundary between prefix and item reference is fixed by the licence.

The check digit is calculated as follows: starting from the rightmost data digit, multiply odd-positioned digits by 3 and even-positioned digits by 1, sum the products, take that sum modulo 10, and subtract from 10 (or 0 if the result is 10). Most barcode libraries do this automatically; if you are computing it yourself, write a unit test against a known-good GTIN before trusting your code.

GTINs are allocated within a GS1 Company Prefix that GS1 issues to you. You apply through your local GS1 member organisation (GS1 US, GS1 UK, GS1 Germany, and so on). Pricing depends on how many GTINs you need to allocate over the licence term and on the region; small-business single-GTIN allocations are available in most countries for businesses that only ever need one.

Once you hold a prefix, you and only you are authorised to allocate item references within it. The numbers are yours for the life of the licence. They are not yours forever in any abstract sense — if you let the GS1 licence lapse, the prefix may eventually be reallocated — but for any practical timescale, treat them as permanent corporate assets.

GS1's GTIN Allocation Rules answer the question "do I need a new GTIN?" The short version: yes when the product differs in any way that affects trading. New formulation, new size, new flavour, new claim on the label, new packaging material that changes the consumer-facing product, new region with distinct artwork — all typically warrant a new GTIN.

The cost of getting this wrong is severe and one-directional. Allocating an unnecessary GTIN is a paperwork nuisance — you carry an extra row in the master. Re-using a GTIN across two genuinely different products is a recall and chargeback event: retailer EDI breaks, lot traceability collapses, and the wrong product can be picked, shipped, and consumed.

Together, GTIN + lot + serial uniquely identify one specific item of one specific run. This combination is what makes FSMA 204 traceability (food KDEs), DSCSA serialisation (US pharma), EU MDR UDI-DI/UDI-PI (medical devices), and EU FMD (anti-counterfeit pharma) all possible on top of the same GS1 base.

On a barcode, these are concatenated using Application Identifiers (AIs). A GS1-128 case label might read (01)10012345678905(10)ABC123(17)270101(21)SN0001 — case GTIN, lot ABC123, best-before 01 Jan 2027, serial 0001. The parentheses are human-readable only; the symbology itself uses FNC1 separators.

Most regulated products travel through commerce in nested packs: consumer unit inside an inner, inside a case, on a layer, on a pallet. Each level of trade item gets its own GTIN. The indicator digit in GTIN-14 conveys which level you are looking at.

There is no global standard mapping of indicator digit to packaging level — the brand owner assigns them. What matters is that you publish the mapping to your trading partners and stay consistent. If indicator 2 means "case of 12" for one of your SKUs, do not let it mean "case of 24" for the next one.

GS1 Digital Link is the modern way to publish a GTIN on a pack. Instead of a UPC/EAN linear barcode that only encodes the number, you publish a URL such as https://id.gs1.org/01/00012345678905 in a QR code or DataMatrix. Scanning it with a phone takes the consumer to a brand page; scanning it at the till still resolves the GTIN at the start of the path.

This is the direction of travel: by the late 2020s the major retailers expect 2D codes (Sunrise 2027) to replace UPC/EAN at point of sale globally. The GTIN does not change — only the carrier and the extra payload (lot, expiry, serial) it can hold.

• FDA UDI (medical devices, 21 CFR 801 Subpart B) — UDI-DI (device identifier) is a GTIN; UDI-PI (production identifier) carries lot + expiry + serial.
• EU MDR / IVDR UDI — same dual structure, EUDAMED-registered.
• DSCSA (US pharma serialisation) — GTIN + serial + lot + expiry encoded in DataMatrix on every saleable unit and homogeneous case.
• EU FMD — pharma unit identifier built on GTIN.
• FSMA 204 (US food traceability) — GTIN + lot are mandatory KDEs for every covered Food Traceability List item from harvest through retail.
• Tobacco TPD2 (EU) — every unit pack carries a unique identifier registered against the manufacturer's GTIN list.

What every one of these has in common: they extend GS1 GTIN with a lot, a serial, and an expiry, and they require you to be able to trace any unit back to the run that made it. If your master data is sound at the GTIN level, every one of these overlays is achievable. If your GTIN data is messy, no amount of serialisation software will save you.

• Reusing a GTIN for a reformulated product — breaks every downstream traceability link and triggers retailer chargebacks.
• Sharing GTINs across regions when packaging differs — retailers reject; allergen/claims mismatches can become recalls.
• Allocating GTINs from an unowned company prefix — you do not own those numbers; collisions are inevitable.
• Storing GTIN as an integer in the database — leading zeros stripped; joins silently fail.
• Storing UPC-12 as separate from GTIN-14 internally — same GTIN, different display, two records refusing to reconcile.
• Recalculating the check digit on print and getting the GTIN-14 indicator-digit weighting wrong.
• Not retiring an old GTIN before allocating a new one for a major change — old stock and new stock both in distribution under different GTINs with no version flag.
• Treating variable-measure GTINs (indicator 9) like fixed-measure — the AI 310x weight matters and POS will scan it.
• Letting marketing assign new GTINs in a spreadsheet without IT review — duplicates, gaps, and prefix mistakes follow.

• GTIN identifies the product (the SKU), not the unit or the lot.
• Store as 14 digits, always, including leading zeros.
• Check digit is mandatory and recalculable — never strip it.
• Allocate a new GTIN whenever the trade item materially changes.
• Lot (AI 10), serial (AI 21), expiry (AI 17), SSCC (AI 00) all sit alongside GTIN — they are not substitutes for it.
• Every retail regulatory overlay — UDI, DSCSA, FSMA 204, FMD — extends GTIN; it does not replace it.