Know before you count.
A pre-receiving sanity check.
Attach a photographed or scanned shipping document — a delivery note, a packing slip — and EvoSoft OCR reads it and checks it against the purchase order lines you're about to receive. It's a prerequisite to the physical count, never a replacement for it: the warehouse floor is still the only source of truth.
All three lines still load for receiving regardless of match outcome — a low-confidence flag is information for the warehouse team, never a reason to withhold a line.
- Lines withheld on low confidence
- 0
- Physical count changes
- None
- Matching approach
- Deterministic
- Documents per batch
- Multi
PO lines ever withheld on low confidence
Changes to your physical receiving process
PO-line matching — auditable, not a model guess
Documents supported per receiving batch
Reading is probabilistic. Matching isn't.
A vision-capable model is genuinely good at turning a messy photo into structured text. Deciding which PO line that text corresponds to is a different kind of problem — one that has to be code you can test and audit, not a judgment call left to the model.
-
Attach, don't replace
Attaching a shipping document is entirely optional. Skip it and PO lines load exactly as they do today — nothing about the existing "Get PO Lines" flow changes.
-
Deterministic matching
Exact item-number match first, then supplier cross-reference — plain, testable logic, not a model guessing which line is which.
-
Two confidence numbers, never blended
How sure the model is about what it read, and how sure the matcher is about the correspondence, are answers to different questions — reported separately, always.
-
Never holds up receiving
If the check times out or fails, every PO line still loads — the physical count and the rest of your process proceed exactly as normal.
-
The floor is still the source of truth
This check only ever annotates suggested PO lines before counting starts. It never writes to, replaces, or short-circuits the physical scanning and counting that follows.
-
Not just for receiving
Warehouse GRN reconciliation is the first integration — the same extract-then-match approach applies anywhere a document needs checking against known records, e.g. expense recognition.
A step before you count, not instead of it
Nothing about your existing receiving workflow changes — this slots in right before physical counting begins.
-
Attach the shipping document(s)
Photograph, scan, or attach a PDF of the delivery note or packing slip when retrieving PO lines — optional, and more than one document per batch is fine.
-
Lines load exactly as normal
Every PO line loads regardless of what the check finds — the check only ever adds an annotation on top, never withholds a line.
-
Count with the flags in view
Confirmed, not confirmed, or low-confidence — the warehouse team sees it before they start scanning, physical counting proceeds exactly as it always has.
Common questions
Can a low-confidence result block receiving?
No. Every PO line loads regardless of the check's outcome — a flag is information for the warehouse team, never a gate.
Does this replace physical scanning and counting?
No, and it's not designed to. Physical scanning remains the one real confirmation in the process — this only ever runs before it, on the suggested PO lines, and never touches the physical count records.
What happens if the check fails or times out?
The rest of the process is unaffected — PO lines still load, and you proceed with the physical count as usual.
Is this specific to warehouse receiving?
No — GRN reconciliation is the first integration built on a general-purpose document-extraction-and-matching surface. Other use cases (e.g. expense recognition) are expected to reuse the same underlying API.
Ready to check
before you count?
EvoSoft OCR is available by request. Tell us about your receiving process and we'll get you set up.
Request access