Restaurant operating system
Six ways in. One way through.
A diner scans the code on the table. A waiter taps it into a phone. A kiosk takes it at the counter. Zomato drops one in. From that point on they are the same object, on the same rail — and the restaurant only has one of everything to look at.
Channels in
Table QR Kiosk Waiter app Counter Zomato / Swiggy Your website- Order One queue, whatever the channel. Items, add-ons, notes and the table it belongs to. OrdersMenuTables
- Kitchen The ticket appears on the kitchen screen the instant it is accepted. Stock is drawn down from the recipe. KDSInventory
- Ready The floor is told, the diner is told. Dine-in goes to a waiter; delivery goes to a rider. Waiter appDeliveryWhatsApp
- Bill GST computed on the post-discount value. Split it, part-pay it, settle it in cash, card or UPI. BillingCustomersLoyalty
- Analytics Every settled bill lands in the day's numbers — by item, channel, table and hour. AnalyticsExpenses
One database·one order object·nothing to reconcile
See which module owns what
Back office · the whole rail on one dashboard
The rail is one thing. You hold seven.
Not seven products — the same orders, menu and stock, rendered for whoever is holding the device. Every one of them writes back to the same database.
Twenty-two modules, six categories.
Twenty-one are licensable — switch on what the restaurant runs today and the rest waits behind the same login. Every one has its own page.
Core
Order ManagementEvery channel, one queue Menu ManagementItems, add-ons, availability Billing & InvoicingGST bills, splits, receipts Table ManagementLive floor, status, moves QR Self-OrderDiners order from phone InventoryStock that deducts itselfOperations
Kitchen Display (KDS)Live tickets, no refresh ReservationsBookings, slots, auto-seat SuppliersPurchase orders and GRN DeliveryRiders, tracking, settlement AnalyticsRevenue, items, occupancy Customer-Facing DisplaySecond screen at counter ExpensesDaily spend, categories, receiptsStaff
Staff ProfilesPeople, roles, permissions Shifts & AttendanceRosters, clock-in, leave Waiter AppTake orders at table PayrollWages, advances, payoutsCRM & Growth
Customers (CRM)Profiles, history, spend Loyalty & OffersPoints, tiers, offers, referralsNotifications
WhatsApp NotificationsYour own number, automaticThe kitchen finds out immediately.
Of the five stages, this is the one that decides whether the rest of the evening goes well. Tickets are pushed over a WebSocket the moment an order is accepted — there is no refresh button on the kitchen screen because there is nothing to refresh.
- Tickets arrive by live push, not polling — the board is never stale
- Cards tint green to amber to red as the clock runs on each ticket
- Section filters: main kitchen, tandoor, desserts, bar
- Order-level and item-level notes printed on the ticket itself
- One tap to bump; the waiter's phone is told the same second
- Stock comes off the recipe on the same event, not at end of day
Kitchen display · live board
A restaurant system is a money system.
Which is why these are constraints the build is held to, not features we are selling.
- Dine-in floors Tables, sections, waiters and a kitchen that has to keep up. The floor plan is live, table moves and merges are a drag, and the bill knows which table it came from — including the one that was split three ways at the end.
- Cloud kitchens No floor, and orders from four places at once. Aggregator orders, your own website, phone orders and the counter land in one queue, fire to one board, and settle on one set of numbers.
- Cafés & counters Speed at the till. A kiosk that takes the order, a customer display that shows the bill as it's rung up, UPI settlement, and a thermal receipt — without a waiter in the loop at all.
- Chains One PostgreSQL schema per restaurant. Menu, orders, staff and bills live in their own schema. There is no shared table to leak across and no tenant id to forget in a WHERE clause.
- Everyone GST-ready billing, WhatsApp from your own number, and it is live today. Tax on the post-discount taxable value, split bills, part payments, round-off held on the bill, ESC/POS receipts — running at app.tadkatech.in on a Mumbai VPS, with a staging environment on a nightly PII-scrubbed clone of production.
See it running on your menu.
We set the restaurant up with you — menu, tables, staff and printers — rather than handing over a login and wishing you luck.