Minimum Nights & Blocked Dates: Stop One-Night Bookings Fragmenting a Long Weekend

A beachside chalet with four units. Malaysia Day long weekend — Saturday, Sunday and Monday are all off. The owner is ready to sell three nights in one go. At 11pm someone books a single Saturday night, RM180. The next morning a family asks for all three nights, RM540. Saturday is gone in that unit, so the family is turned away. What is left is Sunday and Monday, and nobody wants the tail end of a holiday. One RM180 booking ate an RM540 one.

A two-unit village homestay during the school holidays. The owner has promised Unit B to her own family that weekend. She means to block it out, but never gets around to it — an online booking lands at midnight. Now she has to call the guest, apologise, and refund.

A six-room guesthouse in town. The cheapest room gets booked one night at a time, all month. Every departure means cleaning, fresh linen and a key handover. Six separate nights is far more work than one guest staying six nights — for roughly the same money.

Why this keeps happening

First: scattered nights are not worth the same as consecutive ones. In peak season demand arrives in blocks — three nights, four nights, a full school-holiday week. Sell one night in the middle of a block and the block splits in two. Two two-night fragments are much harder to sell than one four-night run, because people taking a proper holiday will not move rooms halfway through it.

Second: an open booking form accepts anything. With no rule in place, the form will take one night on any date, including dates the owner had quietly reserved for family or for maintenance. The form knows nothing the owner has not told it.

Third: the cost of a booking does not scale with its length. Cleaning, linen, key handover, answering the guest's questions — that work happens once per booking, not once per night. Six one-night bookings means six rounds of it for the same revenue as one six-night stay.

Fourth, and most often missed: the check-out day gets counted wrong when owners block dates. A guest arriving on the 12th and leaving on the 15th occupies the nights of the 12th, 13th and 14th. The night of the 15th was never sold to anyone. Plenty of owners block "the 12th to the 15th" in their head and lose a sellable night every single time.

What owners try instead

The most common one: putting the rule in a Facebook caption or an Instagram bio — "minimum 2 nights during the holidays". The problem is that the caption has no connection to the booking form. Guests who go straight to the booking link never see it, and one-night bookings keep arriving. The owner ends up being the bad guy, turning people away after they have paid.

Second: closing online bookings entirely during peak season and handling everything over WhatsApp so each request can be screened. It does give control, but it chains the owner to a phone during the busiest week of the year, and the booking that arrives at 2am simply disappears.

Third: accept now, sort it out later — hoping the one-night guest can be talked into a different unit or different dates. Sometimes that works. Usually it does not, and the owner absorbs the cost of the broken block.

The right way: minimum nights per room type, plus blocked dates

In TempahKu, minimum nights is a setting on each room type, not one setting for the whole business. Open Settings → Services and every unit has a minimum-nights field next to its price and unit count. It defaults to 1 night, and 1 is also the lowest value that can be saved — so there is no way to accidentally store 0 and make the room unbookable.

Because it lives on the room type, your family chalet can require 2 nights while the budget room stays at 1. You are not forced to pick one rule for everything.

When you set it above 1, guests see the rule on the booking page — "min 2 nights" appears beside the unit name, before they pick any dates. If they still try a range that is too short, the form refuses with a direct message: "Minimum 2 night(s) for this option." The condition sits at the point of decision, not in a caption that may never be read.

The same rule binds you too. When you enter a booking yourself from the dashboard, the system runs the identical validator — you cannot record a range a guest would have been refused. There is one deliberate exception: you are allowed to record a stay that has already started, because sometimes the guest really is in the room and you are just catching up on the paperwork.

For dates you simply will not sell — a family event, repainting, or your own break — use blocked dates. Two things matter about how they are counted:

First, blocked dates are counted by night, and the check-out day is not a night. If you block the 15th, a booking arriving on the 12th and leaving on the 15th still goes through, because it only uses the nights of the 12th, 13th and 14th. What gets stopped is any booking that actually sleeps there on the 15th. That means you do not over-block by a night, and a guest checking out on the morning of your blocked date does not have to be turned away.

Second, blocked dates apply to the whole business, not to one unit. If you only want to hold a single unit back for family, blocked dates are the wrong tool — deactivate that unit temporarily, or record a booking in your own name instead. Blocking a date closes every unit for that night.

One more helpful detail: the booking page only ever receives upcoming blocked dates. Last year's closures are not dragged onto the guest-facing page.

What these settings do NOT do

This is the part worth understanding before peak season, so nothing surprises you.

Minimum nights does not change by date. It is a fixed value on the room type. If you set 3 nights for the school-holiday week, it stays at 3 until you change it back — including on an ordinary Tuesday in February when a guest would happily have taken one night. Put a reminder in your calendar to reset it once the season ends. TempahKu will not do it for you, and we would rather you did not assume it will.

There is no automatic peak-season pricing. Each unit has one nightly price, and it does not rise on its own over a long weekend. If you want a holiday rate, you change the price yourself and lower it again afterwards.

One stay booking is one unit. A guest who wants two chalets makes two bookings. That is deliberate — if a single booking could hold two units, only one would actually be reserved, and the second would still be sellable to someone else while the guest believed they had both.

When it helps most

Long weekends and public holidays. This is the clearest case: three consecutive days, high demand, and one mid-block single night capable of wrecking the whole run. A 2 or 3-night minimum that week turns fragmented bookings into full ones.

School holidays. Families are looking for several nights anyway, so a minimum rarely blocks a real booking — it mostly filters out the early single-night reservations that would otherwise lock up your best dates.

Units with heavy turnaround work. If a unit takes a long time to reset, a 2-night minimum cuts how often that work happens without cutting revenue.

And when it does not help: quiet months, or budget rooms near a hospital, station or airport that genuinely live on one-night guests. There, a minimum just refuses money that wants to come in. It is a seasonal rule, not a permanent one.

In closing

Peak season is not a demand problem — the demand is there. The problem is the shape that demand takes when the booking form accepts anything. One single-night booking on the wrong night can block three others from ever being sold, and owners usually only notice after they have turned away something bigger.

Two settings solve most of it: a minimum stay on the right room types, and blocked dates for the nights you are not selling. Both are enforced on the booking form itself rather than in a caption, and both bind you exactly as they bind your guests. The one thing left to you is remembering to change them back when the season ends.