Restaurant purchasing problems rarely begin when the invoice arrives.
They usually begin earlier: someone orders from memory, buys too much because a supplier offers a deal, forgets what is already in storage, uses the wrong pack size, or places an urgent order without documenting why.
A simple purchase-order system creates control before the money is spent.
It connects inventory, par levels, forecast demand, supplier terms and receiving into one repeatable process. The result is fewer emergency purchases, fewer duplicate orders, cleaner invoice checking and better visibility over food cost.
What a restaurant purchase order should do
A useful purchase order should answer six questions:
- What are we buying?
- How much are we buying?
- From which supplier?
- At what unit and expected price?
- When should it arrive?
- Who approved the purchase?
The system does not need to be complicated. It needs to make the buying decision visible before delivery.
Start with on-hand stock, not memory
The first ordering question is not, “What do we usually buy?”
It is:
What do we actually need after considering what is already on hand?
Before ordering, review:
- current usable stock,
- open purchase orders not yet received,
- expected demand until the next delivery,
- par level,
- known events or unusually large bookings.
This prevents duplicate purchasing and overstock.
Use par levels as the base
A simple order quantity can begin with:
Order quantity = Target stock level − Usable on-hand stock − Open incoming quantity
Illustrative example:
- Target stock: 40 kg
- Usable on hand: 18 kg
- Already ordered and due tomorrow: 7 kg
40 − 18 − 7 = 15 kg to order
This is better than placing another 22 kg order because someone forgot about the open delivery.
For a deeper explanation of target stock levels, see our Restaurant Inventory Par Levels guide.
Adjust pars for real demand
Pars should not be treated as fixed forever.
Adjust expected demand for:
- day of week,
- seasonality,
- holidays,
- events,
- promotions,
- weather where materially relevant,
- known catering orders,
- menu changes.
A Friday order built from Monday demand can create either a shortage or excess stock.
Convert usable demand into purchase quantity
When an ingredient has meaningful trim or cooking loss, order based on purchase quantity, not only usable quantity.
Formula:
Required purchase quantity = Required usable quantity ÷ Yield %
If the kitchen needs 24 kg of usable product and expected yield is 80%:
24 ÷ 0.80 = 30 kg to purchase
Our Restaurant Recipe Yield Test guide explains how to calculate reliable yield assumptions.
Standardize the item description
A vague purchase order creates receiving problems.
Instead of writing:
Chicken — 5 boxes
use a controlled description such as:
Chicken breast, approved brand/specification, 2 kg × 6 packs per case — 5 cases
The description should identify the product clearly enough that the receiving team can verify it.
Control unit of measure
Many purchasing errors come from unit mismatches.
Examples:
- order says 10, supplier interprets 10 cases instead of 10 kilograms,
- recipe uses grams while purchasing uses cases,
- one supplier sells by each and another by pack,
- the invoice price is per kilogram but the manager compares it with a case price.
Each item should have a clearly defined purchasing unit.
Track pack size
Pack size matters because unit price comparisons can be misleading.
Suppose:
- Supplier A case: 12 kg for $66
- Supplier B case: 10 kg for $58
Case price alone makes Supplier B look cheaper.
But price per kilogram is:
Supplier A: $66 ÷ 12 = $5.50/kg
Supplier B: $58 ÷ 10 = $5.80/kg
Normalize the unit before comparing suppliers.
Include the expected price
A purchase order becomes more useful when it records the expected unit price.
This gives receiving or accounts payable a reference against the invoice.
Useful fields include:
- last approved price,
- current quoted price,
- contract price where applicable,
- expected total.
When the invoice differs, management can investigate the variance rather than discovering it weeks later.
Calculate an expected order value
For each line:
Expected line value = Order quantity × Expected unit price
Then:
Expected purchase-order value = Sum of all line values
Illustrative example:
| Item | Qty | Unit price | Expected value |
|---|---|---|---|
| Chicken breast | 30 kg | $5.20 | $156.00 |
| Rice | 20 kg | $1.80 | $36.00 |
| Cooking oil | 12 L | $2.40 | $28.80 |
Total expected PO value = $220.80
Figures are illustrative.
Use approval thresholds
Not every purchase needs owner approval.
A small restaurant can use simple thresholds such as:
- routine orders within approved par and price: purchasing manager,
- order above normal quantity: general manager approval,
- new supplier: owner or senior approval,
- unplanned capital or non-food purchase: separate approval.
The exact limits should fit the size of the business.
Separate ordering from receiving where practical
For stronger control, the person receiving the delivery should verify it against an approved purchase order rather than accepting whatever arrives.
This does not require a large accounting department.
Even in a small restaurant, the control can be:
- Manager creates and approves order.
- Supplier receives the order.
- Receiving employee checks delivery against PO.
- Invoice differences are documented.
- Manager closes the PO.
Use purchase-order numbers
Assign a unique number to each order.
Example:
PO-2026-1048
This reference can appear on:
- supplier communication,
- receiving record,
- invoice check,
- credit claim,
- purchase analysis.
A unique reference makes discrepancies easier to trace.
Set order cutoff times
Managers should know when orders must be placed to receive the next scheduled delivery.
Record:
- supplier order days,
- cutoff time,
- delivery days,
- minimum order,
- lead time,
- holiday changes.
Late ordering should be an exception, not a normal operating method.
Track minimum order constraints
Minimum orders can create unnecessary inventory.
If a supplier requires a $300 minimum but the restaurant only needs $220 of product, do not automatically add slow-moving items just to reach the threshold.
Consider:
- combining order timing,
- using an approved alternative supplier,
- changing delivery frequency,
- renegotiating the minimum,
- evaluating whether the supplier still fits the operation.
Do not let supplier promotions drive inventory
“Buy ten cases and get one free” sounds attractive.
But the right question is:
Will we use the product before quality or shelf life becomes a problem?
A deal that creates dead stock is not a saving.
See our Restaurant Dead Stock guide for the cost of overbuying.
Record why an order exceeds normal par
When management deliberately orders above normal stock levels, add a reason.
Examples:
- large catering event,
- holiday demand,
- known supplier closure,
- temporary price protection,
- promotion with forecasted demand.
This helps future managers understand whether the excess stock was planned or accidental.
Control emergency purchases
Emergency buying is sometimes necessary.
But it should be documented separately because it often costs more.
Track:
- item,
- quantity,
- emergency supplier,
- normal supplier,
- normal price,
- emergency price,
- reason.
If emergency purchases repeat, the problem may be par levels, forecasting, supplier reliability or ordering discipline.
Receive against the PO
When the delivery arrives, the receiving team should compare it with the approved order.
Check:
- item,
- quantity,
- unit,
- pack size,
- price where visible,
- approved substitution,
- quality,
- temperature where required,
- delivery condition.
Use our Restaurant Receiving Checklist for the detailed receiving process.
Record short shipments
If the restaurant orders 12 cases and receives 10, the PO should not be silently closed.
Record:
- ordered quantity,
- received quantity,
- short quantity,
- whether the supplier will back-order, credit or cancel the balance.
This prevents the inventory system from assuming stock arrived when it did not.
Record over-deliveries
Over-delivery is also a control issue.
If the restaurant ordered 5 cases and the supplier delivers 8, do not accept the extra three automatically.
Ask:
- Was the PO changed?
- Was there a supplier error?
- Do we actually need the excess?
- Will it create storage or shelf-life risk?
Approve substitutions before acceptance
A substitution may change:
- cost,
- yield,
- allergen profile,
- recipe consistency,
- pack size,
- brand standard.
Require approval for material substitutions instead of allowing drivers or receiving staff to decide casually.
Match PO, receiving and invoice
A strong purchasing process compares three records:
- what was ordered,
- what was received,
- what was invoiced.
This is often called a three-way match.
The principle is simple:
Do not pay for something the restaurant did not order or receive without understanding the difference.
Investigate price variance
For each important item:
Price variance per unit = Invoice price − PO price
Illustrative example:
- PO price: $5.20/kg
- Invoice price: $5.55/kg
- Quantity: 30 kg
Unit variance = $0.35/kg
Total variance = $0.35 × 30 = $10.50
The difference may be legitimate, but it should be visible.
Track quantity variance
Quantity variance identifies differences between what was ordered and what was received.
Quantity variance = Received quantity − Ordered quantity
If 50 units were ordered and 46 received:
46 − 50 = -4 units
This should feed supplier performance review when it occurs repeatedly.
Track open purchase orders
At any time, management should be able to see orders that are:
- created,
- approved,
- sent,
- partially received,
- fully received,
- closed,
- cancelled.
An open-order report prevents duplicate buying and highlights late deliveries.
Close purchase orders properly
A PO should be closed when:
- the ordered quantity has been fully received,
- the remaining balance has been cancelled, or
- the supplier has confirmed the order is complete.
Do not leave old POs open indefinitely.
Use order history when setting future pars
Purchase-order history gives management useful demand information.
Review:
- average weekly quantity,
- seasonal changes,
- frequency of emergency orders,
- frequency of overstock,
- supplier lead-time changes.
Ordering history should improve the next forecast.
Connect PO data with inventory counts
Inventory data becomes more reliable when purchases are documented consistently.
The basic food-cost flow is:
Opening inventory + Purchases − Closing inventory = Cost of food used
If purchase records are incomplete or duplicated, food-cost analysis becomes unreliable.
Our Restaurant Inventory Count Sheet guide explains how to improve physical count consistency.
Connect ordering with purchasing analysis
Purchase orders tell you what management intended to buy.
Purchase analysis tells you what the business actually bought over time.
Compare:
- quantity by item,
- spend by supplier,
- price movement,
- emergency purchasing,
- category spend.
See our Restaurant Purchasing Analysis guide for that broader review.
Connect purchase orders with supplier performance
The PO creates the reference that lets management measure whether the supplier performed correctly.
You can compare:
- promised date versus actual date,
- ordered quantity versus received quantity,
- approved specification versus delivered specification,
- expected price versus invoice price.
That data can feed the Restaurant Supplier Scorecard.
Do not let WhatsApp become the purchasing system
Messaging apps are convenient for communication, but they are weak as the only purchasing record.
Problems include:
- orders buried in conversation,
- unclear versions after changes,
- missing approval,
- no standardized item units,
- difficult historical analysis.
If an order is sent by message, it should still come from or be copied into the official PO system.
Use a simple PO template
| Field | Example |
|---|---|
| PO number | PO-2026-1048 |
| Supplier | Fresh Foods Co. |
| Order date | October 3 |
| Delivery date | October 4 |
| Item | Chicken breast |
| Pack / unit | kg |
| Qty | 30 |
| Expected price | $5.20/kg |
| Expected line value | $156.00 |
| Approved by | Kitchen manager |
| Status | Sent |
The example is illustrative.
Create a weekly ordering rhythm
A practical routine can be:
- Count critical inventory.
- Review sales forecast and events.
- Review open POs.
- Calculate required order quantities.
- Review price and supplier choice.
- Create PO.
- Approve exceptions.
- Send to supplier.
- Receive against PO.
- Close and review variances.
Consistency is more important than sophistication.
Review exception rates
Once the system is operating, track how often orders deviate from plan.
Useful exception measures include:
- emergency purchases,
- orders above par,
- late supplier deliveries,
- short shipments,
- unapproved substitutions,
- invoice price mismatches.
If exceptions are frequent, the ordering process needs attention.
Do not measure buyers only on low prices
If a manager is rewarded only for obtaining the lowest price, they may buy too much, accept poor yield or choose unreliable suppliers.
Better purchasing considers:
- usable cost,
- quality,
- yield,
- delivery reliability,
- shelf life,
- inventory impact.
Use total cost, not invoice price alone
The true cost of a purchase can include:
- product price,
- delivery charge,
- minimum-order pressure,
- excess trim,
- poor yield,
- emergency replacement cost,
- waste from overbuying.
A disciplined PO process makes these trade-offs easier to see.
The purchase order is the control point before the invoice
Restaurants often focus on food cost after the month is over.
But purchasing control happens earlier.
By the time an unnecessary case is sitting in the walk-in, the money has already been committed.
A purchase-order system creates a decision point before that commitment.
It forces the restaurant to ask whether the quantity is needed, whether the price is acceptable, whether the supplier is correct and whether the order fits the operational plan.
That makes purchasing less reactive and food-cost control more preventive.
Use an approval matrix for exceptions
Routine orders should move quickly, while unusual purchases receive more scrutiny. A simple approval matrix can distinguish normal replenishment from higher-risk decisions.
| Purchase type | Typical approval |
|---|---|
| Routine order within par and approved price | Purchasing or kitchen manager |
| Quantity materially above par | General manager |
| New supplier or new specification | Senior management / owner |
| Emergency purchase above normal price | Manager with documented reason |
The roles and limits should match the restaurant’s size. The purpose is to make exceptions visible without slowing normal purchasing.
Frequently asked questions
Does every restaurant need formal purchase orders?
Not every small purchase needs a complex document, but important supplier orders benefit from a controlled record showing item, quantity, unit, expected price, delivery date and approval.
What is a three-way match?
It compares the approved purchase order, the receiving record and the supplier invoice so the restaurant can identify differences in quantity, price or product before payment.
When should a purchase order remain open?
Keep it open while part of the order is still expected, disputed or back-ordered. Close it when the order is fully received or the remaining balance is formally cancelled.
Operational note: The formulas, approval examples and controls in this guide are illustrative. Purchase-order procedures should be adapted to your restaurant’s size, supplier agreements, accounting controls and local regulatory requirements.