Restaurants: noticing food cost creeping up week by week
Ask a restaurant owner what their food cost is and you will usually get a percentage: "around 30%". Ask when it was last worked out properly, and the answer is often the last stock take, or the accountant's monthly figures, weeks after the month ended.
The trouble is that food cost rarely jumps. It creeps. Cooking oil goes up a little. The fish supplier adds a few cents per kilo. A popular dish is portioned a bit more generously by a new cook. Each change is small, nobody decides on it, and by the time the monthly numbers arrive, a few points of margin have gone.
This post is about seeing that creep while it is still small.
Where food cost creeps from
- Supplier prices. The most common source. Fresh produce, meat and seafood prices move often, and small increases are easy to miss on a busy delivery day.
- Menu prices that stay the same. Menus are expensive to reprint and nobody wants to raise prices, so costs move and prices do not.
- Portion drift. Portions slowly grow, especially with new staff or when nobody weighs.
- Waste. Over-ordering, spoilage, mistakes in the kitchen and staff meals that are not recorded.
- Mix changes. Customers shift towards dishes with a higher food cost, so the overall percentage rises even though no dish changed.
- Substitutions. A cheaper ingredient is out of stock and a more expensive one is used instead, at the same menu price.
Two numbers worth tracking
Theoretical food cost per dish. What each dish should cost, from its recipe and current ingredient prices. When an ingredient price changes, every dish that uses it changes too. Tracking this tells you which dishes have become less profitable, without waiting for a stock take.
Actual food cost overall. Purchases (adjusted for opening and closing stock) divided by food sales, for a week or a month. The gap between the theoretical and actual figures is waste, portioning, theft and recording mistakes.
You do not need both to start. Even tracking ingredient prices from each supplier, week by week catches most of the creep.
Watching supplier prices in your own data
If your purchasing or inventory system keeps each delivery's lines with a unit price, you can see price changes per ingredient. Here is an example for MySQL, assuming a purchase_lines table:
SELECT p.item_name,
p.supplier_name,
YEARWEEK(p.received_date, 3) AS week,
ROUND(SUM(p.qty * p.unit_price) / SUM(p.qty), 2) AS avg_unit_price
FROM purchase_lines p
WHERE p.received_date >= CURDATE() - INTERVAL 12 WEEK
GROUP BY p.item_name, p.supplier_name, YEARWEEK(p.received_date, 3)
ORDER BY p.item_name, week;
On SQL Server, group by DATEADD(week, DATEDIFF(week, 0, p.received_date), 0) instead of YEARWEEK, and use DATEADD(week, -12, CAST(GETDATE() AS date)) for the date filter.
Using SUM(qty * price) / SUM(qty) gives a weighted average, so one small top-up order at a higher price does not distort the week.
Look for items whose price has gone up steadily over several weeks, especially the ones you use in your best-selling dishes.
Seasonal swings are not creep
Fresh produce prices naturally rise and fall with seasons and weather. Seafood is often dearer before festivals. These swings are normal and usually reverse. The things to look out for are:
- Increases that do not come back down after the season.
- One supplier rising while others stay flat for the same item.
- A steady upward staircase over months, which is usually a supplier passing on costs a little at a time.
Comparing with the same weeks last year helps separate the season from the creep.
What to do when you see it
- Talk to the supplier with specific figures: "Your price on prawns has gone from $X to $Y over eight weeks."
- Get a comparison quote for the items that rose the most.
- Re-cost the affected dishes and decide which to reprice, re-portion or rework.
- Check portions on the dishes where actual cost is well above theoretical.
- Make price changes visible. A short weekly list of every ingredient whose price changed, in front of whoever runs the kitchen, is one of the most effective habits a restaurant can have.
Seeing the creep without the spreadsheet
The difficulty is the same as in retail: slow changes are hard for people to notice and easy for a computer to track. Nobody has time to compare hundreds of ingredient prices every week by hand.
Cuedis reads your purchasing and sales records from the MySQL or SQL Server database your system already uses. It learns the usual price of each item from each supplier, watches slow trends separately from one-off changes, and puts it in the morning briefing when something has been creeping up, for example "plywood creeping up about 1% a week" in a renovation business, or cooking oil in a kitchen. If your system keeps recipes, you can then ask in plain words which dishes use it.
Food cost is decided in hundreds of small moments every week. Watching the trend, rather than waiting for the month-end figure, is how you keep it where you planned it.