How to Bill a Restaurant Order in 3 Taps

Tap 1 — the table

Open the floor view. You see your tables with their live status: free, occupied, bill printed. Tap the one the guests are sitting at and the order opens against that table.

That single tap is doing more than it looks. It attaches the order to a table, which means anyone on the team can pick it up — the captain who took the starters can hand over to the cashier at settlement without a word. For takeaway or a counter sale, tap New order or Quick bill instead and skip the table entirely; for a QSR counter you'd usually run token billing, where the order gets a number instead of a table.

Tap 2 — the items

Tap each dish. Categories keep your fastest-moving items on the first screen, so a regular order rarely needs scrolling or searching. Tap the same dish again and the quantity goes to two. The running total updates as you tap, which matters more than it sounds when a guest asks "how much so far?" halfway through.

Variants and modifiers are the part that separates a real restaurant POS from a calculator. Half plate or full. Extra cheese. No onion. Less spicy. These attach to the item, carry their own price where relevant, and — crucially — travel with the item onto the KOT, so the kitchen sees the instruction rather than hearing it shouted.

One habit worth building: send the order to the kitchen as soon as the guest finishes speaking, before you take the next table. That's what turns the POS from a billing machine into a service tool.

What happens in between: the KOT

Between tap two and tap three, the kitchen has already started cooking. When you save or send the order, the KOT is issued — printed on the kitchen printer, shown on the kitchen display screen, or both. It carries the table number, the items, the modifiers and the time.

Nobody walks a paper slip across the floor. Nobody deciphers handwriting. And because the ticket is timestamped, you can see later how long tickets actually took, which is the only honest way to argue about kitchen speed. Our KOT and KDS guide covers how to set the screens up and where to put them.

Tap 3 — settle and print

The guest asks for the bill. Tap Settle, choose how they paid, confirm. Done.

In that one tap the software does five things you would otherwise do by hand: it prices the order, applies the tax rate stored against each item and splits it into CGST and SGST, records the payment method, frees the table for the next party, and posts the sale into today's reports. If a thermal printer is paired, the receipt prints at the same moment.

Split payments live here too. Two friends paying half in cash and half by UPI is one bill with two payment lines, not two bills — which keeps your day-end cash count and your UPI settlement honest. We go deeper on that in accepting UPI and split payments.

The five-minute setup that makes three taps possible

Three taps at the counter is the payoff for doing four things once.

1. Outlet details. Legal name, address, GSTIN if you are registered, FSSAI number. This is what prints in the header of every bill.
2. Menu items. Name, price, category, and the GST rate plus HSN or SAC per item. If your menu is already in a spreadsheet, bulk import it rather than typing. Get the tax field right now and you never think about it again — see our guide to the 5% versus 18% question before you fill it in.
3. Tables or sections. Name them the way your staff already name them, not the way a floor plan does. "Terrace 3" beats "T-14" if that is what the captain shouts.
4. Printer. Pair the thermal printer over Bluetooth or LAN and print one test bill. Do this before service, not during it.

Note the order of importance: the menu is the whole job. Everything else is minutes. An outlet with a clean, well-categorised menu bills fast on any decent system; an outlet with 400 uncategorised items will be slow on all of them.

Three flows, one habit

When the internet drops mid-order

Nothing changes. On an offline-first POS the menu, prices, tables and tax rules live on the device, so all three taps work with no connection: the order is created, the KOT fires, the bill prints, the sale is saved locally. When the connection returns everything syncs, and because each order gets a stable unique ID at the moment it is created on the device, nothing gets counted twice. That architecture is the difference between carrying on and stopping service — we explain the mechanics in restaurant billing without internet.

Four mistakes that turn three taps into ten

1. No categories. A flat list of 200 items means scrolling on every order. Group them the way guests order.
2. Prices typed at the counter. If cashiers are entering amounts by hand, your reports are fiction and your tax is a guess. Prices belong on the item.
3. Settling before sending the KOT. The kitchen should be cooking while the guest is still deciding on dessert.
4. One shared login. Give each person their own PIN. Then a void, a discount or a missing bill has a name against it — see staff roles, PINs and accountability.

Train new staff on exactly this: table, items, settle. Twenty minutes on a quiet afternoon and they're on the floor. That is the real test of a POS — not how many features it has, but how fast someone who has never used it can bill their first order.