GS1-128 Label

A GS1-128 label is a printed label that carries a GS1-128 barcode symbol (Code 128 symbology governed by GS1 rules) and human-readable fields. It encodes GS1 Application Identifiers (AIs) to structure data such as Global Trade Item Number (GTIN), batch/lot, expiration date, serial number, and the Serial Shipping Container Code (SSCC) for logistics units. FNC1 separators in the symbol delimit variable-length data. The label’s human-readable interpretation (HRI) mirrors the AIs using parentheses for clarity, while the parentheses are not encoded in the barcode data.

In regulated manufacturing, GS1-128 labels are ubiquitous on cases and pallets to support aggregation and shipping, and may appear on secondary packs where space and policy permit. They enable consistent scanning across ERP, MES, WMS, and downstream distributors. The GS1 General Specifications define data syntax, check digit algorithms, and symbol requirements; regulators specify where and how such identifiers must appear for traceability and labeling controls in GMP/GDP contexts.

GS1-128 labels encode data using GS1 Application Identifiers (AIs), which are numeric prefixes that define the meaning, format, and length of each data element. Common examples include: (01) GTIN (fixed length 14), (10) Batch/Lot (variable length), (17) Expiry Date (YYMMDD), (21) Serial Number (variable length), and (00) SSCC (fixed length 18, including extension digit and check). Variable-length AIs must be followed by the FNC1 separator unless they are at the end of the symbol, ensuring unambiguous parsing. Human-readable interpretation prints the AIs in parentheses to aid manual verification.

• Core product identity: (01) GTIN; optional (240) Additional Item ID; (241) Customer Part Number.
• Batch/expiry/serialization: (10) Batch/Lot; (17) Expiration; (21) Serial Number.
• Logistics unit: (00) SSCC for cases/pallets; (37) Count of Trade Items on Logistics Unit.
• Dates and measures: (11) Production Date; (310x) Net Weight; (30) Variable Count.
• Regulatory adjuncts: Combine with 2D symbols where mandated (e.g., package-level 2D DataMatrix for DSCSA/UDI), while GS1-128 commonly serves cases and pallets.

Symbology and print rules are defined by GS1: Code 128 character set, start/stop patterns, check calculation (Modulo 103 at symbol level), quiet zones, and X-dimension selection matched to print process and scanner capability. The GS1 General Specifications also cover HRI placement, minimum bar height, and label placement guidelines for logistics units. MES/WMS systems must validate data format per AI definition and enforce FNC1 use for variable-length data elements. At receipt or during in-process checks, scanners parse the symbol into discrete (AI, value) pairs for system validation and genealogy.

GS1-128 labels are most prevalent on logistics units (cases, pallets) using the SSCC (00). They also appear on secondary packaging or shipper cartons where linear symbols are acceptable and space allows. In pharmaceuticals under DSCSA, packages must bear a product identifier in a 2D DataMatrix; homogeneous cases may carry the identifier in GS1-128 or 2D, while pallets use SSCC-based labels. In medical devices (UDI), the AIDC technology is not prescriptively defined; many labelers use GS1-128 on secondary packaging and GS1 DataMatrix on small primary packs, with HRI UDI text alongside.

Beyond regulated packs, GS1-128 is used internally for WIP totes, kitting containers, and material bins to harmonize scanning across MES and WMS. In cosmetics, food, and cannabis, GS1-128 supports retail/wholesale logistics and recalls with batch/date AI elements, and it enables traceability aggregation to ship units via SSCC. Blood and tissue sectors typically use ISBT-128 rather than GS1-128; cross-sector facilities must segregate schemes to prevent identifier collisions and scanning confusion.

Under cGMP, labeling operations must be procedurally controlled, with verification and reconciliation. The MES should own label templates, AI data mapping, and issuance logic (e.g., serials, SSCCs); control print triggers at defined operation steps; and log each print/reprint with reason codes, operator ID, device ID, and time. Inline or at-line scanning should confirm correctness (e.g., GTIN matches order BOM; lot and expiry match batch record), linking scans to the eBMR/eDHR. Part 11 expectations apply where electronic records and signatures authorize label content, template changes, or reprints.

• Template lifecycle under change control; dual review/approval; version pinning per product/SKU and market.
• Controlled number range management (e.g., SSCC pools), with uniqueness and reuse prevention.
• Two-person verification for critical reprints or template edits; audit-trail with before/after diffs.
• Automated checks: AI format validation, date encoding (YYMMDD), serial length, FNC1 placement.
• Line clearance and label reconciliation steps per 21 CFR 211.130, documented in the batch record.

Printer qualification and routine verification are part of the process validation lifecycle. The MES should also enforce device binding (only approved printers on approved lines for given SKUs) and capture print/scan exceptions as deviations for QA review.

GS1-128 labeling’s reliability depends on clean master data and deterministic number issuance. ISA‑95 delineates responsibilities: Level 4 (ERP) maintains GTIN assignments and customer/market attributes; Level 3 (MES/WMS) executes label printing, manages SSCC pools, and records genealogy; Levels 2/1 (control/shopfloor) perform in-line scans and vision checks. For outbound logistics, WMS associates SSCCs with shipment manifests and publishes EPCIS events for aggregation and shipping, ensuring downstream partners can trust the hierarchy (item→case→pallet).

