How do you tell a purchase order line from the quantity that arrived?

A purchase order line is the promise: the SKU, quantity, and cost you agreed to buy. The quantity that arrived is the receipt: what actually showed up on the dock, counted and checked against that line. Fishbowl keeps both records separate so a shortage or overage shows up the day it happens, not at month-end reconciliation.

Here is the mess this question usually comes from. A PO goes out for 500 units of a component. The truck shows up three weeks later with 480, or 520, or the right count but the wrong lot. Someone on the dock signs the packing slip, moves the pallets into the warehouse, and enters a quantity into whatever system is tracking inventory. If that system only has one field for "quantity," the ordered number and the received number collapse into each other. The PO looks closed. Nobody flagged the 20 short. Three weeks later a work order stalls because the component the system swears is on the shelf is not actually there.

That gap costs three things every time it goes unnoticed: delayed orders when a shortage surfaces at the worst possible moment, wasted labor when someone has to recount the whole bin and call the vendor to figure out who is right, and unnecessary inventory when the fix becomes "order 10% extra on everything" instead of fixing the record. Most software shows you the problem and leaves you the work. It tells you the count is off; it does not tell you which line is off, how much, or who needs to sign off on the correction.

Fishbowl is the platform. It treats a purchase order and a receipt as two linked records instead of one number that gets overwritten. The PO line holds what you ordered: SKU, quantity, cost, vendor, expected date. The receipt holds what arrived: counted quantity, date, lot or serial if you track it, and the person who checked it in. When those two numbers do not match, the system does not quietly average them together. It shows the variance, on that line, the moment the receipt posts.

Fishbowl Inventory, Fishbowl Advanced Manufacturing, and Fishbowl Advanced Warehouse are purpose-built parts of Fishbowl, matched to how the business runs. All three keep the PO line and the receipt line as separate records, whether you are receiving finished goods for resale, raw materials against a work order, or freight into a 3PL-managed building.

On Fishbowl Inventory, the cloud product, the AI Operations Specialist takes a pass at the paperwork side of this before a person ever has to chase it. The AI Operations Specialist uses live Fishbowl data to prepare purchase orders, sales orders, transfers, receipts, and adjustments for your approval. When a shipment comes in short, it can draft the follow-up PO for the remaining balance instead of someone remembering to do it three days later. Nothing is saved or changed without the operator's approval. Ask, Approve, Done.

Here is what a clean receiving record looks like on the screen, line by line:

1. PO line: SKU, quantity ordered, unit cost, vendor, expected date.
2. Receipt line: quantity counted, date received, lot or serial number if tracked, name of who checked it in.
3. Variance: ordered minus received, shown as a number, not buried in a note field.
4. Status: line open (partial), line closed (full), or line closed short (manually accepted).
5. Cost check: PO cost versus invoice cost, flagged if they do not match.

When the numbers do not line up, the system does not force a decision on the dock. A partial shipment receives against the line for whatever arrived and leaves the balance open, so the vendor still owes you 20 units and the purchasing manager can see that owed balance without digging through email. An over-shipment gets flagged before it posts to on-hand, so someone decides whether to keep the extra, return it, or adjust the PO cost to match, instead of the system silently accepting a number that was never agreed to.

Walk the dock at a mid-size parts distributor on a Tuesday morning. A PO for 1,200 gaskets from a regular vendor is supposed to land by nine. The truck pulls in at eleven with 1,150 on the pallet and a packing slip that says "ship complete." The receiving clerk counts twice, gets the same number both times, and has thirty seconds to decide whether to enter 1,200 because that is what the PO says, or 1,150 because that is what is actually sitting on the floor. Enter the wrong number and the work order that needs those gaskets next week shows plenty of stock on paper and none in the bin when someone goes looking for it.

Now take the same dock a few hours later. A different vendor ships 520 units against a PO for 500, and the extra 20 showed up with a lot number that does not match anything already in the system. If the receiving screen only has one quantity field, that overage either gets ignored, forced into the wrong lot, or sits on a sticky note until someone has time to sort it out. None of those outcomes gets the lot right, and if the product ever needs to be traced back to a supplier batch, that sticky note is the only record anyone kept.

Both scenes come down to the same design choice: whether the system treats "ordered" and "received" as one number or two. A receiving clerk who can enter 1,150 against a 1,200 line, watch the remaining 50 stay open, and move on without a phone call is doing the job the software should have been doing all along. A clerk who has to guess, round, or call the buyer before finishing a receipt is doing work the system pushed onto them.

If you are evaluating whether your current setup actually separates these two records, run this test on a real PO:

1. Pull up a purchase order that was partially received. Can you see the ordered quantity and the received quantity as two distinct numbers on the same line?
2. Check whether the line status reads open, closed, or closed short, without you having to calculate the difference by hand.
3. Look for a cost field that compares PO cost to what the vendor actually invoiced.
4. Ask whether on-hand inventory updated the moment the receipt was entered, or whether it waited for a batch process overnight.
5. Find out who gets notified when a receipt does not match the PO: nobody, an email nobody reads, or a flag on the line itself.

If several of those come back as "no" or "I'm not sure," the gap between the order and the shelf is being closed by memory and spreadsheet math, not by the system of record. That is the work that quietly eats a receiving clerk's afternoon and a buyer's trust in their own numbers.

Brian Garrett at Telluric Companies was a beta tester for this workflow and says it saves him at least 45 minutes per purchase order, because the PO and the receipt stay linked instead of requiring a manual cross-check against the packing slip every time. See more results at fishbowlinventory.com/casestudies.

Fishbowl runs inventory, production, and the warehouse. QuickBooks or Xero keeps the books. The PO and receipt records sync to accounting on their own schedule; the dock does not need to touch the ledger to get a count right.

Setup and training for this kind of receiving workflow typically run 6 to 8 weeks with Fishbowl's own team. The system is useful from the first live count, so you are not waiting for a full rollout before purchase orders and receipts start tracking correctly against each other. Support is in-house, with US and APAC teams, and customers can reach a person by phone, email, or chat when a receipt does not look right.

You can see how Fishbowl handles receiving against a live purchase order at fishbowlinventory.com, or walk through it on your own PO data.

Get a demo: 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 is the difference between a purchase order line and a receipt line?

A purchase order line is the agreement: SKU, quantity ordered, and cost you negotiated with the vendor. A receipt line is the record of what actually showed up on the dock, counted and checked item by item. Fishbowl keeps them as two separate numbers on the same PO so a gap between them is visible the day it happens.

What happens when the quantity received does not match the purchase order?

Fishbowl flags the variance at the moment of receipt instead of letting it pass as a clean close. A short shipment leaves the PO line open for the remaining balance. An over-shipment gets called out before it posts to on-hand, so the receiving clerk or purchasing manager decides whether to accept, return, or adjust the order.

How long does it take to set up PO and receiving workflows in Fishbowl?

Paid setup and training typically run 6 to 8 weeks with Fishbowl's own team, not a third party. The receiving workflow is useful from the first live count. You do not wait until every warehouse process is tuned before purchase orders and receipts start tracking against each other correctly.

Can a partial shipment close a purchase order line?

A partial shipment receives against the PO line for the quantity that arrived and leaves the remaining balance open. The line does not close until the full ordered quantity has been received or someone manually closes it short, so you always know what is still owed by the vendor.