Managing Food Cost, Costing and Selling Prices Together

Purchase prices and selling prices should not live in separate worlds

You keep food cost, costing and selling prices in view together when you do not maintain three different sets of figures, but one clean path from ingredient to sold dish. That is exactly where BonZumo helps with item and ingredient management, recipes, base recipes, costing views and price management. The decisive factor is not just the software, though, but that your units, quantities and responsibilities are set up properly.

In day-to-day business, price decisions usually fail not because nobody can calculate, but because the data is scattered. Purchasing thinks in kilos, bags and cases, the kitchen thinks in grams, millilitres and portions, and sales thinks in dish prices. If those levels are not connected, a dish on the menu may look profitable even though its current food cost has already risen. That is why every pricing decision should start from the same maintained items that also make up your recipe.

The ingredient unit determines how reliable your costing will be

The most common mistake happens when an item is created. If you buy hard cheese as a 1 kilogram pack, but the kitchen calculates with 35 grams per portion, that relationship has to be clear. A purchase price of 14 euros per kilo is usable for costing. A price such as "one pack costs 14 euros" is only enough if the pack size is stored cleanly as well. Otherwise your business later compares piece prices with gram consumption without noticing.

In BonZumo, it is therefore worth maintaining ingredients in a way that lets your team immediately recognise which unit applies to purchasing and which quantity is used in the recipe. That is not a side issue, but the basis for keeping recipe costs understandable. If the cheese price rises, you do not want to guess again what that means for a pasta dish. You want to see which ingredient is affected, which quantity is used per portion and how strongly the portion cost changes.

In practical terms, define first which base unit you want to use for each important ingredient. For dry goods that is often grams or kilograms, for liquids millilitres or litres, for individual goods pieces or portions. Then check whether the purchase price matches that unit. That creates one shared language between stock, kitchen and costing.

Base recipes make prep work measurable instead of vaguely expensive

As soon as you produce prep components, a simple ingredient list per plate is no longer enough. A sauce, dough, stock or topping is usually not purchased directly as one portion, but made first and then distributed across several dishes. If you only estimate that prep stage roughly, your food cost gets distorted. Then the final dish appears too cheap one day and too expensive the next, even though the real issue is that the prep stage is mapped poorly.

BonZumo covers this with base recipes. You can create a prepared component with its ingredients and quantities, and then use it in several dishes. Yield is the key point here. If you cook a batch that should theoretically produce 5 litres of sauce, but after reduction, skimming or leftovers only 4.4 litres are actually usable, that usable quantity has to flow into your costing. Otherwise you calculate with a theoretical amount that never reaches the plate.

This step is especially valuable for dishes built on volatile raw ingredients. A tomato sauce used in pasta, lasagne and a daily special would be a typical example. If the price of a central ingredient changes, you only need to adjust it in the right place. After that, you can check in the recipe views which dishes are affected instead of reworking every meal from scratch.

Portion costs only become operationally useful through recipe quantities

A higher purchase price is not yet a finished decision. Only the portion tells you whether you need to act. Take a hypothetical pasta with 35 grams of cheese per plate. If the cheese costs 18 instead of 14 euros per kilo, the cheese share per portion rises from 0.49 to 0.63 euros. That difference looks small, but together with further increases in pasta, butter, cream or energy, a dish that seemed stable can quickly become a real cost driver.

The recipe and costing views in BonZumo help precisely at this point: you do not just see the ingredient, but the effect on the dish. That makes pricing discussions in the team more factual. Instead of saying "everything has become more expensive," you can ask more precisely: Is the portion too large, is one ingredient the problem, is the base recipe too elaborate, or has the selling price simply remained untouched for too long?

It is important not to confuse food cost with total profit. Recipe costs primarily show you the material side of one portion. Rent, labour, depreciation, fees, spoilage and other operating costs are not fully contained in that single number. For day-to-day price maintenance, recipe costing is still extremely valuable because it shows you the first and often most important change: what does the dish cost to produce from the perspective of the goods used?

A purchase price change does not always require an immediate menu price change

When raw ingredients become more expensive, the obvious reaction is often to raise the selling price. That can be right, but it does not have to be. Sometimes the better decision is to review the portion first, adjust a base recipe, or temporarily change how strongly a dish is positioned. Especially with popular classics, a small quantity adjustment can make more operational sense than a sudden menu price jump that immediately irritates guests.

The strength of connected costing is therefore not that it changes prices automatically, but that it makes your decision easier. You can see which ingredient became more expensive, which dishes are affected and how large the effect is per portion. Then you decide consciously: leave the price unchanged because the dish should remain a draw, increase it moderately because the cost rise is lasting, or adjust the recipe because the current setup no longer makes sense.

That distinction matters so your business does not chase every purchasing fluctuation nervously. A one-off supplier price outlier is something different from a stable shift across several orders. Before you touch selling prices, always check whether you are seeing a short-term market impulse or a new normal. For that, you need discipline in maintaining purchasing data, not just a nice costing screen.

Margin is not the same as profit, and that prevents wrong pricing conclusions

