Where the traceability of the whole chain is born

The problem

Traceability is born at the dock, under pressure from a truck that charges by the minute.

Critical component receiving is the point where the traceability of the whole chain is born. If the lot enters wrong here, the birth history of every unit carrying it is contaminated, and nobody finds out until it matters — which is to say, at the worst possible moment. The two usual exits are both bad. If the supervisor keys it in carefully, the truck waits, and demurrage on a dangerous goods vehicle is not cheap. If they type fast, one digit goes wrong in a lot identifier. On top of that, with pyrotechnic material the paperwork is not only ERP: there are receiving records, segregated storage records and inventory reconciliation records kept in parallel today, sometimes on paper and sometimes in the warehouse's own spreadsheet.

• The truck arrives with gas generators: regulated pyrotechnic material with transport documentation, a certificate of analysis and a lot label on every container. The supervisor has to check it all, sign, and then key it in line by line.
• Both exits are bad. If they key it in carefully, the dangerous goods vehicle waits and demurrage is not cheap. If they type fast, one digit goes wrong in a lot identifier and the birth history of every unit carrying it is contaminated — found out at the worst possible moment.
• With pyrotechnic material the paperwork is not only ERP: receiving records, segregated storage records and inventory reconciliation records are kept in parallel, sometimes on paper and sometimes in the warehouse's own spreadsheet.
• This is the point where the traceability of the whole chain starts. Everything downstream — the first-off record, the DMC, the per-unit history — inherits whatever was entered here.

How it fits the IRIS system

Connect in photo mode pushing to ERP — packing list, certificate and labels, no supplier changes.

Connect in photo-the-analog mode, pushing to ERP.

Photo of the packing list, photo of the container labels, and the summary appears on the tablet with the discrepancies already highlighted: quantity, part reference or lot that do not match the open purchase order are flagged before the signature, not months later. One tap validates, and the receipt goes to the ERP via API and to the parallel warehouse records at the same time.

• Photo of the packing list: vision AI recognizes each supplier's format without asking anyone to change theirs, and extracts the tabular structure.
• Photo of the container labels: reading GS1-128 codes, two-dimensional codes, barcodes or plain text by OCR.
• Automatic cross-check against the open purchase order: discrepancies in quantity, part reference or lot are flagged before signing.
• One-tap validation on the industrial tablet.
• Push to the ERP via API, and to the parallel warehouse records.

See the full IRIS architecture →

Before and after

Today's receiving versus captured receiving

Aspect	Today	With iLEAN Connect
Truck at the dock	30-45 minutes	A few minutes
Lot identifier errors	Found months later, in a containment	Flagged before the signature
Certificate of analysis	Filed on paper, unlinked	Tied to the lot from minute one
Segregated storage and reconciliation records	Kept in parallel by hand	Fed from the same validated capture
Chain from supplier container to serialized unit	With gaps	Complete
Receiving/warehouse module licenses	Two or three, used to key in	One: the supervisor who validates

from 30-45 min of truck waiting to a few minutes · from lot errors found months later to discrepancies flagged before the signature · from traceability with gaps to a complete chain from the supplier's container to the serialized unit.

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.
• 💰 CFO angle: the receiving/warehouse module typically demands two or three active licenses largely dedicated to keying in entries. With Connect only the supervisor validates, without entering the ERP: typically 50-70% fewer licenses on that module, plus the cost of a mass-capture module you no longer need.
• From 30-45 minutes of dangerous goods truck at the dock to a few minutes, and carrier demurrage eliminated.
• A complete chain from the supplier's container to the serialized unit, which is what a supplier lot alert is later cross-checked against.

CFO angle — direct saving on ERP licenses. The receiving/ warehouse module typically demands 2-3 active licenses largely dedicated to keying in entries. With Connect only the supervisor validates, with one tap and without entering the ERP: typically 50-70% fewer licenses on the receiving/warehouse module, plus avoiding the cost of a mass-capture module and carrier demurrage. Estimated payback 3-8 months. *Estimate to validate.*

And the fair question from the production manager

"Does it recognize every supplier's packing list and every label format?" — yes, and without asking any of them to change theirs: the model extracts the tabular structure with no per-supplier template, and labels are read by GS1-128, two-dimensional code or OCR depending on what is there. It is an anchored task, where the best models drop below 1.5% error [1]; on top of that the capture is cross-checked against the open purchase order, and the supervisor validates before anything enters.

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