Good service starts with a clear view
Restaurant overview
Everything happening on the floor and in the kitchen.
Sales snapshot
Example paid bills over the past seven days
Sample transactions only. Payments are not processed in this demo.
Kitchen activity
Orders waiting and being prepared
Active tables & bills
Orders currently associated with occupied tables
| Table | Area | Guests | Kitchen | Outstanding bill |
|---|
Choose a table, add a meal, send it to the kitchen, mark it ready, and complete a sample payment. Recipe ingredients are deducted when food is sent to the kitchen.
Floor management
Every table at a glance.
Choose a table to open its bill or begin a new order.
Illustrative floor arrangement. A future version can support customizable room layouts and multiple branches.
Touchscreen ordering
New order
Find food, customize items, and send the order to the kitchen.
The menu
Beautifully presented, simple to navigate.
Image credits
Table order
Manage items and the current bill.
Only free a table after guests leave.
For table service, food can be prepared before the customer settles the bill.
Held for payment
These items have not been released to the kitchen or deducted from ingredient stock.
Already sent to kitchen
New items to send
Dine-in sends food to the kitchen immediately; Pay-first keeps it on hold until payment. No physical printer is connected.
Settle the table
Cash is manually counted. MoMo and card are simulated; live payment verification would require a provider integration.
Guest requests awaiting staff 0
Accept customer requests before preparation. Pay-first requests remain held.
Loading guest requests…
Cross-device activity
Shared tickets
Call waiter requests
Connecting…
Kitchen display system
Where every order moves.
Track tickets from arrival to serving.
Tickets are shared across the simulated modules inside this browser only. Multi-device kitchen synchronization, printers, and offline-LAN operation need a real backend and local-network implementation.
Recipe-level inventory
Know what goes into every plate.
Ingredient quantities update when orders are sent to the kitchen.
Ingredient store
Sample quantities and usage, not certified costing data.
| Ingredient | Unit | Available | Low-stock alert | Status |
|---|
Example: adding Jollof & grilled chicken uses rice, chicken, oil and seasoning. Actual recipes must be configured with the restaurant's measured ingredient quantities and portion yields.
Menu items are linked to ingredient recipes; consumption is recorded when an order is sent. A production system would also track purchases, waste, spoilage, staff actions, and stock-count adjustments.
Manager workspace · preview
Make the restaurant yours.
Manage your menu, approve photography, set up dining tables, and control stock.
Customer order requests 0
Review website, QR and tablet requests before kitchen preparation.
Loading guest requests…
Shared restaurant activity
Live customer and waiter tickets from connected devices.
Shared kitchen tickets
Customer assistance 0
Connecting…
Customer feedback
No feedback yet.
Customer requests require staff acceptance. Payments are demonstration-only until a verified provider is integrated.
Today's controls
Your most important daily configuration tools
Recent manager activity
Demo-only changes recorded in this browser
Recorded sales
Illustrative sales register, including demo transactions
| Reference | Table | Payment method | Amount | Recorded |
|---|
Dining tables & sections
Each table retains its seat count. Occupied tables cannot be removed or reserved.
| Table | Dining area | Seats | Current status | Controls |
|---|
Ingredient inventory
Adjust counted quantities and low-stock alerts. Menu recipes draw from this inventory.
| Ingredient | Available | Low-stock threshold | Status | Controls |
|---|
Restaurant identity
Preview how the restaurant identity appears in this browser.
Customer ordering channels
Choose how guests may order. Waiter ordering always remains available.
How it works: Tablet and QR orders enter a shared guest-request inbox. Staff must accept each request before it follows the existing pay-first or dine-in kitchen rules. This is a demonstration: orders, kitchen status and ingredient stock are synchronized for connected staff; payments and receipts are simulated. Production use requires real authentication and a verified payment provider. Manager configuration has no sign-in protection in this demo.