Set Seasonal Rates and Minimum Stays

Seasonal overrides let you change nightly price, minimum stay, or availability for a defined date range. Use a focused range and preview the result before applying a broad change.

What you will accomplish

By the end of this guide, you will be able to complete a seasonal pricing override from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Prepare the approved date range, nightly rate, minimum stay, and affected units.
• Check existing reservations and provider-controlled pricing rules.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open the pricing calendar

Open Calendar Management or the connected pricing calendar for the relevant units. Move to the season you want to edit.

Expected result: The complete seasonal date range is visible.

Step 2: Select the units

Choose only units that share the same commercial rule. Separate properties with different currency, demand, or minimum-stay policy.

Expected result: The selection contains no unintended unit.

Step 3: Select the date range

Highlight the first through last night of the season. Review check-in boundaries around existing reservations.

Expected result: The override covers the intended sellable nights.

Step 4: Choose what to change

Set Nightly rate, Minimum stay, or Availability independently. Leave fields unchanged when the base or provider value should continue.

Expected result: The override changes only approved fields.

Step 5: Enter the seasonal values

Enter the correct currency amount and whole-night minimum. Block availability only when the nights should not be sold.

Expected result: Values match the approved pricing decision.

Step 6: Preview and apply

Review units, dates, mode, and resulting values before saving. Split a large range when holidays need different rules.

Expected result: The calendar shows the intended override.

Step 7: Verify guest-facing availability

Check a sample stay that meets the minimum and one that does not. Confirm the displayed price and availability agree with the calendar.

Expected result: Guests receive the expected rule.

Step 8: Review channel synchronization

When pricing is channel-managed, verify the provider received the change and no provider rule immediately overwrote it.

Expected result: CleanOver and the sales channel remain consistent.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.