Why your vendor invoice weight never matches what came off the truck
iotoms team · August 19, 2026 · 4 min read
A produce and protein distributor runs one receiving dock behind three vans. Purchase orders go out in cases — forty-count boxes of tomatoes, forty-pound cases of chicken thigh — because that's how vendors quote and invoice. Every case that comes off the truck gets a checkmark against the PO: case count matches, driver signs, invoice gets keyed into the ledger at the billed weight. Nobody weighs anything. Why would they? The case count is right.
Six months later, someone finally puts a scale at the dock, mostly to settle an argument about whether the vans were getting shorted on load-out. The scale tells a different story than the invoice. A case billed at 40 lb comes in at 37.4 lb. Another comes in at 41.1 lb. Across a week of deliveries from the same vendor, the average lands consistently under the billed weight — never wildly, never enough to trigger a complaint on any single delivery, but every single time.
The gap that never shows up on one invoice
This is the trap with catch-weight goods. The purchase order is written in a nominal unit — cases, crates, boxes — because that's how ordering and case-count logistics work. But the actual product inside each case varies: trim loss, moisture loss, pack-line tolerance, sometimes just a vendor rounding every case down instead of up. The invoice bills the nominal weight, not the real one, and nothing in a case-count check catches that difference.
A single case being three percent light doesn't move anyone to act. It's inside the range a receiving clerk would wave through without a second thought. But three percent light, on every case, from one vendor, every week, for six months, is not noise — it's a systematic short-ship that never once crossed a threshold anyone was watching. The distributor was paying invoice price for product weight that was never actually delivered. On thin protein and produce margins, that gap alone can be the difference between a profitable route and a break-even one.
The compounding part is what makes it expensive rather than just annoying. It doesn't show up as a loss on the P&L — it shows up as slightly worse gross margin on every load built from that vendor's stock, spread across every van, every customer invoice, every week. Nobody investigates "margin was down half a point again" the way they'd investigate a single bad shipment. The cost hides precisely because it's distributed instead of dramatic.
What it takes to actually catch it
The fix isn't spot-checking deliveries harder. It's changing what gets recorded at receiving, and then watching that record over time instead of per delivery.
Weigh every case at receiving, not a sample. A sample only tells you the sample was fine. Systematic short-shipping is invisible unless every unit gets a real number attached to it, because the whole pattern is designed to survive a spot check.
Net out tare before you compare anything. The scale reading includes the crate, the ice, the packaging. Compare the billed weight to the product weight, not the gross weight, or you'll chase a variance that's actually just a heavier pallet.
Record expected weight against measured weight on every line, not just count against count. The PO says 40 lb. The scale says whatever the scale says. That per-line delta is the actual signal — case-count matching is a different check entirely and tells you nothing about weight.
Track the variance by vendor over time, not by delivery. One light case is a rounding error. A vendor whose average variance is persistently negative across dozens of deliveries is a pattern worth a conversation — and worth a credit. The only way to see that pattern is to log every variance against the vendor it came from and look at the trend, not the single event.
Set a threshold that turns a pattern into an action. Once variance by vendor is visible, decide in advance what triggers a dispute, a credit request, or a sourcing conversation — a running average past a set percentage, say, rather than reacting to whichever delivery happens to get noticed.
The takeaway
If you're buying anything by the case and it's actually priced by weight — produce, meat, poultry, seafood, bulk dry goods — case-count receiving alone will never catch a vendor who's consistently light. The checklist:
- Weigh every case at receiving; don't sample.
- Net out tare before comparing to the invoice.
- Log expected weight vs. measured weight per line, not just unit counts.
- Roll variance up by vendor across weeks, not deliveries.
- Set a variance threshold that automatically flags a vendor for a credit request or a sourcing review.
This is exactly the gap iotoms' catch-weight inventory is built to close: every receiving line records expected weight against measured scale weight with tare already netted out, and that variance rolls up per vendor automatically — so a pattern that used to take six months and an argument to notice shows up the first week it starts.