Multi-venue operations: what to centralise

Multi-venue operations raise a question that a single restaurant never has to answer: what should be decided once, for every venue, and what should be decided in each venue by the people who run it? Get it right, and a group gains the advantages of size, such as better supplier terms, consistent standards and a clear view of the numbers, while each venue keeps the life and local knowledge that made it work. Get it wrong, and the group either becomes a set of separate restaurants that happen to share an owner, or a head office that tries to run every kitchen from a spreadsheet.

There is no single answer for every group. A chain of identical cafés will centralise more than a collection of distinct restaurants under one owner. But the same pattern appears in almost every successful group. A handful of things are run from one place, because doing them once is cheaper, safer or more consistent. A handful must stay local, because they depend on knowing the guests, the team and the night.

This guide sets out the four things worth running from one place, the three that must stay local, and a simple test for telling them apart. It covers how to centralise without crushing the venues, the role of consolidated reporting and one system across venues, and the order in which most groups should make the changes.

A single restaurant is run by a few people who see everything. The owner knows the suppliers, the chef knows the recipes, the manager knows the regulars. When a second and third venue open, that knowledge has to be shared or copied, and the people who held it cannot be everywhere at once.

Every group answers the question, whether deliberately or not. A group that never decides ends up with each venue doing everything its own way, with no shared buying, no comparable numbers and standards that drift apart. A group that centralises everything ends up with venue managers who cannot change a special without asking head office. Both are expensive.

A simple test separates what to centralise from what to keep local. Ask three questions about each activity.

Centralise where scale or consistency matter and local knowledge does not. Keep local where local knowledge matters most. Where all three matter, centralise the framework and leave the decisions inside it to the venue.

Applied across most groups, the test points to four things worth running from one place:

Each one gains from scale or consistency, and none depends on knowing what is happening in a particular dining room tonight. The rest of this section looks at each in turn.

Centralised purchasing means agreeing suppliers, products and prices once for the whole group, rather than each venue negotiating its own. It is usually the quickest gain from becoming a group, because suppliers will offer better terms for larger, more predictable volumes, and because one person who knows the market well can negotiate better than several managers who each buy a little.

This is the restaurant version of supply chain management: deciding where goods come from, on what terms, and how they reach each kitchen. Centralise the agreement, not necessarily the ordering. Each venue can still order what it needs, when it needs it, from the agreed suppliers at the agreed prices. That keeps the advantage of scale without forcing a head office to guess each kitchen's needs.

Two risks come with centralised purchasing. The first is losing good local suppliers, such as a baker or a fish merchant whose quality is the reason guests come. Leave room for them: a short list of approved local suppliers that venues can use alongside the group's main ones.

The second is ordering that stops matching each venue's trade. A central buyer who sets standing orders for every venue will over-supply quiet sites and under-supply busy ones. Keep the ordering with the people who know the kitchen, and the terms with the people who know the market. Our guide to restaurant supplier management covers the wider process.

Consolidated reporting brings every venue's numbers into one view: sales, covers, spend, costs and the other measures the group watches, side by side and added together. It is what lets an owner with five venues see the business as a whole, spot the venue that is drifting, and compare like with like.

It only works if the numbers are measured the same way everywhere. A cover must mean the same thing in each venue, sales must be counted the same way, and costs must be allocated consistently. Agree those definitions centrally, write them down, and do not let venues change them without discussion.

The purpose of consolidated reporting is questions, not league tables. A venue with lower spend per head may be in a cheaper neighbourhood; one with higher labour cost may open longer hours. The group view shows where to look; the venue manager explains what is happening.

Report the same few measures for every venue, every week, with a short summary for the group. Highlight exceptions rather than showing everything. Our guide to restaurant KPIs worth tracking every week sets out a list that works for each venue and for the group.

Alongside reporting, the core of finance is usually best run from one place: paying suppliers, payroll, accounts, tax returns and cash management. These benefit from scale and consistency, and they need skills that most venue managers do not have and should not need.

