A centralized dashboard that ranks every location by identical KPIs is a useful way to find the sites quietly dragging your group down. Start small: pick three priority KPIs and connect your POS and inventory data for a pilot at two or three venues. Below, we cover the KPIs, data feeds, tooling options, rollout steps and real decisions the reports unlock.
TL;DR:
- Start with revenue per labor hour, COGS percentage, and food waste, and document formulas, exclusions, labor costs, and net sales consistently across every venue.
- Spreadsheets can serve two or three venues; BI tools require someone to maintain the data model, while integrated systems suit groups without analysts.
- Pilot POS and inventory feeds at two or three venues, then reconcile sales to POS reports, labor hours to payroll, and stock counts before expanding.
- Check sales and labor daily, review KPIs weekly with site managers, and examine COGS variance, waste, and trends in a monthly review.
- Low revenue per labor hour may signal overstaffed quiet shifts; compare cover counts with rosters, adjust hours, and track the metric afterward.
Table of Contents
- Which KPIs should you measure at every location?
- Should you report with spreadsheets, BI tools or an integrated platform?
- How do you set up multi-site reporting step by step?
- What decisions do cross-site reports unlock?
- Why a centralized, operator-focused view beats site-by-site reports
- How can we help you roll out multi-site reporting faster?
- FAQ
- Sources
Which KPIs should you measure at every location?
Pick metrics that stay fair across venues of different sizes, then define each one once and use it everywhere. Our core set for multi-site reporting:
- Revenue per labor hour: net sales divided by total paid labor hours. It adjusts for venue size and volume, which can make it more useful than raw revenue when spotting efficient sites and considering their staffing models.
- Labor cost %: total labor cost divided by net sales.
- COGS %: opening stock plus purchases minus closing stock, divided by net sales.
- COGS variance: actual COGS minus theoretical COGS from recipes and sales mix.
- Covers and average check: covers are guests served; average check is net sales divided by covers.
- Food waste: waste cost divided by food purchases, logged the same way at every site.
- Inventory variance: counted stock versus expected stock, by item category.
Write the formula down, including what counts as net sales and which labor costs are in. Sites that calculate "labor" differently will produce rankings you can't trust.
Labor and COGS are where the pressure sits. The R&CA 2025 Industry Benchmarking Report finds that labour and cost of goods sold are the primary financial pressures on Australian hospitality venues, with food, beverage and labour costs together able to exceed three quarters of revenue.
Why it matters: if those two lines take most of every dollar, a small gap between sites adds up fast.
Should you report with spreadsheets, BI tools or an integrated platform?
All three work at some scale. The right pick depends on venue count and the skills you have in-house.
- Manual spreadsheets: cheapest to start and fine for two or three venues. Digital tools for tracking and reporting are common in quick service, and spreadsheets remain widely used alongside waste-tracking technology and inventory software. The cost shows up later: manual updates, version drift and slow data.
- BI platforms: strong visuals and flexible analysis, but someone has to build and maintain the data model and enforce KPI definitions. They suit groups with an analyst on staff.
- Integrated inventory and reporting systems: connect stock, ordering and reporting in one place, so KPI definitions are standard from day one. They fit growing groups without a data team, and our hospitality inventory software page shows what that looks like in practice.
Whichever route you take, hold it to a minimum checklist:
- Identical KPI definitions across every site
- A ranking view that sorts venues by any KPI
- Date-range comparison against prior weeks and months
- Role-based access, so site managers see their venue and operations managers see the group
The trade-offs are setup time, upkeep and how fresh the data is. If your numbers arrive late, you're reading history, not managing.
Market context helps too. Tools like StayStrategy's city-level market intelligence show what's happening around your venues, which pairs well with the internal numbers.
How do you set up multi-site reporting step by step?
Here's the rollout we recommend, with suggested owners and timing:
- Define KPIs (first, ops manager): choose a starting set, and write formulas and exclusions down.
- Standardize item and menu mapping (next, kitchen leads): align names, units and recipes across sites.
- Connect POS and inventory (after mapping, ops manager and kitchen leads): start with the pilot venues only.
- Build the pilot dashboard (after connecting the feeds, ops manager): pilot sites ranked on your chosen KPIs.
- Validate and reconcile (before rollout, finance): fix mismatches before anyone acts on the numbers.
- Train and roll out (after validation, ops manager): bring in remaining sites with a short training session each.
Before you trust the dashboard, run this validation checklist:
- Reconcile dashboard revenue to POS end-of-day reports
- Spot-check inventory variance on a handful of high-value items
- Match paid labor hours to payroll
- Confirm every site uses the same trading-day cutoff
Set a cadence that people will keep: a daily operational check on sales and labor, a weekly KPI review with site managers, and a monthly deep-dive into COGS variance, waste and trends.
What decisions do cross-site reports unlock?
Reports earn their keep when they change what you do on Monday morning. Common moves:
- Reallocate labor: a site with low revenue per labor hour may be overstaffed on quiet shifts, while a high performer's roster becomes the template.
- Investigate COGS variance: a gap between actual and theoretical COGS points to over-portioning, theft, receiving errors or pricing drift.
- Cut recipe waste: rank sites by waste percentage, then compare prep methods at the best and worst. Our guide on restaurant waste tracking walks through the logging side.
Here's a typical walkthrough. The ranking flags one site with the lowest revenue per labor hour in the group. You drill into cover counts and see lunch is slow while staffing matches dinner levels. You trim lunch hours, then watch the metric over time.
Pro Tip: Set the success metric before you change anything, such as a target revenue per labor hour or COGS variance, so you can tell whether the fix worked.
For more on running several venues, see our post on cost control for multi-venue restaurant groups.
Why a centralized, operator-focused view beats site-by-site reports
Group problems don't always announce themselves. One site slips a point on labor, another drifts on COGS, and each looks acceptable in isolation. A unified dashboard ranking every venue on the same KPIs exposes the quiet underperformers before they drag the group down. We think that's the real value: not prettier charts, but a single honest scoreboard.
With labor and COGS being the biggest pressures on margin, consistent definitions are your best control. After rollout, aim for something simple: a narrowing gap between your best and worst site on revenue per labor hour, and a COGS variance that shrinks quarter on quarter.
— Admin
How can we help you roll out multi-site reporting faster?
If you'd rather not stitch feeds together yourself, our platform was built for this. We give you real-time stock tracking, low-stock alerts, supplier ordering and reporting tools in one place.
- Live stock tracking across single or multiple locations
- Low-stock alerts so you reorder before you run out
- Supplier ordering built into the same system
- Reporting tools for inventory and costs
See our Starter, Regular and Pro plans at $39, $69 and $99 AUD per month, or start a free trial and run a pilot on your own venues.
FAQ
What is multi-site reporting for restaurants?
It means pulling sales, labor, inventory and waste data from every venue into one view, using identical KPI definitions. That lets you rank sites side by side and spot outliers quickly.
Which three KPIs should I start with?
Start with revenue per labor hour, COGS % and food waste. Together they cover the two biggest cost pressures plus a controllable loss, and they're simple to calculate consistently.
How often should I review multi-location restaurant metrics?
Check operations daily, review KPIs weekly with site managers, and run a deeper monthly review of COGS variance and trends. Daily and weekly rhythms catch problems early, while the monthly review shows whether fixes held.
Do I need a BI tool to compare restaurant sites?
Not necessarily. Spreadsheets can work for a few venues, while BI tools or an integrated platform suit larger groups. What matters most is that every site uses the same KPI definitions.
Sources
A ranking is only as good as the feeds behind it. These are data sources to consider first:
Bad reports can trace back to normalization, not just software. Watch for inconsistent SKU and menu names between venues, different end-of-day cutoffs, mismatched time zones and conflicting shift definitions. Sites using different trading-day cutoffs will skew daily comparisons.
For integration, you have three routes: direct connectors, CSV or API imports, and a manual-entry fallback for sites without a clean feed. Use the fallback sparingly and flag it in the report.
Give every feed an owner. The kitchen lead maintains inventory item mapping, the operations manager owns POS mapping, and finance owns payroll. When a number looks off, everyone knows who checks it. A mobile app can also make stock counts faster; our piece on the role of a mobile inventory app in your kitchen covers that side.