| Primary purpose | Identifies a trade item or product configuration. | Identifies logistics and trade-item data using GS1 Application Identifiers. | Stores product, traceability, and logistics data in a compact two-dimensional symbol. | Choose based on whether the label must identify only the item or also prove and track its journey. |
| Typical payload | One 13-digit GTIN. | GTIN, serial number, lot or batch number, production date, expiry date, quantity, SSCC, or other standardized data elements. | GTIN plus serial number, lot or batch number, expiry date, or other supported GS1 data elements. | Use GTIN-13 for identity; use GS1-128 or GS1 DataMatrix when uniqueness, traceability, or shipment data is required. |
| Data structure | A fixed-length identifier without embedded meaning about the product. | Uses GS1 Application Identifiers to define the meaning, format, and length of each data field. | Uses GS1 Application Identifiers and supports structured data in a two-dimensional format. | Application Identifiers make variable data more consistent across international supply-chain systems. |
| Symbol type | One-dimensional linear barcode. | One-dimensional linear barcode. | Two-dimensional matrix barcode with finder patterns and error correction. | Select a matrix symbol when label space is limited or multiple fields must fit on a small tamper-evident label. |
| Best payload size | Small and fixed: one item identifier. | Small to medium: several structured fields, with symbol size increasing as data is added. | Medium to relatively large payloads in a compact footprint, subject to symbol size and scanner capability. | For serialized security labels, include only operationally necessary fields to preserve scan reliability. |
| Serialization support | No serial number is encoded by the GTIN-13 itself. | Supports a serial number when encoded with the appropriate GS1 Application Identifier. | Supports a serial number and is well suited to unique item-level identification. | Use serialization to distinguish individual labels and detect duplicate or unexpected scans. |
| Traceability fields | Not embedded in the code; traceability must be linked externally. | Can encode lot, batch, date, quantity, and logistics-unit information. | Can encode lot, batch, date, and serial information in a compact symbol. | For global shipping, pair the barcode with a secure database record rather than relying on the symbol alone. |
| Scanning orientation | Generally requires the scanner beam to cross the bars correctly. | Generally requires the scanner beam to cross the bars correctly; orientation and quiet zones matter. | Area imaging scanners can read it from different orientations, provided the symbol is unobstructed. | DataMatrix is often more practical where packages may be scanned from varied angles. |
| Label-space efficiency | Requires a relatively long horizontal area for reliable printing and scanning. | Usually needs more linear space as additional data is added. | High data density can reduce the label footprint, but adequate module size and margins remain essential. | Prefer GS1 DataMatrix for small seals, narrow labels, or labels containing several variable fields. |
| Human-readable text | The 13-digit number is normally printed below the symbol. | Application Identifier values should be printed in human-readable form where operationally required. | Key encoded values should be printed beside or below the symbol when manual recovery is needed. | Always retain a readable serial or reference number for exception handling. |
| Security capability | Identifies an item but does not provide item-level uniqueness or tamper evidence by itself. | Supports serialized and logistics data, but physical tamper evidence must be provided by the label material and construction. | Supports serialized data in a compact format; physical tamper evidence still requires a suitable security label design. | Combine the barcode with destructible film, void adhesive, sequential numbering, and scan-event verification where appropriate. |
| Printing requirements | Sharp, high-contrast bars and clear quiet zones are required. | Requires consistent bar width, high contrast, correct data formatting, and clear quiet zones. | Requires accurate square modules, a complete finder pattern, strong contrast, and sufficient quiet zone. | Validate printed labels after exposure to abrasion, moisture, temperature changes, and adhesive removal. |
| Equipment compatibility | Widely supported by laser and imaging barcode scanners. | Widely supported in distribution and warehouse scanning environments. | Requires an area-imaging scanner or camera-based reader with GS1 DataMatrix support. | Confirm scanner support throughout every carrier, warehouse, customs, and receiving checkpoint. |
| Global shipping suitability | Suitable for basic product identification when no shipment-level or serialized data is needed. | Strong choice for cartons, pallets, logistics units, and shipment labels carrying structured supply-chain data. | Strong choice for compact item-level labels requiring serialisation and traceability. | Use the code that matches the largest required payload while preserving reliable scanning at all destinations. |
| Recommended use case | A tamper-evident label that only needs to identify the product type. | A carton or pallet label containing a serial shipping container code, quantity, lot, or shipment-related data. | A small serialized seal or label containing product identity and traceability data. | Match the code to the payload, then test the complete label—including adhesive, substrate, and protective coating. |