When you scan a barcode, you really want to know just one thing: is this right? Most scanning solutions never answer that question. They record the code and leave the checking to you. ScanVerify takes a different approach: every scan immediately receives one of three statuses — expected, unexpected or duplicate. It sounds simple, and that is exactly the point.
The three statuses explained
Expected
The scanned barcode is on the project's expected list and hasn't been scanned before. This is the status you want to see: the right item, on the right order, exactly once. Project progress counts up automatically, so the dashboard shows how much is still missing.
Unexpected
The barcode is not on the list. That can mean many things: a wrong box on the pallet, an item belonging to another order, a shipment assembled incorrectly. What matters is that you know now — on the floor, with the pallet still in front of you — not next week when the customer reports a wrong delivery.
Duplicate
This barcode was already scanned within the project. Without this status, duplicate scans silently become duplicate rows in your records: a count that doesn't add up, stock that drifts, an invoice that's too high. With the duplicate status you see it immediately and decide what to do.
Why a status per scan beats checking afterwards
Checking afterwards — comparing an export against the order list in Excel — has two fundamental problems. First, time passes between the error and its discovery, and in that time the pallet is wrapped, the truck has left or the count is closed. Second, it's manual work, and manual work is the first thing skipped when it gets busy — precisely when most errors happen.
A status per scan solves both. The check costs zero extra actions (the audio cue and the colour on screen do the work), and it happens at the only moment the error is still cheap: now.
An error caught at the loading dock costs a minute. The same error at the customer costs a return, a credit note and trust.
Reliability starts with the read itself
A status is only as reliable as the code that was read. That's why ScanVerify checks read quality first: EAN-13, EAN-8 and UPC-A are validated against their check digit, and other codes are only accepted after a silent double confirmation across two consecutive camera frames. Prefixes added by hardware scanners (AIM, GS1) are stripped automatically. Only then is the status determined.
How this fits into a complete warehouse process is covered in Barcode scanning and verification in the warehouse.
Frequently asked questions
Can I see when something was scanned?
Yes. Every scan is logged with its timestamp and status in the history, and that information travels along in the export to your own system.
What happens to unexpected scans in the export?
Unexpected and duplicate scans are recorded too, including their status. Your ERP or WMS gets the full picture, not just the successful scans.
Where does the expected list come from?
You import it per project, for example as a CSV from your own system. See the documentation for the steps.
Want to see ScanVerify in action?
Download ScanVerify from the Google Play Store and start scanning, verifying and connecting right away. Completely free during the introduction phase.
Nu beschikbaar inGoogle Play