Rate Plan Settings
      Back to home
      1. Knowledge base
      2. Rate Management
      3. Rate Plan Settings

      Managing Maximum Length-of-Stay Restrictions

      You can now define maximum length-of-stay (LOS) restrictions in SabeeApp, just like minimum stay restrictions. This guide walks you through how to configure, update, remove, and link maximum LOS restrictions, as well as the limitations imposed by various sales channels.

      🔧 Setting Up Maximum Stay Restrictions

      To configure maximum stay restrictions:

      1. Go to Prices > Rate plans.
      2. Select the desired rate plan.
      3. Click Show tools to access the Minimum and Maximum stay tabs.
      4. Open the Maximum stay tab.

      📆 Set Maximum Nights (in Bulk)

      Bulk updates require you to first define a date period. Without selecting a date, room selection and restriction updates are disabled.

      • After selecting the date ( and also pressing Apply) and room(s), you’ll see a message below the input field showing the minimum nights already set. This ensures you don’t enter a maximum value lower than the minimum.
      • The message adjusts dynamically based on the selected rooms.

      ⚠️ Example: If a room has a minimum of 4 nights set, inputting 3 as the maximum will trigger an error.

      • The text in the message changes based on the selected rooms, as different values could have been set for different rooms. If multiple rooms are selected, the highest value is chosen - i.e. if one room has 2 as mininmum stay, the other has 3 as minimum stay, 3 will be displayed here as the minimum value for the maximum nights input field.
      • Once valid values are entered, click Update to save. Invalid entries will produce an error, and no changes will be saved.

      • After a successful update, the table refreshes and the Maximum nights row will be filled.

      ✏️ Updating Maximum Nights Individually

      You can also update restrictions one cell at a time directly in the table.

      • Enter the desired number into the cell.
      • The system validates it against the current minimum nights for that day.
      • If any value is invalid during a multi-cell edit, none of the changes will be saved.

      ❌ Removing Maximum Stay Restrictions

      Unlike minimum stays (where setting the value to 1 removes the restriction), maximum stays require using the Remove restriction function.

      To remove a maximum stay restriction:

      1. Select the date range and rooms.
      2. Click Remove restrictions.
      3. Only restrictions within the selected range and rooms will be deleted.

      Minimum stays can still be removed either by setting the value to 1 or using the same removal method as for maximum stays.

      🔗 Linking LOS Restrictions Across Rate Plans

      Not Linked to Master Prices

      If a rate plan isn’t linked to Master Prices:

      • You can still link length-of-stay restrictions to Master Prices using the toggle.
      • Once linked, restrictions must be managed via Master Prices.
      • Min and max nights are linked together, not separately.

      Linked Rate Plans

      If a rate plan is linked:

      • It will always link LOS restrictions to Master Prices or the immediate parent rate plan (in case of chained linking).

      Example:

      • Master Prices → Weekend Rate → Weekend Rate HOLIDAY
      • If Weekend Rate links its LOS restrictions to Master Prices, and Weekend Rate HOLIDAY links to Weekend Rate, all three will inherit LOS rules from Master Prices.

      You can also break the chain by turning off the toggle at any level.

      🌐 Channel-Specific Length-of-Stay Limits

      Different online sales channels (such as Booking.com or Expedia) have their own rules and limitations for minimum and maximum length-of-stay (LOS) restrictions.

      🔎 Viewing Channel Limits

      You can check the supported LOS limits for each connected channel by clicking the Limits on channels button.

      Note: This button is only visible if the rate plan is connected to at least one external channel.

      ⚠️ What Happens if You Exceed a Channel’s Limit?

      If you enter a LOS restriction that exceeds a channel’s supported maximum, SabeeApp will automatically adjust the value before syncing.

      For example, if you enter 45 nights for a rate plan connected to Booking.com, which allows a maximum of 30 nights, SabeeApp will sync only 30 nights to Booking.com.

      No warning or error will be shown — the system simply syncs the highest allowed value for that channel.

      ⚙️ Important Notes About Channel Behaviour

      • Custom Settings in Channel Extranets: Some channels let you configure custom LOS rules directly in their extranets.

        If these are set manually:

        • SabeeApp typically cannot detect or override them.
        • This may cause mismatches between what you see in SabeeApp and what’s enforced on the channel.

      • Unknown or No Limits: For some channels, LOS limits are not provided via their API.

        In these cases:

        • The maximum LOS value may be unknown, or
        • The channel may not enforce any limits at all.

      As a result, it’s always a good idea to verify LOS rules directly in each channel’s extranet if you're unsure how a restriction will behave.

      📝 Updates to Minimum Nights Functionality

      The same enhancements applied to maximum nights—such as date/room selection and validation—have also been implemented for minimum stay restrictions.

      🛒 Maximum Nights on the Internet Booking Engine (IBE)

      • Not supported on the current/old IBE.
      • Supported only on IBE 3.0.

      🔌 How to Handle Maximum Stay Restrictions with the Connect API

      If you are using your own booking engine and integrating with SabeeApp via the Connect API, it’s important to manage maximum stay restrictions manually on your side.

      What You Need to Know:

      • SabeeApp enforces stay restrictions (like maximum nights) on its own Internet Booking Engine (IBE) — if a guest books through SabeeApp’s IBE, the rules are applied automatically.

      • However, the Connect API does not block bookings that exceed these restrictions. This means your custom booking engine will not automatically prevent overstay bookings unless you add that logic yourself.

      What You Should Do:

      1. Retrieve restrictions from SabeeApp using a POST request to the endpoint: availabilityandrates/restriction.

      2. Check the guest’s intended length of stay against the maximum allowed stay for the selected dates and room.

      3. If the stay exceeds the limit, display an appropriate message or block the booking from continuing.

      ⚠️ Please note: Steps 1 and 2 need to be developed as part of your custom booking engine.

      By implementing this, your booking engine will properly respect the maximum stay rules configured in SabeeApp and help prevent invalid bookings.
      If not implemented, overstay reservations will still be submitted to SabeeApp, even if they exceed the configured restrictions.