Cancellations and removed items
What this is for
Two separate audit reports covering the two ways food or an order can disappear:
- Cancelled orders — a whole order stopped.
- Removed KOT items — one dish taken off a bill after the kitchen ticket had already gone.
The second is the one to read carefully. It's the classic route by which a restaurant loses money without anything looking obviously wrong.
Cancelled orders
An audit report showing cancellation reasons and who cancelled.
| Figure | What it is |
|---|---|
| Total Cancelled Orders | How many. |
| Total Cancelled Amount | What they were worth. |
| Top Cancelled Reasons | The pattern. |
Per order: Order Number, Order Date, Cancelled Date, Customer, Table/Waiter, Cancellation Reason, Cancelled By, Order Total.
Filter by cancellation reason, by user, and by date.
Reading it
The gap between order date and cancelled date is the useful column, and it's easy to miss.
- Cancelled within a minute — a mis-tap. Harmless.
- Cancelled after an hour — something went wrong in service.
- Cancelled the next day — someone tidying up, and worth asking what they were tidying.
Top reasons tell you where to look. A dominant "kitchen error" is a kitchen conversation; a dominant "customer changed mind" may mean waits are too long.
Removed KOT items
Items cancelled off a ticket after the kitchen had them.
| Figure | What it is |
|---|---|
| Total Removed Items | How many. |
| Total Removed Amount | Their value. |
| Top Cancellation Reasons | Why. |
| Top Waiters | Who. |
Per item: Order Number, KOT Number, Item Name, Quantity, Total Price, Removed By, Removed Date, and the reason.
Why this one matters
An item removed after the kitchen ticket went means the food was made and then taken off the bill. You paid for the ingredients and the labour, and no money came in.
Some of that is legitimate and unavoidable — a wrong item, a dish sent back, a guest who changed their mind. Some of it isn't. This report is how you tell the difference, and it exists precisely because that difference is otherwise invisible.
What to look for
- Concentration on one person. The Top Waiters figure is right there. One person removing substantially more than colleagues on the same section is worth understanding — usually training or a habit, occasionally not.
- Concentration on one dish. That's a kitchen or menu problem, not a staff one.
- A rising total. The absolute number matters less than the trend.
- Thin reasons. Removals with vague reasons are the least useful and the most worth asking about.
- High-value items. A removed steak is not the same event as a removed side of bread.
Handling it well
Approach it as a process question first. Most removals have honest explanations, and treating the report as an accusation is how you stop people recording them accurately — which loses you the report entirely.
But do read it. Monthly, at management level, alongside refunds.
The control that goes with it
Delete Item After KOT is a permission. Decide deliberately who has it.
A reasonable arrangement: anyone can cancel an item before the ticket goes; only a manager can remove one after. That's the moment the cost is incurred, and it's a sensible place to put an authorisation step. See What each role can do.
Make sure your cancellation reasons are a real list. A reason set of "Other" produces a report with no information in it.
Good to know
- Both are per branch and follow your operating shifts.
- Cancelled orders and removed items are different events. An order cancelled before any ticket went cost you nothing but a table.
- Cancelling can't be undone, which is why the reason is required at the time.
- Deleted orders don't appear in either report. That's the argument for cancelling rather than deleting — see Refunds and cancellations.