GS1-128 Label

A GS1-128 label is a barcode label that encodes one or more GS1 Application Identifiers (AIs) in the Code 128 symbology, allowing consistent capture of product and logistics data worldwide. It can carry the GTIN for a trade item, batch or lot number, expiration date, serial number, and additional attributes such as quantity or weight. Because the data format is standardized by GS1, trading partners and regulators can interpret it unambiguously.

The term "GS1-128" refers to a rules-based data format built on the Code 128 barcode. It is not a separate barcode type. Code 128 provides the encoding mechanics and check character, while the GS1 data structure leverages an FNC1 control character and specific AI prefixes to mark each data element. Human-readable text often shows AIs in parentheses to aid operators, but the parentheses are not encoded.

In practice, GS1-128 labels appear on saleable units, inner packs, shipping cases, and pallets. At item and case levels, typical AIs include (01) GTIN, (10) batch/lot, (17) expiration date, and when required, (21) serial number. At pallet level, the label usually carries the Serial Shipping Container Code (SSCC) using AI (00), which uniquely identifies the logistics unit and links physical movement to digital records, work orders, and the shipping label.

GS1-128 labels support compliance with packaging and labeling controls in GMP and device quality regulations. In the United States, 21 CFR 211.130 requires procedures to ensure correct labels and labeling are used and reconciled for drug products. Device labeling controls are addressed in the Quality System Regulation, and electronic records and signatures associated with label template control and print histories are subject to 21 CFR Part 11 expectations. These controls ensure identity, strength, quality, and traceability are preserved from packaging through distribution.

Supply chain requirements further shape the use of GS1-128. The Drug Supply Chain Security Act (DSCSA) sets end-to-end traceability and product identifier expectations for prescription drugs in the United States, driving standardized encoding of GTIN, serial number, lot, and expiration. In the European Union, safety features and traceability expectations under Directive 2011/62/EU and related acts, along with GDP principles, reinforce robust identification and distribution practices. For medical devices, the FDA UDI Rule and the EU MDR 2017/745 establish UDI carriers and data content; GS1-128 is an accepted linear carrier where appropriate form factor and scanning distance warrant it.

Technically, the barcode is governed by international standards. Code 128 encoding is defined by ISO/IEC 15417, while print quality verification follows ISO/IEC 15416. GS1 General Specifications prescribe the AI catalog, data sequences, FNC1 usage, symbol sizing, and quiet zones. These references are widely cited by manufacturers, distributors, and auditors in developing and assessing compliant labeling systems.

Implementers should align SOPs to recognized sources: FDA guidance portals for drugs and devices, the Electronic Code of Federal Regulations for binding text, EudraLex volumes for EU rules, and GS1 publications for application guidance. Cross-referencing internal validation protocols to these norms reduces regulatory risk and clarifies acceptance criteria for labels at receipt, issue, and release.

For foundational references and program alignment, see 21 CFR 211 for drug CGMP labeling controls and 21 CFR Part 11 for electronic records associated with label lifecycle management. Device manufacturers should also map device labeling procedures to 21 CFR 820 expectations.

GS1-128 labels are used across finished pharmaceuticals, biologics, medical devices, in vitro diagnostics, dietary supplements, ingredients, and broad consumer and industrial sectors. The unifying purpose is reliable, scan-based identification that supports release, pick/pack/ship, receiving, and investigation workflows. Whether the product is regulated as a drug, a device, or food, the encoded GS1 AIs provide machine-readable context that aligns physical materials with master data, documents, and system transactions.

At manufacturing sites, GS1-128 labels help close the loop between batch records, label issuance, and reconciliation. In warehouses and distribution centers, they serve as the primary scan target to trigger location moves, status changes, and shipment confirmations. In wholesale and retail channels, they enable order fulfillment accuracy and reverse logistics. Because the GS1 data model is consistent, scan events can be consumed by enterprise systems regardless of the brand of scanner, printer, or warehouse software.

Regulated distribution adds expectations on custody and environmental control. EU GDP and national guidance emphasize identity verification during receipt and dispatch, temperature-managed handling, and documented traceability. GS1-128 helps satisfy these expectations by carrying product identifiers, lot, and expiration in a widely scannable linear barcode, supporting exception handling and recall readiness.

Operationally, label content must be coordinated with warehouse and transportation systems. Stock rotation, ship confirmations, and proof-of-delivery events often depend on scan accuracy at dock doors and on routes. For many operations, the GS1-128 case label becomes the canonical identifier for carton-level movements, while the SSCC pallet label provides the link to the logistics unit. Successful deployments document the data ownership model and visualization across WMS, ERP, and carrier platforms to avoid conflicting identifiers and scanning friction.

