Restaurant POS Live

The restaurant POS

Tables across the top, the menu below, the open order down the right. Punch, fire the KOT, settle at the counter or send it to the room.

The POS is one screen: the tables of the outlet, the menu of the moment, and the order being built. A captain punches, the KOT fires to the kitchen station each dish belongs to, the bill is made when the table asks, and it settles at the counter or goes to the room.

What it does every service

Dine-in by table, room service by room, takeaway and delivery by ticket.
A KOT per kitchen station — the tandoor's ticket does not print at the bar.
Modify or cancel a KOT with a reason, and the kitchen gets the reprint.
Split a bill, merge two tables, move a party to another table.
Settle by cash, card, UPI, on account, or to the room — chosen from the guests in house, by room and name.
Reverse a bill, with a reason, and the reversal on the day's report.

To the room

A bill sent to the room is on the guest's folio in the same second, as a restaurant charge with its own tax. Not an export, not a sync — the same row.

On its own

The POS sells to a restaurant with no hotel: an outlet that is a customer in its own right, with its own login, its own day end and its own GST bills, and no booking chart anywhere in sight.

More on Restaurant POS

KOTs and the kitchenA ticket per station, a modification the kitchen sees as a reprint, and a KOT the kitchen can hold — with the store drawn down on every fire. Tables, stewards and the floorThe table belongs to somebody. Steward-wise sales are answerable because the captain on the table is a fact, not the login on the till. Charge to the roomThe bill goes to the guest's folio in the same second, as a restaurant charge with its own tax — after the guest's name and room are matched. The bill and its GSTA numbered GST bill per outlet with HSN codes per line, the slab per dish, and service charge that is taxable because the law says so. Tenders and reversalsA tender is controlled — cash, card, UPI, on account, to the room, complimentary — and a bill that was wrong is reversed, not deleted. Cashier shifts and the outlet day endA shift opens with a float and closes with a count; the day end closes every open table, reads the tenders, and refuses to close a day still in the future. An order arrives from somewhere elseZomato, Swiggy, the outlet's own online menu — an order posted as JSON lands as a ticket, once, with unmapped items refused by name. The menu, and a price that knows what time it isCategories, dishes, variants, a price per channel, and a schedule — happy hour is a window on the menu, not a second menu. A restaurant without a hotelThe POS sells on its own — an outlet that is a customer in its own right, with no booking chart, no room, and every till, bill and day end working. The kitchen storeUnits, locations, ingredients, recipes with yield loss, an append-only stock ledger, and consumption on every KOT — so the food that was used is a cost the day carries.