The right selling price starts with a clear calculation path
I calculate the right price for a dish by starting with the real recipe cost per portion, then adding the effect of yield and waste, then checking how much contribution margin the dish must leave for labour, rent, energy and the rest of the business, and only then comparing that result with the role of the dish on my menu. That means I do not price from instinct, and I do not simply double the ingredient cost and hope it works. If a bowl of pasta costs me 3.60 in ingredients, a selling price of 7.20 may still be too low because it does not properly help finance service, kitchen prep, cleaning and overhead. The right price is the one that carries the dish and the operation, not just the shopping basket behind it.
My practical target is not “as cheap as possible” but “clear enough that every portion sold truly contributes.” I work backwards from the plate: what does it cost today, what should it contribute at minimum, and what job is it supposed to do on the menu? A lunch bowl that helps fill quieter midday tables can be priced more tightly than a signature evening plate, but I still set that intentionally. I decide in advance what food-cost range I accept for each category. A guest magnet may tolerate a somewhat higher food-cost share if drinks and dessert often follow. That distinction matters because it separates real pricing from guessing. Otherwise, a dish can look popular on paper while quietly draining margin every shift.
I calculate recipe cost per portion exactly, not approximately
The most common mistake happens at the start: pricing the idea of a dish instead of the dish that actually leaves the pass. I only get a usable price when I list every ingredient with purchase unit, purchase price and portion quantity. For a tomato pasta, that might mean 120 grams of pasta, 140 grams of tomato base, 20 grams of onion, 8 grams of garlic, 12 millilitres of olive oil, 18 grams of parmesan, two basil leaves and seasoning. What matters is not that pasta is “cheap,” but that 1 kilogram at 2.40 means 120 grams cost 0.29. The same thinking applies to cheese, herbs and oil, where small amounts are easy to ignore. If I skip that detail, the error does not stay small once the dish sells a few hundred times.
I also break every base preparation down to a usable production unit. A sauce is never “one pot” in my calculation; it is, for example, 3.2 kilograms of finished sauce after cooking and reduction. Only then can I calculate the cost per 100 grams or per ladle. The same applies to dressings, stocks, dips and crumb mixes. This is where hidden cost often builds up: a base recipe feels cheap in bulk, yet expensive in actual plated portions. If a batch of tomato sauce costs 11.84 and yields 3.2 kilograms finished, the cost is 0.37 per 100 grams. A 140-gram portion on the plate therefore carries about 0.52 of sauce cost. That level of recipe maintenance is exactly why I keep structured cost data for dishes and components, as in Understand what goes into every dish on your menu.
How the ideas connect
The opening sections of this article, shown together.
What path should I follow to set the right selling price for a dish?
Begin with the accurate [recipe](/en/integrations/chrome-extension/) cost per portion, add the effects of yield and waste, decide the…
The right selling price starts with a clear calculation path
I calculate the right price for a dish by starting with the real recipe cost per portion, then adding the effect of yield and waste,…
I calculate recipe cost per portion exactly, not approximately
The most common mistake happens at the start: pricing the idea of a dish instead of the dish that actually leaves the pass. I only get…
Yield, shrinkage and side items decide whether the calculation is honest
The next mistake is looking only at what I buy, not at what actually becomes saleable food. Potatoes lose weight when peeled, meat loses weight during cooking, herbs wilt, lemons are not fully usable and fryer loss is real. So I never price from gross purchase weight alone; I price from usable yield. If I buy 5 kilograms of carrots and only 4.2 kilograms remain after trimming and sorting, my true cost per usable kilogram is higher than the invoice suggests. The same logic applies when a tray bake gives me 18 portions instead of the planned 20. Each portion becomes more expensive even though the supplier price never changed. If I ignore yield, I underprice without noticing until the monthly result exposes it.
I also include every small item that teams often forget because it feels routine: the dip in the ramekin, the side salad, the lemon wedge, the bread basket, takeaway packaging, the butter portion or the extra parmesan if it is part of the standard serve. These details can easily tip an otherwise neat calculation. A schnitzel plate may look acceptable at a 4.90 food cost, but once I fully count fries, salad garnish, cranberry side, lemon, frying loss and sauce, the real figure might be 5.85. If I set my menu price from the lower number, I am short almost one full unit on every plate. A single ticket will not reveal the problem, but 300 portions in a month definitely will. Honest pricing starts where wishful omission stops.
Contribution margin turns cost into a sustainable selling price
Recipe cost gives me the lower boundary, not the final answer. The selling price must still leave enough contribution margin to support wages, rent, energy, cleaning, equipment, software and entrepreneurial risk. So for each dish I ask a simple operational question: after food cost, what remains to help fund the rest of the restaurant? What matters here is that I compare selling price and food cost on the same basis, meaning net with net or gross with gross; for actual pricing, net is cleaner. If my pasta plate costs 3.60 net and I sell it for 11.90 net, the contribution before overhead is 8.30. In Germany, restaurant food prices in 2026 generally include 7% VAT, while drinks are generally subject to 19%. The right price therefore depends on my actual cost structure, not just on an attractive menu number.
I do not use one identical multiplier for the whole menu because different categories behave differently. A simple soup with a low prep burden should not be priced by the exact same logic as a braised dinner dish that ties up labour, energy and mise en place for hours. A dessert with a high spoilage risk has another profile again. I therefore set a target corridor by category instead of chasing a single universal formula. My decision criteria are specific: labour intensity, perishability, portion reliability, waste exposure, plating time and strategic menu position. A factor-of-three rule can be a rough starting check, but if I stop there, I end up with mathematically tidy prices that still fail in service reality. Sustainable pricing has to survive a full week of actual operations, not just a spreadsheet review.
The right price also depends on the dish’s role on the menu
I never price dishes in isolation because guests do not experience them in isolation. Some items are there to open the order, some lift the average spend, and some give the menu its identity. A vegetarian lunch plate can be intentionally attractive if it helps stabilise midday traffic and often leads to drinks and coffee. A labour-heavy evening special, by contrast, has to pay its way even if the table orders only water. So I ask not only “what does this dish cost?” but also “what is this dish supposed to do on my menu?” That perspective protects me from two classic errors: the overpriced slow mover and the underpriced bestseller that keeps the kitchen flat out while contributing too little. Popularity alone is not proof of a good price.
Take a burger section as an example. I may have a basic burger that sells often, a barbecue version that sells steadily and a truffle burger that sells less often but shapes perception of quality. If I price all three only from food cost, the numbers can look consistent while pushing guests toward the wrong choice for my menu economics. The basic burger might become so attractive that hardly anyone trades up. So I consciously review the spacing between neighbouring prices: which step still feels understandable to guests, and which difference clearly reflects more value? I am not trying to trick anyone with pricing psychology. I am trying to create orientation. Guests notice when the relationship between portion, ingredients and price feels coherent, and my service team recommends more confidently when that coherence is real rather than improvised.
Regular recalculation prevents quiet losses after a good first setup
A correctly calculated price does not stay correct on its own. Purchase prices move, portion sizes drift upward, garnish gets more generous, a new pan changes cooking loss or a supplier changes pack size. That is why I recalculate regularly instead of treating pricing as a one-time setup task. I start with my high-volume items and my margin-critical dishes, not with the whole menu at once. A workable rhythm can be to review bestsellers monthly, recalculate the full menu seasonally and fully price any special before launch. If the calculation worsens, I do not automatically raise the menu price first. I check which lever is best: recipe, portioning, side composition, procurement or selling price. Good control comes from seeing the cause, not just reacting to the symptom.
For example, imagine my chicken curry rises from 3.10 to 3.85 in food cost because coconut milk and poultry became more expensive. I then have several fair options: adjust the recipe, tighten rice portioning, rethink the included side or raise the selling price. The wrong response is doing nothing because I fear guest reactions. The other wrong response is raising the price without checking whether the dish still feels convincing at that level. Sometimes disciplined portioning solves enough of the gap. Sometimes the market around my concept has already moved from 13.50 to 14.90 and I need to move with it. To review these changes calmly, I compare dish performance with my broader day and shift patterns so I can see whether the item still earns its place, using the same operational mindset as Understand the day's activity before you close up.
I organise price decisions fairly for kitchen, service and guests
I do not change prices in isolation and then expect the team to absorb the consequences. If a price goes up or a portion logic changes, I explain internally why it changed. The kitchen needs to know the intended portion standard, otherwise one cook plates 160 grams and another plates 210. Service needs to understand the value of the dish so they can describe it confidently instead of sounding apologetic. Guests deserve fairness too. A higher price is easier to accept when quality, consistency and portion expectation still make sense. What I avoid is the unfair combination of shrinking the plate, removing a side and increasing the price at the same time without properly updating the menu description. That creates distrust, and distrust is more expensive than a careful decision ever was.
In practice I use a short decision checklist for each item. First, the recipe must be complete. Second, yield must be checked. Third, the target portion must be fixed. Fourth, the required contribution margin must be defined. Fifth, the dish’s menu role must be clear. Sixth, I compare it with neighbouring dishes. Seventh, I test whether service can explain it naturally. A roasted vegetable plate at 12.90 can be fair if it includes good oil, proper feta, solid prep work and a filling side. The same 12.90 becomes weak if the portion swings from cook to cook or the plate regularly looks sparse. The right price is therefore not just a number from a table. It is the result of a business decision that my team can actually hold and my guests can experience as consistent.
Putting it into practice
Later sections put the topic in the context of day-to-day operations.
The right price also depends on the dish’s role on the menu
I never price dishes in isolation because guests do not experience them in isolation. Some items are there to open the order, some lift…
Regular recalculation prevents quiet losses after a good first setup
A correctly calculated price does not stay correct on its own. Purchase prices move, portion sizes drift upward, garnish gets more…
I organise price decisions fairly for kitchen, service and guests
I do not change prices in isolation and then expect the team to absorb the consequences. If a price goes up or a portion logic changes,…