A Short Delivery Is Not a Refusal
Receiving more than was ordered is refused. Receiving less is reported and accepted. That asymmetry is the whole design of the check at the receiving door, and the reasoning behind it applies to a great many controls that get built symmetrically and then bypassed.
A hundred were ordered. Ninety arrive. The lorry is at the door and the goods are on the floor. A system that refuses to book them in has not prevented anything; it has just moved the record into somebody's notebook.
The check at the receiving door compares what is arriving against what was ordered, and it treats the two directions completely differently. Over is blocked. Under is noted. Most people's instinct is that a control should be symmetrical, and this is a good case for why that instinct is wrong.
Why over-receipt is blocked
Two separate reasons, and either alone would justify it.
-
It is a fraud vector with a well-known shape
The classic version is a receipt padded to cover an inflated invoice. Goods are booked in that never arrived, the paperwork matches, and the payment goes out against an order that appears fully delivered. Nothing downstream questions it because every document agrees.
-
It is a stock accuracy problem even when it is honest
An over-receipt booked without question becomes real stock — quantity nobody ordered, sitting in the system, feeding reorder calculations and stock valuations. A supplier who ships ten per cent extra as a matter of course quietly inflates your balance sheet.
Why short delivery is not
Because a short delivery is normal. Partial shipments, back-orders, a supplier splitting an order across two lorries — these are ordinary events in every supply chain, and there is nothing to prevent. The goods that did arrive are physically present and need booking in.
And because of the second-order effect, which matters more than the first. A control that refuses to record goods sitting on a warehouse floor gets bypassed. The stock is put away, the paperwork is done later or not at all, and the system stops describing reality — at which point every other control that reads stock levels is also compromised. Blocking a short receipt would trade one accurate refusal for a whole category of untracked stock.
A control people work around is worse than no control, because it looks like one.
The check counts everything received, not this delivery
This is the half that makes it a real control rather than a courtesy, and it is worth being explicit about because the naive version is genuinely defenceless.
The comparison is cumulative. What is measured is everything ever booked against the order plus what is arriving now, against the ordered quantity. If it read only the current delivery, an order for a hundred could be received a hundred today and a hundred again tomorrow, and neither delivery would exceed the order on its own. Every downstream document would agree and nothing would have fired.
An order for 100, delivered twice
A per-delivery check would have accepted both, because neither exceeds the order on its own. The message names all four figures — what is arriving, what that would make the total, what was ordered, and by how much it is over.
The tolerance, and the setting people reach for instead
The over-receipt tolerance ships at zero: any excess at all is an exception. There is a separate switch that decides whether an exception blocks or merely reports, and it ships on.
The intended lever is the tolerance. An organisation whose suppliers routinely ship two or three per cent over — common with anything measured by weight or cut to length — raises the tolerance to match their reality, and the guard keeps working for everything outside it. The lever people reach for first is the blocking switch, and turning that off disarms the check for every excess of every size while leaving the exceptions being generated and ignored.
| Situation | The right adjustment |
|---|---|
| Suppliers ship slightly over by nature of the goods | Raise the tolerance to just above what is normal for them. |
| One supplier is chronically over | Leave the tolerance and take it up with the supplier. The exceptions are the evidence. |
| Receiving staff are blocked constantly | Look at whether orders are being amended after the fact rather than at the guard. |
| You want a record but not a refusal | Turn blocking off deliberately, and make sure somebody is reading the exceptions. |
Where the check does not apply
Stock arriving with no purchase order behind it — opening stock at go-live, a donation, a customer return — has nothing to be measured against, and the check says so and stands aside. That is the honest behaviour: an absent order is not a failed comparison, and treating it as one would block every legitimate receipt that did not originate in purchasing.
Worth noting for anyone reconciling: those receipts are real stock movements with no order to match them, so a receiving report filtered to matched receipts is not a complete picture of what came in.
Turning exceptions into information
The guard blocks what it should and records what it sees. What organisations ask for next is the reporting layer above it — who is over, how often, and by how much.
Over-receipt by supplier
How often each supplier exceeds an order and by what margin, which turns individual refusals into a conversation with a name on it.
A recorded override
Accepting a specific over-receipt with a reason and an approver, rather than raising the tolerance for everybody.
A short-delivery ageing report
Outstanding quantities by age, so a back-order that never arrived is chased rather than forgotten.
We publish scope, not dates.
Scope receiving controlsWhat AWRA OpsHub does today
- A comparison at the receiving door between what is arriving and what was ordered, run before the receipt is booked.
- A cumulative measure counting every prior receipt against the order, so a second full delivery is caught where a per-delivery check would accept it.
- An exception naming the item, what was ordered, what had already been received, what is arriving and by how much the total would exceed the order.
- A per-organisation over-receipt tolerance, shipping at zero, and a separate switch deciding whether an exception blocks or reports.
- Short deliveries accepted and recorded rather than refused, so goods physically on the floor can always be booked in.
- Receipts with no purchase order behind them — opening stock, donations, returns — passed through rather than treated as failed comparisons.
- The whole check keyed on the item identifier as a string, because collapsing it to a number would match no line and silently disarm the guard.
More we can add to your workspace
- An over-receipt report by supplier, showing frequency and margin, so a chronic pattern becomes a conversation rather than a series of individual refusals.
- A recorded override for a specific delivery, accepted with a reason and an approver, instead of raising the tolerance for every supplier.
- A short-delivery ageing report, listing outstanding quantities by age so a back-order that never arrived is chased.
- A per-supplier tolerance, so the one who ships by weight and the one who ships in boxes are not held to the same margin.
- A prompt to amend the order when an over-receipt is genuinely a change of scope rather than an error.
- A notification when an exception is raised, so a refusal at the door reaches purchasing without the receiver having to explain it.
Where we point you to a specialist
- We will keep refusing to block a short delivery. Goods that are physically present have to be recordable, and a control that stands between a warehouse and its own stock is one that gets worked around within a week — after which the system stops describing reality and every control that reads stock levels is weaker for it.
- Setting your over-receipt tolerance is an operational judgement about your suppliers and your goods, and it stays yours. Zero is the correct default because it is the only one that is right everywhere until somebody knows their own trade.
- Whether an over-delivery may be kept, returned or invoiced is a matter between you and your supplier under your terms of purchase. We will refuse to book it in silently and record what was presented; the commercial decision belongs to the two of you.
A recorded override is the contained piece most organisations want first, because it lets a genuine one-off be accepted by a named person without weakening the guard for everybody else.
Our take
The asymmetry is the point, and it is the part worth taking away even if you never use this particular product. Controls are usually specified symmetrically — check both directions, block both directions — and the ones that survive contact with an operation are the ones that block where the risk is and record where it is not. Over-receipt is a fraud vector and a stock accuracy problem; short delivery is Tuesday. The other decision that makes this a real control rather than a gesture is that it counts cumulatively, because the interesting version of the attack is not one delivery of a hundred and ten but two deliveries of a hundred. If you are evaluating a receiving check anywhere, that is the question to ask first.
Check your tolerance before you blame the guard
Constant refusals at the receiving door usually mean either a tolerance that does not match your goods or orders being amended after delivery. Both are quick to establish and neither is fixed by switching the check off.
Talk through receivingFrequently asked questions
Why can I not book in a delivery that is over the order?
Because an over-receipt is both a recognised fraud pattern — a padded receipt covering an inflated invoice — and a stock accuracy problem, since the excess becomes real stock nobody ordered and feeds reordering and valuation from then on. The refusal names the item, what was ordered, what had already arrived, what is being presented and by how much the total would exceed.
What if my supplier always ships slightly over?
Raise the over-receipt tolerance to just above what is normal for your goods. That is the intended lever and it keeps the guard working for everything outside the margin you have accepted. Turning off the blocking switch instead disarms the check for excesses of every size while still generating exceptions nobody reads.
Does a short delivery stop anything?
No. Short deliveries are accepted and recorded, because partial shipments and back-orders are ordinary and because goods sitting on a warehouse floor have to be recordable. What a short delivery leaves behind is an outstanding quantity on the order, which is what the receiving side of the process then tracks.
Can somebody get around it by splitting the delivery?
No, and this is the half that makes it a real control. The check measures everything ever booked against the order plus what is arriving now, against the ordered quantity. Two deliveries of a hundred against an order for a hundred are caught on the second one, even though neither exceeds the order on its own.
What about stock that arrives with no purchase order?
It passes through. Opening stock at go-live, a donation and a customer return have nothing to be measured against, and treating an absent order as a failed comparison would block every legitimate receipt that did not originate in purchasing. Worth remembering when reconciling: those movements are real and have no order behind them.
Who finds out when a delivery is refused?
Whoever is standing at the receiving screen. A notification to purchasing when an exception is raised is on the list above, and it is the piece that stops a refusal at the door becoming an argument between a receiver and a driver with nobody from purchasing in the conversation.
