Most inventory shrinkage doesn't happen at the point of sale. It happens at the receiving dock, in the ten minutes between a delivery truck arriving and a staff member signing for it. A case gets miscounted, a substituted SKU goes unnoticed, a damaged carton gets shelved anyway and none of it gets flagged, because most receiving processes are built to move goods onto shelves quickly, not to verify them accurately. The discrepancy doesn't disappear. It just resurfaces weeks later as an unexplained variance at cycle count, by which point there is no way to tell whether it was a supplier error, a receiving error, or theft.
The Blind Spot Between the Purchase Order and the Shelf
In most small and mid-sized retail operations, receiving works like this: a delivery arrives, a staff member checks the packing slip against the boxes on the pallet, signs for it, and moves the goods to the floor or the back room. The packing slip, not the original purchase order, is the reference document. That is the core problem: the packing slip reflects what the supplier says they shipped, not what you actually ordered or what you actually received.
When the packing slip and the physical delivery are checked against each other but never checked against the PO, three categories of error pass through undetected. A supplier can under-ship and note the correct quantity on the slip anyway, expecting the shortfall to go unnoticed. A picker on the supplier's end can pull the wrong case pack size, shipping 12-packs where 6-packs were ordered, and the slip may or may not reflect the substitution accurately. Or the shipment can simply be counted incorrectly at your dock, with a rushed staff member rounding a count instead of verifying it.
Every one of these errors becomes a phantom inventory number the moment the receipt is confirmed. Your system now believes you have stock you don't have, or is missing stock you actually received. Neither error is visible again until something forces a physical recount.
What Blind Receiving Actually Catches
Blind receiving is the standard fix for this blind spot, and it works by removing the one piece of information that makes sloppy counting possible: the expected quantity. In a blind receiving workflow, the staff member counting the delivery does not see how many units the PO expects, or what the packing slip claims was shipped. They count what is physically in front of them and enter that number. Only after the count is submitted does the system compare it against the PO and packing slip and surface any variance.
This matters because when a staff member can see the expected count while they're receiving, they tend to count toward that number rather than counting independently a documented bias that undermines the entire point of a verification step. Removing the expected quantity from view forces an honest, independent count, which is the only kind of count that can actually catch a discrepancy rather than just confirming one that isn't there.
- Short shipment: fewer units received than the PO specifies
- Overage: more units received than ordered or invoiced
- Substituted SKU: a different size, colour, or variant than what was ordered
- Damaged or defective goods received in otherwise correct quantities
- Mis-picked case packs: correct product, wrong unit-of-measure or pack size
The True Cost of an Unflagged Discrepancy
An unflagged short shipment doesn't just mean you have less stock than expected it means your inventory system now believes a lie. If a PO for 500 units is received and confirmed as 500 when only 480 arrived, your system's on-hand count is inflated by 20 units from the moment the receipt is posted. Those 20 units will eventually sell out of a count that never existed, producing an unexplained negative variance at the next cycle count. That variance gets coded as shrinkage, which is the wrong diagnosis: it wasn't stolen or lost, it was never there.
The financial impact compounds through your cost of goods sold. If the invoice is paid based on the original PO quantity rather than the quantity actually received, you've paid for units you don't have, and your landed cost per unit on the units you did receive is understated. Margin reports built on that understated cost will show better profitability than what actually exists a problem that only becomes visible when someone reconciles supplier invoices against verified receiving counts, which most retailers do rarely, if ever.
Building a Discrepancy Resolution Workflow
Catching a discrepancy at the dock is only useful if what happens next is structured. A discrepancy resolution workflow should flag the variance immediately at the point of counting, require photo documentation for damaged goods or visibly incorrect shipments, and route the flagged PO to the buyer responsible for that supplier relationship rather than leaving it for someone to notice later.
From there, the buyer decides how to resolve it: request a credit memo for a short shipment, initiate a return for damaged goods, or accept an overage and adjust the PO to match. Whatever the resolution, it needs to be recorded against the original PO so the eventual invoice match reflects what was actually received, not what was originally ordered. Without this closed loop, discrepancies get caught but never resolved, which just moves the reconciliation problem from the warehouse floor to accounts payable.
Vendor Scorecarding: Turning Discrepancy Data Into Leverage
A single discrepancy is a receiving problem. A pattern of discrepancies from the same supplier is a sourcing problem, and you can only see the pattern if every discrepancy is logged against the supplier that caused it rather than resolved and forgotten.
Tracking discrepancy rate by supplier over time short shipments as a percentage of total orders, average days to resolve a flagged discrepancy, frequency of damaged goods on arrival turns receiving data into negotiating leverage. A supplier with a 4% short-shipment rate across the last two quarters is a supplier you can bring hard numbers to, not a vague complaint. For high-volume categories, that data is often the difference between renegotiating terms and quietly absorbing the loss indefinitely.
Receiving discrepancies are one of the few sources of inventory error that are almost entirely preventable with the right workflow, because unlike theft or customer-facing shrinkage, the moment of error is a controlled, observable event: a delivery arriving at a specific dock, counted by a specific person, against a specific purchase order. Blind receiving, photo-documented discrepancy flags, and a defined resolution path close that gap. What remains after that is data supplier by supplier that tells you exactly where your receiving risk is concentrated.
Receiving That Catches Every Discrepancy, Automatically
Momentum's zero-friction receiving matches every delivery against open POs with barcode scanning, flags short shipments, overages, and damaged goods with one tap, and routes discrepancies straight to the responsible buyer. Try the live demo to see how a receipt gets verified in seconds, not guessed at.
