How to Factor Energy Costs Into Dish Costing Properly

Why I no longer leave energy costs out of dish costing

Yes, energy costs belong in dish costing. I do not treat them as an ingredient cost, but as a separate production or overhead share per dish. That is exactly where they are often forgotten, even though stoves, ovens, fryers, refrigeration, dishwashing and hot holding all help pay for every plate. If I ignore them, a dish may look profitable on paper while failing to carry its real cost in day-to-day service. I notice this most clearly with braised dishes, baked items, fried food and anything that needs to be kept hot or cold for a longer time.

The usual mistake starts when only ingredient purchase prices are maintained properly. Then the lasagne in the costing includes flour, milk, meat and cheese, but not the 45 minutes of oven time plus preheating. For me, the practical question is therefore not whether energy matters, but how I assign it fairly to a dish. I do not need a perfect engineering model for that. I need a stable rule for the business, one I can apply consistently, review regularly and explain to my team when prices change or recipes are adjusted for the next menu cycle.

Which costs I include specifically and which ones I keep separate

I separate three levels. First, the pure recipe cost: ingredients, quantities, yield and waste. Second, the energy-related production effort: cooking, chilling, hot holding, dishwashing and, where relevant, ventilation during the production window. Third, general operating costs such as rent or base lighting, which I do not allocate millimetre by millimetre to each portion but still carry in my pricing logic as overhead. This separation keeps me from counting energy twice or not at all. An espresso has low ingredient cost, but the machine and standby time still matter. A cold bowl needs little cooking energy, yet refrigeration and mise en place are part of it.

It is also important not to hide everything inside a vague markup. If I say every dish gets ten percent for energy, that may be excessive for a salad and far too low for an oven dish. I prefer working with production groups instead. For example: cold assembled, briefly pan-fried, long-cooked, fried or baked. Each group gets its own surcharge or minute value. That keeps costing manageable and closer to reality. Especially for daily specials or short seasonal menus, this saves repeated debates and reduces the temptation to correct prices later based on instinct alone.

A practical example: oven-baked lasagne versus a cold bowl

Take two deliberately hypothetical lunch dishes: an oven-baked lasagne and a cold couscous bowl. Both appear on the menu at 12 euros gross. For food in Germany, I need to check tax treatment carefully. Since 01 January 2026, restaurant and catering services for food are again generally subject to 7% VAT, while drinks are excluded from that rule and generally remain at 19%, according to the Federal Ministry of Finance guidance and the German VAT Act. So 12 euros gross for a food item equals 11.21 euros net.

If the bowl has recipe costs of 3.10 euros and the lasagne 3.60 euros, the difference looks small at first glance. But if I assign 0.25 euros of energy to the bowl and 1.10 euros to the lasagne, the contribution margin changes noticeably. Suddenly the more expensive ingredient is not the main issue; the energy-intensive production is. These are exactly the cases I miss when I compare only food-cost percentages. The lasagne may still deserve its place on the menu, but then I decide consciously: a smaller portion, a better prep window, a different selling price, or a side that raises the guest’s perceived value in a clear and defendable way.

How I calculate energy costs without complicated metering

I start pragmatically with a monthly number. I collect the business’s electricity, gas and similar energy costs and mark the share that is mainly kitchen- and food-related. After that, I do not spread it blindly across all items. I distribute it by productive kitchen hours or by production groups. A simple method is this: energy-relevant monthly cost divided by productive kitchen hours gives me a cost per hour. I then assign realistic kitchen time windows to dishes, such as six minutes on the stove, twelve minutes in the fryer or forty minutes in the oven including a share of preheating. It is not perfect, but it is surprisingly useful in practice.

The model becomes more robust if I group devices. A fryer can have its own hourly value, a combi oven another, and cold production almost no cooking value at all. That way my kitchen lead does not need to know every kilowatt-hour, only the typical path of a dish. A schnitzel with a fried side follows a different energy logic from a salad with pre-cooked chicken. One common trap matters here: device time is not automatically portion time. If ten trays are in the oven at once, I need to spread that energy over the produced quantity, otherwise each single portion looks artificially expensive in my costing sheet.

When an energy surcharge is fair and when it distorts prices

An energy surcharge is fair when it reflects the actual production reality and makes my pricing logic easier to understand. It distorts prices when I use it as a rescue tool for every weak calculation. For example, if a dessert only looks expensive because I loaded too much refrigeration cost onto it, I may overprice one of my strongest sellers for no good reason. On the other hand, a dish that braises for hours can seem cheap if it carries the same surcharge as an open sandwich. That is why I do not just check the percentage. I also ask what role the dish plays on the menu: anchor item, add-on sale, mixed-calculation support or premium plate.

For the decision, I use four questions. First, how energy-intensive is production per sold portion in reality. Second, how much does volume fluctuate, because a single plate and a large batch are not the same thing. Third, how price-sensitive are my guests in that segment, such as weekday lunch versus evening dining. Fourth, is there a practical alternative, such as bundling prep, changing the cooking method or replacing a side. The right solution is not always a higher price. Sometimes it is enough to smooth a production step, fill an oven run better, or offer a dish only on days when that production is already running anyway.

How I organise this cleanly in the business

In the system, I first maintain the reliable base: ingredients, quantities, yield and waste in the recipes. That is exactly where I use the structured recipe and costing foundation in inventory management. There I can see clearly what a dish costs from the ingredient side and assess target food cost and selling price on a factual basis. I keep the energy share as a deliberate operating rule outside the plain ingredient list, so my team does not start treating electricity like butter or rice. That separation keeps master data tidy and makes discussions clearer when a recipe performs well on paper but not in service reality.

From an organisational point of view, I define who maintains what. Purchasing or the kitchen lead updates ingredient prices. I as the operator, or the responsible head chef, review energy surcharges by production group each month. For new dishes, we run a short costing check before the menu goes to print, using an extra field on our internal sheet: recipe cost, energy share, target contribution margin and final net selling price. Net is the reliable basis; gross and net must not be mixed. For food taxed at 7%, net equals gross divided by 1.07, as set out by the Federal Ministry of Finance guidance and the German VAT Act.

How I notice that my costing still is not reliable enough

One warning sign is when energy-intensive dishes are popular but contribute less than expected by month end. Then I do not look only at revenue. I look at patterns: long cooking times, many small production batches, extended hot holding, heavy dishwashing load and poor utilisation of certain devices. For this review, clean sales and closing views help because I can see when and how often items actually sold; that is where I use the connection provided by reporting and closing. It does not automate energy costing, but it shows me where my assumptions about volume or production density no longer fit the real flow of the business.

The second common mistake is simple convenience. An energy surcharge gets set once and then sits unchanged for months even though opening hours, equipment, prices or production methods have changed. Then I am costing based on historical habits instead of the current operation. My answer is a fixed review rhythm: immediately when energy prices shift sharply, otherwise at least quarterly and again before a menu change. If I find that a surcharge is too rough, I do not keep simplifying blindly. I change the logic. Two usable production groups are better than six theoretical ones that nobody in the house can later apply consistently or explain with confidence.