What are Orphan Gaps, and How to Use PriceLabs to Leverage Them?

An orphan gap is a short run of unbooked nights, usually one to three, sitting between two confirmed reservations and too short for a guest to book under your current minimum stay. The gap is not caused by weak demand. It is caused by your own settings, which is why it is fixable. Left alone, those gap nights expire unsold while you still carry the fixed costs of owning the property. This guide covers what creates orphan gaps, five ways to prevent them before they appear, the five PriceLabs customizations that handle gaps, and when leaving a gap open is the better call.

What are orphan gaps?

Orphan gaps, also called booking gaps, gap nights, or orphan days, are unoccupied dates trapped between two bookings. Say your calendar shows reservations from 22 to 27 February, 2 to 4 March, and 6 to 7 March. That leaves 28 February, 1 March, and 5 March open. If your default minimum stay is two nights, nobody can book 5 March at all, because a single night does not clear the threshold. Those orphan days stay available in your system and invisible on the search results guests actually see.

The cost is larger than the nightly rate suggests. A gap night still absorbs a share of your fixed monthly costs, and if a guest does book either side of it, you are often paying for a turnover clean on both ends anyway. For a manager running 6 to 49 units, two unbookable nights a month per property compounds into a meaningful slice of annual revenue that never appears in any report, because unsold inventory does not generate a line item.

What causes orphan gaps

Four things create most of them. A minimum stay set higher than how your market actually books is the biggest one, and the fix starts with setting minimum stays against real market data rather than a number that felt right when you listed. Cancellations are the second cause, since a cancelled six night stay can leave an awkward booking gap once the dates either side fill in.

The third is fixed check-in and check-out days. If you only accept Friday arrivals because that is when your cleaner works, every booking that ends on a Tuesday leaves three nights nobody can reach. The fourth is a booking window that has shortened faster than your rules have adapted, a pattern covered in the 2026 revenue management planning guide. Far-out dates lock into short stays, and the leftovers surface later.

How to prevent orphan gaps without any software

These five moves work on Airbnb, Vrbo, and Booking.com directly, with no pricing tool involved. They are worth doing first, because a tool applied on top of badly set defaults just automates the wrong rule faster. If you are still deciding whether automation is worth it, the explanation of how dynamic pricing works is a better starting point than a feature list.

1. Match your minimum stay to how your market books

Look at the typical length of stay in your area by season, not across the whole year. A three night minimum that protects your July weekends will strangle your February midweek. Managers who run this check properly usually find their minimum is one night too long for at least one season, and the correction alone removes most gaps. The same logic applies to high and low season planning, where shoulder weeks need looser rules than peak.

2. Vary the rule by day of week

Weekend and weekday demand rarely share a length of stay pattern. Setting a longer weekend minimum protects your highest rate nights from being chopped up by two night stays, while a shorter weekday minimum keeps Monday to Thursday reachable. This is one of the levers that separates a calendar that fills from one that sits at 60 percent, and it shows up clearly once you start measuring occupancy properly.

3. Use check-in and check-out day rules deliberately

Fixed arrival days are a common self-inflicted cause of gaps. If operations genuinely require Friday changeovers, keep the rule, but add an exception for dates adjacent to an existing booking so a guest can slot in behind a departure. Both Airbnb and Vrbo support arrival and departure restrictions natively, and the trade-off between operational tidiness and lost nights is worth pricing out rather than assuming once you can forecast which arrival days your demand actually wants.

4. Talk to the guest already booked beside the gap

The cheapest way to fill a gap is to extend a stay that already exists. A guest arriving the day after a two night hole has zero acquisition cost, no new clean, and no channel commission on the extension if you handle it as a direct booking. Offer a modest discount on the extra nights, a local experience, or a late checkout. A template is included further down this article.

5. Make your cancellation terms clear enough to reduce late drops

A clear and visible vacation rental cancellation policy reduces the number of gaps you have to fix in the first place. Guests need two things stated plainly: the deadline and the refund or fee schedule. When a cancellation does happen, reach out with alternatives such as different dates or a larger unit before releasing the inventory, because a rescheduled booking beats a refunded one.

The five PriceLabs settings that prevent and fill orphan gaps

PriceLabs handles them at two stages: stopping them from forming, and pricing them to sell once they exist. The table below shows which setting to reach for and when. All five live under Customizations, and they interact, so the order you set them in matters more than most managers expect. The full release notes covering gap prevention features give the background on the newer options.

