The QR order lifecycle and what guests see

Each status, who changes it and what the guest sees — no surprises.

The golden rule: accepting an order = one paid sale in the POS. The platform only stores and forwards; it never accepts or rejects by itself.

1Submitted
The platform validated, priced and stored it. Guest: “Sent — waiting to reach the restaurant”.
2Delivered
The POS stored it locally. Guest: “At the cashier — waiting for confirmation”.
3Accepted
“Accept” in the POS creates one paid sale at the current POS prices, and the expected time = the longest item in the order.
QR table orders at the cashier: new, in the kitchen, ready, served — accept, accept & print, or reject · Arabic interface
4Preparing → ready → served
Staff update them with the main button in the table-orders window and the guest sees each step. “+5′ / −5′” adjust the time and the guest sees “time updated”.
An order being prepared: the main button “Ready”, with its invoice number · Arabic interface
5Rejected
Only before acceptance, with a reason shown to the guest. A rejected order never counts in the bill.
6Cancelling after acceptance = a return
An accepted order is a sale whose invoice never changes; removing an item is a return from “More → Remove item (return)”, and adding items creates a supplementary order with its own invoice.
The guest is never told “accepted” before the POS actually saved the sale.
“More” after acceptance: ±5′, add items, remove item (return), print the invoice or for the kitchen, finish · Arabic interface

1Submitted