Configuring a location
Location details and hours
A branch's identity and its clock. Get the address, the time zone and the hours right and everything downstream behaves; get the hours wrong and customers are told you are closed while you are standing in the shop.
Details
Location settingsLocation details.
Needs the permission locations.update_all_settings (update all locations settings). Owners and Admins have every permission by default.
- Name— how your team and your customers refer to this branch. “Camden”, not the full postal address.
- Address — pick from the suggestions rather than typing it out, which records the coordinates as well. Those are what distance-based rules need.
- Time zone — the most consequential field on the page. See below.
- Contact details — phone, email and website for this branch, shown to customers on public pages.
- Image — a photo of the branch, which helps a customer choosing between two of them.
The time zone is not cosmetic
It decides when your hours apply, where the day breaks for daily figures, what time a confirmation says, and when a scheduled report goes out. See time zones and local days.
Opening hours
Set once per weekday, in the branch's own time zone. A brand-new location has none set, which means customers can join at three in the morning — so this is worth doing before you print anything.
Three sets of hours, not one
You can keep separate hours for general opening, for the waitlist and for bookings, because they are genuinely different questions. A restaurant might take bookings until ten in the evening, close its walk-in waitlist at nine, and have the kitchen open until half past ten.
The waitlist inherits your general hours by default, so a branch that wants one set of hours simply sets them once and never thinks about it again. Where you need them to differ, switch inheritance off for that one.
Exceptions on particular dates
Bank holidays, a late opening, a day closed for a refit. Date exceptions override the weekly pattern for that date only, and can also be inherited from your general hours rather than set three times.
If customers report you are closed when you are open
Check three things in order: the branch's time zone, whether the waitlist is inheriting general hours or has its own, and whether a date exception is in play for today.
Schedules
Location settingsSchedulesis where individual services and resources get their own working hours, rather than following the branch's.
This is what lets a stylist work Tuesday to Saturday in a shop that opens seven days, or a treatment room be available only in the mornings. A resource set to follow the location's hours needs nothing here.
These hours narrow availability; they never widen it. A resource cannot be bookable at a time the branch is closed because its own schedule says so.
Closing a branch temporarily
There is no open-and-closed switch on a location today. To stop people joining, use a date exception marking the branch closed, or switch the waitlist off under waitlist rules. Both give the customer a clear explanation rather than a form that fails.
Deleting a location
Deleting takes its queues and history with it
A branch you have closed for good can be deleted, but everything belonging to it goes too. If you might want the figures later, export what you need from reports first.