Yes, you can set different booking rules per property in WPRentals, including check-in and check-out days, stay limits, and lead time. Each listing has its own booking panel, so owners change rules without code. One apartment can use Saturday-only weekly arrivals, while another accepts flexible two-night stays. These per-property rules still work with seasonal prices, hourly mode, and long-stay discounts, so many hosts with very different needs can share one site.
How does WPRentals let hosts set different rules per property?
Each property can keep its own booking and stay rules inside the same WordPress site.
Every listing has a pricing and booking rules area the owner edits from their dashboard. In WPRentals, this panel controls base nightly rate, weekend rate, cleaning fee, and extra guest fee, all tied to that one property. The theme saves rules per listing, so changing prices for one cabin won’t change a nearby villa.
The same panel also handles minimum and maximum nights for that exact property. WPRentals checks those values when guests use the booking form and blocks dates that break them. One place can need at least 2 nights and at most 30, while another allows 1-night stays and blocks anything over 7.
Owners also pick if a listing uses instant booking or request-to-book, again per property. In this setup, one host can run instant bookings with a security deposit, while another prefers to approve every request and use another service fee. At first it feels complex. It isn’t, because the theme keeps all choices inside that listing, so a marketplace with 50 owners can run 50 different rule sets without custom code.
- Each listing has its own pricing and booking rules panel with listing-only fields.
- Owners set base, weekend, and seasonal prices on the property itself.
- Per-listing minimum and maximum stay work through the property booking form.
- Instant booking, deposits, and fees are configured separately for each property.
Can I customize check-in and check-out days for each individual listing?
You can set different allowed check-in and check-out weekdays for every listing on your site.
Each property gets changeover settings so hosts pick which weekdays work for arrivals and departures. In WPRentals, these rules sit in that listing’s calendar and booking options, which keeps them separate from other properties. A host can set “check-in only on Saturday and check-out only on Saturday” for one house and leave another house flexible.
The theme also lets owners tie turnover rules to date ranges for certain seasons. For example, the owner can select 1 July to 31 August on the listing calendar and allow “check-in only on Saturdays” in that period. Outside August, the same listing can accept arrivals any day, all controlled from the visual calendar.
This setup works when some properties run strict weekly stays and others do short breaks. One chalet can run Saturday-to-Saturday all year, while a city studio nearby accepts weekday arrivals and short weekend stays. Because WPRentals keeps changeover rules per listing, marketplace admins don’t need to write code or keep several plugins just to support different host habits.
How are minimum and maximum stays managed for diverse host policies?
Each property can enforce its own minimum and maximum stay, with extra rules for special times.
The theme lets you define global default min and max nights, but each listing can override them using its own settings. In WPRentals, the listing edit screen has simple “Minimum nights” and “Maximum nights” fields that apply only to that property. One house can use a 2-night minimum and 21-night maximum, while another in the same city can need 5 nights minimum and 90 nights maximum.
Hosts often need tighter rules for holidays or high season, and the theme covers that with “custom price for period” settings. On one listing’s calendar, the owner marks a date range and assigns a special price and special minimum stay, such as “5 nights from December 20–27” or “7 nights in August”. The booking form blocks any request that breaks those rules, even if the normal minimum is lower.
Length-of-stay discounts like weekly or monthly deals can also work per listing. WPRentals lets owners set a percent or flat discount for 7+ nights and 30+ nights at property level, and those discounts still respect min and max nights. A guest who books 14 nights on a listing with a 3-night minimum and 30-night maximum can get the weekly discount. But a 2-night request on that same listing gets rejected before payment.
| Rule layer | Scope | Example use |
|---|---|---|
| Global defaults | Whole site | Base min 2 nights for all listings |
| Listing min max | Single property | Studio min 1 night house min 7 nights |
| Custom period rules | Property date range | Holiday min 5 nights August min 7 nights |
| Max stay caps | Single property | Cap stays at 30 or 90 nights |
| Stay discounts | Per listing | Weekly 10 percent monthly 20 percent |
The table shows how rules go from global defaults down to narrow date ranges on one listing. At first, the stack looks like it might clash. Instead, WPRentals reads the most specific period rule on those dates, while the property min and max keep broad limits. That way, one property runs as a strict 30-night rental and a second as a 3-night holiday spot, in the same install.
Can I control lead time and same-day bookings differently for each property?
Lead time, same-day booking, and buffer days can all use per-listing values.
Each property has its own “how many days in advance” rule. One owner can need bookings to be made at least 3 days before arrival, while another accepts next-day stays. WPRentals stores this as a number on the listing, and the booking form blocks any check-in that falls inside that buffer. Guests see the earliest allowed date in the calendar.
Hosts can also forbid same-day or next-day bookings for only some listings. The theme includes per-property settings for preparation days between stays, so a host can enforce 1 buffer day for a small flat and 2 buffer days for a large villa that needs more cleaning. Because all these values are per listing, a marketplace can run strict and flexible hosts together without rule conflicts.
How do per-property rules work with seasonal, weekend, and hourly pricing?
Seasonal, weekend, and hourly prices work on top of each property’s own booking rules to give the final rate.
Seasonal custom price periods are set on the property calendar, so each listing can keep its own high and low seasons. In WPRentals, an owner might flag June 1–September 1 as “high season” for one beach house with higher nightly prices, while an inland house uses a shorter peak such as only July. These periods stay per listing, not site-wide, so they match each host’s reality.
Weekend prices also live per listing using “Price per weekend night”. One property can charge 150 per night on weekdays and 200 on Friday and Saturday, while another keeps 100 every day. If you run hourly mode globally in your PMS (Property Management Software), the theme still lets owners define open hours, minimum hours per booking, and special hourly periods for each listing, such as “only 9:00–17:00 on weekdays”.
Length-of-stay discounts and seasonal overrides both apply when the guest picks dates or hours on a listing. The theme first calculates the base or seasonal price, then applies weekend or custom period values, then weekly or monthly discounts if rules allow it. Because everything runs at property level, you can keep very different setups on one site: an hourly meeting room with a 2-hour minimum, a weekend cabin with higher Friday and Saturday rates, and a monthly rental that gives a strong 30-night discount.
FAQ
Can many owners use different booking rules on one WPRentals marketplace?
Yes, each owner’s listings can use different booking, pricing, and stay rules on the same marketplace.
Owners manage their properties from the front-end dashboard, so they never touch each other’s settings. A city site with 100 hosts can support strict 7-night villas, flexible 2-night apartments, and hourly coworking spaces together. WPRentals keeps rules tied to the listing, which helps for multi-vendor setups.
If I change rules for one property, do other listings change too?
No, changing booking rules for one listing affects only that listing.
Each property stores its own min and max stay, changeover days, pricing, and lead-time numbers. When you edit those values in the dashboard, the theme updates the booking logic only for that property’s calendar and booking form. Other listings keep their rules until their owners change them. This sounds obvious, but it matters when you manage many units.
Can instant booking and request-to-book differ between properties?
Yes, some listings can use instant booking while others need manual approval before a stay is confirmed.
On each property you pick if guests can book and pay at once or must send a request first. WPRentals uses the same min stay, max stay, and calendar rules in both modes, but in request-to-book the host must approve before the dates lock. This mix lets careful hosts review guests, while others enjoy more automated bookings. It is a trade, more control for more clicks.
How can hosts preview or test their custom rules before going live?
Hosts can test rules by checking the property calendar and running trial searches on the public booking form.
After saving changes in the listing dashboard, owners can open the listing page and try different check-in and check-out dates to see how price and validation behave. WPRentals also shows min stay, blocked days, and changeover rules inside the calendar view, so owners can see if a high-season rule or buffer day works as planned before they push the listing hard. Some will still double-check often. That is normal.
