Yes, you can set stay ranges like “1–6 months” in WPRentals, but you enter them as nights. For example, you’d enter 30 as the minimum and 180 as the maximum nights for a 1–6 month range. The booking form then blocks shorter or longer stays while still applying your weekly and monthly discounts on top.
How does WPRentals handle minimum and maximum stay lengths overall?
You control multi-week or multi-month limits by entering their night values.
Each listing in WPRentals has fields for minimum and maximum nights, so you set stay length per property. For a two-week minimum you’d set 14 nights, while a six-month maximum might be about 180 nights as a starting point. The theme reads these numbers and checks every booking request against them. Guests never see the raw values, only whether their dates are allowed.
The booking form enforces these rules in real time when guests pick dates. If a stay is too short or too long, the form shows a message and blocks the request. Owners don’t have to review odd cases like 1 night for a “30-night minimum” apartment, because those never reach the inbox. The system filters them out before anyone wastes time.
Length-of-stay discounts in WPRentals work together with min and max rules, not instead of them. You can define weekly and monthly discounts so that once a stay passes 7 or 30 nights, the price per night drops. The engine checks if the stay respects min and max nights, then checks which discounts apply. This lets you support extended stays such as 45 or 90 nights with clear pricing and no manual math.
Can I configure weekly or monthly minimum stays like 1–6 months in WPRentals?
You can enforce multi-month minimums by setting high minimum nights per property.
Owners who want only long bookings can set the minimum nights to values like 30, 60, or 90. In WPRentals you do this in the listing pricing settings by typing the number of nights that should be the shortest stay. For example, a corporate rental might allow only 60+ night bookings, so the owner enters 60 as the minimum. Any search or booking attempt below that fails validation.
WPRentals also supports very long stays while still capping them. If you want at most 6 months, you could set a max of 180 nights and let the theme stop anything longer. The booking form then allows a 32-night stay or a 120-night stay but blocks 200 nights. Each accepted stay is still just one reservation with one total price, even if it covers several calendar months.
Monthly discounts kick in automatically once the stay passes your chosen threshold. In WPRentals you can define a monthly discount as a percentage, like 20 percent off after 30 nights, or as a fixed amount per month. The engine combines base nightly price, seasonal or weekend changes, and any long-stay discount into one total. At first this looks complex. It ends up pretty simple to use day to day.
| Stay goal | Suggested min nights value | Typical use case |
|---|---|---|
| About 1 month stays | 30 nights minimum | Relocation or temporary housing |
| 1 to 3 month stays | 30 min 90 max | Intern or project-based work |
| 1 to 6 month stays | 30 min 180 max | Mid-term furnished rentals |
| At least 2 weeks | 14 nights minimum | Holiday villas or seasonal homes |
| Cap very long stays | 180 or 365 max | Avoid de facto long leases |
This table shows how simple number choices control stay ranges in WPRentals. By tuning minimum and maximum nights, you match your business model without touching any code. You also keep tighter control over how long guests can occupy each property.
How do seasonal rules change minimum stay lengths for specific months or periods?
Seasonal overrides let you require longer minimum stays only in busy periods.
The “custom price for period” option lets you pick any date range on a calendar and give it special rules. In WPRentals you can say, for example, that from December 20 to January 5 the minimum stay is 5 nights, while the rest of the year the minimum is 2 nights. You enter those dates, set a different minimum nights number for that block, and the theme enforces it only for that time.
Each period rule can have its own minimum stay, maximum stay, and custom prices. That means you might have summer with a 7-night minimum, winter with a 3-night minimum, and a low season with just 2 nights. WPRentals reads the guest’s check-in and check-out dates, sees which periods they touch, and checks the rules for those days. If the stay breaks the period minimum, the booking is blocked.
Changeover rules can also line up with these seasonal minimum stays on the same calendar. Owners can say, for one range of dates, “check-in only on Saturday” plus “minimum 7 nights,” which is common for weekly villas. The theme then only lets guests click those allowed days, and the length rule pushes them to pick enough nights. Here the trade-off is strict control in peak season but more work when planning exceptions.
Can I mix nightly, weekly, and monthly pricing when enforcing stay limits?
Mixed nightly, weekly, and monthly pricing all follow the same stay length rules.
Your base unit of price is always per night, but you can stack weekly and monthly discounts. In WPRentals these discounts never bypass the minimum and maximum nights that you set in the listing. The system first checks that the length is allowed, then checks if it qualifies for a weekly or monthly discount, and finally totals the price.
This setup even works if you host both nightly and hourly rentals on the same platform. The theme lets you run some listings in hourly mode and others in daily mode, each with its own duration rules. At first, that split sounds messy. In practice, long-stay settings all live in a clear dashboard where you set numbers and dates, not code.
FAQ
How do I set a “month” minimum if WPRentals uses nights?
You set a “month” minimum by entering the matching number of nights, like 30.
WPRentals uses nights as the unit for all stay rules, so weeks and months become longer night counts. A common pattern is 7 nights for a week and 30 nights for a month as a quick rule. You can adjust those values if your local market expects slightly different lengths.
Can different properties on the same site use different minimum and maximum stays?
Yes, every listing can have its own minimum and maximum nights on the same site.
In WPRentals, min and max stay fields are stored per property, not globally. One apartment might need a 3-night minimum with no maximum, while another must be at least 30 nights and capped at 180. Owners or admins just set these values in each listing pricing area, and the booking form respects them automatically.
What do guests see if their chosen dates break the stay rules?
Guests see an error message and can’t send the booking if rules are broken.
When a user picks check-in and check-out dates that don’t meet the minimum or exceed the maximum, the WPRentals form runs a quick check. It shows a short message explaining that the stay length isn’t allowed and stops the request. That sounds strict, but it avoids confusion for both guests and owners and keeps your calendar cleaner.
Can I safely cap very long bookings like over 6 months?
Yes, you can cap very long stays by entering a maximum number of nights per listing.
To prevent overly long bookings, you might set the maximum to 180 nights for about six months or 365 for one year. WPRentals then refuses any booking that tries to go past that limit, even if the calendar is free. This gives you a simple way to avoid bookings that drift into lease-like territory, without turning WPRentals into full property management software (PMS).
- Weeks or months are always entered as a number of nights in the settings.
- Each property can have its own minimum and maximum nights on the same site.
- Guests see an error message if their dates break stay length rules.
- Setting a clear maximum nights value safely caps very long bookings.
