A browser-based multi-role restaurant ordering and operations system
I built Jemo to connect guest ordering, restaurant staff, kitchen operations and billing in one browser-based workflow.
Hero workflow: A guest scans Table 4 and orders from their phone; the order appears in the manager's action feed and Table 4 becomes active, while the guest tracks Order #55 from their phone.
The problem and product goal
I built Jemo to connect guest ordering, restaurant staff, kitchen operations and billing in one browser-based workflow.
The system connects these roles into a single operational loop: guests scan a table QR code to browse the menu and order from their phones, kitchen staff manage preparation tickets on a dedicated Chef Station display, and managers track table occupancy and settle bills from a central Billing Desk, all running in standard web browsers.
What was built
- Guest QR Ordering & Live Tracking: A browser-based mobile web ordering experience accessed by scanning a table QR code. Guests browse categorized menus, view real-time cart pricing, submit orders, and track preparation progress directly on their phones.
- Manager Billing Desk: A desktop command view displaying table occupancy (vacant vs. running), a live incoming order action feed, KOT printing, and table bill settlement with Cash and UPI payment modes.
- Kitchen Display System (Chef Station): A dedicated high-contrast terminal for kitchen displays and tablets. Organizes orders into chronological tickets with item quantities, modifier notes, and stage toggles (Start Cooking, Mark Ready).
- Menu Management & Cost Inputs: A complete back-office manager for organizing categories, toggling real-time dish availability, and entering per-item recipe making costs to calculate estimated gross profit margins.
- Post-Order Rewards: Spin-to-Win and reward coupons designed to encourage a future visit.
- CA/Accounting CSV Export: CSV export containing bill date, bill number, item breakdown, payment mode, tax and totals.
- Multi-Role Scoped Access: Purpose-built interfaces tailored to distinct restaurant responsibilities: Guest, Waitstaff, Kitchen Chef, Manager, and Owner.
Operations & kitchen lifecycle
Once Table 4 places Order #55, the operational loop moves through the kitchen and floor staff. The kitchen station isolates the preparation workflow with clear tickets and timer cues, while the billing desk maintains table status until final settlement.
The Kitchen Display System keeps preparation tickets in one digital queue, with controls for starting preparation and marking an order ready. Cooks tap “Start Cooking” when preparation begins and “Mark Ready” when the meal is plated. At the desk, the manager can view the live running balance for Table 4 (₹308 for 1x Cold Coffee, 1x Burger combo, and 1x Pizza) and open the settlement modal for settlement via Cash or UPI.
Operations lifecycle: Order #55 is routed to the kitchen Chef Station (left) showing items and preparation status. Once the meal is served, the manager opens the Table 4 bill modal (right) for settlement via Cash or UPI.
Menu management and cost inputs
The Menu Manager stores dish pricing, availability and a making-cost input for each menu item. Jemo uses that cost input to calculate an estimated gross margin.
By recording the making cost of each menu item—such as ₹60.0 for Paneer Tikka or ₹50.0 for a Burger combo—Jemo uses those making-cost inputs in its estimated-profit calculations.
For post-order rewards, the menu system connects directly to promotional features: after placing an order, guests can spin for a surprise discount (such as “FREECOFFEE”) saved to their phone, using Spin-to-Win and reward coupons designed to encourage a future visit.
Menu management and cost inputs: Operators manage dish pricing, categories, and item making costs to track estimated margins (desktop), while post-order rewards provide guest discount spins and reward coupons designed to encourage a future visit (mobile).
How the system connects
A browser-based architecture that coordinates guests, floor staff, kitchen display stations, and billing without local server installation.
Browser Clients
Guest QR / Waiter or Staff / Chef KDS / Billing Desk / Owner
Flask Application Layer
Routing, sessions, ordering, kitchen, billing and restaurant management
SQLAlchemy Data Layer
Orders, tables, menu items, staff, coupons and preferences
Relational Database
Persistent tabular storage (PostgreSQL in production, SQLite in local development)
Role/PIN access
Owner credentials and role-scoped PIN logins for floor waitstaff and kitchen stations
Cost & estimated-margin calculations
Dish making-cost inputs calculate item-level estimated gross margins
Rewards/coupons
Spin-to-Win and reward coupons designed to encourage a future visit
CA/accounting CSV export
CSV export containing bill date, bill number, item breakdown, payment mode, tax and totals
My role and workflow
I worked as the Founder, Software Developer & Product Builder, taking Jemo from product concept through to a deployed, running system.
I defined the product requirements and expected behaviour, translating restaurant operational workflows into product decisions across guest, kitchen, and manager roles. I tested the running system against real restaurant ordering scenarios to verify that table states, ticket queues, and bill calculations matched live shift requirements.
Implementation ran on an AI-assisted workflow with LLMs (Claude and Codex) assisting with code generation, route logic, and debugging. I directed each iteration, decided what product behavior was required, verified the resulting implementation from both guest and operator sides, decided what was ready to ship, and handled deployment and ongoing iteration.
Technical snapshot
- Role
- Founder, Software Developer & Product Builder
- Stack
- Python, Flask, Flask-SQLAlchemy, Jinja2, Tailwind CSS, SQLite / PostgreSQL, Gunicorn
- Hosting
- Linux Cloud VPS, Gunicorn, Nginx reverse proxy
- Architecture
- Multi-role browser-based application (Guest, Waiter/Staff, Kitchen Chef Station, Manager Billing Desk, Owner)
- Key Workflows
- QR Table Ordering, Floor Table Management, Kitchen KDS Queue, Billing & Settlement, Recipe Cost Inputs, CA/Accounting CSV Export
- Status
- Live product with interactive demo cafe.
Technical Architecture Note
For an architectural deep-dive into table session modeling, concurrency control, and zero-app mobile workflows, read the companion build note: Architecting a Multi-Role Restaurant Ordering & Operations Workflow →
Need something like this?
Tell me what you need, your timeline, and what is already in place. Smaller scoped work is welcome too.