GS1-128

GS1-128 is a barcode standard, not a barcode symbology. It uses Code 128 as the underlying symbology (the way bars and spaces encode characters) and adds two things: the GS1 Application Identifier (AI) structure that gives meaning to each field, and a special FNC1 function character placed immediately after the start character to mark the symbol as GS1-encoded.

Each AI is a 2-, 3- or 4-digit prefix that tells the scanner what the next field means: AI 01 is GTIN (product), AI 10 is batch/lot, AI 17 is expiry, AI 21 is serial, AI 37 is unit count, AI 00 is the SSCC pallet ID, AI 422 is country of origin, AI 400 is customer PO. A single GS1-128 symbol can concatenate multiple AIs, with FNC1 used as the field separator after any variable-length AI.

The result is a self-describing label: a single scan returns a structured object {gtin, lot, expiryDate, quantity, sscc, ...} that downstream systems can consume without bespoke parsing. Compare that to plain Code 128, which is just a string the receiving system has to parse with custom logic and which breaks every time a supplier changes their label format.

Every GS1-128 barcode is a Code 128 barcode — but the reverse is not true. The distinction matters because mis-printed 'GS1-128' barcodes that are actually plain Code 128 are one of the most common reasons receiving systems reject pallets.

• Code 128 is the underlying symbology (ISO/IEC 15417) — bars and spaces that encode characters.
• GS1-128 adds the AI structure plus FNC1 in the first position after the start character, telling the scanner 'this is GS1-encoded.'
• FNC1 is also used as the field separator after a variable-length AI (e.g. AI 10 lot must be terminated by FNC1 if any other AI follows in the same symbol).
• A GS1-128-aware scanner transmits the AIM identifier ]C1 in front of the data so your software can detect GS1 encoding and split into fields automatically.
• A scanner reading a Code 128 that lacks FNC1 transmits ]C0 — your software then has no structural way to know which characters mean what.

The GS1 AI directory has hundreds of entries. The operating subset for regulated inventory is small — the table below covers ~95% of real-world GS1-128 labels.

A license plate is a single inventory identifier — usually a pallet or a tote — that carries every fact downstream systems need. Without license plates, every move requires re-entry of lot/expiry/quantity. With them, one scan tells the WMS exactly what is on the pallet and where it should go.

GS1-128 is the format because it is universally readable, self-describing, and the SSCC (AI 00) makes the license plate globally unique across firms (so the receiver's WMS recognises the same pallet your shipper created). The typical logistic label carries:

• SSCC on its own (AI 00) — large, top of the label, the dominant scan target.
• Content GS1-128 underneath (AI 01 GTIN + AI 10 batch + AI 17 expiry + AI 37 count) — one scan returns the structured content of the pallet.
• Human-readable text alongside every barcode so the operator can verify without a scanner.
• Optional GS1 DataMatrix as a 2D backup when the label has space constraints or when receivers prefer 2D imaging.

The decision rule we use: linear GS1-128 for case + pallet (logistic units) because the laser scanners at most receiving docks read it fastest and the label has room. GS1 DataMatrix at unit level (carton, vial, device) because the payload is larger (serial + lot + GTIN + expiry in DSCSA / FMD) and the unit is too small for a linear barcode. The two coexist on the same regulated product.

A GS1-128 barcode that is structurally correct but physically poor (low contrast, ink-spread, edge damage, missing quiet zone) will be rejected downstream. ISO/IEC 15416 defines a grade scale from A (best) through F (fail) based on seven measured parameters: decode, symbol contrast, minimum reflectance, minimum edge contrast, modulation, defects, and decodability. Most retailer and pharma receiving standards require grade C (2.5 / 4.0) or better; some retailer programmes (Walmart, Tesco) require grade B.

• Decode — does a reference algorithm successfully decode the symbol? Pass/fail.
• Symbol contrast — difference between the lightest and darkest reflectance values; thermal-transfer ribbon quality is the usual driver.
• Modulation — relative reflectance of weakest bar/space vs strongest; degrades with worn print heads.
• Defects — voids in bars and spots in spaces; common with worn print heads or contaminated media.
• Quiet zone — required clear space on each side of the symbol (10× narrow element width for GS1-128); commonly violated when labels are designed too tight.

1. GS1 company prefix configured at tenant level — V5 refuses to print a GTIN or SSCC outside the allocated prefix.
2. Per-label template configured per use case (receiving license plate / pallet logistic label / case label / unit label) with the AIs needed for that label, FNC1 placement validated at template-save time.
3. Print agent (tools/print-agent) writes ZPL to ZPL-II / Zebra / Datamax printers with FNC1 emitted correctly; preview rendered in-browser so the operator can verify before print.
4. Scan-side parser ingests both ]C1 (GS1-encoded) and ]C0 (plain Code 128) — for ]C0 incoming we attempt a best-effort parse and log a supplier-label-quality finding so we can chase the supplier; for ]C1 we get the structured object directly.
5. License-plate inventory uses SSCC (AI 00) as the primary identifier through goods-in → putaway → dispense → pack → ship; one scan at each step returns GTIN + lot + expiry + count.
6. Outbound EDI 856 ASN auto-generated with SSCC references that match the printed logistic labels — receiver reconciles the pallet in one scan at their dock.
7. Print-quality verifier integration (optional Honeywell / Cognex / Microscan / Axicon verifier) — grade trended per print head per shift, declining grade auto-opens a maintenance task.
8. Mobile-safe label preview at ≤390px CSS width — the operator on iPhone sees the same label preview as on a 24-inch screen, no horizontal scroll.

1. FNC1 missing in the first position — barcode scans as plain Code 128 (]C0); downstream parsers reject or mis-parse.
2. Variable-length AI not terminated by FNC1 — AI 10 lot followed by AI 17 expiry without separator; AI 10 absorbs the next field's digits and you get garbage.
3. Date AI in wrong format — YYYY-MM-DD or MM/DD/YY instead of YYMMDD; symbol structurally invalid.
4. Print quality below grade C — scans on the verifier in QA but fails at the retailer's dock; chargeback.
5. Custom in-house AI ranges — non-standard AIs break interoperability with every external partner.
6. Issuing a GTIN you don't own — the GTIN must be allocated from your GS1 company prefix; using a number outside your prefix invalidates the label and is in some jurisdictions actionable.
7. Re-using an SSCC within 10 years — violates GS1 General Specifications; receiver's WMS treats your pallet as a duplicate of a historical pallet.
8. Missing or violated quiet zone — label designed too tight; symbol decodes inconsistently across reading angles.

• Inbound from any major food, pharma or supplement supplier — receiving scans the GS1-128 on the pallet; SSCC reconciles to the EDI 856 ASN.
• WMS license plates — one barcode per pallet through the entire warehouse lifecycle from goods-in to ship.
• Pharma case-level — DSCSA in US, FMD in EU. Unit-level rides on GS1 DataMatrix; case-level on GS1-128.
• Retail and grocery outbound — SSCC on every pallet, matched to EDI 856 ASN. Walmart / Tesco / Carrefour / Ahold-Delhaize compliance programmes are GS1-128-based.
• FSMA 204 traceability — Traceability Lot Code, lot, quantity, production date carried on the GS1-128 logistic label.
• ISO 22005 food traceability and BRCGS Issue 9 — GS1-128 is the practical implementation of the identification + lot capture clauses.