Food cost: traditional method vs Masterestaurant method

Food cost: the complete guide, from the formula to weekly control

What is food cost?

Food cost is the share of food sales that goes to paying for the ingredients used to make the dishes you sold. You calculate it by dividing the cost of food sold by food sales for the same period.

It is the first profitability indicator in any kitchen because it moves every day: it climbs with each piece of waste, each over-portioned plate and each supplier price increase, and it only comes down when someone measures it and acts. It is not the purchase price of an ingredient, and it is not the margin on a single dish: it is the ratio between what the food you sold cost you and what you charged for it. That is why two restaurants buying at the same prices can run very different food costs: the difference lives in recipes, portions, waste and the menu mix each one sells.

Food cost formula: how to calculate food cost percentage step by step

The food cost formula for a period is cost of goods sold divided by food sales, expressed as a percentage. Cost of goods sold is beginning inventory, plus purchases during the period, minus ending inventory: what actually left the kitchen, sold or lost. For a single dish the math is shorter: the cost of its standard recipe divided by its menu price before tax. The two numbers answer different questions. The dish number tells you what the plate should cost if it is made exactly as written; the period number tells you what it really cost, with waste, generous portions, ordering mistakes and staff meals included. Without a physical count at the start and end of the period, the second number cannot be calculated.

Theoretical vs actual food cost: the gap where the money goes

The gap between theoretical and actual food cost is the most useful number a restaurant has, because it is where money disappears without anyone seeing it. Theoretical food cost comes from multiplying the units sold of each dish by the cost of its standard recipe; actual food cost comes from inventory. When actual runs higher, the causes are few and well known: unrecorded waste, portions off recipe, recipes costed with old purchase prices, deliveries received without weighing or counting, and staff meals nobody logged. Measuring the gap every week, not only at month-end, lets you fix it while you still know what caused it and who can fix it.

What should food cost be for a restaurant?

There is no single ideal food cost: it depends on the concept, the check size and how heavy labor is.

As a benchmark, median food cost was 32.4% of sales in limited service and 32.0% in full service, based on 2024 data from the National Restaurant Association. A somewhat higher food cost can be healthy if the dish turns fast and needs little labor; a lower one can hide thin portions that drive guests away. That is why the number that decides profitability is not food cost alone, but prime cost: food cost plus labor cost.

Food cost and prime cost: why you track them together

Prime cost adds food and beverage cost to total labor cost, and it is the number that best predicts whether a restaurant makes or loses money. A low food cost is worthless if the kitchen needs too many labor hours to achieve it, and an elaborate menu can raise payroll by more than it saves on purchasing. In full service, labor was a median 36.5% of sales in 2024; among operators who reported a pre-tax profit it was 34.2%, according to the National Restaurant Association. Reviewing both costs together, every week, keeps you from fixing one at the expense of the other.

How to lower food cost without cutting portions?

Food cost comes down for good through five levers, and none of them is serving less. The first is the standard recipe with its recipe card:

weights, yields and an updated cost for every dish. The second is purchasing: fewer items, clear specs and prices checked against every invoice. The third is receiving: weigh and count what arrives before you sign. The fourth is waste: log it by cause at the end of every shift. The fifth is the menu: push your best-margin dishes with menu engineering. With wholesale food prices 35% above pre-pandemic levels, according to the National Restaurant Association, these levers matter more than ever.

Why does my food cost go down in the system but my restaurant still doesn't close the month profitably?

Because you're measuring food cost alone and forgetting prime cost. Food cost sits near the National Restaurant Association's 32% ceiling for full-service profitability;

sounds good. But prime cost is food cost plus kitchen and front-of-house payroll, and together they should stay within a healthy ceiling of total revenue. I've seen hundreds of owners who thought a food cost near that ceiling meant they were on track, only to discover payroll pushed prime cost into loss territory. The guardian isn't food cost, it's prime cost. Masterestaurant calculates both in parallel and shows you the truth: if food cost is fine but prime cost is well above the healthy ceiling, the fault isn't the menu, it's payroll. That lets you act fast on what really hurts. Without that parallel measure, a dangerous prime cost hides inside a seemingly healthy food cost for months until the bank calls.

Is it true that a 35% food cost is bad, or does it depend on restaurant type?

It depends. A pizzeria with handmade dough and fresh cheese can run near the low end of the National Restaurant Association's food cost range;

a sushi or steakhouse might sit near the high end if raw materials are expensive. What IS bad is not knowing why it's at 35%. I was wrong on this for years: I thought the single number was enough. It's not. Masterestaurant breaks it down and you see which protein is a high-risk outlier where changing suppliers is urgent, and which dish is an opportunity to raise price. Without that dish-by-dish breakdown, 35% is a dead number: it doesn't tell you which dish hurts or which has margin to grow. The number is only valuable if it comes with dish-level criterion. Most owners treat 35% as a verdict; Masterestaurant treats it as a starting question.

I changed suppliers three weeks ago and I don't see the savings reflected in my margins. What's happening?

There's a 2-4 week lag between the switch and the real number in your cash, because you're still selling old inventory at old cost.

Impatient owners see the new price on the supplier invoice and count the margin as won before they've actually made it. But if you bought meat on Monday from the old supplier and received the new purchase Friday, you sell that old meat until the following Tuesday. The real number appears at the first cash close after old inventory is gone. With Masterestaurant, you see exactly when that happens: dish cost drops sharply on day 8 or 9 after the switch. Without the system, you assume it worked because you think it should; with the system, you have operational proof of when the savings became real. You stop guessing and start knowing.

Can I use last month's food cost to set this month's prices?

No, and that's the root reason many restaurants don't close. If you use August food cost to set September prices, you're selling at old prices with new costs.

