How restaurants calculate their food cost percentage

The formula I actually use in a restaurant

Restaurants calculate their food cost percentage by dividing cost of goods used in a period by sales from that same period, then multiplying by 100. In practice, I use: food cost percentage = cost of goods used ÷ sales × 100. The cost of goods used is not simply what I bought. It is opening stock + purchases - closing stock. So if I want to know how much of my revenue was consumed by food and drink, I first have to determine what stock was actually used during the period. That is where the real discipline sits, because the arithmetic is easy but the operational groundwork is not.

A simple example shows the logic. If I start the month with stock worth 8,000 euros, buy 12,000 euros of goods, and count 7,000 euros of stock at the end, my cost of goods used is 13,000 euros. If sales in that same month were 52,000 euros, the food cost percentage is 25 percent. That number does not mean profit. It only shows how much of sales went into goods. Wages, rent, energy, packaging, and card fees are not included yet. That is why I use the percentage as a control figure, not as a shortcut to declare the month good or bad.

If the basis is inconsistent, the percentage is misleading

The crucial point is that cost of goods and sales must be calculated on the same basis, either both net or both gross. I prefer net figures because they are cleaner for comparison. In Germany, this matters even more because since 1 January 2026 restaurant and catering services for food are back at 7 percent VAT, while drinks are generally excluded from that reduced rate and usually remain at 19 percent, according to the German Federal Ministry of Finance guidance, dated 22 December 2025 and the current German VAT Act, Section 12.

That difference distorts the result as soon as I have mixed sales. If I casually combine gross food sales and gross beverage sales, but compare them with net purchasing costs, I bend the percentage before I even start interpreting it. A small calculation makes the point: 10.70 euros gross at 7 percent equals 10.00 euros net, and 11.90 euros gross at 19 percent also equals 10.00 euros net. Gross, those sales look different; net, they are the same. So before I discuss performance with my team, I check what basis the report is using. A food cost percentage should reflect operating reality, not hide a setup mistake in tax and pricing logic.

One practical example from my own restaurant setup

Take a fictional but realistic example from my business: a small trattoria with lunch trade, evening service, and a terrace that becomes busy on warm weekends. In June I make 38,000 euros net from food and 14,000 euros net from drinks, so 52,000 euros net in total. Opening stock is 6,500 euros, purchases during the month are 15,200 euros, and closing stock is 7,100 euros. That gives me a cost of goods used of 14,600 euros. My overall food cost percentage is therefore 28.1 percent. That headline figure is useful, because it tells me how much of my net sales was consumed by goods in that month.

Then I split that same month into operating areas, because the total alone does not tell me what to change. Suppose 10,900 euros of the 14,600 belong to the kitchen and 3,700 euros to beverages. Then my food percentage is 28.7 percent and my drinks percentage is 26.4 percent. If the drinks side suddenly comes in higher than usual, I do not start by blaming supplier prices. I look at pouring discipline, complimentary servings, recipe consistency, and spoilage. In a hot week, for example, too much prepared lemonade may have been discarded. That separation turns one bare percentage into a usable management decision instead of a vague feeling.

Why the calculation is often wrong even when the formula is right

The most common mistakes are not percentage errors but input errors. Many restaurants compare purchases with sales and call it food cost, without adjusting for opening and closing stock. That makes a heavy buying week look like a weak performance period even if much of the stock is still sitting on the shelf. Others mix time periods: June sales, a stock count from mid-July, and supplier invoices that are not fully posted yet. Waste, staff meals, tasting portions for an event, or spoiled produce often disappear into one generic line. Then the percentage looks alarming even though the real problem is poor documentation rather than runaway usage.

Another trap is being too broad with mixed products. A house lemonade is not only syrup and water; it may also include garnish, ice, pouring loss, and disposable material in takeaway trade. A pasta dish is not just the bag of pasta if tomato sauce, parmesan, oil, and a bread side are routinely part of the plate. I do not ask my team to work with vague product groups when I actually need decisions about best-selling dishes. The goods logic has to match the sales logic. Otherwise I end up punishing the wrong item, the wrong shift, or the wrong department for a number that was built on rough assumptions.

How I organize the process so it stays fair and repeatable

To keep food cost percentage from becoming the number of the month based on gut feeling, I define a fixed routine. First, I set the period, for example a calendar week or a month. Second, I define which storage areas belong to it: main storeroom, walk-in fridge, bar stock, wine shelf, dry storage, and, if relevant, an outside station. Third, one responsible person counts with clear units such as kilograms, liters, bottles, pieces, or cases. Fourth, unclear differences are checked immediately before memories fade. An opened bucket of feta is not estimated like a full crate of tomatoes; it is converted into a traceable quantity so the next count remains comparable.

The process stays fair when I do not use the percentage as a weapon against individual employees. If a new starter dish produces too many leftovers, that is first an organizational issue: portion size, mise en place, sales forecast, or recipe design may not fit together yet. So I discuss the process before I hunt for a person to blame. In concrete terms, the team needs clear ownership. Whoever counts documents transparently, whoever buys maintains pack sizes and prices, and whoever owns recipes updates components after changes. That way the number becomes reliable without turning into pressure on service, kitchen, or bar staff who may only see one part of the picture.

Where Bonzumo helps me build a cleaner data basis

For the calculation itself, what I need most is reliable master data and counted stock. That is where Bonzumo can help in a practical way. In inventory management, I can assign ingredients and quantities to products, maintain base recipes with yield and waste, and record and evaluate counted quantities through stocktaking. If I define a tomato sauce as a base recipe, I do not have to mentally re-estimate it every time I review a pasta dish; it becomes a structured component used across several items. That improves recipe cost visibility and gives me a better basis to judge whether an unusual percentage comes from purchasing, from the recipe, or from stock handling. Understand what goes into every dish on your menu.

What matters is being precise about what the system does and what my operation still has to do. Bonzumo supports structured recipe maintenance, goods information, stock movements, and stocktaking, but it does not magically detect perfect theoretical-versus-actual consumption if I have not maintained clean data. My team still has to keep units consistent, update recipe quantities after menu changes, and count stock properly. The practical benefit is substantial anyway: I can find the same item in sales, in the recipe structure, and in inventory instead of reconciling three disconnected lists. Especially when the menu changes with the season, that saves me less mathematical effort than avoidable coordination mistakes in daily work.

What decisions I actually take from the percentage

A food cost percentage is never the end of the conversation for me; it is the start of the right question. If the percentage rises overall, I first check category, period, and likely cause: purchasing prices, portioning, spoilage, shrinkage, promotional business, or a changed beverage mix. With a popular lunch dish, for example, I may discover that the supplier did not become more expensive at all; the pasta portions have simply been ladled too generously for weeks. Then I do not jump straight to raising the menu price. I first test portioning tools, plating standards, and recipe instructions. Price changes are only one possible response, and often not the best one.

I also connect the percentage with what was actually sold and closed that day. When order, payment, and end-of-day activity are traceable in one shared data context, questions can be checked where they arose instead of from memory alone. Bonzumo’s linked transaction flow helps with that because sales, payments, receipts, timestamps, and closing all refer back to the same process, which makes later clarification easier. That is especially useful when I review a busy day before discussing anomalies with the team. Understand the day's activity before you close up. The management task still remains mine: turn one percentage into a fair, concrete action instead of staring nervously at a rising number.