Virtuosos of Price

PriceLabs Minimum Stay Settings

Minimum stay settings sit at the intersection of two things that pull in opposite directions: your preference for longer, lower-friction bookings and your guests' preference for flexibility. When those two things are out of balance, the calendar fills with gaps that no amount of rate adjustment will fix. For example, a three-night minimum can prevent a guest from booking an otherwise available two-night gap. Whether accepting that shorter stay is worthwhile depends on operating costs, calendar geometry and the demand still likely to book.

The problem is that minimum stay rules are easy to set and easy to forget. A host configures a baseline in PriceLabs during onboarding, the platform applies it across the calendar, and months pass before anyone looks at whether the rule is still serving the listing. By then, the booking history reflects the rules that were in place, including the shorter reservations they excluded. This guide is about understanding what the settings actually control, how to read the signals that tell you something is wrong, and how to make changes that are grounded in your own data rather than in assumptions.

What PriceLabs Minimum Stay Settings Control

PriceLabs gives you several layers of minimum stay control. First identify the active mode and scope. Recommended mode applies recommendations that refresh monthly; Custom mode lets you edit your rules, including suggestions from the recommendation engine. Review either against your operating constraints. PriceLabs' recommendation guide explains the distinction.

Minimum-stay inheritance selects one complete rule set, in this order: listing, subgroup, group, account. The sets do not merge. A listing-level default can therefore displace inherited orphan and last-minute rules. Check the effective set using PriceLabs' customization hierarchy.

Default minimum stay is the Custom-mode fallback. Lowest Minimum Stay Allowed is the separate lower bound, including for date overrides. Recommended mode has lowest and highest bounds plus a separate Lowest Orphan Gap allowed. Inspect that gap bound separately; the documentation does not establish one universal cross-mode floor. Minimum-night settings describes these controls.

Seasonal minimum-stay profiles apply a saved minimum-stay set to a seasonal date range. That profile replaces the account, group and listing sets. The default Lowest Minimum Stay still applies unless the seasonal minimum-stay profile specifies its own lower bound. PriceLabs' profile guide explains this exception.

Day-of-week rules let you apply different minimums depending on which day a stay begins. A Friday arrival might carry a different minimum than a Tuesday arrival, because the demand profile for those two entry points is different.

Last-minute rules respond to lead time. Orphan-gap rules respond to gap length. Review both: removing a shorter-stay last-minute suggestion can leave an orphan rule allowing that stay length. This distinction is documented in the recommendation guide.

Date-specific minimum-stay overrides handle exceptions, subject to the applicable lower bound and orphan rules. In Custom mode, priority runs from lowest allowed stay to orphan, date override, adjacent after, adjacent before, far-out, last-minute, then default. Orphan rules normally only reduce the requirement. Support-enabled options can allow increases or protect date overrides from orphan reductions. Check the active options and each date's tooltip against the minimum-night guide.

What PriceLabs does not control

The connected route matters. PriceLabs documents sending minimum stays to Airbnb directly, and advises hosts using a PMS or channel manager to connect PriceLabs through that system. A rule displayed in PriceLabs is a documented expectation until you confirm it at the destination. It does not establish a ranking improvement. The Airbnb integration guide describes the route and readback.

Checklist: settings to locate before making any changes

Active mode, complete inherited set and default minimum stay
Lowest allowed stay, plus Recommended-mode highest and orphan bounds where available
Seasonal minimum-stay profiles, dates and any inherited lower bound
Day-of-week, last-minute, orphan, adjacent and far-out rules
Date overrides and any advanced options affecting their priority
Actual PriceLabs connection, destination restrictions and any other system writing them

PriceLabs documents overwriting existing Airbnb minimum-night settings with its configured values. A mismatch calls for checking delivery, the connection and competing writers, rather than assuming a higher manual Airbnb value wins. Read Airbnb's Custom Trip Lengths after syncing. This guide's instructions are based on documentation checked October 14, 2026; no live account sync was tested.

When the calendar does not show the minimum you expected

Record the listing, connected PMS or channel, dates, timezone and intended stay length. Start by reading the effective calendar value and its tooltip. In the documented PriceLabs interface, open the listing's Customizations, choose Stay Restrictions, and inspect Minimum Stay Settings. Confirm Custom or Recommended mode before following a rule hierarchy. Minimum-night guide

