How to Control Food Cost in a Restaurant More Effectively

Start with the dish, not with purchasing

I control food cost most effectively by breaking every sold dish down into ingredients, quantities, yield and the actual selling price. That is the key decision point. I do not start by chasing a supplier discount; I start by asking whether my menu is economically built around the recipes we actually produce. If a pasta dish looks attractive to guests but barely contributes because the garnish is too generous, the base sauce is too expensive and the margin is too thin, no hurried warehouse savings will fix it. I need an honest cost basis per plate first, otherwise I am treating symptoms instead of the cause.

In practice, that means I keep ingredients and quantities cleanly maintained for every relevant dish, even for seemingly small items such as oil, herbs or dip sides. In Bonzumo, I can assign recipes to products and review the resulting recipe costs; base recipes can also reflect material cost, yield and waste. That lets me see not only the purchase price of a kilo of tomatoes, but what a portioned tomato sauce really costs in service. This way of working starts with master data. If my kitchen team maintains units inconsistently or recipes are outdated, every later evaluation becomes unreliable, no matter how carefully I read the numbers.

Food cost often falls through smaller standard deviations

In daily operations, high food cost surprisingly often does not come from one big mistake, but from many small deviations. One cook plates fries by feel, another colleague pours wine a little too generously, the pass adds too much garnish to each plate, and prep is planned without a fixed yield. Each deviation looks harmless on its own. Over a week, though, those differences add up to a real loss of result. That is why I do not treat food cost as an office KPI only, but as a production standard. The fair question for my team is not who is to blame, but where we lack clear quantities, suitable tools or understandable rules.

A fictional bistro example makes that visible. My Caesar salad sells well, yet its food cost swings too much. When I check it, I do not find one dramatic outlier but three causes at once: too much dressing per portion, inconsistent chicken weights and croutons made from fresh baguette instead of sensibly using leftovers. The answer is not a blanket ban or a lecture about discipline. I define portioning aids, adjust the recipe and explain to the team why this dish is economically sensitive. Quality stays intact, while the cost becomes predictable. That is usually a stronger lever than negotiating one more cent off a carton.

Plan purchasing only in view of stock and menu

Many restaurants spend unnecessarily because purchasing, storage and menu planning are treated as separate topics. I control costs better when I connect three questions before ordering: what we will probably sell in the next few days, what is already in stock and which recipes draw on the same item several times. If I order by gut feeling alone, I buy safety quantities that later turn into spoilage, panic re-orders or improvised specials. A lower unit price helps me very little if the purchased quantity does not match the pace of sales. Good purchasing is therefore mainly a quantity decision, not just a price negotiation.

Bonzumo supports that process because suppliers, purchase orders, item information and stock can be maintained within the same inventory workflow. It does not replace my judgment, but it helps me make that judgment on one shared data basis. If I change the menu for a coming weekend, I first review the affected recipes, then check the existing stock and only then plan the order. That sequence prevents duplicate entry and blind top-up buying. If you want the product context behind recipe structure, counting and purchasing preparation, the clearest starting point is Understand what goes into every dish on your menu.

Stocktaking is not a monthly ritual, but a control tool

Food cost is very hard to control reliably if I count once a month and then act surprised about variances. For me, stocktaking is above all a structured conversation with the business: do the counted quantities, recorded stock and lived routines still match? I check sensitive items such as meat, fish, spirits, coffee or frying oil more frequently in smaller cycles. That saves time and makes causes visible. If I only notice after four weeks that a product keeps disappearing or being recorded wrongly, nobody in the team can still explain its origin precisely. The later I count, the more I am guessing instead of managing.

In Bonzumo, stocktaking is there to capture and evaluate counted quantities, not as a magical full automation. In daily work, that is exactly what helps, because I can investigate deviations deliberately. For example, I may set a short weekly rhythm for the bar and a longer rhythm for dry storage. What matters is that everyone works with the same articles and units. A classic pitfall is mixed package logic: one person counts bottles, another liters, a third notes opened goods without a rule. What looks like shrinkage then is often just an organisational error. If I do not standardise the count, I should not trust the conclusion.

Separate waste fairly: production, spoilage, error, theft

As soon as inventory variances appear, I need to distinguish carefully as the operator. Not every loss is shrinkage in the narrow sense, and certainly not every difference is a suspicion against employees. I separate four groups: production-related loss, spoilage, service or booking errors, and only at the very end possible unexplained removal. That order matters because it protects my team and improves the analysis. If bread is discarded daily because I order the wrong quantity, that is not personal misconduct. If a sauce repeatedly spoils, the issue may be cooling, prep timing or container size. Only the right category leads to a useful solution.

A practical example is chicken breast in lunch service. If stock is missing at month end, I first check whether the trimmed yield stored in the recipe is realistic. After that I look at spoilage from overproduction, then wrong stock postings or undocumented staff meals. Only when those points have been reviewed properly do I speak about implausible losses. That approach is fairer and more effective than broad suspicion. It also keeps leadership credible: people report mistakes earlier when they know I distinguish between process weakness and misconduct. Cost control improves faster when the team trusts the method behind it.

Read sales, kitchen and closing together

I control food cost better when I do not treat sales reality and production reality as separate worlds. A dish can look profitable on paper and still create problems if it is often voided, rung in incorrectly, produced twice or left standing at the pass. That is why I watch not only recipe cost, but also the path from ordering to the end of the shift. When bar, kitchen and service work from the same order context, follow-up questions become concrete: was it actually sold, correctly produced, voided or later replaced? That link prevents me from blaming every deviation on purchasing or on the kitchen alone.

Bonzumo helps here through its order and closing context. Production stations and kitchen monitors show open and processed orders within each station, while receipts, voids and time stamps keep transactions traceable. That is not an automatic food-cost rescue, but it is a real organisational advantage. If I find that dessert usage fluctuates because items are often triggered incorrectly and then remade, I do not blindly change the recipe; I change the workflow. The operational handover is easier to picture in Give service, kitchen and bar a shared view of orders, because that exact transition between front and back of house is the central point there.

Use a few metrics, clear responsibilities and a calm rhythm

To make food-cost control hold up in daily work, I limit myself to a few fixed weekly metrics: recipe cost for the most important dishes, targeted counts of sensitive items, spoilage in euros, unusual top-up purchases and conspicuous deviations by storage area. More spreadsheets do not automatically make me smarter. What matters is who maintains and reviews what. A head chef may own recipe changes, a shift lead may document spoilage reasons, the office may review order quantities and I decide which dishes need a price or concept adjustment. Food cost stays a leadership task that is shared clearly, not a lonely spreadsheet exercise.

The biggest trap is activism. If I react to rising costs by immediately shrinking portions, buying cheaper products and raising prices at the same time, I quickly lose quality, team trust and menu logic. A calmer sequence works better: first maintain the data, then choose two or three obvious cost drivers, observe their causes in the operation, adjust the standard and review the effect after a defined period. A fictional example would be focusing first on the burger, the bowl and the house dessert because the volume effect is highest there, instead of rebuilding the whole menu. That turns food-cost control from a savings reflex into a fair, manageable improvement process.