GS1‑128 Case Label – Structured Barcode for Logistics

This topic is part of the SG Systems Global regulatory & operations glossary.

Updated October 2025 • GS1 Barcoding, SSCC, AI Data, Case/Pallet Labeling • ERP, WMS, MES, QA/RA, Food & CPG

The GS1‑128 case label is a standards‑based logistics label that uses Code 128 with Application Identifiers (AIs) to carry structured product and shipment data. Everyone recognizes its value for outbound freight, ASNs, and pallet building—but the same label is far more powerful inside your four walls. Consider a protein processor purchasing cases of cured ham. Each case arrives with a GS1‑128 label encoding SSCC (AI 00), GTIN (AI 01), Lot/Batch (AI 10), expiry (AI 17), and often catch‑weight (AI 310n). Those AIs are scanned once at Goods Receipt, then propagated through WMS put‑away, directed picking, decasing into identity‑preserving bins, and ultimately into a sandwich line where consumption is recorded to an electronic BMR/MBR. The result is end‑to‑end lot genealogy from supplier case SSCCs to finished sandwich GTINs.

“Treat the GS1‑128 on every case as your plant’s passport—scan once, propagate everywhere, and never break the chain of identity.”

1) What a GS1‑128 Case Label Covers—and What It Does Not

Covers: logistics and material identity at the case level: AI (00) for the SSCC (unique case identifier), AI (01) for the case‑level GTIN, AI (10) for Lot/Batch, AI (17) for expiry, AI (15) for best‑before, AI (37) for case count, and weight AIs such as AI (310n/315n) for catch‑weight proteins scanned into Quarantine/Hold until Component Release. The label is meant to be decoded by scanners and consumed by WMS, MES, and eBMR systems as a single source of identity throughout inbound, storage, production, and shipping.

Does not cover: consumer unit serialization (often 2D codes or AI 21 at unit/carton), pallet‑level labels (which carry their own SSCCs), or regulated device identifiers like UDI that coexist with GS1 keys. GS1‑128 also doesn’t replace recipe documents (MBR/BMR) or SOPs; rather, it feeds them with verified identity.

2) Legal, System, and Data Integrity Anchors

Once scanned into electronic systems, GS1‑128 data forms part of the data integrity record set. For regulated sites, controls must satisfy 21 CFR Part 11, EU Annex 11, and CSV expectations with audit trails, role‑based access, and document control over label templates, parsing logic, and master data. In food, AI (10) and AI (17) feed HACCP, allergen control, and recall readiness. In cosmetics and OTC, labels must align with ISO 22716 and MoCRA requirements on material traceability and labeling claims. Suppliers should be managed via SQM, Vendor Qualification, and—if needed—SCAR workflows when labels fail verification.

3) The Evidence Pack for GS1‑128 Control

A robust “GS1‑128 pack” lets you prove that labels are specified, printed, scanned, and retained correctly:

• Label specifications listing required AIs by packaging level, X‑dimension, bar height, quiet zones, HRI formatting, and placement tolerances; controlled under Document Control with revision history and approvals.
• Template governance for artwork and data mapping (ERP → label), integrated with Labeling Control and Change Control.
• Verification logs showing label verification/barcode validation results, symbol grades, and corrective actions.
• System interfaces documenting AI parsing in WMS/MES, EDI ASN mappings, and EPCIS events.
• Traceability proofs linking receipt scans to bin identities, weigh/dispense records, and finished goods in the eBMR/PQR.
• Retention plan per Record Retention & Archival, including label images, raw decode strings, and device IDs.
• Training & access records under Training Matrix and UAM.

Auditors should be able to begin with a finished lot and, within minutes, view the list of supplier SSCCs, lots, expiry dates, and verification grades scanned at receipt—no spreadsheet stitching required.

4) From Supplier Dock to Finished Sandwich—A Standard Path

