The delivery note, to ERP in one tap

The problem

All of your traceability rests on typing under pressure.

today it means signing and typing line by line, or the driver waits racking up demurrage, or it's rushed and the origin batch ends up poorly traced.

• The truck arrives with sacks of dried peppers, cumin, turmeric or pepper: a twelve-to-twenty-line delivery note, a certificate of analysis per lot and pallets labeled with an origin lot and a harvest, sometimes in another language and another unit system.
• Both ways out are bad. Either the driver waits forty minutes racking up demurrage while somebody types line by line, or it gets typed in a hurry after the truck has gone and the origin lot ends up badly traced at the exact point where traceability begins.
• That reappears months later, when a customer asks which harvest and which grower a jar came from and the chain breaks at the first link, which is the one nobody thought was fragile.
• And the certificate of analysis ends up filed loose, unlinked to the lot, when it is precisely the document that proves aflatoxin and ethylene oxide compliance for that specific material.

How it fits the IRIS system

Connect in photo mode — note, certificate and labels, with no supplier changes.

Connect photographs the delivery note + labels (GS1-128, QR, plain OCR). On-screen summary, one-tap validation, push to ERP via API.

The certificate of analysis stops being a filed sheet of paper and becomes linked to the origin lot from minute one. That is what turns grower-to-jar traceability into a lookup instead of a reconstruction, and it is the only ring of the chain that cannot be repaired afterwards: if the lot was typed wrong at the dock, every batch downstream inherits the error.

See the full IRIS architecture →

Before and after

Today's intake versus captured intake

Aspect	Today	With iLEAN Connect
Truck at the dock	20-40 minutes	Validation in seconds
Certificate of analysis	Filed loose	Linked to the lot on arrival
Grower → jar traceability	Rebuilt under pressure	Complete and queryable
Badly traced origin lots	Surface months later	Do not occur
Driver demurrage	Recurring	Eliminated
Receiving-module licenses	Two or three	One, the validator

20-40 minutes of manual entry → validation in seconds.

Impact estimate

Estimated impact — to validate against your actual invoice.

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.

• 💰 CFO angle: the receiving module typically needs two or three active licenses; with Connect only the receiving manager validates: 50-70 % reduction, recurring.
• From 20-40 minutes of manual entry per truck down to a validation in seconds, on every delivery and not only the quiet ones.
• Driver demurrage eliminated truck after truck, which is a recurring invoice that nobody budgets for and everybody pays.
• And a traceability chain that starts complete instead of starting rushed, which is what holds up when a harvest or a grower is questioned months afterwards.

50% to 70% savings on receiving-module ERP licenses + no more driver demurrage. *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 GS1-128 or QR where they carry one and by optical recognition where they do not. It is an anchored task, where the best models drop below 1.5% error [1], and the receiving manager validates before anything enters.

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