How real-time EPOS data sharpens restaurant decisions

General information for UK hospitality operators, not legal advice. If something here is wrong or out of date, the editorial policy explains how to report it.

A bearded shop assistant serves a customer paying by phone at a white tablet till.

Real-time EPOS data turns till transactions into hourly signals on sales, labour and stock that managers can act on during the shift, not the next day.

What does EPOS data actually tell a manager beyond the day's takings? Used properly, real-time epos data turns individual till transactions into hour-by-hour signals on sales, labour and stock that a manager can act on before the shift ends, rather than reading about the problem the next morning in a printout nobody has time to study.

Most venues already run an EPOS till. The question is whether the data it generates sits inside the till, only visible to whoever is standing next to it, or whether it feeds a dashboard that anyone with the right access can check from a phone or office screen. That distinction is the whole difference between EPOS as a payment terminal and EPOS as a management tool.

What real-time epos data actually shows you

At a basic level, real-time epos data gives a manager three things a Z-read at close of play cannot: a live revenue figure that updates through the session, a breakdown by hour so patterns can be seen while they are still happening, and a per-item view of what is actually selling. None of this requires waiting for the till to be cashed up. A manager checking a dashboard at 2pm can see that the lunch trade is running twenty percent behind a normal Tuesday, and can decide there and then whether to send a team member home early rather than carrying the labour cost through a quiet afternoon.

The value is not the data itself but the speed at which it becomes visible. A sales figure that only surfaces the following morning has already cost the business whatever decision should have been made the day before. This is the gap that a proper EPOS system closes, by pushing sales and item-level data out of the till and into a shared view that managers can act on while the shift is still running.

Matching staffing to the pattern, not the guess

Rotas are usually built a week or more ahead, based on a manager's sense of how busy a shift is likely to be. Live sales data replaces that guesswork with an actual hourly pattern: which hours consistently run hot, which run quiet, and how that varies by day of the week. Over a few weeks this becomes a reliable staffing template rather than an assumption carried over from the previous manager. Getting this wrong in either direction is expensive: overstaff a quiet Tuesday afternoon and labour cost eats the session's margin, understaff a Friday evening rush and service slips along with the average spend per head as customers wait too long to order a second round.

Staffing decisions made from sales data still have to sit inside the same rules that govern any shift pattern, including the daily and weekly limits set out in the Working Time Regulations 1998, such as the 48-hour average working week and the requirement for adequate rest breaks. A dashboard that suggests calling someone in for an extra shift is only useful if that call also checks the hours that person has already worked that week.

The link between sales data and staffing only works if the labour side of the ledger is also under control. Pay rates, hours worked and who is actually on shift all need to be accurate before a manager can trust a labour-cost-per-hour figure sitting next to the sales one, and that discipline is covered in more detail in a companion piece on controlling labour costs without cutting corners on service.

Spotting problems before they become expensive

Voids, refunds, no-sales and discounts are all recorded by an EPOS till, but they are rarely reviewed in real time unless someone is deliberately looking. A pattern of voids clustered around one till, one shift, or one member of staff is often the first visible sign of either a training gap or something more deliberate, and the earlier it is caught the smaller the loss. Waiting for a monthly report to flag an unusual void rate means a month of exposure has already happened before anyone acts on it.

The same logic applies to discrepancies between what the till says should be in the drawer and what is actually counted at the end of a shift. Reviewing sales data alongside cash reconciliation, rather than treating them as two separate jobs done by two different people at two different times, is what turns a small daily gap into something a manager notices in days rather than weeks. The practical mechanics of matching till totals to counted cash are set out in a separate guide on cash handling and till reconciliation, which pairs naturally with a live sales feed rather than replacing it.

Turning top sellers into stock and pricing decisions