It's a lag that eats your margin week by week, and in sectors where tomatoes rise 12% in one week or beef falls 8%, that gap is fatal. The Masterestaurant method updates each dish cost weekly; as a result, price must be tied to CURRENT cost, not 30 days ago. If tomatoes rose 20% this week, tomato sauce must reflect that cost in today's prices, or you change recipe to hold margin. I've seen restaurants fail because they updated prices monthly while costs moved weekly; the lag was the key that opened the loss door. Traditional thinking is monthly food cost, monthly price. Real thinking is weekly cost, responsive pricing.

How do I know if I'm spending what I should on payroll for my operation size?

Prime cost should stay within a healthy ceiling of total revenue. Inside that, food cost sits near the National Restaurant Association's 32% ceiling, and payroll makes up the rest, depending on how many staff you dedicate to kitchen vs front.

A small restaurant tends to run high payroll because you don't have volume to dilute; a large one can be several points lower because employees produce more per head. I audit payroll two ways: money per shift (do I spend $5,000 payroll on $15,000 daily sales? = 33%, that's fine for your size) and productivity per person (does each cook produce $60 of food per hour worked? Below that means excess staff or poorly placed). Masterestaurant measures both and shows where inefficiency lives: idle staff or staff assigned badly to peak hours. Without that measure, a payroll number just sits there; with it, you know if you're right-sized or bloated.

I discovered my kitchen recipe isn't what the menu says. How much is that costing me?

It's one of the most common leaks I've seen, because it hides: the official recipe says 150g beef, but the kitchen makes 180g out of generosity or habit, and no one counts.

That drops the dish margin in one hit. Calculate what it costs you: ingredient difference × number of that dish sold per month × margin lost. Example: if the difference is $0.30 per dish and you sell 600 of that type monthly, that's $180 monthly walking out as kitchen generosity. Per year: $2,160. That's just one of ten dishes. Masterestaurant detects this because expected cost and real cost don't match week to week: if the system says margin should be 30% but comes out 38%, the difference is in the kitchen, not the supplier. Audit right now: weigh a dish cooked today, count ingredients for real, calculate true cost, compare to what the recipe promises. The gap is where your leak lives.

How often should I review ingredient prices if I stock only shelf-stable items: flour, rice, canned goods?

Monthly is fine for pure shelf-stable goods; they don't move like meats or seasonal produce. But there's a trap:

if your menu is 60% pasta, rice, and canned items, the other 40% (meats, vegetables, dairy) is volatile and affects prime cost overall. I'd review weekly minimum on that 40% volatile, monthly on the 60% stable. Without a system, spend 30 minutes every Friday: call three key suppliers (meats, vegetables, dairy), note changes, spot trends. That catches most of the risk. Masterestaurant automates it, but if you work by hand, 30-minute discipline once weekly is what saves restaurants: it's the difference between surprise in January ("why did margin fall?") and decision in week two ("beef rises, switch suppliers"). Traditional thinking is monthly photo; weekly manual is radar; Masterestaurant automates the radar into your phone.

What do I do if I audit and discover my real food cost is 40% or higher?

First, verify the calculation is correct: ingredient cost divided food sales, both numbers from your real flow, not estimates. If it's real, you have a two-part problem:

speed or recipe. Speed means ingredient prices changed but you didn't update dish cost in the system, so you sold at a loss. Recipe means the formula in the menu isn't what the kitchen makes: bigger portion, more expensive ingredient, different technique. Audit one dish now: weigh the portion that goes out today, count the actual ingredients it carries, calculate real cost with today's prices, compare to what the official recipe promises. The gap is where the leak lives. I've watched restaurants fix their food cost completely in 45 days just by correcting kitchen recipes, without touching selling prices; it's the most underestimated lever in the business.

If I lower food cost by cutting portions, does my margin go up?

Technically yes; operationally, you lose customers. Food cost drops 2-3 points (e.g., 32% to 29%), but customers see the smaller portion, talk about it, leave, and sales fall 10-20%, erasing the gain and moving to real loss.

It's the oldest trick in the sector and it never works. Masterestaurant doesn't lower food cost by cutting; it lowers it by improving: switch suppliers (same ingredient, lower price, no perceptible change), change recipe (similar outcome with cheaper ingredient), or raise selling price (if real margin exists, higher price is valid if the market supports it). Real improvement, not quality reduction. I've audited hundreds of restaurants, and the list of those that broke trying to lower food cost by cutting portions is long; the list of those that broke by improving supplier price without affecting customer is zero. Confuse the two paths and you ruin yourself. One builds, one destroys.

What changes in your operation?

The traditional method tells you food cost AFTER the month is over; Masterestaurant tells you DURING the week, when you can still react: change supplier, adjust selling price, or switch ingredients.

It's the difference between a photograph (post mortem) and a radar (real time). With the traditional method, a restaurant sees a 32% food cost in November and assumes everything is fine. In December, with the seasonal jump in ingredient costs, it climbs well above target, but they don't discover it until January. Masterestaurant detects the shift in the second week of December: "a key ingredient just spiked, margin is slipping, react now." It's the difference between surprise and decision.

What changes in your operation — in practice?

The traditional method uses a single number (example: 32% of cost of goods sold). Masterestaurant divides: the menu averages 32% total, but some dishes run well under that (safe), while others run well above it (fragile to changes).

This lets you know exactly which dish hurts if costs rise, and which you can expand without risk. Under the traditional method, if you audit inventory once a month and find loss to waste, you don't know when it started: two weeks ago or every week? Masterestaurant separates real waste (acceptable, ~2-3%) from abnormal waste (theft, spoilage, poor storage), because expected cost recalculates every week. Seeing the difference is seeing where it really hurts.