Five seats. Five screens. One live restaurant.

Your waiter's phone is the floor.

Waiters, cashiers, hosts and captains each get a phone app for their job — not one till at the counter that everyone queues for.

The guest already ordered on their phone. Staff should not have to re-type it.

Home shows what needs you now: a table asking for water, a dish that's ready to serve, a table that needs cleaning. You don't hunt through a list. The urgent things come to you.

Tables sit on a live map, grouped by room. Available, occupied, reserved, cleaning — tap one to seat a guest or free it when they leave.

When a guest taps Call waiter, Water, Tissue, Clean table or Bill on their phone, it lands as an alert on yours. Resolve it when you've done it. Nobody shouts across the room.

Orders move on the same screen: confirm, cooking, ready, served, done. Cash or UPI at the table or the counter — the bill is already made.

If a guest needs to log in at the table, you read them a one-hour OTP. No shared password. No paper pad.

1. Home
2. Tables
3. Alerts
4. Orders
5. OTPs

Waiter · home

• WaiterTables, serve, and the calls that come from the QR.
• CashierSee the bill. Take cash or online. Close the order.
• HostThe door and the floor map — who sits where.
• CaptainThe waiter tools, plus a view of the whole team.

• Runs on the phone they already carry.
• Each role sees only their job.
• Guest calls arrive live. No WhatsApp group.
• The kitchen ticket and the waiter screen are the same order.

One screen for the whole day — open to close.

This is the command centre for one restaurant. You start the day, watch the floor, fix the menu, pay staff, and read what last night actually did.

You should not have to ring the captain to find out how the night went.

Open operations and the floor unlocks — QR, kitchen, waiter app. Close it and guests cannot order. The day is a real session, not a guess.

The dashboard is the live room: sales, orders, average bill, how people paid, outlet health. SpiceBot's briefing sits on the same morning screen.

Live orders, kitchen display, table map and printable QR codes are one click apart. You can accept a ticket, reprint a QR, or take a complimentary bill without leaving the desk.

Staff is a roster with real jobs: waiter, cashier, host, captain, kitchen. Attendance, tips and a log of who did what — including which waiter resolved a table request — tied to the same open day.

Menu editor, stock, food rescue, guests, reviews, GST and Razorpay payouts live here too. Surplus can be listed as a donation. Analytics and an AI report sit on the same morning screen. Support is a ticket from the panel, not a WhatsApp to a vendor.

Manager command center

• Command centreSales, orders, health, how people paid — live.
• OperationsOpen the day. Close the day. Attendance sits on that session.
• Live ordersEvery ticket. Accept, reject, invoice. Cash, online, or complimentary.
• Kitchen (KDS)The same tickets the chef sees, from your desk.
• Tables & QRRooms, capacity, status, bulk QR download, table transfer.
• Table actionsWater, tissue, waiter — who asked, who resolved it, how long.
• StaffRoster, attendance, tips, activity. Roles, not one login.
• Menu editorDishes, sizes, add-ons, photos, veg tags, item offers.
• Food rescueList surplus. Track pickups. Not a bin run at close.
• AnalyticsRevenue, peak hours, top dishes. SpiceBot writes the report.
• StockIngredients, recipes, wastage, low-stock alerts.
• CRM & loyaltyWho came back, what they spent, what they earned.
• MoneyGST, service charge, Razorpay account, settlements.
• Reviews & reportsWhat guests said. What SpiceBot thinks it means.
• SupportTickets to us from the panel. Call when it cannot wait.

• Open and close is a product, not a habit.
• QR, kitchen, money and staff share one clock.
• SpiceBot briefs you before the first guest sits.
• GST and UPI are settings, not a plugin.

Every outlet on the same system. Head office on top.

The outlet still runs Eatomatic. Head office sees all of them — one menu, one set of numbers, one place to say yes to a new site.

Outlet two should not mean a second software stack.

The command centre rolls up the network: revenue, orders, outlet health, what sold. You compare site against site on the same yardstick.

The global catalogue is the brand menu. Change a dish once. Outlets get it. Promotions work the same way — one code, every site or the ones you pick.

A new outlet requests to join. You approve or send it back. Broadcasts go to every floor or just one. Support tickets from outlets land on one desk.

Billing can be HQ-pays (one bill for the brand) or each outlet pays its own. Starter, Growth or Scale — ten sites, twenty-five, or no cap.

Guests belong to the brand. Points earned in one outlet work in the others. You do not rebuild CRM per address.

Franchise HQ

• Brand command centreNetwork sales, orders, health, top sites.
• Global catalogueOne menu. Push it to every outlet.
• Global promotionsOne offer. All sites, or the ones you choose.
• BroadcastsA note to every floor, or to one.
• Outlet requestsA new site asks to join. You say yes or no.
• My outletsSearch, sort, health, KYC, orders, ratings.
• Plans & billingHQ pays, or each outlet pays. You pick.
• OrdersLook across the network without logging into each site.
• Support deskOutlet tickets, one queue.
• Brand settingsProfile, terms, who the brand is on paper.

• First restaurant and twentieth restaurant use the same product.
• Menu and offers live at brand level — outlets don't drift.
• One bill at HQ, if you want it that way.
• Loyalty follows the guest, not the pincode.