The full feature list

Built for four different people, working off one order.

A guest, a cook, a waiter and an owner each need something different from a restaurant’s software. NaRestro is the same order, shown four different ways — nothing gets re-typed, re-shouted, or re-checked by hand between them.

For the guest

A menu that does the ordering, not just the showing.

Everything a diner touches, from the first scan to the closed slip — fast, filterable, and built to be read in their own language.

Scan and order, no app

Every table carries its own QR code. Scanning it opens that table’s menu directly — nothing to install, nothing to sign up for, and nothing that works for the wrong table by mistake.

Order more than once, without losing your place

Close the order tracker to keep browsing and it’s still one tap away — NaRestro recognises the returning device and reopens the same table session, so a second or third round never means starting over.

Menu, Telugu, Hindi, or English

Dish names, descriptions and full dish stories all translate together and switch instantly — a guest reads the whole menu in the language they’re actually comfortable in, not a machine-translated label bolted onto an English menu.

Diet filters, right under search

Veg, egg and non-veg filters sit visible by default, not buried in a settings menu — alongside live search across every dish name, so finding the right plate takes seconds.

Every dish tells its own story

A short story, the handful of ingredients a guest will actually taste, and where the dish comes from — written once by the kitchen’s own content pipeline and always editable by the owner, never guessed live in front of a guest.

Dish stories, read aloud

Tap Listen and hear the story narrated in a real voice, in the guest’s own language — pre-rendered ahead of time, so it plays instantly and costs nothing per guest, every single time it’s played.

Tap an ingredient, find what else has it

Curious what else on the menu uses tamarind, or paneer, or basil? Tap the word in “What’s in it” and every other live dish that shares it appears right there — each one opening its own full sheet.

“Our Suggestion” pairings that actually open

A dish page can recommend what goes with it — tap the pairing to see the full dish, or add it straight to the slip with the same confirming animation as every other add, so it’s never a silent tap into the void.

Nutrition, expanded, not buried

Estimated calories, protein, carbs and fat open by default in their own accented panel — clearly marked as estimates, one tap from collapsing again for a guest who’d rather not see them.

A carousel the owner actually controls

The banner at the top of the menu is not decoration — the owner searches any dish, and NaRestro drafts a slide from its real name, photo and price in seconds, ready to edit and publish.

Browse by photo, then keep browsing without scrolling back

Thirty-plus sections shown as two rows of real dish photography up top — and once you’ve scrolled into the full list, a compact version of the same bar docks to the top of the screen, so switching sections never means scrolling back to find it.

Watch the kitchen work, in real time

Once an order is placed, its status moves with the kitchen — accepted, preparing, ready — without a refresh, and the tracker is always one tap away even after it’s closed.

Call the waiter, request water, right from the table

A guest’s request goes straight to the floor the instant it’s sent — not shouted across a dining room, and not left waiting for someone to notice a raised hand.

For the kitchen

A pass that never loses a ticket.

Built around how an actual kitchen calls a dish — not a generic order queue borrowed from retail.

Tickets appear the instant they’re placed

The kitchen display updates live over a persistent connection — no printer to jam, no runner to relay an order by memory, no manual refresh standing between a guest’s tap and the pass.

Filter by station

A grill station doesn’t need to see dessert tickets. Station filters keep each screen showing only what that part of the kitchen actually cooks.

One tap through the whole lifecycle

Accept, prepare, mark ready, mark served — each stage is one tap, matching how a real kitchen calls a dish rather than a generic order-status dropdown.

Recall, without losing the ticket

A busy pass means a wrong tap happens. Recall puts a served ticket straight back where it belongs — without deleting it, re-entering it, or losing track of what the table actually ordered.

A chime that actually plays

Browsers silently block audio that isn’t triggered by a real tap — NaRestro’s kitchen chime unlocks itself on the very first touch of the screen each shift, so a new ticket is never missed because a phone’s autoplay policy swallowed the sound.

Reject with a reason

An 86’d dish doesn’t just vanish from an order — rejecting it tells the guest why, so the slip stays honest about what’s actually coming.

For waiters & the floor

The floor finds out the moment food is ready.

No more staring at the pass, no more guessing whose table just got bumped.

The waiter knows before the guest waves

The moment the kitchen marks a plate ready, the assigned waiter’s app buzzes and chimes — with the table and dish, so food leaves the pass while it’s still hot, not whenever someone happens to look over.

Your tables, or every open one

A waiter sees the tables assigned to them, plus anything currently unassigned — so nothing sits waiting just because it wasn’t formally handed to anyone yet.

A clock that tells you what’s urgent

Ready tickets are marked calm, warm or hot depending on how long they’ve been waiting — a glance at the queue tells a waiter what to run next, not just what’s oldest.

Guest requests land on the right phone

A call for the waiter or a request for water is routed straight to the floor app — not lost in a dining room’s noise, and not dependent on eye contact across the room.

For owners & admin

One desk for the whole restaurant.

Everything above is configured, written, and watched from here — in the same calm design the guest sees, not a spreadsheet wearing a dashboard’s clothes.

One dashboard, one visual language

The admin console is built in the same calm, photo-forward design as the guest menu — laid out as a bento grid, not a generic back-office table of rows nobody enjoys using.

Full control of the menu

Categories, dishes, pricing, availability and dietary tags — changed here, live on every guest’s phone immediately, with no separate publishing step to forget.

Printable table QR codes

Every table gets its own QR code tied to a real, unguessable token — generated from the floor plan, and NaRestro warns explicitly if a code still points at a local address before it goes anywhere near a printer.

Staff roles that actually gate access

Admin, kitchen and waiter accounts see only what their role needs — enforced by the session on the server, never by which buttons happen to be hidden on a screen.

A promo carousel you can build in a minute

Search a dish, and NaRestro drafts the whole carousel slide from its real name, photo and current price — edit the headline, the button, and where it links, then publish. Up to six slides, reordered by drag.

Dish content, generated once, owned forever

A single pipeline authors each dish’s story, its key ingredients, its pairing suggestion and its translations — written once, stored, and always editable by the owner. It never calls out to an AI model while a guest is waiting, and it never quietly regenerates something a human already corrected.

House-style photography, honestly labelled

Dishes without their own photograph get one generated to match the restaurant’s real props, plating and lighting — and the guest menu always says so. A real kitchen photograph, once uploaded, is never overwritten by a generated one.

A real billing counter

A dedicated checkout screen for the till — built for a cashier working a real shift, not repurposed from the admin order list.

Integrations, honestly

A roadmap of what NaRestro connects to — POS, payments, delivery aggregators — shown as exactly that: a roadmap. Nothing on this page claims to be live until it actually is.

All of it, running one real restaurant.