Kitchen Order Tickets (KOT) for Indian Restaurants: Paper, Printer, or Screen — and How to Set It Up

Published 6 August 2026

Walk into most Indian restaurants, dhabas and cafes and you'll find the same thing behind the counter: one screen, one person running it, and a kitchen with no phone, no tablet and no screen of its own. The order still has to get from the counter to the cook somehow — and for the vast majority of outlets, that somehow is still a printed slip of paper. This is a practical guide to what a Kitchen Order Ticket (KOT) actually is, why the kitchen's copy has to be separate from the customer's bill, and how to set printed KOTs up properly on Biller.app — without assuming you need a kitchen screen to run a real kitchen.

What a KOT actually is

A KOT is the kitchen's own copy of an order — table or counter, items, quantities, any modifiers ("no onion", "extra spicy"), and the time it was sent — with no prices on it at all. That last part matters: a cook needs to know what to cook and how much, not what it costs, and printing prices on a kitchen slip is how a used ticket ends up quietly doubling as a discount receipt. The bill and the KOT are two different documents generated from the same order, for two different audiences, and good software keeps them that way rather than printing one thing twice.

The signal is the print, not the typing

The single most common mistake in a KOT setup is treating "the waiter typed the order into the POS" as the moment the kitchen finds out about it. It isn't — and it shouldn't be, because a cook can't act on a screen they don't have. On Biller.app, adding or editing items on a table never sends anything to the kitchen by itself; the kitchen only learns about an order when someone deliberately sends it — tapping Print KOT on a Quick Bill table, or Move to Kitchen on an Advanced-flow ticket. If you go back and bump up a quantity that's already been sent, Biller.app doesn't reprint the whole order — it prints a follow-up ticket for just the extra, e.g. +2 Paneer Tikka, so the kitchen adds the right amount instead of re-cooking what's already on the pass. And if a ticket jams or walks off the counter, Print KOT on the bill footer always works as a plain reprint, whether or not anything new has been added.

What real outlets actually look like

Most of what gets written about "kitchen display systems" assumes a kitchen with a mounted screen and a cook glancing up at it between orders. That's real for some outlets, but it isn't the median one. In a full day spent in real Indian outlets, the common pattern was: no phone or screen in the kitchen at all, one counter screen running the whole front of house, one person doing most of the ordering-and-billing work rather than a deep role hierarchy, and well under a hundred bills a day. For that outlet, a printed KOT that lands physically at the pass — no login, no glancing at a screen mid-cook — is not a compromise. It's the right tool. A three-step flow (type the order, tap Print KOT, cook works off the slip) beats a clever screen nobody in the kitchen has time to check.

Paper KOT vs. a kitchen screen (KDS)

Treat this as an either/or by need, not a ladder you're expected to climb. If your kitchen has a real screen and staff who'll glance at it, the kitchen ticket wall is genuinely good — live rounds, aging tickets, void/waste tracking that stays visible on the screen instead of disappearing. If it doesn't, a printed KOT does the job without asking your kitchen to change how it works.

Setting up printed KOTs on Biller.app

1. Install the printer companion app on any always-on computer at your outlet (a spare PC, laptop or Raspberry Pi) — it's what lets Biller.app's cloud service reach a printer on your local network. The companion's own setup page detects printers already connected to that computer and can add one for you as part of pairing.
2. Give the printer a role — Receipt, Kitchen, or Both — so a kitchen ticket only ever prints where the kitchen actually is, and a bill copy only prints where the counter is.
3. Turn on "Automatically print a KOT here when sent to the kitchen" on that printer so a KOT prints itself the moment a ticket is sent — no separate tap at the printer.
4. Set the paper width (58mm or 80mm) to match your roll, and run a Test Print before you rely on it for real orders.
5. No computer at all — just a phone and a Bluetooth thermal printer? Turn on print bridge mode from that phone instead, and it becomes the printer, no separate app or agent needed.

Send a Quick Bill order and the printed ticket comes out compact — bold item lines, no per-item category header — because a single-station kitchen has nothing to route between. Run an Advanced-flow ticket (a kitchen-board setup, or a delivery/aggregator counter) and the ticket prints larger, with each item's category shown above it and a divider between items, built to be read at a glance across a busier kitchen rail.

What's still honest to say isn't there

Biller.app doesn't pull orders in automatically from Swiggy or Zomato yet — there's no live aggregator integration. What it does do: type a delivery runner's pickup OTP into a bill's Delivery OTP field and it prints on both the KOT and the receipt, so a runner can be matched at handoff without needing that integration to exist. This is a print/setup guide, not a claim that every kitchen workflow is solved — see our honest POS comparison for where the category as a whole still has gaps.

Bottom line

A KOT's job is simple: get the right order to the right kitchen, fast, without prices on it, without assuming a screen exists where it doesn't. For most outlets today, that means a printer, a role, and a paper width — set up once, working automatically after that. If your kitchen has grown into a real screen setup, the ticket wall is there too. Both are core product on Biller.app, free to start with 510 Biller credits once per outlet — a plain bill costs one credit, and credits never expire — on a single counter or across multiple outlets.