What a KOT does and why the order of steps matters
A kitchen order ticket (KOT) is the instruction your kitchen cooks from. In a well-run restaurant the bill is built from the same KOTs, so what the kitchen cooked and what the guest paid for always match. When those two records are kept separately, on a handwritten slip in the kitchen and a different note at the counter, items get cooked but not billed, billed but never cooked, or cancelled without anyone knowing who approved it.
This guide is for owners and managers of dine-in restaurants, cafes, family restaurants and hotel restaurants where the kitchen and the cash counter keep blaming each other. By the end you should be able to map your own order flow, decide how KOTs reach each kitchen section, and set a small number of rules for changes, cancellations and settlement that your staff can follow on a busy Saturday night.
The five stages of a restaurant order
Every order, whether a cup of tea or a family dinner for eight, passes through the same stages. Software does not remove any of them. It makes each stage leave a record, so a gap can be traced to a person and a time.
- Order capture: the captain or waiter enters items against a table number, with any notes such as "less spicy" or "no onion, no garlic".
- KOT generation: the POS prints or displays a KOT in the right kitchen section, with the table number, items, quantities, notes and time.
- Preparation: the kitchen cooks from the KOT and, if a kitchen screen is used, marks items as preparing, ready and served.
- Billing: when the guest asks for the bill, it is generated from the running order on that table, not typed afresh.
- Settlement: the cashier records how the bill was paid, and the table returns to vacant so it can be seated again.
| Stage | Who owns it | Typical problem without control |
|---|---|---|
| Order capture | Captain / waiter | Items told verbally to the kitchen and never written down |
| KOT generation | POS | One slip for all items, so the bar or tandoor misses its part |
| Preparation | Kitchen | No record of when an order came in, so delays are argued about |
| Billing | Cashier | Bill made from memory; a second round of drinks is forgotten |
| Settlement | Cashier / manager | Bill printed but payment mode not recorded, or table left open |
Routing KOTs to the right kitchen section
Many Indian restaurants have more than one preparation point: a main kitchen for curries and rice, a tandoor for breads and kebabs, a bar or beverage counter, sometimes a separate Chinese or dessert station. If one KOT lists everything, someone has to read it aloud or walk it around, and that is where items are missed.
Take an example table that orders paneer tikka, dal makhani, four butter naan and two fresh lime sodas. With section-wise routing, the tandoor printer receives the paneer tikka and naan, the main kitchen receives the dal, and the beverage counter receives the sodas. Each section sees only what it must prepare, and each slip carries the same table number and time.
Notes, modifiers and course timing
Notes such as "less oil", "Jain" or "extra gravy" should be chosen from a fixed list in the POS wherever possible rather than typed freely, because typed notes are inconsistent and hard to read under pressure. For course timing, train captains to send starters first and send the mains as a second KOT when the table is ready, instead of firing everything at once and letting mains go cold.
Printer or kitchen screen?
A KOT printer is simple and works well when the kitchen is small. A kitchen screen adds status updates and shows how long each order has been waiting, which helps the head cook prioritise during a rush and gives the manager a factual answer when a guest complains about delay.
Dine-in, takeaway and delivery: how each order type differs
Most restaurants now handle all three order types from the same kitchen. Keeping them as separate order types in the POS matters because the kitchen packs them differently, the bill is settled at a different moment, and your reports need to show which channel is growing.
| Order type | How it is identified | When the bill is settled | Extra details to capture |
|---|---|---|---|
| Dine-in | Table number and captain | At the end of the meal; several KOTs may join one bill | Covers (number of guests), table moves |
| Takeaway | Order or token number | Usually before the food is handed over | Packing instructions, pickup time |
| Delivery (own riders) | Customer phone and address | On delivery or in advance, as per your policy | Address, rider assigned, delivery charge, packing status |
| Delivery app order | App order ID | Through the app's payout, not at your counter | App order reference so the payout can be matched later |
If your delivery app orders are not connected to the POS, decide who enters them and when. An order that is cooked from the tablet screen but never entered in the POS will not appear in your sales, stock or reports, and nobody will notice until the payout does not match.
Changes and cancellations: the rules that stop leakage
Most money lost between kitchen and counter is lost here. A guest changes an order, a dish is sent back, or an item is quietly removed from a bill after the guest has paid in cash. Clear rules, enforced by user permissions rather than trust alone, prevent most of it.
- Before a KOT is sent: captains may edit freely, because nothing has been cooked yet.
- After a KOT is sent: removing or reducing an item needs a manager's approval and a reason chosen from a short list, such as guest changed mind, wrong order taken or item unavailable.
- Cancellation slip: every approved cancellation should print or display in the same kitchen section, so the cook stops preparing it.
- Cooked but not served: if the dish was already made, record it as wastage so your stock figures stay honest.
- After the bill is printed: items should not be deleted by the cashier; any change should need manager rights and be visible in the audit log.
- Reprints: a reprinted bill should be marked as a duplicate so it cannot be used to collect payment twice.
A cancellation the kitchen never hears about still gets cooked. A cooked dish that is cancelled without a wastage entry disappears from your food cost. Both need a record.
Table moves need the same discipline. When a party shifts from table 4 to a larger table 9, or two tables are merged for a group, the running order should move with them. Creating a fresh order on the new table is how the first round of starters gets left off the final bill. How these cancellations and discounts should be reviewed each week is covered in our guide to restaurant reports owners should review weekly, and recording cooked-but-wasted food is explained in restaurant inventory basics.
Printing the bill and settling the table
When the guest asks for the bill, the cashier should open the table's running order, check that every KOT is included, apply any approved discount or coupon, and print the GST invoice. If guests want to pay separately, split the bill in the POS by item or equally, instead of writing two bills by hand.
Settlement is the step most often skipped. The bill is printed, the guest pays, and the cashier moves on without recording whether it was cash, card, UPI or a wallet. At closing time the drawer and the UPI app do not match the system, and nobody can say which bill was paid how. Make it a rule that a table only returns to vacant after the payment mode is recorded.
Before closing each night, the manager should check one list: bills printed but not settled, and tables still showing as running. Each one is either a genuine credit, a mistake, or a problem that needs a conversation the next morning.
Preparing the KOT flow before go-live
A new POS rarely fails because of the software. It fails because the menu, printers and roles were set up in a hurry the day before opening. Work through this list with your manager and head cook first.
- Menu mapping: every menu item, including half and full variants and add-ons, is assigned to the kitchen section that prepares it.
- Printers and screens: one printer or screen per section, tested with a dummy order, with spare paper rolls kept at each point.
- Notes list: the ten or fifteen notes your guests ask for most are created as quick options.
- Roles: captains can send KOTs; only managers can cancel after a KOT or edit a printed bill; cashiers settle bills.
- Rehearsal: run a mock rush with staff playing guests, including a table move, a split bill and a cancellation.
- Power and internet: decide what happens during an outage; a single outlet with local printers may prefer an offline desktop setup.
How MATROP's restaurant software handles this flow, and when you may not need it
Our restaurant POS software covers the flow described above. Table management shows a floor map with each table as vacant, running or billed, and supports merging, splitting and shifting tables with waiter assignment. KOTs print automatically or appear on a kitchen screen, with item notes, status tracking (preparing, ready, served), time tracking and separate KOTs for different kitchens such as main, bar and tandoor. Billing supports GST invoices, split bills, discounts and coupons, multiple payment modes (cash, card, UPI, wallet), refunds and reprints. Role-based access for admin, manager, cashier, waiter and kitchen, shift-wise login and audit logs support the cancellation rules above.
Delivery orders can be recorded with address, rider assignment, delivery charges and packing status. For delivery app orders the workflow supports manual entry, and a direct API connection is handled as a custom integration, which we scope separately. If you are unsure whether you need that kind of custom work, our explainer on custom versus ready-made software may help. Restaurants inside hotels can also look at our hotel management software for rooms and front desk.
You may not need a KOT system at all if one or two people cook and serve a short menu from the same counter. In that case a simple billing setup is enough. If your outlet works counter-first, with payment before cooking, read our quick service billing tips instead, because the flow is different. MATROP PRIVATE LIMITED has its office in Ranchi, and works with restaurants across India; implementation covers requirement study and demo, menu, GST, printer and role setup, and training for cashiers, captains and kitchen staff with support during the first days.
Questions people ask
Do we need a kitchen display screen, or are KOT printers enough?
Printers are enough for many single-kitchen restaurants. A kitchen screen helps when you want cooks to mark items as preparing or ready and when you want to see how long each order has been waiting, which is useful in busy or multi-section kitchens.
What should happen when a guest cancels an item after the KOT has reached the kitchen?
The cancellation should be entered in the POS, approved by a manager with a reason, and a cancellation slip should reach the same kitchen section so the cook stops. If the dish was already cooked, record it as wastage rather than simply deleting it.
Can one table's order be split into separate bills for different guests?
Yes, if your POS supports split bills, and MATROP's restaurant software does. Agree in advance whether staff split by item or equally, so the cashier does not improvise at the table.
How should delivery app orders be handled if we have no direct integration?
Assign one person to enter each app order into the POS as soon as it is accepted, using a separate delivery order type, so the kitchen gets a KOT and your sales reports include those orders.
