Make location part of availability, not just a label in the confirmation. A staff member or shared resource must not become available in two places at the same time.
Define what belongs to each location
Create a simple map of services, staff, rooms and equipment by site. Some services may exist everywhere; others may require a specialist room or a particular employee. Reflect those differences in the booking options.
A Shopify inventory location and a booking location are not automatically the same concept. Confirm how your app connects them, if at all, before relying on storefront availability.
Decide where customers choose the location
Customers should know the venue before choosing a time and paying. Depending on your store, location can be selected on a service page or through separate location pages. Keep the selected location visible through confirmation.
Avoid making customers discover the venue only in a post-purchase email. Include the address, arrival instructions and contact route in the booking details.
Protect shared staff and equipment
| Situation | Rule to model |
|---|---|
| One employee works at two sites | A single availability source plus travel time |
| A room hosts several services | Shared room capacity across all relevant services |
| Equipment moves between sites | One resource, with transport and setup time |
| Locations have different opening hours | Location-specific schedules and exceptions |
| Sites cross time zones | Clear local time and consistent calendar events |
Test a booking at location A followed immediately by one at location B. If travel is required, the second should not be offered until the employee can realistically arrive.
Compare the plan for the whole operation
BookX lists location limits by plan. Sesami lists multi-location on its Premium tier. Other apps may model locations through services, staff or resource settings. Ask the vendor to demonstrate your specific structure rather than accepting the phrase “multi-location” alone.
Cowlendar can be evaluated for staff and resource availability, but the exact location workflow should be confirmed with support. Price the configuration for your full team and expected booking revenue.
Make permissions and reporting practical
A site manager may need access to their own schedule without changing another location's configuration. Review the available staff portal and permissions. Check whether reports can distinguish location, service and staff rather than grouping everything into one total.
Give the central team a process for transferring bookings between sites. A transfer may affect availability, price, customer travel and payment; it is not merely editing an address.
Run a location-by-location acceptance test
Book the same service at each site. Verify the customer sees the correct address, staff member, time zone and price. Then close one location for a day and confirm the other remains available.
Finally, test a cancellation, staff absence and shared-resource conflict. Keep one written source of truth for schedule changes so local teams do not maintain competing calendars.
For complex combinations, use our booking constraints guide to turn each operational rule into a test.
Official sources
Common questions
Are Shopify locations automatically booking locations?
No. Inventory locations and service availability may be separate concepts. Verify the mapping in the booking app.
How do I stop staff being booked at two branches?
Use a shared availability model for the person and include travel time. Test cross-location conflicts rather than maintaining independent calendars that cannot see each other.
Written by the Cowlendar team. Recommendations reflect our editorial judgment; we make Cowlendar. App facts are based on the linked public documentation checked on September 22, 2026, not a claim of independent hands-on testing. Pricing and plan limits can change.
Originally published Jul 3, 2025.
Built for Shopify