Venues still own the numbers they influence: their sales, their rota, their food cost. The finance team owns the systems that record and pay. Keep the line clear, so that nobody in a venue is chasing an invoice when they should be running service.

One system across venues means every venue uses the same tools for bookings, menus, orders, the kitchen, guests and reporting, set up in the same way. It sounds like a technical choice, but it is really an operational one. Without it, consolidated reporting means stitching together exports from different systems, staff who move between venues have to learn new tools, and a change made at one venue has to be repeated by hand everywhere else.

With one system, a menu can be copied from one venue to another, a guest is recognised wherever they book, reports can be compared directly, and a manager covering another venue already knows how everything works.

One system does not have to mean identical setups. Each venue can have its own floor plan, opening hours, menus, prices and booking rules inside the same system. What should be the same is the structure: how dishes are named and categorised, how services are defined, how guests are recorded and how covers are counted.

Decide that structure centrally before rolling the system out to every venue. Changing it later, once each venue has built its own habits, is far harder. Our guide to choosing restaurant software without a demo haze covers how to choose.

Standardising across venues means agreeing, once, the things that must be the same everywhere: recipes and portions for shared dishes, food safety and allergen procedures, brand and guest-facing standards, health and safety, and the core of training. These protect guests, the brand and the business, and they should not depend on which manager is on duty.

Standards are the framework within which venues make their own decisions. A shared recipe sets the portion and the method; the venue decides how many to prep tonight. A shared allergen procedure sets the five steps; the venue's servers carry them out.

Not everything needs a standard. Focus on the things where inconsistency causes real harm. Food safety and allergen procedures come first, because a mistake can hurt a guest. Recipes and portions for shared dishes come next, because they drive cost and guests expect the same dish to be the same. Brand standards, such as how the phone is answered and how guests are greeted, follow.

Write each standard down, keep it short, and make it easy to find. A standard nobody can find is not a standard. Our guide to restaurant operations: the week as a system covers how standards fit into the routines of each venue.

The same test points to three things that must stay with the venue:

Each one depends on local knowledge that head office does not have and cannot get quickly enough. Centralising them makes them slower and worse.

The rota depends on knowing the venue's trade, its team, their skills and their lives: who can work late, who is training, who is good on the grill, who needs Saturdays off this month. A head office can set the budget and the rules, such as labour cost targets and legal limits on hours, but the rota itself belongs to the venue.

The same goes for hiring the team, within group standards for pay and contracts. A venue manager who chooses their own team owns its performance. One who is sent staff by head office does not.

Guests have relationships with venues, not with groups. They know the manager, the server who remembers their order, the chef who comes out to say hello. They come because of how the venue makes them feel. That relationship is built locally and must be managed locally.

The same applies to the neighbourhood: local events, nearby businesses, the school around the corner, the community the venue serves. A central marketing plan can set the brand and the calendar, but each venue needs room for its own local promotions and partnerships.

During service, decisions have to be made in seconds: whether to seat a walk-in, how to handle a complaint, whether to 86 a dish, when to call in an extra pair of hands. These cannot wait for head office, and they depend on what the manager can see in the room.

Give venue managers clear authority for service decisions, within standards for things like comps and refunds. A manager who has to phone someone before offering a free dessert to an unhappy guest has lost the moment.

Menus sit between central and local. Shared dishes, recipes and the structure of the menu often benefit from being set centrally, especially in a chain with a single brand. But specials, local dishes, seasonal changes and prices for a particular neighbourhood often benefit from local input.

A common approach is a core menu set centrally, with room for a few local dishes and specials. Prices can be set by the group with local adjustments where costs or guests differ. The test still applies: centralise what gains from consistency, keep local what depends on local knowledge.

Marketing also sits in the middle. The brand, the website, group-wide campaigns and the guest database gain from being managed centrally. Local events, partnerships and the tone of each venue's social media often work better when they come from the venue.

Divide it clearly. The centre owns the brand and the tools; the venue owns its local voice and its community. A central email to every guest in the group should not clash with a venue's own message to its regulars.

