Multi-location salon management: one system, clear local ownership

Short answer: Run multiple salon locations from one shared operating model, but keep local responsibility explicit. Standardise services, statuses, permissions and reporting definitions; assign staff and resources to the correct branch; give clients an unmistakable location choice; and review both branch-level and group-level results. Central visibility should not erase differences in capacity, demand or legal entity.

The second location exposes every informal habit from the first. A service name that “everyone understands”, a holiday mentioned in chat and a price kept on paper become conflicting versions of truth. The goal is not to make branches identical. It is to decide what must be shared and what a local manager owns.

What should be centralised across salon locations?

Centralise definitions that clients and reports depend on:

• service naming rules, categories and required duration fields;
• appointment statuses and cancellation reasons;
• client identity and duplicate-record handling;
• permission roles and access-review cadence;
• payment-method names and end-of-day reconciliation;
• KPI formulas and reporting cut-off;
• brand, privacy and communication templates.

Keep branch-specific facts local: opening hours, staff availability, rooms, devices, local prices where genuinely different, tax/legal entity details, emergency contacts and daily handover. Document who may change each field.

The locations setup guide covers Tervita's operational branch records. Use the service catalog guide to keep a shared vocabulary while assigning the right service availability.

How should online booking present several branches?

The location must be obvious before a client chooses a time. Show the branch name, address, access information, language notes and any materially different cancellation or payment condition. Do not rely on a tiny address at the final confirmation step.

Test the flow from a phone for three scenarios: a client loyal to one specialist, a client loyal to one branch and a client who wants the earliest slot anywhere. Confirm that the selected service, employee and time all belong to the selected location. The online-booking guide provides a wider client-journey checklist.

Avoid creating separate client records merely because the person visits another branch. A shared history can prevent duplicated messages and conflicting contact data. At the same time, limit access to what each role needs. The GDPR principle of data minimisation and appropriate access still applies across branches; Article 5 of the GDPR remains the source, not the convenience of a group dashboard.

How do you prevent cross-location schedule errors?

Every bookable object needs a branch context: specialist shift, room, device and service. Travel time between branches must be blocked explicitly. A person cannot finish at one address and begin at another at the same minute, even when both calendars individually look free.

Use one process for absence and shift changes. The local manager records the change where booking availability is calculated, not only in a group chat. Review tomorrow's schedule by branch and flag appointments whose staff, service or resource location does not match. The staff-scheduling article explains bookable time and rest rules in more depth.

For shared equipment, decide whether it moves and how the move is represented. Tervita can associate operational context with locations and show branch reporting, but it does not currently promise a multi-location inventory-transfer workflow. If stock transfers, batch traceability or central purchase orders are mandatory, keep a dedicated controlled process or select specialist inventory tooling.

Which permissions should local and central teams have?

Design roles around decisions, not job titles alone. A branch manager may manage local schedules and staff without seeing group billing. An accountant may need invoices and reports without editing bookings. A receptionist may work at two branches but should not automatically gain owner access.

Use four questions for each permission:

1. What task requires it?
2. Which locations and legal entities are in scope?
3. Is viewing enough, or is editing required?
4. Who reviews and removes the access when the role changes?

Tervita provides preset and custom role concepts described in team and roles. The owner remains responsible for configuration and periodic review. Shared software does not justify shared access to everything.

How should branches be compared?

Start with clean inputs, then show each branch beside the total. Use the same definitions for bookable hours, completed visits, no-shows, revenue and payment methods. Explain differences in service mix, team size, opening history and local demand before ranking managers.

Tervita's reports can be scoped by location and include a branch comparison table. They are operational reports, not franchise accounting or consolidated statutory statements. The salon KPI guide gives formulas and fairness checks.

A weekly multi-location review can be short:

• tomorrow's staffing and resource exceptions;
• unresolved client or payment handovers;
• data-quality differences between branches;
• next two weeks' capacity by location;
• one local action and one group-wide action.

What does a good branch handover contain?

Record the client-safe operational fact, owner and deadline. Examples include a device unavailable until maintenance, a room closed for repair, an approved staff absence, a payment discrepancy or a client callback. Do not copy sensitive consultation notes into a broad handover channel.

Open the second location in the system before opening it to clients. Enter hours, team, services and resources; simulate direct and cross-branch bookings; test rescheduling; verify roles; and compare the first report. Keep a rollback plan for the public booking link if the setup is wrong.

The strongest model is “one language for the business, one accountable owner per branch”. Central data makes comparison possible; local ownership makes the next appointment work. Try Tervita for 14 days and model both branches with test data before changing the live booking path.