Multi-branch restaurant management: a guide for café and restaurant chains
The moment you open a second branch you notice the old setup isn't enough: you enter the menu twice, merge two reports at close, and track which staff work where in a separate spreadsheet. By the third branch it's a management problem.
This post covers the essentials of running several branches: menu and prices, staff and permissions, stock and reporting.
One account, several branches
The first rule of multi-branch management is that branches aren't separate systems but branches of one account. That way reports can be combined, staff can be assigned across branches and supplier accounts are kept chain-wide.
Branches under one account; reports together or apart.
Menu and prices: per branch
Each branch keeps its own menu and prices. One branch can sell an item another doesn't, and your airport branch and neighbourhood branch can charge different prices. The QR menu opens according to the branch of the table scanned.
Items can be added from a shared catalogue, and each branch can adjust name, description, photo, station and price. For bulk updates, menus can also be imported from a spreadsheet (CSV).
Staff and permissions: within branch limits
Each user is assigned to one or more branches. A branch manager runs their own branch and doesn't see the rest of the chain. Permissions are granted by role, one by one: can waiters void items, who sees financial reports, who can change the menu?
Don't let a shared "manager password" go round. Every action should be recorded under the account of the person who took it.
Every action that touches money or access — voids, refunds, permission changes — is written to the audit log with who did it and when. As branches multiply, that log is your assurance for the hours you're not on site.
Stock: transfers between branches
Each branch has its own stock. When one branch sends surplus to another, it's recorded as a transfer: out of the sending branch, into the receiving one. So one branch's count difference isn't really stock that went to another branch.
Reports: together and apart
A chain manager sees reports both branch by branch and combined. When the weekly meeting asks "why is one branch's average bill lower than another's?", the answer is on one screen: best sellers, voids, payment types, waiter performance.
Branches belong in one account, not separate systems.
Bookkeeping: the drawer is per branch, accounts are chain-wide
In bookkeeping each branch has its own cash drawer. Supplier accounts are chain-wide: whichever branch took the delivery, the debt shows in one account. See bookkeeping integration.
New branch checklist
When adding a new branch to the system.
Delivery and multiple branches
Yemeksepeti orders work per branch too: each branch gets its own connection code and orders land only on that branch's till. See the Yemeksepeti integration page.
Frequently asked questions
Which plan includes multiple branches?
Multiple branches are part of the Enterprise plan; extra branches are charged per branch. Current details are on the pricing page.
Can one employee work at two branches?
Yes. A user can be assigned to several branches and can only act in the branches they're assigned to.
Conclusion
Multi-branch management means bringing branches into one account and giving each its own menu, till and team. Once that's in place, opening a new branch isn't rebuilding the system — it's adding one more branch. See ari adisyon's scale features on the features page.