Restaurant KOT Void and Cancellation SOP: Stop Production, Keep the Trail
A stage-based SOP that stops the kitchen clearly, protects the guest bill and keeps production, waste and approval evidence connected.
Last verified: 2026-08-31
A restaurant KOT cancellation must reach the station before staff assume production stopped. The POS should create a visible cancellation or amendment linked to the original ticket, while the kitchen acknowledges whether work was not started, stopped, completed or already served.
Do not use one delete button for every case. Cancelling before preparation, voiding a billed line, remaking an item and refunding payment are different events with different evidence.
Stage decision table
The station, not the waiter, confirms production stage. Time-stamp request and acknowledgement.
If a ticket cannot be stopped, the record should say completed rather than pretending the cancellation prevented production.
| Stage | Kitchen action | Front/finance action |
|---|---|---|
| Not sent | No KOT impact | Remove under draft policy |
| Sent, not started | Acknowledge stop | Cancel with reason/authority |
| Preparing | Stop if safe; record used inputs | Approve cancellation and waste |
| Completed | Hold/dispose/reassign only under policy | Record full cost impact |
| Served/handed over | No production cancellation | Resolve bill/refund separately |
| Paid | No silent deletion | Use approved refund and VAT treatment |
Use a linked cancellation ticket
Keep the original KOT ID, order ID, item, quantity and send time. Issue a new cancellation/amendment event showing old instruction, new status, requester, reason and approver.
Make the event visually distinct on printer or KDS. A small negative quantity without the original context is easy to miss.
Reason and responsibility
Reason codes describe the trigger, not guilt. Add a short factual note and link any complaint, incident or support reference.
| Code | Reason | Owner for review |
|---|---|---|
| GST | Guest changed/cancelled | Service manager |
| ENT | Entry or modifier error | Front-of-house lead |
| AVL | Item unavailable | Kitchen/procurement |
| QLT | Quality failure | Kitchen lead |
| DUP | Duplicate send | POS owner |
| DLY | Delay exceeded resolution | Duty manager |
| SYS | System/printer routing | Operations/IT |
Approval matrix
Set approval by stage, value, payment status and risk. A waiter may request cancellation, but a manager should approve higher-risk cases such as completed, served or paid orders.
Prevent self-approval where practical and preserve overrides. Emergency safety action can happen immediately, followed by documented approval.
Connect KOT, bill, refund and VAT record
Update the customer bill only through the approved billing control. If payment occurred, connect the refund or receivable decision. If a statutory invoice was issued, obtain advice instead of assuming a KOT cancellation reverses it.
NBR guidance says applicable businesses issue the VAT invoice and keep sales records. An internal cancellation event does not erase those obligations.
Sources for this section: NBR: 10 Responsibilities of Taxpayers
Capture wastage and remake separately
If ingredients were consumed, create a wastage record with quantity, cost basis, cause and approver. If the kitchen remakes an item, issue a linked remake ticket without automatically charging the guest twice.
Separating cancellation and remake reveals whether loss came from guest change, entry error, availability, quality or production failure.
When printer or KDS acknowledgement fails
Use the approved fallback to contact the station, record the person reached and keep the cancellation visible until acknowledged. A verbal call is an emergency channel, not the final record.
After service, test routing and investigate why the event failed. Do not close the technology issue because the cook happened to hear the shout.
Day-close review
- All open cancellation requests acknowledged
- Completed/served cases approved
- Bill and payment trail linked
- Wastage/remake recorded
- Reason-code outliers reviewed
- Printer/KDS failures escalated
- Manager signs exception report
Metrics that lead to action
Track cancellation count and value by stage, reason, station, waiter, hour and item. Review completed-after-cancel, missing acknowledgement and repeated unavailable items. Use context and sample evidence before taking personnel action.
How we calculated and verified this
This SOP distinguishes an internal kitchen instruction from customer billing and statutory records. NBR is cited only for the public duties to issue applicable VAT invoices and keep sales records.
The restaurant must have its accountant approve how a KOT cancellation connects to bills, refunds and VAT documents. KOT workflow itself is an operator control.
A good KOT cancellation process stops production visibly and preserves the original instruction. It then carries the decision into billing, payment, wastage and review without silent deletion.
Rosuii can hold the order and kitchen workflow; accounting and VAT treatment still require approved professional rules.
Related guides
See this workflow in Rosuii: Send orders to kitchen and preserve status changes in Rosuii
Sources checked
Last updated:
Frequently asked questions
Can a waiter delete a KOT after sending it?
What if food is already prepared?
Does KOT cancellation cancel the VAT invoice?
How should a remake be recorded?
What should day close review?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