Event data (commission, pack, aggregate, ship, receive) should be captured contemporaneously and transmitted in near real-time to enterprise repositories. Well-designed interfaces include store-and-forward buffers and reconcile exceptions (e.g., shipment without a corresponding SSCC scan) before release.

Labeling systems are GMP-critical because mislabeling is a severe defect. A risk-based GAMP 5 approach classifies components: commercial label management software and print engines typically fall under configurable software (Category 4), custom drivers or scripts under custom (Category 5). Validation should show traceable requirements→risks→specifications→testing, including negative tests (e.g., invalid AIs, wrong FNC1) and regression coverage for template changes. Part 11 applies to electronic records and e-signatures for template approval and critical reprint authorization, with secure audit trails and time-synchronized system clocks.

• ALCOA+ principles for template content, print logs, and verification results.
• Access control and segregation of duties (author vs approver; operator vs QA).
• Printer qualification (IQ/OQ) and routine verification (e.g., barcode grade checks) with periodic review.
• Disaster recovery/backup for template libraries, number ranges, and print job histories.
• Supplier assessment for label software and printer firmware; change notification monitoring.

Data integrity governance should incorporate periodic audits of numbering uniqueness (SSCC and serials), reconciliation of issued vs. used labels, and cross-checks between MES/WMS and EPCIS repositories. MHRA’s data integrity guidance provides pragmatic controls for audit trails, contemporaneous recording, and review-by-exception.

Before batch or lot release, QA expects objective evidence that the right label content was applied to the right unit, and that defective labels were detected and segregated. In-process control may blend camera-based print quality inspection, 100% barcode verification at critical points, and sample-based destructive challenge tests. Results are linked to eBMR/eDHR, enabling exception-based review (EBR) when controls are robust. For devices, UDI presence/legibility and correct DI/PI parsing must be demonstrated; for pharma and other commodities, AI values must match batch records and disposition.

• Sampling plans defined in SOPs, with tightened inspection on changeovers and first-article prints.
• Formal reconciliation: printed, applied, destroyed, returned-to-stock; investigation triggers for mismatches.
• Label storage and environmental controls for media and ribbons; expiry/requalification of label stocks.
• Changeover line clearance documenting removal of prior-SKU labels and ribbons; verification scans post-changeover.
• Release gating: shipments blocked in WMS until SSCC scans are complete and pass validation.

GS1-128 participates in traceability by encoding batch/lot and, where applicable, serial numbers. Aggregation relates child items (often with 2D DataMatrix on unit packs) to parent cases and pallets identified by SSCC in GS1-128. EPCIS events capture these relationships so trading partners can verify parent-child hierarchies and receive dispositions. For DSCSA, the package identifier is a 2D DataMatrix that carries GTIN/NDC, serial, lot, and expiry; homogeneous cases and logistics units often use GS1-128 with SSCC and may also repeat the product identifier as required by trading partners.

In medical devices, the UDI’s Device Identifier (DI) typically aligns to the GTIN, and Production Identifiers (PI) encode lot, expiry, and serial when required. GS1-128 may carry the UDI in linear form on secondary packs, while GS1 DataMatrix is common on primary packs with space constraints. Across food, cosmetics, and cannabis, batch/expiry in GS1-128 supports recall-readiness and rapid one-up/one-down tracing, while SSCC-based shipping labels allow quick case/pallet quarantine and targeted retrievals.

• Missing FNC1 after variable-length AIs (e.g., (10) lot), causing downstream parse failures; enforce AI schema validation in MES.
• HRI/text content diverges from encoded data; require automated verify-and-compare of scanned data to HRI and master data.
• Wrong date format (encoded YYMMDD vs. printed MM/YY); standardize format rules and perform sample decoding at setup.
• Reused SSCCs due to poor number-range governance; allocate centrally and block reuse until system-defined cool-off horizon is exceeded.
• Quiet-zone, X-dimension, or bar height violations causing scan issues in cold chain or curved surfaces; qualify media and validate against worst-case conditions.
• Template drift after change; use version pinning by SKU/market and require QA e-signature for release with audit-trail review.
• Excessive reprints without investigation; cap reprints, force reason codes, and trigger deviation after threshold breaches.

Operationally, the strongest mitigations are: controlled template libraries, automated verification at point-of-print and point-of-use, strict number management (serials/SSCC), and well-defined reprint and reconciliation SOPs tied to batch records. Integrating MES and WMS reduces handoffs where label data can desynchronize.

V5 Ultimate centralizes GS1-128 labeling in the execution layer: master data (GTINs, AI mappings), validated templates, printer/line binding, SSCC pools, and automated print-verification steps live in MES/eBMR/eDHR. WMS components then aggregate items to cases/pallets and post EPCIS events, while QMS governs template change control and deviation/CAPA on label incidents. Because MES, QMS, eBMR/eDHR, LIMS, WMS, and Maintenance share one record, label content, print evidence, and release decisions are inherently synchronized and reviewable by exception.