Paint and component receipt enters the ERP with a photo, not twenty typed lines
The truck arrives with drums of basecoat and solvent and cartons of components. The delivery note has 12 to 20 lines; every drum has its lot and its expiry. Today the choice is bad on both sides: either the truck waits and charges demurrage, or somebody types fast and traceability breaks. With iLEAN Connect: a photo of the note, a photo of the labels, one validation tap, and everything enters the ERP with the right lot, expiry and supplier.
Receiving is where traceability breaks — and where demurrage is paid if it does not.
A paintshop receiving dock carries a structural tension: the truck wants to leave and the ERP wants twenty lines. Drums of basecoat and solvent with their lot and expiry, cartons of components with their certificates, a delivery note in whatever format each supplier decided to use. And one person in the middle:
- Either demurrage, or haste — doing it properly means holding the truck while lines are typed one by one; doing it fast means signing and typing later, from memory or from a phone photo. Both options cost, one in visible money and one in invisible money.
- Traceability breaks here and shows up weeks later — a badly associated basecoat lot causes no trouble on the day it is typed. It causes trouble the day quality tries to trace a finish defect back to the drum it came from, and the trail leads nowhere.
- Every supplier with its own format — no two delivery notes are alike, and asking suppliers to change theirs is not a realistic option. Normalization, if it happens at all, is done by hand at the dock.
In the end receiving works because somebody holds it together with craft, not because the system supports it. And that craft is recorded nowhere.
Connect in photo mode — the supplier's note exactly as it comes, and the labels exactly as they are.
The information needed is already printed: on the delivery note and on the drum and carton labels. What is missing is the path from that paper to the ERP without passing through a keyboard. Connect covers it with vision, without demanding that suppliers change anything and without changing the dock process.
A photo of the delivery note, a photo of the labels, a one-tap validation on the tablet, and everything enters the ERP with the right lot, expiry and supplier. The truck leaves in minutes and traceability from drum to painted rack is closed from the first moment.
How Connect works in a paintshop receiving dock:
- It recognizes each supplier's format — the vision does not depend on a single template: it interprets the delivery note as it arrives, with its own columns and layout. Nobody outside has to be asked to change.
- Labels in any encoding — GS1-128, QR, barcode or plain printed text. Whatever is on the drum or the carton is read without demanding a specific standard.
- Lot and expiry as fields, not as text — what is read is structured into the fields the ERP expects, so the transfer is direct and the lot is usable for tracing later.
- One-tap validation — the manager reviews the summary and confirms. Lines with a doubtful reading appear highlighted and are the only ones requiring attention.
- Traceability closed at source — the basecoat lot enters the system at the moment of receipt, so when a defect has to be traced back to the drum weeks later, the path exists.
Typed receiving vs. receiving with Connect photo
| Aspect | Delivery note typed line by line | With iLEAN Connect photo |
|---|---|---|
| Truck time at the dock | 30-45 min | 5-10 min |
| Lot and expiry errors | Hidden until tracing is needed | Doubtful reading flagged before entry |
| Supplier delivery note format | Normalized by hand by a person | Interpreted exactly as it arrives |
| Drum → painted rack traceability | Reconstructed, if possible | Closed at receiving |
| Receiving-module licenses | One per person who types | One: the person who validates |
| Carrier demurrage | A recurring cost | Eliminated |
Impact estimate for your plant — to be validated with your own 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.
- Automotive paintshop receiving drums of basecoat and solvent and cartons of components daily, with 12-20 line delivery notes and several suppliers using different formats.
- Connect photo pilot at the dock with an API transfer into the ERP after one-tap validation. Without asking suppliers to change or redesigning the receiving process. First value expected within a few weeks.
- CFO angle — the receiving module typically requires 2 to 3 active licenses; with Connect a single person validates without the rest entering the ERP. Typical reduction of 50-70% in that module's licenses, plus the elimination of carrier demurrage.
- Indicative payback of 3 to 8 months combining dock time, demurrage avoided and licenses. Estimate to be validated against your real numbers.
- The hard lever that does not appear on the spreadsheet: basecoat lot traceability. The day a finish defect has to be traced back to the drum, either the trail is there or it is not.
And the fair question from the warehouse manager
"What if it misreads a lot and throws my inventory out?" — hallucination is a problem of free generation, not of anchored tasks. Reading a lot printed on a label and mapping it to a known field is an anchored task, and there the best models brought the error below 1.5% [1]. There are also two nets underneath: lines with a doubtful reading arrive highlighted, and nothing is transferred to the ERP without a person confirming it. The practical result is fewer errors than typing at speed with the truck waiting.
[1] OpenAI paper "Why Language Models Hallucinate", 2025 — on the reliability of AI in anchored tasks.
What people ask about receiving without typing
Do we have to ask the supplier to change their delivery note?
No, and that is a design condition. Asking paint or component suppliers to adopt a specific delivery note format does not work in practice: each has its own ERP and its own templates, and the one who sells you least is the one least likely to change. Connect's vision interprets the note exactly as it arrives, in whatever layout it comes, and the same applies to the drum labels, whether GS1-128, QR, barcode or plain text. The adaptation is done by the system, not by the supplier or the person at the dock.
How long does receiving a truck like that actually take?
The realistic target is going from 30-45 minutes to 5-10. The bulk of the current time is not unloading: it is typing the delivery note line by line and copying the lot and expiry from every drum. With Connect that part becomes a handful of photos and a validation on the summary, where only the lines flagged as doubtful need attention. The side effect people usually appreciate most is demurrage: when the carrier stops waiting, that recurring cost disappears from the invoice.
What happens with lines the AI does not read confidently?
They arrive highlighted on the validation screen, and they are the only ones requiring intervention. The system does not hide its uncertainty to look more effective: if a lot is printed on a label that is creased or paint-stained, it flags it. The person corrects that specific field — not the whole record — and validates. It is an important difference from typing: when typing, the error also exists but nobody knows where it is; here the system points exactly where to look.
How does this translate into ERP licenses?
The same way as in the lab, by counting how many people need access to the receiving module today only to book goods in. Typically that is 2 or 3 active licenses. With Connect the entry happens by API and only one person validates, so the rest no longer need access to that module: the usual reduction is between 50 and 70%. It is a recurring saving and an easy one to audit, because it comes straight from the number of contracted users against the number who really need to operate the module.
Why does the basecoat drum lot matter so much?
Because it is the link that holds all downstream traceability together. When a finish problem appears — uneven coverage, a shade out of tolerance, a recurring defect in a production window — the inevitable question is which basecoat lot it came from. If receiving was typed in haste and that lot was badly associated, the investigation stops there and has to proceed by elimination. Closing traceability at the moment of receipt takes seconds; reconstructing it weeks later, when parts are already at the customer, costs far more and is sometimes impossible.
One morning at your receiving dock is enough for us to size it.
We work on your plant's real data, not ours. We look at your actual delivery notes and labels and calculate the case with you. Assessment with no commitment.
See how we apply it in your plant — demo at your dock ‹ See all 12 paint & assembly cases See automotive