Tetra M Labs.
Notice: Tetra M Labs has no cryptocurrency token. Any ‘TETRAM’ coin is not affiliated with us.

ERP

Purchase order process: how small businesses buy without the mess

Most surprise bills in a small business do not start with a dishonest supplier. They start with an order nobody wrote down. Someone phones in an order, the goods arrive, the invoice arrives, and nobody can say who approved it, at what price, or whether the delivery matches what was asked for. A clear purchase order process fixes that, and it does not need a procurement department — just a written habit, followed every time.

A purchase order is a written instruction to a supplier: what you want, how much of it, at what price, and on what terms. Once accepted, it is also evidence of what was agreed — the buyer can prove what was ordered, and the supplier what was promised. Everything else in the process exists to keep that document accurate and to check reality against it.

The purchase order process, step by step

A good purchase order process has six steps, and skipping any of them is usually where the trouble starts.

1. Identify the need. Someone in the business needs something — stock, materials, a service, equipment. The request should say what is needed, how much, and by when. Be specific here: the exact item, the specification, and the quantity.

2. Get a price. For routine, low-value purchases from a regular supplier, an agreed price list may be enough. For anything larger or new, get a quote in writing first, confirming price, delivery charges, taxes, delivery date, and payment terms. A verbal price remembered differently by each side is a dispute waiting to happen.

3. Approve the purchase. Before the order goes out, someone with authority approves it — in a very small business, that may be the owner for everything above a set amount, with smaller routine purchases approved by a manager. The point is not bureaucracy; it is that no order leaves without a second pair of eyes on the amount and the supplier. This also stops duplicate orders, where two people order the same thing because neither knew the other had.

4. Issue the purchase order. Send the supplier a numbered purchase order with the item, quantity, agreed price, delivery address, delivery date, and payment terms. Numbering matters: a gap or duplicate in the sequence warns that an order was missed or sent twice. Keep a copy on file, and quote the number on all later correspondence about that order.

5. Check the delivery. When goods arrive, check them against the purchase order before signing: the right items, the right quantities, and no visible damage. If something is short or damaged, note it on the delivery document at the time — a complaint raised weeks later, after a clean signature, is much harder to resolve. For services, confirm the work was done to the agreed scope before accepting the invoice.

6. Match the invoice before paying. Before payment, compare three documents: the purchase order, the delivery evidence, and the supplier's invoice. They should agree on item, quantity, and price. If the invoice price is higher than the order, or the quantity billed exceeds what was delivered, hold payment and query it. Paying first and asking later reverses all your leverage. This three-way check catches pricing errors, duplicate invoices, and short deliveries that would otherwise slip straight into your costs.

What a good purchase order contains

A purchase order need not be long, but it must be complete: supplier and business names, a unique order number and date, a clear description of each item or service, quantities, unit prices, total amount, delivery address and required date, and payment terms. If tax treatment, discounts, or return conditions matter, put them in writing too — anything left to assumption will be assumed differently by the other side.

It also helps to keep one purchase order per supplier and, where practical, per delivery.

Common purchase order process mistakes

The most common mistake is ordering without a purchase order at all — by phone, message, or in person — and treating the invoice as the first written record. By then, there is nothing to check the invoice against, and any error becomes an argument about memory.

The second is approving after the fact. A purchase order raised after the goods have arrived is not a control; it is paperwork catching up with a decision already made. Approval must come before the order is sent, or it approves nothing.

The third is never closing old orders. Orders that were partly delivered, cancelled, or superseded should be marked closed, so nobody matches a new invoice against an old order by mistake. A list of open orders is also genuinely useful: it shows what you have committed to spend but have not yet been billed for — exactly what cash-flow planning needs.

Keeping the purchase order process simple for a small team

A small business does not need a complicated system, but it does need a consistent one. One numbering sequence, one person (or one small group) authorised to approve above a set amount, one place where purchase orders are filed, and one rule: no purchase order, no payment, except for genuinely minor expenses handled another way. That single rule, applied kindly but firmly, changes behaviour quickly — suppliers learn to ask for the order number, staff learn to raise the request first, and invoices start arriving with something to check them against.

Good buying is not about suspicion. It is about clarity: the supplier knows exactly what is wanted, the business knows exactly what it committed to, and the invoice can be checked in minutes rather than argued over for weeks. A written order, approval before it goes out, a check on delivery, and a match before payment — that discipline scales from a two-person business to a much larger one without changing shape.

If you want your orders, invoices, and reporting in one place, join the waitlist for Point at tetramlabs.com.