[CMS] Revenue Manager can set Max Stay Configuration by date range in Bulk Update Restrictions

1. Update: The Bulk update > Restriction screen supports several restriction types (e.g. Minimum stay) but not Maximum stay. Revenue Managers need to cap length-of-stay per room type/rate plan/channel for specific periods, entered per weekday within a date range, then synced to OTA Room Sale using the correct mapping code.

2. Navigation: CMS > OTA Room sale > Bulk Update > Restriction 

3. Create Maximum stay at Restriction

• Select update (1): Maximum stay
• Room type (2)
• Rate plan (3)
• Channel (4)
• Add date range (5)
• Select date range (6)
• Input the value of max stay in textbox for each day 7). Defaut is 90 
• Click “copy” icon (8) to paste the value of first max stay in the first textbox into the rest textboxes of max stay within selected date range of that row. 
• Click “cancel” icon (9) to not save the change
• Click Update button (10) to complete the setting. 

• Copy and Paste the created max stay 
  • Click “copy” icon (1) to copy the created max stay row
  • Click “paste” icon (2) to generate the new row behind.
  • The textbox of max stay is disabled → because the day of the week is out of the period time
    • For example:
      • Max stay 1 (period time from 2026-10-15 – 2026-10-20) start from Thursday (2026-10-15) to Tuesday of next week (2026-10-20) → Wednesday’s textbox is disabled
      • Max stay 2 ( period time from 2026-10-21 – 2026-10-25) start from Wednesday (2026-10-21) to Sunday (2026-10-25) → Monday’s and Tuesday’s textbox are disabled

• Note that the next rows of max stay must not overlap the period time with the rows above. If not, system will highlight the row that set up the overlapping time and click update will save unsuccessfully as well as the error message ”Date ranges are overlapping. Please adjust.”

After saving, the max stay is updated on OTA room sale screen:

*Note that If a rate is updated in both a source (like Bulk Update Restriction) and directly on the OTA Room Sale grid, the most recent timestamp wins

4. Reservation on BE

• Search flow checks LOS (length of stay) against Maximum stay right after saving  → Check the total of LOS against the Minimum of Maximum stay of each day within the LOS

• If LOS (length of stay) of reservation < or = the Minimum of Maximum stay of each day within the LOS  → Display mapping code that meets the conditions.
  • For example, LOS (length of stay) of reservation is 10 and the Minimum of Maximum stay of a day within the LOS is 10 (or 11)  → Display mapping code that meets the conditions. 

• If LOS (length of stay) of reservation > the Minimum of Maximum stay of each day within the LOS  → NO Displaying any mapping code.
  • For example, LOS (length of stay) of reservation is 12 and the Minimum of Maximum stay of a day within the LOS is 10 (or 11)  → NO Displaying any mapping code and message pop up “A stay of 12 nights is not available for these dates. You can book up to 10 nights” and warning “No available rooms match your selected dates. For longer stays, please check our long-stay policy on our website or contact the hotel directly for more information.

5. User activity log (UAL)

• Activity group: OTA
• Action: Bulk update restriction

Detail: