Restaurant Analytics Dashboard: What One Screen Should Actually Show

Knowing which restaurant metrics matter is one problem. Seeing them in one place, updated daily, without exporting four spreadsheets is a different problem entirely. This post is about the second one — the dashboard, the product view, the single screen you glance at over morning coffee.

A good restaurant analytics dashboard is not the one with the most charts. It is the one where every number on the screen leads to a decision you can make this week. Below is what that screen should surface, why each metric earns its spot, and how a multi-location group should read the same data across venues.

Rule One: Every Number Must Map to an Action

The fastest way to build a dashboard nobody opens is to show vanity metrics — total lifetime orders, a running revenue counter, a busy graph with no benchmark. They feel impressive and tell you nothing. A useful tile answers a question: "Is this higher or lower than last week, and is that good?"

Before a metric goes on the screen, it has to pass one test: if it moves, do you know what to do? If the answer is no, it belongs in a report you pull occasionally, not on the dashboard you check daily.

Revenue Per Channel — Not Just Total Revenue

Total revenue is the least actionable number on most dashboards because it hides where the money came from. The same €10,000 week is healthy if 60% is direct dine-in and pickup, and fragile if 70% comes through delivery marketplaces that take a cut of every order.

Split revenue by channel: dine-in, direct pickup, your own delivery, and third-party marketplaces. Now the screen tells you something — whether your direct channel is growing, whether you are over-reliant on commission-bearing orders, and where to push next.

Profit Per Delivery Order, Not Delivery Revenue

Delivery revenue looks great until you net out the costs. A €100 marketplace order at 25% commission nets €75 before food cost; the same order placed directly through your own site nets close to the full amount minus payment processing. A dashboard that shows delivery revenue without showing margin per channel is actively misleading.

The tile that matters is contribution per order after commission and delivery cost. When you can see that a direct order is worth meaningfully more than a marketplace order, the case for steering customers to your own channel writes itself.

Service Metrics: Table Turnover and Average Ticket Time

For dine-in venues, the dashboard should surface table turnover (parties served per table per shift) and average ticket time (order placed to delivered). These are the service KPIs that turn a full room into actual revenue. A turnover rate of 1.8 on a Friday with a waitlist means you are leaving money in the lobby — the fix is process, not more tables.

• •Table turnover by shift and day of week — find the slow nights and the capacity-constrained peaks
• •Average ticket time, trended — a climbing line during peak service is an early staffing warning
• •Upsell attach rate — share of orders that included a modifier, add-on, or suggested item
• •Order accuracy — share of orders that went out right the first time

Upsell Attach Rate and Average Order Value

Average order value tells you whether the menu and prompts are working. Upsell attach rate tells you why. If AOV is flat, look at how many orders actually picked up a suggested add-on or larger size — that is the lever you control without raising a single price. A dashboard that shows AOV without attach rate shows the symptom and hides the cause.

Pair these two and a pattern appears fast: low attach rate plus low AOV means the upsell flow is missing or poorly placed; high attach rate plus flat AOV means you are upselling cheap items and should rethink what gets suggested.

Repeat-Customer Rate — The Slow Signal That Matters Most

Repeat-customer rate — the share of orders from someone who has ordered before — moves slowly, but it predicts long-term health better than any single week of sales. A direct ordering channel makes it visible at the customer level; marketplace orders usually hide the customer entirely, so you cannot tell a loyal regular from a one-time tourist.

A practical filter for any dashboard tile: would you change something this week if this number moved? Revenue per channel, profit per delivery order, table turnover, attach rate, and repeat rate all pass. A lifetime-orders counter does not.

Multi-Location: Compare, Don't Aggregate

For a group, a single blended number across all venues is the worst of both worlds — it hides the underperformer and flatters the star. Multi location restaurant analytics is about comparison: the same five metrics, side by side, per venue, normalized so a small kiosk and a flagship are judged on rates rather than raw totals.

When one location runs a 22% upsell attach rate and another runs 9% on the same menu, that gap is a training playbook, not a mystery. When one venue's direct channel is 55% of revenue and another's is 20%, you know where the marketing budget should go. The value of group analytics is not a bigger total — it is the outlier you would never spot in a blended average.

When NOT to Over-Engineer This

A single-location cafe doing 80 covers a day does not need cohort retention curves or predictive forecasting. The five tiles above, reviewed weekly, beat a 40-widget dashboard nobody reads. Add complexity only when a real decision needs it — predictive demand planning matters at multi-venue scale, not at one quiet bistro. Sophistication you do not act on is just noise with better styling.

Where the Dashboard Lives

With Ordering.Tools, revenue by channel, average order value, upsell attach rate, popular items, and repeat-customer rate are visible in the admin analytics dashboard without manual exports, and group operators can compare venues side by side. For the underlying definitions and targets behind each number, see our guide on restaurant KPIs and the metrics that predict profit. For how groups roll this up across brands and sites, see the Multi-Location and Restaurant Chains feature pages — and the Analytics Dashboard feature page for the live product view.

Key Takeaways

• •Every dashboard tile must map to a decision you can act on this week — kill the vanity metrics
• •Show revenue per channel, not just total revenue, so you can see your reliance on commission orders
• •Track profit per delivery order, not delivery revenue — margin per channel is what matters
• •Pair upsell attach rate with average order value to see the cause, not just the symptom
• •Repeat-customer rate is the slow signal that predicts long-term health best
• •For groups, compare venues on normalized rates side by side — never blend into one average