Minimum stay, closed to arrival, closed to departure and maximum stay all interact with each other and with each OTA differently, and this explains what each one actually does and where they conflict.
Rate restrictions — minimum stay, closed to arrival, closed to departure, maximum stay — are some of the most useful tools for managing demand, and also some of the easiest to set up in a way that quietly contradicts itself across channels. Understanding what each restriction actually controls, and how they interact when more than one applies to the same date, is what prevents a restriction meant to help from accidentally blocking bookings you wanted.
A minimum stay (min stay) restriction requires a booking to cover at least a set number of nights to be made for a given date — useful for protecting high-demand dates from single-night bookings that block a longer stay around them. Closed to arrival (CTA) prevents a guest from checking in on a specific date, while still allowing bookings that pass through that date having already arrived earlier — it targets check-ins specifically, not the whole stay. Closed to departure (CTD) is the mirror of that, preventing checkout on a specific date while allowing stays that continue through it. Maximum stay caps how many nights a single booking can cover for a given date, which is less commonly used but relevant around events where you want turnover rather than one long booking occupying a room.
Each restriction answers a different question — how long, can you arrive, can you leave, how long at most — which is exactly why combining more than one on the same date needs care.
A min stay of three nights combined with a CTA on a date in the middle of that window can create a combination where no valid booking actually satisfies both conditions for a guest trying to arrive on that exact date — the restrictions aren't contradicting each other in the system, but together they can produce a result that looks, from the guest's side, like nothing is bookable despite rooms being available. Min stay and max stay set on overlapping date ranges with different values can similarly narrow the valid stay length to a range that doesn't match what you actually intended, especially if one was set for a different event or season and never revisited. The restriction that's technically working correctly can still produce a result nobody wanted, simply because two correct rules combined in a way nobody checked.
Most OTAs support the core set — min stay, CTA, CTD — but the exact way they're configured, displayed to the guest, and how far in advance a change takes effect can differ by platform, which is why a restriction set correctly on one channel can behave slightly differently on another even when pushed through the same channel manager. Checking the guest-facing side of each OTA for the specific date in question, rather than only the extranet's own confirmation that a restriction was applied, is the only reliable way to see what a guest searching that date actually encounters.
Read-back verification covers restriction pushes the same way it covers rates and availability — when a min stay, CTA, CTD or max stay restriction is sent to a channel, the system reads back what the channel actually stored and confirms it matches what was intended, catching a push that didn't apply as expected. The calendar's bulk edit and date-shift tools also make it faster to review and adjust restrictions across a date range at once, rather than checking each date individually. If restriction conflicts have blocked bookings you didn't intend to block, that combination is the structural fix — you can try it on the public demo at try.primehostpartners.com without signing up.