← All postsCatch weight

How to receive a catch-weight purchase order when the box never weighs what the PO says

iotoms team · August 30, 2026 · 5 min read

A seafood distributor running two trucks and a single cold-dock receives twelve pallets of frozen fillets on a Tuesday morning. The purchase order is clean: 400 cases, nominal weight 10 lbs a case, cost $6.20 a pound, total cost baked into the PO before the truck even leaves the vendor's yard. The receiving clerk checks the case count against the packing slip, signs, and moves on to the next delivery. Case count matched. Everyone assumes the PO is done.

Three weeks later the accounts team is reconciling vendor invoices and finds the vendor billed $700 over what the PO said. Nobody can say why, because nobody weighed anything at the dock — the PO was received on the nominal weight, and frozen fillets never actually weigh the nominal weight. Every case is a little under or a little over. On 400 cases, that drift adds up to real money, and it's now an argument with a vendor who has the scale tickets and the distributor doesn't.

The gap is between "ordered" and "received," not "received" and "billed"

Most catch-weight conversations focus on the invoice: does the number the vendor billed match what came off the truck. That matters, but it's the second problem. The first problem happens earlier, at receiving, and it's simpler to fix because it doesn't require chasing a vendor after the fact — it just requires capturing the right number before the goods ever go into stock.

A purchase order for a catch-weight item is placed against a nominal weight because that's the only number anyone has before the product exists. Ten pounds a case is an estimate, not a promise. The vendor's own scale at packing is more accurate than the label, and the receiving dock's scale is more accurate still, because it's measuring the actual product in front of the actual clerk, not a number printed weeks earlier.

The fix isn't "trust the vendor" or "distrust the vendor" — it's "reprice at the point where you have the best number." That point is the dock scale, at receiving, before the stock is put away and before the cost is posted to inventory.

What actually has to happen at the dock

Receiving a catch-weight PO correctly means three things happen in order, not three things that get reconciled a month later:

  1. The case count is checked against the PO and packing slip, same as any receipt.
  2. Each case, pallet, or lot is weighed on the dock scale, and that weight — not the nominal weight on the PO — becomes the received quantity.
  3. The PO line reprices against the weighed total, using the same per-pound cost the PO was negotiated at, so the cost basis going into inventory is the actual weight times the agreed rate — not the nominal weight times the rate.

If the PO said 400 cases at 10 lbs (4,000 lbs nominal) at $6.20/lb, that's $24,800 on paper. If the dock scale says the actual total was 3,968 lbs, the receipt should post at $24,601.60 — not $24,800, and not whatever number eventually shows up on the vendor's invoice. The inventory that lands on the shelf carries a cost basis that matches what physically arrived, and the variance between nominal and actual is visible immediately, by vendor and by SKU, instead of buried until the invoice reconciliation happens weeks later.

This also changes what "received" means for stock counts. If the system only tracks cases, a receiving clerk can match case count and move on while the actual product on the shelf is 32 lbs lighter than what the ledger assumes. Tracking weight at receipt means the stock count and the cost both reflect reality from minute one.

Why this gets skipped

Weighing at receiving takes longer than checking a case count off a clipboard, and on a busy dock morning that's a real cost. The usual shortcut is to receive on nominal weight and let accounts payable sort out the difference when the invoice lands — which is exactly how the seafood distributor above ended up disputing a $700 gap with no scale data of its own to argue from.

The other reason it gets skipped is tooling: if receiving a catch-weight PO means pulling up a spreadsheet, re-typing a weight, and manually adjusting a cost field, clerks will avoid it under time pressure. It only sticks as a habit when weighing and repricing is the fast path, not an extra step bolted onto the normal one.

What to check before your next catch-weight delivery

  • Can your receiving flow capture a weight per case or per lot, not just a case count? If not, you're receiving on faith.
  • Does the system reprice the PO line automatically from the weighed total, using the negotiated rate? Manual repricing gets skipped under pressure — it should happen the moment the weight is entered.
  • Is the variance between nominal and actual weight visible per vendor, not just totaled across a month? A vendor whose product consistently runs light needs a conversation before it needs a dispute.
  • Does the inventory cost basis update from the receipt, not from the invoice? If stock value is still keyed to nominal weight after receiving, every margin report downstream is working from a wrong number until someone manually corrects it.
  • Is the scale ticket or weighed total stored against the receipt, so if a vendor invoice disagrees weeks later, there's a number to argue from that isn't "we think it was about right"?

iotoms handles catch-weight items this way at receiving: cases in, weight captured per lot, the PO line repriced against the weighed total automatically, and the variance logged by vendor so a pattern shows up before it becomes a write-off.

See your own routes running on iotoms

Book a demo