A KOT printer for a cloud kitchen is the cheapest piece of equipment that changes how a lunch rush feels. When 100 orders arrive between 12 and 1, the difference between a kitchen that reads them off a phone and one that pulls a printed ticket off a thermal printer for each order is the difference between shouting and cooking. This post is about that hour: what a kitchen ticket needs on it, which printer to buy, how automatic printing of WhatsApp and store-page orders works, and how the tickets run through the stations.
It assumes a single cloud kitchen with two to four cooks, orders arriving from WhatsApp, a store page and possibly an aggregator, and a goal of getting every order packed within 15 minutes during the rush.
What breaks at 100 orders in 60 minutes
At 20 orders an hour, reading orders off a phone works. Someone calls out "two chicken biryani, one raita", the cooks nod, and the order gets packed. At 100 orders an hour, that method fails in three predictable ways.
First, the person holding the phone becomes the bottleneck: they are reading, calling out, answering "which one was extra spicy?", and marking orders ready, all at once. Second, add-ons and variants get lost in the shouting. "Family pack, no onion, extra raita" becomes "family pack". Third, nobody knows what is done. Three orders of the same dish sit on the counter and nobody is sure which bag belongs to which customer.
A printed ticket fixes all three because it moves the order from a screen one person holds to a piece of paper that travels with the food. The wider picture of why a KOT exists and what it should carry is in the complete KOT system guide; the rest of this post is specific to a cloud kitchen's rush.
Choosing the printer
Thermal printers come in two widths, 58mm and 80mm, and connect by USB, LAN or Bluetooth. For a cloud kitchen the decision is mostly about ticket width and placement.
| Consideration | 58mm | 80mm |
|---|---|---|
| Text per line | Around 32 characters | Around 48 characters |
| Long item names with add-ons | Wrap to two lines | Usually fit on one |
| Paper cost | Lower per roll | Higher, but fewer wrapped lines |
| Best for | Short menus, tight counters | Menus with variants and add-ons |
| Price | Lower; basic models are inexpensive | Higher; auto-cutter models cost more |
For a biryani or thali kitchen where most tickets carry a variant and an add-on, 80mm with an auto-cutter is worth the extra. For a momo or roll kitchen with short item names, 58mm is fine. The connection type matters less than placement: the printer should sit at the pass or the packing station, where the ticket meets the bag, with a power point and away from the steam. The detailed comparison, including models and paper, is in thermal printer for restaurant billing: 58mm vs 80mm.
What a kitchen ticket should carry
A KOT is for the cook and the packer, so it is a different document from the customer's bill. From top to bottom:
- Order number and time received, in large type. The number is what everyone calls out; the time is how you spot an order that has waited too long.
- Channel and type: WhatsApp, store page or dine-in; delivery, pickup or scheduled. A pickup at 1:30 and a delivery due now are cooked in a different order.
- Items with quantity, variant and add-ons, one item per block, add-ons beneath it. "2 x Chicken Biryani (Family), extra raita, no onion" together.
- Customer instructions, if any, on their own line so they are not missed.
- Delivery or pickup details, enough to pack the right bag: area or pickup slot, and whether payment is done or cash is to be collected.
Prices do not belong on a KOT; the cook does not need them and they clutter the ticket. The bill, with prices and GST, is a separate print for the customer when needed.
What this looks like on Tezzu
On Tezzu, KOT printing is built in. Connect a 58mm or 80mm thermal printer to the device running the dashboard or staff app, and every new order prints a kitchen ticket as it comes in, whether it arrived from the WhatsApp bot, the store page at tezzu.in/store/your-name, a scheduled pre-order or a dine-in QR table. There is no step where someone has to open the order and press print, which is the step that gets skipped at 12:40.
The ticket carries the order number, the time, the channel and order type, each item with its variant and add-ons grouped under it, the customer's instructions, and the delivery or pickup line, in the order described above. Bundles print with every pick listed under the bundle name, so a thali kitchen sees "Lunch Thali: jeera rice, dal makhani, paneer bhurji, raita, papad" rather than just "Lunch Thali".
The same order appears on the live dashboard and the staff app, which is where it is marked preparing, ready and out for delivery; the printed ticket is the kitchen's copy, and the status updates are what the customer sees on WhatsApp. A GST bill for the customer is a separate print from the same order, so prices stay off the kitchen ticket.
If the printer goes offline, the order is still in the dashboard and the app, and the kitchen works from the screen until it is back. The same printer handles dine-in orders from QR tables, described in dine-in with Tezzu, and the complete list of ordering and kitchen features is on the features page.
Print your first KOT before the next lunch rush
Connect a thermal printer, take a test order on WhatsApp, and watch the ticket come out at the pass. Every plan starts with a 7-day free trial, then ₹10 per order and no commission.
Start your free 7-day trialThe rush, minute by minute
Here is how the hour runs in a four-person biryani kitchen with an 80mm printer at the pass.
12:00 to 12:15. Orders start at about one a minute. The printer prints each ticket as it lands; the pass cook tears it off, reads the items aloud once, and clips it to the rail in order. The rice and gravy cooks pull from the rail left to right.
12:15 to 12:40. Peak, two to three orders a minute. The rail holds eight to twelve tickets. The pass cook watches the time printed on each ticket; anything older than twelve minutes moves to the front. Scheduled pickups for 1:30 are clipped to a separate hook and left alone until 1:10.
12:40 to 13:00. Packing catches up. The packer takes the ticket with the finished food, checks the add-on line, writes the order number on the bag, and drops the ticket on a spike. Riders match bag numbers to the order on their phone. Nothing leaves the kitchen without its ticket having been spiked.
The rail, the hook and the spike are the whole system. The printer feeds it, the ticket's time stamp orders it, and the spike closes it. How a kitchen structures the rest of its order flow, from WhatsApp to a display or a rail, is in cloud kitchen order management, and the staffing side of a 100-order hour is in peak hour management.
Paper, placement and what to do when it fails
Thermal paper is cheap enough that a ticket per order is never worth saving on; buy a month's supply and keep two spare rolls at the pass. Mount the printer where the ticket can be torn off with one hand, at chest height, out of the steam path from the rice station, because damp paper jams. Print one test ticket before the rush every day; the moment to discover the roll has run out is 11:45, well before the first real order.
When the printer does fail, fall back to the staff app: one person reads orders from the app and writes order numbers on bags. It is the method you were trying to leave behind, and it works for twenty minutes while someone swaps the roll or the cable.
Frequently asked questions
Which KOT printer is best for a cloud kitchen?
An 80mm thermal printer with an auto-cutter suits most cloud kitchens, because tickets with variants and add-ons fit on one line and tearing is one-handed. A 58mm printer is enough for short menus with few add-ons. Choose USB, LAN or Bluetooth based on what the device running your ordering dashboard supports and where the printer will sit.
Can WhatsApp orders print automatically on a KOT printer?
Yes, if your ordering system has KOT printing built in. On Tezzu, an order from the WhatsApp bot, the store page or a QR table prints a kitchen ticket as it arrives, without anyone opening it. The ticket lists the items, variants, add-ons and instructions in a fixed layout every time.
What should be printed on a KOT?
Order number and time, channel and order type, each item with quantity, variant and add-ons, customer instructions, and the delivery or pickup line. Leave prices off; they belong on the customer bill, which is a separate print. Use large type for the order number, since that is what gets called out across the kitchen.
Do I need a kitchen display system instead of a printer?
Usually no, at this size. A display works well when several stations each need their own view; a single cloud kitchen with one pass is served better by a ticket that travels with the food to the packing station. Many kitchens run the staff app on a tablet at the pass alongside the printer and get most of the benefit of both.