Three branches or twelve, on one account.
A group in Kochi is usually one brand run out of a room above the busiest of its branches. The switcher in the header puts a single branch in front of you on nearly every screen — and a named handful ignore it and read the whole business, with a badge saying so. Here is where that line falls, screen by screen.
- One brand, one account, three to twelve branches
- A role per branch, granted at one and withdrawn at another
- Submitted at the branch, approved and locked at head office
The call at half eleven.
Nobody in a group disputes the number. They dispute whose number it is, and against what.
The owner’s morning is a WhatsApp group with four managers in it and photographs of drawer counts. At half eleven comes the call asking why Vyttila’s Saturday was down — down against Kaloor, or against Vyttila’s own last four Saturdays, or against the figure someone read off a different screen an hour ago.
One screen answers that, and only one. Intelligence · Locations deliberately sends no branch filter at all and prints the branch table: net sales, orders, average order value, refund rate and returning, one row a branch. The branch you happen to have in the switcher is highlighted in its own row, so you can see where you were standing when you asked.
A branch under thirty paid orders in the range is marked low sample and held out of the ranking, so a quiet Tuesday never tops the table on a percentage. A branch that sold nothing in the range is still on the table, at zero, rather than quietly missing. Read the rest of Business Intelligence.
One branch in front of you, and the screens that ignore it.
The switcher is not a filter you set and forget. It is where the boundary lives, and the product decides which side each screen is on rather than leaving that to whoever logged in last.
Reads the whole business
- The branch comparison table in Intelligence
- Customers, across every branch they have ordered from
- Workforce
- Data quality
- The audit log
- Every rewards screen — the programme, coupons, milestones and campaigns
Reads the branch in the switcher
- Reports — orders, payments, items and taxes
- The dashboard, including today’s running totals
- The P&L tab
- Live operations
- The daily close list, headed ‘Last 14 days at this location’
- The counter, the kitchen screen and menu availability
The left column is not a convention. Each of those screens prints the words ‘Org-wide — not affected by the location switcher’ where you would otherwise look for the branch name. On the right there is no page-local override and no ‘All locations’ aggregate anywhere in the admin, which is a decision rather than a gap: Dashboard & Reports is one branch at a time and says so, and the group-wide read is Business Intelligence, only Business Intelligence. Worth knowing on day one rather than in week three.
Who may do what, and at which branch.
A person does not hold a role here. A person holds a role per branch, and the grant row is unique on the person and the branch together.
A supervisor at two branches
Weekdays at Kaloor, Sundays on the counter at Panampilly Nagar. The same person can be allowed to take a refund at Kaloor and refused it at Panampilly Nagar, because each grant carries its own extra permissions and its own denied ones. Effective access is the role, plus the defaults, plus what was added at that branch, minus what was withdrawn at that branch.
A manager who asks for the group
Someone assigned to three of the five branches who opens an org-wide screen is narrowed to their own three rather than shown the group. Asking for a branch they are not assigned to is refused outright rather than returned empty, so a blank screen never has to be interpreted.
Month end, submitted and locked
The close is one row per branch per business date, moving from open to submitted to approved to locked. The person who submitted it and the person who approved it are both on the row, and reopening one requires a reason that stays there.
Locking is its own permission
Separate from managing the close, which is exactly the split a group needs: five branch managers submit, one person at head office locks. A locked date refuses backdated finance edits from then on while orders and refunds at that branch carry on as normal.
The permission model underneath all of this is Staff & Roles; the month-end rows are Daily Close. Everything a group decides about access — who approves a close, who publishes an SOP, who sees org-wide numbers — is layered on the role a person holds at that one branch.
Written once at head office, previewed at every branch.
A new fire-safety check has to reach five branches this week — except Kakkanad already wrote its own version, and nobody wants to flatten it. Publishing shows you that before it writes anything.
Asset matching is forgiving on purpose. The category is compared trimmed and case-insensitive, so ‘Cold storage’ at Kaloor and ‘cold storage’ at Vyttila are the same category and both branches get the check — one branch spelling its equipment differently is not a reason for a check to go missing there.
The other head-office channel is the Team Board. A shift note belongs to the branch the writer is signed in to. An announcement with no branch on it reaches every location, and only an organization owner may post one or moderate one — so the one-to-many channel is permissioned rather than open to anyone with a login.
Attendance & Routines owns the SOP and the checks it produces. Team Board owns the notes and the announcements.
The module that lets branch two exist.
Multi-Branch Controls has no screen of its own. What it does is permit a second branch at all, and hand out the two permissions this whole segment turns on.
A branch is not created by a setting. Both paths that create one are checked against the same branch ceiling, and a branch you switch off keeps occupying its slot until the ceiling moves. Pricing follows the same shape — every plan is priced per location, per month, so five branches is five times and there is no group licence to negotiate for.
Menu overrides
One catalog sits behind every branch, which is what makes an override mean something rather than being a second menu to maintain. A dish switched off at Edappally because the supplier missed a drop keeps selling at the other four, and an attempt to punch it at the Edappally counter is refused there.
What an override can be
A menu section can be switched off or reordered for one branch. A choice group can be turned off at one branch and reset back to the global template when that branch no longer needs its own version. On or off, order, and a stock count — that is the whole vocabulary, and it is deliberately smaller than a second price list.
The second permission is SOP publishing, which is the preview above. See Multi-Branch Controls for the ceiling and the two permissions, and Menu & Catalog for the one catalog they are written against.
What each branch keeps for itself.
Each branch is set up on its own tabs — info, hours, tables, printing, order options, team, SEO — and carries its own settings row underneath them.
- Whether pickup runs there, and which payment methods it takes
- The UPI account that branch collects into
- Its own prep times, and its busy and critical buffers
- Its receipt printer address, port and paper width
- Whether express pickup runs at that counter
- Whether it takes delivery at all, and its own delivery prep time
A branch can also override the brand where it has to — its display name, the name printed on its receipts, its phone, email, logo and time zone. Anything it leaves blank falls back to the organisation’s.
Four modules are switched on one branch at a time: Local SEO Pages, Host & Tables, Digital Menu Boards and Team Board. Everything else, once bought, is on for the whole business. For a group that is the difference between the flagship on Marine Drive, which wants a waitlist and a screen over the counter, and the express counter at Kakkanad, which wants neither.
Money is kept once and pointed at branches. UPI IDs live on the business and each branch is aimed at the one it collects into, so a group can run a single collecting account or one per branch without keeping two systems. The wallet is the organisation’s, with a table under it reading sales, gross collected, platform fees, gateway fees and net for each location, inactive branches badged as such.
Organization Admin is where the tabs and the module switches are. Payments & Wallet is where the per-location table is.
One guest, whichever branch they walk into.
A guest earns points at the Bypass branch on Friday and spends them at Marine Drive on Sunday, and nothing has to be reconciled between the two.
One points balance
The points ledger carries the guest and the organisation and no branch at all. There is one balance for the business, so a branch never has to decide whether to honour points earned somewhere else, and no branch ends the month owed anything by another.
Where rewards do split
The programme, the coupons, the milestones and the campaign audience are one list for the whole business. A daily deal is the exception: it is raised against one branch and will not save without one, which is what makes a Tuesday offer at Vyttila possible without touching the other four.
One area, one branch
Two of your branches both want to answer the search for Kakkanad. An area slug is a public URL owned by exactly one branch, so claiming one a sibling already holds is rejected when you save it, and the message names the branch holding it.
A bounded number of them
Twenty-four areas a branch and ninety-six across the business, which is the ceiling on how many near-identical pages a chain can put out. Two spellings of one place fold to a single page and the loser redirects to the winner rather than 404ing, and each branch’s SEO fields have a seven-day cooldown.
Rewards & Deals holds the ledger and the deal. Local SEO Pages holds the areas and the rule that stops two of your own branches bidding against each other for one of them.
What a group cannot do here.
Multi-branch pages in this market promise a familiar handful of things. These are the ones this product does not do, listed here so the answer arrives before the demo rather than after it.
- Move stock between branches. There is no transfer, no indent and no central kitchen — a stock count and a purchase order belong to the branch that raised them.
- Charge a different price for the same dish at two branches. Branch-level menu control is on, off, reorder and a stock count.
- Run a second brand out of the same head office. The ceiling counts branches of one organisation, and an organisation carries a single storefront, logo and domain, so your other brand needs its own account, its own ceiling and its own bill.
- Franchise billing. There is no royalty calculation, no revenue share and no fee split. A group of branches you own is the shape this supports.
- Show every branch’s close, drawer and variance on one board. Each close list is the branch in the switcher, fourteen days at a time.
- Give you a consolidated P&L or a consolidated GST return. The group-wide read reports net sales, orders, average order value, refund rate and returning per branch, and stops there.
- Add branches free. The ceiling is checked on every create, a switched-off branch keeps its slot, and every plan is per location, per month.
Where a group needs one of them, tell us on the form below. Better argued before the second branch is set up than after five of them are running.
Book a RestoMama demo
Tell us about your restaurant and the workflows you want to launch first.
- One replyA person from the team, not an autoresponder sequence.
- One serviceWe walk your own dinner rush end to end — bill, KOT, payment, dispatch, day close.
- No hardwareIt runs in the browser on the machines and printers you already have.
See a real service, end to end.
We will take one dinner rush the whole way — ring a bill, print the KOT, call the token, mark the payment, dispatch the order, pay the agent and read the day close. On your menu, with your zones, in about thirty minutes.
- Billing and the counterOrder, modifiers, receipt, token
- The kitchen screenKOT routing, stations, prep state
- Payments and closingUPI, card, cash, wallet, day-end
- Dispatch and payoutsZones, assignment, tracking, settlement