What Is a KOT in a Restaurant? Plain Answer

By Scan2Plate · Published 2026-09-21 · 6 min read

A KOT, or Kitchen Order Ticket, is the slip that tells a restaurant kitchen what to cook. It lists the items ordered, their quantities and the table or token they belong to. It is separate from the customer's bill because the kitchen needs to know what to make, not what it costs.

What is actually on a KOT

A KOT carries only what the kitchen needs to act on. A typical one shows the table or token number, a serial number so tickets can be referred to, the time it was raised, and each item with its quantity and portion size.

What it does not carry is price. A cook does not need to know that the paneer is ₹240, and putting it there invites the ticket to be mistaken for a bill.

Why the kitchen ticket is separate from the bill

Because they happen at different times and answer different questions.

A table that orders in three rounds generates three KOTs, because the kitchen has to cook three times. It generates one bill, because the guest pays once. Collapsing the two would mean either printing a bill the guest has not asked for, or making the kitchen wait until the end of the meal to start cooking.

The separation is also what makes a missing round detectable. If the kitchen cooked it, a KOT exists. If that KOT's items are not on the bill, something went wrong between the two — and that is a difference you can actually look for.

How a KOT works in practice

1. The order is taken. A waiter writes it on a pad, or enters it on a POS, or a guest places it from a QR menu on their own phone.
2. The KOT is raised. On paper this is a carbon pad, one copy to the kitchen and one kept. On a system it prints in the kitchen or appears on a kitchen screen.
3. The kitchen cooks from it. The ticket is the instruction, so the order of tickets is the order of cooking.
4. The dish is marked done. On paper, the slip moves to a spike. On a screen, the ticket moves through preparing and ready.
5. The items reach the bill. On paper, someone adds them up at the end. On a system, they were already on the running bill from the moment the order was taken.

Paper KOT or kitchen screen?

Both are in use across India, and neither is wrong.

Paper survives heat, steam and a dropped connection. It needs no power at the pass. It is also the version that gets misfiled, goes under a counter, or is written in handwriting the cook on shift cannot read.

A screen is always legible, shows what has been waiting longest, and lets the floor see what is ready without walking into the kitchen and interrupting. It needs somewhere safe to mount and a connection.

Many restaurants run both: a screen at the pass, and a printed ticket for a station that cannot see it. A kitchen display system and a KOT printer are not alternatives so much as two outputs of the same order.

Numbering a KOT, and why it is not the bill number

A KOT carries its own serial, separate from the bill serial, and the two are not interchangeable.

One table can produce three KOTs and one bill. If the kitchen ticket and the bill shared a number, either the second round would overwrite the first or the guest would receive three bills. Keeping them separate is what lets you say “KOT 112 was cooked and appears on bill 47” and have both halves of that sentence mean something.

In a paper system both series are written by hand, which is where they drift. On a system the bill serial is allocated centrally per business day, so it cannot repeat even when two counters bill at once, and a cancelled bill retires its number instead of passing it on.

What happens when an order changes

Orders change constantly, and how a system handles the change is more revealing than how it handles the happy path.

1. An item is added. A new KOT is raised for the addition only. The kitchen should not receive the whole order again, because it has already cooked most of it.
2. An item is cancelled before cooking. The cancellation has to reach the kitchen and the bill. Cancelling on the ticket alone leaves it on the running total.
3. An item is cancelled after cooking. This is a management decision, not a software one: the food exists and somebody pays for it or it is written off. What the system should do is record which happened.
4. A table moves. The order moves with it, or the kitchen delivers to an empty table.
5. A guest changes a portion from half to full. Treat it as a cancellation and a new item, because it is a different dish to cook and to cost.

KOT and the bill, reconciled

At the end of a service the useful question is whether everything cooked was charged for.

With paper, answering it means matching a spike of kitchen slips against a stack of bills, which nobody does nightly and everybody intends to. With a system the reconciliation already happened: the order that produced the KOT is the order on the bill, because they are the same record viewed twice.

That is the real argument for putting KOTs on a system, and it is not about the kitchen at all. The kitchen manages fine with paper. It is the round that got cooked and never billed that costs money, and that is a reconciliation problem rather than a cooking one.

Common KOT mistakes

• Reusing a KOT number. If two tickets share a number, a dispute about what was cooked cannot be settled.
• Writing the price on it. Invites the ticket to be handed over as a bill.
• Not raising one for an added round. The commonest way a round gets cooked and never billed.
• Cancelling in the kitchen only. If the order is cancelled on the ticket but not on the system, the bill still has it.
• Handwriting portion size. Half and full look identical when written quickly; they are different dishes to cost and to cook.

Questions people ask

See how KOTs reach the kitchen