1) Goods Receipt. On arrival, the ham cases are scanned at the dock. The system validates AI (00)/(01)/(10)/(17)/(310n) per the PO and supplier spec. Inventory is created into Quarantine/Hold pending Component Release, with cold‑chain notes feeding Temperature Mapping and Environmental Monitoring logs.

2) Put‑Away & Storage. Location assignment follows FEFO rules; allergen zoning is enforced via bin/zone topology. The SSCC remains the master key for the case; counts/weights follow AIs, and status is visible to Production Scheduling and OEE planners.

3) Kitting & Decasing. When a sandwich order drops, directed picking pulls the earliest‑expiry cases. At decasing, the SSCC is scanned again, and identity is copied into multiple traceable bins with the same GTIN, lot, and expiry. If the site practices zone picking, each zone validates the lot before release to the line.

4) Weigh/Dispense & Line Execution. Operators scan the bin at a weigh/dispense station. Actual use is captured by gravimetric weighing, with tare verified via tare weight. For bulk ingredients (bread, sauces), macro dosing applies; for seasonings or allergens, use micro‑ingredient dosing. The eBMR line records GTIN/lot/expiry from the scan, not from an operator’s memory.

5) Quality & Compliance Checks. In‑process controls (IPC) verify that only approved lots are used per Master Recipes and Recipe Versioning. Deviations, if any, are logged and dispositioned through Deviation/CAPA.

6) Pack & Ship. Finished sandwiches inherit the ham lot(s) and receive their own GTINs and dates. Cases of sandwiches are labeled with new SSCCs and GS1‑128s, and outbound events flow to trading partners via EDI ASNs and EPCIS.

7) Recall & Audit Readiness. If a supplier later recalls a ham lot, QA filters all finished sandwich lots that consumed that lot in the affected window and places Hold on inventory. The drill is measured against recall readiness KPIs and reviewed in the PQR.

5) Designing the Case Label—A Practical Method

Begin with a minimal, compliant set of AIs, then add the ones that make internal control easier:

• Required logistics key: AI (00) SSCC for the unique case ID—critical for dock‑to‑stock and Pack & Ship.
• Item identity: AI (01) GTIN (case‑level) with HRI text; never substitute the unit GTIN.
• Traceability: AI (10) Lot/Batch and AI (17) expiry (or AI (15) best‑before) for upstream traceability and FEFO.
• Quantity: AI (37) case count or AI (310n/315n) net weight for catch‑weight protein; helpful for backflush accounting accuracy.
• Optionals: supplier GLN in HRI, storage condition text, and a supplemental 2D (if a customer spec requires) while retaining GS1‑128 as the logistics primary.

Use FNC1 separators for variable‑length AIs (e.g., AI 10) so verifiers and handhelds decode consistently. Keep eye‑level placement and quiet zones per spec to support high‑speed scanning in machine vision tunnels.

6) Master Data—AIs, GTINs, UOM & Print Templates

Identity is master‑data driven. Maintain a packaging hierarchy with correct GTINs for unit/inner/case in ERP, with explicit UOM conversions, and rules for which AIs appear at each level. Tie label templates to the item master and lock them under Document Control. If you manage origin statements, track COO/COI as attributes so the HRI text matches system truth. For conversion and label claims (mass↔volume), govern factors through Recipe Scaling & Basis and avoid spreadsheet “side logic.”

7) Data Integrity—Make Scan ≡ Master

Preserve raw and parsed data for every scan: the full barcode string, field values, device ID, operator, time, and location. Stamp changes to parsing rules in the audit trail. Guard access via UAM and train operators under a formal training matrix. At decasing, generate child IDs (bins) that inherit GTIN/lot/expiry and keep a parent‑child relationship to the SSCC for lot genealogy. Do not let printers “invent” AIs on the fly—values must come from MES/WMS or trusted supplier events.

8) Sampling, Verification & Cross‑Checks

Layer your controls to intercept issues early:

