Picture a guest on your houseboat or cabin site on a Tuesday night. They want Friday and Saturday — two nights. Your minimum stay on a weekend is three nights. Your booking engine checks the rule, finds the request invalid, and returns the same message almost every engine returns: "No availability for your selected dates."

That guest had a credit card out. They were on your site, not an OTA. And in one screen, your engine told them — falsely — that you were full.

Here's the uncomfortable part: if your current engine is leaking this way, you can't see it. There's no line in any report called "guests we turned away for asking the wrong way." The booking just doesn't happen, and you assume demand was soft. It wasn't.

What the leak actually looks like

What your engine should have said is: "That weekend needs a three-night minimum. Here are the nearest dates that work: Thu–Sun, or the following Fri–Mon." Same boat. Same rules. Completely different outcome.

The guest doesn't know your min-stay rule exists. They read "no availability" as "sold out" and do the obvious thing: they open a new tab, search the same dates on Booking.com or Airbnb, and book whatever comes up — which might be you, now wearing a 15–18% commission on a booking you'd already won on your own website.

That's the leak. It's silent, it's uncounted, and it's almost certainly happening on your site right now.

Why you've never seen it in your numbers

This is what makes the min-stay leak so expensive: it hides in the one place you'd never look — the gap between traffic and bookings you've already written off as "just browsers."

Your analytics show the session. They show the guest reached the booking step. They don't flag why the guest left, because from the engine's point of view nothing went wrong — it correctly applied your rule and correctly returned a result. The result just happened to be a lost sale.

So when you review the month, you see a booking engine that "converted poorly" and you blame the site, the photos, the price. The real culprit is a rule doing exactly what it was told, with no fallback when a guest asks one night short.

The maths, kept conservative

Let's not inflate this. Say you run a 20-room property with weekend and peak min-stays — typical for a Murray River houseboat operator, a Hunter Valley lodge, or a Mornington Peninsula villa.

Assume your branded site gets enough direct traffic that just two guests a week hit a min-stay dead end and bounce. That's not a stretch; near-miss date searches are extremely common around weekends and school holidays.

  • 2 lost bookings/week × 52 weeks = ~104 bookings/year turned away by two words.
  • At an average $600 booking value, that's ~$62,400 in revenue routed elsewhere.
  • The slice that rebooks you via an OTA still costs you 15–18% commission — roughly $90–$108 per booking straight off the top.

Even if you halve every assumption — one guest a week, half rebook through an OTA — you're still looking at tens of thousands in commission bleed and lost direct margin a year. From two words.

The point isn't the exact figure. The point is that the number is non-zero, recurring, and invisible, which is the worst combination a leak can have.

The fix: surface the 3 nearest bookable dates

The fix is not "remove your min-stay rules." Those rules protect your turnover costs and your peak pricing — keep them. The fix is changing what happens when a guest misses them.

Accommador's booking engine treats a near-miss as the start of a conversation, not the end of one. Instead of "no availability," it does three things in the same screen:

  • Explains the rule plainly — "this period has a 3-night minimum" — so the guest understands they weren't rejected.
  • Surfaces the 3 nearest bookable date ranges that satisfy the rule, ranked by how close they are to what the guest asked for.
  • Keeps them on your site, ready to book, instead of sending them to a new tab and an OTA search bar.

A guest who came for Fri–Sat and is offered Thu–Sun very often takes it. They wanted your property on that weekend — they're flexible on the edges far more than a dead-end message gives them credit for. You only find that out if your engine asks.

This is the single biggest reason operators move their booking engine to Accommador. The nearest-bookable-dates engine isn't a paid add-on or a higher tier — it's part of the one platform, alongside the 100+ channel manager, payments and Xero reconciliation.

How to find your own leak in under a day

You don't have to take the maths on faith. The fastest way to know whether "no availability" is costing you is to watch your own engine do it. Open your live booking page, search realistic min-stay and fixed-arrival dates — a two-night request against a three-night weekend rule — and see what comes back. If it's a dead end, that's the exact screen your guests see before they open a new tab.

If two words are quietly routing your guests to an OTA, you'll see it in seconds — and you'll know precisely what it's worth to fix.

What it costs to plug it

The reason the nearest-bookable-dates engine is built into Accommador is simple: a min-stay rule should protect your margin, not silently donate guests to an OTA. The closed-loop direct-sales engine — marketing, booking engine, 100+ channel distribution, payments and Xero reconciliation in one place — starts at $500 AUD/mo per location, everything included. Monthly billing, cancel anytime. Start free.