Restaurant Food Cost Control

Why food cost gets away from you

Restaurant food cost control fails for a boring reason: most operators calculate food cost once a month, from an accountant’s report, six weeks after the money was spent. By the time the number arrives, the deliveries are eaten, the waste is in the bin, and the month you could have fixed is closed.

Food cost is not one number. It is the sum of dozens of daily decisions — what you ordered, what you paid, what you prepped, what you threw away, what you gave away, and what walked out the back door. Each of those decisions is small. Together they are the difference between a restaurant that pays its owner and one that does not.

A restaurant running at 32% food cost and one running at 36% look identical on the floor. Same guests, same tickets, same noise. On €600,000 of annual food revenue, those four points are €24,000. That is not a rounding error. That is a salary.

The only formula you need

Food cost percentage is opening inventory plus purchases, minus closing inventory, divided by food revenue for the same period. That is it. The formula is not the hard part. Running it often enough to act on it is the hard part.

Most operators can recite the formula and still cannot tell you last week’s number. The gap between knowing the formula and having the number is where restaurants lose money. Weekly beats monthly, because a week is short enough that you still remember what happened in it.

• Opening inventory + purchases − closing inventory = cost of goods used
• Cost of goods used ÷ food revenue = food cost %
• Run it weekly, on the same weekday, using the same method every time
• Count the same items in the same order so the count itself stays fast

Where the money actually disappears

When food cost climbs, operators usually blame supplier prices. Prices matter, but in our experience they are rarely the biggest line. The bigger leaks are internal, unglamorous, and entirely fixable.

Over-portioning is the quietest one. A protein portion that runs ten grams heavy on every plate does not look like anything on the pass, and costs thousands over a year. Prep waste is the second: trim that could have been stock, product prepped on a Thursday for a Friday that never came. Then there is spoilage from over-ordering, staff meals that were never costed, comps and remakes that nobody logged, and deliveries that were signed for without being weighed.

None of these show up in a supplier invoice. They show up only in the gap between what you bought and what you sold — which is exactly what a weekly food cost number measures.

• Over-portioning — the cost of a heavy hand, multiplied by every cover
• Prep waste — trim, over-prep, and product prepped for a day that never came
• Spoilage — the cost of ordering for a busy week that turned quiet
• Uncosted staff meals, comps, and remakes
• Delivery shortages — invoiced in full, delivered in part
• Theft — smaller than most owners fear, larger than most owners check

Set a target, then defend it

A food cost target is only useful if it comes from your own menu, not from an industry average. Cost every dish, weight each by how often it actually sells, and you get a theoretical food cost — the number your menu would produce if execution were perfect.

The distance between theoretical and actual food cost is your operational leak. If your theoretical is 29% and your actual is 35%, you do not have a pricing problem. You have an execution problem, and repricing the menu will not fix it. If your theoretical is 34% and your actual is 35%, your execution is fine and your menu is priced wrong. Those are two different problems with two different fixes, and you cannot tell them apart without both numbers.

A weekly routine that survives a real service week

Systems that require an hour a day do not survive contact with a real restaurant. The routine that lasts is short, fixed, and always on the same day.

Count key inventory on the same weekday, before the first delivery. Enter purchases as invoices arrive rather than in a monthly pile. Log waste at the point it happens, not from memory at the end of a shift. Then, once a week, look at one number and compare it to last week. Thirty minutes, once a week, is enough to keep food cost from drifting.

The discipline matters more than the sophistication. An imperfect count done every Monday beats a perfect count done twice a year, because trend is what tells you something changed.

How master.restaurant handles it

The master.restaurant dashboard is built around this routine. You enter revenue, purchases, inventory and payroll; it returns food cost, labor cost and break-even without spreadsheets, local files, or formulas that break when someone drags a cell.

The course covers the operational side: how to count quickly, how to read the gap between theoretical and actual, and what to change first when the number moves. Data is entered manually and deliberately — no POS integration — because the act of entering the numbers is what keeps an operator close to them.