|
GS1 128 compliance - Background
UCCEAN (also known as GS1 128 barcode), is a very important barcode used by many logistics, warehouses and manufacturing firms in their daily activities. Each of these companies may implement its own warehouse management systems differently and adopt different UCCEAN barcode scanning algorithms. Some may implement the scanning algorithms very strictly while others may allow flexibility in the barcode as long as it adheres to the general GS1 specifications.
ConnectCode supports the different variations through a Strict GS1 128 Compliance option. When this option is selected, the barcode generated adheres strictly to the UCCEAN / GS1 128 specifications. Otherwise it generates a barcode that can be read by the scanning algorithm of many legacy systems. This gives users a choice to choose the preferred implementation of the UCCEAN barcode as required by different organizations with various scanning devices and systems.
If you are new to this barcode, you may want to use the default implementation and leave the checkbox unchecked. In the event that the default (legacy) implementation does not meet the strict conditions required by some companies, you may want to turn on the Strict GS1 128 Compliance option.
Default/Legacy Implementation
The following shows the structure of the UCCEAN barcode generated using the default / legacy implementation. This implementation is usually accepted by most warehouse and logistics firms.
|
UCCEAN Barcode (Default Implementation)
|
|
Start Char (Start Markers for Code 128 Subset A/B/C)
|
|
FNC1 Marker (Separator)
|
|
Application Identifier (AI)
|
|
Actual Data Following AI
|
|
FNC1 Marker (Separator)
|
|
Application Identifier (AI)
|
|
Actual Data Following AI
|
|
Check Char
|
|
Stop Char
|
Strict GS1 128 Compliance
The following shows the structures of UCCEAN barcodes generated using the Strict GS1 128 Compliance mode. This implementation is accepted by organizations that require a stricter implementation. The main differences are
1. This mode may create even shorter barcodes because it employs subset C compression whenever the data consists purely of digits.
2. Also, the FNC1 character, a special marker used to separate multiple application identifiers in the barcode, is used only when the particular application identifier is associated with variable data.
Example - Structure of a Fixed Length Data Application Identifer
|
UCCEAN Barcode (Fixed Length Data)
|
|
Start C Marker
|
|
FNC1 Marker (Separator)
|
|
1st Application Identifier (AI)
|
|
Fixed Length Data Following 1st AI
|
|
2nd Application Identifier (AI)
|
|
Actual Data Following 2nd AI
|
|
Check Char
|
|
Stop Char
|
Example - Structure of a Variable Length Data Application Identifer
|
UCCEAN Barcode ( Variable Length Data)
|
|
Start C Marker
|
|
FNC1 Marker (Separator)
|
|
1st Application Identifier (AI)
|
|
Variable Length Data Following 1st AI
|
|
FNC1 Marker (Separator)
|
|
2nd Application Identifier (AI)
|
|
Actual Data Following 2nd AI
|
|
Check Char
|
|
Stop Char
|
Strict GS1 128 Compliance availability
This option is available from ConnectCode Barcode Fonts version 5.5. It is supported in the following components :
- Font Encoder
- .Net Dynamic Link Libraries
- Microsoft Excel Visual Basic Applications integration
- Crystal Report Formulas
Back to UCCEAN Barcode Font
|
