Workflow visualization
Every workflow behind Walid Kitchen at a glance — from the moment a customer walks in or orders online, to the dish leaving the kitchen. Review each flow, then click into the mocks.
User action
System state
Success
In progress
Alert / attention
Terminal
1 · Roles & screens
Three roles, three surfaces, one shared order store. Every screen talks to the same data, so a cashier and the kitchen never see different orders.
🔐Sign inPick a role
→
🧾CashierOrder entry · payments
→
🍳KitchenKitchen display
→
📊AdminReports · stock · menu
🗄️Shared order storelocalStorage → cloud
←
all roles read / write the same orders
2 · Order lifecycle
The happy path end-to-end. A fast-food order should go from customer to served in well under 15 minutes.
🆕Start orderTakeaway · Dine-in · Delivery
→
🧺Add items & modifierstap product · no onions?
→
🍳Send to kitchenappears on KDS instantly
→
💰PaymentCash · M-Pesa · Card
→
⏳Kitchen preparesNEW → PREPARING
→
🛎️Readycall the number
→
🍽️Serveticket cleared · stock drops
3 · Kitchen display status flow
The KDS replaces paper tickets. Kitchen staff "bump" each order forward; overdue orders flash so nothing burns.
🆕NEWtap Accept
→
⏳PREPARINGtap Mark Ready
→
🛎️READYtap Serve
→
✅SERVEDdone for the day
⏰Order idle 3+ mincard flashes red
→
cooks see it and prioritize — no paper, no shouting
4 · Payment flows
Three ways to pay, each ending with a PAID order and a receipt. M-Pesa is the most common in Kenya, so it gets a dedicated STK push flow.
💵 Cash
1Enter amount tendered
↓
2Change calculated
↓
3Complete → PAID
↓
4Print / send receipt
📱 M-Pesa
1Enter phone number
↓
2STK Push sent
↓
3Customer enters PIN
↓
4Confirmation → PAID
↓
5Receipt generated
💳 Card
1Insert / tap card
↓
2Terminal approves
↓
3Approved → PAID
↓
4Receipt generated
5 · Offline-first sync (works without internet)
The killer requirement for a Kenyan restaurant: it must keep selling even when the network drops. Every write is saved locally first, then pushed when internet returns.
✍️Sale / status changewritten locally, always
→
📥Queued "pending-sync"offline badge shows count
→
📶Internet returnsBackground Sync wakes up
→
🔄Push queue + pull updatesorders up · menu changes down
→
conflicts resolve by newest timestamp (UUID + updated_at)
→
✅Cloud in sync
⚠️Offline?No blocked screens — only a badge
→
try the sync badge in the top bar of any screen to simulate it
6 · Inventory via recipes
Menu items are linked to ingredients through recipes, so stock depletes automatically with every sale.
🍔Sale completese.g. Chicken Burger
→
📖Recipe lookup1 bun · 1 fillet · 1 cheese · sauce
→
➖Decrement ingredientsstock recorded locally
→
🔻Below reorder level?checked per ingredient
→
📢Low-stock alertto admin dashboard
7 · Website → POS integration
Online orders land in the exact same order store as counter orders, so the kitchen sees everything on one display.
🌐Customer orders onlinepickup or delivery
→
🗄️Order enters shared storesame queue as the counter
→
🍳Appears on kitchen displaynew-order sound + toast
→
💰Pay at pickupM-Pesa · cash · card
→
🍽️Served — customer tracks live status