1. Rate restrictions are controls applied to hotel inventory that shape which bookings are accepted — not just whether a room is available, but when guests can arrive, depart, and for how long
2. CTA (Closed to Arrival) blocks check-ins on a specific date; CTD (Closed to Departure) blocks check-outs on a specific date
3. MinLOS sets a minimum nights requirement; MaxLOS sets a ceiling; both prevent stays that create unsaleable gaps or dilute revenue during peak demand
4. Stop Sell closes a room or rate plan on one or all channels entirely — the bluntest tool, used when inventory is nearly exhausted or a channel needs to be protected
5. Restrictions applied incorrectly — too aggressively or left active after the peak period — create booking gaps and lost revenue that are easy to avoid
What Rate Restrictions Are and Why They Matter
A hotel rate restriction is a rule applied to a room type, rate plan, or channel that determines which reservations the system will accept — independent of whether the room is physically available.
Availability says whether a bed is free. Rate restrictions say whether a booking on those dates is commercially acceptable. A room can be available on a Monday night but restricted to arrivals of two nights or more. A room can be open on a Thursday but closed to guests departing that day because every Thursday checkout creates an unworkable gap before a weekend block booking.
These controls sit inside the property management system and push outward to OTA channels via the channel manager. When a restriction is set in the PMS, it applies everywhere the channel manager distributes — Booking.com, Airbnb, Agoda, the hotel's own booking engine — simultaneously.
Understanding what each restriction does, and when to use it, is one of the core skills in hotel revenue management.
The Five Restrictions Explained
CTA — Closed to Arrival
CTA prevents new reservations from having a check-in date on the restricted day. Guests can still stay through that date — a booking arriving the day before is unaffected. What CTA blocks is the arrival itself.
- When to use it: CTA is most often applied on days when the hotel is nearly full and accepting one-night arrivals would occupy rooms that could otherwise extend an existing multi-night stay. It is also used operationally — when front-desk staffing is thin on a specific day, or when back-to-back arrivals create a housekeeping bottleneck.
Example: A hotel is 90% full on Saturday and has remaining rooms it expects to sell as part of Friday–Sunday packages. Setting CTA on Saturday closes Saturday as a standalone arrival date while keeping Friday–Sunday packages bookable.
CTD — Closed to Departure
CTD prevents bookings from having a check-out date on the restricted day. Guests already booked through that date are unaffected. CTD stops new reservations from ending on that day.
- When to use it: CTD is used when a departure on a specific day creates a gap that cannot be filled. The classic case is a high-demand Saturday night: if a guest departs Saturday, the room is vacated mid-peak-period and may not resell for the remaining night at the same rate. Setting CTD on Saturday forces guests to either stay through Sunday or arrive on a different day.
CTD is the least-used restriction of the five — many hotels manage without it — but it is valuable for properties with very short booking windows and high same-day demand.
MinLOS — Minimum Length of Stay
MinLOS requires that any new booking span at least a defined number of nights. A MinLOS of 3 on a Friday means guests booking that Friday must also take Saturday and Sunday.
- When to use it: MinLOS is the most widely used rate restriction in hotel revenue management. It is applied during high-demand periods — holidays, local events, peak season — to force longer stays and prevent single-night bookings that would block a room from being sold as a weekend package.
The risk is setting MinLOS too high. A MinLOS of 4 on a Friday when the market supports 2-night stays will generate vacancy rather than revenue. The goal is the minimum restriction that prevents genuinely problematic short stays, not the maximum that would theoretically fill rooms.
Interaction with CTA: CTA and MinLOS are often applied together. CTA closes Saturday as an arrival date; MinLOS of 2 on Friday requires that any Friday arrival stays through Saturday. Together, they ensure Friday rooms sell as weekend blocks rather than one-night gaps.
MaxLOS — Maximum Length of Stay
MaxLOS caps how many nights a booking can span under a specific rate plan. A MaxLOS of 7 means guests cannot book more than one week under that rate.
- When to use it: MaxLOS is less common than MinLOS. It is primarily used when a hotel has a promotional or discounted rate — an advance purchase rate, a flash sale, a direct booking discount — that it does not want guests booking for extended stays. Without MaxLOS, a guest can book an 18-night stay at a promotional rate intended for short breaks.
It is also used in markets where local STR regulations or hotel policies limit consecutive-night stays under certain license categories.
Stop Sell
Stop Sell closes a room type or rate plan entirely on one or all channels. No new bookings are accepted regardless of dates or length of stay. Unlike CTA or MinLOS, which restrict the shape of bookings, Stop Sell removes the option to book at all.
- When to use it: Stop Sell is applied when inventory is nearly exhausted and the remaining rooms should be protected for walk-ins, corporate accounts, or direct bookings at a higher rate than OTAs would generate. It is also used to remove a room type from a channel temporarily — for maintenance, a rate renegotiation, or a promotional period exclusive to another channel.
Stop Sell applied to a single channel while leaving others open is a standard practice for rate parity management. If an OTA is consistently undercutting the hotel's own rate, Stop Sell on that channel closes the pricing gap without affecting overall distribution.
Apply rate restrictions across all your OTA channels from one place
Smart Order's PMS and channel manager push CTA, CTD, MinLOS, MaxLOS, and Stop Sell to every connected platform simultaneously — so a restriction set once applies everywhere instantly.
How to Use Restrictions Together: Two Common Scenarios
Scenario 1 — Holiday weekend
A hotel anticipates high demand for a three-day public holiday weekend (Friday–Sunday). The goal is to maximize revenue from full-weekend stays and avoid one-night bookings that create gaps.
- Set MinLOS of 3 on Friday to require full-weekend coverage
- Set CTA on Saturday to prevent Saturday-only arrivals
- Set CTD on Sunday to prevent Sunday departures that leave a room vacant for the rest of the weekend
Together these three restrictions funnel all bookings toward Thursday–Sunday or Friday–Sunday patterns, which are the commercially optimal outcomes.
Scenario 2 — Approaching sellout
A 40-room hotel has 4 rooms remaining midweek and its last available Saturday night is in two days. OTA demand is strong.
- Set Stop Sell on OTAs for the remaining rooms, routing remaining demand to the direct booking engine at a premium rate
- Keep the direct booking engine open with a MinLOS of 1 — no length restriction — to accept last-minute walk-in value
- Once the final rooms sell, Stop Sell on all channels clears the date entirely
Mistakes That Cost Bookings
Leaving restrictions active after the peak period.
A MinLOS set for a holiday weekend that runs for two weeks afterward creates a booking gap for the regular weekday demand that follows. Restrictions must be time-boxed — set with a clear end date when they are created.
Setting MinLOS too high for the actual booking pattern.
If 80% of guests in your market book two-night stays, a MinLOS of 4 eliminates most of your demand rather than optimizing it. Use your booking history to set the minimum that filters out genuinely short stays without blocking normal demand.
Applying Stop Sell globally when channel-specific is sufficient.
Closing all channels because one OTA has a rate issue eliminates direct booking revenue as well. Stop Sell should be applied at the channel level by default.
Not coordinating MinLOS with rate plan structure.
A non-refundable rate with MinLOS of 3 and a flexible rate without MinLOS at the same price gives guests no reason to book the non-refundable option. Rate restrictions and rate plan design need to work together to give each plan a distinct value proposition.
FAQ
What is the difference between CTA and Stop Sell?
CTA (Closed to Arrival) blocks check-ins on a specific date while leaving the date available as part of a longer stay. Stop Sell removes the room from sale entirely — no booking of any type is accepted on that date. CTA shapes the booking pattern; Stop Sell eliminates it.
Can you apply rate restrictions to individual OTA channels?
Yes. Most channel managers, including Smart Order, allow restrictions to be set globally (applying to all connected channels) or per-channel (applying only to Booking.com, or only to Airbnb, etc.). Channel-specific restrictions are useful for rate parity management and for protecting direct booking inventory.
Does MinLOS affect existing reservations?
No. MinLOS and all rate restrictions apply to new bookings only. Guests who have already confirmed a stay are unaffected by any restriction changes made after their booking.
When should a hotel use MaxLOS?
MaxLOS is most useful when a discounted rate plan is being offered and the hotel wants to limit it to short stays. It is also used in markets with regulatory caps on consecutive STR nights or when a property has corporate rate agreements that specify stay length limits.
How do rate restrictions interact with OTA availability calendars?
When a restriction is pushed from the PMS via the channel manager, OTAs update their availability calendar to reflect it. A CTA on a Saturday will show as unavailable for arrival in the OTA's calendar even if rooms are physically open. Guests searching for Saturday arrivals will not see the listing as available, but guests whose stay spans Saturday — arriving Friday and departing Sunday — will still be able to book normally.