Symptom	Read-only check	Safe recovery or stopping point
A group orphan rule disappeared	Check listing → subgroup → group → account scope. Minimum-stay sets replace one another as complete sets.	Compare the selected complete set with the intended one; do not assume missing settings merge from another level.
A seasonal default is lower, but the calendar is not	Inspect the seasonal Min Stay Profile and its lower bound. A default lower bound can carry into that profile.	Confirm whether the seasonal profile deliberately supplies its own bound before proposing a change.
A date override still permits a shorter gap stay	Inspect applicable orphan behavior and support-enabled options. Normal orphan reductions and the optional protection for date overrides have different behavior.	Retain the actual account flags; stop if their status or priority is unclear.
A Recommended rule goes below the expected ordinary bound	Read the separate Lowest Orphan Gap setting. The guide allows it to differ from the regular lower bound.	Review that specific mode's bounds and tooltip; do not apply the Custom-mode order universally.
A last-minute rule is already shorter than a gap rule	Compare the effective values; ordinary orphan behavior reduces requirements instead of increasing them.	Keep the documented increase option separate from default behavior.

The inheritance check is supported by PriceLabs' hierarchy. The seasonal check and its lower-bound exception are supported by Min Stay Profiles. Other rule checks use the minimum-night guide. These checks diagnose configured restrictions; they do not prove that a shorter stay would be profitable or that the minimum caused a ranking change.

When PriceLabs and the channel disagree

Confirm the writer and destination first. An operator using a PMS should check PriceLabs → PMS → channel, rather than changing an old direct Airbnb record. Read the current PriceLabs value, sync status, any recorded error and the receiving PMS/channel value for identical listing, stay dates, currency and guest count. The Airbnb integration guide documents this route and destination review.

If the sync toggle is off, the displayed PriceLabs prices have not been enabled for delivery. If it is on, check the last sync and next scheduled daily run before treating a normal queue interval as a failed update. A manual Sync Now requires the toggle to be on and is a live publishing action; do it only within the operator's authority. A fresh timestamp still needs a destination check. Sync timing and controls

For Hospitable, inspect the connected property identity and the markup configured for each channel. The vendor also documents a conflict with Hospitable's inbuilt dynamic pricing and calls for checking the Hospitable destination after PriceLabs updates. A missing markup or changed property ID can explain errors. Do not automatically delete records, disable another pricing system or create a dummy reservation as a diagnostic shortcut; preserve the existing setup and escalate the named error. PriceLabs and Hospitable integration

Finally inspect whether the intended stay can be selected on the actual booking channel without submitting a reservation. Record the shown restriction and quote. An absent search result alone does not identify the restriction or establish a ranking penalty. Stop when the active writer, supported field or destination value remains unknown; another rate change will not resolve missing evidence.

The linked vendor guides contain interface illustrations, including older example dates. They are documentation images, not screenshots of a current Revande account. This update verifies source instructions; it does not claim a live account sync test.

Compare the products, billing basis and testing limits in the PriceLabs vs Beyond comparison.

How Minimum Stay Adjustments Affect Booking Velocity

Booking velocity, the pace at which nights on your calendar convert to confirmed reservations, is sensitive to minimum stay in ways that are not always obvious.

A trip shorter than the effective minimum cannot be booked under that restriction. Check whether a guest can book your intended dates and trip length before diagnosing a visibility problem. A failed booking attempt alone does not establish an Airbnb ranking penalty or prove why a search result is absent.

When your minimum stay is lower than what the market typically books, you may fill nights quickly but with shorter stays that leave gaps on either side. Whether those gaps fill depends on how your calendar looks to the next guest searching. A shorter gap admits fewer stay lengths, but its chance of filling also depends on lead time, price and local trip patterns. Do not infer the size of that demand from gap length alone.

Worked example: reading your own booking length data

To understand whether your current minimum stay is aligned with actual demand, do the following:

