Restaurant billing software with KOT & GST

Yes — take orders by table, fire KOTs and settle a GST bill; takeaway and delivery modes are supported too.

Yes — 80mm thermal receipts print silently.

Yes — the counter runs offline.

Yes — that is the whole point of a KOT. The moment a round is confirmed the kitchen ticket prints, while the table stays open and unbilled. Further rounds fire their own KOTs against the same table. The bill is totalled only when the guest asks for it, so the kitchen never waits on the cashier.

No — there is no aggregator API. Delivery orders are entered at the counter like any other order and tagged to the aggregator as their own tender. When the payout arrives, net of commission, you reconcile it against those orders. It is honest bookkeeping rather than an automatic feed, and it keeps the ledger correct.

Entered as delivery-mode bills — there is no automatic API pull from the platforms, and we would rather say that than imply an integration. The day-end then shows the cash, UPI and aggregator split so platform settlements reconcile against your own numbers instead of being taken on faith.

Yes — half/full portions, add-ons, spice levels — so the KOT the kitchen sees is the order the customer gave. Seasonal menu changes are ordinary edits, not a rebuild.

The restaurant rate scheme and the composition option are national and set by notification — we print no figures that move, and the regime you elect is your CA's conversation. LekhaPro raises compliant bills and posts them to real books under either, and the day-end GST summary comes from those postings.

Plans are ₹249, ₹449 and ₹2,499 a month (yearly = two months free), with the full restaurant counter — tables, KOTs, modifiers, day-ends — in the offline core of every plan. GST-inclusive totals are on the pricing page.

Yes — the Desktop edition runs the whole floor offline: orders, KOTs, bills and day-end. Saturday nine o'clock is exactly when the connection fails and exactly when billing must not.

Yes — the three modes are first-class on the same bill stream, and the day-end separates them so you can see what the dining room, the counter and the platforms each actually did. One ledger underneath all three.

Yes — the same billing runs token-style counter service for a QSR or sweet shop and table-plus-KOT service for a dining room, with takeaway parcels and delivery-mode bills alongside either. A kitchen that does all three across one day — counter breakfast, table lunch, delivery dinner — closes one day-end, not three.

Menus are yours to edit — seasonal items come and go as ordinary changes, and variants and modifiers carry the price differences with them. What it does not do is auto-sync a delivery-platform menu: that update stays deliberate and manual, and we would rather state that than imply a sync that is not there.

Because no trade is more local than food — a kebab town, a dhaba highway, a tourist season and an aggregator-heavy metro run different services — and because professional tax on a staff-heavy trade is a state fact each page cites with its source. The software is identical everywhere.