Two families, one cottage
A family arrives at a cottage on a Saturday afternoon to find another family already unpacking. One booked through Airbnb a month ago, the other through your website last week. Your reservations team spends the evening finding the second family somewhere else to stay, paying the difference and apologising, and then finds a poor review waiting on the channel a few days later.
You have a channel manager. You were told this could not happen.
Where the gaps really are
A channel manager connected through each channel's API usually keeps calendars in step. The trouble is that not everything is connected that way. Some properties still use iCal calendar links, which refresh on the channel's schedule, not yours, so a booking can sit on one calendar for a while before it appears on another.
Other causes are human: an owner books a week for friends by telling someone in the office, who blocks it on one calendar only; a property was listed twice on a channel during a move to new software; a manual block for maintenance was never removed and is now hiding availability, or was removed from one place and not another.
| Cause | How it happens | Usual fix |
|---|---|---|
| iCal sync delay | Calendar link refreshes on the channel's schedule | Move to an API connection where the channel allows |
| Owner stays added by hand | Blocked on one calendar only | Owner bookings entered in the master system |
| Duplicate listing | Property listed twice on a channel | Audit of listings against properties |
| Manual blocks | Added or removed in one place only | Blocks controlled from the master calendar |
What a double booking really costs
The rebooking cost is the visible part. The bigger costs are reputational and structural: channels can penalise hosts for cancellations, guests post reviews about it, and owners worry about their property's standing on the channel. Staff lose an evening or a weekend dealing with it, and the fear of it makes teams cautious about opening availability late.
How we close the gaps
We start with an audit rather than new software, then add a safety net that checks for conflicts continuously.
- Connection audit: we list every property and every channel it appears on, and record how each one is connected: API, iCal link or manual. Duplicate and orphaned listings are found.
- Stronger connections: where the channel and your property management system support it, iCal links are replaced by API connections through your channel manager.
- Single source for blocks: owner stays and maintenance blocks are entered once in your master system, through a simple form for owners and staff, rather than on individual channels.
- Conflict checker: a scheduled job reads each channel's calendar for every property and compares it with the master calendar, alerting your team by email or Slack when two stays overlap or a channel shows availability that does not exist.
- Rebooking playbook: when a conflict is found, the alert includes guest details, alternative properties with availability on those dates and a template message, so the team can act quickly.
What your team can rely on
Conflicts are caught when they happen, usually long before arrival, while there is still time to move a guest to a similar property. Owners use one route to block their weeks, and your team stops maintaining calendars in several places.
Knowing the checker is running also makes it easier to keep late availability open, which is often when the most valuable bookings come in.
Signs this is your situation
- Some properties still connect to channels through iCal links.
- Owners block their own weeks by phone or email.
- You have had a double booking in the last season despite a channel manager.
- You are not sure every listing on every channel is still connected.
- Staff hold back late availability in case of clashes.