Run Three Restaurants As Cleanly As You Ran One
Every order, menu, stock count, staff record and report in RestioX belongs to a branch. Head office sees the group, a branch sees its own floor, and you decide — setting by setting — what is pushed from the centre and what stays local.
Start Free Trial See pricing1 push
Sends the menu items you select to every branch you tick — with or without their prices
5
Setting groups each branch keeps to itself: hours, holidays, shifts, delivery and tax
0
Exports needed to see the group — sales and tax already consolidate across branches
1 address
A white-label subdomain per restaurant, with a landing micro-site on the same domain
Isolation That Lives in the Query, Not in a Dropdown
Most systems bolt multi-site on as a filter: everything sits in one pile and a select box decides what you look at. RestioX works the other way round. The branch scope is applied to the database query itself, so a Riverside manager who opens Orders, Staff, Inventory or Customers gets Riverside — there is no filter to forget and no URL to edit.
Crossing that boundary is a privilege, not a default. Only a role that has been granted group-wide access can switch branch or open an all-branches view, and the roles are yours to define: a Branch Manager who sees one site, an Area Manager who sees four, an owner who sees everything.
- Orders, KOTs and payments belong to the branch that took them
- Staff, rosters, shifts and attendance stay on their own site
- Stock, suppliers, purchase orders and wastage are counted per branch
- Customer records and order history follow the same boundary
- Reports open scoped to your branch unless your role says otherwise
- Custom roles with granular permissions decide who is allowed to cross
What Head Office Controls, What the Branch Controls
Brand consistency fails in two directions. Too little central control and every site invents its own menu; too much and a manager cannot mark a sold-out special off at 8pm. Here is where RestioX draws the line — and every row below is a real setting, not a philosophy.
| Control | Head office | Individual branch |
|---|---|---|
| Menu structure and items | Builds the master menu and pushes selected items to chosen branches | Receives the push — it does not have to rebuild the catalogue by hand |
| Item prices | Decides per push whether prices are overwritten or left alone | Keeps its own price whenever the push runs without the overwrite option |
| Item availability | Can sync availability with the push so a delisted item goes dark everywhere | Marks a dish sold out for tonight, on its own floor, without calling anyone |
| Price changes | Schedules a new price to take effect at a future date and time | Sees the new price appear at the scheduled moment — no midnight edit |
| Trading hours, holidays and shifts | Sees which sites are open and which are closed for a holiday | Owns its own opening hours, holiday closures and operational shifts |
| Tax rates and rules | Reads one tax report consolidated across every branch | Applies the rates its own address is actually subject to |
| Delivery settings | Compares delivery performance branch by branch | Sets its own delivery radius, fee and minimum order value |
| Staff, roles and permissions | Defines the custom roles and the permission set behind each one | Hires into those roles and runs its own rota within them |
| Loyalty programme | Sets the earn rules and whether points are pooled across the franchise | Awards and redeems at the counter like any other site |
| Reporting | Opens sales and tax consolidated across all branches, or filtered to one | Opens its own numbers, and only its own |
| Branded web address | Owns the white-label subdomain and the landing micro-site on it | Trades under it |
Everything a Group Needs, Nothing a Single Site Doesn’t
None of this is a separate product you graduate into. It is the same admin you already use, with a branch dimension running through it.
-
Branch-scoped by default
Orders, menus, inventory, staff, customers and reports are isolated per branch at the data layer. Cross-branch visibility is something a role is granted, never something a user stumbles into.
-
Multi-branch menu sync
Select items, tick the target branches, choose whether to overwrite prices and whether to sync availability, then push. One action instead of one admin session per site.
-
Scheduled price changes
Set the new price and the moment it should start. It goes live on its own, so a group-wide reprice does not need anyone awake at 6am.
-
All-branches sales and tax
Consolidated sales and tax reporting across every site, or filtered down to one, without exporting anything into a spreadsheet to add it up.
-
Per-branch settings
Opening hours, holiday closures, operational shifts, delivery settings and tax are configured on the branch, because that is where they are actually true.
-
Franchise-pooled loyalty
Switch pooling on and a balance earned at the airport unit is spendable at the high street unit, while the earn stays attributed to the branch that made the sale. Switch it off and every site runs its own programme.
-
White-label subdomains
Each restaurant can be served on its own branded address, storefront and checkout included, instead of a shared platform URL.
-
Custom roles
Build the roles your structure needs — branch manager, area manager, franchise owner — and give each one exactly the permissions it should have.
Works with
Push a Menu Change to the Branches You Choose
Select what should travel — a whole category, a new seasonal range, one repriced burger — then tick the branches that should receive it. Two switches decide how far the push reaches: overwrite prices, and sync availability.
Leave both off and you have pushed the item and its description while every branch keeps the price it charges and the stock state it is in. That is the difference between a chain and a franchise, expressed as two checkboxes: a company-owned chain usually pushes everything, a franchisor pushes the dish and lets the franchisee price for their own high street.
- Choose target branches per push — never all-or-nothing
- Overwrite prices, or leave local pricing completely untouched
- Sync availability so a discontinued item goes dark everywhere at once
- Copy Menu clones an entire menu into a new branch in one action
- Scheduled price changes go live at the date and time you set
One Number Set for the Group, One for Each Site
Sales and tax reports run across every branch at once, so the group total is a report you open rather than a spreadsheet you assemble on a Sunday. Switch to a single branch and the same report narrows to that site.
It matters most at tax time. A group operating across more than one jurisdiction files from a report that already knows which sale was taxed at which rate, in which branch, on which day — instead of from three exports and a formula somebody wrote in 2022.
A consolidated report is not a branch filter left blank. The all-branches view is a deliberate, permission-gated mode, which is why an unauthorised role cannot reach group numbers by clearing a dropdown.
What Every Branch Keeps to Itself
These are the settings a head office should not be guessing from another city.
- Opening hours Open and close times per day, owned by the branch and respected by the storefront and the till.
- Holiday closures The dates this site is shut. Online ordering and reservations honour them without anyone flipping a switch.
- Operational shifts Named service periods — breakfast, lunch, late — defined to match how this particular site actually trades.
- Delivery settings Radius, delivery fee and minimum order value, set where the drivers and the streets actually are.
- Tax rates The rates this address is subject to, applied at its own tills and rolled up into the group tax report.
- Item availability Take tonight’s sold-out dish off this floor only, without touching the group menu or any other branch.
The First Week of Being a Group
The second restaurant is where good habits either get built or get lost. This is the order the work actually happens in.
-
1
Hour one
Create the branch
Add the site with its address, contact details and currency. From that moment every record it creates carries its branch, so nothing you do next can bleed back into site one.
-
2
Hour two
Copy the menu across
Use Copy Menu to clone your categories, items and modifiers into the new branch in a single action, instead of retyping a hundred and eighty dishes and getting four of them wrong.
-
3
Day one
Set what is genuinely local
Opening hours, holiday closures, operational shifts, delivery radius and fees, and the tax rates the new address is subject to. Five settings, all on the branch, none of them guessed by head office.
-
4
Day two
Hire into roles, not into permissions
Reuse the custom roles you already defined. A Branch Manager at site two inherits exactly the permission set site one uses, scoped to site two — you are not rebuilding an access model per restaurant.
-
5
Day four
Schedule the launch prices
Set the opening price list to take effect at the hour you open. If the introductory pricing is meant to end after a fortnight, schedule that too and stop carrying it in your head.
-
6
Week two
Read the group, not the branches
Open sales and tax across all branches and compare the two sites in one number set. The first honest read of whether site two is a second business or a second location.
Points Earned at One Site, Spent at Another
Turn pooling on and the loyalty balance follows the customer rather than the postcode. Someone who collects points at your airport unit can spend them on the high street, and the earn is still recorded against the branch that made the sale — so the site whose till took the money is the site credited in reporting.
Leave pooling off and each restaurant runs a self-contained programme. That is often the right answer when franchisees own their own customer relationships and settle separately.
- One balance across the group, or one per site — your call
- Earn stays attributed to the branch that made the sale
- Redemption at the counter checks the pooled balance in real time
The Brand’s Address, Not Ours
Each restaurant on the platform can be given its own subdomain, so guests order from an address that carries the brand instead of a shared platform URL with an account id buried in it. The storefront, the menu and the checkout all answer on that address.
Alongside it, a restaurant can publish a landing micro-site — the pitch, the story, the hours, the reservation link — on the same branded domain. A multi-concept group can stand up a page per concept without commissioning a separate website build for each one.
- A branded subdomain per restaurant
- Storefront, menu and checkout all served on it
- A per-restaurant landing micro-site on the same address
Two sites is where the spreadsheets start
Open branch two inside RestioX before the workarounds harden into process.
Three Ways Groups Run on RestioX
The operator opening site two
You already know the menu works. What you do not want is two admin logins, two menus quietly drifting apart, and a Sunday spent adding numbers together. Copy the menu, set the local hours and tax, read both sites in one report.
The franchisor
Protect the dishes, the descriptions and the brand’s address. Leave pricing, hours and staffing to the people who signed the agreement and pay the rent. Push what must be identical, and deliberately nothing else.
The multi-concept group
Different names, different menus, sometimes the same kitchen. Every concept gets its own branch, its own branded address and its own landing page, all managed from a single account.
Multi-Branch Questions, Answered Plainly
Not unless their role says so. The branch scope is applied to the query, so Orders, Staff, Inventory, Customers and reports all return that branch’s records by default. Seeing across sites, or opening the all-branches view, is a permission you grant to specific roles such as an area manager or the owner.
No. There is a master menu you push from, but every push names its target branches, and two options decide how much of it travels: overwrite prices, and sync availability. Leave both off and a branch receives the item while keeping its own price and its own sold-out state.
Yes, as long as the push runs without the overwrite-prices option. That is the normal franchise arrangement: the dish and its description are controlled centrally, and the price is set where the rent is paid.
Schedule it. A price change can be given a future date and time and it takes effect at that moment on its own. You set the new Sunday roast price on Thursday afternoon and it goes live at opening on Sunday.
That is a setting. With franchise pooling on, a balance earned at one location can be redeemed at another, while the earn stays attributed to the branch that made the sale. With pooling off, each site runs a self-contained programme.
Yes. The platform supports a white-label subdomain per restaurant, and the storefront, menu and checkout are served on it. Each restaurant can also publish a landing micro-site on that same branded address.
Ready to Run the Group From One Place?
Branch scoping, menu sync, scheduled prices, pooled loyalty and your own branded address are in RestioX today. Add your second branch and read the whole group in one report.
Start Free Trial