Multi-location operators

From five locations to fifty without changing your books.

Location-level P&L without leaving QuickBooks. Same-store vs new-store breakouts. Margin drift detection on every unit, every week. The diagnostic layer your accountant doesn't have to learn — for the CEO and CFO who need answers between closes.

Location-level P&L

Without leaving QuickBooks.

QuickBooks treats class and location as tags bolted onto a single-tenant ledger. The rollup happens in Sheets. Here it happens in the diagnostic layer — without disturbing your accountant's workflow. The bookkeeper keeps booking to QBO classes the way they always have. The CEO and CFO get the location-aware P&L on top.

Two reports do most of the work: the Location Profitability Summary gives one row per location with Revenue, Cost, Gross Profit, Operating Income, Net Income, plus optional variance against any comparison period. The P&L by Location pivots locations as columns and account subtypes as rows. Both export to CSV / XLSX / PDF.

  • OAuth into QBO; your accountant's workflow doesn't change
  • Location dimension on every projection, every diagnostic, every report
  • Hierarchical locations: regions roll up to brands, brands to parents, automatically
  • Same-store vs new-store breakouts on every comparison period
  • Permissions scope down: a regional manager sees only their region
Margin drift detection

Catch the slow leaks before they're losses.

Margin drift is hard to see in a monthly close. A 60bp slip per month for six months looks like noise on any single P&L; it's a 360bp leak by year-end. Anomaly detection running weekly on unit-level metrics catches the drift in week three, not December.

01 · WEEKLY

Detection runs on a weekly cadence.

Each location's prime cost, food cost, labor ratio, and average ticket are watched against the location's own 12-month envelope. A 2σ move triggers a finding. The high-severity findings hit the CEO's dashboard before they hit the close.

02 · PER UNIT

Calibrated on each unit's own history.

Houston Heights runs leaner than Austin East Side — that's known. We don't measure each unit against a network average. We measure each unit against its own twelve-month envelope. The detection is sensitive to deviation, not to absolute level.

03 · EXPLAINED

Each finding comes with the reason.

"Labor at Houston Heights is +3.6σ above trailing 12 months. Driven by a 12% headcount increase that began March 1. Revenue lift has not yet materialized at the expected ratio." The CEO gets an answer, not just a number.

Same-store vs new-store

Decompose the network number automatically.

The headline number — "network revenue up 8.4% YoY" — can be most of the story or most of the lie depending on the underlying mix. The platform decomposes it for you: same-store comparable growth, new-store contribution, ramp drag from underperforming new units. Each component drills to the contributing locations.

For unit-level capital allocation decisions — should we open more locations like Plano? are the newer Heights-class units ramping fast enough? — the decomposition is the whole game. The CEO needs to see what's same-store and what's new-store before deciding what to do next.

You don't need to replace QuickBooks to get location-level diagnostics. You don't need a six-month NetSuite implementation to get unit economics. You connect via OAuth, and the layer above your books does the work your accountant has been doing in Sheets — in real time, on real data.
Books unchanged · diagnostic layer above

Stop signing contracts before you've seen your own numbers.

Connect your books in an afternoon. See the diagnostics and the first scenarios on your real data, the same week. No implementation fees, no six-month rollout, no SOW.

app.rollupbooks.ai Start free
Already a user? Sign in ↗