Revenue management, answered

In what order do my pricing settings stack, and which one wins when they conflict?

Base price sets the floor, then seasonal adjustments layer on top, then minimum-stay rules shape which nights are sellable, and finally explicit date-level overrides win everything. When any two settings conflict, the most specific rule always takes precedence.

By Jack Murphy, Head of Revenue Management at UpRev. Running pricing for US vacation rental managers since 2017. Last updated September 1, 2026.

The Hierarchy in Practice

Think of it as a funnel: base price establishes your year-round anchor, seasonal bands adjust that anchor across defined windows, and day-of-week weights fine-tune within those bands. A date-level override sits above all of them because it is the most explicit instruction you have issued for that exact night. If your seasonal band and a manual override disagree, the override wins without exception.

Where Minimum-Stay Rules Fit In

Minimum-stay requirements do not change the price itself, but they control whether a night can be sold at all, which makes them a gating layer between your pricing stack and the actual booking. A three-night minimum applied to a holiday weekend can effectively nullify a strong price signal by killing orphan nights around it. Always audit minimum-stay settings alongside your pricing layers, not separately, or you will price nights that can never actually book.

Managing Conflicts Across a Portfolio

With multiple properties under management, conflicts most often surface when a blanket seasonal adjustment runs over a property-specific override a homeowner or your team set months earlier. Build a standing review cadence, at least monthly for high-demand calendars, to surface any overrides that are silently overriding your seasonal strategy. Document every override with a reason and an expiration date so nothing lingers past its purpose.