The shipping labeler stitched to the active order, with no retyping
The industrial labeler that prints the shipping label for seating and suspension Tier-1s is modern and has an API — but it sits isolated, and manually typing the part number and lot is still the standard method at every order change. With iLEAN Connect it is stitched bidirectionally to the ERP: part number, lot, quantity and GS1-128 travel automatically from the active order, with no typing in between. Pure poka-yoke.
The labeler has an API — but the part number and the lot are still typed by hand at every order change.
In a Tier-2 metal stamping plant, the shipping label is the identity document of the container going to the Tier-1: part number, lot, quantity and the GS1-128 code the customer scans on receipt. All of that already lives in the ERP — and yet, at every order change, somebody translates it by hand on the labeler panel, because the equipment, modern and API-equipped as it is, sits isolated from the ERP.
- Manual typing at every order change — when the new production order starts, somebody types the new part number and lot into the labeler panel, from memory or reading a printout, and adjusts the quantity. One panel, several opportunities for error, no cross-check against the ERP.
- One fat finger is an 8D — one wrong digit in the part number or the lot and the container ships with the wrong lot to the seating or suspension Tier-1: 8D plus a hold on the shipment, containment, an impact on your PPM and on each OEM's requirements. It happens 1 to 3 times a month, and some end in an 8D. Estimate to be validated against your plant's data, but that is the order of magnitude.
- The Tier-1 scans the GS1-128, it does not read the label — their receiving and sequencing depend on that code: if the GS1-128 does not correspond to the real content because it was mistyped at source, the material enters their system wrong and the failure propagates all the way to their line, in exactly the link they audit first.
The ERP knows which order is active, which part number, which lot and which quantity apply. But it does not tell the labeler: somebody has to translate it by hand, with the container waiting to leave and the risk of an 8D on the table.
Connect stitches the ERP and the labeler over API — the order change stops being typing and becomes a tap in the ERP.
The order change needs no more screens and no more transcriptions: it needs the data that already lives in the ERP to reach the labeler at exactly the right moment, without anyone rewriting it. That is what Connect is for.
When the ERP marks an order start, it automatically publishes part number, lot, quantity and GS1-128 to the labeler. The order change is a tap in the ERP.
How Connect works on the shipping line of a Tier-2 stamping plant:
- Connect stitches two modern systems over API — the labeler already has a modern interface, whether an industrial Zebra, Domino, Videojet or Markem-Imaje type; Connect connects to it and to the ERP bidirectionally without replacing any equipment or touching the printing hardware.
- The ERP publishes at order start — part number, lot, quantity and GS1-128 reach the labeler at the very instant the ERP marks the order start, in a single transaction.
- The order change stops being typing — it becomes a tap in the ERP: when the ERP records the new order, Connect publishes the package; nobody types the part number or the lot into the labeler panel again.
- Interlock before printing — Connect cross-checks what is about to be printed against the ERP order; if a single field differs, the labeler does not print: it holds and alerts the person with the exact field that does not match.
- The GS1-128 comes from the data, not from the panel — part number, lot, quantity and the destination Tier-1 template travel tied to the order; switching between customers stops depending on navigating panel menus.
- A record of the change for the auditor — what was published, at what time, to which device and with what confirmation is filed automatically, with nobody having to reconstruct it for the 8D or for the customer audit.
Part number typed into the panel vs. published from the ERP order
| Aspect | Isolated labeler, manual typing | With iLEAN Connect |
|---|---|---|
| Order change on the labeler | Typed by hand into the panel at every order | A tap in the ERP — published automatically |
| Typing errors in part number or lot | 1-3 a month, some with an associated 8D | Zero human-origin errors on the shipping label |
| Container shipped to the Tier-1 with the wrong lot | Caught at the customer's receiving — shipment hold | Eliminated at source — the label comes from the order data |
| Consistency, ERP order ↔ printed GS1-128 | Nobody checks it before printing | The labeler does not print if it does not match the order |
| Risk of an 8D and PPM impact towards the Tier-1 | Latent at every order change | The human-origin error that triggers it is eliminated |
| Record of the change for the auditor | Reconstructed afterwards across systems | Filed automatically: what, when and with what confirmation |
Impact estimate for your plant — to be validated with your own numbers.
The block below is an estimate to be validated against your plant's actual data. We put it forward so the committee has an order of magnitude; we refine it during the assessment.
- Tier-2 metal stamping plant with a relatively modern API-equipped shipping labeler and several order changes per shift, serving several Tier-1s and different part numbers.
- Connect pilot on the order change — it stitches the labeler to the ERP over API bidirectionally, without replacing equipment or touching the printing hardware. First value expected within a few weeks.
- Fast payback estimated at 3 to 6 months, depending on the frequency of order changes per shift and the cost of each 8D. Estimate to be validated.
- The hard lever is the drastic reduction in the risk of an 8D from mislabeling and of a shipment hold towards the Tier-1: a single container with the wrong lot at a seating or suspension Tier-1 can cost, between containment, sorting and PPM impact, far more than the whole pilot. This poka-yoke is also the natural foundation of the flagship's fourth ring against per-order deviation. Estimate to be validated.
And the fair question from the quality manager
"What if the AI invents a part number or a lot?" — it cannot: in this case the AI generates no data, it carries it anchored. The part number, the lot, the quantity and the GS1-128 come straight from the active ERP order; hallucination is a problem of free generation, not of anchored tasks, where the best models brought the error below 1.5% [1]. And even then, the critical call is not made alone: Connect cross-checks what is about to be printed against the ERP order before publishing, reads back what the labeler confirms it applied, and holds the print if anything differs, alerting the person before the first label comes out. The safety rings exist precisely for this.
[1] OpenAI paper "Why Language Models Hallucinate", 2025 — on the reliability of AI in anchored tasks.
What people ask about stitching the shipping labeler to the ERP
Why does typing the part number and lot at every order change end in an 8D?
Because it is a manual transcription at the most critical point of the flow. At every order change somebody types the new part number and lot into the labeler panel — from memory or reading a printout — with the container waiting to leave. One wrong digit and the container ships with the wrong lot to the seating or suspension Tier-1, who catches it at their receiving or on their line. From there the 8D, the shipment hold and containment are triggered, plus the impact on your PPM indicator and on each OEM's requirements. The error is neither the machine's nor the system's: it is human in origin, and it happens exactly where the ERP already knows which part number and which lot apply but does not tell the labeler.
How does iLEAN stitch the ERP and the labeler over API if both are modern systems?
Connect stitches together two modern systems that do not talk today. The shipping labeler already has an interface — REST API or OPC-UA depending on the equipment — and the ERP exposes its production events over REST API or webhook. Connect connects to both sides without touching the database directly and without replacing any equipment: when the ERP marks the order start, Connect publishes the part number, lot, quantity and GS1-128 to the labeler in a single transaction. The order change stops being typing on the panel and becomes a tap in the ERP — the event that already exists. There are no intermediate files and no manual exports: the data travels anchored from the system where it already lives to the label.
What is the GS1-128 and why does the Tier-1 care so much about it?
The GS1-128 is the standard barcode on the logistics shipping label: it encodes part number, lot, quantity and date in a normalized way, in application identifiers the seating or suspension Tier-1 reads automatically on receiving the container. They care because their receiving and their sequencing depend on that scan: if the GS1-128 does not correspond to the real content — because the part number or the lot was mistyped at your plant — the material enters their system wrong and the failure propagates to their line. Publishing the GS1-128 directly from the ERP order guarantees that what the Tier-1 scans is exactly what your system declares, with no human transcription in between that could break it.
What if the labeler is a different brand or model?
It does not change the approach. Connect does not depend on a specific brand: it connects to whatever the labeler exposes — REST API, OPC-UA or the device's labeling protocol — whether it is an industrial Zebra, Domino, Videojet or Markem-Imaje type. What gets integrated is not the printing hardware but the data flow: the ERP publishes the package and the labeler loads the right template and prints it. If you change labeler tomorrow, the connection is repointed on the device side and the rest of the interlock — cross-check against the ERP, confirmation read-back, hold if anything differs — stays the same. The integration lives in Connect, not in the labeler model.
How is human-origin error on the label really eliminated?
By taking the transcription out of the middle and adding a data interlock. The part number, the lot, the quantity and the GS1-128 come straight from the active order in the ERP — nobody retypes them on the panel, so the fat-finger error disappears at its source. Before releasing the print, Connect cross-checks what is about to be printed against the ERP order; the labeler confirms back what it applied and Connect compares that against what was published; if a single field differs, it holds the label and alerts the person with the exact field that does not match. The operator stops typing and moves to verifying the first label, which is where their judgment adds value. Zero shipping labels with a human-origin error towards the Tier-1.
Does your labeler have an API? A free audit of the integration gap — we will send the estimated ROI for your plant within 48h.
We work on your plant's real data, not ours. Assessment with no commitment.
Request estimated ROI within 48h ‹ See all 12 metal stamping cases See automotive