What GS1 Barcode Standards Actually Define, and What to Watch for in Practice - Sorting Out GTIN, AI, GS1-128, and GS1 DataMatrix

A common source of confusion when introducing barcodes is that requests like “we want a JAN code,” “we want GS1-128,” and “we want a QR code” all get discussed at the same level. In reality, you need to separate four things:

1. What you are identifying (the identification key, such as GTIN)
2. What attribute information you want to carry (lot number, expiry date, etc.)
3. Which symbol represents it (the type of barcode)
4. How the system uses it after the scan

GS1 is the international standard that ties these four together.

1. The short answer

1. GTIN and the type of barcode are different things. GTIN is the product identification code. EAN/UPC, GS1-128, and GS1 DataMatrix are just ways of representing a GTIN.
2. GTIN alone is often not enough. If you need lot numbers or expiry dates, you use GS1 Application Identifiers (AIs).
3. Different use cases call for different symbols. POS centers on GTIN, logistics uses GTIN-14 or SSCC, and traceability needs GTIN plus lot, expiry, and serial.
4. Being readable is not the same as being usable. You need to design the scanner settings, how the upper system interprets the data, and the rules for updating your product master.
5. The retail shift to 2D is still in transition. For the time being, you will need both 2D barcodes and the traditional linear barcodes side by side.

2. The layers of GS1

2.1 Identification codes (what you are identifying)

• GTIN-13: Single items or the smallest trade unit. Used as the JAN code in Japan.
• GTIN-14: Aggregated packaging such as cases or cartons.
• SSCC: Logistics identification at the pallet or case level.

2.2 Application Identifiers (AIs)

AIs are 2 to 4 digit numbers that define the meaning and format of the data carried in a barcode.

2.3 Barcode symbols (how it is represented)

• EAN/UPC (JAN symbol): Carries only the GTIN. Aimed at POS.
• ITF: GTIN only. The thicker logistics barcode.
• GS1-128: GTIN plus attribute information. Used for logistics labels (it is not the same as plain Code 128).
• GS1 DataMatrix: Compact and stores a lot of information. Suited to medical devices and small parts.
• GS1 QR Code: A 2D code. Strong for consumer-facing information.

3. Where people get stuck in practice

3.1 Do not casually reuse GTINs

Once a GTIN is used, it cannot be reused. If the size, content quantity, or sales unit of a product changes, you need a new GTIN. Treating GTIN as “an internal code we can reuse once it frees up” will break consistency with your e-commerce site and inventory system.

3.2 Watch the difference between fixed-length and variable-length AIs

• Fixed-length AIs can be directly followed by another AI.
• Variable-length AIs (like lot number) must be followed by FNC1 (a separator).
• In practice, putting fixed-length AIs first and variable-length AIs after them is the most stable.

3.3 FNC1 is a control character, not a literal string

FNC1 is not the text “FNC1” - it is a control character inside the barcode symbol. Treat scanner output and on-screen display as separate things.

3.4 Pay attention to what the scanner returns

Scanners may prepend an identifier indicating the symbol type (for example ]C1 for GS1-128 and ]d2 for GS1 DataMatrix). When you build a verification system, decide up front whether you receive that identifier or strip it.

3.5 Verify print quality in the actual environment

Even if it looks fine on screen, read rates can drop sharply due to:

• Label printer resolution and thermal transfer conditions
• The material of the cardboard or film
• Glossy or curved surfaces
• Unauthorized shrinking or margin trimming during design tweaks

3.6 Do not crowd multiple barcodes together

Placing a POS JAN code right next to a marketing QR code can cause misreads or slow checkout at the register.

4. The order to roll things out

1. Decide the business use case (POS, logistics inspection, or traceability).
2. Decide the identification key (GTIN, GTIN-14, SSCC).
3. Decide the attributes you need (lot, expiry, serial).
4. Decide the symbol (pick the one that fits the use case).
5. Decide the scanner output spec (how to handle identifiers and pass data to the upper system).
6. Decide product master and change rules (numbering, changes, discontinuation).
7. Verify printing on actual goods (real labels, real scanners).
8. Run end-to-end business testing (confirm the operation works, not just that the code reads).

5. Summary

• Treat numbers, attributes, symbols, and processing as separate concerns.
• Start the design from who scans what, where, and what they do with it.
• Barcodes are not done when they read. The goal is that they work in the business.

References: GS1 General Specifications, GS1 Japan Basic Guide, GS1 Application Identifiers