How To
One Sales View Across Every Restaurant Location
How to consolidate sales, labor, and food cost across locations and POS systems into a daily flash report your managers trust.
By Localhost Labs
In short
- Track prime cost (COGS plus labor as a share of sales) by location, estimated daily and confirmed weekly, not only at month end.
- A consolidated view depends on shared definitions: net sales, business day, item mapping, delivery recorded gross, and labor from actual hours.
- This week: write down those definitions and send a manual daily flash for one week to see where the data is hardest to get.
Ask the owner of a three-location restaurant group how yesterday went, and the honest answer is often "I'll know on Thursday." Sales are in the POS, but one location runs a different POS than the other two. Labor is in the scheduling app and the payroll system. Delivery revenue arrives net, days later, from three platforms. Food cost lives in invoices and a count sheet. Someone pulls it all together by hand, and by the time the numbers are ready, the week is over.
Multi-location restaurant sales reporting does not need to be elaborate. It needs to be consistent, fast, and trusted by the people who run the kitchens. This post covers what that takes.
Why this matters more now
Margins leave little room for a slow read on the business. In its 2026 State of the Restaurant Industry release, the National Restaurant Association said 42% of operators reported their restaurant was not profitable the prior year, and more than 9 in 10 cited food, labor, insurance, energy, and swipe fees as significant challenges.
Costs are still moving. USDA's Economic Research Service, in its August update, forecast food-away-from-home prices to rise 3.6% in 2026, after a 3.8% increase in 2025. And labor is a large, fast-moving number: the Bureau of Labor Statistics shows food services and drinking places employed about 12.4 million people in July (preliminary), with production and nonsupervisory workers averaging $20.20 an hour.
Fragmentation is common, too. DoorDash, citing its own 2026 operator research, reports that 40% of operators run their business across four to five separate systems that don't share data, and 83% believe connected systems would improve profitability. Delivery adds its own layer: in NRA survey data filed with the FTC in May, 63% of limited-service operators on third-party delivery said they are on three or more platforms.
Start with prime cost
If you track one number across locations, make it prime cost: cost of goods sold plus total labor, as a share of sales. It captures the two costs a manager can influence day to day. Writing in Nation's Restaurant News this month, one contributor put a healthy prime cost somewhere between 55% and 60% of sales, and noted that plenty of restaurants run at 68%. Your right target depends on your concept. For scale: on $3 million in annual sales, ten points of prime cost is $300,000.
The practical problem is that prime cost is usually calculated monthly, after the books close. By then, a labor overrun or a food cost drift has already run for weeks. The goal of a consolidated view is to get an honest estimate daily and a true number weekly.
The daily flash report
A flash report is a short summary of yesterday, delivered every morning before managers start their day. It should fit on one screen. Here is what one might look like for a hypothetical three-location group on a Tuesday. All figures are illustrative.
| Location A | Location B | Location C | Group | |
|---|---|---|---|---|
| Net sales | $8,400 | $6,100 | $5,200 | $19,700 |
| vs. same day last week | +4% | −6% | +1% | −0.1% |
| Labor cost | $2,352 | $1,952 | $1,508 | $5,812 |
| Labor % of sales | 28.0% | 32.0% | 29.0% | 29.5% |
| Theoretical food cost % | 29.5% | 30.5% | 30.0% | 29.9% |
| Estimated prime cost % | 57.5% | 62.5% | 59.0% | 59.4% |
| Delivery share of sales | 18% | 31% | 22% | 23% |
| Comps and voids | $95 | $310 | $60 | $465 |
The group number looks flat and unremarkable. Location B does not: sales are down, labor did not flex with them, delivery is a larger share of its sales, and comps are high. That is four specific questions for one manager, asked the same morning, rather than a vague sense at month end that "B has been soft."
Notice what makes this possible. Every location defines net sales the same way, labor comes from the time clock rather than the schedule, and food cost is theoretical (from recipes and item sales) so it can be calculated daily. Actual food cost, from inventory counts, confirms it weekly or at each count. We walked through that reconciliation in multi-location restaurant inventory without spreadsheets.
What a single view actually requires
The dashboard is the easy part. The hard part is making numbers from different systems mean the same thing. A consolidated view needs:
One definition of net sales
Decide, once, how net sales are calculated: after discounts and comps, excluding sales tax, tips, and gift card sales. Then apply it to every location and every POS. Two locations on different POS systems will often report "sales" differently by default.
One business day
Late-night locations may close after midnight. Some POS systems end the business day at a fixed time, others at the last closed check. Pick a cutoff and normalize every source to it, or your same-day comparisons will be off.
One menu and location map
If one location calls it "Chx Sand" and another "Chicken Sandwich," or files it under a different category, item-level comparisons fail. Map every item and category from every POS to a single master list.
Delivery recorded gross
Record delivery orders at their gross value, with commissions and platform fees as a separate cost line. If delivery is booked at the net payout amount, locations with more delivery will show lower sales and higher food cost percentages than they really have, and the commissions disappear from view. Our breakdown of what third-party delivery really costs covers how to reconcile payouts to the POS.
Labor from actual hours
Scheduled hours tell you the plan. Clocked hours tell you what happened. Pull actual hours daily, apply wage rates, and decide how to handle salaried managers and payroll burden, whether as a daily allocation or a weekly adjustment. Just be consistent.
Drill-down, not more charts
The owner needs the group view. The manager needs their location, by daypart and by hour. The chef needs food cost by item. One source of truth with different views beats three separate reports that disagree.
What to do this week
Even without new systems, you can start:
- Write down your definitions of net sales, business day, and labor cost, and share them with every manager.
- Build a manual flash for one week: net sales, labor %, and comps for each location, sent by 9 a.m. It will be tedious, and it will show you which data is hardest to get.
- Map your top 50 items across locations to common names and categories.
- Calculate prime cost for last month by location, not just for the group.
If the manual flash takes more than half an hour a day, that is useful information. It tells you how much time the business spends assembling numbers rather than acting on them. Our guide to custom software versus off-the-shelf tools lays out the trade-offs if you are weighing how to fix it.
This is the kind of connected view we build for multi-location restaurant groups: POS, labor, delivery, and inventory in one place, with one set of definitions. If it would help to talk through your current reporting, you can book a conversation whenever it suits you.