Choose the barcode from the receiving process and required data, then specify the label, print engine and inspection. A readable code is not necessarily an accepted code.
A case barcode may identify a type of traded product, while an SSCC identifies an individual logistics unit. The barcode format, encoded data and physical label must support that intended use. Obtain the customer’s current labelling specification before choosing between ITF-14, GS1-128 or a two-dimensional code. Do not replace an established receiving barcode simply because a new code holds more data.
GS1 UK distinguishes ITF-14 for traded-unit identification from GS1-128 when additional attributes, such as batch or date information, are needed. QR Code with GS1 Digital Link and GS1 DataMatrix use different data syntax; they are not interchangeable artwork options. Check GS1’s case-barcode guidance and agree the exact accepted format with the recipient.
| ITF-14 | Consider for a traded case identified by its GTIN where the receiving specification accepts it. It does not carry the extra batch and date fields that GS1-128 can encode. Confirm the available area and required print quality. |
|---|---|
| GS1-128 | Consider when the approved logistics or traded-unit format needs GS1 Application Identifiers. These describe the meaning and structure of encoded fields. Define the required identifiers rather than sending a list of text fields alone. |
| GS1 DataMatrix | Uses GS1 element-string syntax. Confirm that the receiving scanner can read the code and that its software correctly parses and uses the data. A successful phone-camera scan is not a complete receiving-system test. |
| QR Code with GS1 Digital Link | Encodes identifiers in a web-compatible URI structure. Confirm the business purpose, identifier governance and receiving-system support. An ordinary web-address QR code is not automatically a GS1 logistics label. |
| More than one barcode | Define which code each scanner should select. Test that additional codes do not create ambiguous reads, mismatched identifiers or an unintended workflow. |
The verification and reject-control guide separates these checks. Final print resolution is a machine-and-artwork decision, not a guarantee supplied by a dpi number.
Not as an automatic substitution. An SSCC is the identity of the logistics unit; the accepted barcode format and label content are governed by the applicable GS1 and trading-partner requirements. Confirm the receiving workflow before changing the data carrier, and do not create a different pallet identity just to print another symbol.
No. GS1-128 uses the Code 128 symbology with GS1-specific structure and data rules. A scanner reading a Code 128 string does not establish that it is a correctly encoded GS1-128 record. Validate the software configuration and the fields expected by the recipient.
No. Resolution must suit the code’s module size, data density, label area and required print-quality result. More data can enlarge the code or reduce the module size if the area is constrained. Select the print engine after reviewing the longest real data record and trialling the printed and applied result.
No single retail transition rule should be assumed to replace every warehouse or logistics labelling requirement. Retail checkout, case receiving and pallet identification are different applications. Keep the customer’s current specification as the acceptance basis and plan any code migration with both the data owner and receiver.
Technical references: GS1 UK: barcodes for cases; GS1: differences between 2D barcode options; GS1 UK: barcode placement. External references explain general principles; they are not specifications or availability statements for a Lancing machine.
Include the required barcode format, expected data, final label dimensions, pack surface, scanning arrangement and representative artwork. Lancing can review the print-and-apply requirements without assuming that one barcode type suits every receiver.