How to Run Multiple Locations or Businesses on Acuity Scheduling

Yes — if the locations belong to the same business. The standard pattern is one Acuity account with a separate calendar per location (or per staff member per location), each with its own hours and availability. Clients pick the right calendar when they book, and everything lives under one login.

The catch is that almost everything else in Acuity is account-level. Branding, the scheduling page's look and feel, policy text, and payment configuration apply to the whole account — your downtown studio and your suburban one present the same face and follow the same rules. For a genuinely uniform business, that's fine. The moment locations need different branding, different policies, or different payment accounts, calendars stop being enough.

Reporting is the other ceiling. Acuity's built-in reports were designed for a single business: there's no per-location comparison view, no no-show-rate report, and no cancellation analytics at all — and the revenue report excludes cancelled and no-show appointments, so location-level money questions end up answered in spreadsheets, if they get answered at all.

For distinct businesses — different brands, different client bases, different payment accounts — Acuity's official recommendation is simple: one account per business. Each account is a clean silo with its own login, its own scheduling pages, its own client list, and its own settings.

As an isolation model, that's correct. Businesses genuinely shouldn't share a client database or a payment connection. The problem is everything above the scheduling layer: you now have two (or ten) of everything — logins, settings screens, confirmation email templates, reports — and no single view that spans them.

At the top end, Acuity offers an Enterprise tier: sales-led, custom-scoped, and aimed at large multi-calendar organizations — contact Acuity for its scope. If you're a franchise at that scale, it's worth the sales conversation. If you're running three locations or a dozen agency clients, you're in the awkward middle — too big for one account to feel manageable, far too small for Enterprise — and this middle band, more than one location but fewer than enterprise-scale calendars, is exactly where the friction concentrates.

Separate accounts solve isolation and create an operations problem. The failure modes are predictable:

• Credential juggling. Every account is a separate login. Browsers fight multiple simultaneous sessions, so teams fall back to a shared password spreadsheet — a security incident waiting on its first ex-employee.
• No cross-account reporting. “Which location had the worst no-show rate last month?” has no answer inside Acuity. Each account only knows about itself, and none of them tracks no-show rate to begin with.
• No per-location comparison. Even basic questions — busiest hours by location, average ticket by location, which site fills fastest — require exporting from every account and merging by hand, every time.
• Compounding report drift. Acuity's revenue report excludes cancelled and no-show appointments and can drift from Stripe or Square totals when refunds occur. One account's drift is an annoyance; five accounts' drift is a monthly bookkeeping project.
• Settings sprawl. A policy change — a new cancellation window, updated reminder wording — has to be repeated in every account, and nothing records who changed what, where, or when.

None of these stop bookings from happening. What they stop is management: the operator's ability to see the whole business, compare its parts, and change things safely.

Agencies and multi-brand operators inherit every problem above, plus a trust dimension: those aren't your accounts, they're your clients'. The standard workaround — each client hands over their Acuity password, the agency keeps them all in a doc — fails every basic security test:

• Onboarding and offboarding. Every staffing change at the agency should mean rotating passwords across every client account. In practice, nobody rotates anything.
• No health overview. The only way to know a client's booking flow is broken — or their client's card was declined — is to log into that account and go looking, client by client.
• No accountability. With shared logins, every action looks identical. When a client asks who changed their availability last Tuesday, there is no answer.

The pattern in every row: Acuity answers the scheduling question at each scale, and leaves the management question — one login, comparison, oversight — unanswered. That's the layer to buy or build, not a reason to migrate off Acuity.

Tecton Scheduler doesn't replace Acuity — it layers a management plane on top of the accounts you already run. Each location or client connects as an isolated tenant, and you operate all of them from one place:

1. Connect each Acuity account as its own tenant. Every location or client keeps its own Acuity account, branding, and policies. Tecton syncs appointments and services from each account on demand or on a schedule, with credentials encrypted at rest — no shared password doc.
2. Configure each tenant independently. The reschedule window, optional reschedule fee, and public branded reschedule link are set per business in Settings — one client can charge a fee inside 24 hours while another charges nothing.
3. Run the fleet from the super-admin console. Usage, plans, and per-tenant feature flags live in one screen, and billing issues surface in the console instead of in an angry client email.
4. Compare locations with real analytics. Revenue booked vs. collected, bookings, cancellations, no-shows, and new clients per tenant with prior-period comparisons — plus a demand heatmap by day and hour that shows which location fills which hours.
5. Keep an audit trail. Every change is recorded: who touched which tenant, and when. That's the accountability shared Acuity logins can never provide.

The scheduling layer stays exactly where it is — each business keeps its own Acuity account, booking pages, and client relationships. What changes is that the operator finally has one place to stand. For a deeper look at the per-location metrics this unlocks, see our guide to building an analytics dashboard for Acuity Scheduling.