• Decode checks on receipt (are required AIs present and valid against the PO and supplier spec?).
• Print quality verification per shift/lot using your verifier; block receipt if grades fall below action limits.
• Cross‑checks vs. laboratory tests (protein % or moisture) and physical weight checks for AI 310n accuracy.
• Exception handling via Deviation/CAPA, with inventory staying on Hold until resolved.

For internal labels, qualify print engines and scanning cameras like any other measurement device; treat mis‑reads as potential data integrity signals.

9) Equipment Status—Printers, Scanners & Verifiers

Keep all identity equipment in a validated, calibrated state: install/operate/perform under IQ/OQ/PQ, maintain calibration status, and capture device IDs with each scan/verification. If symbol grades fall, initiate RCA and consider TPM to prevent recurrence. Integrate printers into your OEE model; poor label quality causes downstream idle time in picking and shipping.

10) Labels, Claims & Conversion Logic

If labels display net contents or claims, align them with measured reality and conversion rules governed in the MBR/MMR. Tare variability and density factors must be version‑controlled; see Tare Weight and Recipe Scaling & Basis. For net‑content compliance, integrate SPC and control limits; when printing consumer weights from case/batch data, guardband per TNE and monitor Cp/Cpk.

11) Warehouse Status & Logistics Units

Treat the SSCC as the case’s “license plate.” Enforce status transitions (Hold → Released) and location scans at every move. For dock‑to‑stock speed, use zone picking and dynamic lot allocation, honoring FEFO rules. At shipping, generate new SSCCs for outbound cases/pallets and publish matching AI content in EDI/EPCIS so partners can reconcile quickly.

12) GS1‑128 in Daily Control—Identity That Flows

“Scan or stop” should be the rule. Job release is blocked if material identity is missing; digital travelers require a valid bin scan before the step proceeds; SPC charts monitor weight claims where relevant; Hold/Release is automated based on scan‑derived status. Supervisors review exceptions in Internal Audits, and improvements are captured via Kaizen/visual controls. The bottom line: a readable label and a disciplined scan are cheaper than any after‑the‑fact investigation.

13) Metrics That Demonstrate Control

• Receipt Decode Pass Rate by supplier/SKU (AIs present, correct, and verified).
• Label Grade (ISO/IEC 15416) by printer/line and reprint rate.
• Identity Exceptions (GTIN mismatch, invalid lot/date) caught pre put‑away; CAPA closure time.
• Traceability Latency (time from finished lot → supplier SSCC list) and recall drill coverage.
• Catch‑Weight Variance at receipt (AI 310n vs. actual) tied to weighing status.
• Scan Compliance at decasing and dispense (no scan, no consume).
• ASN/EPCIS Match Rate (outbound AIs match what was shipped) and dock‑to‑stock lead time.
• Audit Findings related to data integrity/audit trail for labels (target: zero criticals).

These connect label quality to speed, risk, and cost—from the receiving bay to the last mile of traceability.

14) Common Pitfalls & How to Avoid Them

• “Logistics‑only” mindset. Don’t stop at shipping—use GS1‑128 for decasing/bin identity and eBMR.
• Missing SSCCs on cases. Require AI (00) from suppliers or assign at receipt; otherwise recall readiness slows dramatically.
• Wrong packaging‑level GTIN. Enforce the case GTIN; unit GTINs on cases break WMS rules.
• Free‑text drift. HRI text must mirror encoded AIs; govern via Labeling Control.
• Printer‑side scripting. Printers should render, not decide; source values from validated systems with CSV.
• Untracked decasing. Splitting a case into multiple bins without batch‑to‑bin breaks geneaology.
• No verification. Without label verification, poor grades silently create scan failures and NCRs.
• Poor training. Use a formal training matrix so “scan or stop” is cultural, not optional.

15) What Belongs in the GS1‑128 Label Dossier

Include: AI policy by level; supplier versus internal specs; artwork and template versions; verifier requirements and acceptance limits; test labels and expected parses; EDI/EPCIS mappings; receiving/decasing/dispense SOPs; audit trails for parsing and template changes; retention rules; and references into QC Release, Hold/Release, and recall procedures. Link the dossier to your VMP and CPV where label data feeds ongoing verification.

16) How This Fits with V5 by SG Systems Global

Identity as Master Data. In the V5 platform, AI mappings (00/01/10/15/17/37/310n) are versioned, approved, and effective‑dated. The GTIN hierarchy and UOM rules are centralized, while templates are governed under Document Control with audit trails.

Execution & Interlocks. V5 Receiving won’t post without valid SSCC/GTIN/lot/date. Decasing creates identity‑preserving bins. The MES enforces “scan‑to‑consume” at weigh/dispense; eBMR lines inherit GTIN/lot/expiry automatically. If a supplier lot later fails, V5 instantly finds affected WIP/FG and can Hold them.

Printing, ASN & EPCIS. V5 prints outbound GS1‑128 labels with new SSCCs and publishes matching AIs in EDI ASN and EPCIS events. Dashboards track decode pass rate, label grades, recall latency, and OEE impacts.

Bottom line: V5 turns GS1‑128 into a plant‑wide identity backbone—from dock to sandwich line to shipping—delivering faster receiving, cleaner eBMRs, and traceability you can prove in minutes.

17) FAQ

Q1. Is GS1‑128 only for outbound shipping?
No. Use it internally for receiving, picking, decasing, weigh/dispense, and eBMR traceability. Scanning once at the dock and propagating AIs through bins and batch records preserves identity from ingredient to finished lot.

Q2. What’s the difference between SSCC (AI 00) and GTIN (AI 01)?
GTIN identifies what the item is; SSCC identifies which logistics unit (this specific case). Most processes need both: GTIN for item governance and SSCC for unique case tracking and recall precision.

Q3. Our supplier’s case label lacks SSCC—can we still trace?
You can print an internal SSCC at receipt, but first capture the original label image and AIs. Request suppliers to add AI (00); case‑level uniqueness improves recall readiness and dock‑to‑stock speed.

Q4. How do we handle catch‑weight meats on GS1‑128?
Include AI 310n (net weight) on the case; verify at receipt against a calibrated scale under IQ/OQ/PQ/calibration. Track consumption by mass in MES so finished items inherit the correct lot and costing.

Q5. Should we add 2D codes if we already have GS1‑128?
You may add GS1 DataMatrix/GS1 QR for dense data or presentation scanning, but retain GS1‑128 as the logistics primary for cases/pallets unless a customer specification demands otherwise. Keep both under Labeling Control.

Q6. How does GS1‑128 link to our BMR/MBR?
Scans at weigh/dispense write GTIN/lot/expiry to the eBMR line. Finished lots inherit source lots for genealogy and PQR reviews. Control this under the MBR.

Q7. Where should the label be placed on the case?
Follow your spec for sides/ends, height, and quiet zones to support machine vision and manual scanning. Validate readability at the intended conveyor speed and environmental conditions (condensation, shrink film).

Q8. Do we need EPCIS if we already send ASNs?
EPCIS complements ASNs with event‑level traceability (e.g., which SSCCs were packed, shipped, received). If your customers require rapid, itemized reconciliation or regulatory lineage, EPCIS is worth implementing.

Related Reading
• GS1 Identity: GTIN | Lot/Batch (AI 10) | Application Identifier (AI) | SSCC | EPCIS
• Systems & Records: WMS | MES | eBMR | MBR | BMR | Record Retention | Data Integrity | Audit Trail
• Labeling & Control: Label Verification | Barcode Validation | Labeling Control | Pack & Ship | Recall Readiness
• Operations: Goods Receipt | Directed Picking | Zone Picking | Dynamic Lot Allocation | Weigh & Dispense | Gravimetric Weighing | Batch‑to‑Bin Traceability
• Quality & Validation: QC Release | Deviation/NC | CAPA | IQ/OQ/PQ | Calibration Status | VMP | CPV