How do I calculate fixed and variable costs correctly?

1. Start with one time period and one clear separation rule

I calculate fixed and variable costs correctly by doing two things first: I choose one time period, usually a month, and I classify every cost by its cause. Fixed costs are the costs I still pay in that month even if I sell less than planned. Variable costs rise because I sell one more dish, one more drink, or one more takeaway order. Rent is usually fixed. Ingredients are usually variable. The mistake is rarely the arithmetic itself; it is mixing both blocks. If I put rent into recipe cost, my dish looks falsely expensive. If I leave packaging or garnish out of variable cost, my dish looks falsely profitable.

In practice, I ask one simple question for each line item: would this cost still exist this month if I sold one portion fewer? A baked potato with herb quark makes that visible. Potato, quark, salad garnish, herbs, and a takeaway box belong to the variable side because they are consumed per sale. My monthly rent does not change because I sold 280 or 340 portions, so it stays fixed. Staff costs often sit in between. My core weekday team feels fixed within the month, while extra event hours are closer to variable or at least step-fixed. I mark those grey areas openly instead of pretending to have perfect precision with the wrong logic.

2. Build the numbers from a usable list, not from vague totals

I do not begin with a rough annual estimate and then guess my way downward. I build a simple working list with five columns: cost type, amount, period, classification, and reason. Then I go through recurring items one by one: rent, utilities, leases, software fees, fixed cleaning contracts, insurance, depreciation, and the staffing base I need even before the first evening rush. On the variable side I collect ingredient prices, bread baskets, sauces, takeaway packaging, and other sale-related consumables. That distinction between business-level cost and product-level cost matters, because otherwise I either overload a recipe with costs that do not belong there or ignore small sale-driven items that quietly erode margin.

For individual dishes, a maintained recipe is far better than a memory-based estimate. If ingredient quantities and base recipes are stored cleanly, I can see what truly moves with each sale. Understand what goes into every dish on your menu is useful precisely because it helps structure ingredients and quantities as a calculation basis. A stew is a good example. I do not only record carrots, lentils, stock, and cream; I also think about yield and waste. Two kilos of raw vegetables do not automatically become two kilos of saleable portions. If I ignore trim loss or evaporation, my variable cost looks lower than reality and my later price decision starts from a false number.

3. A concrete restaurant example I can actually recalculate

Take one baked potato with herb quark and side salad as a hypothetical menu item. Per portion, I may have 0.55 euros for the potato, 0.62 euros for quark and dairy, 0.48 euros for salad and garnish, 0.19 euros for herbs and seasoning, and 0.16 euros for oil and small ingredients. That gives me 2.00 euros in pure ingredient cost. If the order is takeaway, I add 0.42 euros for container, lid, napkin, and cutlery, so variable cost becomes 2.42 euros. If I sell the dish at a net example price of 9.90 euros, the contribution margin before fixed costs is 7.90 euros in-house and 7.48 euros takeaway. The key is using one consistent basis: I calculate selling price and variable costs either net or gross, in practice usually net. Especially in Germany, I do not mix food and drinks in one margin calculation if different VAT rates apply. That number shows me immediately how much each sale helps cover the month.

Now I add the business layer. Suppose my month includes 3,200 euros rent, 480 euros fixed software and phone charges, 600 euros insurance and fees, 1,400 euros depreciation and leasing, 11,500 euros core staffing, and 1,120 euros other fixed overhead. My fixed cost block is then 18,300 euros. If I divide that by the 7.90 euro contribution margin of the in-house version, I would need about 2,317 portions of that one item just to cover those fixed costs. Of course a real restaurant lives from many products, not one potato dish. That is exactly why this calculation matters: it reminds me that a selling price must stand not only against ingredients, but against the whole running operation.

4. Handle grey areas like labour, energy, and cleaning honestly

Many costing errors appear where a cost is neither fully fixed nor cleanly proportional to sales. Labour is the classic example. If I need one cook and one service person for the basic lunch and dinner operation from Monday to Friday, I usually treat that staffing core as fixed for the monthly view. If I add a temporary extra shift for a booked private event, that extra labour is more closely tied to activity. Energy works similarly. Refrigeration, standby equipment, and basic lighting create a stable base consumption even on a slow Tuesday. Longer production, heavier dishwashing, and a full terrace increase usage above that level. So I do not force everything into two simplistic boxes without comment.

