Stop wrong orders reaching your kitchen

When a plate goes back, the kitchen gets the blame and the kitchen is usually the last place the order was still correct. Walk it backwards and the same five gaps come up in every restaurant, whatever it bills on.

• At the table. The guest said less spicy, or no onion, or half. Nobody repeated it back, so nobody knows whether it was heard.
• Between the table and the till. The order is carried in someone's head, on a chit, or on a phone screen, past two other tables who also want something.
• At the till. Right dish, wrong table. Right table, wrong portion. The note that was said out loud and never typed anywhere.
• Between the till and the kitchen. The ticket that never printed, the one that printed twice, and the dish that was sold when the kitchen ran out of it an hour ago.
• At the pass. The right ticket, the wrong plate, or a round cooked a second time because nobody could tell whether it had already gone.

The habits below close the first four. They cost nothing to start on Monday, and the till only has a job in two of them.

Read the order back before you leave the table, dish by dish, with the qualifiers out loud: two butter chicken, one half, one less spicy, one plain naan. That one habit catches the mishearing while it is still free to fix, and it is the practice Checkmate recommends in its guide to order errors (a US company, read 2026-09-09; the habit translates without changing a word).

Checkmate's other habit matters more on an Indian menu than it does on theirs: keep item names short and distinguishable. If your menu carries Paneer Butter Masala, Paneer Makhani and Butter Paneer, somebody will ring the wrong one on a Saturday night, and no software fixes a naming problem. Rename them so a tired person reading a screen at speed cannot confuse them.

The other half of a correct order is knowing what you can still sell. A dish the kitchen ran out of at nine should be marked out of stock on the till, where the tile then greys out and reads Out of stock, instead of being sold twice more and apologised for twice more. It is one toggle per dish under Settings, which an owner or manager sets, and it is the cheapest apology you will ever avoid.

A modification only exists if it reaches the cook. Say it back at the table, then type it on the line: less spicy, no onion, no garlic, extra gravy. On the register a note belongs to the dish it was said about, so it prints on the kitchen ticket under that item rather than in a comment box at the bottom of the bill, which is the one place a cook will never look. Portions and add-ons travel the same way, because half or full is part of the order, not a billing detail.

Two rules keep notes useful. Write what the kitchen must do, not what the guest is like: "no onion" tells a cook what to do, "fussy table" does not. And keep them short enough to read at a glance on 58mm paper, because a note that wraps over three lines is a note the cook skims.

The kitchen should cook a round because a ticket told it to, once. Take the whole table, check it, fire it. If the table orders again twenty minutes later, that is a second round and a second ticket. The failure this prevents is the expensive one: a second ticket that repeats the first round, so the tandoor makes four rotis nobody ordered while the new dish waits.

The register follows the same rule so a busy cashier cannot break it. Before a round is fired, tapping the same dish again just bumps its quantity on the check. After it is fired, the same tap opens a new line that rides the next ticket, because the earlier line has already been cooked. A fired line's quantity can still come down freely, which is how a table that took three waters and returned one gets billed for two without anybody being called over. It cannot go up, for the same reason: the kitchen only makes what a ticket named.

Nothing cooked without a KOT. That is not only about mistakes. Petpooja's glossary describes the oldest Indian skim plainly in its KOT cancellation entry (read 2026-09-09): the order is taken, the food goes out, the cash is pocketed and the KOT is cancelled so the item never reaches the bill. Their conclusion is the right one, that a cancellation needs a manager's approval and a logged reason, and it is why the void below is deliberately not a one-tap action.

If you want the definition rather than the mistakes, Restroworks has a clear explainer of what a KOT is and why it exists (read 2026-09-09). This page assumes you already know, and is about the twenty minutes when it goes wrong.

Paper and a kitchen display do the same job and fail differently. Paper is easy to read, costs nothing to add a station to, and is gone the moment it falls behind the counter or the roll runs out mid-service. A display keeps the round in front of the cook until somebody bumps it, shows what is still waiting and how long it has waited, and does not care that the printer jammed. Most kitchens are best with both: the screen at the pass, paper where flour and heat make a tablet a bad idea.

You will meet vendor claims of a big percentage drop in order errors from digital tickets. There is no study behind any of them, so we do not print the figure and neither should anyone selling to you. What a screen honestly buys is a ticket that cannot be dropped and a pass that can see its own queue. If the printer dies, the sale still goes through: tickets queue and retry for a few minutes, then park for someone to retry by hand. Setting either up is a guide, not a blog post: the kitchen display and the kitchen printer.

A captain app on the waiter's phone attacks the second gap in the list, the walk. The order is typed at the table, in front of the guest who can hear it read back, and fires to the same printer or screen. It does not replace the ticket, and it is only worth it if your floor is big enough that the walk is real. The captain guide shows the flow.

When a mistake reaches the table, fix the guest first and the record second, and correct the check by editing what is wrong rather than starting again. A rebuilt check destroys the evidence of what actually happened: the wrong dish, the round it was on, who was signed in. Nobody can look at it a week later and tell whether it was an honest error, a training gap or something worse.

Before the round fires, a wrong line is just removed, no PIN and no ceremony, because nothing has been cooked. After it fires, cooked food is real cost, so taking a line to zero asks for a reason picked from a list of four, plus a manager's PIN when a cashier is the one doing it. An owner or manager confirms their own, which keeps a single-manager restaurant working at 11pm. The line stays on the check, struck through, reading Cancelled and the time it was sent to the kitchen; the reason and the approver go to the order ledger rather than onto the check. After the bill is settled the correction is a refund and never an edit: the cashier types the amount again, then a manager or the owner enters their PIN. An issued tax invoice is a numbered document and the series has to stay intact, which is why the CGST invoicing rules treat a correction as a new record (ClearTax summary, read 2026-09-09).

The whole ladder, from a line removed before firing to yesterday's bill reprinted with DUPLICATE on it, is in the wrong bill post, and the button-by-button version is discounts, voids and refunds.

Start tomorrow with the free half: read every order back at the table, name the dishes so they cannot be confused, and mark what is out of stock before doors open. The till's part, notes that print and one ticket per round, is what EasyKOT does for ₹299 a month or ₹2,990 a year plus 18% GST, with three months free and no card.