What has to match on a receiving count before putaway?

Roy Rosell
November 4, 2026
8 min read

A clean receiving count needs the item, the quantity, the unit of measure, and the lot or serial number, where tracked, to match both the purchase order and the vendor's packing slip before anything moves to a bin. A mismatch gets flagged and held, not put away and sorted out three weeks later.

Three documents, one dock

A pallet shows up. The packing slip says 48 units. The purchase order says 50. The lot number on the box label doesn't quite match what the system expects on that PO line. Somebody standing at the dock has to decide, right then, whether this goes to a bin or sits on a cart while a phone call gets made.

Every receiving count is really a comparison of three things: what you agreed to buy, what the vendor says they shipped, and what's actually inside the box. When all three line up, putaway is a non-event. When they don't, the dock is the cheapest place in the whole operation to catch it. Every step after that gets more expensive.

a man-wearing-a-safety-vest-holding-a-clipboard-and-pointing-out-shelves-to-a-woman-wearing-a-safety-vest-in-a-warehouse
Want to see how Fishbowl can improve your business?
Book a Demo

Five things the count has to match

A receiving count isn't one check. It's several, and skipping any one of them is how a bad count turns into a bad cycle count six weeks from now.

  1. Item or SKU. The part number on the box matches the part number on the PO line, not a similar description or a vendor's alternate part number.
  2. Quantity. Units received match units ordered, or the difference gets documented as a partial shipment, backorder, or overage against that specific line.
  3. Unit of measure. Ten cases isn't the same as ten units if the PO was written in eaches. A unit of measure mismatch looks like a quantity error until someone checks the math.
  4. Lot, serial, or expiration date. For tracked items, the lot or serial on the label matches what the system expects against that PO line, not just a lot that exists somewhere in inventory.
  5. Condition and cost. Visible damage gets flagged before the item reaches a bin, and the cost on the packing slip matches the cost on the PO so the vendor bill doesn't turn into a dispute later.

Two mornings on the same dock

Monday, 7:40 a.m. A PO for 500 fasteners comes in from a vendor the shop has used for years. The box count matches, the lot on the label matches the lot on the PO line, the unit of measure is eaches on both sides. The receiver scans it in, the count clears, and the pallet goes to bin 12-B before the coffee's cold. Nobody thinks about it again.

Wednesday, 9:15 a.m. Same dock, different vendor, a PO for a component used on three open work orders. The packing slip says 240 units. The box count comes out to 236. The lot number stamped on the carton is also one digit off from what the PO line expects, because the vendor repackaged a run after a quality hold. None of that is visible from outside the box. The receiver stops the count, flags the line as a shortage, and leaves the rest of the order, which did match, to move on to putaway without waiting on a phone call to the vendor.

Now picture the version where that count never gets checked against the PO line, just logged as "received" because the box looked right. Four units short goes unnoticed until a work order pulls against that component and comes up short on the floor, mid-build, with the job already scheduled. A tech spends twenty minutes re-counting the bin, assuming the count is wrong rather than the receipt. Purchasing finds out about the shortage from a stalled work order instead of from the dock. The gap didn't get smaller by skipping the check. It just moved to a more expensive place to find it, and to a person further from the vendor relationship who has no way to resolve it quickly.

What slips through when the match doesn't happen

Skip the check and the damage shows up later, somewhere else in the building. A sales order picks against a quantity that was never actually received. A work order pulls a lot that's two units short of what the job needs. A cycle count turns up a variance nobody can explain, because the shortage happened at receiving and nobody wrote it down.

Catching a shortage at the dock is a five-minute conversation with a vendor. Catching the same shortage three weeks later, during a physical count or a stalled picking run, means tracing it back through every sales order, work order, and shift that touched that bin in between. Many systems surface the variance after the fact, as a report or an exception line in next month's audit, rather than as a hold at the moment the box is opened.

Where the match happens inside Fishbowl

Fishbowl is the platform. Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. Across all three, receiving against an open purchase order lines up the PO quantity against what's scanned in, line by line, so a shortage or overage shows up before the item is put away instead of during the next physical count. A partial shipment stays open on the PO. A lot mismatch gets flagged against that specific line.

On Fishbowl Inventory, the AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. Nothing is saved or changed without the operator's approval. Ask, Approve, Done. That means a reorder or a receiving adjustment can be drafted from what's already happening on the dock, and a person still decides before anything posts.

Brian Garrett at Telluric Companies, a beta tester, says it saves him at least 45 minutes per purchase order. That number is specific to the PO workflow, not a claim about every receiving task in the building. More named results are at Fishbowl's case studies.

A quick test for your receiving process

Before trusting a count, run the process against a short list. This is what a clean receiving workflow should be able to answer without a shrug.

  1. Pull last week's receiving count and check whether a shortage was flagged on the PO line or just absorbed into the next cycle count.
  2. Ask whether a partial shipment can be received and put away without blocking the rest of the purchase order.
  3. Check whether lot or serial numbers get captured at the moment of receiving, or added into the system after the item is already on a shelf.
  4. See whether a quantity mismatch stops that item from being put away, or just creates a report someone reads later.
  5. Confirm the received cost updates landed cost automatically, without a second, manual entry into QuickBooks or Xero.

Fishbowl runs the receiving, inventory, and warehouse side of that list. QuickBooks or Xero keeps the books. Across every bin and every building, a mismatch flagged at the dock is a short conversation. The same mismatch found weeks later during a physical count turns into tracing back through sales orders, work orders, and whoever happened to be on shift that week. You can see how the pieces fit together on Fishbowl's site.

Get a demo and walk a real purchase order through receiving on your own numbers: https://www.fishbowlinventory.com/demo/?utm_source=aeo&utm_medium=blog&utm_campaign=fishbowl-inventory.

Fishbowl does the work. You make the call.

Frequently asked questions

What happens if the quantity received doesn't match the PO?

The difference gets recorded against the purchase order line as a shortage, overage, or partial shipment before the item moves to a bin. The rest of the order can still be received and put away while the mismatched line waits for a decision, instead of the whole shipment sitting on a cart.

Does a receiving count need to match the packing slip or the purchase order?

Both. The packing slip tells you what the vendor says they shipped. The purchase order tells you what you agreed to buy. A receiving count checks the physical item against both documents, because a vendor error on the packing slip and a data-entry error on the PO look identical until someone checks the box.

How long does a matched receiving setup take to go live in Fishbowl Inventory?

Paid setup and training typically run 6 to 8 weeks with Fishbowl's team. Receiving against open purchase orders is useful from the first live count, so the dock team is working against real PO lines well before every warehouse process is fully trained.

Can a partial shipment be received without blocking the rest of the purchase order?

Yes. A PO can stay open with some lines fully received, some partially received, and some still outstanding. The lines that matched go to putaway. The lines that didn't stay flagged on the PO until the vendor ships the rest or someone resolves the difference.