Kitchen waste is food you paid for and did not sell. If it is not logged, it does not disappear. It hides inside actual food cost as a variance nobody can name. Tracking it is a count, a reason, and a cost, not a speech about sustainability.
Separate the reasons
A single “waste” bucket cannot be coached. Use reasons a station will actually pick:
- –
Spoilage and expiry. Product that died in storage. This is purchasing, par levels, or rotation.
- –
Prep trim and butchery loss above the yield already in the recipe. If the recipe already assumes 20% trim, do not log that 20% again or you will double count.
- –
Over-production. Batches made and not sold. This is forecasting and prep lists.
- –
Dropped, burnt, or remade items. This is the line.
- –
Plate waste, if you measure it. It is a menu and portion signal, and it is the easiest to ignore because it happens after the sale. It does not explain a COGS variance the same way, because the sale already happened, but it explains a guest and a portion.
- –
Staff meals and unrecorded comps, if they are not already a sale at zero. Otherwise they look like theft or spoilage.
Value it at cost
Log quantity in the same unit as inventory, and value it at the current ingredient cost, not at menu price. Menu price makes waste look enormous and does not match the food cost formula. A kilo of rice thrown out is the invoice price of that kilo. The food waste cost calculator turns a day’s weight and a cost per kilo into the month, the year, and the group; the food waste statistics page has the published figures on what food service throws away, with sources.
Then compare the week’s waste cost with the variance between actual COGS and theoretical cost. They will not match to the halala. They should be in the same conversation. If variance is SAR 4,000 and logged waste is SAR 400, the rest is portioning, missing invoices, counts, or waste nobody wrote down. That relationship is theoretical versus actual food cost.
Make the log shorter than the excuse
If logging takes a meeting, it will happen on Monday for the previous week and it will be fiction. The entry a cook will make mid-service is: item, quantity, reason, station. AKLI’s waste module is that entry, costed against inventory, with a trend by day and by branch. It is described under waste tracking.
What not to claim from a month of logs
A new log creates a baseline. It does not, in the first week, prove a percentage reduction. Publish the categories and the cost. Decide which reason is largest. Change one par, one yield, or one prep list. Measure the next period against the same rules. AKLI will show the figures; it will not invent a case study for you.
Questions operators ask
How should kitchen waste be valued?
Log quantity in the same unit as inventory, and value it at the current ingredient cost, not at menu price. A kilo of rice thrown out is the invoice price of that kilo.
Will logged waste equal food-cost variance?
No. They will not match to the halala. They should be in the same conversation. If variance is SAR 4,000 and logged waste is SAR 400, the rest is portioning, missing invoices, counts, or waste nobody wrote down.
What does a new waste log prove in the first week?
A new log creates a baseline. It does not, in the first week, prove a percentage reduction. Publish the categories and the cost, change one par, one yield, or one prep list, and measure the next period against the same rules.