Minimum stay restrictions and the MinStay Recommendation Engine

Start here, because every other setting reacts to this one. If your market wants seven night stays and you accept a four night booking, the remaining three nights may never sell. The MinStay Recommendation Engine analyses how bookings are actually made in your market and suggests restrictions you can accept or edit as a starting point, which is faster than guessing and easier to defend to owners than a number you picked yourself. Pair it with the base price logic that sits underneath it so rate and stay rules pull in the same direction.

Minimum stay for orphan gaps and orphan pricing

This is the setting that makes existing gaps bookable. Set the orphan gap minimum stay to Length of Stay so the requirement automatically matches the size of the gap: a two night hole becomes a two night minimum, a one night hole becomes one night. Cascading the values covers every gap size instead of only the one you thought of. If you are comfortable with stays up to seven nights, enter one to your maximum restriction so the rule applies across the range. The same orphan day logic is used in small hotel and aparthotel setups.

You then decide what those nights are worth. PriceLabs applies a 20 percent discount to gaps of two nights or less by default, and you can replace that with your own percentage or a fixed rate. Percentages usually age better than fixed amounts because they move with your underlying pricing strategy instead of drifting out of date. Note that if an orphan night is also a last-minute date, the larger of the two discounts applies rather than both.

Adjacent day bookings and adjacent pricing

Where orphan rules fill gaps, adjacent day rules stop them forming. The setting applies separate stay requirements and rates to the nights directly before and after an existing reservation. The practical version documented in the PriceLabs guide to preventing gap creation works like this: if your default is a three night minimum, set the first night after a booking to three nights, then set the second night after to seven so a new reservation starting there has to be substantial rather than gap-creating. To rule out one night gaps entirely, use a much higher figure such as 99.

Extending that seven or 99 night rule to within three nights after an unavailable night closes off two night gaps as well. You will still get gaps, but they land at three nights or longer, which are far easier to sell than a stray Wednesday. One caveat worth knowing: the option to raise minimum stays this way is enabled on request, so contact support before you plan around it. Managers running larger portfolios often combine this with owner-specific pricing rules so the approach can vary by unit.

Minimum stay for far-out bookings

This one protects dates you have not reached yet. You set a lead time, commonly 90 days, and require longer stays for anything booked before it. The reasoning is straightforward: a two night booking taken eight months out locks up a date you could have sold as part of a week, and you gain nothing by accepting it early. Pair it with the mirror-image rule for close-in dates, covered in the last-minute pricing guide, where the minimum should loosen rather than tighten.

Smart check-in and check-out

This is the newest of the five and the one most orphan gap advice still misses. Two options sit inside it. Block Check-In/Check-Outs That Leave Orphan Gaps stops guests from arriving or departing on dates that would strand a night: if a checkout on the 14th would leave the 15th alone, guests are pushed to check out on the 15th instead. Allow Check-In/Check-Outs on Adjacent Nights does the reverse, overriding your fixed changeover days so a guest can slot in immediately after a departure. Both sit above your defaults in the hierarchy of minimum stay restrictions.

The constraint is compatibility. Smart check-in and check-out only works if your PMS or channel supports arrival and departure restrictions, and it is enabled by request through support. Airbnb, Vrbo, Booking.com, Guesty, Hostaway, OwnerRez, Track, and Mews are among those supported, with the full list in the PriceLabs check-in and check-out documentation. If your system only handles check-in restrictions, set the check-out side directly in the PMS.

One rule governs how these interact: orphan gap minimum stays take precedence over adjacent day minimum stays when the two conflict. That single fact explains most of the confusing calendar behaviour managers report, and the complete customization hierarchy is worth reading once before you configure anything complicated.

When should you accept an orphan gap instead of filling it?

Not every one deserves a discount. Filling one costs you a clean, a changeover, and sometimes the option value of a longer booking, and there are four situations where holding the line pays better. The first is a genuinely high-demand window. If the dates either side are selling at peak rates and your booking pace is ahead of last year, a two night hole in August will often close at full price without help, and discounting it early gives away margin you did not need to spend. Checking how each channel is actually performing tells you whether the pace supports waiting.

