Restaurant Analytics: 5 Numbers to Check Every Day

Bario Team

Your daily report already knows why Tuesday felt slow and which cocktail carries the bar. Five numbers, five minutes with your morning coffee, here is how to read them.

You closed at midnight, counted the drawer, and it felt like a good night. But was it? Compared to last Saturday? Was the terrace carrying the beach, or the other way around? Feelings are how tired owners measure a shift; numbers are how the shift actually went.

The point of restaurant analytics is not dashboards for their own sake, it is five minutes with your morning coffee that change what you do today. Bario's reports are built from every order your team tracked from open to paid, so the data is already there. Here are the five numbers worth checking daily, and what each is telling you.

1. Daily revenue, the trend, not the total

Yesterday's total on its own says almost nothing. Yesterday against the same day last week says a lot: a Tuesday down 20% on the last four Tuesdays is a signal, weather, a competitor's event, or a menu change that misfired.

Do this: check the daily revenue trend before you check anything else, and only investigate when a day breaks its own pattern. That keeps this a thirty-second habit instead of a spreadsheet session.

2. Peak hours, where minutes become money

Revenue by hour shows when your venue actually earns. Most owners guess their rush wrong by an hour or more, and staff accordingly, which is how you end up overstaffed at 11 a.m. and drowning at 7 p.m.

Do this: match your shift start times against the real curve. Moving one waiter's start one hour later can cover the evening spike at zero extra cost. If you see a dead 90 minutes every afternoon, that is your happy-hour slot, you now know exactly where discounted drinks cost you least.

3. Popular items, your menu, ranked by reality

The popular items report ranks what actually sells. Read both ends of the list. The top tells you what to never run out of and what to feature. The bottom tells you what clutters the menu, ties up prep, and slows the kitchen for three orders a week.

Do this: once a week, act on one item. Retire a bottom-dweller, or take your number-one cocktail and put it on the menu's front page. Small menu, honest menu, faster kitchen.

4. Per-employee performance, coaching, not policing

Orders and revenue per employee show you how the floor really runs, especially when shared tablets use PIN switching, so every order is stamped with who took it. The gap between your best and newest waiter is not a disciplinary matter; it is your training plan written in numbers.

Do this: look for outliers, then look for reasons. If Maria sells double the cocktails, find out what she says at the table and make it the house script. If a new hire's numbers stall for two weeks, they need a shadow shift, not a warning.

5. Shift hours, the cost side of the story

With one-tap clock in/out, worked hours land in your reports next to the revenue those hours produced. Revenue is vanity until you put labor next to it: a record Saturday that took nine staff might be worse business than a quiet Wednesday run by three.

Do this: glance at hours against revenue for the same day. When the ratio drifts for a week, your schedule needs surgery, and the peak-hours chart above tells you exactly where to cut or add.

Make it a five-minute ritual

  • Morning coffee: revenue trend, then yesterday's peak hours. Thirty seconds each.
  • Monday: popular items, make one menu decision.
  • Friday: employee performance and shift hours, set the weekend roster with data.
  • End of month: export everything to CSV for your accountant, in one click.

No setup is required for any of this, if your team takes orders through Bario, the reports are already filling themselves. Roles apply here too: managers and admins see reports; waiters do not.

From daily glance to seasonal advantage

The daily five keep a shift honest. Stacked over weeks, the same numbers start answering bigger questions.

Comparing whole weeks smooths out the noise of one rainy Tuesday and shows whether the new menu, the new hire, or the new opening hours actually moved anything. Peak-hour curves from June are the most honest staffing forecast you will get for August, better than last year's memory, because they are this year's guests.

And when the accountant asks for the season, you do not spend an evening transcribing: the CSV export hands over every report in one click. For seasonal venues this is the quiet superpower, you close in October with a complete, numeric record of what worked, and reopen in May knowing exactly what to repeat.

The takeaway

Restaurant analytics is not a data science project. It is five numbers, read in five minutes, that quietly answer the questions you used to argue about: when to staff, what to stock, who to coach, and whether last night was actually good. The nights already generate the data. Start reading it.

Want reports that fill themselves? Start free, no card required, or try the live demo and open the reports tab on a venue with data in it.