Why are rooms bookable on one OTA but closed on another?
A guest wants a bank-holiday break at your Irish hotel. One booking site offers a double room; another shows nothing. Follow the same search through your reservation system and each channel to find which condition blocks the sale.
Rooms can be available on one online travel agency (OTA) and unavailable on another because their inventory, room mapping, stop-sell settings, stay restrictions or occupancy rules differ. A missing sellable rate or an unsuccessful update can also block a booking. Compare identical searches before changing anything: an empty room does not automatically qualify for every stay, and a deliberate channel restriction is not a synchronisation fault.
Start with one identical guest search
For an OTA availability mismatch, compare your hotel property management system (PMS), channel manager and OTA extranet, the platform’s management area. Booking.com distinguishes inventory from searchable availability: rooms must also suit the guest’s dates and occupancy.
- Record arrival, departure, room count, adults, children’s ages and search time, including timezone. Use the same currency, such as EUR, and login state.
- Compare the same physical room category and equivalent rate plan, including meals and cancellation conditions. Mapping means linking those products between systems.
- Save the initial result and nightly settings. Identify which system controls each field before editing it; make one change at a time.
A bank-holiday diagnosis, step by step
Hypothetical example: a Galway hotel searches one double for two adults, Friday arrival and Sunday departure: two nights during an illustrative Irish bank-holiday weekend. Channel A offers it; Channel B does not. These are fictional channels and findings, not a customer case.
Assume eight doubles each night from Friday to Sunday: four booked, one separately held for a group and one out of service. That leaves 8 − 4 − 1 − 1 = 2 sellable rooms nightly. The intended policy on both channels is a two-night minimum, maximum two adults, with arrivals and departures permitted.
| Possible cause | Check | Expected evidence | Corrective action |
|---|---|---|---|
| 1. Inventory exhausted | Reconcile bookings, group holds and maintenance for every occupied night. | Two sellable doubles nightly; compare the quantity sent to each channel. | Correct a mistaken hold or channel quantity only after reconciliation. Never invent extra rooms. |
| 2. Stop-sell | Inspect room-level and rate-level closure settings separately. | Both levels open for Friday and Saturday. A closed room can override an open rate. | Remove only an unintended closure, at the level where it exists. |
| 3. Minimum stay | Compare arrival-based and stay-through restrictions. Try Friday–Monday as well. | In this example, B requires three nights on Friday arrivals; A requires two. B offers the three-night search. | Restore B’s intended two-night rule in its controlling system, then verify receipt. |
| 4. Arrival or departure closed | Check Friday arrival and Sunday departure flags independently. | Neither is closed in this example. A restriction on either endpoint could block this itinerary. | Correct a mistaken flag; retain any intentional restriction. |
| 5. Occupancy mismatch | Check guest capacity and whether a two-adult offer exists. | Both channels accept two adults for this double; no child is included. | Correct an erroneous capacity or occupancy setup without exceeding the room’s actual limit. |
| 6. Incorrect mapping | Match PMS category and rate identifiers to each channel’s identifiers, not just names. | The intended double and flexible room-only plan are linked on both channels. | Have the connection owner repair any wrong or missing link; verify before reopening sales. |
| 7. Missing sellable rate | Check an active, valid offer covers every night and the requested occupancy. | No gap in Friday or Saturday rate coverage. | Restore missing coverage. Investigate availability here, not price differences. |
| 8. Update not applied | Compare the saved setting with delivery responses and the receiving extranet. | After correction, B records a two-night minimum for the tested Friday arrival. | If values differ, collect timestamps and error details for the provider before retrying. |
These checks apply general diagnostic reasoning to fictional data. Booking.com documents room closures, valid rates and arrival/departure restrictions, plus arrival-based versus stay-through minimum stays. Confirm each channel’s supported controls.
In this example, the three-night minimum is the confirmed mismatch. If that rule were intentional, the two-night search should remain unavailable. Record the decision rather than opening every channel indiscriminately.
Repeat the same acceptance check on every channel
A saved change is not sufficient evidence. Booking.com’s inventory readback documentation separates room-level closures from rate restrictions. Ask your provider for the appropriate receiving-side evidence if it is unavailable in your interface.
- Log channel, property, room and rate identifiers, exact dates, occupancy, timestamp and expected result. Capture the corrected setting in the extranet.
- Repeat Friday–Sunday for one room and two adults: both fictional channels should now offer the intended product. Friday–Monday should also work while Sunday inventory remains available.
- Test Friday–Saturday: one night should still fail the two-night minimum. Test three adults in the double: that should still fail its two-person capacity.
- Record actual results and screenshots per channel. If a valid search fails, inspect overlapping restrictions and booking windows; escalate with the evidence. Do not treat repeated refreshes as proof of a fix.
Use RoomRaccoon to trace the mismatch
The RoomRaccoon hotel channel manager describes pooled inventory and room/rate mapping to OTAs. Its hotel property management system provides reservation and group-booking context. Use these records to establish intended availability, then compare the receiving channel. Confirm supported restrictions, access to delivery evidence and who controls each setting for your particular connection; this checklist is a manual investigation, not an automated diagnostic feature.
Bring one mismatched stay and your room categories to a demonstration of how your property’s distribution would be configured.
Book a demo for your propertyFrequently asked questions
Does “unavailable” mean the hotel is full?
No. It can mean no room-and-rate combination meets that specific search. Check each occupied night and the applicable restrictions before concluding that inventory is exhausted.
Can a guest stay through a closed-to-arrival date?
Yes, if their arrival is on another date and every other condition permits the stay. Closed to arrival restricts check-in; a stop-sell is a different control.
Should I change the OTA extranet directly?
First establish which system owns the setting. Coordinate any temporary extranet change with the connection provider and reconcile it with the controlling system to avoid conflicting updates.
Does a successful update prove the room is bookable?
No. Booking.com warns that overlapping restrictions can block availability without an error. Verify the received settings and repeat the guest search.
Sources and checks
Checked 13 November 2026. Platform documentation supports the distinctions above; the Galway scenario and acceptance tests are illustrative.