The second is maintenance. A single night between bookings is the cheapest slot you will ever get for a deep clean, a repair, or an inspection, and blocking it deliberately costs less than scheduling around a full calendar later. The third is a gap that would create a same-day turnaround your team cannot service. If filling Wednesday means a checkout and check-in on the same morning in two units, the operational risk usually outweighs one night of revenue, a judgement the vacation rental revenue management guide treats as a portfolio decision rather than a listing one.

The fourth is far-out dates. A stray night 200 days away has plenty of time to fill on its own, and discounting it now means you have permanently given up the chance of selling it at a better rate as part of a longer stay. Reserve gap discounts for the near term, where the date is genuinely at risk of expiring unsold. This is the same discipline behind resisting the urge to override automated rates.

Template: asking a guest to extend into the gap

Send this to a guest whose stay sits directly beside the gap, ideally a week or two before arrival rather than after they have checked in. Keep the ask small and make the benefit concrete, since a vague offer to extend rarely converts. Adapt the tone to your market and guest profile.

Hi [First name],

Thanks for booking [Property name] for your stay in [Destination]. We are looking forward to hosting you.

You are with us from [date] to [date]. If you would like to stay through [date], we can offer [benefit one], [benefit two], and [benefit three].

Let me know if that is of interest and I will get it added to your reservation.

Best,

[Your name], [Property name]

How to tell whether your gap strategy is working

Occupancy alone will not show you the answer, because filling gaps at a discount can raise occupancy while lowering revenue. Track three things together. The first is the count of unbookable nights per property per month, which is the number your settings directly control. The second is RevPAR across the whole period rather than the ADR on the gap nights themselves, since a filled gap at 20 percent off should still lift RevPAR if it did not cannibalise a longer stay.

The third is length of stay distribution. If your average stay is shrinking after you loosen minimums, the rules are letting in bookings that create more gaps than they close, and you should tighten the far-out setting first. Portfolio Analytics reports length of stay by stay date and booking window trends across your portfolio, which is where this pattern becomes visible before it shows up in the monthly numbers. Give any change a full booking cycle before you judge it.

If your gaps cluster in one season rather than across the year, the problem is usually seasonal rather than structural, and date-specific overrides will fix it faster than reworking your defaults. Event weeks and holidays behave differently enough that a blanket rule change tends to create new problems elsewhere on the calendar.

Frequently asked questions

How do orphan gaps work in PriceLabs?

Orphan gaps form between two bookings on your calendar. If one reservation runs Monday to Thursday and the next starts Saturday, Thursday and Friday sit as a two night gap that only sells if your minimum stay is two nights or fewer. Setting the orphan gap minimum stay to Length of Stay between one and two nights adjusts the requirement automatically for that window and makes the gap bookable.

Can I set a decreasing minimum stay across a four night gap?

No. PriceLabs can lower the minimum stay to match the length of the gap, so a four night gap can carry a four night minimum, but it cannot step down night by night across the same gap. Orphan gaps only appear when your default minimum stay is longer than one night, so if your default is two nights, a single open Wednesday gets an orphan rule that drops it to one.

My minimum is four nights midweek and two at the weekend. Can a guest book four nights from Sunday?

Yes. The default weekend is Friday and Saturday, so a Sunday arrival falls under the weekday rule and a four night stay clears it. If you want Sunday to behave differently, adjust it explicitly rather than relying on the weekend definition.

Does filling orphan gaps hurt my average daily rate?

It lowers ADR on those specific nights and usually raises revenue overall, which is why RevPAR is the metric to watch. A 20 percent discount on two nights that would otherwise have earned nothing is a gain, provided the discount did not stop a longer booking from landing on the same dates.

How often should I review my orphan gap settings?

Quarterly is enough for most portfolios, with an extra check at each season change and before any local event window. Markets shift on shorter cycles than they used to, and a minimum stay that was correct last summer often is not correct this one.

Set your gap rules once and let them run

Orphan gaps are a settings problem, not a demand problem, which means they respond to a couple of hours of configuration far better than to repeated manual discounting. Start with your minimum stays, add orphan gap rules to catch what slips through, then use adjacent day and check-in rules to stop the pattern repeating. Start a 30-day free trial with no credit card required and set the rules against your own calendar.

Orphan gaps often show up right around high-demand event windows — see our full guide to event pricing for Airbnb.

For the broader mechanics behind how any of this pricing actually gets decided, see our complete guide to dynamic pricing for short-term rentals.