Item-level sales data answers questions that a total revenue figure cannot: which dishes are actually driving the bulk of covers, which are barely selling despite taking up a fridge slot and a supplier line, and which have crept below their target gross profit as ingredient costs have risen. A dish that looked profitable when the menu was last costed can quietly stop paying its way if a key ingredient has gone up in price and nobody has revisited the recipe cost since. Running current sales mix through a free GP calculator alongside up-to-date supplier prices is a quick way to check whether the bestsellers are still the most profitable items, or whether volume is masking a thin margin.

Stock ordering benefits in the same way. A manager who can see that a particular starter has outsold forecast for three weeks running can adjust the next delivery before running out mid-service, rather than discovering the gap when a customer orders it and the kitchen has none left. The same visibility works in reverse: a slow-moving item flagged early can be pulled from the next order before it turns into wastage sitting in a walk-in fridge.

Comparing sites without losing the plot

For operators running more than one venue, real-time sales data changes the comparison from a monthly spreadsheet built from separate reports into something a manager can look at any afternoon. Two sites with similar covers can have very different labour costs, void rates or average spend, and those differences are only visible once the data sits side by side rather than in five different formats emailed in from five different sites. Spotting a strong performer early means the practices behind it, whether a staffing pattern, a menu change or a promotion, can be tested at other sites before the quarter closes rather than after. The operational load of running several venues without this kind of shared view is covered in more depth in a guide on managing multiple restaurant sites without losing your mind, which sets out the wider pattern this data feeds into.

The comparison only holds if every site is recording sales the same way, with the same categories and the same treatment of discounts and service charges. A dashboard built on inconsistent inputs from different sites produces figures that look precise but are not actually comparing like with like, which is worse than no comparison at all because it can lead a manager to act on a difference that is really just a reporting quirk.

Keeping the numbers straight for VAT and payroll

Sales data does not stop being useful once the shift ends. The same figures that inform staffing and stock decisions during service also underpin VAT returns, and businesses must keep the underlying records, including till and sales data, for six years under the rules on VAT records. A live feed that already exports and stores this data removes the risk of a gap in the archive being discovered only when HMRC asks a question about a return from three years ago.

The same data also crosses into payroll, particularly where tronc or service charge distribution depends on recorded sales, or where hours worked are checked against actual trading volume to confirm pay meets the National Minimum Wage rates for the hours genuinely worked. Keeping sales, hours and pay reconciled against each other, rather than as three separate systems that only get compared when something goes wrong, is what makes a wage query or a VAT check a quick lookup rather than a week of reconstructing history from paper.

Keeping this on the record

Every decision made from a sales dashboard, from cutting a shift short to reordering a bestseller, needs the underlying figures to be evidenced and retrievable rather than remembered, since a manager's recollection of last Tuesday's takings is not something an auditor, an accountant or an EHO can check. An EPOS system that stores sales, item and hourly data automatically gives that evidence a permanent home, so the numbers behind a staffing call or a menu change are still there months later when someone needs to check them.

Frequently asked questions

How often does EPOS data need to update to be useful for decisions?

Anything from every few minutes to hourly is enough for most operational calls, such as whether to send someone home early or push a dish before it sells out. End-of-day Z-reads are fine for accounting but too slow for staffing and stock decisions made mid-shift.

Do we need EPOS data if we already have a manual sales sheet?

A manual sheet tells you what happened yesterday. EPOS data tells you what is happening now, broken down by hour, site and item, which is what actually changes a decision such as calling in extra cover or cutting a shift short.

Can EPOS data replace a stock count?

No. Sales data shows what should have left the kitchen or bar based on till records, but only a physical count shows what actually left the stockroom. Comparing the two is how wastage, over-portioning and theft get spotted.

How long should we keep EPOS sales records?

VAT records, which typically include till and sales data supporting your returns, must be kept for six years. Many operators keep detailed EPOS exports for the same period so figures can be cross-checked against supplier invoices and payroll if ever queried.

Is real-time EPOS data only useful for multi-site groups?

Single-site venues benefit too, mainly for matching staffing to hourly demand and catching till discrepancies quickly. Multi-site groups get an additional layer of value from comparing sites against each other rather than only against their own history.

See how Zynthio handles this