What Does a Dish Really Cost Me to Produce?

The honest short answer: ingredients alone are almost never enough

A dish usually costs me noticeably more to produce than the sum of the ingredients on the purchase invoice. To get a usable number per portion, I add up recipe quantities, yield after trimming or cooking, waste, small extras such as dip cups or takeaway packaging, and a fair share of direct kitchen labor. A pasta plate that first looks like €2.90 in food cost can easily land at €4.20 or more in reality. That gap decides whether a bestseller truly earns money or just creates a lot of revenue. Even one extra bread basket or 15 milliliters more sauce can shift the calculation in a visible way.

I separate the question into three levels so my team and I talk about the same thing. First, pure recipe cost: everything that physically ends up in or with the dish. Second, production-near add-ons such as bread on the side, oil usage, a small bowl, a napkin for takeaway, or packaging. Third, overhead such as rent, cleaning, admin, or music licensing, which I do not force into the production cost of a single plate. When staff ask what a dish “really costs,” I usually mean the first two levels. For price decisions, the rest comes later. That keeps the calculation understandable, comparable, and discussable during a menu review without turning it into number chaos.

A concrete example: chicken pasta calculated realistically

Take a chicken pasta with cream sauce, mushrooms, and arugula. Per portion, I store 120 grams of dry pasta, 140 grams of raw chicken, 80 grams of mushrooms, 120 milliliters of base sauce, 12 grams of Parmesan, 8 grams of arugula, and 5 milliliters of lemon oil. Then I do not work with pack prices in a vague way, but with cost per gram or milliliter. If a 5-kilo bag of pasta costs €11.00, then 120 grams cost about €0.26. That is how a guessed price turns into a verifiable portion cost. If the pack size changes, for example from 5 kilograms to 3, I update the base immediately instead of waiting until I change the selling price.

For the chicken, I do not simply calculate with raw weight. If 1,000 grams raw cost €8.40, but after trimming and cooking only 780 grams remain usable, then 1 gram ready to serve costs about €0.0108. For 110 grams on the plate, that is roughly €1.19. Add pasta at €0.26, mushrooms at €0.22, sauce at €0.54, Parmesan at €0.20, arugula at €0.09, and oil at €0.05, and I already reach €2.55 in recipe cost. If I then add €0.35 for small materials and €0.60 for direct kitchen labor, the dish costs me around €3.50 to produce. If I also give a piece of focaccia as a standard side, I need to add that cleanly as well.

Yield often matters more than the supplier’s list price

The biggest lever is often not the supplier’s list price but the yield. So I ask: how much of what I buy actually becomes saleable portion output? That applies not only to meat and fish, but just as much to herbs, cheese, sauce, vegetables, or frying oil. A crate of arugula with high discard, Parmesan left on the grater, or sauce reduced too far changes production cost immediately. If I only enter ideal values, I flatter my margin and later wonder why turnover looks strong while the result stays weak. Especially with seasonal products, I check after the first two deliveries whether my assumed yield really holds up in daily service.

Base recipes in particular need careful maintenance. If I cook a 6-liter batch of cream sauce, but after reduction and straining only 4.8 liters remain saleable, that loss belongs in the calculation. That is why I work with base recipes that include material cost, yield, and waste instead of estimating each portion from memory. In Bonzumo, I can assign ingredients and quantities to products and maintain base recipes with yield; the calculation then shows the resulting recipe cost. You can see that structure in Understand what goes into every dish on your menu. The deciding factor is still my own data maintenance: if the kitchen lead changes quantities and nobody updates the recipe, even a good calculation view becomes inaccurate.

What I charge to the plate — and what deliberately stays overhead

Not every expense in a restaurant belongs in the production cost of one dish. I assign to a plate only what is directly required for its production or can reasonably be allocated per portion: ingredients, sides, packaging, garnish, production-related losses, and direct kitchen labor. Rent, music licensing, office software, or front-of-house cleaning stay overhead at first. Otherwise almost every dish starts looking artificially expensive, and I lose sight of which product is operationally efficient and which is problematic. This separation also helps me compare a lunch special honestly with an evening dish, even though both use the same room and the same kitchen.

