How I Reduce Food Waste in My Restaurant

I reduce waste by making the biggest reasons visible first

I reduce food waste by separating the cause before I try to fix it. In practice, most waste in a restaurant comes from one of three places: I bought too much, I prepped too much, or I produced at the wrong moment. Once I know which of those is happening, the next decision becomes much clearer. In a sample operation with a lunch menu and an evening service, that often means leftover side dishes after lunch, over-prepared components by night, or a few dishes that simply sell far less often than expected. For one week, I look not only at food cost, but at exactly where food gets thrown away by product group.

I do not tell my team to “be more careful” and leave it at that. I set up a simple recording habit instead: unopened goods with date, opened goods with a reason, production leftovers with the station noted, and plate waste kept separate from both. That matters because leftover tomato sauce needs a different solution from ten unsold salmon portions. If I dump everything into one vague shrinkage category, I am deciding blind. I also organise this fairly: the last shift does not automatically get blamed. Quite often, the real cause started two days earlier in purchasing, menu design, or a prep decision that looked generous at the time but was already too large.

The menu is usually the biggest lever, not the storeroom

Many restaurants waste food because the menu promises more variation than the operation can keep fresh in an economical way. So I start by reducing waste through shared ingredients and clear sales priorities. If three starters each require a separate specialist ingredient that barely appears anywhere else, the risk of spoilage rises almost automatically. A stronger setup is a menu where fennel, yoghurt, herb oil or a base stock appear in several dishes in a sensible, high-quality way. That does not mean a boring menu. It means controlled overlap. Less scatter in purchasing usually means less spoilage in cold storage, especially with delicate ingredients that do not survive wishful forecasting.

I test every dish with two questions: how often does it really sell, and which ingredients sit around only because of that one dish? With recipes and base recipes maintained in Bonzumo, I can structure ingredients, quantities, yield and waste for each product. That lets me see more than a selling price. I can judge whether a dish is unnecessarily risky because of its components. That is exactly how I use Understand what goes into every dish on your menu: not as magic, but as a structured basis for decisions. I am not relying on gut feeling alone; I am working with maintained quantities, recipe costs and repeatable building blocks my team can actually prepare and sell.

Purchasing and prep have to follow real days, not ideal quantities

The next lever is my ordering rhythm. Many businesses do not buy too much overall; they buy too much for the wrong days. I separate weekend trade, quiet weekdays, reservation levels and weather-sensitive peaks. A simple example: for Friday evening I may accept a bigger buffer than for Tuesday lunch if the goods are highly perishable. I would also rather order smaller amounts twice than place one “comfort order” that feels safer on paper, provided the supplier is reliable. That creates a bit more planning work, but it often saves more value in avoided spoilage than a large delivery ever saves in convenience. My aim is not a full store room, but stock that still has a realistic path onto plates.

Bonzumo helps here through preparation, not through automatic guesswork. I can maintain suppliers, purchase orders, item data and counted stock in one connected process. Inventory, in this context, is the recording and checking of counted quantities; it is not a proven automatic actual-versus-expected consumption engine. That limitation is useful because it keeps my decisions honest. If a stock count shows two crates of herbs that no longer fit into the next days’ menu plan, I adjust the order and the day’s specials immediately instead of pretending the problem will solve itself. Used properly, purchasing becomes deliberate control rather than repetition of old quantities, and that alone usually cuts preventable waste.

In the kitchen, waste often comes from the wrong production timing

Not every thrown-away ingredient was badly purchased; often it was simply produced too early. With short-life components in particular, sequence matters. I do not have the kitchen prepare everything at the start of the shift just because the room is quiet. Instead, I separate stable base preparations, half-finished components and final fragile elements. For example, the base of a sauce may be ready in advance, while fresh herbs or a crisp garnish should only be finished close to service. That keeps quality high and overproduction lower at the same time. It also avoids the common late-evening trap where the team pushes out too much just to feel ahead, then throws away what should never have been finished yet.

For that workflow, service, kitchen and bar need the same view of the order status. With configured production stations and the kitchen monitor in Bonzumo, my team can follow open and processed orders in their own station context, and menu courses can be released separately. I use that to avoid producing an entire table’s meal just in case the next course might be needed soon. Give service, kitchen and bar a shared view of orders means something very practical to me: less blind pre-production, clearer station priorities, and fewer plates that lose quality because they were fired too early and then need replacing. Waste is often a timing problem wearing a purchasing mask.

Portion size, side-dish logic and plate returns need their own review

Food waste does not end in the store room. If full side dishes or half portions come back again and again, that is not a guest problem; it is feedback to me. So I review plate waste separately from production waste. If a schnitzel dish regularly returns with most of the salad untouched, purchasing may not be the issue at all; the composition may be wrong. A better answer can be a guest choice of side dish or a smaller lunch portion at a fair price. That way I am not saving money by shrinking quality. I am matching quantity more precisely to the occasion. This matters especially at business lunch and in evening menus where guests may still want dessert but not a heavy standard portion beforehand.

I organise this fairly by not making the service team responsible for every returned item. Instead, I ask for short, concrete notes such as “potato side too large” or “dessert after menu rarely finished.” From that, I change scoop sizes, plating aids or side-dish options. The main pitfall is false thrift: if I just cut portions aggressively, I annoy guests and shift the problem into extra orders, complaints or poor value perception. The better route is a coherent standard portion, plus a clear option for small, regular or extra where demand really varies. Waste reduction works when the guest still feels well served, not when the plate simply looks meaner.

Hygiene and safe handling remain the limit for any reuse

Not everything left over may, or should, be used again. In Germany, as a food business operator, I must organise safe food and hygienic processes under Regulation (EC) No 852/2004. HACCP-based procedures include hazard analysis, monitoring, corrective action, verification and suitable documentation, as the German Federal Institute for Risk Assessment explains in its HACCP guidance. For my operation, that means leftover use is only sensible if storage, cold chain, processing steps and responsibility are clearly defined. A stock list alone does not prove food safety, and no cost-saving idea is worth blurring that boundary.

So I set explicit house rules: anything that can safely and sensibly be reused gets a defined route; anything doubtful is discarded and documented. A typical mistake would be passing cooked components between shifts without clear labelling and relying on memory. I also keep training duties distinct. For highly perishable foods, appropriate expertise under section 4 of the German Food Hygiene Ordinance is relevant, while instruction under section 43 of the German Infection Protection Act is a different obligation. Reducing waste must never mean stretching safety rules. My line is simple: better to lose one tray than to risk unsafe reuse that endangers guests and damages the whole business.

Lasting results come from a fixed weekly rhythm, not one-off action

In the end, lower waste only lasts if it becomes part of my routine. I run a short weekly cycle: first I review counted stock, then I look at the week’s waste reasons, then I adjust the menu, prep volumes and purchasing for the coming days. Not every number needs a giant report. Even the simple insight that bread is left over on Mondays, fish components on Wednesdays and dessert mise en place on Sundays will change decisions quickly. What matters is that I spot patterns instead of overreacting to one outlier. One rainy terrace day proves very little; the same waste pattern over four weeks tells me the system, not the weather, needs adjusting.

Fair organisation matters here as well. I link figures to responsibilities, but not to blame. The kitchen contributes on prep levels and yield, service reports guest leftovers, the office adapts delivery quantities, and I make the underlying decisions about the menu and safety buffers. When I close that loop every week, food waste usually falls noticeably without turning the team into anxious penny-pinchers. The goal is not an empty fridge at any price. The goal is a business that balances freshness, reliability and margin cleanly enough that valuable food reaches guests instead of the bin. That is how I reduce waste in a way my team can maintain, not just admire for a week.