Receiving stops blocking the dock

The problem

Either the truck waits, or the batch is badly traced.

And they have to sign and then log into the ERP to key it in line by line. There are only two possible endings: either the carrier waits and charges demurrage, or it gets keyed in fast. And what gets keyed in fast comes back weeks later, when somebody needs to trace which leather roll went into which seat of which vehicle, and it turns out you cannot. Backward traceability is as demandable as forward: when the customer opens an investigation, the chain has to reach the roll and its certificate.

• The truck arrives with fabric rolls, leather hides, foam, frames or mechanisms: a delivery note with fifteen or twenty lines, a label with a batch on every unit, and the material quality certificates that in automotive are not optional.
• The receiving lead signs and then keys it into the ERP line by line, with the driver standing there. There are two endings: the carrier waits and charges demurrage, or it gets keyed in fast and badly.
• What was keyed in fast comes back weeks later, when somebody needs to know which leather roll went into which seat of which vehicle, and cannot. The batch was typed loosely, or not at all.
• The certificate ends up in a folder nobody opens again, when it is exactly the document that closes the chain back to the roll and the one the customer's investigation asks for first.

How it fits the IRIS system

Connect in photo mode — delivery note, labels and certificate, no supplier asked to change anything.

Connect in photo-of-the-analog mode. Vision recognizes each supplier's delivery note layout, without asking anybody to change theirs, and extracts the full tabular structure. For the units it reads barcodes, QR, data matrix codes or plain text by optical recognition. And the material quality certificate is captured as a document and stays tied to the batch that arrived, not filed separately in a folder nobody opens again. One-tap validation on the tablet and the write into the ERP through its programming interface. From forty-five or sixty minutes of truck at the dock to under ten. From loosely tied batches that surface during an investigation to complete photo-based traceability from day one. And again the financial angle: the receiving and warehouse module typically requires two or three active licenses, receiving lead, support and supervisor. With Connect only the lead validates with one tap, without logging into the ERP. Typical reduction of fifty to seventy percent in that module's licenses, plus what you save on dedicated capture modules and on demurrage charged by the carrier.

Backward traceability is as demandable as forward: when the customer opens an investigation, the chain has to reach the roll and its certificate. Captured by photo, that chain exists from day one instead of being reconstructed loosely during the investigation. And the receiving lead validates with one tap on the tablet, without logging into the ERP at all.

See the full IRIS architecture →

Before and after

Today's receiving versus captured receiving

Aspect	Today	With iLEAN Connect
Truck at the dock	45-60 minutes	Under 10
Delivery note lines	Keyed one by one	Extracted as a table, one tap
Roll and batch labels	Read by eye	Barcode, QR, data matrix or text
Material certificate	Filed separately	Tied to the batch that arrived
Which roll went into which seat	Reconstructed, loosely	Queryable from day one
Receiving module licenses	Two or three	One, the lead who validates

Impact estimate

Impact estimate — to be validated with your 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.

• Estimated payback 3-8 months, plus the recurring annual saving, to validate against your own dock times and invoice.
• 💰 CFO angle: 50-70% fewer licenses on the receiving and warehouse module, because only the lead validates, plus what you save on dedicated capture modules.
• From 45-60 minutes of truck at the dock to under ten, truck after truck, with the demurrage charged by the carrier gone.
• And complete photo-based traceability from the roll to the seat, from day one, which is what holds up when the customer opens an investigation.

Estimated payback 3-8 months · 50-70% fewer licenses on the receiving module Estimated payback of three to eight months, plus the recurring annual saving. An estimate to validate.

And the fair question from the production manager

“Does it recognize every supplier's delivery note?” — yes, and without asking any of them to change theirs: the model extracts the table structure with no per-supplier template. Labels are read by barcode, QR or data matrix where present and by optical recognition where not. It is an anchored task, where the best models drop below 1.5% error [1], and the receiving lead validates with one tap before anything enters the ERP.

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