Locations describe where a service is delivered.

Locations identify where services can be delivered and can affect which staff/services are appropriate for a booking.
Locations describe where appointments are delivered and can participate in staff/service availability. Use separate locations when the customer or scheduler genuinely needs to distinguish where a service can happen—not simply as labels for internal teams.
A Location by itself does not create availability. The Service and eligible Staff must also support that location, and staff schedules/time off still control whether a slot exists.
Removing or changing a location can make a service/staff combination unavailable for future bookings. Existing appointments should be reviewed before renaming or deleting a location that customers may already have in their confirmation details.
Open Booking → Locations.
Create a Location when the place itself is reusable across services. Services then reference that shared location instead of repeating address/map/contact details. If the Google Maps Address integration is enabled, complete address/map data so confirmation/direction links are meaningful.
Use the tables below when you need the exact meaning of a field, column, filter or action. Read the workflow and dependency sections above first so each option is used in the right context.
| Column | Use |
|---|---|
| Name | Shows the record name. |
| Address | Shows the address value recorded for each row. |
| Slug | Shows the slug value recorded for each row. |
| Phone | Shows the record’s telephone number. |
| Shows the record’s email address. | |
| Latitude | Shows the latitude value recorded for each row. |
| Services | Shows the services value recorded for each row. |
| Actions | Contains the management actions available for the record. |
| Field / option | Use |
|---|---|
| Name | The human-readable name used to identify this record. |
| Address | Stores the physical address used for the location/customer record. |
| Description | Longer descriptive information for this record. |
| Slug | The URL-friendly identifier used where this item has a public address. |
| Phone | The contact telephone number. |
| The email address associated with this account or record. | |
| Latitude | Stores the map latitude for the Booking Location so mapping/location features can position it accurately. |
| Longitude | Stores the map longitude for the Booking Location so mapping/location features can position it accurately. |
| Place Id | Stores the external place identifier used with the configured maps/location integration. |
| Map Url | Sets or displays the URL used for map url. |
| Is Active | Controls whether this record is treated as active. |
Booking Settings · Services · Appointments · Overview
Locations are shown on the locations page and on a page for each location, in the designs chosen for Locations layout and Location detail layout (see Frontend Designs). The Booking Locations block shows them on any page, and a booking form can be limited to the services of one location (see Page Builder Components). Designed location pages can be bound to a location (see Data-Bound Sections).