How do you design a pallet label the customer's scanner can read?
· Toni Martir, arquitecto de software
The pallet of yoghurts from the previous article carries its SSCC on the label, the number that identifies it, plus the product, the batch, the case count and the best-before date. The manufacturer prints the label and a scanner, a barcode reader, reads it in the customer's warehouse. If the scanner fails, there is the text under each barcode, which GS1 requires as a back-up for keying it in.
GS1 sets the essentials in its General Specifications: the size, where everything goes, how big the bars are and in what order the data comes. And before printing hundreds you scan one, because a barcode can print sharp and still carry the wrong number.
The A5 label on the pallet of yoghurts, from top to bottom
In each barcode's row, the first box is the text printed under that barcode. All three have a 0.51 mm module and 32 mm bars, and with 5 mm of white space on each side they fit comfortably across the label's 148 mm. The numbers are examples: GS1 keeps the 952 range for that purpose.
The measurements
GS1 suggests A6, 105 × 148 millimetres, if the label carries only the SSCC or little else, and A5, 148 × 210, if it also carries product data, according to its logistic label guideline. The top holds free text at least 3 millimetres high; the middle, the barcode data written out with data titles, in English unless the companies agree on another language, and at least 7 millimetres high.
The bottom holds the GS1‑128 barcodes, with the bars upright. Their module, the width of the narrowest bar, is between 0.495 and 0.940 millimetres; the bars are at least 31.75 tall, not counting the text, and each side keeps 10 modules blank, about 5 millimetres. With those margins, a barcode cannot be longer than 165.1 millimetres.
The order of the data
Every barcode starts with an FNC1, a special character that lives in the bars, never appears in the text, and tells a GS1‑128 apart from any other Code 128. After it comes each item with its Application Identifier, the number in brackets that says what the item is. The SSCC's (00), the product's (02) and the date's (15) have a fixed length, so the scanner knows where they end. The batch's (10) and the case count's (37) are variable length, and each is followed by another FNC1 when more data comes after it.
The guideline recommends putting fixed-length data first: in the example, the product and the date share one barcode, and the batch, an FNC1 and the case count go in another. Under each barcode goes its text, with the identifiers in brackets and without the FNC1s.
In the designer
In Report Manager, the label is a report with an A5 page, one barcode component
per barcode and, under each one, an expression with its text. In «Bar type»,
choose Code128C for the two digits-only barcodes, which always have an even
number of digits, and Code128B for the batch one, which can contain letters. Better not
to use «Code128», which picks the type itself: in one of my tests the .NET engine
encoded the batch wrongly. In «Expression», the FNC1 is written ¿, and the second
barcode's is '¿10' + PALLET.BATCH + '¿37' + Str(PALLET.CASES).
«Bar.Modul», the module, goes to 0.051 cm: 0.05 cm rounds down to 0.494 millimetres, below the minimum. The component's height is the bar height, 3.2 cm, and the bars start at its left edge: the 5 blank millimetres go outside the component.
Check that it scans
Scan one label and compare what the scanner returns with what you meant to encode; the FNC1 that separates two items arrives as the GS control character. I decoded the example's bars with a program of my own. With Report Manager's .NET engine, the one behind the .NET designer, the web designer and Reportman Server, all three barcodes returned exactly the right data. With printreptopdf 4.0.16 for Linux, the ¿ came through as two characters, and the SSCC scanned with an extra zero at the front and without its last digit, while the text underneath still showed the right number.
So how do you design it?
On A5 if it carries product data, with the GS1‑128 barcodes at the bottom and the SSCC's last. Each barcode with a module of 0.495 to 0.940 millimetres, at least 31.75 tall and 10 blank modules on each side; inside, fixed-length data first and an FNC1 after every variable-length item that has another one after it. And before printing hundreds, scan one.
Report Manager draws the barcodes with its barcode component, as Code128C and Code128B with the FNC1 written ¿, on one of its predefined page sizes, A5. With Reportman Server, which uses the .NET engine, the label is designed in the browser and generated as a PDF through its API.
Sources
- GS1, GS1 General Specifications, release 26.0,
ratified January 2026. Section 6.6.3.1, the three building blocks: «The top building block may
contain anything, e.g., text and graphics», «The middle building block contains non-HRI text
reflecting the information represented in the barcode(s) using data titles» and «The bottom
building block contains the barcode(s) including human readable interpretation (HRI).»
Section 6.6.4.1.1: «GS1-128 barcodes SHALL be placed in a picket fence orientation relative
to the base of a logistic unit» and «the GS1-128 barcode encoding the SSCC SHALL be placed in
the lowest portion of the label». Section 6.6.4.1.2: «As a back-up key entry and diagnostic
aid, a human readable interpretation (HRI) of each barcode element string encoded in a GS1-128
SHALL be provided.» Section 6.6.4.2: «The data content SHOULD be at least 7
millimetres/0.275 inches in height. If there is no other language agreed between trading
partners, data titles must be printed in English.» Section 6.6.4.4: «All non-HRI text
included in the top building block SHALL be clearly legible and no less than 3
millimetres/0.118 inches high.» Section 6.6.4.5: «A6 (105 mm x 148 mm), which is
particularly suitable when only the SSCC, or the SSCC and limited additional data, is
encoded» and «A5 (148 mm x 210 mm)». Section 5.12.3.5, table 5-51, for GS1-128 on logistic
units: minimum module 0.495 mm, target 0.495 and maximum 0.940; minimum height 31.75 mm, «for
bar height only and does not include the human readable interpretation»; and a quiet zone of
«10 X» on the left and on the right. Section 5.4.1: «The maximum physical length is 165.10
millimetres (6.500 inch) including Quiet Zones.» Section 5.4.3.7: «a Code 128 symbol, which
begins with one of the GS1-128 symbology double character start patterns, is always a GS1-128
barcode». Table 7-6, the identifiers of predefined length, among them 00 (20 characters), 02
(16) and 15 (8). Section 7.8.6.2: «An element string that does not start with two characters
defined in Table 7-6 SHALL be terminated by a separator character, unless it is the last
element string to be encoded». Section 7.8.4: «The value of the decoded separator character
transmitted in the decoded data string is always control character
» . Section 4.14: «HRI SHALL be limited to element strings and will not include barcode overhead such as separator characters.» and «parentheses SHALL surround AIs in HRI». Prefix table: «952 Used for demonstrations and examples of the GS1 system». - GS1, GS1 Logistic Label Guideline, release 1.3, ratified July 2019. Section 7: «A5 (148 mm x 210 mm) or 6 x 8 inch, suitable when additional data such as trade item data are needed. Applied for example on pallet labels.» Rule [6-11]: «It is best practice is to encode data of fixed length before any variable data within a GS1-128 barcode». Section 6.3: «The X-dimension is the specified width of the narrowest element in a barcode symbol.» Rule [6-21]: «All the data shown in each barcode should be provided below each symbol.»
- GS1, GS1 Application Identifiers (official reference, also as
JSON-LD): (00) «SSCC», N2+N18; (02) «CONTENT», N2+N14; (15) «BEST BEFORE or BEST BY»,
N2+N6, all three with
separatorRequired: false; (10) «BATCH/LOT», N2+X..20, and (37) «COUNT», N2+N..8, both withseparatorRequired: true. - Report Manager, barcode component: «Code128A, Code128B, Code128C, Code128 Code 128 family, A and B allow alphanumeric coding», «The C allow only numeric values but generates the narrowest barcode», «The Code128 generates a B and C mixed barcode», «To generate GS1 barcodes, the FNC1 char must precede the barcode, it's represented by the ¿ char», «Bar Modul»: «Internally stored in twips, editable in cms or inch, determine the minimum bar with», and the engines: «Delphi and Lazarus engine (VCL and LCL designers, printreptopdf, repweb, ActiveX)» and «.NET engine (.NET designer, web designer, Reportman Server)»; barcode printing: with Code128C «the total number of digits must be even»; page setup: «you can select a predefined page size»; expression evaluator: «function Str (num:variant):string»; and Reportman Server: «Reportman Server is one container on your network that holds the report engine, the report store and a web designer. Your team designs reports in the browser, previews them as PDF and runs them through a public API».
- Own test, 17 November 2026: the label in the diagram, on A5, with «Bar.Modul» at 29 twips
(0.5115 mm) and a height of 3.2 cm. The bars in the PDF from printreptopdf 4.0.16 for Linux
have a 0.5115 mm module and are 32.0 mm tall, starting at the component's left edge; at 28
twips, which is what 0.05 cm gives, the module is 0.4939 mm. Decoded with a program of my own,
the bars from the .NET engine (the Reportman.Reporting library from
github.com/tonimartir/reportman, built on 17
November 2026) return
]C1followed by021952414100012815261215, by10L2511, GS,3748, and by00395241410000000122, with 178, 178 and 156 modules (91.1, 91.1 and 79.8 mm). The ones from printreptopdf return the SSCC as]C100039524141000000012, and the second barcode starts with a space before the FNC1. With the Code128 type and the batch after the case count, the .NET engine encodedL2511as0051.
Toni Martir, arquitecto de software · · sources checked on