Booking
Updated Oct 2026
Booking software for multi-location businesses
One location is a calendar. Two locations is a data problem: the same client, two price lists, a stylist who works across both, and two sets of numbers that nobody can add together.
Why the second location breaks the first setup
Most booking tools are built for a single address. They store services, staff, opening hours and prices at the account level, which works perfectly until you open somewhere else. At that point you need the same fields to hold different values per site, and many tools simply do not have that layer.
The symptoms are predictable. A client books at the second location and the front desk cannot find her history because she exists twice. A staff member is booked at location A while she is scheduled at location B. A report shows total revenue but cannot tell you which site is actually paying its rent. None of these are dramatic failures. They are slow, daily friction that quietly costs hours.
Four ways vendors handle multiple sites
Almost every product you will look at fits one of these models. Knowing which one you are buying saves a long demo.
| Model | What you get | Where it hurts |
|---|---|---|
| One account, many locations | Shared client records, per-location staff and pricing, combined reporting | Usually the most expensive tier; setup is more involved |
| Separate account per site | Simple, cheap, each manager runs their own book | Duplicate clients, no cross-location view, manual reporting |
| Enterprise suite | Deep permissions, transfers, central pricing control | Overkill under four sites; long contracts and onboarding |
| Booking plus separate POS | Best-of-breed at each job | Two client databases that drift apart |
For two to five sites, the first model is usually the right answer. The enterprise suites earn their cost at a scale where you have a regional manager, not before.
What to test in a trial, in this order
- One client, two locations. Create a client at site A, book her at site B, and check that the history, notes and formulas follow her. If the tool asks you to create her again, stop there.
- Staff who move. Put one person on the rota at both sites and try to book her at the wrong one. Good software blocks it or warns you; weak software lets it happen.
- Location-specific pricing. Change a service price at one site and confirm the other site is unaffected. Then check what happens to packages and gift cards bought at the other address.
- Permissions. A site manager should see their own staff, clients and takings, not the whole group. Test this with a real manager account, not the owner login.
- Reporting. Ask for revenue, utilisation and no-show rate per location, and for a combined view. Export both to a spreadsheet and see whether the totals reconcile.
- Transfers and deposits. Move an appointment between sites and check that the deposit follows it rather than being refunded and recharged.
Run these six tests in a trial account with your own service list. A sales demo will show you the happy path; these are the paths that decide whether the tool survives year two.
Client records are the real asset
Service menus and rotas can be rebuilt in an afternoon. Client history cannot. Before you commit, ask two blunt questions: can I export the full client list with notes and appointment history, and in what format? A CSV with names and phone numbers is not enough if the notes, allergies, colour formulas and previous visits stay behind.
Also ask who owns the record when a client books through a marketplace. If the booking arrived via a platform's consumer app, some of that relationship may belong to the platform rather than to you. That matters more with every location you add, because the marketplace may be the main source of new clients at the new site.
Rollout order that avoids a bad first month
Do not switch every site on the same Monday. Move the newest or quietest location first, run it for two to three weeks, and fix the setup issues there. Then move the busiest site, keeping the old system readable for a month so staff can answer questions about past visits. Central pricing and the shared client list should be configured before the first site goes live, not after.
Platforms that sell proper multi-location tiers include Square Appointments, Booksy and Fresha — check current pricing for your number of sites.
If you are still deciding on the core platform, how to choose booking software covers the evaluation process, and staff scheduling for small salons goes deeper on rotas that span more than one address.