What Does Running a Restaurant Kitchen Really Cost?

The honest short answer: the cost is not the stove, but the total of all the work around it

Running a restaurant kitchen really costs as much as food, labor, energy, space, cleaning, equipment, depreciation, waste, and organizational mistakes add up to. Anyone who looks only at food purchasing almost always underestimates the kitchen by a wide margin. In a plausible example for a mid-sized restaurant with €120,000 monthly revenue, the kitchen can easily tie up a five-figure amount per month before any profit is left. What matters is not a magic industry benchmark, but how cleanly I assign every cost category to a real kitchen process: purchasing, prep, production, service pass, storage, and end-of-day work.

I never explain this in my operation with a single ratio, because a lunch-driven kitchen with fast table turns costs differently from an evening restaurant with heavy mise en place. A pasta dish sold for €18 may look simple on the menu, yet butter, hard cheese, boil-off loss, labor time, dishwashing effort, and last-minute re-prep can make it surprisingly expensive. So the real question is not only what the kitchen costs, but which costs I reliably carry per dish sold. Only then do I see whether my price works, whether the team has enough breathing room, and whether certain dishes truly support the business or merely create the appearance of turnover.

Food cost: the box is visible, but yield and prep are often where it gets expensive

The first major block is food cost, but I do not calculate it only with supplier prices. I calculate with what actually lands on the plate after trimming, portioning, and cooking. If I buy 10 kilos of vegetables but lose peel, stalks, and cooking weight, the usable share is what matters. The same applies to meat cuts, fryer oil, bread sides, dips, and garnish. A soup does not cost only the crate of tomatoes; it also includes stock, garnish, transfer loss when decanting, and the question of whether I have to throw away two liters at the end. This is exactly where many kitchens create hidden extra cost that disappears in rough calculations.

For my team, that means we maintain recipes and base recipes so ingredients and quantities remain traceable. In Bonzumo, I can assign ingredients and quantities to an item, store base recipes with yield and shrinkage, and then review the resulting recipe cost. In practice, that means a prepared tomato sauce gets its own cost basis, and the pasta dish pulls that foundation into costing in a structured way instead of by gut feeling. The benefit becomes tangible when we adjust prices or review portion sizes. If you want to dig deeper into the connection between ingredients, quantities, and costing, see Understand what goes into every dish on your menu.

Labor cost: the most expensive kitchen minute is often the unplanned one

The second major cost block is labor, and many businesses make the same mistake here: they count only the staffed hours at the stove. But I also pay for the time before the first ticket and after the last plate. That includes receiving deliveries, putting stock away, pre-production, labeling, cleaning, prep lists, walk-in organization, and short kitchen-service handovers. One example: if two cooks each need to arrive 45 minutes early to prepare sauces, the salad station, and dessert mise en place, that is not a side note. It is a fixed part of kitchen cost. An equally expensive problem is a poor handover, when the late shift first has to search for half-finished prep instead of continuing smoothly.

That is why I look at productive and unproductive kitchen time for each sales phase. A quiet hour in the afternoon can be useful if it creates deliberate prep for the evening; it is expensive if it is simply idle time with the kitchen fully running. To organize this fairly in the business, I do not just discuss who stayed longer, but why. If, for example, every Sunday from 5 p.m. onward a second station is regularly needed just to absorb fries, salads, and re-prep, that workload must be included in the costing of the popular dishes involved. Otherwise I celebrate high plate counts while every peak period quietly eats up extra labor cost that was never properly reflected in the selling price.

Energy, space, and equipment: small amounts day to day, big totals by month-end

Many operators underestimate fixed and semi-fixed kitchen costs because they rarely appear in one visible place. Electricity for refrigeration, extraction, combi steamers, and dishwashing continues even when no ticket is coming in. Gas or extra electricity for peak production, water use, cleaning chemicals, workwear, knife-sharpening service, small tools, waste disposal, and maintenance belong here as well. If refrigeration is badly organized and doors stay open too long, the result is not only a higher spoilage risk but also higher ongoing energy demand. In other words, the kitchen costs money even when nobody is actively cooking. That is exactly what overly optimistic monthly calculations tend to leave out.

