- Choose shared settings
- Apply a local change
- Check both outlets
A central update should not erase an intentional branch exception.
Illustrative decision process, not a product screenshot or customer result.Choosing ordering software for multiple locations requires a clear answer to one question: which branch owns each customer promise? The menu, availability, fulfilment and reports should all follow that ownership consistently.
Map the customer-to-branch decision
Determine whether customers select a branch or the system assigns one using a verified rule. Test an address near a delivery boundary and a customer collecting from a different outlet.
The chosen branch should be clear before confirmation. A correct menu at the wrong outlet can still produce an order the restaurant cannot fulfil.
Define menu and availability scope
Keep a record of shared items and local differences. Ask how central price changes are approved and how a branch marks an item unavailable. Verify that a local change does not unintentionally affect the entire business.
Do not infer independent stock, menu schedules or transfer functions from a multi-location label. Demonstrate the exact requirement.
Test roles and reporting together
| Role | Required view |
|---|---|
| Branch operator | Relevant orders and permitted actions |
| Kitchen team | Correct branch's preparation instructions |
| Dispatch supervisor | Orders belonging to the fulfilment team |
| Owner | Comparable branch records and exceptions |
Have a branch user attempt a prohibited action. Then trace sample orders from two outlets into their reports. This connects access control with operational accuracy.
Plan the next location before signing
Ask what is required to add an outlet: configuration, menu review, users, devices, training and commercial changes. Confirm how a temporary closure or a permanently closed branch is handled.
Use a pilot and a repeatable launch checklist. Copy approved settings deliberately while reviewing local hours, stock and delivery boundaries. Growth should not depend on undocumented setup knowledge held by one person.
Explore Restrova's multi-branch solution, ordering websites and pricing. Use the branch management guide and request a demonstration with two contrasting locations.
Can every branch use the same ordering URL?
That depends on the product and customer journey. A shared entry point can work if branch selection is clear; separate destinations can work if links and management remain consistent. Verify the intended approach.
Should branches share customer records?
Only according to a clear business purpose, access policy and applicable privacy requirements. A central dashboard should not imply unrestricted staff access to personal information.
A practical check: Keep common and local settings distinct
Illustrative scenario: Two outlets share photography but have different opening times and stock. Test one shared update and one local change, then inspect both customer menus.
- Choose shared settings.
- Apply a local change.
- Check both outlets.
Decision rule: A central update should not erase an intentional branch exception.

