Reservations, live table state, kitchen display, inventory, staff roster and GST billing on one layer. Guests stop waiting because the ticket got lost. You stop discovering wastage at month-end.
Built for Independent restaurants, cloud kitchens and multi-outlet groups.
Scope this with usThe problem
The floor runs on memory. KOTs disappear between the pass and the kitchen. Stock is counted when someone has a free Sunday. Reservations live in a diary that cannot see walk-ins. WhatsApp orders hit a personal phone. GST invoices are a closing-time scramble — and the owner only finds out a dish is 86'd when a table has already ordered it.
In practice
A guest books on WhatsApp, is sat against a live table map, orders from a QR or a waiter with a handheld. The kitchen sees the ticket instantly. Inventory ticks down. The bill is GST-ready. A no-show from last Friday is already on a reminder cadence — not a name the host vaguely remembers.
Live
Table & ticket state
Host, pass and kitchen see the same ticket
Fewer
86's after the order
Stock and recipes sit behind the menu
Cleaner
GST close
Invoices from the till, not a Sunday spreadsheet
One
WhatsApp number for the house
Bookings and takeaway, not a chef’s personal chat
The shift
From this
To this
What's included
Bookings, waitlist, walk-ins and turns on one floor plan. Covers and turn time are visible to the host, not guessed.
Order, split bill, UPI, card and cash — with GST invoices that match what left the kitchen.
Tickets fire to the right station. Bump when it’s up. No more carbon copies in a wet pocket.
Menu, modifiers and 86's in one place. QR for the table that wants it; handheld for the one that doesn’t.
Bookings, takeaway and ‘is the tandoor still on?’ on a number the restaurant owns — not a chef’s personal chat.
What left the pass should leave the store. 86 alerts, wastage logs, and a count that is not a Sunday project.
Who is on, who called out, who can close. Tied to the till so a shift is not a rumour.
Covers, average ticket, food cost, voids and the dishes that actually make money — the morning after, not the month after.
The same recipes and permissions across kitchens, with each outlet’s till still closing on its own.
Every role connected
Seat from a live map. Know which table is turning. Stop promising a 7:30 that the kitchen cannot fire.
See the ticket. Fire it. Bump it. The grill does not need a meeting.
The night should close on numbers, not a story.
Go-live
Week 1
Floor plan, stations, menu, till and the WhatsApp that currently runs the house.
Week 2
Tables, recipes, tax, staff roles, kitchen stations. Manager PIN on comps.
Week 3
One sitting or one outlet beside the old KOT. Tune ticket routing from real tickets.
Week 4
QR, WhatsApp number and the till on the new layer. Old pads boxed, not burned, until the first Friday holds.
Ideal for
Independent restaurants, cloud kitchens and small groups
Deployment
Cloud, with handhelds and a kitchen display on the floor
Commercials
Scoped per outlet and station — not a per-cover tax
We walk service: reservations, seating, KOT, pass, billing, stores. The first build is the path that currently breaks most often — usually the ticket between floor and kitchen, or stock that only exists in someone’s head.
Reservations, table state and walk-ins share one map so the host is not guessing covers.
Kitchen display replaces the paper KOT. Inventory and recipes sit behind the menu so 86's are real, not a surprise.
Billing, GST, staff roster and owner dashboards close the night without a shoebox of bills. High-stakes comps and voids wait for a manager PIN.
FAQ
Not if it already closes the night well. We sit on the till you trust, or replace the parts that currently lose tickets. The kitchen display and reservations layer are usually the first win.
We go live beside the current KOT for a sitting, then cut over. If the ticket routing is wrong, we see it on real tickets — not a slide.
Yes — on a number the restaurant owns. Bookings, waitlist pings and takeaway. The chef’s personal chat goes back to being personal.
Walk us through one service. You leave with a written plan for tables, tickets and the till — and a clear call on what to keep of the stack you already have.
We’ll tell you if a platform already fits better.
A 30-minute discovery call to research the use case together. You leave with a written plan — we'll tell you if a platform already fits better.