If you want to keep food cost, costing and selling prices together in view, you need to separate two terms clearly: recipe margin and your business’s actual profit. A costing view can show how much lies between goods cost and selling price. But that does not mean the dish earns your business that amount overall. Labour effort, idle time, breakage, discounts, packaging and many other costs continue alongside it.

For your pricing decision, recipe margin is still useful because it quickly shows whether a dish basically has room or is dangerously tight on material cost. It only becomes problematic when a decent material spread is automatically treated as secure profit. That is exactly where many wrong decisions happen in hospitality: popular dishes stay too cheap because their goods cost still looks acceptable on the surface, even though they are very labour-intensive to produce.

That is why you should always put two questions next to each other internally. First: does the food cost fit the selling price? Second: does the dish also fit the real labour and operating context? BonZumo supports the first part through items, recipes and costing views. You need to add the second part as an operating decision. This clear separation makes your pricing work more reliable than any gut estimate.

Spoilage, shrinkage and yield belong in the same view as the purchase price

Many costings look good on paper and then fail in practice. The reason is often not the supplier list price, but how much of that product is actually usable. Cheese with dried edges, vegetables with trimming loss, frying oil with change intervals, herbs with rapid spoilage or a dessert topping that is portioned too generously can change food cost much more than the pure price-per-kilo calculation suggests.

That is why base recipes and yield are so important. If your team does not get 2.5 kilograms of usable product from 2.5 kilograms of raw goods, then the usable quantity has to be part of the costing. Otherwise the dish appears artificially profitable. The same applies to shrinkage during live operations. A planned recipe value is only truly helpful when you compare it with counted stock and inventory results. Not to resolve every loss mathematically, but to recognise patterns.

BonZumo supports inventory, goods information, stock movements, and the maintenance of recipes and base recipes. That helps you investigate differences more specifically. If a product should be used sparingly according to the costing, but stock drops faster than expected, you have a clear review point: portion discipline, spoilage, incorrect issue or a mistake in recipe maintenance. That is exactly where food cost returns from theory to day-to-day business.

Selling prices need fixed review rules instead of occasional gut decisions

Even good costing helps little if you only touch selling prices from time to time. A fixed review rhythm is more useful. For strongly fluctuating product groups, that may mean weekly checks for selected key items; for more stable menus, monthly or at each menu change. What matters is that you keep asking the same question: which ingredients changed materially, which dishes are affected, and what pricing decision makes sense as a result?

Price management in BonZumo gives you an organisational anchor for that. You can look at selling prices and menu structure in connection with maintained items and recipes instead of working in an isolated spreadsheet. That is especially helpful for seasonal revisions. If you first change the menu, then adjust the recipe and then review the selling price, the decision stays understandable. A quick price change without recipe maintenance only creates new confusion.

Set an internal threshold for when you react. Not every difference of a few cents needs a new menu immediately. But if several main ingredients rise at the same time or a base recipe visibly tips, that should lead to a concrete decision. You need to define that threshold yourself. The software does not decide how price-sensitive your guests are or which dishes should remain strategically important.

Team responsibilities decide whether your numbers stay current

The best shared view of food cost, costing and selling prices is not created by more calculation fields, but by clear responsibility. Someone has to update purchase prices, someone has to approve recipe quantities professionally, someone has to review selling prices and someone has to follow up inventory differences seriously. If everyone is a little responsible, in the end nobody is accountable and the numbers drift apart again.

For a smaller business, even a simple split is often enough. Purchasing maintains goods receipts and supplier prices. Kitchen leads review recipes, yields and portion sizes. Management or the owner decides on selling prices and the target food cost. What matters is that changes do not remain hidden in notes or chat messages. They should end up where your business can find them later and relate them to each other.

In practice, a monthly review appointment with three documents helps: a list of relevant purchase price changes, the affected recipes and an overview of dishes with critical material spread. Then you are not discussing expensive goods in abstract terms, but concrete decisions. That is what a shared record is for: the team sees the same items, the same quantities and the same reference points.

A simple calculation example shows whether your system really fits together

Take one dish from your menu that sells often and contains a more expensive core ingredient. In our hypothetical example, it is a pasta with a base sauce, cheese and herbs. First check the purchased cheese item with its unit and current price. Then open the recipe for the dish and check which quantity per portion is stored. After that, look at the sauce base recipe and review yield and quantity used per plate. Only then do you evaluate the selling price.

If these four steps work cleanly together, you have already built your shared view. You can see whether the cost increase affects only one ingredient, whether the base recipe distorts the costing, or whether the portion size has drifted out of control. After that, you decide more consciously whether a price adjustment is necessary or whether the kitchen should tighten up first. That is how food cost, costing and selling price become one connected management process instead of three isolated numbers.

If important information is missing during this test, you immediately know where you need to improve. If the purchasing unit is missing, item maintenance is unclear. If the usable yield is missing, the base recipe is incomplete. If the connection to the dish is missing, the recipe is not practical enough. And if the selling price is never reviewed in that context, what you lack is not another report, but a fixed operational process. That is exactly where you should start before deciding on new prices.