A pallet arrives from your supplier. The packing slip says 500 units, but receiving counts 460. With another truck to unload and three more POs waiting, the 40-unit gap never gets recorded. Instead, all 500 units are received in the system.
Weeks later, the warehouse runs out of that SKU while the system still shows units available. An order comes in that the team cannot fulfill, and nobody immediately knows why the recorded count and the shelf disagree. The problem started at the dock door: 40 units that never arrived were added to inventory.
A short-shipped PO is a supplier issue that also needs a clear record in your receiving and inventory workflows. If the physical count is not reconciled with the PO, the discrepancy can sit unnoticed until an order exposes it.
What actually happens when a PO comes in short
A receiving discrepancy starts with a simple comparison: the PO says 500 units, but the team physically counts 460. What happens next determines whether the shortage becomes an inventory error, an unresolved supplier issue, or both.
If someone records the full PO quantity as received, on-hand inventory increases by 500 even though only 460 units arrived. The system now includes 40 units that do not exist on the shelf.
If someone records the correct physical count of 460, on-hand inventory may be accurate. But the remaining 40 units still need a documented status. Are they arriving in a later shipment? Is the supplier disputing the shortage? Has purchasing cancelled the balance or adjusted its replenishment plan? Without that follow-up, the PO and the teams relying on it can remain out of step.
These are different problems, but they begin at the same point: the quantity received does not match the quantity expected, and nobody closes the gap.
How a receiving discrepancy becomes an unexpected stockout
The 40-unit gap may not cause an immediate problem. It remains in the system as an overstated on-hand balance: inventory records include units that never arrived. As orders come in, available-to-promise counts down from that inflated number.
Eventually, the last physical unit is picked while the system may still show stock available. More orders can be accepted, but the warehouse cannot fulfill them. The first visible sign may be a failed pick, a cancelled order, or a customer asking why a confirmed order cannot ship.
By then, the receiving error could be weeks old. If nobody recorded the original shortage, the team has to work backward through receipts, PO lines, adjustments, and physical counts to find where the 40-unit difference began.
Why this compounds fastest right before peak season
Receiving volume often rises as teams prepare for Q4. More POs, more deliveries, and less time to investigate each receipt can make shortages or damaged units easier to miss. The pressure is especially high when new team members are learning the SKU catalog and receiving process.
A 40-unit discrepancy on a slow-moving SKU might go unnoticed for weeks. On a product you expect to sell heavily during Black Friday, that same gap can turn into accepted orders the warehouse cannot fulfill. If your process relies on someone remembering to follow up after the truck leaves, peak season puts that process under more pressure.
Why "count more carefully" doesn't fix it
The instinct is to tell receiving to be more careful, or to add a second count as a check. That helps at the margin, but it doesn't solve the actual problem: even a careful count that gets logged correctly still needs to propagate — to the PO status, to the supplier record, to available-to-promise, to whichever channel is showing that SKU as in stock. A receiving discrepancy that's caught on the dock but not corrected everywhere downstream is still a receiving discrepancy; it's just one a human happened to notice instead of one that got automatically flagged.
This is the same failure mode behind an unreconciled return corrupting a SKU for months — a single event creates a gap between what one system records and what's physically true, and unless something is specifically watching for that gap, it just sits there until an order finds it.
SuppliFlex treats a short receipt as exactly that: an exception, not a rounding error. When a receiving discrepancy shows the PO quantity and the confirmed count don't match, it's surfaced in the exception inbox with the SKU, the supplier, and the size of the gap — flagged for someone to resolve, not buried in a report nobody opens until month-end. That's the difference between visibility and a response path: a dashboard can show you that a SKU's count changed; an exception inbox tells you which receipt caused it and gives someone an action to take before it turns into a stockout three weeks later.
What to check this week
You can start by checking how your team records and resolves short receipts:
Pull a sample of recent POs and compare ordered quantity with confirmed received quantity, line by line. For each difference, check whether the remaining units are documented as a partial shipment, supplier dispute, cancellation, or approved adjustment. A gap is worth investigating when there is no clear explanation or follow-up.
Ask your receiving team what happens when the physical count is short. Is the difference entered into a system and assigned to someone, or is it discussed verbally and left for later? Then check whether inventory availability reflects the confirmed receipt and whether purchasing can see what is still outstanding.
If you receive inventory at more than one location, run this check by location and SKU. A shortage at one warehouse or 3PL can be harder to spot when teams are looking only at combined inventory totals.
If this sounds like your dock right now
If you're heading into Q4 without a clean way to catch a short-shipped PO before it becomes a phantom stockout, that's worth a closer look before volume ramps up, not after the first cancelled order. Book a 20-minute diagnostic and we'll walk through your actual receiving and reconciliation setup — no pitch, just a look at where your numbers are most likely to split. Book a diagnostic session here.