Every kitchen throws food away. Milk goes past its date, pastries get over-baked, a dish comes back. Each one is small. Added up over a month, it can be a real number, and most restaurants never see it, because it disappears into food cost with everything else.
Tracking waste turns that invisible number into one you can manage. This guide covers what to log, how to put a cost on it, and what to do with the patterns once you have them.
Why waste is worth tracking
When you only look at food cost as a whole, you can see that it went up, but not why. Was it a price increase, over-portioning, theft or waste? A waste log answers one of those questions directly. It also changes behavior. When staff know that thrown-out food gets written down, they tend to rotate stock, prep closer to what's needed and speak up when something keeps expiring.
What to log
Keep the log simple enough that someone on a busy line will actually use it. Each entry needs four things:
- Item: what was thrown out. Use the same names as your inventory so the cost lines up.
- Quantity and unit: 2 liters, 12 portions, 1 case. Use the unit you buy or count in.
- Reason: pick from a short fixed list, so you can group entries later.
- Who and when: the person and the shift.
A reason list that works for most restaurants:
- Spoilage: past date, gone off, freezer burn.
- Overproduction: prepped or cooked more than sold.
- Prep and cooking mistakes: burnt, dropped, wrong recipe.
- Returns and comps: sent back or given away.
- Over-pours and spillage: mostly at the bar and coffee station.
Five or six reasons is enough. With twenty, people pick at random and the data stops meaning anything.
Put a cost on every entry
A log that says "2 liters of oat milk" is useful. A log that says "$8 of oat milk" is persuasive. To cost an entry:
Waste cost = quantity wasted × unit cost
Use the unit cost you actually pay, from your latest invoice, in the same unit you logged. If you buy oat milk by the case of 12 liters and log waste in liters, divide the case price by 12.
For a prepared item, such as a portion of soup or a baked tray, use the recipe cost: the cost of the ingredients that went into it.
A worked example
Example: a café's waste log for one week, with made-up round numbers.
| Item | Quantity | Unit cost | Reason | Cost |
|---|---|---|---|---|
| Oat milk | 6 liters | $2.00 / liter | Spoilage | $12.00 |
| Croissants | 20 | $1.00 each | Overproduction | $20.00 |
| Whole milk | 4 liters | $1.50 / liter | Spillage | $6.00 |
| Chicken sandwich | 3 | $3.00 each | Returns | $9.00 |
| Salad mix | 2 kg | $6.00 / kg | Spoilage | $12.00 |
| Total | $59.00 |
Example: $59 a week is $236 over four weeks, from one small café. Two lines stand out: croissants (overproduction) and dairy and greens (spoilage). Those are two different problems with two different fixes.
Turn the log into fixes
Look at the log once a week, sorted two ways: by cost and by reason. The biggest lines tell you where to start.
Spoilage usually means ordering or rotation.
- Order closer to what you use. If the same item expires every week, the par level or order size is too high.
- Put new deliveries behind old stock, and date-label everything when it's opened.
- Check that the fridge is holding temperature.
Overproduction usually means prep isn't matched to sales.
- Prep from what you expect to sell that day of the week, not a fixed number.
- Bake or cook in smaller batches through the day for items that sell unevenly.
- Track what's left at close for a couple of weeks before changing the number.
Mistakes and returns usually mean training or recipes.
- If one dish comes back often, taste it and check the recipe card and portion.
- If waste clusters on one shift, find out what's different about that shift.
Over-pours and spillage usually mean tools: measured pours, jiggers and the right size of milk jug.
Example: in the week above, the café cuts its croissant bake from 60 to 45 on quiet weekdays and orders oat milk twice a week instead of once. The next week's log shows croissant waste of 5, not 20, and no expired oat milk.
Waste and inventory
Anything you throw out has left your inventory. If it isn't logged, your on-hand count is wrong until the next full count, and orders based on that count will be wrong too. Logging waste against inventory keeps the count closer to what's really on the shelf between counts.
Make it easy to log
The best waste log is the one people use. Put it where the waste happens: a phone at the station, not a clipboard in the office. Make it a step on the closing checklist to log anything thrown out at close. And never make logging feel like a punishment. A cook who logs a dropped tray is doing exactly what you asked.
How Ospelia does it
Ospelia's Waste log takes seconds per entry: pick the item, enter the quantity, choose a reason (spoilage, spillage, comp, over-pour) and it's logged against the person and the shift. Each entry is priced at the item's real unit cost, and the running total shows what waste has cost this month, with the most-wasted items and the reasons behind them per location.
Every entry takes the quantity off the on-hand count in Inventory, so the next order is worked out from what's really on the shelf. Recipes & plate cost cost every recipe from the unit prices you actually pay. Waste is costed so you can see it; your food cost in the P&L is set by your food-cost target and recipes.
