Scanqur collects your table and WhatsApp orders into one live feed, lets you complete or cancel each with a reason, and turns the record into monthly reports: revenue, average order value, completed versus cancelled. Service stays calm; the numbers stay honest.
Grill 45
3 live · 27 completed today
Orders arrive on paper tickets, in chat threads, in shouted requests, and once served, they evaporate. Ask a busy merchant their average order value or how many orders they cancelled last month and the honest answer is a shrug. Not because they don’t care, but because nothing was keeping score.
Nobody has time for bookkeeping between tables. Scanqur’s approach: managing today’s orders, the thing you must do anyway, automatically produces the history and the monthly numbers. Handle the order once, and the record keeps itself.
Incoming orders from table ordering land in a live feed, each tagged with its table. You work through them and mark each completed, or cancel it with a reason (guest left, item unavailable, duplicate). Completed and cancelled orders move to a paginated history, organised by month, without ever cluttering the live view.
Each month’s history is summarised automatically:
When orders live in three places, the busiest twenty minutes of the day is exactly when one gets missed, and that guest remembers.
"We never got the fries" is unanswerable without a trace of what was ordered, when, and what happened to it.
Without revenue, order counts and cancellation numbers per month, pricing and staffing decisions run on gut feel, and gut feel has expensive blind spots.
New orders appear instantly with table tags. Complete them as they go out; the feed only ever shows what still needs attention.
Cancellations require a reason, so your history distinguishes a kitchen 86 from a no-show, the difference matters when you read the report.
Every completed order stays on file, browsable by month, without slowing down the live view. The record is there when a question comes up.
Revenue, average order value and cancellation rate per month, computed for you. Read them in the time it takes to drink an espresso.
Kitchen sees the live feed, managers see history and reports. Scanqur’s team roles keep each screen matched to the job.
Enable table ordering (and WhatsApp ordering if you take pickup orders). Orders start arriving in the Orders page of your dashboard.
A phone at the pass or a tablet by the counter, open on the live feed. During service, this screen is the single source of "what’s still owed".
Delivered to the table, handed over the counter, tap complete. Two seconds of discipline is what makes every downstream number true.
Wrong order, guest left, item unavailable: pick the reason that actually happened. In three months, the pattern in those reasons will tell you something.
Tip: If "item unavailable" dominates your cancellations, the fix is menu discipline: hide 86’d items the moment the kitchen calls them.
Five minutes with last month’s revenue, average order value and cancellation rate. Compare with the month before. Decide one thing to change. Repeat monthly, that loop is the whole discipline.
Close out orders in the moment
Completing orders in a batch at midnight makes the daily rhythm invisible. Real-time completion keeps the feed useful and the timestamps honest.
Watch average order value, not just revenue
Revenue follows footfall; AOV follows your menu and your team. If AOV rises after you added dessert photos, that photo shoot just paid for itself.
Treat cancellation rate as an early alarm
A rate that creeps up usually means a menu that promises what the kitchen can’t deliver. Catch it in the monthly report before guests catch it at the table.
Don’t let “pending” become a graveyard
Anything still live at closing time is either forgotten or unrecorded. End every day with an empty live feed.
Don’t pick cancellation reasons at random
A report built on careless inputs reports nothing. The reason list is short on purpose, take it seriously.
Don’t obsess over daily numbers
Days are noisy: weather, football, a tour bus. Months are signal. Judge changes month over month.
Rachid’s grill house always "felt" busiest on Fridays, yet the till never quite matched the crowd. Orders ran through shouted tickets and a WhatsApp thread; nothing was counted.
After moving ordering to Scanqur, he ran two months on the new workflow: complete on delivery, cancel with a reason, reports on the first of the month.
The report found the leak: Friday’s cancellation rate was triple the weekly average, and the dominant reason was "item unavailable". The kitchen was running out of the mixed grill platter mid-rush, and orders for it were dying at the pass. The revenue-per-order number also showed Fridays trailing quieter weekdays.
The fix cost nothing: prep more platters on Fridays and hide the item the moment stock runs low. A month later, Friday’s cancellation rate had fallen to normal and its average order value led the week, the crowd was finally showing up in the till.
3×
Friday cancellation rate, found and fixed
5 min
monthly report reading time
100%
of orders on file, searchable by month
Order management gets its data from these features upstream.
One code per table, orders arrive tagged in your dashboard, and the floor keeps moving. Full setup guide.
Read articleCustomers build a cart on your menu and send the order to your WhatsApp, structured, pre-filled and commission-free.
Read articleViews, unique visitors, top products and top categories, so menu decisions run on evidence instead of hunches.
Read articleOne live feed during the rush, one honest report when it’s over. Scanqur order management is free to start.
Merchants complete thousands of orders through Scanqur every week.