Most small businesses start restocking the same way: email or call a supplier, get a rough confirmation, and find out what actually showed up when the box does. That works until it doesn't — a supplier ships the wrong quantity, an invoice arrives for parts that never came, or nobody can say what's still on order versus what's already in stock. A purchase order system fixes that by turning "I think I ordered that" into three linked records: what you ordered, what arrived, and what you owe for it.
Why a single PO form isn't the system
A purchase order by itself is just a promise — it says what you intend to buy, not what happened. The document alone doesn't update your stock count, doesn't tell you if the supplier shipped short, and doesn't connect to what you actually get billed. A real purchase order system needs the order to be the start of a chain, not a standalone piece of paper that gets forgotten in an inbox once it's sent.
The three-document chain: order → delivery → invoice
The pattern that actually works mirrors the sales side of the same business: raise a purchase order against a supplier, receive the stock against a delivery note (or goods-receipt note) that records what physically arrived, then turn that into a purchase invoice for what you're being billed. Each step should update the next — the delivery note references the order, the invoice references the delivery — so at any point you can see what's ordered but not received, received but not invoiced, or fully closed out.
What to put on the purchase order itself
Keep it simple but complete: a sequential PO number (so nothing gets duplicated or lost), the supplier, the items and quantities with your expected unit cost, and an expected delivery date. That's enough to compare against what shows up later — you don't need approval workflows or budget-holder sign-off chains unless your business genuinely has multiple people authorizing spend, which most small operations don't.
Matching what arrived against what you ordered
This is the step most ad-hoc systems skip, and it's the one that catches short shipments and pricing errors. When stock arrives, record it against the specific purchase order — item by item, quantity by quantity — rather than just adding it to inventory as a generic stock-in. If the delivery note shows less than the PO quantity, that PO stays open for the remainder instead of silently disappearing once anything at all has arrived.
Turning the delivery into an invoice — and reconciling the supplier balance
Once stock is received, the purchase invoice should come from that same delivery record, not be re-typed from the supplier's paper invoice as an unrelated document. That keeps quantities and costs consistent between what you received and what you're paying for, and it's what lets the supplier's running balance update automatically — instead of you totaling up invoices by hand at the end of the month to check what you owe.
Do you need full procurement software for this?
Enterprise procurement platforms add multi-level approval routing, budget controls, RFQ/bidding workflows and vendor scorecards — genuinely useful for a company with a dedicated purchasing department and multiple people who need to sign off before money moves. A small business with one or two people ordering stock usually doesn't need any of that; what it needs is the order → delivery → invoice chain itself, done consistently, inside the same system that already tracks its inventory and sales invoicing — not a second procurement subscription to keep in sync with the first one.
Stokpax builds that chain as the buying-side mirror of its sales workflow: raise a purchase order with a supplier, receive stock against a purchase delivery note, then turn that into a purchase invoice — on-hand quantity and the supplier balance update automatically at each step, in the same catalog you invoice customers from. It's not a general-purpose approval/procurement tool; it's the restocking half of the system a parts store or small distributor already uses to sell, from $29/month with a 7-day free trial.
