getting started.
A venue is usually serving guests in about twenty minutes.
Create the venue
Name, address, hours. Then categories and items with prices, prep times and dietary marks.
Print the codes
Add every table, room and counter as a service location. Each gets a QR that already knows where the guest is sitting.
Open for service
Guests scan and order. Tickets reach the pass, requests reach the floor, all visible from a phone.
We enter the first menu with you
Send a photo of the printed menu and we'll get the first venue typed up on the call.
Staff training is one shift
The kitchen screen has two buttons. The floor app has three. That is deliberate.
A person, not a ticket queue
Write to [email protected] during service and you get someone who knows your venue.
during service.
One order crosses three screens.
The guest orders on their own phone, the pass gets the ticket six seconds later, and your dashboard shows both while it happens. Nobody types the same order twice.
She scans and orders in ninety seconds.
The QR opens the menu already knowing the table. Prices, prep times and photos are all there, and there is no app to install.
Any phone camera
The ticket is on the pass before the waiter turns round.
Sorted by how long it has waited, modifiers printed with the item. One tap marks it ready and calls the floor.
Table 12
#A4F2 · 2 covers
Two buttons, one shift to learn
You watch the line from your apron pocket.
Orders in play, kitchen pace and open requests on one screen. Any staff phone can claim a request, wherever it is.
Manager · owner · platform scopes
After service
₹48,260 +12.4%
Tonight, against last Friday.
Orders
96
Average order ₹503, one cancellation.
Closed itself
21:40
No spreadsheet, no end-of-day tally.
the dashboard.
What you run once the venue is live.
One login per person, scoped to what they should see: a waiter gets the floor, a manager gets the venue, an owner gets every venue at once. Everything below is in the product today.
During service
- OverviewRevenue, covers, orders in play and kitchen pace, with the floor laid out room by room.
- OrdersPending through done, waiter assignment, rush and allergy flags, line-level voids.
- Service requestsWater, bill, cutlery and call-a-waiter, each timed and claimed by one person.
- Kitchen displayTickets sorted by how long they have waited; ready in one tap.
What guests can order
- MenuCategories, items, prices, prep times, dietary marks, photos and 3D models.
- Per-venue overridesOverride a price or 86 a dish for one venue without touching the master menu.
- Service locationsTables, rooms, counters and baskets, each with its own QR poster, or the whole sheet as one download.
Who can do what
- TeamManagers, waiters, kitchen and cashiers, invited by email, with PIN access for shared terminals.
- Shift stateOff-shift and no-access states, so a terminal login stops working the moment it should.
- Guest credentialsRotate the codes a venue publishes without reprinting anything else.
After service
- ReportsRevenue, orders, top items and payment mix over 7, 30, 90 days or a year.
- HistoryEvery order and every request, filterable by date, exportable as CSV.
- ReviewsWhat guests wrote, and replies sent from the same screen.
- Audit logWho changed what and when, across the organisation.
More than one venue
- Organisation overviewRevenue, ratings and orders rolled up across venues, then drill into any one console.
- Master menuOne catalogue synced to every venue, with local overrides where they earn it.
- RegionsCountries, states and districts, so a growing group stays organised.
the boring, important part.
Your data stays yours, and stays up.
A service that drops at 8pm on a Friday is worse than no service. These are commitments, and we will put them in the contract if you ask.
Encrypted in transit and at rest
TLS everywhere, including the guest menu. No order or guest record travels in the clear.
Role-based staff accounts
A kitchen login sees tickets. A manager sees takings. Nobody sees more than their job needs.
Export everything, any time
Menu, orders and reporting come out as files you keep. Leaving should be as easy as joining.
The guest menu keeps working
Menus are served statically and cached, so a wobble upstream does not leave a table staring at a spinner.
Twenty-one more answers to the questions operators ask us.
Twenty minutes from now, a table could be ordering.
Bring a photo of your menu to the call. We will have your first venue live before it ends. No card, no commitment.
Not ready to talk? Read the FAQ or see the guest menu
We build custom solutions around how your venue runs, either inside Zervoo or alongside what you already use, down to a guest app in your own brand.
end to end.
ONE SYSTEM · AND CUSTOM WHEN YOU NEED ITNot another menu app. the whole restaurant.
The menu in real 3D and AR, with dish models we make from your photos. Guests order and pay from their own phone.
DashboardEvery order and every number live, with the menu managed from the same screen.
Kitchen displayA screen on the pass tracking every active order, oldest first.
POSWalk-ins, phone orders and settling up at the counter, on the till you already have.
Custom buildsGuest apps and tools built in your brand, inside Zervoo or alongside the systems you already run.