Why overbookings happen
Very few overbookings are bad luck. There is usually a gap in the process behind them that can be named.A double booking happens when two channels sell the same room before one knows about the other. Where inventory is maintained by hand, that gap is large: a phone booking at 10 am is only entered in the extranet in the afternoon, and in between the room is still free on Booking.com. With a channel manager the gap shrinks to a short time, but it does not disappear entirely, because each OTA processes updates at its own pace.
The risk is greatest for the last free room of a room type. As long as ten rooms are free, a short delay goes unnoticed. If only one is left, a single minute in which two guests book at the same time is enough. And the very evenings when the property is almost full are also the evenings when alternative accommodation is hard to find.
| Cause | Typical situation |
|---|---|
| Manual maintenance | Phone, email and walk-in bookings are not entered in the system straight away but noted on paper or added later. |
| Delay between OTAs | Two OTAs sell the same room because one has not yet processed the new inventory. |
| Last rooms | A room type has only one room left, and several channels are offering it at the same time. |
| Room closures | A room is out of order due to water damage or refurbishment, but the closure is only entered in the extranet or not at all. |
| Group enquiries | A group has been confirmed by email, but the rooms are not yet recorded as a booking and keep being sold individually. |
| Wrong mapping | An OTA room type is mapped to the wrong room type in the PMS, so inventory is deducted in the wrong place. |
| Parallel operation during a system change | Old and new systems run at the same time, and a booking is only changed in one of them. |
What an overbooking costs
The direct costs are quickly totted up: a room in another hotel, often at a higher price than yours because it is booked at short notice, plus a taxi or transfer and, where appropriate, a gesture such as a dinner or a voucher for the next stay. As a rule, you also lose the room revenue for that night.
The indirect costs weigh more heavily. A guest who is turned away after a long journey is very likely to write a review, and it stays visible long after the bill is forgotten. OTAs do not take kindly to overbookings either; what they expect of you in an individual case, such as covering the extra cost of alternative accommodation, is set out in your partner terms. Read that part of your contract before the worst case happens.
Avoiding overbooking: the checklist
The good news: a few fixed rules can lower the risk considerably. What matters is that everyone on the team knows them, including the weekend temp.
Fixed rules against double bookings
- There is exactly one inventory: every booking, whatever the route, is entered in the hotel software immediately, including walk-ins and phone bookings.
- OTAs are connected through a channel manager that reports every booking to all other channels immediately.
- Rates, availability and closures are only changed in the hotel software, never additionally in the extranet.
- Rooms that are out of order are entered in the system as a closure immediately, with dates and reason.
- Confirmed groups are recorded as a booking or closure immediately, not only when the rooming list arrives.
- Every OTA room type is mapped to exactly one room type in the PMS and re-checked after every change.
- Room types with few rooms have a sales limit, so the last room is not offered on all channels at once.
- Channel manager alerts are reviewed daily, not only when a guest is standing at the door.
- When changing systems, there is a clear cut-over date from which bookings are only made in the new system.
If it happens anyway: step by step
A well-handled walk can even turn a guest into a regular. A badly handled one costs you reviews for months.The earlier you spot the overbooking, the more options you have. So check the tape chart for the coming days every day for room types with more bookings than rooms, or bookings stuck without a room assignment. A shortfall can often still be solved internally, for example with a free upgrade to a higher room type.
If there is no room left, decide which guest has to move. What has proved itself: not the regular guest, not the family with children, not the guest celebrating an occasion such as a wedding anniversary, but if possible a guest on a short stay who can easily accept an equivalent hotel nearby.
What to do in an overbooking
- 01Check internal solutions
An upgrade to a higher room type, a room swap, a room freed up by a cancellation. Only if none of that works do you walk the guest.
- 02Arrange an alternative before the guest arrives
Reserve an equivalent or better hotel nearby. Partner hotels you help out and who help you are worth their weight in gold here.
- 03Inform the guest early and personally
Before arrival if possible, by phone or email, honestly and without excuses. Offer the ready-made alternative, rather than just describing the problem.
- 04Cover the costs
Cover the price difference, transfer and an appropriate gesture. The guest should not lose out because of your mistake.
- 05Inform the OTA
For an OTA booking, report the case via the extranet and follow the requirements in your partner terms, so the guest is not recorded there as a no-show.
- 06Close the booking properly in the system
Cancel or rebook correctly and note what happened in the booking, so the invoice and reports are right.
- 07Find the cause
Work out where the inventory drifted apart and adjust the rule so it does not happen again.
Deliberate overbooking: what is behind it
Some properties, mainly larger ones, deliberately overbook by a few rooms because experience tells them to expect cancellations and no-shows. The idea: if two out of a hundred guests typically do not turn up, you sell two more rooms than you have. That can pay off, but it requires reliable figures over many months, flexible rates with late cancellation deadlines and a network of alternative hotels.
For small and mid-sized hotels, the maths rarely works out. With 15 or 30 rooms, cancellations fluctuate strongly, non-refundable rates and deposits already reduce no-shows, and every single walked guest weighs much more heavily in reviews. If you want less vacancy from last-minute cancellations, you are usually better served by clear cancellation policies, deposits and a waiting list at reception.
STRYK has no function for deliberately selling more rooms than you have. The sales limit per room type works in the opposite direction: it can cap sales below the number of active rooms, but never above it.
How STRYK protects you against overbooking
In STRYK, there is a single room inventory for reception, your own booking engine and connected OTAs; the channel manager is included in the STRYK core price, and we confirm the available channels for each hotel after mapping and a connection test. For every action that occupies or closes rooms, STRYK briefly holds the affected room type and nights and checks once more, immediately before saving, whether the room really is free: for a new booking at reception, a booking through the booking engine, an OTA booking via the channel manager, a room closure, a data import and a room move. Two simultaneous bookings for the last room are therefore checked one after the other, and only one is confirmed.
Only active rooms and room types are counted. A room you take out of service or close disappears from sellable inventory immediately, and the new figures go to the connected OTAs. On top of that, STRYK reconciles the complete picture with the OTAs once a day. With the sales limit per room type, you deliberately hold rooms back in tight room types. For apartments or individual units, overbooking protection can be set per room type so that every booking needs a specific free, suitable unit.
If an OTA booking arrives for which no suitable free room is left, STRYK does not place it in an occupied room but shows it as a reconciliation alert so your team can decide. No system can completely rule out an OTA selling in the seconds before its update. What STRYK makes sure of: the conflict is noticed immediately, not only when the guest is standing at reception.
| Action | What STRYK does |
|---|---|
| Booking at reception, including walk-ins and multi-room bookings | Holds occupancy per room type and night, re-checks free rooms, only then confirms |
| Booking through your own website | The same check immediately before confirmation, with the same inventory as reception |
| Booking, modification or cancellation via an OTA | Books newly occupied or released nights into inventory and reports them to all channels |
| Room closure for repairs or refurbishment | Takes the room out of sellable inventory and sends the new figures |
| Room move and room planning | Checks the target room for the whole stay before the booking moves |