6.1 Top building block

The top building block may include any text or graphics. The name and address of the sender and receiver are typical examples. In many instances companies may also wish to add specific graphics to a label (e.g., company logos).

[6-1] (Normative) All text shall be clearly legible and no less than 3 millimetres / 0.118 inches high. [GENSPECS, 6.6.4.4]

6.2 Middle building block

The middle building block contains non-HRI text reflecting the information represented in barcode(s) using data title rather than AIs, and optionally additional information not represented in barcodes (preferably including data titles).

[6-2] All barcoded data elements must also be included as text with data titles.

[6-3] (Normative) The data content should be at least 7 mm (0.28 inch) in height [GENSPECS, 6.6.4.2]

[6-4] A GS1 2D barcode, if used, should be placed to the right of the text within the middle building block.

Data titles are the standard abbreviated descriptions of element strings used to support the human interpretation of encoded data. Data titles should be used adjacent to all data fields included in the middle building block.

Note: Data Titles may also be used adjacent to barcodes and HRI.

[6-5] (Normative) Data titles should be provided for all AIs encoded in the barcodes.

[6-6] (Normative) If there is no language agreed between trading partners, data titles must be printed in English. A second language may be added. For English data titles, the exact data titles as specified in the 'GS1 General Specifications' should be used. [GENSPECS, 6.6.4.2]

[6-7] Data titles should be presented in UPPERCASE.

[6-8] To avoid any confusion, the data title for dates may be followed by the chosen format, e.g. BEST BEFORE (dd.mm.yyyy): 24.12.2013. This may be different from the format used within the barcode which is always YYMMDD.

6.3 Bottom building block

The bottom building block contains the GS1-128 barcode(s) including their human readable interpretation (HRI).

GS1-128 is a special version or subset of Code 128.

[6-9] (Normative) GS1-128 barcodes must be distinguished from Code 128 barcodes by the use of the special Function 1 character (FNC1) after the start character.

An enlarged section of the first part of a GS1-128 barcode showing the FNC1 in blue is shown below.

Figure 6‑1 . FNC1 character in GS1-128 barcode.

Enlarged section of first part of a GS1-128 barcode

showing the Function 1 character in blue

GS1 Application Identifiers

Each data field in a GS1-barcode is preceded by a GS1 Application Identifier (AI). GS1 Application Identifiers are used to identify the meaning and format of the data following each AI.

The data fields are either of fixed or variable length, depending on the AI. There is a range of AIs for additional data, such as weight, area or volume. Full details of all the GS1 Application Identifiers can be found in the 'GS1 General Specifications' [GENSPECS].

[6-10] All the data in each GS1-128 barcode is denoted by the use of GS1 Application Identifiers, which specify the format of the data which follows them. This data may be numeric only, alphanumeric, fixed or variable in length.

Concatenation

A GS1 Application Identifier and the data that follows it are known as an element string, and several element strings may be shown in one GS1-128 barcode. This joining together of element strings is known as concatenation.

Concatenation is an effective means for encoding several AIs in a single barcode and should be used to save label space and optimise scanning operations.

[6-11] It is best practice is to encode data of fixed length before any variable data within a GS1-128 barcode

[6-12] The order in which the element strings appear in GS1-128 barcodes is not specified. Quality software contains optimisation procedures, which improves scanning and printing

[6-13] (Normative) The SSCC, defined by AI (00), shall always appear in the lowest barcode on the label [GENSPECS, 6.6.4.1.1].

[6-14] The SSCC can be alone or concatenated with other data in the same barcode. Concatenation shall not be used with SSCC on cartons and outer cases and on A6 / 4x6 labels.

X-dimension (Symbol size)

The X-dimension is the specified width of the narrowest element in a barcode symbol.

[6-15] (Normative) The allowed X-dimension range for the GS1-128 barcode symbol is between 0.495 mm (0.0195") and 0.94 mm (0.0370"). The target X-dimension recommended for the GS1-128 barcode symbol is 0.495 mm (0.0195"). [GENSPECS, 5.9.3.5, table 5].

[6-16] When multiple barcodes are used it is recommended to use similar X-dimensions. This helps scanning systems to work more effectively.

[6-17]Note that using an X-dimension at the higher end of the permitted range can support consistent scanning when the barcode might be used in challenging application environments (e.g., freezing can degrade print quality).

Barcode height

[6-18] (Normative) A minimum height of at least 31.75 mm (1.250") applies to all the GS1-128 barcodes on the label. The minimum symbol height indicated is for bar height only and does not include the Human Readable Interpretation. [GENSPECS, 5.9.3.5, table 5]

Quiet zones / Light margins

[6-19] (Normative) Barcodes shall be printed with quiet zones (or light margins) at each side. The quiet zones must be at least 10 X-dimension (10 X) in width. Centred barcodes will help ensure the quiet zones are respected.

Orientation and placement

[6-20] (Normative) Horizontal orientation (picket fence orientation) of barcode symbols must be used on logistic units. In other words, the bars and spaces shall be perpendicular to the base on which the logistic unit stands.

Human readable interpretation

[6-21] All the data shown in each barcode should be provided below each symbol. Brackets (parentheses) are normally printed around each AI but these must not be encoded in the barcode.

[6-22] (Normative) The data must be shown in characters at least 3 mm high and clearly legible. [GENSPECS, 4.15]

AI uniqueness (no repetition)

[6-23] Each GS1 Application Identifier (AI) may only occur once on a logistic label.

6.4 Rules related to label segments

The order and top/down alignment of label segments may vary depending on the size of the logistic unit and the business process being served.

[6-24] (Normative) Within each separate label segment the building blocks must be placed according to the lay-out defined in section 2.2 . Building blocks [GENSPECS, 6.6.3.2]

[6-25] (Normative) A segment holding the SSCC shall always be present, and shall be positioned under any other segments. [GENSPECS, 6.6.3.1]

[6-26] Segments may be printed as separate labels in which case they should be placed vertically in close proximity of each other, with the segment containing the SSCC at the bottom. When segments are added separately, care should be taken not to obscure existing segments.

[6-27] The carrier segment may be replaced during the journey of the logistic unit. The original SSCC should be preserved in that case, either by leaving the segment holding the SSCC intact, or by reproducing the original SSCC on the new label / label segment.