Walk-through
What the guest, waiter, kitchen, cashier, owner, and operational agent each do, and how the same restaurant record connects them.
The owner adds business, tax, service, menu, table, floor, staff, and payment details. A printed menu can be imported on-device, or sent to an optional configured AI reader for difficult layouts. The team reviews every item, creates tables or other service zones, and exports the QR assets used at the venue.
A guest scans with the phone camera and reaches the correct table session without an app or account. They can browse dietary context, select variants, add notes, and order in rounds. Staff can use the POS or waiter screen for dine-in, counter, takeaway, delivery, room, or drive-in orders.
The KDS shows incoming tickets with the service context, notes, dietary markers, elapsed time, and station or course information. Cooks move tickets through preparation states, adjust ETA, hold or fire courses, and mark unavailable dishes sold out. Supported KDS actions can queue during a short network interruption and replay after reconnection.
Waiters see occupied tables, elapsed seating time, running totals, and service requests. They can acknowledge calls, add a new kitchen round, move a session to another table, merge parties, and hand ready items to the correct table or pickup token while role checks protect owner and cashier controls.
The server rebuilds totals from trusted menu prices and produces a restaurant-scoped bill with GST, discounts, tips, service charge, and statutory business details. Guests can open an amount-filled UPI intent or pay by cash; staff verification or a signature-verified Razorpay webhook records settlement. A WhatsApp deep link can share the invoice when configured, without pretending that opening UPI alone proves payment.
The cashier reconciles float, cash movement, expenses, denominations, and variance. Owners review sales, taxes, payment mix, menu performance, stock, feedback, and staff activity. The Owner Ops agent can turn those records into findings and approval-safe actions; franchise operators can compare authorized outlets without weakening tenant isolation.
Tenant-scoped APIs connect the live floor, KDS, POS, payments, inventory movements, customer records, reports, and approval history. The same source data supports daily operations and later reconciliation.
Core browser workflows run on ordinary phones, tablets, and laptops. Thermal printers and payment or delivery providers require supported hardware, credentials, and real venue validation before launch.