5 POS metrics every UK restaurant owner should track live
Five numbers, watched live during service, will tell you most of what you need to know about the business.
Most POS reports never get read. A handful of live numbers, though, will tell you almost everything about how a shift is going while you can still change it.
The five that matter
- Net revenue: are you actually growing?
- Average order value: is upselling working?
- Items per order: are guests adding extras?
- Top & bottom sellers: what to push, what to cut
- Refunds: the early warning that something's wrong
Act while it still matters
By the time a weekly report lands, the shift it describes is over. The same numbers on a live dashboard let you nudge a special, re-stock a runaway seller or step in on a spike of refunds during the same service.
- ✓Net revenue and AOV, per shift
- ✓Your three best and worst sellers
- ✓Any refund spike, the moment it starts
What good looks like, number by number
Net revenue is only useful against a baseline: same day last week, same shift. A Saturday that’s 12% down at 8pm is a problem you can still work on. By Monday all you can do is read about it.
Average order value responds quickly to changes in how you sell. QR menus that show photos of the dishes you want to sell, staff prompted on one upsell line, desserts offered before the table asks for the bill. Each shows up in AOV within days. If AOV rises when a particular person is on shift, you’ve found your trainer.
Items per order tells you whether growth is real or just footfall. Covers up with items flat means you’re working harder for the same money, because the extra revenue is all coming through the door rather than off the menu.
Top and bottom sellers earn their place weekly: push the winners onto the specials board and the QR menu’s first screen, and give the bottom three one honest chance (rename, re-photo, re-price) before they go. A shorter menu is faster prep and fewer errors.
Refunds are the earliest warning you get. One refund on its own means little, but three in an hour usually points at something specific, like a dish going out wrong or a till mischarge. The number is only useful if you see it during the shift.
The five-minute Monday review
The live view is for running the shift. Once a week, look at the same five numbers over a longer window: is revenue growth coming from covers or from AOV? Did the new special crack the top five or just cannibalise the old one? Are refunds clustering on one day, and who was on? Twenty minutes a month of this beats any quarterly report, because you’ll act on it the same week.
“The point of a live number is that you can still do something about it during the shift.”
All five live on Servio’s owner dashboard in real time, per shift, on your phone. It’s included on Growth, no report-builder required. If you’re still choosing a system, our cost guide explains why analytics shouldn’t cost anything extra.
Three numbers you can safely ignore
Part of watching the right numbers is refusing the wrong ones. Total lifetime sales looks nice but answers no question you actually face on a shift. Social followers matter to your marketing, but they don’t belong on the operational dashboard. And daily covers on its own is easy to misread: covers up with items-per-order down means you got busier without making any more money. Every number on your screen should pass one test: if this moves, do I know what I’d do about it? If the answer is no, it doesn’t need to be on the screen, and it’s taking attention away from the five that do.
This is also the honest reason analytics belongs inside the POS rather than bolted on. Numbers you have to export, reconcile and format get looked at monthly. Numbers that are simply there, on the same screen that runs the till and updated live, get looked at hourly. Checking them has to take no effort at all, or it stops happening.
Common questions
Which POS numbers matter during service?
Net revenue, order count, average ticket, top sellers and kitchen ticket age. Those five tell you whether the floor is busy, whether tickets are stalling, and what to push or 86.
Do I need a separate BI tool for this?
Not for day-to-day service. Owner analytics inside the POS should show live takings and ticket health without exporting a spreadsheet mid-shift.
How often should owners check the dashboard?
Glance at the open of service, after the first rush, and before close. The point is fast decisions, not a nightly report that arrives too late to help.