The order report
What this is for
The detailed sales and performance of orders — the row-level view behind the sales report's totals.
Use it when you need to find specific orders rather than understand a trend.
What's on it
Each order with its number, date, type, table, customer, waiter, status, payment status and total.
Filter by:
- Date range
- Order type — dine-in, delivery, pickup, or any custom type
- Order status and payment status
- Handler — who processed the order
- Waiter — who was assigned the table
Handler and waiter are different
Worth understanding, because it changes what the numbers mean.
- Handler — who actually worked the order in the system.
- Waiter (assigned) — who was looking after that table.
They're the same person often and not always: a manager who takes payment on a table a waiter served appears as handler, while the waiter stays the assigned waiter.
For sales-per-waiter, filter by waiter. For "who did this", filter by handler.
What to use it for
Finding an order. A customer rings about last Tuesday. Filter to the date and find it.
Checking a shift. Filter to a date and a handler to see what one person did across a service.
Sales by waiter. Filter by waiter over a week. Combined with average order value, this is the most concrete upselling conversation you can have — one waiter's average basket against another's, on the same section.
Auditing something odd. An unusual number in the sales report has orders behind it. This is where you find them.
Checking an order type. How is the new drive-through actually doing? Filter to it.
Payment status against order status
Two independent things, and filtering by the wrong one is the most common mistake here.
- Order status tracks the food — placed, preparing, served, completed.
- Payment status tracks the money — billed, payment due, paid.
A Completed order can be unpaid. A Preparing order can be paid. See The order journey.
To find money you're owed, filter by payment status, not order status — or use due payments, which is built for it.
A weekly check worth doing
Filter to the last week and look for:
- Orders still open that should have closed. A table left Running for three days is a table nobody freed.
- Orders with payment due that nobody is chasing.
- Cancelled orders clustered on one shift or one person — then go to cancellations.
- Orders with no waiter on a night you were running sections.
Each of those is a small process failure that's easy to fix while it's small.
Good to know
- Per branch, and follows your operating shifts.
- Filters persist. An unexpectedly empty report is usually a filter left set, not an empty week.
- Deleted orders don't appear. Cancelled ones do — which is exactly why cancelling beats deleting.
- Exports — see Exporting reports.