Bulk orange and aseptic input intake, without typing into the ERP

The problem

Two kinds of intake, one bottleneck: a person typing while the truck waits.

This plant's goods intake has two very different natures. On one side, agricultural bulk: orange trucks crossing the weighbridge with their weight ticket and delivery note. On the other, industrial pallets: aseptic carton reel, caps, cultures, rennet, sugar or bought-in concentrate, each with its certificate of analysis and its barcoded batch label. Both end the same way. The receiving supervisor has to sign the paper and then log into the ERP to key it in line by line. Either the driver waits twenty to forty-five minutes on demurrage, or it gets typed in a hurry and the batch is badly traced. The second option is not paid for that day. It resurfaces three weeks later, in a traceability query nobody can close because the batch that was typed is not the batch that arrived.

• On one side, agricultural bulk: orange trucks crossing the weighbridge with their weight ticket and delivery note, all day, for weeks.
• On the other, industrial pallets: aseptic carton reel, caps, sugar or bought-in concentrate, each with its certificate of analysis and its barcoded batch label.
• Both end the same way: the receiving supervisor signs the paper and logs into the ERP to key it in line by line. Either the driver waits twenty to forty-five minutes on demurrage, or it gets typed in a hurry and the batch is badly traced.
• The second option is not paid for that day. It resurfaces three weeks later, in a traceability query nobody can close because the batch that was typed is not the batch that arrived.

How it fits the IRIS system

Connect in photo mode with ERP posting — note, ticket and labels, no supplier changes.

Connect in "photo of the analog" mode with ERP posting. The flow:

The delivery note stops being a filed sheet of paper and becomes an image attached to the goods receipt from minute one, cross-checked against the open purchase order before anyone signs. That is what turns a three-week-old traceability question into a query instead of a reconstruction — and what keeps the bay fluid in the weeks the season saturates it and the weighbridge queue reaches the road.

• Photo of the truck's delivery note, photo of the weighbridge ticket and photo of the pallet labels.
• iLEAN reads standard logistics barcodes carrying batch, expiry and quantity, and reads the note and ticket by OCR.
• It automatically cross-checks against the open purchase order in the ERP and flags immediately if quantity, batch or certificate do not match.
• The receiving supervisor sees the summary on the tablet and validates with one tap, or flags the discrepancy.
• The API writes the goods receipt into the ERP, with the original image of the delivery note attached and queryable forever.

See the full IRIS architecture →

Before and after

Today's intake versus the captured intake

Aspect	Today	With iLEAN Connect
Truck at the bay	20-45 minutes	Under a minute to validate
Delivery note and weighbridge ticket	Typed, then filed	Photographed, read and attached forever
Reel and cap batch labels	Keyed by hand	Barcode read: batch, expiry, quantity
Mismatch with the purchase order	Found weeks later	Flagged before the signature
Hauler demurrage	Invoiced every season	Eliminated
Licenses on the goods receipt module	Four	One, the supervisor who validates

from 20-45 minutes of waiting per truck, to validation at the bay in under a minute. From typed traceability, to photographed traceability. From invoiced carrier demurrage, to a fluid bay in peak season.

Impact estimate

Estimated impact — to validate against your actual ERP 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: if four people across receiving and the weighbridge hold an ERP license purely to post goods receipts, with Connect one is enough: from 4 to 1, a 50-70 % reduction on the goods receipt module, recurring.
• Estimated payback 3-7 months in season.
• Demurrage eliminated, truck after truck, in the weeks the bay is saturated.
• And complete batch-to-plant traceability by image — the delivery note, the ticket and the reel label attached to the goods receipt — which is what closes the query that today stays open for three weeks.

direct CFO angle. If four people across receiving and the weighbridge hold an ERP license purely to post goods receipts, with Connect one is enough: from 4 to 1. Typical ratio for this archetype: −50 % to −70 % on goods receipt module licenses, a recurring annual saving, plus eliminated demurrage and complete batch-to-plant traceability by image. Estimated payback 3 to 7 months in season. *Estimate to validate against the actual ERP invoice.*

And the fair question from the production manager

«Does it recognize every supplier's delivery note and every grower's ticket?» — 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 standard logistics barcode 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 supervisor validates before anything is written to the ERP.

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