---
title: "The second branch: growing without losing control | GoSufra"
description: "What to centralise and what to keep local when you open another site, how to compare branches fairly, and the signs that the timing is wrong."
url: "https://gosufra.com/en/blog/multi-branch/"
language: "en"
source: "https://gosufra.com"
---
# The second branch: growing without losing control

What to centralise and what to keep local when you open another site, how to compare branches fairly, and the signs that the timing is wrong.

2026-08-17 · 8 min read

![Illustration of three branches connected to one hub](https://gosufra.com/blog/multi-branch.svg)

## Key points

- A second branch exposes every unwritten procedure you were performing in person.
- Centralise menu, recipes, pricing and roles; keep stock and shifts local.
- Compare branches on relative metrics, never on total sales.
- Do not open a second site until the first runs two full weeks without you.

The first branch works because you are in it. You notice the plate that ran late, you correct the waiter, and you know the cheese is nearly out because you saw it.

The second branch exposes that fact without mercy: **you were the system**.

## A test before the decision

Before signing a second lease, run one test: **disappear for two full weeks.**

No visits, no daily call to the manager. If you come back to steady sales, unchanged quality and controlled stock, you are ready. If you come back to fix what piled up, a second branch will multiply the chaos, not the profit.

## What is centralised and what stays local

This is the most important design decision in expansion:

| Element | Central | Local |
| --- | --- | --- |
| Menu and recipes | ✅ |   |
| Price structure | ✅ | limited, with approval |
| Roles and permissions | ✅ |   |
| Brand and packaging | ✅ |   |
| Chart of accounts | ✅ |   |
| Stock and balances |   | ✅ per branch |
| Suppliers | ✅ negotiating frame | ✅ local receiving |
| Shifts and staff |   | ✅ |
| Promotions | ✅ frame | ✅ execution |
| Tax rate |   | ✅ per branch |

**The rule:** anything touching product identity is centralised; anything touching daily operations stays local.

A branch that can edit a recipe will be making a different product within two months, and you will lose the reason customers trust the name.

## Comparing branches fairly

Comparing branches by total sales is unfair and misleading: a bigger site in a busier location will always win.

Compare on relative metrics:

| Metric | Why |
| --- | --- |
| Sales per seat | Neutralises floor size |
| Sales per labour hour | Neutralises team size |
| Food cost percentage | Exposes portioning and receiving discipline |
| Prime cost | Overall operational health |
| Average check | Quality of upselling |
| Discount and void rate | Discipline and integrity |
| Average rating | Consistency of experience |

A branch with lower sales and better prime cost may be **more successful** than a larger one that consumes everything it sells.

## Three predictable problems

**1. Quality drift.** Solve it with written and photographed standards: portion weights, a picture of the finished plate, a target prep time. Review with numbers, not impressions.

**2. Stock leakage.** It grows with distance. The remedy is automatic deduction from recipes, weekly counts on high-value lines, and an audit trail on every manual adjustment.

**3. Permissions.** A branch manager needs enough access to run the site, not enough to rebuild the menu. Set roles precisely, and separate who approves a discount from who applies it.

## Move the competence before the brand

The common expansion mistake is moving the name without moving the people. Hire the new branch manager **two months before opening** and run them inside the first branch. Whoever opens the new site should have lived enough full service days in the original to know what “right” looks like.

## The technical shape

Two branches tolerate two spreadsheets on two machines. Four do not: you will spend your days assembling numbers that disagree.

What you need is **one database with a per-branch view**: a shared menu, separate stock and staff per branch, reports that place branches side by side, and permissions defining who sees what. That is what the multi-branch dashboard in GoSufra is built on — and because tax, stock and shifts are configured per branch, you do not need a separate installation for each site.

## Signs the timing is wrong

- The first branch depends on your daily presence.

- Procedures exist only in your head.

- Current margin is thin — expansion multiplies losses as readily as profits.

- No manager is ready internally.

- The last three months have been unstable.

A second branch does not repair a struggling first one. It multiplies whatever you already have.

- expansion
- branches
- management
- growth

## In the product

### [Analytics, Branches & Control](https://gosufra.com/en/features/analytics-and-reports/)

Explore

## Run all of this from one system

POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start.

[Create your free account](https://app.gosufra.com/register?lang=en)

## Related articles

![Illustration of bar charts with a trend line](https://gosufra.com/blog/restaurant-kpis.svg)

Analytics 2026-07-20 · 9 min read

### [Eleven numbers you should see every morning](https://gosufra.com/en/blog/restaurant-kpis/)

A practical restaurant dashboard: sales, average check, food cost, labour, prime cost, discounts and voids — with the formulas, the ranges, and what to do when they move.

Read article

![Illustration of neatly stacked inventory crates](https://gosufra.com/blog/inventory-control.svg)

Inventory 2026-05-18 · 9 min read

### [Inventory control: stopping leakage before it reaches the P&L](https://gosufra.com/en/blog/inventory-control/)

A practical stock system for restaurants: purchasing and receiving, count cadence, batch and expiry tracking, and reorder points that prevent running out mid-service.

Read article

![Illustration of a checklist with ticked boxes](https://gosufra.com/blog/opening-checklist.svg)

Growth 2026-04-06 · 9 min read

### [A thirty-day checklist for opening a restaurant](https://gosufra.com/en/blog/opening-checklist/)

A week-by-week plan for getting a restaurant ready: menu and costing, suppliers, systems and hardware, training and a soft launch — in an order that does not conflict.

Read article

[← All articles](https://gosufra.com/en/blog/)

[Contact us](https://wa.me/201132421261)