Managing multiple locations in Square POS for restaurant chains

How to set up new locations, keep one menu consistent, control who sees what and compare performance across your restaurants.

Square lets you run many restaurant locations from a single account. Each location gets its own business details, hours, bank account for transfers, devices and reports, while you share one item library, one team list and one customer base across all of them. The key to running a chain well in Square is deciding upfront what should be the same everywhere and what is allowed to differ.

This guide covers setting up locations, managing menus and prices, team access, reporting and a few habits that keep multi-unit operations consistent.

Add a new location

In Square Dashboard, go to Account & Settings, My business, Locations, and select Create Location. You need the account and settings permission to do this. For each location you set:

  • Business name, internal nickname, description, address and contact details
  • Brand logo and color, time zone and business hours
  • The bank account for transfers (or tags to tell transfers apart)
  • The language for Square emails and customer receipts

You can also match the item library from an existing location when you create a new one, which saves rebuilding your menu. A few rules from Square's help center: an account can have up to 300 locations, locations cannot be deleted (only deactivated), and some plans charge an extra fee per location, which you can check under Pricing and subscriptions in Dashboard.

Decide what is shared and what is local

Usually the same everywhereOften different by location
Core menu items, names and photosPrices (rent and wages differ)
Modifiers and recipesLocal specials and seasonal items
Discount and loyalty rulesHours and holiday closures
Permission sets by roleWhich team members work there
Report definitions and KPIsDevices, printers and kitchen setup

Write this down. When a new general manager asks to rename an item or add a special, everyone knows whether that is a local call or a brand decision.

Manage menus and location pricing

  • One item, many locations. Keep a single item for each dish and choose which locations sell it, rather than duplicating items per location. Duplicates make reports harder to compare.
  • Price overrides. If an item costs more downtown than in the suburbs, create a price override in Square Dashboard from the item library. Items with location pricing show a "Varies by location" label. Square notes that overrides cannot be created from the Square POS app.
  • Bulk edits. For big price changes across many items, exporting the item library to a spreadsheet, editing and re-importing is often faster than clicking through each item. Test with a few items first.
  • Keep names stable. Renaming items creates separate lines in reporting, which breaks location-to-location comparisons over time.

Control team access by location

When you add or edit a team member, you assign the locations they work at. Square's help center explains that those locations determine what they can access, including menus, catalog items and reports, so a team member assigned only to one location cannot see another location's data.

  • Give each location's manager access to their own location only.
  • Give area managers or operations leads access to the locations they oversee.
  • Use the same permission sets across locations so a "shift lead" means the same thing everywhere.
  • Deactivate team members who leave the same day, at every location.

For more on roles, see managing multiple users in Square.

Compare performance across locations

Square reports can be filtered by location, so you can look at each restaurant on its own or side by side. A simple weekly scorecard for each location might include:

  • Net sales and number of transactions
  • Average ticket size
  • Sales by hour, to check staffing against demand
  • Top and bottom items, to spot local menu differences
  • Discounts, refunds and voids, as an early warning sign

Look for outliers, then ask why. If one location's average ticket is consistently lower, compare how staff suggest add-ons, or whether a popular item is often 86'd there.

Habits that keep a chain consistent

  1. A launch checklist for new locations: location details, matched item library, price overrides, devices, team members, permission sets, a test transaction and a test refund.
  2. One owner for the item library. Changes go through one person or team, with a simple request process for local managers.
  3. A shared calendar of menu changes so every location switches on the same day.
  4. Monthly location reviews using the same scorecard everywhere.

Common mistakes

  • Duplicating items for each location instead of using price overrides.
  • Giving every manager access to every location's reports and customer data.
  • Opening a new location without testing devices, receipts and bank transfers first.

One app for every location

Customers should not need a different app for each of your restaurants. With Orda for multi-location brands, you get one branded iOS and Android app and web ordering that covers all your Square locations. Customers pick their nearest location, the menu syncs from that location's Square catalog, and orders flow into that location's Square POS. From the Orda dashboard you can enable or disable locations, add location images and pause online orders at a single location when the kitchen is slammed. Square Loyalty works across the locations in your program. More than 10,000 Square businesses have used Orda.

Related guides: best practices for your Square Dashboard and using Square's dashboard for restaurant insights.

Ready to
Launch Orda?

Connect your store
Launch in 5 minutes