Start with one representative restaurant, document the configuration that works, then review each additional location before it goes live. Menus, permissions, payments, devices and reporting need explicit store-level checks.

Separate shared decisions from local settings

List the restaurants and their countries, currencies, timezones, service channels and equipment. Decide which menu and membership rules should be consistent and which must differ locally.

A shared merchant account is not a promise of automatic configuration cloning, consolidated accounting or cross-store funds settlement. Confirm any group requirement before choosing a plan.

  1. Name an owner and local contact for each restaurant.
  2. Record menu languages, prices, opening periods and order channels.
  3. Define where membership groups and promotions apply.
  4. List payment accounts, terminal providers and printer connections separately for each location.

Give staff the access they need

Review employee roles and the restaurants each person can access. A manager who needs a report does not necessarily need permission to change payments or promotions.

Give each employee their own account and check access before opening. Ask the owner or an authorised manager to review store settings and arrange checks separately from live service.

Check plans and costs before adding locations

Review the published included-store allowance and additional-store price for Pro or Premium, then confirm the actual subscription in Merchant. Staff, terminal and feature access also depend on the plan.

Payment processing, hardware, message providers and any agreed implementation work have their own costs. Zero platform order commission does not remove those charges.

Prove one complete workflow

Use a platform test environment to check a representative guest order, staff handling, POS, kitchen destination and supported printing flow. Payment and refund checks require the appropriate test accounts and provider setup.

The public MenuSnap demo does not place real orders and cannot prove your own payment account, printer, fiscal setup or offline behaviour. Use it to review the guest experience, then arrange the checks required for the installation.

  1. Confirm menu content, options, languages and prices.
  2. Check order routing, employee access and the active printing executor.
  3. Check connection status and rehearse a connection loss and recovery in the test setup.
  4. After reconnection, check updated order and payment states before repeating actions.

Review results, then expand

Agree on the reports and period you will review for each restaurant. Keep sales, received payments, refunds and shift cash distinct, and check timezone and currency before comparing stores.

Keep the previous operating procedure available during the agreed transition. Expand when the first restaurant can complete its everyday workflow and the local administrator has accepted its configuration. Country-specific payment and fiscal requirements must be confirmed separately.

MenuSnap frequently asked questions

Can I copy one restaurant configuration to every location?

Do not assume automatic copying or identical settings. Review each location’s menu, prices, staff access, payments, printers and legal requirements, even when the operating procedure is shared.

Can multiple restaurants share members?

Membership groups can have a configured restaurant scope. Check the group and offer rules first; membership sharing does not provide cross-store prepaid-funds settlement.

Will offline POS keep QR ordering working?

No. Guest QR ordering and cloud services need internet. POS payments, refunds, settlement and shifts need server confirmation; a separate card terminal follows its own provider’s connectivity rules.