Two guests, one therapist, 11:00 Saturday
A guest books a facial for 11:00 on Saturday through a beauty booking marketplace. Ten minutes later, another guest books the same therapist at the same time on your website, because the website's availability was last updated from the spa system an hour ago. On Saturday morning both arrive. One gets the facial, the other is offered a different therapist, a different time or a refund. Neither is impressed.
The week before, a reseller package was booked by phone into a slot that the marketplace had already sold, because the marketplace allocation was a fixed block entered by hand at the start of the month.
Each channel has its own copy of the diary
| Channel | How it knows availability | Typical delay |
|---|---|---|
| Spa booking system | It is the diary | None |
| Your website | Sync or embedded widget | Minutes to hours |
| Booking marketplace | Allocation or sync | Varies, sometimes manual |
| Reseller packages | Phone booking | Depends on reception |
| Hotel front desk | Separate list | Updated by hand |
Where a channel receives a copy rather than reading the diary directly, there is a window in which two sales can collide. Busy times, when you most want online sales, are exactly when that window is most likely to be hit.
Double bookings and nervous online selling
Each double booking is a disappointed guest, a refund or a compromise, and sometimes a review. Staff spend Monday mornings reconciling channels. To avoid it, many spas hold back availability from online channels, which means turning away bookings that would have been fine. Marketplace fees are paid on bookings that later have to be moved or refunded.
How we build one availability source
- We map every channel you sell through and how each one gets availability today.
- Your spa booking system remains the master diary. A small availability service reads it in real time where its API allows, or as frequently as it allows.
- Your website booking reads directly from that service, so it sees what the diary sees.
- For channels that support it, such as marketplaces with an API, availability is pushed as soon as it changes, and their bookings are written straight back to the diary.
- While a guest is paying, the slot is held briefly so nobody else can take it, then either confirmed or released.
- Channels that cannot be connected get a smaller fixed allocation, and a daily report shows any collisions so you can judge whether that channel is worth keeping.
Some marketplaces only allow limited integration. We will tell you which channels can be fully connected and which cannot before any work starts.
Selling online with confidence
The website and connected channels show what is truly free. Collisions become rare, and when a channel cannot connect, you know exactly how much risk you are taking with it. You can open more of your diary to online sales because the double-booking fear is gone, and Monday mornings are for guests, not reconciliation.
Reception benefits as much as the website. A phone booking taken at the desk is written to the same diary the online channels read, so a caller is never promised a slot that a marketplace sold two minutes earlier. And when you add a new channel later, such as a hotel partner or a new reseller, it plugs into the same availability source rather than becoming another copy of the diary to keep in step.
Is your spa in this position?
- You have had two guests booked into the same slot from different channels.
- Some channels get a fixed allocation entered by hand.
- Your website availability is sometimes out of date.
- You hold back online availability to avoid clashes.
- Channel bookings are reconciled manually.