One channel or many? One log
Channels differ in how the order arrives, not in what it is. The guest who orders from the website, scans the table code, calls, or stands at the till ends up with the same thing: items, quantities, a fulfilment method and a payment method. So every channel must feed one log, where the cashier, the kitchen and the owner see the same orders in the same sequence.
The direct benefit is that an online order appears on the POS screen as if it had been keyed in by hand, prints to the kitchen the same way, and is collected and invoiced by the same logic.
Order statuses: the team's language
The status is what answers "where is my order?" without a phone call. A pending order awaits confirmation; confirmed means sent to the kitchen; preparing means work has started; ready means it awaits pickup or the courier; out for delivery means it has left; completed means it is done; cancelled means it was stopped, with a reason.
More important than the names is the discipline: every status change is logged with its time and who made it, whether the cashier, the kitchen screen or the call-centre agent. That is how the order log becomes a history you can go back to in a complaint or a dispute.
Numbering: a number everyone knows
An order needs two numbers: a permanent one that never repeats, used on the invoice, in reports and in links to other systems, and a short daily one that is called out on the floor. The short number should carry the channel letter, so the cashier knows at a glance that the order came from the website, the phone or the till itself, and it restarts every day so it never reaches numbers that are awkward to call.
Payments, refunds and returns on the order itself
Money must be recorded on the order, not in a side ledger. A payment on collection, an online payment confirmed by the gateway, or a payment at the till at the end of a table session; all of them on the same order. A cancellation after payment records a full refund automatically, and returning a single item records a partial return at its value, so the day's sales and collections stay right without a manual adjustment in the report.
- Never record a payment before it is actually confirmed, especially online payments.
- Tie every refund to its reason and to who made it.
- A partial return deducts the item, not the whole order.
Handover to the kitchen
Confirming the order is the moment it moves to the kitchen: a ticket on the kitchen screen or the section printer, with the items, modifiers, notes and the table number or fulfilment type. If the guest adds a second round on the same table, the second ticket arrives with that round's items only, and nothing earlier is reprinted.
And when the kitchen marks the order ready, the status should return to the cashier and the guest automatically, so nobody needs to shout through the pass.
The metrics worth a daily look
Revenue alone hides problems. Alongside it, watch confirmation time, the gap between an order arriving and being confirmed; preparation time from confirmation to ready; the cancellation rate and where it comes from; and the number of orders per channel. A rising confirmation time in the evening means the live board has no owner at that hour, and a rising cancellation rate from one channel means a problem in that channel, not in the kitchen.
Review these numbers in the end-of-day report per branch and compare them with the previous week. The restaurant that knows why yesterday's order was late is the one that does not repeat the delay today.
