Sales restrictions: conditions for selling a date

This content is not available in your language yet.


Why	Sell a date on your terms: a minimum stay, closed to arrivals, closed for OTAs only, or closed entirely.
Who	The administrator who manages occupancy and revenue.
What you’ll get	Restrictions set for a single date in the price manager calendar, and in bulk for a period; plus a clear picture of what the channels receive.
Limitations	Restrictions apply at the point of sale: bookings that already exist are not changed retroactively.

A price says how much a date costs; restrictions say on what terms it can be sold: a minimum stay, no arrivals, closed for channels. Both live in the “Price Manager”. Prices are covered in Change prices: one date or in bulk; this article is about the terms of sale — what you can restrict, how to set it for one date or in bulk, and what the channels will see.

What you can restrict

The set of restrictions is the same everywhere — only the place of editing differs: a calendar cell or the bulk update.

Min stay and Max stay — the floor and the ceiling of the length of stay: an arrival on this date is only possible if the stay is not shorter than the minimum and not longer than the maximum.
Min at check-in and Max at check-in — the paired limits, applied when a stay checks in on this date.
Min days before arrival and Max days before arrival — how far in advance the date can be booked: the shortest and the longest horizon.
“Closed for sales” — the date is not sold at all: neither through channels nor directly.
“Closed for OTAs” and “No OTA” — two names for the same restriction: the date is closed for channels only; direct bookings — the hotel website and the front desk — keep going.
“No check-in (CTA)” — a stay cannot start on this date.
“No check-out (CTD)” — a stay cannot end on this date.
“Avail.” with the ”+/-” field — an availability adjustment: by how many rooms to increase or decrease the sale on the date.

The same restriction goes by different names across the interface. Full closure of a date is “Closed for sales” in the calendar and in the bulk update, and “Closure” among the inheritance switches in the rate plan card. The channel ban is “Closed for OTAs” in the cell editor and “No OTA” in the bulk update; in inheritance it is “OTA limit” with a numeric “OTA” field.

For child rate plans, every restriction can be inherited from the parent — the inheritance switches in the rate plan card control this. How inheritance works is covered in the article about rate plan inheritance.

One date: in the calendar cell

A one-off edit is made in the price manager calendar — the same cell editor as for the price; here we look at the restriction buttons and fields:

Open the “Price Manager” in the left menu — the “Calendar” tab opens by default.
In the filters, pick the “RATE PLAN”, the “ROOM TYPES”, and the “START DATE” — the grid shows a 14-day window from that date.
Click a price cell in the row of the room type you need — an editor opens right in the cell: the “Price” field and, next to it, restriction buttons and fields.
Turn on the “Closed for sales”, “Closed for OTAs”, “No check-in”, and “No check-out” buttons and, if needed, fill in the “Min”/“Max” fields: two numeric sets — for the stay and at check-in, one more — for the days-before-arrival limits, plus the “OTA” and ”+/-” fields.
Click “Done” — the restrictions apply to that date. “Cancel” closes the editor without changes.

Result: the terms of sale are set for a specific date and apply when that date is sold.

In bulk: for a period

When the terms are needed for a range — weekends, holidays, the high season — use the “Bulk Update” tab:

Open the “Bulk Update” tab.
In the “1. SCOPE” section, set the rate plan, the “From”/“To” period, the room types (with “Select all” and “Exclude all” buttons), the days of week (the “Weekdays”, “Weekends”, “All” shortcuts), and, if needed, “Exclude dates”.
Open the “3. RESTRICTIONS” section: the numeric fields “Min stay”, “Max stay”, “Min at check-in”, “Max at check-in”, “Min days before arrival”, “Max days before arrival”, the “OTA” field, and “Avail.” (”+/-”).
Four switches have three states — “Yes”, “No”, ”—”: “Closed for sales”, “No OTA”, “No check-in (CTA)”, “No check-out (CTD)”. “Yes” turns a restriction on for the selected dates, “No” turns it off, and ”—” leaves it untouched: on those dates the restriction stays as it is.
Click “Check and apply” — the button becomes active once the settings have something to apply.

Result: the restrictions are applied to every date in the scope in a single action.

The “2. PRICES” and “4. PERIODIC MEAL PRICE” sections are about money, not about the terms of sale; they are covered in the article about changing prices.

Preview before applying

To the right of the form there is a panel with the “Overview” and “Changes” tabs. The “Changes” tab is the preview: the “Result of the current bulk update settings” — what you will get with the current field values. The “Recalculate” button refreshes the picture; until the settings are complete, the tab shows “No data to preview”.

The “Prices”/“Restrictions” radio switches the preview between the price level and the restriction level. This switch exists only here, in the bulk update preview; there is none in the calendar.

What goes to the channels

Restrictions are exported to the connected channels together with prices and availability — there is no separate “send” step. “Closed for sales” zeroes out the date’s availability in every channel: nobody can buy that date. “Closed for OTAs” is softer: channels cannot sell the date, while the hotel website stays in the game — direct bookings continue.

Delivery to the channels is checked in the delivery log: Delivery log: verify what was sent to channels. Bookings sold by channels are covered separately: Bookings from channels: what arrives in the calendar.

Honest boundaries

Restrictions work at the point of sale. They do not change existing bookings retroactively: remove “No check-in” or lower the minimum stay — the bookings that already exist stay as they are.
Restrictions protect sales but do not hard-block the front desk. In the quick booking form, a “Confirm override” checkbox may appear when a restriction is violated; the behavior is enabled on the “Rate Plans” screen, “Settings” tab. While it is off, restrictions are shown as information and do not block the form: the front desk can consciously book over a restriction.
The terms of sale are edited in the price manager, not in the Planner: the Planner is about bookings. To close a date, use “Closed for sales” in the “Price Manager”.