Multi-unit restaurant groups lose margin between locations every quarter. Most operators never see it happening. The consolidated financials look acceptable. Revenue is up. Portfolio prime cost sits at 61% — manageable. Leadership reviews the numbers, approves the close, and moves on.
Meanwhile, Location 7 runs a 68% prime cost. Location 12 runs 57%. Nobody at the corporate level knows. Nobody reviews the P&L by location on a weekly basis. The average hides the variance. The variance is where the real business lives.
This pattern repeats across every multi-unit group we work with. Margin does not disappear in one dramatic event. It leaks quietly between locations — through inconsistent food cost, labor coded differently across units, delivery revenue that does not reconcile cleanly, and a reporting structure never built to surface the problem.
A consolidated P&L tells you how the portfolio performed as a whole. It cannot tell you which locations carry the others. It cannot tell you which concepts are structurally unprofitable. It cannot tell you which general manager's decisions drive your best and worst margin performance.
For groups running 10 to 50 locations, the gap between your best and worst unit is almost always larger than leadership realizes. Industry data shows the spread between highest and lowest performing locations on prime cost can exceed 12 to 15 percentage points — even within the same concept and market.
The operators protecting profitability right now review location-level P&Ls weekly, not monthly. They compare the same metrics across units in a standardized format. They see variance the moment it emerges — not 30 days later in the next close. That cadence is not a best practice. It is the minimum requirement for managing a multi-unit group in the current cost environment.
That spread represents real, recoverable margin. It is invisible inside a consolidated report. The only way to see it is to build the infrastructure that surfaces it — by location, every week.
When managers at different locations code the same expense differently, your chart of accounts becomes unreliable as a comparison tool. One location codes a repair under maintenance. Another codes it under supplies. A third puts it in miscellaneous.
Three locations. Three different numbers. None of them comparable. Over time, this creates a false picture of which locations control costs and which do not. Moreover, it makes any variance analysis meaningless because the underlying data is inconsistent at the source.
Tracking total labor cost as a percentage of revenue tells you something. Tracking front-of-house labor, back-of-house labor, and management labor separately — by location, by daypart — tells you everything.
Groups that blend these into a single labor line miss the specific driver of any labor variance. You cannot fix a problem you cannot locate. Additionally, without daypart-level visibility, every scheduling decision relies on incomplete data. The labor cost management problem is structural, not operational.
Third-party delivery platforms remit on their own schedule, net of fees. Commission structures vary by market. When that revenue does not flow cleanly into your accounting system by location, you end up with distorted revenue figures and food cost percentages that do not reflect actual performance.
For groups doing meaningful delivery volume, this reconciliation problem is often larger than anyone realizes. Furthermore, it typically goes undetected until someone audits the platform statements against the P&L directly — by which point the distortion has run through multiple periods.
A location running 2% above theoretical food cost is not a rounding error. On a location doing $80,000 in monthly food sales, that is $1,600 per month in unaccounted cost. Across 20 locations over 12 months, that number becomes material.
Most groups see the variance on a report and absorb it into the close. They do not investigate. The reason is structural — the reporting infrastructure does not make the source easy to find. Therefore, the problem repeats every single period.
Solving location-level margin loss is not about working harder. It is about building the right reporting infrastructure. Specifically, one that makes performance visible at the right level of granularity, on the right cadence.
Multi-unit groups need location-level P&Ls structured identically across every unit. They need those P&Ls populated and reviewed weekly. They need labor tracked by role and daypart, not just as a total. They need delivery revenue reconciled before it enters the accounting system. And they need a chart of accounts built for comparison, not just compliance.
At TRIS, this is the work we do inside every group we partner with. Not reporting for the sake of reporting. Financial infrastructure designed to surface the specific decisions that protect and grow margin across every location in your portfolio.
Consequently, the groups we work with stop managing portfolio averages and start managing individual unit performance. That shift changes everything about how financial decisions get made — and how quickly problems get solved.