Multi-Location

Multi-Unit Restaurant Management: A Guide for Restaurant Groups

Updated on 10 min read

Multi-unit restaurant management works when three things are in place: KPIs defined the same way across every location, one view that brings POS and labor data together every day, and a system that speaks up on its own when a location starts to slip. That is not a question of discipline in the restaurants. It is a question of the information the head office works with. Kiosa solves it with One View (every location at a glance) and the AI partner (answers questions with real numbers and takes work off your plate).

From the third location onwards, the old way of working breaks. Not dramatically, but gradually. A weak Monday at location 2 disappears because location 3 had a strong day. A rising labor cost percentage at location 1 only shows up when the monthly P&L arrives. That is not a management failure. It is a system design problem.

Contents

  1. Why it tips over with several locations
  2. What central management really means
  3. The five KPIs every location must deliver daily
  4. Comparing locations fairly
  5. Early warning: catching deviations before they get expensive
  6. The steering rhythm
  7. The three most common mistakes
  8. What a multi-location system has to do
  9. From spreadsheets to a system: how to go about it
  10. Example: Mama Trattoria, 10 locations
  11. What it costs
  12. FAQ

Why it tips over with several locations

You run a single restaurant on experience: you are there, you see how full it is, you know the team. With two locations you still commute between them, call in, get a feel for things. From the third location, information gaps open up that you don't notice at first. Complexity grows faster than the number of sites: with ten locations there are 45 possible location-to-location comparisons. Nobody keeps those in their head.

A typical setup:

  • The POS system delivers sales, with a separate login or report per location.
  • The workforce system knows shifts and working hours, but not sales.
  • Accounting delivers the P&L several weeks late.

Three systems that know nothing about each other. Someone at head office merges the numbers by hand, usually on a Monday. By the time they arrive the numbers are already old, and even then the context is missing: is a day's sales at location 3 good or bad? Compared with last week, with the other locations, with the plan?

Typical symptoms:

  • You only hear about problems when the P&L comes in.
  • Your general managers report in different ways: one by spreadsheet, one by WhatsApp, one not at all.
  • You don't know for sure which location is profitable, because costs are allocated differently.
  • Forecast and actuals diverge, but nobody analyses why.

The real scaling break is not operational leadership and not staffing. It is the information base.

What central management really means

"Managing centrally" does not mean making every decision at head office. It means head office has a complete picture every day, while locally run restaurants still act on their own. It is not surveillance. It is a navigation instrument.

A central view across several locations delivers this automatically, every day:

  • sales, labor cost and food cost per location, calculated with the same logic
  • deviations with context: which location is off, and against what?
  • a ranking: who is ahead this week, who is falling behind?
  • the trend: is a location getting better or worse than in recent weeks?

The alternative is real: if you run five locations and only see structural problems at location 4 in the following month's P&L, you have lost weeks of margin by then.

The five KPIs every location must deliver daily

Not every number is a steering metric. Many numbers only describe, without telling you whether you need to act. These five should be available daily for each location:

1. Sales against forecast or plan. The absolute figure matters less than the deviation from what was expected. The same day's sales send a different signal when more was expected than when less was expected.

2. Labor cost percentage. Labor cost relative to sales. It only exists when POS sales and labor data are combined, and it shows the same evening whether the day was profitable. Your concept sets the target, not an industry figure.

3. Sales per labor hour. The most direct productivity metric. It shows whether the team is in the right place at the right time, and it makes differences between locations visible.

4. Food cost percentage. Cost of goods relative to sales. Sharp deviations upwards point to shrinkage, portioning or purchase prices.

5. Rank in the group. The relative position: which location sits in the top third, which in the bottom third, and has that changed?

With these five numbers every day, you know where attention is needed today and where it isn't. Labor cost percentage and sales per labor hour need POS and labor data together. That is why connecting both sources is the first step, see integrations.

Comparing locations fairly

The biggest mistake in restaurant groups: judging each location on its own. 32 percent labor cost, good or bad? Impossible to say without context. If your best location sits well below that and your weakest well above, you know where the lever is.

Three levels of comparison make sense:

  • Location against location. Your best location is your realistic benchmark, not an industry figure nobody can verify.
  • Location against its own history. Is the location getting better or worse? A trend over several weeks says more than a single month.
  • Location against plan. Plan vs. actual only works if the plan is realistic.

Direct comparisons are methodologically tricky: a city-centre site has different sales potential from a suburban one, and seat count, trading days and season all distort the picture. A fair comparison normalises these differences, for example sales per seat and trading day instead of absolute sales, and looks at the development, not just the snapshot. A location that has been sliding for months is more urgent than one that sits slightly below average but stays stable.

How this looks in Kiosa is on the page managing restaurant chains. For a deeper dive into the method, read restaurant location benchmarking.

Early warning: catching deviations before they get expensive

The most expensive problem is not the location that is obviously doing badly, but the one that is slowly fading. Early warning is based on patterns, not on single alerts.

Example: for fourteen days, one location comes in below forecast every Tuesday, and no other weekday shows this. That is not chance, it is a structural signal. Without early warning it only becomes visible in the monthly sales.

Typical indicators:

  • The average check falls over several weeks.
  • The labor cost percentage rises while sales don't fall.
  • Reviews drop. That can be an early signal before sales move.

Each signal on its own is not yet a problem. Several at once are a clear reason to look into it.

The steering rhythm

