Four Things a Scan Does Not Decide
Our scanner bridge turns a phone into a scanner paired to a desktop session, and every scan lands as an auditable event with a device, an actor, a resolution and an exception code. It is one of the better things in the product. It also decides exactly one thing, and buyers routinely assume it decides four.
A scan answers one question: what is this? Everything else you might want at the moment of the beep — how many, who says so, which one, and whose it is — is a separate question that the barcode cannot answer and the system does not pretend to.
That sounds obvious written down. It is not obvious in a warehouse at seven in the morning, and it is not obvious in a demonstration, where a scan and a stock movement happen half a second apart and look like one act.
What the bridge actually is
A person at a desktop opens a session. A phone pairs to it with a token that has a fingerprint, a last-used time, a soft expiry and a hard expiry, and can be revoked. From then on the phone is a scanner for that session and the desktop is the screen.
Each scan is stored as an event, and the event is far richer than a barcode. It carries the code, when it was scanned, the device label and fingerprint, the address it came from, who the actor was, what the code resolved to and with what status, an exception code if it resolved to nothing, the action that was chosen afterwards, and when the event was consumed.
That is a genuinely auditable capture. A month later you can answer which device scanned what, when, under whose account, and what happened next — including the scans that failed to resolve, which are usually the interesting ones.
The scan is evidence of an identification. It is not evidence of a decision.
The four things it does not decide
-
How many
A barcode identifies a product, not an amount. Every item carries its own unit — pieces, cartons, kilograms — so the system knows what one of a thing is. What it cannot know is whether that beep meant one bottle, one case of twelve or one pallet, because there is no pack conversion behind the barcode, so the person scanning still types the quantity in the item's unit. More on quantities in the quantity post.
-
Whether it is allowed
Scanning is identification; approval is a separate act with its own permissions, its own value threshold and its own separation of duties. A scan cannot approve a write-off and should not be able to. Where this catches people out is in expectations: a scanned adjustment is not a fast-tracked one.
-
Which unit this is
A product barcode is the same on every unit of that product. Individual identity needs a serial. Serial numbers are recorded as stock moves, each with its own status, but a scan is matched to the product rather than to the serial on the unit. So a scan tells you the model, and the serial is a second thing somebody records.
-
Whether it is yours
Ownership lives on the item — owned, a customer's, or a supplier's consignment, with held stock kept out of valuation and the ledger — and the scan inherits whatever the item says. It cannot tell your units from held units of the same product on the same rack, which is why held stock belongs on an item of its own.
Why this matters more in a scattered, high-turnover operation
Peruvian distribution — Lima out to the regions, mining and industrial supply into remote sites, retail across a geography with real logistical friction — has two characteristics that make the boundary important.
The first is that the person scanning is often the only person present. There is no supervisor at the receiving door of a remote site. The scan is the whole record of what arrived, which means everything the scan does not carry has to be carried by the process around it.
The second is staff turnover. A scanning workflow is learned in an hour, which is its great virtue, and the four boundaries above are learned by being told. Nobody discovers them from the interface, because the interface behaves identically whether the operator understands them or not.
| The assumption | What actually happens | What to put in the process |
|---|---|---|
| One beep is one unit | The quantity is whatever is typed after the scan | Fix one scanning convention per catalogue and put it on the wall, in words |
| A scan confirms the goods are ours | It confirms the product exists in the catalogue | A separate check against the delivery note; the system will not do it |
| A scan proves who received it | It records who was signed in on the device | Personal logins, not a shared warehouse account — this is the single highest-value discipline here |
| A failed scan is a bad barcode | It is an exception event with a code, stored | Review unresolved scans weekly; they are your best data-quality signal |
| A scan is an approval | It is an identification; approval is a separate gated act | Do not design a process that assumes scanning shortens the approval chain |
The fourth row is the one nobody uses and everybody should. Unresolved scans are recorded with an exception code. A weekly look at them will find your missing barcodes, your duplicate labels and your untrained operators faster than any report designed for the purpose.
The capture is the hard part, and it is done
Everything on this page that is still to come sits downstream of a capture layer that already exists and is properly auditable. That is worth saying plainly, because it changes the size of the work.
Serial capture at the scan
The event already carries a resolution and an action, and serials are already written as stock moves. What is being built is the wire between them and the decision about what happens when a serial scans twice.
A pack-size convention the system knows
A pack size with a conversion into the item's own unit would let one beep mean twelve without anybody remembering. The unit is already on every item; the conversion is the larger of the two remaining pieces.
An exception queue with an owner
Unresolved scans are stored with codes today and nothing pushes them at anybody. A queue with an assignee is small work with a fast payback.
We put scope on a public page and dates in a written quote. Tell us how your receiving door actually works and we will come back with a written scope, timeline and cost before you commit.
Scope the scanning workflowThree questions that find the edge of any scanning claim
Scan something that is not in the catalogue. Show me what is stored.
A good answer sounds like
An exception event with a code and a timestamp, retrievable later.
What it actually means
Many systems store nothing at all for a failed scan, which means your data-quality problems are invisible by construction.
Who does a scan say it was?
A good answer sounds like
A named user, from the session, on a device that can be identified and revoked.
What it actually means
If the answer is the warehouse, you have a scanning system with no accountability layer, whatever the audit trail looks like.
What does one scan add to stock?
A good answer sounds like
A number the operator supplies, or a configured pack size.
What it actually means
Ours is the former. The distinction decides how much training your process needs and how many transpositions you will live with.
Our position
Use the bridge — it is fast, it is auditable, it costs nothing in hardware, and the event record is better than most. Then put four things in the process rather than in the system: one scanning convention for quantity, personal logins on every device, a separate check that the goods are yours, and a weekly review of unresolved scans. None of those are features you can buy your way out of here, and all four are cheap if you decide them before go-live.
What AWRA OpsHub does today
- A phone-to-desktop scanner bridge with token pairing, device fingerprinting, soft and hard expiry, last-used tracking and revocation.
- Every scan stored as an event carrying the code, the device, the actor, the address, what it resolved to, the resolution status, an exception code where it failed, and the action chosen afterwards.
- A unique barcode per item, enforced at the database level.
- Scanning against items and locations, and mobile capture that survives losing signal for the operations that support it.
- Barcode and QR label generation for items, assets and locations.
- Serial numbers recorded as stock moves, with a status per movement.
- Ownership on every item — owned, customer or consignment stock — so goods you are merely holding stay out of valuation and the ledger.
- A unit of measure on every item — whole numbers for pieces and cartons, up to three decimals for kilograms and litres.
More we can add to your workspace
- Quantity meaning on a scan: a pack size converting into the item's own unit, so one scan of a case means twelve pieces rather than whatever the operator types next. Commission it
- Serial capture at the scan, so a beep resolves to the individual unit rather than to the item. Serials are recorded per movement today; reading one from the scan is being built. Commission it
- Ownership resolved per unit at the scan, so your stock and held stock of one product can share a barcode. Ownership is set per item today. Commission it
- An exception queue. Unresolved scans are recorded with codes and nothing surfaces them to a person. Commission it
- An approval authority. Scanning identifies; approving is a separate, gated act. Commission it
Where we point you to a specialist
- The capture layer is genuinely good and we would rather you used it than not. This page is about the boundary of what it claims, not a caution against it.
- Personal logins are a process decision available to you today and they are the difference between an audit trail and a warehouse-shaped fog.
- This is market-neutral. It is what a barcode is; Peru is where a remote receiving door with one person at it is most likely to be your reality.
Design the receiving door, not the scanner
The scanner works. The decisions that make it useful are about conventions and logins, and they take an hour to agree. Bring your receiving process and we will go through it.
Walk the processFrequently asked questions
Do I need special scanning hardware?
No. The bridge pairs an ordinary phone to a desktop session over a token, so the device most of your team already carries is the scanner. Dedicated hardware is faster in a high-volume lane and unnecessary everywhere else.
What stops a paired phone being used later by somebody else?
The token carries a device fingerprint, a soft expiry, a hard expiry and a last-used time, and it can be revoked. That is a real session model rather than a permanent pairing, which is the right design — but it does not replace personal logins, because the session belongs to whoever opened it.
Can I scan a location as well as an item?
Yes, and locations can be labelled. That is what makes a two-scan workflow possible at the bin — scan the place, scan the thing — which is the cheapest accuracy improvement available in this product.