One connected service loop
Follow every order from entry to close.
This illustrative record follows one dine-in service. Other service modes are configured per venue.
Illustrative product demo · Illustrative venue · T7 · Order #17
Connected service loop
Guest, kitchen, open check, and owner states advance as one bounded sequence. Current state: Payment confirmed by staff.
Live route
Payment confirmed by staff
Guest
Paneer Tikka · T7
Complete
Kitchen
Order #17
Complete
Open check
3 → 4 items
Complete
Owner
Staff confirmation
Complete
UPI confirmed by staff.
Chapter 01
Capture the service mode you actually run
Guest browser ordering and staff entry feed the same operating flow. The example below is a dine-in illustration; takeaway and delivery remain venue-configured workflows.
Same illustrative order · Illustrative venue · T7 · Order #17
Product state
Guest order entry
The complete static product state is loading. Essential workflow labels remain available without motion.
- Dine-in
- Enable only the service modes your venue operates.
- Counter and quick service
- Enable only the service modes your venue operates.
- Pickup and takeaway
- Enable only the service modes your venue operates.
- Delivery-led kitchens
- Venue-managed delivery; live aggregator ingestion is not part of this flow.
Chapter 02
Give the kitchen one accepted queue
Confirmed orders become live kitchen tickets. Staff acceptance is an explicit state change, not an invisible handoff.
Same illustrative order · Illustrative venue · T7 · Order #17
Product state
Kitchen acceptance
The complete static product state is loading. Essential workflow labels remain available without motion.
Chapter 03
Keep additions on one open check
New items join the active guest session while item count and total update together. The illustrative check moves from three items at ₹577 to four items at ₹726.
Same illustrative order · Illustrative venue · T7 · Order #17
Product state
Open check update
The complete static product state is loading. Essential workflow labels remain available without motion.
Teams can add orders to an active guest session and keep one bill up to date.
Chapter 04
Keep the check honest through payment
A guest-reported UPI payment stays pending until staff checks the venue account and confirms it. eRestro does not imply automatic bank reconciliation.
Same illustrative order · Illustrative venue · T7 · Order #17
Product state
Billing and payment confirmation
The complete static product state is loading. Essential workflow labels remain available without motion.
Guests can report a UPI payment; staff confirm it after checking the venue's payment account.
Chapter 05
Let the owner see operational state
Current orders, unsettled work, and confirmed value remain visible in the venue admin as the service advances.
Same illustrative order · Illustrative venue · T7 · Order #17
Product state
Owner service overview
The complete static product state is loading. Essential workflow labels remain available without motion.
Capability index
Configure the operation around the service loop.
- 01
Menu management
Owners can manage menu sections, items, options, and availability.
- 02
Inventory management
Owners can track stock items, purchases, and inventory movements.
- 03
Staff access controls
Owners can assign staff roles and permissions for venue operations.
- 04
Operational reporting
Owners can review sales and order reporting for their venue.
- 05
Configurable GST
Venues can configure GST and receipt details, subject to validation by their accountant.
Venue fit
The core loop, adapted to each venue.
Primary fit
Restaurants, cafés, QSRs, bakeries, and bars or pubs map directly to the core service loop.
Qualified fit
Cloud kitchens, food-court outlets, and cafeterias use a supported subset with specialist limits named before rollout.
Setup
Start with one real service flow.
Configure a venue, choose its service modes, prepare the menu, and validate the workflow your team will operate.
Start free