Spoilage
Product that didn't get used before its date. Flags over-ordering, incorrect par levels, or storage and rotation problems.
Two taps to log a waste event — spoilage, prep error, comp, or staff meal. Each one costs itself at the current price and comes off your live count. Weekly patterns tell you where the money went and what to change.
The waste log is built for kitchen speed. Pick the ingredient, pick the reason, confirm the quantity. Timestamp, cost, and stock deduction all happen in the background. Nothing to fill in at the end of shift.
Logs in two taps from the pass tablet
Grouping waste into a single figure tells you nothing useful. Reason codes separate the fixable from the expected — so the right conversation happens in the right place.
Product that didn't get used before its date. Flags over-ordering, incorrect par levels, or storage and rotation problems.
Waste from the preparation process — bad cuts, over-portioning, broken-down product. Maps back to recipe yields and training gaps.
Product sent out as a manager's compliment or replacement dish. Ties to service decisions rather than kitchen performance.
Food used for team meals. Tracked separately so it shows up as an intentional cost, not unexplained variance.
Most venues are binning 3–5% of their food cost without knowing the reason.
That's not a kitchen problem or a supplier problem — it's a visibility problem. When waste is logged with a reason, patterns become obvious. The fix is almost always simpler than the loss.
See how it connects to stockEvery waste event deducts from live counts in real time. No separate adjustment at end of shift.
Read more →Prep error waste maps back to recipe yields, showing where theoretical and actual portions diverge.
Read more →Weekly waste reports, par adjustment signals, and shift breakdowns in your back-of-house dashboard.
Read more →Book a 30-minute walkthrough. We'll show you what waste tracking looks like in a live kitchen — from the log tap on the pass to the weekly report in the dashboard.