Setting a minimum length of stay: how many nights minimum for your B&B?

A guest books one night on a busy Saturday. Sounds great — until you realise that single night leaves a hole: the Friday before and the Sunday after now won't sell, because nobody wants to book around one occupied night. You've earned one night of revenue but ruined three nights of your weekend. That's exactly the problem a minimum length of stay solves.

A minimum length of stay (or min-stay) is a rule that says: on this date I only accept bookings of at least X nights. It's one of the most underrated settings in your channel manager — used wrongly it scares guests away, but used well it protects both your margin and your calendar.

Why a min-stay is more than being "difficult"

At first glance a minimum number of nights looks like a barrier you impose on yourself. Why turn a booking away? Three reasons.

1. Fixed cost per booking. Every booking costs you the same fixed work whether the guest stays one night or five: cleaning, laundry, check-in, admin. A one-night booking of €100 with €30 of fixed cost nets you €70. Five one-night bookings cost you that work five times over. Follow that logic through in Length-of-stay discounts for your B&B — it shows in black and white why longer stays are often more profitable.

2. Orphan nights. A lone booking in the middle of a free weekend cuts your calendar into fragments. The "orphan nights" beside it often stay empty because nobody books around an occupied night. A min-stay keeps your availability in larger, sellable blocks.

3. Peak demand. On a festival weekend, over the Christmas period or a long weekend, demand is high enough that you can comfortably ask for a two- or three-night minimum. You fill with longer, more valuable bookings instead of giving your best nights away to single overnights.

When a min-stay backfires

This is where it often goes wrong. A min-stay is a double-edged sword: every night you fence off is a night that can't be booked.

• Too strict in low season. On a quiet Tuesday in November, one booked night beats an empty room. A three-night min-stay left on all year loses you money precisely in the quiet periods.
• The "gap between two bookings". Say you have two bookings with exactly two free nights between them. If your min-stay is three, nobody can fill that gap — you're bricking up your own calendar. Good systems solve this with a gap-fill rule that automatically lowers the min-stay for exactly those gaps.
• Confused with arrival restrictions. Some hosts mix up a min-stay with a "no arrivals on Sunday" rule. Those are different levers; use them deliberately.

The rule of thumb: a min-stay is a seasonal, demand-driven instrument, not a permanent wall. Higher in high season and on peak dates, lower or off in low season.

Concretely: which thresholds suit your type of property?

There's no universally correct number, but these are realistic starting points:

• City B&B, lots of short trips: usually 1 night, with 2 nights on weekends and peak dates.
• Rural B&B or guest room: 1 night midweek, 2 nights on weekends.
• Seaside or countryside holiday home: 2 to 3 nights in season, often 7 nights (Saturday-to-Saturday) in the summer holidays. More on that in Channel manager for your seaside holiday home.

Start modestly, look at your own data — where's your sweet spot today? — and adjust.

How do you set it on Booking.com and Airbnb?

On Booking.com you find the minimum length of stay in the extranet under Rates & Availability → Calendar: select a period and set the minimum number of nights. You can vary it per room type and per rate.

On Airbnb it sits under Availability → Trip length, with separate settings for default, weekends and specific date ranges.

And there's the catch: you have to do it on each channel separately. Set two nights minimum on Booking.com but forget Airbnb, and a single-night booking still slips in through the channel you skipped — right on the date you wanted to protect. Keeping two, three or four extranets in sync by hand is error-prone and time-consuming.

How BedFlow PMS handles this for you

In BedFlow PMS you set the minimum length of stay once in your central calendar — per period, per room type — and the system pushes that restriction to all your connected channels like Booking.com and Airbnb at once. Raise the min-stay for a busy festival weekend and it applies everywhere immediately, without hunting for the same date in every extranet.

An important detail: the same rule also governs your direct bookings through your commission-free booking widget. So a guest on your own site can never sneak in a single night on a date you'd reserved for longer stays. One setting, consistent everywhere — and your calendar stays in healthy, sellable blocks.

Want to be sure a stricter min-stay actually reaches your OTAs and doesn't just sit locally? That's precisely the kind of synchronisation a good channel manager exists for.

In closing

A minimum length of stay isn't a way to scare guests off — it's a way to allocate your scarce nights to the bookings that yield most and fragment your calendar least. Set it higher where demand is high, lower where you need to fill, and let gap-fill sort out the isolated gaps.

• Use a min-stay on peak dates and weekends, not as a permanent wall.
• Lower it or switch it off in low season so you don't lose nights.
• Make sure the rule applies identically on every channel — otherwise a single-night booking leaks in.

Want to see how to set this once and have it applied correctly everywhere? Check the pricing, read the documentation or try BedFlow PMS free for 30 days — no credit card required.