Coder and labeler integrated with iLEAN — the operator stops typing the SKU changeover.

The problem

The modern coder is already on the line — but disconnected from the ERP.

It happens in a great many food products plants: the investment in the Markem-Imaje, Domino or Videojet coder has already been made. The machine has an Ethernet port, speaks OPC UA, exposes a REST API. And even so, at every SKU changeover, the operator climbs up to the line, opens the coder panel and types by hand the new batch, the new date, the new expiry, the new SKU's allergens.

The result is always the same pattern:

1. One wrong digit in the batch — the operator types 251207 when it was 251208, and 1,200 bags are printed with a batch that does not exist in the ERP. Traceability broken.
2. Wrong expiry date — the previous SKU's shelf life (90 days) is applied to the new SKU (60 days, because it contains seeds and oil). Product on the shelf with an impossible date.
3. Previous SKU's allergens — the line switches from a classic product to one with sesame and the label keeps declaring "sesame-free". Recall.
4. Previous batch's label reused — the first box of the new SKU goes out with the previous label because nobody validated the first print.

The production manager knows it, and keeps a SKU-changeover checklist pinned to the wall. The checklist works 99% of the time. That 1% is what ends up in RASFF — and one wrong digit in the date means a recall, not an incident.

How it fits the IRIS system

iLEAN Connect integrated mode — the coder and the labeler become just another ERP peripheral.

The modern coder does not need an operator to type into it: it needs a layer that speaks the ERP's language to it. iLEAN Connect in integrated mode is that layer. It is the putty that fills the dead zone between the ERP production order and the job the coder prints — without asking you to change the coder, the labeler or the ERP.

The production order changes in the ERP. Connect translates. The coder prints the right SKU from the very first bag. The operator signs — they do not type.

How the iLEAN pieces are distributed at a food products plant with a modern coder/labeler:

• Connect (integrated mode) — talks to the coder over its native interface: OPC UA with the Markem-Imaje 9 series, Ethernet/IP with the Domino Ax-Series, REST/MQTT with the Videojet 1860, IO-Link for peripheral actuators. At the other end it reads the production order from the ERP (SAP B1, Sage, A3, Navision, Odoo, Datisa) and the SKU's template. It translates and loads the job in milliseconds. The coder stops having a panel anyone touches.
• Agent — governs the SKU changeover as a process, not as a keyboard. When the production order changes, the agent: validates that the format is approved for that SKU, recalculates the expiry date from the defined shelf life, verifies that the recipe's allergens match those declared on the label template, holds the first print for visual validation and, if everything matches, releases the line. If something does not match, it holds and alerts the quality manager through whichever channel they use. The person signs — the line does not start on its own.
• Edge (optional, recommended) — a machine-vision terminal over the coder's output that reads the first printed bag and compares what was printed against what was expected. If the modern coder already carries its own vision camera, Connect connects to it; if not, an Edge is mounted. It closes the loop: the guarantee that what leaves the printhead matches the production order.

See the full IRIS architecture →

Before and after

Manual SKU changeover vs. changeover triggered by the production order

Aspect	Coder typed by hand	With iLEAN Connect integrated mode
SKU changeover trigger	Operator reads the order and types at the panel	The ERP production order fires the job automatically
SKU changeover time	5-12 minutes per change (climb up, type, verify, climb down)	Seconds — the line stops only for the physical format change
Batch transcription error	Inherent to manual typing	Eliminated — the data travels hands-free
Expiry date	Operator calculates or types the date	Calculated by the SKU template from shelf life
Allergens on the label	Generic template updated "when there's time"	Synced with the active SKU's recipe in the ERP
First-label validation	Operator's visual check, no record	Vision on the first bag + manager's signature
File for the IFS/BRC auditor	Rebuild by hand, weeks	Per-batch dossier, automatic, with a photo of the first bag
Reel label format change	Designer edits and resends to the line lead	Template per SKU, fired by the production order

Impact estimate

Impact estimate for your plant — to be validated with your numbers.

The block below is an estimate to be validated with the specific data of your plant. We put it forward so the committee has an order of magnitude; we refine it during the diagnostic.

• Food products plant with 2-4 packing lines, modern thermal coder (Markem-Imaje 9 series / Domino Ax / Videojet 1860) and/or reel labeler, 15-30 active SKUs in rotation.
• Connect integrated-mode deployment on one pilot line. First value expected within a few weeks: the SKU changeover goes from typing to a job fired by the production order.
• SKU changeover time cut by around ≥ 50% (the slice that used to go to climbing up to the panel and typing).
• Coding errors (batch, date, allergen) trending to zero on the transcription side — the residual sits only in errors in the production order itself, which are caught at first-label validation.
• Indicative payback between 4 and 9 months, depending on SKU changeovers per month, the average cost of a minute of stopped line and your historical exposure to labeling recalls.
• The hard lever, as in the other food-batch landings, is a single avoided recall: product pulled from the shelf, reverse logistics, destruction, brand damage. One recall pays for the pilot.

And the production manager's reasonable doubt

“What if Connect gets the translation from production order to coder job wrong, and the line prints incorrectly at production speed?” — it is the right question. Two answers, complementary. First, technical: Connect in integrated mode does not "interpret" the production order, it recontextualizes it from one format to another. Hallucination is a problem of free generation, not of anchored tasks; in tasks where the AI merely moves a piece of data from one system to another (the ERP production order into the coder's "batch" field), the best models brought error below 1.5% ^[1]. Second, architectural: the first bag of every SKU is validated with vision and the manager's signature before the line is released. The three safety rings exist precisely for this — the person signs what is critical.

^[1] OpenAI paper “Why Language Models Hallucinate”, 2025 — on the reliability of AI in anchored tasks.