CTA and CTD compared
| Restriction | Blocks | Still allows | Typical use |
|---|---|---|---|
| Closed to arrival | Check-ins on the date | Stays that arrived earlier and continue through it | Stop one-night arrivals on a peak Saturday |
| Closed to departure | Check-outs on the date | Stays that continue past it | Avoid a gap night after an event |
| Minimum stay | Stays shorter than N nights that include the date | Longer stays | Protect peak periods |
| Stop-sell | All new bookings for the date | Nothing new | Fully close a room type |
Example
A resort expects a full house on 31 December. Set CTA on 31 December and a minimum stay of two nights on 30 December. Guests arriving on the 30th for two or more nights can still stay through New Year's Eve, but no one can take a single night on the 31st and leave the 30th and 1st empty.
Pitfalls
- Restrictions left on after demand fades block bookings you would have wanted; review them as the date approaches.
- A restriction applied to one rate plan but not another can be bypassed; decide whether it applies per plan or to the room type.
- Channels must receive the same restrictions as your own booking page, or the gap reappears through them.
How bedsKey handles restrictions
bedsKey sets minimum stay, maximum stay, closed to arrival and closed to departure per date and per rate plan, alongside seasonal and derived rates. Stop-sell and closeouts close a room type or date range in one action, and the channel manager pushes changed nights to connected channels.