The Restaurant Purchase Order Process: From Request to Delivery

The restaurant purchase order process is the controlled path every ingredient order follows, from a request based on stock levels to a checked delivery and a matched invoice. Run it as six gates and each one blocks a specific leak: over-ordering, unapproved spend, price drift or short delivery.

Most kitchens already run a version of this process. It just lives in message threads, a supplier's voicemail and a delivery note in a drawer. This guide sets out one process UK operators can run the same way at every site, and shows where each step protects gross profit.

What is a restaurant purchase order, and why does it matter?

A purchase order (PO) is the document a restaurant sends a supplier to confirm what it wants, how much, at what agreed price and for which delivery date. It is the buyer's record of the deal. The delivery note is the supplier's record of what arrived. The invoice is the supplier's bill.

Those three documents should agree. When they do not, the gap usually lands on your food cost line without anyone noticing. A PO gives you the baseline to catch it.

The stakes are bigger than one short case of tomatoes. According to WRAP (4 November 2024), the UK hospitality and food service sector throws away nearly a fifth of the food it buys. Every excess order that ends up as waste started as a purchase nobody challenged.

To see what purchasing accuracy means for your own margin, run a few dishes through the free food cost calculator before you change anything else.

What are the six gates of the restaurant purchase order process?

The Six-Gate PO Loop is StockTake Online's framework for running purchasing as six checkpoints. Each gate has an owner, an input and a leak it closes. Skip a gate and that leak reopens.

1. Request. Someone raises the need, based on stock on hand against par level, not memory.
2. Approve. A named person signs off quantity, supplier and spend before anything is sent.
3. Transmit. The approved PO goes to the supplier in writing, with the agreed price on every line.
4. Confirm. The supplier acknowledges the order and flags substitutions or shortages before dispatch.
5. Receive. Whoever takes the delivery checks it against the PO, not against the delivery note.
6. Match. Order, delivery record and invoice are compared line by line before payment is approved.

The loop closes when the match feeds the next request. Quantities received update stock on hand, and prices paid update recipe costs.

Gate 1: How should a purchase request be raised?

A good request starts with two numbers: what you hold now and what you need before the next delivery. The difference is the order quantity. Par levels make this repeatable because the target is agreed in advance, per item and per site.

Requests raised from memory tend to repeat last week's order. That is how slow-moving lines build up in the walk-in. Tie every request to a recent count and quantities start to follow real usage.

Gate 2: Who should approve a restaurant purchase order?

Approval should sit with someone accountable for the site's gross profit. That is usually the head chef, general manager or bar manager for their own category. Multi-site groups often add a second tier for orders above an agreed value, or for any new supplier.

Keep the rule simple enough to follow on a busy Friday. One approver per category, one threshold for escalation, and no order sent without a recorded approval. Unapproved phone orders are where duplicate deliveries come from.

Gates 3 and 4: How do you send and confirm an order with a supplier?

Send the PO in writing, through one channel, with the agreed unit price on each line. Verbal orders leave no record of what was agreed. Any later dispute then becomes your word against the supplier's.

Confirmation is the step most kitchens skip. Ask suppliers to acknowledge each PO and flag substitutions or shortfalls before the van leaves. Knowing on Tuesday afternoon that the lamb will be short gives the chef time to adjust the menu. Finding out at the back door on Wednesday morning does not.

Gate 5: What should happen when a delivery arrives?

Receiving is where the purchase order earns its keep. The person at the door should check the delivery against the PO before signing the supplier's paperwork. A practical receiving check covers five things:

• Quantity: count cases and weigh anything sold by weight.
• Product: confirm the right item, brand and pack size arrived, and record any substitution.
• Price: compare any prices on the delivery note with the prices on the PO.
• Condition: reject damaged, short-dated or poor-quality items before you sign.
• Temperature: check chilled and frozen goods in line with your own food safety management procedures.
• A restaurant purchase order is the buyer's record of the agreed item, quantity, price and delivery date.
• The Six-Gate PO Loop runs Request, Approve, Transmit, Confirm, Receive and Match.
• Receive every delivery against your PO, not against the supplier's delivery note.
• A three-way match catches short deliveries and price drift before any payment is made.
• Matched prices should update recipe costs, so GP% reflects what you actually pay.