Pull your confirmed reservations for the past rolling period you consider representative, at least three months, ideally six.
Record the length of each stay.
Sort them and compare stay lengths with the effective restrictions when they were booked. A cluster at the minimum is a hypothesis to investigate, not evidence of how many shorter stays were excluded.
Longer confirmed stays also cannot prove that the minimum has no effect: the history contains only reservations your rules permitted.
Measure unbookable gaps separately. Compare their length and lead time with permitted stay lengths, operating costs and available market evidence before considering a change.

Reservation exports and a spreadsheet can support this review. PriceLabs' Portfolio Analytics reports also show length of stay and booking windows, and explicitly warn that the data only reflects allowed reservations. Record any missing history or unavailable market comparison.

Decision rule: Treat booking-length clustering as a prompt for review. If gap evidence and operating economics support testing a shorter stay, choose a bounded date range, record the effective rule and rollback value, and set a review date before changing it. Compare booked nights, lodging revenue, turnover cost and remaining gaps with a suitable baseline. A change in bookings alone does not prove that the new minimum caused it.

Balancing Minimum Stay Rules with Market Demand

The right minimum stay for your listing is not a fixed number. It is a function of your market, your calendar position, and the time of year. A setting that works well in peak season can actively harm you in shoulder season, and vice versa.

Understanding your market's trip length profile

Your booking history shows accepted trip lengths, not all guest searches. Use available market length-of-stay and booking-window data alongside it. Guest searches for comparable properties can reveal availability for specific dates and stay lengths, but search placement also varies with other factors. Record dates, guest count, filters and total price; an absent listing does not reveal its minimum stay by itself.

Seasonal logic for minimum stay

For a high-demand period, consider whether accepting a short booking would block plausible longer stays. For a slower period, weigh the net contribution of a shorter stay against leaving the dates open. Demand alone does not determine the right minimum: costs, lead time and remaining calendar shape also matter.

Use these as hypotheses for a measured review, not as automatic seasonal rules.

Worked example: building a seasonal minimum stay structure

Suppose your market has a clear peak season and a clear slow season, with shoulder periods on either side. A starting structure might look like this:

Peak: higher minimum, set to capture multi-night stays during high-demand windows
Shoulder: moderate minimum, with gap-filling automation active
Slow season: lower minimum, prioritizing occupancy over stay length

For a recurring seasonal structure, use a saved Min Stay Profile in a Custom Seasonal Profile. In PriceLabs' documented interface, review the listing, open Customizations, then Seasonal & Minimum Prices and Custom Seasonal Profile. Name the range and select its Min Stay Profile. Confirm its lower bound: a lower seasonal default can remain constrained by the default Lowest Minimum Stay when the seasonal profile has no lower bound of its own. Check the current interface and effective dates before saving; this is a documented setup path, not a tested account result.

Checklist: before changing a minimum stay setting

What is the current occupancy rate for the period you are changing? (Measure it from your calendar.)
What is the average stay length for confirmed bookings in that period?
Are there gaps on the calendar that a lower minimum might fill?
Are there high-value dates where a higher minimum would prevent a short booking from blocking a longer one?
Have you checked that the change will sync correctly to Airbnb?

Common Missteps in Setting Minimum Stays

Most minimum stay problems fall into a small number of patterns. Recognizing them in your own calendar is faster than diagnosing from first principles.

Setting a high minimum and leaving it year-round

A host might set a three or four-night minimum to reduce turnover costs and leave it unchanged. That can prevent shorter bookings in periods when they would otherwise be worth considering. Review the effective rule against costs, permitted stays and remaining demand before deciding whether a seasonal profile or another bounded change is appropriate.

Ignoring orphan gaps

An orphan gap is an open stretch between unavailable dates. When it is shorter than the effective minimum, that restriction can make it unbookable. Check the orphan rule's gap-length range and lead-time range. An allowed shorter stay makes a booking possible; it does not guarantee demand or revenue.

Find open stretches between bookings or blocked dates and compare their length with each date's effective minimum. Mark which gaps are unbookable under that rule, then review whether an orphan adjustment is permitted and economically sensible.

Conflicting settings between PriceLabs and Airbnb

PriceLabs' documented overwrite behavior gives you a clear expected value to check. If Airbnb differs, inspect the last successful sync, the selected PMS route and any other writer. The direct integration guide also identifies Smart Pricing conflicts and possible sync failure when Airbnb rulesets overlap with PriceLabs check-in/out restrictions. Diagnose the named conflict before removing a rule that serves another purpose.

