"We don't waste much" is a feeling, not a fact
Ask any restaurant owner how much they waste, and the answer is almost always "not much" — said with confidence, without ever actually adding it up in euros. It's not bad faith: kitchen waste is spread across dozens of small events a day (a wilted vegetable, a remade dish, a sauce base thrown out), and none of these events, on its own, feels big enough to bother logging. The problem is that added together, those small events become a number almost no restaurant owner actually knows.
According to Eurostat 2025 data, restaurants and food service are responsible for 11% of total food waste in Italy (14 kg per capita), against 53% from households (69 kg per capita) — a smaller share than common perception suggests, but still a real, largely avoidable cost, because unlike household waste it's concentrated in a commercial business with already thin margins.
Why "measuring" is different from "estimating"
Measured waste has three elements: what was thrown out, how much (in a precise unit), and why. Waste estimated "from memory" at the end of the week has, in practice, only the first element, and often not even that precisely — you remember the most dramatic episodes (a whole case gone bad) and forget the thousand small daily wastes that, added up, weigh more.
The practical difference: a well-kept waste log tells you not just how much you're losing, but where — which product, which reason, which day of the week — exactly the information needed to act. An eyeballed estimate only gives you a vague sense of "waste is high" or "waste is low," with no indication of what to change.
How to estimate the cost of a waste event
The cost of a waste event is almost never a certain figure — it's an estimate, quantity times price:
Estimated waste cost = Quantity discarded × Unit price of the product
The unit price, when not entered manually, can be pulled from a cascade: first the last recorded purchase price for that product, then the current list price, and if the product isn't in the catalog but is an ingredient in a recipe, the unit cost used in that recipe. The important part is that cost never stays at zero: a waste event "with no price" hides the problem instead of measuring it.
Waste categories (and why they matter)
Not every waste event has the same cause, and lumping them all together as "waste" hides useful patterns:
- Expired: the product passed its use-by date before being used. Signals a stock rotation problem or a par level set too high.
- Overproduction: prepared more than what was sold. Signals a wrong demand forecast, often tied to a specific event (a quieter weekend than expected, weather).
- Damaged: broken, dropped, contaminated during prep. Often signals a training or kitchen procedure issue.
- Returned: sent back by the customer or the dining room. Signals a quality issue, an order communication issue, or a mismatch with expectations.
- Other: everything else — useful for not forcing something into the wrong category, but worth watching if it becomes the biggest bucket (a sign the main categories aren't capturing the real cause).
A log that distinguishes these categories tells you whether the problem is upstream (purchasing/forecasting) or downstream (prep/service) — two completely different fixes.
An example of one logged week
Imagine a week where the kitchen logs every waste event as it happens, instead of ignoring it:
| Day | Product | Quantity | Reason | Estimated cost |
|---|---|---|---|---|
| Monday | Mixed salad | 2 kg | Expired | €6 |
| Tuesday | Sea bass fillet | 1.2 kg | Returned | €22 |
| Wednesday | Pizza dough | 3 kg | Overproduction | €9 |
| Thursday | Fresh cream | 1 L | Damaged | €4 |
| Friday | Mixed vegetables | 4 kg | Expired | €12 |
| Saturday | Ground meat | 2 kg | Overproduction | €24 |
| Sunday | Bread | 3 kg | Overproduction | €9 |
Weekly total: €86. On a hypothetical weekly food revenue of €8,500, that's about 1% — not huge as a percentage, but a real, traceable, and above all actionable number: two entries out of seven are "overproduction," and it's the category that weighs the most (€42 out of €86, nearly half). Without the log, this information simply wouldn't exist.
Where waste hides the most (5 things to check)
1. Prep done "by feel" instead of on a demand forecast. Kneading, marinating, portioning ahead of time without a reference for how much you'll actually sell is the most common cause of overproduction.
2. Trim loss not planned into the recipe. If the recipe sheet doesn't account for normal cleaning waste (peels, bones, unusable parts), every dish prepared generates an "invisible" waste that never gets logged as such.
3. Stock rotation not respected. First in, first out (FIFO). If a new delivery gets placed in front of the old stock instead of behind it, the old stock expires before being used — even if "in theory there was time."
4. Menu too wide relative to actual volume. More menu items means more different ingredients held in stock, each with slower turnover and therefore more risk of expiring before use.
5. No threshold that triggers a check. Without a reference (how much waste is normal, how much is excessive), every week looks "normal" until someone looks at the numbers and realizes it isn't.
How BiteBase measures waste
Every waste event logged in BiteBase carries a quantity, a reason from the categories above, and an estimated cost calculated from the price cascade (last purchase price, current price, or the ingredient's recipe cost) — never left at zero, because a waste event with no price is a hidden problem, not a solved one.
When waste logged in a single day exceeds the configured threshold (€50 by default, adjustable), an alert notifies the team, with a higher severity level past twice the threshold. Beyond waste that's already happened, BiteBase also estimates waste on its way: looking at stock expiry dates and recent average consumption, it flags products at risk of expiring before use — before it happens, not after.
Frequently asked questions
Is it worth logging small waste too, like a bunch of parsley? Yes, especially early on: it's the small, repeated waste events that reveal the pattern (same product, same reason, same week of the month) that a single isolated event doesn't show.
Does logged waste automatically reduce stock? No: logging a waste event creates a tracked cost, but stock still needs to be decremented separately if it hasn't already been reduced by another operation. The two pieces of data — waste cost and stock quantity — live in two different places on purpose, because they answer different questions.
What's a "normal" waste threshold relative to food revenue? There's no universal number valid for every type of venue — it depends on the menu, the volume, the cuisine type. The useful data point isn't comparing yourself to a generic average, it's watching your own trend over time: if waste grows month over month with no explanation, that's the signal, regardless of the absolute percentage.