Every Customer Wants a Different Label: Product Label and Barcode Printing Management Integrated with MES

Why One Label Can Become One Customer Claim

Plants that supply several customers quickly learn that the same product needs a different label for each of them. Customer A wants a GS1-128 barcode and part number, Customer B wants its own QR code with a delivery note number, and Customer C wants English text and country of origin. Most label errors get caught at the customer's receiving inspection, and the shipment gets rejected.

Label incidents usually come from one of three places:

Wrong label applied: a label from the next line ends up on the box, or the case label and the unit label get swapped

Wrong data printed: an operator types a lot number or quantity by hand and gets one digit wrong

Outdated template: the customer changed its format, but some printer PCs still have the old file

The root cause looks much the same from plant to plant. Template files sit on whichever PC is attached to each printer, and the only version control is a file name like "final" or "final_v2". Take 10 customers × 5 product families × 3 packaging levels: that's 150 templates. Spread them across a dozen PCs and nobody can say for sure which file is current.

Managing Label Templates as Data

Template master and versioning

Label templates should be handled as master data, not as loose files. The core idea is to record in the system which template version applies to each customer + item + packaging level combination. Operators don't pick the template. Once the work order is set, the template follows from it.

Store a version number, author, reason for change, and the customer's approval document with every template

Never delete old versions. Keep them as history so you can reproduce the exact label used on any past shipment

Change approval and effective dates

Template changes go through draft → review → approval → effective date. If a customer says "new format for shipments starting the 1st of next month," set that date as the effective date, and inventory produced earlier keeps the old template. Restrict unapproved templates to test prints only, so a template still under review can never go out on a real shipment.

Let the System Fill in the Data, Not People

Pull values from MES, eliminate manual entry

Almost everything printed on a label already exists in MES: work order number, part number, lot number, production date, expiry date, pack quantity. Feed those values straight from MES into the template and the operator only has to press print. If you use GS1-128, it's also safer to lock the Application Identifier structure into the template, for example (01) GTIN, (10) lot, (11) production date, and (17) expiry date.

Track reprints and voided labels

Reprints happen all the time because of printer jams and damaged labels. Without controls, a reprint creates two labels with the same serial number. Once the second one lands on a different box, traceability is broken.

Require a reason and supervisor approval for every reprint

Allow a reprint only after the original label has been registered as voided

Log every print, reprint, and void at the serial-number level

Verify After Application: Scan-Match Interlocks

A label can print correctly and still end up on the wrong box. That's why post-application scan verification is the final gate.

At packing, scan the label and compare it with the work order's part number, lot, and quantity

Scan case and unit labels together to confirm the packaging hierarchy is correct

A warning pop-up on a mismatch isn't enough. On a busy floor, people close the dialog and move on. Design an interlock that actually blocks the next step: stop the conveyor, or flag the box as blocked on the shipping screen until a supervisor releases it.

Printer Operations and Failure Handling

Reduce dependence on printer languages and drivers

Industrial label printers use vendor-specific command languages, such as Zebra's ZPL, SATO's SBPL, and TSC's TSPL. When templates depend on a PC driver and a desktop design tool, every PC replacement turns into a problem. Generating the printer-language output on a server and sending it over the network removes most of that dependency.

Have a fallback print path

One stalled printer can stop a whole line. If print jobs run through a server-side queue, you can reroute instantly to a nearby printer with the same resolution. Resolution really does matter here. ZPL coordinates are in dots, so a template designed for 203 dpi prints at roughly two-thirds size on a 300 dpi printer. Group fallback printers by resolution.

How POLYGLOTSOFT Builds Label Management Systems

POLYGLOTSOFT adds centralized template management and MES integration on top of the label printers you already have, with no hardware replacement. We roll out the pieces in stages to fit your plant: a per-customer template master with approval workflows, automatic MES data mapping, reprint controls, scan-match interlocks, and fallback printing for printer failures. If label errors keep getting your shipments rejected, contact POLYGLOTSOFT. We'll review how your labeling works today and help you decide where to start.