Using date-level overrides instead of seasonal rules

Date-level overrides are useful for exceptions. When they become the primary way a host manages minimum stay, the calendar becomes difficult to audit and maintain. A host who has applied dozens of individual overrides over several months may not be able to reconstruct the logic behind them. Seasonal adjustments are transparent and easier to review.

Not testing the guest-facing experience

After an authorized change, inspect the effective PriceLabs value and tooltip, then the receiving PMS if used, and Airbnb's Custom Trip Lengths. Open the listing directly for the intended dates and trip length to check booking eligibility. Record what each destination shows and when. A search appearance or sender success message alone is insufficient to confirm restriction delivery.

Decision rule: Audit an override whose reason, owner or expiry you cannot explain. Move recurring seasonal logic into a profile only after checking inheritance and lower bounds. Keep documented one-off exceptions where they serve a clear purpose.

Reviewing Minimum Stay Settings for Revenue Impact

Minimum stay settings should be reviewed on a schedule, not only when something appears to be wrong. A quarterly review is a reasonable cadence for most listings. A monthly review is appropriate during periods of active experimentation or when the market is changing.

What to record and track

The table below describes the data points worth capturing at each review, where to find them, and what a change in each metric might indicate.

Data point	Where to find it	What a change might indicate
Average confirmed stay length	Reservation history or supported analytics	Change in accepted stays; does not measure excluded demand
Number of unbookable orphan gaps	Calendar audit with effective restrictions	Dates worth reviewing for a permitted shorter stay
Occupancy for the period	Airbnb performance dashboard	Overall demand level, context for other metrics
Nights lost to gaps shorter than minimum	Manual calendar audit	Gap-filling automation may need adjustment
Booking lead time distribution	Airbnb reservation history	Whether last-minute demand is present and being captured
Effective minimum stay at the destination	PMS if used, Airbnb Custom Trip Lengths and direct booking check	Shows whether the intended restriction reached the checked dates

Worked example: a quarterly review process

At the start of each quarter, pull the data points above for the previous quarter. Compare them to the quarter before that. Ask three questions:

Did accepted stay lengths change? Compare effective restrictions, dates and lead times before interpreting that as a demand change.
Did unbookable gaps increase? Check whether booking geometry, blocks or a rule change explains them.
Did occupancy or net lodging revenue change unexpectedly? Review price, availability, market conditions and costs alongside the minimum. A before-and-after comparison can raise a question without establishing its cause.

After answering those questions, decide whether to change anything. Document what you changed and why. In three months, you will have a record to compare against.

Checklist: quarterly minimum stay review

Pull average stay length for the past quarter
Count orphan gaps on the calendar for the past quarter
Check occupancy for the past quarter
Review whether seasonal adjustments are correctly set for the coming quarter
Confirm gap-filling automation thresholds are appropriate for the coming period
Verify live minimum stay on Airbnb matches PriceLabs settings
Document any changes made and the reasoning behind them

The following guides cover topics that interact directly with minimum stay settings. Reading them alongside this guide will give you a more complete picture of how the settings work together.

Where this becomes someone else's job

Reviewing minimum stay settings quarterly, auditing orphan gaps, maintaining seasonal adjustment logic, and verifying that PriceLabs is syncing correctly to Airbnb is work that compounds over time. Each review takes less time when the underlying structure is clean, and more time when it has accumulated months of ad hoc overrides and untested assumptions. At some point, the question is not whether you understand the settings but whether you have the time and attention to manage them consistently.

Revande's Performance service includes a full software stack for dynamic pricing, daily adjustments made by experienced rate strategists, Airbnb listing performance monitoring with email alerts for low visibility or booking conversion, and monthly reports. Minimum stay decisions are part of the rate strategy work, not an add-on.

Revande's Maestro service includes everything in Performance, plus done-for-you listing optimization, proactive Airbnb listing performance monitoring with visibility and booking conversion issues handled for you, compatibility with Airbnb or your channel manager, and ongoing listing refinements. If minimum stay settings are one item on a longer list of things you have not had time to address properly, Maestro is designed for that situation. Compare Revande's revenue management services or read the managed PriceLabs service guide to see how responsibility differs from software access.

Get Started