The main risk of centralising is that venues lose the ability to respond to their own guests and teams. Managers who feel that every decision is made elsewhere stop taking responsibility, and good ones leave. The group becomes slower and more uniform, and loses what made each venue special.

Centralise the minimum that gains from scale and consistency, explain why, and give venues clear authority over everything else. Ask venue managers what slows them down, and fix it. A central function exists to serve the venues, not the other way round.

As a group grows, someone has to hold it together: an operations lead or area manager who visits each venue, checks standards, supports managers and connects the venues with the centre. Their job is not to run each venue, but to make sure each venue is run well, and to carry good ideas from one to another.

A good operations lead spends most of their time in venues, not in the office. They read the consolidated reports to know where to go, and then they go there.

Most groups should not try to centralise everything at once. A sensible order is:

Each step makes the next easier. Reporting depends on one system; purchasing depends on knowing what each venue uses.

At two venues, the owner usually runs the centre personally: buying, reporting and standards, with a manager in each venue. The priority is one system and shared standards, so the second venue does not become a different business.

At five venues, the centre needs people: an operations lead, someone for finance, perhaps a buyer. Consolidated reporting becomes essential. At twenty, the centre is a team with its own budget, and the risk shifts from too little central support to too much. Review the balance every year as the group grows.

Some groups are collections of different restaurants rather than copies of one format: a bistro, a wine bar and a café under the same owner. These groups centralise less: purchasing, finance, systems and safety standards still gain from being shared, but recipes, menus and brand standards may be entirely local.

The test still works. Ask, for each activity, whether scale, consistency or local knowledge matters most. In a group of different restaurants, local knowledge matters more often.

Measure centralisation by its results. Did centralised purchasing lower food cost without lowering quality? Did consolidated reporting help catch problems earlier? Did one system across venues make it easier to move staff and copy menus? Did standards reduce incidents and complaints?

Ask the venue managers too. If they feel supported, the balance is probably right. If they feel controlled, it has gone too far.

Here is an illustrative group of four restaurants under one owner. Before any changes, each venue bought from its own suppliers, used its own booking and till systems, and sent the owner a spreadsheet each month in its own format.

Food cost fell across the group, the owner spotted a struggling venue within weeks rather than months, and the managers said they had more time for their guests.

servearound is built for one system across venues. A network holds every venue, each with its own floor plans, opening hours, menus, prices and booking rules, and staff can be assigned to the venues they work in. Menus can be copied to other venues, where they arrive switched off until each venue is ready, and every guest has one record across the group, keeping the highest tier earned at any venue.

For consolidated reporting, the network dashboard shows revenue, covers, spend per cover and no-show rate for all venues or one, with trends against the previous period, and network transactions total what every venue collected, converted to one currency at each day's rate. Campaigns can be seen across every venue in one list. servearound does not handle purchasing, stock, rotas or payroll. Pricing is per venue, per month: see pricing and Analytics.

Food safety and allergen standards, then one system across venues. Everything else is easier once those are in place.

The supplier terms, yes, once there is enough volume. The day-to-day ordering usually works better with each kitchen.

The rota and the team, the relationship with guests and the neighbourhood, and decisions during service.

Every venue's key numbers in one view, measured the same way, so the group can be seen as a whole and venues compared fairly.

So that reports can be compared directly, menus and settings copied, guests recognised everywhere, and staff can move between venues without relearning.

Centralise the minimum, explain why, and give venue managers clear authority over everything else.

Usually from three or four venues, when the owner can no longer visit every venue often enough.

Yes, but such groups centralise less, because local knowledge matters more for their menus and brands.

Multi-venue operations work best when a group centralises the four things that gain from scale and consistency, purchasing terms, consolidated reporting and finance, one system across venues, and standardising across venues for safety, recipes and brand, and keeps local the three that depend on local knowledge: the rota and team, the guest relationship, and decisions during service.

Use a simple test for everything else: does it gain from scale, does it need to be consistent, and does it depend on local knowledge? Centralise in a sensible order, starting with safety standards and one system, give venue managers real authority, and measure the result by whether venues feel supported rather than controlled.