Restaurant purchasing price lists: how to keep them useful

Early morning, the chef checks a produce delivery at the back door

A supplier price list becomes wrong as soon as the price received is no longer compared with the reference. Three habits are enough to keep it accurate: check every delivery against the expected price, log gaps above a threshold, and link each product to the recipes that use it. The spreadsheet is not the problem, the link between prices and recipes is.

Veal brisket delivered at a higher price, discovered on the monthly invoice

A fictional example. The meat supplier changes the price of veal brisket mid-month, without warning. The delivery note carries no price. The invoice arrives a week later and nobody compares it with the reference: the bookkeeper simply records it. Meanwhile, the daily special that uses this cut has been sold at the same price, and the recipe card still shows the old cost. At close, food cost goes up and nobody knows why.

Why a price list goes stale

It is entered once and never reread. A table created at opening ends up describing the prices of another season.
Prices arrive on the invoice, not at delivery. The check happens when the goods have already gone into the kitchen.
The link to recipes is manual. When a price changes, nobody knows which cards to recalculate, so nobody does.
Each site has its own version. The same product, from the same supplier, appears at three different prices in three tables.
Product references change. Pack size, grade, brand: the price list line no longer matches what arrives.
Nobody owns the update. Without an owner, the table drifts.

The living price list: a five-step rule

Name an owner for each product family. The head chef for meat and fish, the sous chef for dry goods, for example. They answer for the update.
Set the reference price and its date. Each line shows the expected price, the pack size and the day it was confirmed.
Check at delivery. The delivery note is matched against the reference line. If the price is not on it, ask for it to be added: with no price at receiving, there is no check.
Log gaps above a threshold. The threshold is set by family: a volatile product does not get the same threshold as a dry good. Each gap has a "decision" field: accepted, contested, product replaced.
Link products and recipes. For each important product, the list of recipe cards concerned. A price change triggers the recalculation of those cards only.

Price list line template

Field	Fictional example
Product and pack size	Veal brisket, vacuum-packed piece
Supplier	Supplier A
Reference price and date	Price confirmed on the day of the last order
Alert threshold	To be set by family
Last price received and gap	Noted at delivery
Recipes concerned	Daily special, seasonal side
Decision	Accepted / contested / substituted

Mistakes that make it useless

Waiting for the monthly invoice to look at prices.
Updating the price without updating the recipe card.
Letting each site keep its own price list in its corner, without counting who updates it.
Negotiating on overall volume without knowing which products really moved.
Setting an alert threshold so low that the team ignores every alert.

Comparing two suppliers without getting it wrong

The displayed price is not the useful price. Bring each product down to a comparable unit: the price per kilo, or per usable unit, after trimming and waste.

Price per usable unit = purchase price / yield

Yield is what is left after trimming. A product that is cheaper to buy but has a lower yield can cost more on the plate. Write the yield on the recipe card, measured once by the chef on a real batch, and review it if the grade or the supplier changes.

What to measure

The delay between a price increase and the update of the recipe cards concerned. It is the length of time your dishes lie.
The share of deliveries checked against the reference, on the products you track.
The number of gaps that led to a decision (accepted, contested, substituted) compared with gaps that were merely noted.

Where Tsuno comes in

Tsuno keeps recipes with their composition, which shows which dishes a product touches. For invoices and price lists, you decide area by area: keep your purchasing tool as the source of truth, import its exports with human validation, or run a temporary duplicate. Tsuno does not replace your POS or your purchasing software. During setup, we start from your existing documents (spreadsheets, exports) and a person validates the sensitive matches. See integrations.

Key takeaways

A supplier price list stays true when the price is checked at delivery and linked to the recipes that use it. One owner per product family is enough to keep it from drifting.

Further reading: why owners discover cost drift too late, food cost that arrives late, the full cost of waste and prime cost.

Frequently asked questions

What is a supplier price list in a restaurant?

It is the list of prices for the products a supplier offers, which moves with the market and the season. For a restaurateur, it is also the table of reference purchase prices, used to cost recipes.

How often should you update your price list?

At the pace your prices actually move. Variable fresh products are checked at every delivery, dry goods less often. A simple rule by product family beats a general update every quarter.

How do you spot a price increase the supplier did not announce?

By comparing each invoice line with the reference price in your price list and noting gaps above a threshold you set. The check happens at receiving, not at month-end close.

Why link the price list to recipe cards?

Because a price change only matters if it touches a dish. With the link in place, you know immediately which recipes see their cost move and which deserve a decision.

Do you need purchasing software to keep a price list?

Not necessarily. A well-kept spreadsheet can be enough for one site. The difficulty comes from the re-entry time when several sites, several suppliers and several recipe cards are involved.