What Is a Purchase Order? A Manufacturer's Guide

A purchase order (PO) is a document the buyer issues to a supplier specifying exactly what they want to buy: the items, quantities, agreed price, delivery date and terms. It is a formal offer to buy. When the supplier accepts it — by acknowledging it, or simply by shipping against it — the PO becomes a binding contract between the two parties.

That is the definition. What makes the PO genuinely useful in manufacturing is narrower: it is the only document that states, in one place and before anything happens, what was ordered, at what price, and when it is due. Every argument about a late delivery or a wrong invoice is settled by reference to it.

What goes on a purchase order

At minimum:

• PO number — unique, and the reference everything else in the transaction quotes.
• Buyer and supplier details, including the delivery address and, where they differ, the invoicing address.
• Line items: your part number, the supplier’s part number, description, quantity, unit of measure and unit price.
• Required delivery date per line — not a single date for the whole order, if lines are needed at different times.
• Payment terms (30 days from invoice, for example) and delivery terms (Incoterms such as DAP or EXW, if goods cross a border).
• Currency, and the total value.

For food and beverage manufacturers a few more fields earn their place: required minimum shelf life on receipt, batch or lot traceability requirements, temperature and delivery window, and any specification or certification reference the goods must meet. Getting “minimum 75% of shelf life remaining on delivery” onto the PO is far easier than arguing about it at the goods-in door.

How the purchase order process works

The lifecycle has six steps, and confusion about which step you are on is the source of most PO problems.

1. Requisition. Someone identifies a need — usually the planning run, sometimes a person. Internally approved if the value warrants it.
2. PO raised and sent. The order is created in the ERP or purchasing system and sent to the supplier. It now has a number and a status.
3. Acknowledgement. The supplier confirms receipt and — critically — confirms the date and quantity they will actually deliver. This is where a PO becomes a supply commitment. Until then it is a request.
4. Goods received. Delivery arrives, goods-in checks quantity and condition against the PO, and a goods receipt note (GRN) is raised. In food manufacturing this is also where QC release happens; stock received is not the same as stock usable.
5. Invoice and matching. The supplier invoices. Finance performs a three-way match between the PO, the GRN and the invoice. If all three agree, it pays. If they disagree, somebody investigates.
6. Close. The PO is closed when fully received and invoiced. Partially received POs stay open, and a pile of stale open POs is a reliable sign of a purchasing process that is not being worked.

PO vs invoice vs quote vs contract

These get conflated constantly:

• A quotation comes from the supplier and offers to sell at a price. It is not an order.
• A purchase order goes from the buyer to the supplier and offers to buy. Once accepted, it is the contract for that transaction.
• An invoice comes from the supplier after the goods and requests payment. It should quote the PO number and match it.
• A supply agreement or framework contract sits above all of this and sets the terms — pricing, volumes, liability — across many POs. Individual POs then call off against it.

The practical upshot: the PO is the buyer’s document and the invoice is the seller’s. If they disagree, the PO plus the goods receipt is what you argue from.

A worked example

A bakery needs butter for a three-week production run.

The planning run produces a net requirement of 450 kg needed in the warehouse by Monday of week 3. The buyer raises PO 4417: 18 × 25 kg blocks of unsalted butter at £5.40/kg, delivery required 14 September, minimum 30 days shelf life on receipt, payment 30 days from invoice. Total £2,430.

Three things then have to happen, and each is a checkpoint:

• The supplier acknowledges on 2 September, confirming 18 blocks but on 16 September, two days late. That is not a formality — it is a new fact. The buyer either accepts the slip (and checks the production plan survives it) or pushes back.
• The delivery arrives on 16 September with 17 blocks. Goods-in raises a GRN for 17, the PO stays open for 1, and the plan is now 25 kg short.
• The invoice arrives for 18 blocks, £2,430. The three-way match fails — invoice 18, GRN 17 — and it is held until the supplier issues a credit or ships the missing block.

None of these steps is complicated. All three are easy to miss when there are 200 open POs and the acknowledgements arrive as free-text email replies.

PO numbers and why they matter

Use a single sequential series, and make the number the reference on everything: the order, the acknowledgement, the delivery note, the invoice, the credit note. Suppliers who cannot quote the PO number on their paperwork will cost you time in accounts payable every single month.

In the UK, POs themselves are not a tax document — the invoice is what matters for VAT and what HMRC expects you to retain. But the PO is what makes the invoice checkable, which is why finance teams insist on “no PO, no pay” policies. That policy only works if raising a PO is fast; when it is slow, people order first and back-fill the paperwork, which defeats the point.

Where the PO process actually breaks

In manufacturing, the failures are consistent:

• Unacknowledged orders treated as confirmed. The plan assumes the goods are coming because a PO exists. Nobody has confirmed a date. The shortage appears at the pre-production check.
• Acknowledgements that quietly differ from the order. The supplier confirms a different date, quantity or price, in an email body, and it is never reconciled against the PO in the system.
• No chasing until it is late. Following up the day after the due date is a week too late for a supplier who could have flagged it.
• Partial deliveries left unmanaged. Open lines sit unnoticed until the three-way match fails weeks later.
• Stale prices. POs raised at the price in the system, invoices arriving at a price agreed verbally three months ago.

Each of these is a communication problem rather than a systems problem, which is why adding another ERP field rarely fixes them.

Automating the PO cycle

The parts of this that a system should genuinely take off a person: deciding what to order and when, from the material plan; raising the PO with the right dates and terms; sending it; reading the reply; noticing that the confirmed date differs from the requested one; chasing the ones that have gone quiet; and flagging the ones whose slippage actually threatens a production run.

That is the job Leio does — it connects to the ERP and the mailbox, so the acknowledgement buried in a supplier’s reply becomes a status change rather than an unread email, and the planner sees the three orders that matter this week instead of the two hundred that are open.

For where POs sit in the wider planning cycle, see the supply chain planning process. If chasing confirmations is currently somebody’s morning, book a demo.