Professional steering needs a fixed rhythm, not because bureaucracy is good, but because a system prevents mistakes:

  • Every morning: read the briefing. What happened yesterday, where was the deviation, what is coming up today?
  • Weekly: compare locations on the key KPIs. Who has improved, who needs support?
  • Monthly: trend and month-end review, reconciliation with the P&L, align forecast and staff planning with your general managers.

The test of whether you are steering or just reporting: after a short look at the system, can you make a concrete decision? Then you are steering. If you first have to build a presentation, you are reporting.

The three most common mistakes

Too many tools with no connection. POS here, workforce system there, accounting somewhere else, each with its own definitions and exports. The result is hours of data preparation instead of analysis. The answer is not one more tool on the side, but one view that brings the existing sources together.

Numbers without context. A drop in sales sounds dramatic until you see it was a public holiday. Numbers without plan, prior year and comparison lead to wrong decisions.

Reacting instead of forecasting. The P&L shows what happened. A forecast shows what is coming. If you know lower sales are expected next Tuesday, you plan the team accordingly, instead of noticing on Wednesday that labor cost has spiked.

What a multi-location system has to do

The requirements are fundamentally different from a single-site tool:

  • All locations side by side, without CSV exports and manual merging
  • POS and labor in one database, so labor cost percentage and sales per labor hour exist without spreadsheets
  • Alerts on its own when a value tips, instead of someone checking 50 data points every day
  • Day-level forecasts for staff planning
  • Permissions per location: general managers see their locations, leadership sees everything
  • Answers to questions, without anyone having to build a report first

That is exactly what Kiosa is built for. One View brings POS and labor data from all locations together at a glance, with a morning briefing, early-warning signals and a location benchmark. The AI partner makes this data accessible: you ask in the chat as you would ask a controller and get answers with real numbers and their source. Every morning it gives you at most five tasks and prepares what you then approve. More on the One View and AI partner pages.

Kiosa connects to the POS systems OktoPOS and Hypersoft, and to the workforce systems gastromatic, e2n and ordio. What this looks like for your type of operation is shown on the pages for quick-service restaurants, restaurant chains and franchise.

From spreadsheets to a system: how to go about it

The switch rarely happens overnight. A realistic sequence:

  1. Clarify data sources. Which POS and which workforce system runs at which location, and what access do you have? The rollout time depends on this.
  2. Map locations. Every location in the POS and in the workforce system is mapped to a location in the system.
  3. Define KPIs. What is your target labor cost percentage, what is a comparable sales per labor hour? These values come from your own data, not from studies.
  4. Check a comparison period. Do the numbers match what you know from your POS and workforce system? Only then do you rely on them.
  5. Introduce the rhythm. Briefing every morning, location comparison weekly, reconciliation with the P&L monthly.

Example: Mama Trattoria, 10 locations

Mama Trattoria is a Hamburg restaurant group with ten locations and part of Kiosa's founding family. Sven Schneider helped build the group from zero to ten locations. With every new site the manual reporting effort grew, and the system that had worked for two locations was no longer fit for ten. That is where Kiosa came from, first for our own restaurants.

Today Mama Trattoria brings POS and labor data from all locations together in one shared view and compares the ten restaurants using the same logic. We only publish results once definition, measurement period and derivation are documented. More in the case study.

What it costs

One View costs €99 per location per month, with no setup fee. The AI partner is included. For ten locations that is €990 a month. Inventory (+€49), Invoices, Scheduling and Loyalty (+€99 each) are added as you need them; the full stack is €445 per location. 12-month minimum term, then renewal for 12 months at a time. The price calculation for 5, 10 and 20 locations is on the restaurant chains page.

See pricing for the full breakdown.

Everything on Managing multiple locations

Related on kiosa.ai:

From analysis to action

What this is about: a guide to KPIs, location comparison and management rhythm once you run several locations.

Put it into practice: Bring all locations together in Kiosa One View

FAQ

From how many locations is a central view worth it?

The benefit starts at two locations; from three, the manual effort without a central view becomes noticeable. Kiosa is built for operations with 1 to 20 locations.

Which POS and workforce systems can Kiosa connect to?

POS: OktoPOS and Hypersoft. Workforce systems: gastromatic, e2n and ordio. We don't list other systems as integrations. If you use a different system, we clarify in the demo call whether and how it can work. Details are under integrations.

How long does setup take?

That depends on the number of locations, the access you have and the data quality. First we clarify the data sources and the mapping of locations, then we set up the connections and check a comparison period with you.

Can general managers see only their own location?

Yes. General managers see their locations, leadership sees all of them. Everyone sees only what their permissions allow.

Is the system GDPR-compliant?

Yes. Kiosa is GDPR-compliant, the data is stored encrypted on servers in Germany and belongs to you.

What if a location uses an unsupported system?

Then that location can't currently be connected automatically. Raise it in the demo call and we'll tell you honestly what works today and what doesn't.


Your next step

If you run three or more locations and still merge numbers by hand on Mondays, this is the simplest place to start. In a demo call we show you One View and the AI partner with real numbers from a live operation and work out with you what it costs for your locations.

Book a demo call →

Sven Schneider

About the author

Sven Schneider — Founder of Kiosa and Ragazzi Concepts. 15 years in multi-unit restaurants; helped grow Mama Trattoria from 0 to 10 locations in Hamburg.

Kiosa Dashboard

All your numbers. One view. Instantly.

What you just read, Kiosa does automatically: every day, for every location, without you having to piece anything together.

Book a demo call
All articles

Data: Kiosa Gastro-Index (in German): 269,448 venues across Germany, Austria and Switzerland, measured.