Set once at the brand — override only where reality differs
Here is the trap. Everything that works at your first outlet was built assuming there would only ever be one outlet. The menu lives in one place because there was only one place. The price list, the staff list, the tax setup — none of it was designed to exist twice. The moment you duplicate it, you don't get a copy. You get two originals. And two originals start drifting apart from day one.
What drift actually looks like
Drift is not dramatic. It is a slow accumulation of small mismatches that nobody notices until a customer or an accountant does.
Picture a busy Tuesday at your first outlet. Your dairy supplier raises rates, so you bump the price of three paneer dishes before the dinner rush — two minutes on the terminal in front of you, done. The second outlet, across town, hears nothing. It keeps billing the old price for weeks, until a regular who visits both locations asks the manager why the same dish costs less there. Now you are not just correcting a price. You are explaining one.
Or take the new dish. Your chef at the first outlet perfects a seasonal starter. You add it, it sells. But it exists only where it was added, because "putting it on the menu" now means entering it twice, and the second entry never happened. Six months in, your two outlets are serving noticeably different menus — without anyone ever deciding they should.
The quieter versions hurt just as much. A cashier resigns and gets removed from one staff list but not the other. A tax change is applied at one outlet in April and at the other in June. And reporting under drift means exporting two sets of numbers every month and adding them up by hand in a spreadsheet, hoping the categories still line up. They rarely do for long — because the menus themselves have diverged underneath them.
The fix is structural, not effort
The tempting answer is discipline: "we'll just remember to change it in both places." Discipline fails on the first busy Tuesday, which is exactly when prices change. The durable answer is to decide, before outlet two opens, which things belong to the brand and which genuinely belong to the location.
| Belongs to the brand | Stays local to the outlet |
|---|---|
| Menu structure — categories, dishes, descriptions | Prices where rents and costs genuinely differ |
| Recipes and portion standards | Dining-area layout and table map |
| Tax setup and billing rules | Printers and billing devices |
| Roles and what each role may do | The local staff who fill those roles |
Everything in the left column should have exactly one home, which every outlet reads from. Everything in the right column is allowed — expected — to differ, because a rooftop in Koregaon Park and a food-court counter in a mall do not share a rent slip.
A simple test for every setting: if you would want a change to reach every outlet automatically, it is brand. If it only makes sense at one address, it is local. Anything you cannot place is almost always brand — local exceptions are easy to add later; un-merging two drifted menus is not.
What "built in" should mean
Once you have drawn that line, the system you run on should enforce it, rather than depending on you to. Four capabilities do most of the work:
- One menu, read by reference. Outlets should not hold copies of the menu; they should point at the brand's menu. Change a dish once — name, recipe, description, removal — and every outlet is updated the moment you save. There is no "second entry" to forget.
- Price overrides, not price copies. The brand sets the default price. An outlet that genuinely differs overrides only the dishes that differ. Everything it has not overridden keeps following the brand automatically, so a brand-level revision still flows to nine dishes even if the tenth is locally pinned.
- Grouping, so overrides scale. Cities differ more than neighbouring outlets do. If you can group outlets by region or city, one override can price all of Mumbai above all of Pune. You do not repeat the same exception outlet by outlet as you grow.
- One login, an outlet switcher. You should never maintain a second account to see your second outlet. One identity, a switcher to move between locations, and rolled-up views across them — otherwise your own visibility fragments along with your data.
People move between outlets — access should too
The second outlet usually borrows people from the first: your best manager oversees both for the first few months, an accountant reconciles both, a head chef standardises both kitchens. The lazy path is sharing passwords across locations, which destroys accountability — when everyone is "admin," the audit trail names no one. The right shape is one account per person, granted access at the brand level where the role demands it, with specific outlet assignments where it does not. The manager sees both outlets under one login; the new cashier sees exactly one.
The pitfalls almost everyone hits
- Copy-pasting the menu into a second account. This feels like progress on day one and becomes the drift machine described above. If your current system's only path to outlet two is "make another account," that is the moment to change systems — not after the menus diverge.
- Assuming printers and devices carry over. They are physical. The kitchen printer, the billing counter, the KOT routing — each belongs to a room in a building, and each pairs to its own outlet. Budget the hardware and the setup afternoon for outlet two; no software setting removes that step.
- Delaying the structure "until outlet three". Two outlets feel manageable by memory, so the brand-versus-local split gets postponed. But structure is cheapest to adopt when the second menu does not exist yet. At three outlets you are not adopting a structure — you are reconciling three drifted copies while running three restaurants.
Your pre-opening checklist
Before the second outlet bills its first table, sit down for an hour and work through this:
- Confirm the menu, recipes, tax setup, and roles live at the brand level — and that outlet two reads them, rather than holding copies.
- List the dishes whose prices genuinely differ at the new location, and set those as outlet overrides. Leave everything else inheriting.
- Map the new dining areas and tables; they will not resemble outlet one, and they should not.
- Pair the new outlet's printers and billing devices on site, and test a kitchen ticket end to end before opening night.
- Create accounts for new local staff at outlet two only; extend your cross-outlet people (manager, accountant) to both outlets under their existing single login.
- Run one full day's dry rehearsal — order, kitchen, bill, day-end — and check the numbers roll up correctly across both outlets.
The second outlet is where a restaurant becomes a brand. Get the split between brand and local right before you open, and the third and fourth outlets become routine. Get it wrong, and every future outlet multiplies the drift. It is a decision about structure — and it is far easier to make this month than next year.
Built for the second outlet from day one
Zentaro Serve keeps one brand menu that every outlet reads by reference — change it once and every outlet updates. Pricing inherits brand → region → outlet, resolving nearest-first, with outlet-level overrides and even dining-area pricing for an AC hall versus a rooftop. One login gives you an outlet switcher and region roll-ups. Staff can have brand-level access, with specific outlets assigned. When you open the next location, you can copy the kitchen and station setup from an existing outlet. Printers and devices pair for each outlet, as they should. Extra outlets are available as a paid add-on.
Talk to us