Online ordering
Guests order and follow their food from the table
Guests scan the code on their table, order from your live menu and see the order move from received to served. It arrives in the POS like any other order, so nobody re-types it.
QR table ordering is available today. Pickup and delivery checkout on your own website is planned and not built yet. The menu shown is sample data.
Table 12 · Thamel
Himalayan Kitchen
Chicken Momo
Steamed, 10 pcs · tomato achar
Rs 320
1Jhol Momo
In sesame-tomato broth
Rs 360
Dal Bhat Set
Seasonal tarkari, pickle, papad
Rs 450
Masala Chiya
Milk tea, cardamom, clove
Rs 90
- Sekuwa is 86’d tonight, so it isn’t listed.
Pay at the counter when you leave
Meanwhile, at the pass
Place the order on the phone.
Submit requests
Idempotency-Key: qr-order-7f3a91c2
One key per basket. Tap Place order two or three times, like a guest on bad Wi-Fi.
Where it works: Guest's phone
Walk the whole restaurantEvery table has its own code
Each table gets its own QR code. An order placed from it arrives with the table number already attached, so the runner knows where it goes and the bill goes on the right tab. More about QR table ordering.
- 1The guest menu is your POS menu. Change a price once and it’s changed everywhere.
- 2Guests can call a waiter, ask for water or ask for the bill from the same screen.
- 3Guests pay at the counter by default, the same as any table.
Floor · table codes
Example tokens- T12 seats
/order/Xq3v…a41f
- T44 seats
/order/k9Tz…9c02
- T76 seats
/order/Lb0R…e77b
- T124 seats
/order/m2Pw…31d0
- Patio 22 seats
/order/Yd1F…b5e9
- Bar 31 seat
/order/hN4c…0f6a
When a dish sells out
Marking a dish unavailable hides it on the POS and the QR menu. A guest who still has an older copy of the menu open can’t order it, because the server checks every item when the order is sent.
86 · Chicken Sekuwa
Illustrative data- 19:02ManagerMarks Chicken Sekuwa unavailable
- 19:02POSThe till refuses it: it can’t be rung
- 19:05New guest, T4Opens the menu; Sekuwa isn’t on it
- 19:06Guest, T9Menu opened at 18:55 · taps Sekuwa · submits
- 19:06ServerRefuses the line: item unavailable. Nothing reaches the kitchen.
Today a guest menu that is already open doesn’t update itself. The server refuses the order instead. Pushing the change to open screens, and 86’ing automatically when stock runs out, are on the roadmap.
Pickup and delivery from your own website (planned)
Pickup and delivery checkout on your restaurant’s own website is not built yet. When it is, it will use the same menu, prices and order handling as the POS and QR table ordering.
The reason is commission. Nepali operators have reported aggregator commissions of roughly 18 to 22% per order (a 2022 operator quote, not a current rate card). Orders through your own site are designed to carry no per-order commission.
yourrestaurant.com/order
PlannedPickup
Ready in ~20 min
Delivery
Your own riders, your zone
- 01Choose pickup or delivery
- 02Same menu, same prices
- 03Checkout
- 04Into the POS & kitchen
Commission on a Rs 1,500 order through your own site
Rs 0
How it connects
Where a guest’s order goes
A QR order is not a message a cashier copies into the till. It is an order, with a table, a kitchen ticket, a payment and a place in the reports.
Feeds in
Online ordering
Takes the guest’s basket, checks every line against live availability, creates one order per idempotency key.
Online and QR ordering features
Partial means it works today with the limit stated. Planned means it is not built yet.
- Available
- Available
- Partial
- Partial
- Planned
- Planned
QR table ordering
AvailablePer-table codes; orders arrive tagged with the table.
Double-tap safe
AvailableOne idempotency key per basket, so retries return the first order.
Order status for the guest
PartialReceived → preparing → ready → served. Refreshed by polling, not pushed.
Table requests
AvailableCall waiter, water, bill or assistance, straight to staff screens.
Availability
PartialUnavailable items filtered on load and refused on submit. Manual flag; not per branch.
Shared calculation
AvailableThe same totals function as the POS, so the guest sees what the till charges.
Pickup & delivery checkout
PlannedWeb checkout on your own site, on the POS order pipeline.
Pay from the phone
PartialKhalti, eSewa or Stripe checkout with your own merchant account; not yet tested against live accounts. Otherwise guests pay at the counter.
Kiosk
PlannedSelf-order mode of the same public flow.
Aggregator orders
PlannedFoodmandu, Pathao Food and others where public APIs exist, with a manual entry lane where they don’t.
Live updates to guest screens
PlannedStatus and availability pushed to open guest screens instead of polled.
Automatic sold-out
PlannedMark a dish unavailable when stock can no longer cover a portion.
Online ordering questions
Can guests order pickup or delivery from my website today?
Do guests pay from their phone?
What happens if a guest taps “Place order” three times?
Does the guest see status changes instantly?
Try the demo
A sample restaurant in your browser. Take an order, send it to the kitchen, mark it ready and take payment. No account needed.