How I factor waste and spoilage into menu costing

Waste and spoilage both belong in costing, but not in the same line

I account for both, but I do not treat them as the same thing. Unavoidable waste such as peels, bones, trim, evaporation, cooking loss or reduction goes straight into the recipe cost, because it happens even when my team works well. Avoidable spoilage or reject loss, by contrast, sits on top as an operating loss that I spread carefully across the portions I actually sell. That distinction is the practical answer. If I throw everything into one vague “shrinkage” bucket, my food cost stops being useful. Then nobody in the team knows whether we need to correct the recipe, tighten production, change prep timing or simply buy less. A peeled onion and a tray of overheld roasted vegetables both cost money, but they point to very different management decisions.

A simple restaurant example makes this clear. Suppose I buy 10 kilograms of carrots and, after washing, peeling and sorting, only 8.5 kilograms are fit for production. That 15 percent loss belongs in the recipe basis, because it is normal yield loss. If, on a busy Saturday, two hotel pans of prepped roasted carrots then sit too long, dry out and have to be binned, that is not recipe waste anymore. That is spoilage caused by batch size, timing or communication. In my operation I want the costing to show both truths separately: what the ingredient naturally yields, and what the kitchen or planning process is unnecessarily losing. Only then can I protect margin without unfairly blaming staff for losses that are simply part of cooking.

The key number is not purchase quantity, but usable quantity

For costing, the relevant price is not the purchase price per kilo in the box; it is the price per kilo of usable product in the state my kitchen actually cooks with. My basic formula is purchase price divided by yield. If I buy 1 kilogram of onions for 2.40 and, after peeling, only 0.84 kilograms remain usable, then my effective onion cost is about 2.86 per kilogram of processed onion. That is the number I use for soup, sauce or burger garnish. If I keep costing with the raw purchase price, every dish looks slightly cheaper than it really is, and the error repeats across the whole menu. This matters most with products that vary heavily, such as fish, butchered meat cuts, herbs, fruit, leafy greens and house-made stock bases.

I do not guess that yield from memory if the ingredient matters. I measure it cleanly once, then recheck it later when supplier quality or staff routines change. Imagine 5 kilograms of raw chicken legs that produce only 3.6 kilograms of boned, trimmed meat. That is a 72 percent yield. If I cost that item at 85 percent yield because it “felt about right,” every portion is underpriced even if the recipe sheet looks tidy. So I note down the raw weight, usable weight, supplier and anything unusual, such as especially small pieces or heavy bone content. In Bonzumo I can maintain ingredients, quantities and base recipes in a structured way, which is exactly why I use Understand what goes into every dish on your menu as the operational backbone for recipe-based decisions.

Spoilage needs its own surcharge instead of wishful thinking

Not every loss can be attached neatly to one plated dish, so I give recurring spoilage its own small, explicit surcharge at dish or product-group level. This is especially relevant for lunch specials, buffets, breakfast prep, cakes, side dishes and anything with a short holding window. A practical example: on weekdays I produce 40 portions of a lunch dish, but I reliably sell only 37. Three portions disappear again and again through overproduction, quality decline, plating errors or end-of-service leftovers. In that case I cannot pretend the dish only “cost” 37 portions of ingredients. In reality 40 portions tied up stock, labor flow and cold storage space. If I divide ingredient cost only by the ideal output and ignore the repeated loss, my menu price is built on hope rather than on my actual trading pattern.

My rule is to calculate in two steps. First I establish the clean recipe cost using real yield and real usable quantities. Second I add only the recurring spoilage that my operation genuinely experiences. If one tray of lasagna contains material cost for 12 portions but I usually monetize only 11 portions before one portion is left unsold or no longer reaches my quality standard, then the commercial cost of the sold portion is based on 11, not 12. That is not pessimism; it is honest costing. The important trap to avoid is double counting. If cooking loss, trimming loss and reduction are already reflected inside the base recipe, they must not reappear as a flat spoilage surcharge. Otherwise I inflate the dish cost artificially and make the wrong call on price, portioning or prep volume.

A braised beef dish shows how the arithmetic works in real service

Take a braised beef main with root vegetables and mashed potatoes. I may buy 8 kilograms of beef shoulder, but after trimming and cooking loss I might have only 5.6 kilograms of usable plated meat. I also cost the carrots, celery and onions on their cleaned weight, not their incoming crate weight. The sauce reduces heavily during cooking; that is not a mistake or spoilage, but part of production, so it belongs inside the base recipe. If the full batch yields 28 saleable portions, then all batch ingredient costs must be spread across those 28 portions, not across the original raw meat weight and not across a fantasy yield I would only hit in a perfect world. Batch costing protects me from flattering numbers, especially with slow-cooked dishes where moisture loss and reduction are significant parts of the process.

