Skip to main content

Restrictions File

The Restrictions file is used to set Stop Sales, booking limits, and stay restrictions. It defines when a room or rate can or cannot be sold, controlling the operational conditions applied during a date range.

Purpose​

This file is used to define:

  • validity period
  • booking limits
  • minimum and maximum release windows
  • free sales status
  • minimum and maximum stay rules
  • arrival and departure closure conditions

Example​

Download the example Restrictions file (CSV)

Field definitions​

FieldTypeDescription
hotelCodeStringHotel associated with the restriction.
rateCodeStringRate plan affected by the restriction.
roomCodeStringRoom type affected by the restriction.
startDateDateStart date of the restriction validity.
endDateDateEnd date of the restriction validity.
bookingLimitIntegerMaximum number of bookings allowed in the date range.
minReleaseIntegerMinimum number of days before arrival that the product can be booked.
maxReleaseIntegerMaximum number of days before arrival that the product can be booked.
freeSalesBooleanWhether the room can be sold freely.
minStayNightsDuringStayIntegerMinimum stay requirement during the stay period.
maxStayNightsDuringStayIntegerMaximum stay requirement during the stay period.
minStayNightsOnArrivalIntegerMinimum stay requirement on arrival day.
maxStayNightsOnArrivalIntegerMaximum stay requirement on arrival day.
closeMasterBooleanCloses the room/rate at master level.
closeOnArrivalBooleanCloses product sales for arrival dates.
closeOnDepartureBooleanCloses product sales for departure dates.

Notes​

Restrictions are critical because they guarantee that the product is sold under valid commercial and operational conditions. This file normally works together with the Rates and Rooms files to define the effective sales logic.