5 things independent restaurants don't know about their own data

1. Your busiest hour isn't when you think it is

Ask most owner-operators when they make the most money and you'll hear Friday or Saturday night, end of service, full room. The truth is more specific — and more awkward. The highest revenue in a day often sits in a single 60-minute window, and that window moves. It might be 7.30–8.30pm one week and 6.00–7.00pm the next depending on bookings, walk-ins, and how fast the kitchen is turning tables.

Staffing rosters are usually built on habit: the same number of people for "Friday service" every week. When the real peak isn't where you assumed, that's the hour where plates stack up, tickets slip, and regulars start to wonder if the place has lost its touch — not because the team is bad, but because the load doesn't match the plan.

QuantDine surfaces your actual peak hour by day and by week of service, so you can align covers and headcount to when the tills are really working — not when it feels busy from the pass.

2. Your best-selling dish probably isn't your most profitable one

Volume is easy to see: it's the line on the report that makes you feel good. Margin is another story. A £12 pasta that sells forty covers a week might be a workhorse; a £22 special that sells fifteen can still put more cash in the bank after you've paid for the ingredients, prep time, and waste. High volume doesn't mean high gross profit per cover — and most teams never line those two up on the same page.

Food cost as a percentage of sales per dish is the number that matters for menu decisions, but it only comes from accurate recipes, yield assumptions, and the discipline to keep them current. In a small independent, that almost never gets done; there's always a service, a no-show, or a delivery to chase instead.

Menu engineering exists to split velocity from margin: what to put in the window, what to reprice without alienating the room, and what to let disappear quietly. The data is in your sales mix — you just need it surfaced in a form you can act on.

3. You're losing covers on specific days without knowing why

A slow erosion on one lunch or one midweek evening doesn't register as a crisis. Fifteen percent fewer covers on Wednesday over two months can look like "weather" or "January" until you plot it and see a line that only goes one way. By then the habit is broken: guests have found another routine.

In retrospect the cause is almost always in the data somewhere — a price step on a set lunch, a menu item that dropped in quality, a new place two streets over, a lost corporate booking. The POS holds the when; the story usually comes from memory once someone asks the right question.

Catching the slope before it flattens your week is the point. A weekly view of covers by day, against your own history, turns noise into a signal you can respond to with a campaign, a menu tweak, or a frank conversation with the team — while it still moves the needle.

4. Your average spend per head tells you more than total revenue

Total revenue is the number everyone looks at. It also rises and falls with how many people you put through the room, which you already know from being on the floor. It tells you if the week was "big" or "quiet"; it doesn't tell you if the business model inside that volume is healthy.

Average spend per head — check divided by guests — is the cleaner lens. It moves when your menu is priced right, when the team is selling wine and second courses, and when the room is trading up instead of just filling. Two restaurants can clear the same £8,000; one at £22 per head and one at £28 are not the same business. One is living on volume; the other has room to breathe when covers dip.

Tracking that number over time, and against similar services in your own past, is how you test whether "more marketing" or "better food" is actually working. It's the metric that links guest behaviour to margin without fooling you with a busy-but-thin week.

5. The data you need already exists — it's just locked in your POS

Every card tap and every line on a bill is a structured record: what sold, when, at what price, how many covers, and in many setups enough detail to split starters, mains, and drinks. The restaurant isn't short of data; it's short of a layer that makes that data legible for running the place.

POS systems are built to run the till, the floor, and compliance — not to give you a weekly brief on where margin leaks or which day is softening. So the intelligence sits in export files and stale spreadsheets, or nowhere at all.

QuantDine is built to sit on top of that transaction history: peak hours, dish-level performance, cover trends, and the spend-per-head view — updated as your data comes in, without you building another model in Excel. The five ideas above are the kind of thing that falls out once the numbers are in one place, every day, for your site only.