Your Second Branch Exposes What Your First Branch Was Hiding
One branch can run on the owner's memory. Two branches can't. The problems were usually there already; the second location just makes them visible.
Illustrative scenario: two months after the second branch opens, a regular complains that the same sandwich costs more there. The new branch manager has quietly increased a portion because guests asked for it. Each branch keeps its own spreadsheet, so the weekly sales comparison takes a whole evening. A discount nobody can explain shows up at the first branch. And the owner's phone rings all day, because every question between the two managers goes through them.
It's tempting to blame the new branch. More often, the second location has simply removed the thing that held the first one together: the owner standing in it.
What the first branch was hiding
- The menu lived in someone's head. Recipes and portions were “how we do it”, not written down.
- Prices changed informally, by word of mouth, and nobody recorded when or why.
- Permissions were based on trust. Whoever was on shift could do whatever was needed.
- Reports were the owner's memory of a good or bad week.
- Problems were solved in person, so there was no record of them.
None of this is a failure when you have one location and you're there every day. It becomes one as soon as you can't be in both places at once.
Decide what is central and what is local
The goal isn't to make every branch identical. It's to decide deliberately which things are shared and which are each branch's call, instead of letting them drift apart.
| Usually central | Menu items and recipes, portion sizes, how reports are defined, roles and approval rules, approved suppliers |
|---|---|
| Often branch-specific | Prices where costs or local markets differ, opening hours, staffing, delivery areas, local specials |
| Decided centrally, carried out locally | Stock requests, transfers between branches, cash handling and end-of-shift checks |
Different prices across branches are perfectly reasonable when rent, delivery areas or local competition differ. What causes trouble is prices that differ by accident. Decide them, record them, and make sure guests and staff see the same price you meant to set.
Practical steps for the first three months
- Write the menu once. Keep a single list of items, recipes and portions that both branches use, and change it in one place.
- Agree who can change a price and how a change is announced. Keep the date and the reason.
- Define your reports before comparing them. “Sales” should mean the same thing in both branches, for example after discounts and before delivery commissions.
- Set a weekly comparison rhythm: sales, average ticket, discounts, voids and food cost, side by side.
- Put stock requests and transfers in writing, with an approval step, so stock doesn't move between branches on a phone call.
- Give each manager clear decision rights, and step out of the middle. If two managers need you to pass messages between them, the process is missing a step.
Signs your branches are ready to grow further
- Both branches use the same written menu and recipes.
- Every price difference between branches was decided, not discovered.
- Managers can approve the things they're responsible for without calling you.
- You can compare last week's branch results in minutes, not an evening.
- Stock moving between branches is requested and approved in writing.
How Zad. Plus supports multiple branches
Zad. Plus runs every branch from one account. You keep one chain menu, set a price for each branch where needed, and publish new items to every branch at once. The command centre shows today's sales, expenses and stock value, filtered by branch and period, with branch performance and ranking against targets, and a consolidated profit and loss view by branch.
Branches request stock, head office approves and sends it, and a distribution board shows every request by status. Each branch has its own safe alongside the head-office safe. Staff accounts have a role and a home branch, with access to more than one branch where needed.
The tools make the decisions visible and easier to keep. You still have to make them.