English
Español
Català
Français
Deutsch
Italiano
Português
Nederlands
Dansk
Suomi
Norsk
Svenska
Polski
Čeština
Română
Ελληνικά
Türkçe
Українська
Русский
العربية
हिन्दी
ไทย
Bahasa Indonesia
Bahasa Melayu
Filipino
Te reo Māori
Tiếng Việt
日本語
한국어
简体中文
繁體中文Multi-location restaurants
Ordering and operations for multiple restaurants
Grow from one restaurant to several with clear store settings, staff access, reporting scope and additional-location pricing. Plan a staged MenuSnap rollout around how each restaurant works.
Daily management
One operator, different restaurant needs
Make the shared operating procedure clear, then review the local settings that affect guests, staff and payments.
Menus and service by location
Check each restaurant’s menu languages, prices, periods and ordering channels. A common brand does not mean identical opening hours, dishes or payment settings. Confirm each location before publishing.
Access by responsibility
Use employee accounts, roles and restaurant access to define who can work where. Separate daily ordering duties from permissions to change settings, promotions or reports.
Reports with a clear scope
Review the overview, item sales, order channels, payments and shifts for the relevant restaurant. Align period, timezone and currency before comparing locations; sales and received payments are different measures.
Rollout
Prove the workflow in one restaurant first
Map the local setup
List the country, currency, menu languages, order channels, POS devices, kitchen screens, printers and payment accounts. Assign a local administrator for each restaurant.
Validate a complete order
Use a platform test environment to check the guest and staff journey, order totals, kitchen routing and supported printing. The public demo shows the guest experience and does not create a real order.
Agree on the transition
Have the merchant or authorised administrator confirm settings. Prepare staff and a supported offline procedure, and keep the previous operating method available during the agreed transition.
Review, then add the next location
Check payment records, pending synchronisation and the chosen reports. Carry the agreed operating procedure to the next restaurant, then verify its local differences instead of assuming a configuration clone.
Scope and costs
Define what the group actually needs
An additional-store subscription creates capacity for another restaurant. It does not automatically include every headquarters or integration requirement.
Membership and promotion scope
Where enabled, configure the membership group and offer eligibility for the intended restaurants. Shared membership does not imply stored-value balances or cross-store funds settlement.
Subscriptions and local costs
Check included locations, extra-store charges and staff or terminal allowances in Merchant. Provider fees, hardware and any separately agreed implementation work remain distinct from the subscription.
Requirements to confirm separately
Discuss consolidated accounting, custom integrations or deployments before committing. Do not assume automatic store cloning, purchasing, ingredient inventory, central-kitchen management or country-wide fiscal certification.
Plan selection
Choose the location allowance you need
Free
€0 / monthExplore the supported menu and ordering basics in one restaurant.
One restaurant; additional locations are not included.Starter
€9.90 / monthFor one restaurant using the included paid-plan workflows. The displayed Founder price requires eligibility.
Additional locations are not available on Starter. Check the standard price and Founder conditions on the pricing page.Pro
€49 / monthIncludes one restaurant. Each additional restaurant costs €15 per month.
Confirm the active plan, employee and terminal allowances in Merchant.Premium
€99 / monthIncludes three restaurants. Each additional restaurant costs €10 per month.
For a group that needs the included capacity; setup and local provider costs are separate.Published plans are a reference. Founder pricing requires eligibility confirmation; the applicable price and terms are shown when you subscribe.
MenuSnap takes no commission on orders. Payment providers may charge separate processing fees.
See pricingFAQ
Questions about multiple restaurants
Can Starter add another restaurant?
No. Starter Founder and standard Starter are for one restaurant. Review Pro, Premium or a separately scoped arrangement when adding locations.
Does one account give every employee access to all stores?
No. Access depends on the employee’s roles and authorised restaurants. Check permissions before introducing a person to another location.
Can membership be shared between restaurants?
Membership groups can have a configured restaurant scope. Review membership and offer rules first; shared membership does not provide cross-store prepaid-funds settlement.
Is every country and device ready for the same setup?
No. Payment activation, available software releases, printer connections and country-specific fiscal requirements must be checked for each installation.
Build the operating workflow
Build the operating workflow
Guides
How to roll out restaurant software across multiple locations
Plan restaurant settings, staff access, payments, reporting and a staged MenuSnap rollout without assuming every store has the same needs.
Plan the next restaurant with a clear scope
Review the guest demo, compare location allowances and discuss the requirements that depend on your country or equipment.