I do not try to allocate these positions to the cent per plate. I spread them across the month in a way I can explain, then test what level of kitchen output they must support. For example, if my business carries a high electrical load because of a long cold chain but produces relatively little evening revenue on two weekdays, the question is not only how to save energy. It is whether that production breadth on those days makes commercial sense at all. Equipment wear is part of the same reality. A fryer does not cost me only at purchase, but through cleaning, oil, maintenance, and the consequences of downtime. The moment a device fails and the team has to improvise, labor pressure and the error rate often rise immediately.

Waste, spoilage, and failed production: this is where margins disappear quietly

A kitchen does not become expensive only when something dramatic goes wrong. It becomes expensive mainly through small, repeated losses: oversized side portions, forgotten prep, spoiled herbs, incorrectly timed re-production, burnt components, or a dessert batch prepared ahead and then left unsold. In my example business, even daily waste of only a few dozen euros can add up to a four-figure monthly total. During service, that barely stands out, because no single incident looks catastrophic. Taken together, though, this is exactly what decides whether a dish earns money or merely creates work.

That is why I organize stock control and inventory not as an annoying obligation, but as a checkpoint against silent losses. Bonzumo supports this with product information, stock movements, and inventory for recording counted quantities. It does not automatically solve every mystery behind a discrepancy, but it helps us review counted stock in a structured way against stored items and units. In practice, that means if olive oil, ground beef, or a prepared base keeps showing unexpected differences, we look specifically at portioning, storage access, or ordering rhythm instead of vaguely claiming there is “too much consumption.” That turns gut feeling into something the team can actually clarify.

A realistic kitchen example: how I build a monthly cost range

Take a deliberately hypothetical bistro restaurant with €120,000 monthly revenue, of which €85,000 comes from food. Assume kitchen food cost sits between €24,000 and €29,000, and pure kitchen labor cost including prep and close-down sits between €22,000 and €32,000. Add energy, water, and cleaning effort at perhaps €4,000 to €7,000, plus maintenance, small supplies, waste disposal, laundry, and depreciation somewhere around €3,000 to €6,000. Then the monthly kitchen cost block quickly lands in a rough range of €53,000 to €74,000. That is not a market price. It is a transparent framework for building your own calculation.

What I am not doing with this example matters just as much. I am not claiming a universal percentage that fits every business. A small fine-dining kitchen with high labor intensity and fewer covers can be far more expensive per dish than a focused lunch concept with a short menu and heavily standardized mains. On the other hand, a broad menu can make the kitchen look attractive while rarely ordered dishes quietly inflate storage, prep, and spoilage. So I ask by category: which dishes actually contribute margin, which ones block space, which ones require special prep, and which ones only add complexity? Only from that angle does revenue turn into a reliable picture of kitchen performance.

How I control kitchen costs in daily operations without cutting the kitchen to pieces

I do not reduce kitchen cost first by general austerity, but by making better decisions. I check which dishes use the same base preparation, where portions are inconsistent, which delivery frequency encourages spoilage, and on which days prep production is too ambitious. If a ragout sells strongly only on weekends, I prepare it differently from a constant mover such as fries or Caesar salad. A common trap is confusing popularity with profitability. The top-selling dish can still perform worse than an unremarkable classic because it requires more labor and delivers lower yield. That is why I always look at the menu, purchasing, and production flow together instead of treating them as separate topics.

To keep service, kitchen, and closing from working in isolated islands, a shared data basis from sale to follow-up is genuinely helpful. When orders remain visible in the same process, I can connect real sales activity, production pressure, and later review much more clearly. For kitchen organization in particular, it helps that Bonzumo can route orders to production stations and kitchen monitors in the relevant station context, so the team sees open and completed work in a structured way instead of relying on shouted updates and paper slips. If you want to see that operational connection more closely, read Give service, kitchen and bar a shared view of orders. In the end, the fair solution is never blind cost-cutting, but a kitchen whose real effort I can finally see clearly.