eRestro

Product

Everything you need for QR → kitchen → served

Owner, kitchen, and guest each get a focused surface—so onboarding stays short and your team can concentrate on service instead of juggling disconnected tools.

Preview

Product walkthrough

Visuals below use demo imagery to show layout and rhythm—drop in your own screenshots anytime without changing the page structure.

DemoDemo illustration of a restaurant interior — replace with product screenshot
Illustrative hero — replace with your outlet or admin overview.

Three surfaces, one pipeline

Owner tools, kitchen display, and guest ordering stay visually distinct so your training deck stays short.

DemoDemo illustration of a tablet on a desk — placeholder for owner dashboard

Restaurant owner

  • Menu, categories, and pricing with veg / non-veg cues.
  • Tables and QR codes (PNG) for each table.
  • Live orders and today’s analytics in your timezone.
DemoDemo illustration of a kitchen — placeholder for kitchen display view

Kitchen pass

  • Dedicated KDS URL with a secure token — mount a tablet at the pass.
  • Order statuses from pending through served.
  • Built for noisy kitchens and peak-hour India rush.
DemoDemo illustration of dishes on a table — placeholder for guest menu experience

Guests ordering

  • Scan QR — no app install. Works on mobile data.
  • Cart, notes per line, and clear order confirmation.
  • Takeout landing where you enable it from settings.

End-to-end flow

From first scan to the last plate

The same three beats your floor already runs—connected so guests, runners, and the pass stay aligned.

  1. 01

    Scan & browse

    Guests open your menu in the browser with clear price lines, veg cues, and modifiers that stay attached to the parent dish.

  2. 02

    Confirm to pass

    Orders hit the kitchen as a single ticket—no duplicate chits floating between chat and paper.

  3. 03

    Serve with clarity

    Table-aware labels align runners, billing, and the floor so the last mile matches the first tap.

DemoDemo illustration of a meal spread — placeholder for order journey context
Placeholder scene — swap for timeline or analytics screenshot.

Bento: how it fits together

A quick visual grid you can mirror in sales decks—large canvas + supporting tiles until you have real UI captures.

Demo
Demo illustration of shared plates at a table — swap for dashboard or menu builder screenshot

Primary surface

Use this slot for admin overview, menu editor, or live orders—same frame, swap the asset.

Kitchen display

Large type, steam-proof placement, token rotation.

Demo kitchen scene — swap for kitchen display screenshot

Guest web menu

No install; works on everyday 4G.

Demo spread of dishes — swap for mobile menu screenshot
DemoDemo tablet — placeholder for responsive owner experience
Owner & manager — illustrative device shot.

Web-first, mobile-ready

Owners use the admin on desktop or phone. Guests always use the browser — no install. Kitchen runs on a tablet or small PC at the pass.

  • Responsive admin: check live orders between tables without opening a laptop.
  • Guest link: one URL per table QR—no app store friction.
  • Kitchen: full-screen friendly; readable at arm’s length.

Next step

See it on your floor

Request access, read the guides, or compare plans — then swap these demo shots for your real product captures when you are ready.

Request accessRead guidesView pricing