Report Manager
ENES

← All articles

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

Top: free text Who sends the pallet, and to whom
Lácteos Ribera, S.A. Distribuciones Sur, S.L.
Middle: the data with its titles What the barcodes say, written out
SSCC CONTENT COUNT BEST BEFORE BATCH/LOT
First barcode Two fixed-length items: the product and the date
(02) 19524141000128 (15) 261215 91 mm of bars
Second barcode Two variable-length items: the batch, an FNC1 and the case count
(10) L2511 (37) 48 91 mm of bars
Third barcode, the lowest The SSCC, on its own
(00) 395241410000000122 80 mm of bars

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

Toni Martir, arquitecto de software · · sources checked on