Services per location
Choose which services are offered at which branch — a service can be at one place only.
Not every service happens everywhere. The big salon has a massage room, the small one doesn’t. The laser machine is only at one site. So every service carries a list of the locations where it is offered.
This article shows exactly where that setting lives (it isn’t on the locations page — it’s in the offering editor), what it does, what it does not do, and how you can tell you’ve got it wrong.
A service can be at several locations at once. This is not a “one service, one place” choice. By default every service is at all of them.
1. Where the setting lives
Not in Catalog → Locations. It lives on the service:
- In the left icon rail open the boards product and pick your board.
- In the board column click the Catalog hub.
- Choose the Offerings row.
- Open the service you care about and enter its editor.
- In the editor’s left-hand navigation choose the Locations section.
The section’s description: “Restrict this offering to specific branches.”
The section only appears when the board has locations. With zero locations there is nothing to restrict.
2. The two states
The section has one switch: Available at all locations.
| State | What it means |
|---|---|
| On (default) | The service is offered at every branch, including ones you add later |
| Off | A checklist appears. The service is only at the ticked branches |
The hints say exactly this:
- On: “When you add a new location later, this offering will be available there automatically.”
- Off: “Pick exactly which branches it’s available at. Other branches won’t see it.”
Steps to restrict
- Turn off Available at all locations.
- A list of all locations appears. The first one is ticked automatically so you’re never left with zero selected.
- Tick the branches where the service is genuinely delivered.
- Save the service.
If you untick all of them, the service falls back to “everywhere”. There is no “at no branch” state — to hide a service completely, archive it.
3. The difference between “location” and “resource”
This is the most common confusion.
| Setting | What it controls |
|---|---|
| Locations (on the service) | Which branches the service is offered at all |
| Home location (on the resource) | Where a specific piece of equipment or a room physically sits |
| A person’s working hours | Which branch that person is at on which day |
A service being “available at Vitosha” does not mean anyone there can perform it. Two conditions must hold at once:
- The service is allowed at that branch; and
- A suitable resource is on shift at that branch that day.
If the first is true and the second isn’t, the client sees the service but no free times. That is exactly why the amber warning in §5 exists.
4. What the client sees
| Situation | Behaviour on the public page |
|---|---|
| The service is at one branch | The location step is skipped |
| The service is at several branches | The client picks a branch |
| The client already picked a branch | They only see the services allowed there |
| A group class isn’t held at the chosen branch | ”{service} isn’t held at {location}.” + “Try another location — it might be there.” + a Change location button |
The client never sees a service that isn’t delivered where they are — that is the whole point of the setting.
5. The “services with no specialist at this branch” signal
If a service is allowed at a branch but there is no suitable resource there, Mountify surfaces it in three places:
- On the location card in Catalog → Locations — an amber line “N services have no {kind} at {name}”.
- The dot in front of the Locations row in the board column turns amber.
- In the services list, the offending service is flagged as a problem.
Two fixes:
| Fix | When |
|---|---|
| Give someone working hours at that branch | The service really should be offered there |
| Remove the branch from the service’s list | The service isn’t delivered there and shouldn’t have been allowed |
6. Practical patterns
| Situation | Setting |
|---|---|
| Core services are everywhere | Leave Available at all locations on |
| A special treatment only at the big salon | Turn the switch off, tick only the big salon |
| A service you’re piloting at one branch | Restrict it, then widen when you’re ready |
| A new location that isn’t open yet | Don’t touch the services — just give it working hours when it opens |
Advice: don’t restrict services “just in case”. Every restriction is something you’ll forget to undo when circumstances change. Restrict only where the service physically can’t be delivered.
7. What this setting does NOT do
- It doesn’t set a different price per branch. A service’s price is the same across the board.
- It doesn’t set a different duration per branch.
- It doesn’t hide the service in the admin panel. You still see it and can still book it by hand.
- It doesn’t check whether anyone can deliver it. That’s what the signal in §5 is for.
- It doesn’t apply to packages automatically. Packages have their own locations setting, with an “Any location” option.
What’s next
- Locations (branches) — what attaches to a location.
- Create a service — the whole offering editor.
- Service locations — the same setting from the catalog’s point of view.
- Why there are no free times — when the service shows but no slots do.