For logistics execution alignment, see EU and national GDP considerations in EU GDP and how scan points are orchestrated inside a WMS.

GS1-128 relies on the GS1 Application Identifier catalog to mark each data element. Fixed-length AIs, such as (01) GTIN and (17) expiration date, have defined lengths and formats. Variable-length AIs, like (10) batch/lot and (21) serial number, are terminated by either the end of the symbol or a Function 1 character (FNC1) when followed by another AI. Parentheses around AIs are for human readability only and must not be encoded.

Typical trade item labels include (01) GTIN, (10) batch/lot, and (17) expiration date, and when applicable (21) serial number for item-level serialization. Case labels often repeat the item GTIN and batch data and may include (37) count to indicate the number of units inside. Pallet labels usually feature the SSCC using (00), a unique 18-digit identifier that binds the physical pallet to shipment documentation and receiving transactions. Weight- or measure-based items may add (310n) net weight in kilograms with n decimal places.

The combination and order of AIs is governed by GS1 rules and trading partner requirements. Internal SOPs should define which AIs are mandatory by packaging level, how data are sourced from master data and batch records, and who is authorized to approve and release labels for use. Always test that scanners correctly parse variable-length fields, particularly when multiple variable-length AIs appear consecutively.

Code 128 supports three character sets and uses a modulo-103 check character to guard against read errors. GS1-128 adds the FNC1 control character after the start code to signal that the symbol contains GS1 data. For any variable-length AI followed by another AI, a separator (encoded as FNC1, often rendered as the Group Separator control) must be included to delimit fields so that scanners do not annex trailing data to the prior element.

Symbol sizing must respect the X-dimension, bar height, and quiet zones defined in GS1 Specifications so that ambient, handheld, and conveyor-mounted scanners can read the code reliably. Print contrast, edge acuity, and bar uniformity directly affect scan rates. Print quality should be verified using ISO/IEC 15416 methodologies, with acceptance criteria agreed with trading partners. Many buyers require a minimum grade (for example, C/1.5/660) on inbound labels; verification reports should be retained to support deviation investigations.

Environmental factors degrade labels over time. Choose substrates and ribbons or toner that withstand expected abrasion, condensation, UV exposure, and low-temperature conditions. Validate that labels remain scannable on curved, flexible, or frosted packaging. Where space is constrained or very dense data are required, consider whether a 2D symbol is specified by the applicable program; otherwise, ensure linear symbol height and magnification meet the scanning distance and depth-of-field needs at each station.

Robust GS1-128 programs start with controlled label design. Templates should be versioned, approved, and managed under document control with clear ownership of static text, AI placement, and data sources. Change control must ensure that any modification to AI content, order, or formatting is reviewed for downstream impact on scanning, ERP integrations, and regulatory submissions. Electronic approval, access control, and audit trails strengthen evidence that only released templates are in use.

Printing must be governed by procedures that restrict who can print, what can be printed, and from which data sets. Scan-enabled print stations should verify the encoded data against work order, batch, and master data before labels enter production. Line clearance and reconciliation activities at start-up and close-out should document counts of issued, used, and destroyed labels. Where feasible, automated vision or verify-on-print steps prevent unreadable or wrong-code labels from reaching product.

Operational controls also extend to how labels are consumed in warehousing and shipping. Work instructions should define the scan target hierarchy, for example, SSCC at pallet moves and GTIN-lot at case picks. Exceptions such as partial cases, rework, and relabeling need explicit flows to prevent identity loss. Integration with inventory systems ensures that each scan updates quantity, location, and status with minimal operator burden and clear traceability.

Build your SOPs around clear acceptance criteria: which AIs are mandatory per packaging level, the minimum verification grade, permissible magnifications, and reprint thresholds. Risk assessments should consider mislabeling impacts, and validation protocols should emulate worst-case substrates, temperatures, and production speeds.

• Define mandatory AIs by level (unit, case, pallet) and data sources for each field.
• Version-control templates with formal approval and electronic audit trails.
• Gate printing behind order context and real-time data checks, with scan-back verification.
• Verify print quality to ISO/IEC 15416 and retain reports for investigations.
• Reconcile issued, used, and destroyed labels at batch and shift close-out.
• Train operators on scan hierarchy, exception handling, and rework labeling.