In daily practice, I use a simple rule: everything that goes out with the dish or typically occurs with every plate sold may go into the production calculation. Everything that would exist even without that dish stays outside it. A takeaway box belongs in; the monthly kitchen rent does not. A disposable dip cup for a standard side belongs in; general dishwasher maintenance does not. This distinction prevents arguments over terms. Then the kitchen talks about portions and production, while I talk about profitability, without using the same number for two different questions. When I later look at full cost, I label that consciously as the second calculation stage.

Include direct kitchen time without pretending to be exact to the second

For me, labor belongs in the production question, but only as a clearly defined direct production share. I do not time every pan movement to the second. Instead, I calculate recurring work steps: cooking sauce in batches, portioning chicken, finishing pasta, plating the dish. If a sauce batch takes 30 minutes and yields 40 portions, I spread that time across the batch. The minute value is my internal operating figure based on wages, payroll on-costs, and productive kitchen time; it is not an official industry standard. For a complex weekend special, that figure can be higher than for a standardized lunch item with a clear mise en place.

What matters is not charging the same work twice. If the base sauce already includes production time, then in the finished dish I count only the final cooking and plating. This is exactly where many mistakes happen, especially when several people maintain recipes. The opposite mistake is just as dangerous: counting no direct labor at all and making a labor-heavy plate look as cheap as a simple counter item with similar food cost. That is why I discuss with the kitchen lead and shift supervisors which steps truly belong to the batch and which belong to each portion. For new dishes, I review that assumption after one week in real service and correct the minutes per portion if needed.

The typical calculation mistakes behind dish costs

The most common mistake is using a purchase price without a quantity reference. A can of coconut milk costs €2.10, so people feel it is somehow “spread across several dishes” without ever measuring how much goes into one portion. The second mistake is outdated master data after a supplier or pack-size change. The third is silent waste: bread on the side, herbs sprinkled at the pass, oil in the pan, or training portions for new staff. Each item looks small on its own; together they eat the margin. Many supposedly strong dishes tip precisely because of these details. Another classic error is calculating with raw weight for products that are portioned only after cooking.

I catch these mistakes through organization. Every recipe has a responsible person and a date of last review. Volatile items such as meat, cheese, or fresh vegetables get checked more often than dry stock. If complaints arise like “portion too small” or “too much is left over,” I do not look only at the guest conversation; I also look at the calculation. Maybe the target quantity is unrealistic, or maybe too much is being ladled at the pass. It also helps when Give service, kitchen and bar a shared view of orders, so follow-up questions, notes, and portion instructions do not disappear into scraps of paper. That lets me compare later changes against both recipe data and actual production practice.

From production cost to a price decision without thinking errors

Production cost is not yet the selling price, and it is not yet the profit. For pricing decisions, I calculate on one consistent basis, net or gross, but never mixed. In Germany, as of 01.01.2026, restaurant and catering services for food are again subject to 7% VAT, while drinks are excluded from that rule and generally remain at 19%; the basic rule is set out by the Federal Ministry of Finance and in Section 12 of the German VAT Act. So if I compare food-cost ratio or margin, I do it on the same tax basis throughout.

In practice that means this: if my pasta dish sells for €15.90 gross and, as a food item, is taxed at 7%, I divide by 1.07 to get the net revenue. Only that net revenue gets compared with production cost, not the gross selling price. Otherwise I distort the food-cost ratio and the margin. If the dish costs €3.50 to produce, that is only the starting point for the next question: does the remaining contribution margin cover payroll, rent, energy, risk, and a sensible owner margin? That is how I organize fair price decisions: first honest production cost, then a clean tax basis, then the business decision. If the market will not accept the necessary price, I would rather change the recipe or the portioning than beautify the cost calculation.