Restaurant OS
Bookings in the same place as everything else
A reservation in a notebook, a reservation on WhatsApp and a reservation from a portal are three systems that disagree with each other on a Saturday night. One list, attached to your actual tables, does not.
Guests book from the page they are already on
The same QR surface that shows the menu takes a reservation, so a guest who scanned to look at the menu can book for next week without finding a phone number.
- Guest-facing reservation form on the menu page
- Bookings visible against your table list
- Reservation ties into the same customer record as orders
Why it matters that it is one system
Because reservations and orders share a customer record, a booking from a regular is recognisably a regular. That is not possible when the booking lives in a separate portal.
Common questions
- Can guests cancel or change a booking?
- Reservations are managed from the dashboard today. Tell us how your floor handles changes and we will be straight about whether the current flow fits.
- Does it integrate with third-party booking portals?
- Not currently. Bookings come through your own QR page.
The rest of the system
QR menu & ordering
Guests scan, browse a live menu with photos, and order from the table. Orders land in the kitchen without a waiter writing anything down.
Kitchen display
Orders arrive on a kitchen screen the moment they are placed, in sequence, with what is preparing and what is ready visible to everyone.
Billing & invoices
Generate the bill from the order that already exists, apply offers and combos, and produce a proper invoice without re-keying anything.
Customer CRM
Every order builds a customer record: what they ordered, how often they visit, what they spend. Loyalty without a punch card.
Inventory
Track stock against what actually sold, see what is running out before service does, and stop selling what you cannot make.
Put this in your restaurant this week.
₹999 a month. No setup fee, no per-terminal licence, no annual contract.