Then I look at the second level, which many kitchens skip. Out of those 28 prepared portions, perhaps I sell only 26 fully on average over a month. One portion may occasionally leave the pass as a replacement after a guest complaint, and another may be withdrawn because the last serving no longer meets my quality standard at the end of service. If that pattern is repeatable, my commercial costing must ask how many portions I actually convert into revenue, not just how many I can theoretically portion. For braises, soups, desserts from trays and sauce batches, I therefore prefer batch costing over a purely theoretical per-portion view. It reflects yield, reduction and real end-of-service leftovers much better. That is where silent margin loss often hides in otherwise disciplined kitchens.

I record losses where they happen and always with a reason

Costing only becomes useful in daily operations if losses are recorded simply and consistently. I do not want products to vanish into the bin with no explanation. I ask the team to assign a reason, using a short list that is easy to apply: prep trim, spoilage before production, failed production, overproduction, returned item from guest service, breakage or quality withdrawal. This does not need ten approvals or a painful form. A brief record with item, quantity, unit, date and reason is enough to reveal patterns. On expensive items, that one extra detail tells me whether the real problem sits in purchasing, storage, prep, service timing or final production. Without causes, a spoilage percentage may sound alarming, but it does not yet tell me what to change on Monday morning.

I also organize this fairly. I do not expect every server to explain full-cost accounting, but I do make sure everyone knows what they must flag and to whom. The kitchen records failed prep and production loss, the shift lead reviews discarded mise en place or returned dishes, and I review the pattern regularly rather than only when month-end numbers look ugly. If mashed potatoes are left over every third Thursday, that is not bad luck; it is a planning issue. If dessert glasses start breaking more often with a newly onboarded weekend team, that points more toward training and workstation setup than toward purchasing. A single generic “waste” line hides that difference. A reason code, even a simple one, turns loss from blame material into a management tool.

Good costing still fails if production and demand are out of sync

Waste and spoilage rarely fall just because I improve the spreadsheet. Most of the time I also have to align kitchen timing, service information and prep logic. Imagine the kitchen preps ten fish portions at 18:00 because it feels safer, while reservations and early tables already suggest many guests will choose vegetarian dishes that evening. If later several fish portions have to be discarded, the issue is not mainly the purchase price of fish. It is the mismatch between production timing and expected demand. In that case I do not reach first for a price increase. I change the production rule: maybe six portions are prepared first, with the remaining four held back until the first order pattern is visible. The financial answer depends on the operational answer.

That coordination works best when service, kitchen and bar can work from the same order context instead of from shouted updates and memory. That is why I value a setup where Give service, kitchen and bar a shared view of orders helps the team react earlier to what is actually selling. In practice I review every suspicious loss with three questions in the same order. First, is the recipe technically correct, with real yield and realistic quantities? Second, does the production volume match our actual sales pattern? Third, is the loss driven by mistakes, rush or unclear communication? That sequence stops me from solving every margin problem with a price rise. Wilted herbs may require a different order rhythm or storage routine, while repeated burger remakes may require clearer specs and calmer handover at the pass.

The final pricing decision comes only after the losses are separated

When I set or review a selling price, I first total the corrected recipe cost based on usable quantities. Then I add a spoilage surcharge only where the loss is proven, recurring and not already captured in recipe yield. Only after that do I test whether my target food cost still works. If it does not, I have three honest levers: adjust the menu price, change the portion or garnish, or reduce the underlying loss operationally. For example, if my house tiramisu ends up effectively 12 percent more expensive than the raw recipe suggests because of breakage, edge trim and recurring unsold leftovers, I cannot keep the old price and pretend a better week will fix it. I need to choose a lever deliberately instead of letting the margin erode silently.

The right answer is not always a price increase. Sometimes a better cut plan or a more precise mold size solves the issue because portions become cleaner and edge waste falls. Sometimes a base recipe needs redesign because a sauce reduces too far or a vegetable cut throws away too much edible product. Sometimes the only honest conclusion is that a delicate but popular dish simply has to sell at a higher price to remain viable. That is how I factor waste and spoilage into costing in a way that is fair to guests and fair to the team: unavoidable yield loss belongs in the recipe, avoidable recurring loss belongs in a controlled surcharge, and the final price comes only after both are separated and understood. That gives me numbers I can actually run a restaurant on.