Skip to main content
eRestro

Use cases by service and venue

Start with how your service moves.

Choose the venue type and service styles closest to your operation. See what eRestro supports today—and which specialist workflows remain outside the product.

Service-style index

Choose how orders enter and move.

A venue label never silently determines configuration. The same venue can run more than one service style, each mapped to a verified or explicitly qualified product claim.
  1. 01

    Dine-in

    Dine-in teams can connect table-aware ordering, waiter context, and kitchen tickets.

  2. 02

    Counter and quick service

    Staff can enter dine-in, takeaway, and delivery orders in eRestro.

  3. 03

    Pickup and takeaway

    Owned pickup and manually managed delivery orders can move through eRestro's order and kitchen flow.

  4. 04

    Delivery-led kitchens

    Owned pickup and manually managed delivery orders can move through eRestro's order and kitchen flow.

Venue-fit index

Choose the closest operating pattern.

Primary fit means the current service loop maps strongly. Qualified fit names the specialist boundary before rollout.
Primary fitQualified fit

primary fit

Direct operating fit

The current service loop maps strongly across the venue's stated service styles.

01

Restaurant operations

Restaurant

Primary fit

Run the dining room as one service.

Connect table-aware ordering, waiter context, kitchen tickets, live checks, and staff-confirmed payments.

Fit note

Fullest fit across dine-in, takeaway, and delivery operations.

Service styles
Dine-in · Counter and quick service · Pickup and takeaway · Delivery-led kitchens
Supported today
  • Table service
  • Browser guest ordering
  • Staff order entry
  • Kitchen display
  • Open checks and billing
  • Reported UPI confirmation
  • Configurable GST
See the restaurant flow
02

Café service

Café

Primary fit

Keep counter and table orders in step.

Move browser and staff-entered orders into one kitchen queue while owners retain live venue visibility.

Fit note

Strong fit for counter, takeaway, and optional table service.

Service styles
Dine-in · Counter and quick service · Pickup and takeaway
Supported today
  • Browser guest ordering
  • Staff order entry
  • Kitchen display
  • Owned pickup and manual delivery
  • Owner order visibility
Explore the café workflow
03

Quick service

QSR

Primary fit

Move counter orders cleanly through the kitchen.

Give staff a fast order-entry path, route confirmed tickets to the kitchen, and keep owners aware of the live queue.

Fit note

Strong fit for counter ordering and kitchen flow; kiosks and customer pickup displays are not included.

Service styles
Counter and quick service · Pickup and takeaway
Supported today
  • Staff order entry
  • Browser guest ordering
  • Kitchen display
  • Owned pickup and manual delivery
  • Owner order visibility
See the QSR flow
04

Everyday bakery orders

Bakery

Primary fit

Bring counter and pickup orders into one queue.

Manage the sellable menu, enter orders, and pass confirmed tickets to the kitchen without claiming bakery production workflows.

Fit note

Core ordering fit; weighted items, production batches, and bakery-specific preorder are not included.

Service styles
Counter and quick service · Pickup and takeaway
Supported today
  • Menu management
  • Staff order entry
  • Kitchen display
  • Owned pickup and manual delivery
  • Owner order visibility
Explore core ordering
05

Bar and pub service

Bar or pub

Primary fit

Keep table service and open checks connected.

Link staff order entry, kitchen tickets, changing checks, and staff-confirmed UPI payments during service.

Fit note

Core ordering fit; age-verification and alcohol-compliance workflows are not included.

Service styles
Dine-in · Counter and quick service
Supported today
  • Table service
  • Staff order entry
  • Kitchen display
  • Open checks and billing
  • Reported UPI confirmation
See the service loop

qualified fit

Core flow with explicit limits

The core ordering flow applies, while specialist workflows remain outside the current product.

06

Qualified cloud-kitchen fit

Cloud kitchen

Qualified fit

Coordinate owned orders at the kitchen pass.

Move venue-owned pickup and manually managed delivery orders into the kitchen display with live owner visibility.

Fit note

Owned pickup and manual-delivery plus KDS only; live aggregator ingestion and multi-brand management are not included.

Service styles
Pickup and takeaway · Delivery-led kitchens
Supported today
  • Owned pickup and manual delivery
  • Staff order entry
  • Kitchen display
  • Owner order visibility
Review the supported flow
07

Independent food-court outlet

Food-court outlet

Qualified fit

Operate one outlet with a clear order queue.

Use core staff ordering, kitchen tickets, and billing for one independent outlet without implying food-court-wide coordination.

Fit note

Independent outlet only; cross-stall carts, operator-wide tenancy, and unified settlement are not included.

Service styles
Counter and quick service · Pickup and takeaway
Supported today
  • Basic ordering and billing
  • Staff order entry
  • Kitchen display
  • Owner order visibility
Review the core workflow
08

Qualified cafeteria fit

Canteen or cafeteria

Qualified fit

Keep basic cafeteria ordering and billing clear.

Use staff order entry, kitchen tickets, and standard billing without claiming employee-benefit or meal-plan automation.

Fit note

Basic ordering and billing only; employee identity, subsidy, entitlement, and meal-plan workflows are not included.

Service styles
Counter and quick service · Pickup and takeaway
Supported today
  • Basic ordering and billing
  • Staff order entry
  • Kitchen display
  • Owner order visibility
Review the basic flow

Rollout decision

Use the label to orient. Use the workflow to decide.

A venue name is a starting point. Validate the exact order, kitchen, billing, and owner handoffs your team will operate.
Discuss your setup
  1. 01

    Choose service styles

    List every service mode the venue runs instead of inferring the workflow from its category.

  2. 02

    Confirm the connected handoffs

    Walk ordering, kitchen work, billing, and owner visibility as one operating sequence.

  3. 03

    Name specialist workflows before rollout

    Treat every qualification as part of scope, especially delivery, compliance, multi-outlet, and specialist production needs.

Next step

Validate one real service flow.

Configure one venue, choose its service styles, and test the handoffs your team will operate before expanding the rollout.

Start freeTalk through your setup