Multi-location hairdressing software: manage salons centrally

The second salon is not a doubling of the first. It brings questions with it that simply do not exist in a single business: who is allowed to see which calendar? Is the regular who normally comes to the town-centre salon known at the branch? Does the balayage price apply at both addresses? And who records the sick note when the owner is standing in the other building that day?

Those questions decide the administrative load of the next few years, and they are answered badly when the system knows the second location only as a second account. This article works through the five places where a multi-site business differs from a single salon, and how you tell — in Salon Wizard or in any other system — whether each of them is solved in a way that holds.

Many salons run their second location as a second login at first: its own account, its own calendar, its own client list. That works surprisingly long — until the day three things start happening at once.

• Rotating staffing: as soon as somebody works here on Tuesdays and there on Thursdays, availability has to be true across both buildings, or that person gets booked in two places at the same hour.
• The travelling client: the colour formula was left at one salon and the client is sitting in the chair at the other.
• Joint figures: utilisation, no-show rate and revenue per working hour only mean something when both businesses are counted together.

As long as none of these three occurs, two separate accounts are the simpler solution and a rebuild would be premature. Once two of them happen regularly, something is being reconciled by hand every week that a system ought to be carrying.

Deploying people across several locations is the technically hardest part. A member of staff is and remains one person, but has different working hours per site, sometimes different services, and almost always a different team around them. A system that creates them twice loses exactly that: the double booking is not prevented, because as far as the software is concerned two different people are free.

So check whether one person can be assigned to several locations, with site-dependent hours but a single shared availability. Settle the travel time between them as well: when the morning ends at the branch and the afternoon starts at the main salon, there has to be a buffer between the last and the first appointment that online booking respects.

A second point concerns cover and casual staff. They work irregularly and usually wherever somebody is missing. A system that allows the location assignment only at the moment a person is created, and never afterwards, turns every stand-in into an administrative procedure.

There is no universally correct answer here, only a decision that has to suit the business. A shared client base means colour formulas, appointment history and notes are visible at both addresses, the client repeats nothing, and duplicate entries do not appear. Separate records mean each house sees only its own clients, which can be clearer where the sites are far apart and serve genuinely different neighbourhoods.

In daily salon life the shared version is usually the more useful one, because it solves the case that otherwise causes trouble: the regular is sitting in the other building and nobody knows which colour last worked. It does require a settled answer to who may see what — including whether staff can read the notes of a location they never work at. The same ground is covered in more detail in digital client records for hairdressers.

What matters most is that the decision is not final. Ask whether two separate client bases can be merged later without producing duplicates. That is precisely the step needed when a salon is bought rather than opened.

Two locations are rarely identical. One opens on Saturdays, the other does not. One offers extensions, the other has nobody trained for them. And prices often differ, because rent and clientele look different on a shopping street than in a residential area.

Software for several locations therefore has to let a service be defined centrally and deviate per site — in price, duration or availability. The alternative is creating every service several times over, and that takes its revenge at the next price adjustment: one change becomes as many changes as there are locations.

The same applies to the public page. Each location needs its own web address with its own postal address, its own opening hours and its own booking route — not because it looks nicer, but because clients and search engines both search by place. A single page carrying both addresses in running text answers the question “hairdresser near me” well for neither of them; how the channels feed one calendar is covered in online booking for hairdressers.

With the second location a question of roles appears that did not exist before: not everybody working in the system should be allowed to do everything. A location manager needs their calendar, their clients and their services. They do not necessarily need the revenue figures of the other house, and as a rule not the contract data.

So check whether the system distinguishes a site-bound view from a business-wide one, and whether a new team member can be assigned to one location without automatically seeing everything. That separation is not only a data protection matter — see access rights and client data — but a practical one: a calendar forty columns wide, drawn from three buildings, is unusable for whoever is on reception.

On the other side, the owner needs a view that sets all locations side by side: utilisation, cancellations, rebooking rate, revenue per hour. Without that combined picture there is no way to judge whether the second salon is carrying itself or merely drawing the first one empty. Settle before you decide whether that reporting exists in the system, or whether it is rebuilt by hand in a spreadsheet every month.