For execution support and governance capabilities, see tooling for label design, line-side scanning at a scan-pack station in WMS, and template and record controls aligned to 21 CFR Part 11.

When serialization is required, GS1-128 commonly carries the product identifier (GTIN, AI 01) with the serial number (AI 21), along with lot (AI 10) and expiration (AI 17). This enables unique identification at the package level and supports saleable returns verification and suspect product investigations. The label content must match the commissioning records so that any scan is traceable to the authoritative event history.

Aggregation links serialized children to parent cases and pallets, creating a digital hierarchy that mirrors the physical pack-out. Case and pallet labels then become scan targets for inventory movements and shipping, avoiding the need to scan each child unit. These hierarchies are often communicated and reconciled through event-sharing standards so that receiving parties can confirm content and status without opening containers.

At minimum, design your system so that each scan at packaging, warehousing, and shipment reliably updates the event trail and inventory state. Rework and de-aggregation must be captured with the same rigor, ensuring that previously shipped or destroyed identifiers cannot re-enter commerce. Robust exception handling and alerts reduce the risk of orphaned serials or broken aggregation trees.

For U.S. drug distribution, align labeling and events with the DSCSA product identifier and enhanced tracing requirements. For inter-company sharing and auditability, plan your event model around EPCIS events so that scan data can be exchanged and verified end to end.

A frequent error is producing a standard Code 128 barcode with product data but without GS1 syntax. Without the initial FNC1 and properly ordered AIs, scanners and downstream systems cannot parse fields reliably, resulting in misroutes and investigation overhead. Another common failure is omitting the FNC1 separator between consecutive variable-length AIs, which causes the second field to be appended to the first during decoding.

Date formats must follow GS1 rules. For example, expiration date (17) requires YYMMDD; using local date formats leads to false rejects at receiving. Lot and serial data are case-sensitive and length-bound; trimming leading zeros, inserting spaces, or transcribing ambiguous characters such as O and 0 can break matching logic. Human-readable text cannot substitute for machine-readable data when scan-based processes are in scope.

Cross-program confusion is another source of defects. Do not mix device UDI DI and PI semantics across carriers; ensure that DI corresponds to GTIN and that production identifiers map to the correct AIs and formats. Blood and tissue products may follow different standards; do not reformat or reinterpret labels intended for other frameworks without a formal change assessment and trading partner agreement.

Environmental and operational realities matter. Labels that perform on a flat carton may fail on curved vials or cold, moist surfaces. Ribbon, substrate, and print engine maintenance dramatically affect symbol grades. Validate performance against the actual use case and scanning distances, including conveyor speeds and mobile device optics.

For device UDI data structure alignment, consult UDI DI vs UDI PI to avoid conflating identifiers across carriers.

GS1-128 sits alongside other carriers and standards. For logistics units, the SSCC label provides a single identifier for pallets that ties to shipment documentation and receiving. In device UDI programs, a linear GS1-128 or a 2D GS1 DataMatrix may be used depending on space and scanning distance, but the underlying DI and PI semantics remain the same. In healthcare donations and transfusion, sectors may use distinct systems such as ISBT; do not cross-apply rules without a formal mapping.

From a systems perspective, the label is a node in a broader data flow. The GTIN, lot, expiration, serial, and SSCC connect to master data, work orders, inventory, and shipments. Clean interfaces between labeling, MES, WMS, ERP, and trading partner channels ensure that each scan event lands in the right ledger. Advance ship notices and pallet-level identifiers reduce manual receiving and speed discrepancy resolution when exceptions occur.

V5 Ultimate operationalizes GS1-128 by unifying template governance, controlled printing, verification, and event capture in a validated environment. Templates are versioned and approved with audit trails, labels are printed only in the right context with scan-back validation, and symbol quality can be verified inline. Event capture ties scans to inventory and shipments, enabling accurate trace forward and trace back during recalls, investigations, and annual product reviews.

V5 also streamlines data movement. It maps AI fields to master data and transaction payloads, updates inventory on scan, and links SSCCs to cartons and orders for fast receiving. Integrations with ERP and partner networks help ensure that shipping confirmations, returns, and rework records remain synchronized with the physical state of goods.

To align technology with compliance and performance goals, explore V5 capabilities for end-to-end lineage, label governance, and shipping execution across regulated manufacturing and distribution.

Learn how V5 connects label execution with upstream and downstream systems, including traceability, ERP integration, and shipping operations that require strong data integrity under 21 CFR Part 11 controls.