Overbooking happens when the same room is sold twice, because two people or two systems each believed it was free. The fix is one shared room inventory that the front desk, your website and every OTA all sell from, updated the moment anything changes.
Short answer: a hotel gets overbooked when availability is kept in more than one place: an OTA extranet, a register, a spreadsheet, someone's phone. Each copy is updated by hand, and one of them is always late. Hotel software prevents it by keeping a single room chart and sending every change to all channels automatically.
Airlines and large city hotels sometimes overbook on purpose, betting that a few guests will not show up. That is a revenue decision made with data. What most independent hotels suffer is different: an accident. Nobody chose to sell room 204 twice. Two channels simply did not know about each other.
The cost is more than one awkward conversation at the desk. The hotel pays for a room elsewhere, the OTA may charge a penalty or lower the property's ranking, and the guest writes the review. One avoided double booking in peak season usually pays for the software that prevents it.
Almost every double booking traces back to one of these. The first three are about channels; the last three are about departments not seeing the same information.
Someone has to log in to each OTA and close the room. On a busy evening one of them is always forgotten.
Five rooms given to one site and five to another. One sells out while the other still shows rooms you no longer have.
The guest is in the room, but the booking is still on a slip of paper while an OTA sells the same room.
Housekeeping or maintenance blocks a room for repairs, and reservations never hears about it.
Twenty rooms promised to a wedding party, written in the banquet diary and nowhere else.
A guest stays one more night. The desk agrees, but tonight's arrival for that room was confirmed weeks ago.
The same six causes, with what happens on paper and what happens when the PMS, channel manager and booking engine share one inventory.
| Cause | With registers and extranets | With a PMS and two-way channel manager |
|---|---|---|
| Extranets updated by hand | Staff log in to each OTA to close the room | A sale on any channel closes the room on all the others automatically |
| Separate allotments per OTA | Each site sells its own fixed share | All channels sell from one pooled inventory down to the last room |
| Walk-ins and phone bookings | Written down first, entered later | Entered on the room chart at the desk or on a phone; OTAs update at once |
| Rooms out of order | Reservations finds out when the guest arrives | Housekeeping marks the room on a phone and it leaves availability everywhere |
| Group and banquet blocks | Held in a separate diary | Blocked on the same chart, so OTAs cannot sell rooms promised to the group |
| Extended stays | Agreed verbally at the desk | The chart shows the next arrival before the extension is confirmed |
Channels are only half the problem. The other half is inside the building. Reservations, the front desk, housekeeping, maintenance and the banquet team each make decisions that change what can be sold tonight.
In a hotel management system they all work on the same room chart. Housekeeping updates room status from a phone. Maintenance marks a room out of order with a return date. The banquet team blocks rooms against an event. The front desk sees all of it before promising a room, and the channel manager passes the result to every OTA.
That is the difference between a channel manager on its own and one that is part of the property management system: the first only knows about online bookings, the second knows about the whole hotel.
Exceed's channel manager is part of the PMS and connects to 200+ OTAs in both directions. For a hotel group selling several properties from one desk, the central reservation system applies the same idea across all of them.
More on the software that keeps rooms and channels in step.
Common questions about hotel overbooking and double bookings
Overbooking is when a hotel has confirmed more reservations for a night than it has rooms to give. Large hotels sometimes do it on purpose to cover expected no-shows. In small and mid-sized hotels it is almost always an accident, caused by availability being kept in more than one place.
A double booking is one specific room, or the last room of a type, sold to two guests for the same night. Overbooking is the wider result: more confirmed bookings than rooms. Most accidental overbooking in hotels is made of individual double bookings.
A property management system with a built-in two-way channel manager and a single room inventory. In Exceed HMS the front desk, the website booking engine and 200+ OTAs all sell from one room chart, so a room sold anywhere is closed everywhere without anyone updating an extranet.
A two-way channel manager sends the change as soon as the booking is saved. How quickly each OTA shows it depends on that OTA, but it is normally a matter of moments, compared with the minutes or hours it takes a person to log in to each extranet.
Rarely, but yes. The usual causes are a connection that has stopped syncing, a room type that was never mapped to an OTA, or two guests booking the last room on two sites in the same instant. Alerts for failed updates and a stop-sell on the last room during peak dates cover most of the remaining risk.
Tell the guest plainly and early, offer a better room if one is free, and if not, arrange and pay for a room of the same standard nearby, including transport. Record what happened so the cause, usually a missed update, can be fixed the same day.
Want to see one room chart shared by the desk, your website and OTAs? Book a free online demo