Record exceptions on the spot and note them on the delivery paperwork. This record is often called a goods received note. It is your evidence when you need a credit from the supplier.

Gate 6: What is a three-way match, and why run it?

A three-way match compares the purchase order, the goods received record and the supplier invoice before the invoice is approved. If all three agree, it gets paid. If they do not, the difference is queried before money leaves the business.

Here is an illustrative example, not taken from a real account. A site orders six cases of lemons at an agreed price. Five arrive, and the receiver notes the short case. The invoice then bills for six cases at a higher unit price. Without the match, the site pays for a case it never received, at a price it never agreed. With the match, both errors are caught in one review.

The match also closes the loop. Once approved, the actual price becomes the cost basis for every recipe that uses the item, so your GP% reflects what you really pay.

How does a manual purchase order process compare with a system-led one?

The six gates work on paper, but they are hard to sustain across several suppliers and sites. The table shows where manual processes usually break.

What are the most common purchase order mistakes in restaurants?

The same few mistakes appear in most kitchens, whatever the size. The costliest are ordering outside the process, receiving against the supplier's paperwork instead of your own PO, and approving invoices without checking line prices. Standing orders that nobody reviews come a close fourth, because usage changes while the order does not.

That is the core issue. A PO is not paperwork for its own sake. Until the invoice arrives, it is the only record of the agreed price.

How does StockTake Online support the purchase order process?

StockTake Online runs all six gates in one place, on any phone, tablet or browser, with no hardware to buy. Orders can show par level and stock-in-hand information on each line, and are approved before they go to the supplier. Order PDFs can be shared with suppliers directly.

At the back door, the team accepts the delivery against the order. They can add extra items, record free-of-charge goods, update prices and attach the invoice or delivery note to the order record. Deliveries can then be filtered by status, such as shipped, partially shipped or pending, so nothing outstanding is missed. The restaurant order and delivery management software page shows how each step works.

Supplier price changes are flagged rather than slipping through at invoice approval. Received quantities update stock, so the next request starts from real numbers. Operators using StockTake Online typically identify up to 3 to 8% in recoverable food cost within 60 days of going live. For supplier catalogues, pack sizes and product setup, see the procurement workflow in StockTake Online.

If you want to go deeper on price history and supplier negotiation, our guide to restaurant supplier management software picks up where this process ends.

Where should you start?

Start with the gate that leaks most. For most sites that is receiving or matching, because both happen under time pressure. Fix those two, then tighten requests with par levels.

Baseline your margin first: calculate your food cost free with the StockTake Online calculator. When you want to see the full loop running on your own suppliers, book a demo with the team.

Frequently asked questions

What is the purchase order process in a restaurant? It is the sequence an order follows from request to payment. Raise a request from stock levels, approve it, send it to the supplier in writing, get confirmation, receive the goods against the PO and match the invoice before paying.

What is the difference between a purchase order and an invoice? A purchase order is created by the restaurant and records what it agreed to buy and at what price. An invoice is created by the supplier and requests payment. Check the invoice against the PO and the goods received before approving it.

Who should approve purchase orders in a restaurant? The person accountable for that category's gross profit, usually the head chef, general manager or bar manager. Multi-site groups often add a second approval tier for larger orders or new suppliers.

What should you check when a restaurant delivery arrives? Check quantity, product and pack size, price, condition and temperature against the purchase order. Record any shortages, substitutions or rejections on the delivery paperwork before signing, so you can claim a credit.

Do small restaurants need purchase orders? Yes. A single site with a handful of suppliers still benefits from a written record of agreed prices and quantities. Without one, short deliveries and price rises are hard to spot and harder to dispute.