A practical example is the dishwashing area. It exists on a quiet day, but after two full evening turns it clearly consumes more water, detergent, and power. If I treat the entire utility bill as fixed, I underestimate the cost of strong trading days. If I treat all of it as variable, a weak month can look healthier than it really is. I therefore split mixed costs where I can explain the logic. A stable base goes into fixed overhead, and the activity-driven remainder stays visible as a variable share or at least an observation item. I use the same approach for laundry, delivery surcharges, or outsourced cleaning that increases with volume. Useful decisions matter more than false mathematical purity.

5. Use the few formulas that actually help in service reality

I rely on four simple calculations. First, total fixed costs for the chosen period. Second, variable cost per product or product group. Third, net selling price minus variable net cost equals contribution margin; a consistent gross basis also works as long as I do not mix methods. In restaurants, I check carefully whether food and drinks are taxed differently. Fourth, fixed costs divided by average contribution margin equals the approximate break-even quantity. This is not an academic exercise for me; it answers an operational question: does this item meaningfully help finance my business? If the contribution margin is too small, the problem is often not just purchasing cost. It may also be a selling price that is too low, weak portion control, or a product that ties up a lot of work while contributing very little. That is why I never manage only by percentages, but always also in euros per item sold.

I then compare the theory with the real selling day, because even a sound formula can fail if operations distort the result. Understand the day's activity before you close up matters here because sales and closing data can be reviewed in context. Imagine I planned to sell 120 portions in a month, but in practice the item appears with frequent corrections, discounts, substitutions, or wrong entries. Then my planned margin and my actual realised contribution are no longer the same thing. The formula remains simple, but the quality of the answer depends on whether articles, quantities, and corrections were handled cleanly during service and reviewed carefully afterward instead of being left to memory.

6. Avoid the cost mistakes that make prices look better than they are

A very common error is treating variable costs as nothing but food cost and ignoring everything else that follows the sale. In my restaurant reality, takeaway packaging, bread service, small complimentary add-ons, and garnish can all be genuinely variable. A second error is reading the month only through revenue. Sales rise, I feel successful, but at the same time longer opening hours, extra permanent shifts, or new software subscriptions may have lifted my fixed base. A third error concerns mixed costs. If I label every labour hour as fixed, I stop seeing which event, delivery stream, or late-night trade actually created useful additional contribution. Strong and weak revenue sources disappear into one blurred total, and the wrong products survive too long.

It is just as misleading to force a supposedly exact fixed-cost share onto every dish as if all items had the same strategic role. I may use overhead allocations as guidance, but not as a law of nature. A modestly priced lunch soup can still be worthwhile even if it carries less fixed cost per portion than an evening main, provided its variable cost is covered and it reliably creates traffic. On the other hand, a beautiful percentage margin on an aperitif means little if the product barely sells or causes bottlenecks during service. Correct calculation therefore means reading every number together with quantity, prep effort, daypart, and guest expectation, not admiring a margin in isolation.

7. Turn the numbers into fair pricing and better team decisions

For me, fixed and variable cost separation is not a one-time spreadsheet ritual. It becomes a rhythm. I review fixed cost lines regularly, update purchase prices, and check key recipes before I make pricing decisions. If feta becomes more expensive or potato sizes change, I do not automatically raise the menu price the same day. I first measure the effect on contribution margin and then choose between four levers: adjust the price, tighten portion control, improve the recipe technically, or keep the item intentionally as a traffic driver. A hypothetical example: if the variable cost of a salad rises by 0.38 euros, a 0.50 euro price adjustment may be smarter than damaging quality through panic-saving that guests will notice immediately.

For staff and guests, I translate these calculations into clear process instead of dry theory. The kitchen needs defined quantities and yield expectations, purchasing needs reliable units, and service needs correct articles and prices in the operational flow. I organise changes so they are documented, not passed along as corridor talk between shifts. If we switch to a more expensive takeaway bowl, I record the new cost and update the costing basis rather than saying packaging is simply more expensive now. If one dish repeatedly causes rework or guest questions, I treat that as an operational issue to improve, not as an individual blame case. That is how correct cost calculation becomes a fair basis for menu pricing, planning, and day-to-day management.