Rooms & Front Desk
Room types, stays and a guest folio. Charge a restaurant bill to a room and settle it at checkout.
Per venue
₹1,500.00/mo
One platform for the floor, the pass, the bar, the shisha lounge, the till and the ledger. Built for rooms where a clumsy interface would be noticed — and remembered.
No card. No install. Menu live in about forty minutes.
0
Uptime, 90d
0
Terminals live
0
Unreconciled bills
Eight surfaces, one spine
Not renders. Each card opens the real interface with live data — the offline queue, the role guard, the settlement rules and all.
Revenue, covers, kitchen load, settlement risk and AI counsel on one pane.
Open itDrag-and-drop rooms, zone rules, merge and split, permanent table QR codes.
Open itA surface that reads like a brand site, not a PDF.
Open itWalk-in, takeaway, delivery, room service. Works with the line down.
Open itSplit, partial, multi-tender, GST invoicing, dine-and-dash defence.
Open itCourse-aware tickets, timers, chef assignment, delay escalation.
Open itFlavour, base, head, coal cycles, refills, cleaning discipline.
Open itRooms, stays, a guest folio. A dinner charged to 214 and settled at checkout.
Open itPlans that derive from each other, seasons, close-outs, allotments.
Open itMenu engineering, forecasting, staff scoring, retention curves.
Open itThe reason this exists
Releasing a table has exactly two callers in the codebase: a completed settlement, or a manager-authorised exception that writes its own audit row first. There is no third path — no admin panel, no support tool.
Staff flag a party as Heading to Exit, which starts a countdown you configure per venue. Breach it and the manager console escalates in real time.
The system watches bills, tables, staff actions and money — never people. No biometrics, no facial recognition, no covert tracking.
Table cannot be released with ₹52,300 outstanding.
What the API returns when the guarantee is tested.
Manager PIN required.
Closing unpaid needs a role, a reason code, a written note and a PIN.
Settled. Table released.
The only unguarded path that frees a table.
Offline-first
Terminals hold a full local ledger. Every mutation carries a client-generated ULID, so an order has a permanent identity before the server has ever seen it.
Every mutation lands on the terminal with a device-scoped ULID and a Lamport counter before the UI acknowledges it.
A durable outbox replays in causal order with idempotency keys. Duplicates are impossible; partial batches resume.
Money never merges — it appends. Two terminals paying one bill is not a conflict, it is two payments.
What still works: taking orders, printing KOTs on the venue LAN, creating bills, cash and card-machine payments, opening and closing tables, stock, walk-ins, shisha.
Try the terminalRooms
A property running a till from one vendor and a front desk from another spends its life reconciling the two. Here there is nothing to reconcile. A guest eats downstairs, charges it to 214, and it is on their folio before they have left the table — same ledger, same audit trail, same login.
Book, check in, move rooms, extend, cancel, mark a no-show. Availability is counted from the rooms — close a day out, hold an allotment back for an operator, or oversell one deliberately.
Charges from the restaurant, the bar, room service and the minibar land on one signed ledger. The balance is the sum of it, so nothing can disagree with it. A mistake is reversed, never edited.
A plan carries its own price or derives from another — non-refundable is best-available minus twelve per cent, in one row. Seasons move the number and only the highest-priority one applies.
Checkout is the last moment anybody can ask, and after it the guest is in a taxi. A manager may let them go with a PIN and a reason, and a month of those is a number an owner can look at rather than a surprise in the accounts.
See the deskThe night audit
A restaurant closes its till and the day is over. A hotel has guests asleep in it, so the day is declared — one folio line per guest per night, at the price that night was sold at. It will be pressed twice at three in the morning, and it is safe to.
Channels, on your terms
Which channels, whose contract, and who owns the inventory when two systems disagree are yours to set — not assumptions in our code. Own it and an oversell is refused with a reason they can show; let them own it and the oversell is taken and shown in red on your calendar.
Plugin architecture
Every capability is a plugin with its own price and permissions. A disabled module is unreachable, not merely hidden — its routes 403, its jobs never enqueue, its tables are never queried.
Room types, stays and a guest folio. Charge a restaurant bill to a room and settle it at checkout.
Online + offline terminal, KOT, GST invoicing
Forecasting, menu engineering, staff scoring
Contactless menu, cart, live order tracking
Aggregator sync, dispatch, virtual brands
Stock, suppliers, recipe costing, waste
Profiles, preferences, spend, segmentation
Points, tiers, gift cards, member pricing
Bookings, waitlist, reminders, no-show policy
Flavours, coals, refills, service timers
Live tickets, timers, chef assignment
Rosters, clock-in, tips distribution
Separate beverage queue and pass
Subscription
No add-on ladder, no per-cover cut, no quote to request. Payment processing is passed through at cost. These are the prices — the same ones your neighbour pays.
One venue · free forever
₹0 always
One venue · everything included
₹1,299.00 /venue/mo
Saves ₹2,598.00 a year
Up to 5 branches
₹3,499.00 /venue/mo
Saves ₹6,998.00 a year
Unlimited · white-label
₹7,999.00 /venue/mo
Saves ₹15,998.00 a year
21 days of Signature on any paid plan. No card. Cancel by doing nothing. Move up or down a tier whenever you like — it is pro-rated to the day.
Prices exclude GST. A venue on Counter is a customer, not a trial — it stays free, and the guest menu keeps working even if a paid plan lapses.
Open an account
A trial is a full Signature venue with a real database behind it. Run a real service on it — a restaurant cannot evaluate a POS any other way.