Traceability starts right from the very first kilo

The problem

There are only two ways out, and both are bad.

Because the supervisor has to sign and also go into the ERP and key in line by line. There are only two ways out: either the haulier waits and charges demurrage, or it gets keyed in fast and the origin of the material is badly tied. And that resurfaces weeks later, when someone has to explain to a customer what the failed batch was made from, and nobody can.

• The lead has to sign and then go into the ERP to capture line by line.
• Either the carrier waits charging demurrage, or intake is typed fast and the material's origin ends up badly tied.
• And that resurfaces weeks later, when you have to explain to a customer what the failing batch was made from.
• And nobody can — because the answer was typed in a hurry at the dock.

How it fits the IRIS system

A photo of the ticket, the note and the labels. No broker is asked to change anything.

With Connect, the photo is enough. The weighbridge ticket, the delivery note and the bale labels. Vision recognises the ticket and note formats without asking the broker to change theirs, and reads the labels by barcode, by QR or by plain text. It extracts supplier, material, weight, bale count and remarks, and lays it out on the tablet. The supervisor validates with one tap and it all lands in the ERP. On top of that, any weight discrepancy against the weighbridge ticket surfaces right then, not at month-end close. The truck goes from forty-five minutes in the yard to minutes, and the origin of the material is tied from the very first kilo. And once again the financial angle. The ERP goods-in and warehouse module typically demands two or three active licences: receiving, support and supervision. With Connect only the supervisor validates, and does so without entering the ERP. The typical reduction is between fifty and seventy per cent of that module's licences, plus dropping the cost of a mass-capture add-on.

The weight discrepancy against the weighbridge ticket is caught at that very moment, not at month-end close, which is when there is no longer anyone to claim it from.

See the full IRIS architecture →

Before and after

Material intake, before and after

Aspect	Today	With iLEAN Connect
Capture into the ERP	Line by line, in a hurry	A photo and one tap
Carrier demurrage	Paid while waiting	Eliminated
Origin of the material	Badly tied when there is pressure	Supplier and bale, from the first kilo
Weight discrepancy	Shows up at month-end close	At the moment of unloading
Different note formats	Each broker has their own	Nobody is asked to change
Receiving module licences	One per person capturing	One, the lead who validates

Impact estimate

Impact estimate — to validate against 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.
• Typical reduction of 50-70% in receiving module licences.
• Plus the recurring licence saving and the demurrage saving, which today is paid without argument.
• And everything downstream stops inheriting the dock's errors.

Payback 3-8 months · typical 50-70% cut in goods-in module ERP licences. Estimated payback is three to eight months, with the recurring licence saving and the haulier demurrage saving running on top. An estimate to validate against the real number of intakes per week. Conservative ranges, an estimate to validate against the plant's real data.

And the fair question from the production manager

"Our brokers each label their own way." — that is the normal case, which is why three readings are combined: barcode, QR and plain text. All three are anchored tasks [1]. And none decides alone: what enters the ERP is what the lead validates on the tablet.

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