Channel manager basics: avoiding overbookings on Booking.com and Airbnb

Selling the same rooms on Booking.com, Airbnb, Expedia and your own website is the easiest way to fill a small hotel. It is also the easiest way to sell the same room twice.

An overbooking is expensive. You pay for the guest's alternative accommodation, you may lose a review, and OTAs can penalise your listing. The good news is that almost every overbooking has a clear technical cause, and most of them can be prevented with a correct setup.

How overbookings actually happen

Manual extranet updates

If you update availability by logging in to each extranet by hand, there is always a gap between a booking arriving on one channel and you closing the room on the others. On a busy evening, two bookings can land in that gap.

iCal delays

Many small properties connect Airbnb, Vrbo and others with iCal calendar links. iCal is simple and free, but it is not real time. Each platform fetches your calendar on its own schedule, typically somewhere between every 30 minutes and every few hours. During that window, a room you have just sold elsewhere still looks free.

iCal also only shares blocked dates. It does not send prices, restrictions or the number of rooms left, so it works poorly for anything other than a single unit.

Two-way API vs iCal

A two-way API connection works differently. Availability, rates and restrictions are pushed to the channel as soon as they change, and new bookings, modifications and cancellations come back to your system automatically. The time window in which a double booking can happen shrinks from hours to seconds.

Room type mapping errors

Each channel has its own list of room types, and your channel manager has to map them correctly. If your "Double with balcony" is mapped to the wrong room on Booking.com, or two channel room types point at the same physical inventory without being counted together, availability goes out of step.

Rate plan mapping

Rate plans such as non-refundable, breakfast included or long stay also need mapping. A rate plan that is not mapped, or is mapped to the wrong room, can stay open on a channel when you thought you had closed it.

Closed dates not pushed

You close a date for maintenance or a private event in your own system, but the closure is never sent to one of the channels, perhaps because it is connected by iCal or because that room type is not mapped. The channel keeps selling.

Cancellations not returned

When a cancellation or modification on an OTA does not reach your system, the room stays blocked or, worse, a modified date range is not updated. Sometimes the reverse happens: you cancel in your system, but the channel still treats the booking as active.

Setup checklist

Most of the work in preventing overbookings happens once, when you connect your channels. Go through this list carefully.

1. Choose one source of truth. All availability should come from one place, your PMS and channel manager. Stop editing availability directly in extranets, except in an emergency.
2. Map every room type. Check that every room type on every channel is mapped to the correct room in your system, and that nothing is left unmapped.
3. Map every rate plan. Do the same for rate plans. Close or delete any rate plan on a channel that you do not intend to sell.
4. Set a maximum to sell per channel if you need it. Allotments or a "max to sell" figure let you limit how many rooms each channel can take, for example keeping two rooms for direct bookings in peak season.
5. Consider a small buffer. On high-demand dates, holding back one room from the OTAs gives you somewhere to put a guest if something goes wrong.
6. Set minimum stay and other restrictions centrally. Minimum stay, closed to arrival and closed to departure should be set once and pushed to every channel, not maintained separately.
7. Replace iCal where you can. Use two-way connections for every channel that offers them, and keep iCal only for platforms where no API is available.
8. Test before you go live. Make a test booking and a cancellation on each channel and check that they appear correctly in your calendar.
9. Check the connection log regularly. A good channel manager shows you failed updates. Look at it every day for the first weeks.

What to do when an overbooking happens anyway

Even with a careful setup, an overbooking can still happen, for example during a channel outage. Have a plan ready so you are not improvising with a guest at the desk.

Act as early as possible. As soon as you spot the double booking, decide which reservation you will move. Contacting the guest days in advance is far better than telling them on arrival.

Have a walk policy. A walk policy sets out how you relocate a guest when you cannot accommodate them. It usually covers which nearby properties you use, who pays for the alternative room and transport, and who makes the decision.

Relocate to an equal or better property. Keep a short list of nearby hotels of similar or higher standard, and agree in advance with their owners that you will help each other when needed.

Offer fair compensation. Pay the difference in price and the taxi, and consider a gesture such as a discount on a future stay. A well-handled relocation often still ends in a positive review.

Contact the OTA's partner support. If the booking came through Booking.com, Airbnb or another channel, tell their partner support team what happened. They can help with the guest, and documenting the cause protects your listing if it was a technical fault.

Find the cause. After the guest is looked after, trace exactly why it happened: mapping, iCal delay, a manual change or a failed update. Fix it so it does not happen again.

How Ospitessa's channel manager handles this

The Ospitessa channel manager is built into the PMS, so the calendar you use every day is the only source of availability.

• On channels with a two-way connection, availability, rates and restrictions are pushed within seconds of any change, and bookings, modifications and cancellations come back automatically.
• Connections cover Booking.com, Expedia, Airbnb, Agoda, Trip.com, Google Hotels, Vrbo, Hotelbeds, Hostelworld, HRS and more than 70 other partners. See the full list on our integrations page.
• iCal is available only as a fallback for platforms without an API connection.
• Room types and rate plans are mapped once, and you can set allotments, minimum stay and other restrictions in one place through rates and availability.
• Bookings from your own booking engine update the same calendar, so direct and OTA bookings never compete for the same room.

If you are moving from manual extranet updates or iCal links and want to check your mapping before switching, book a demo and we will go through it with you.

channel manageroverbookingBooking.comAirbnbdistribution