← All Build Notes
Jemo System Note Operations Architecture

Architecting a Multi-Role Restaurant Ordering & Operations Workflow

How Jemo coordinates guest mobile QR sessions, kitchen display tickets, and desktop billing into a unified, browser-based operations loop.

1. The Problem: Operational Disconnect in Food Service

Many digital restaurant systems treat ordering as an isolated e-commerce cart. A guest scans a QR code, pays upfront through a gateway, and the order is printed out on paper slips. However, in typical dine-in hospitality, service does not follow a linear checkout funnel:

  • Guests frequently place an initial order, then order additional drinks, sides, or desserts later during their visit (a running table tab).
  • Kitchen staff operate in a fast-paced environment where tapping small mobile screens is impractical; they need high-contrast, large-format station displays organized clearly by queue sequence.
  • Managers must track which tables are physically occupied versus vacant, monitor preparation progress, print Kitchen Order Tickets (KOT) when needed, and handle payments at final settlement via Cash or UPI.
  • Forcing guests to download a native mobile app or complete mandatory account sign-up before viewing a menu creates immediate friction right at the table.

The core challenge in building Jemo was connecting four distinct human roles—Guest, Kitchen Chef, Floor Manager, and Restaurant Owner—into a synchronized browser-based workflow without app installations or hardware vendor locks.

2. Architecture: Single Source of Truth Across Four Scoped Roles

Instead of building separate standalone applications for guests, staff, and management, Jemo models the restaurant floor around a shared relational concept: the Table Session.

A table session begins when an order is placed on a specific table number (e.g. Table 4). Subsequent actions attach to that session until settlement:

  • Guest Interface (Mobile Web): Scoped to the specific table session accessed via the physical QR code. The interface runs entirely in standard mobile browsers without an app install or login wall, maintaining cart state, displaying dish availability, and providing order tracking (Placed → Cooking → Served).
  • Kitchen Display System (Chef Station): A dedicated high-contrast, touch-optimized web interface designed for kitchen screens or tablets. It presents incoming tickets chronologically with item quantities, modifier notes, and stage toggles (“Start Cooking” and “Mark Ready”).
  • Manager Billing Desk: A desktop command console that displays table occupancy (vacant vs. running), a live order action feed, KOT printing, and bill settlement with Cash and UPI payment modes.
  • Owner Management Desk: An administrative area for adjusting menu categories, toggling dish availability, entering per-item recipe making costs to calculate estimated gross margins, and generating CA/accounting CSV exports.

3. Implementation Considerations: Table Session State & Concurrency

Designing this workflow required handling several practical operational details:

Additive Orders vs. New Bills: When guests at Table 4 order additional items mid-meal, the system avoids generating a disconnected second bill. Instead, additional line items are added to the existing active table session, routing ticket updates to the kitchen while updating the manager’s cumulative running total.

Network Resiliency on Mobile Wi-Fi: Restaurant dining areas often have uneven Wi-Fi coverage. The guest interface was designed to keep cart interactions responsive client-side, while order submissions are structured to avoid duplicate ticket generation if network latency causes a repeated tap.

Menu Availability Updates: When a dish runs out during service, staff can toggle its availability in the menu manager. The updated status reflects across customer-facing menus and the ordering workflow so guests are not ordering unavailable items.

4. Production Lessons & Trade-offs

Building and operating Jemo highlighted several key design trade-offs:

  • Web vs. Native App: Using standard browser technology eliminated app-store dependencies and customer download barriers. A guest can scan the table QR code and proceed directly to the menu.
  • Pre-payment vs. Table Settlement: Demanding upfront digital payment per item disrupts dine-in dining customs and creates friction for split bills or cash customers. Supporting running tabs settled at the desk matches real hospitality operations far more effectively than rigid checkout funnels.
  • Post-Order Retention: Interactive post-checkout reward components (such as Spin-to-Win discount coupons) were incorporated into the bill tracking experience to encourage repeat visits.

Key Architecture Takeaway

Operational software succeeds when data modeling reflects the physical floor reality. By organizing Jemo around persistent table sessions rather than isolated transactional carts, it keeps multiple restaurant roles working from the same operational state.

Need a multi-role web application or operations system?

If your business requires synchronized workflows between customers, staff, and management, let’s discuss how to architect it cleanly.