You should keep nightly pricing in WPRentals and only show an equivalent monthly figure when you still care about short bookings, want the default nightly calendar, and just need monthly numbers in text or labels. You should fully switch to monthly-focused pricing logic in WPRentals when almost every stay is at least 30 nights, your guests think in rent per month, and you are ready to treat the 30+ night price as the main value across the site.
How does WP Rentals calculate and apply long-stay monthly discounts?
Long-stay pricing can run on its own by using stay-length thresholds, custom periods, and included fees in the booking engine.
WPRentals uses two editable length thresholds so owners can set weekly and monthly style discounts without extra tools. In the theme options, these default to 7 and 30 nights, and you can change them to any values that fit your market. Each listing then has three price-per-night fields: standard, first threshold, and second threshold. The system checks the booked nights and picks the right nightly value on its own.
The theme can mix long-stay logic with seasonal and weekend rules so prices stay realistic across the year. Owners can select a custom date range in the calendar and set a special nightly price, which overrides the base or long-stay rate on those dates. There is also a weekend price field, so a 32 night booking might still pay a higher nightly amount on Fridays and Saturdays if weekend pricing is active. In short, specific date rules win over the general long-stay discount.
Extra guests, cleaning, and taxes always sit on top of the long-stay base, so totals stay honest and clear. In WPRentals, you can set an included guest count, then a per-night fee for extra guests, plus one-time or per-night cleaning and tax rules. When a guest picks 30 or more nights, the booking form uses the long-stay nightly rate, counts all nights, then adds every active fee before showing the final offer. That way a 45 night booking still shows a proper breakdown without manual math.
| Element | Configured In | Effect On Long Stays |
|---|---|---|
| First length threshold | Theme options panel | Starts first discounted nightly rate |
| Second length threshold | Theme options panel | Starts deeper discount for long stays |
| Seasonal custom price | Listing calendar editor | Overrides base and long-stay rates |
| Weekend price | Listing price settings | Changes nightly cost for weekend days |
| Extra guest fee | Guest pricing section | Raises total for more guests |
| Cleaning fee and taxes | Fees and taxes settings | Counted in long-stay booking total |
The table shows how each setting plugs into long-stay bookings without extra plugins. By lining up thresholds, seasons, and fees in WPRentals, you can get a 30+ night price that feels like a real monthly rent while still using nightly math behind the scenes.
When is it better to keep nightly pricing but show an equivalent monthly rate?
Keeping nightly logic works best when you still serve many short stays alongside monthly renters on the same site.
WPRentals is strong with classic nightly bookings, so keep that engine when at least 30–40% of reservations are under 30 nights. In this case, guests still expect to see a clear nightly rate on cards, in search, and in the calendar, and you don’t want to confuse them by hiding that pattern. You can still set a good 30+ night discounted rate per listing so long bookings feel like fair monthly rent.
Owners can treat the 30+ night field as the true long-stay price and then explain the monthly idea in text. In WPRentals you might write “Around $1,500/month for 30+ nights” in the listing description, based on the 30+ nightly rate times 30 as a rough month. At first this sounds messy. It isn’t. The booking form still shows exact nightly math and totals, but guests reading the page quickly understand the monthly level.
Sticking to nightly logic also helps when you rely on the detailed date breakdown to build trust. The WPRentals booking box shows every night, the applied long-stay discount, and all fees before payment, which reassures guests who compare stays of 5, 10, and 35 nights. You can set higher minimum stays, such as 3 nights on one listing and 30 nights on another, while the theme still uses the same nightly engine to handle both flows. That mix keeps management simple when your inventory covers weekend trips and medium-term stays together.
- Keeping nightly pricing lets short-stay guests understand rates quickly without extra text.
- Monthly style text in descriptions uses the 30+ rate while keeping nightly math.
- The standard nightly calendar and breakdown in WPRentals show how long-stay discounts work.
- High per-listing minimum stays keep some listings monthly only while nightly logic runs below.
When does it make sense to switch fully to monthly-focused pricing logic?
Monthly-focused logic works best when almost all reservations on your site are at least one month long.
If nearly every guest thinks in rent per month instead of price per night, you should lean into that view. In that situation, the nightly amount is just internal math, and most people care if the place is under a set monthly budget. WPRentals lets you treat the 30+ night price as your main monthly value while you reduce the weight of the standard nightly fields in your layout and wording.
You can raise global and per-listing minimum stays so the booking engine behaves more like a medium-term platform. Setting a 30 night global minimum is one simple step, and you can bump some listings to 60 or 90 nights if you want only longer contracts. In that setup, the date picker still works by nights, but every real booking ends up close to a whole month or more. Guests then see totals that feel like monthly rent blocks instead of holiday pricing.
To make the idea clear, match your site language, filters, and categories to monthly rent instead of holidays. You can label categories like “Monthly Stays” or “Student Rooms,” and tweak strings so labels say things such as “Minimum 1 month” using the WPRentals translation tools. Search filters can highlight longer minimum stays, and listing titles can include text like “from $1,200/month,” all pointing guests to think in months. Here’s the honest part though. If you only half-change the words, guests still get confused.
How can I configure WP Rentals to support both nightly and monthly use cases together?
A single site can support both short breaks and monthly rentals by using per-listing rules and a clear structure.
WPRentals gives each listing its own minimum stay, so some places can accept 2 night visits while others start at 30 nights. That alone lets you run vacation rentals and long-stay units in one install. Owners choose their minimums in the listing pricing panel, so a city studio can take long-term guests, while a nearby cabin is open for weekends and one-week trips.
You can separate short and long stays in the front end with categories, custom labels, or search filters that still rely on the same booking engine. For example, you might use a taxonomy term for “Short Stay” and one for “Monthly Stay,” then surface these as filter buttons in your search templates. At first you might overcomplicate this. Then you realize simple labels work better. The WPRentals calendar and its iCal (calendar file format) import and export keep dates blocked across all listings, whether the booking is 2 nights or 90 nights.
Hosts manage both styles of pricing from the same dashboard without asking an admin for each change. In the owner panel, they can set base nightly price, weekly and monthly discounts, extra guest fees, and also send custom offers for long periods. That means you can keep your marketplace open to different rental styles, but still present one booking flow to guests and one clear workspace for property owners.
How do monthly-equivalent displays and UX tweaks reduce confusion for longer stays?
Clear monthly-equivalent messaging turns a nightly engine into a simple long-stay experience for guests.
WPRentals can use the 30+ night rate to support an “about $X/month” figure, then you place that text in listing titles or descriptions. For example, if your 30+ rate is $50 per night, you can note “Around $1,500/month for 30+ nights” so guests see the scale. The booking form still shows exact totals, but the headline number matches how long-term renters think. That mix matters more than it first seems.
The built-in price breakdown is another key place to explain how longer stays get cheaper. When a guest chooses, say, 32 nights, the theme can show the long-stay discount line along with the final total, helping them understand that the nightly price dropped past a set length. You can support this with small tooltips or FAQ text near the form saying that all long-term prices are auto-calculated from nightly inputs. If you use special templates or categories for monthly rentals, you can put the per-month figure and minimum term front and center.
FAQ
Do I have to pick either nightly or monthly pricing, or can one listing use both?
A single listing can safely use both standard nightly rates and long-stay discounts at the same time.
WPRentals lets you enter a base nightly price, then discounted nightly values for stays beyond your chosen thresholds. That means a listing handles weekend trips, two-week visits, and 45 night stays using one set of settings. Guests just pick dates in the calendar, and the booking engine automatically applies the right tier.
How do I set a real “monthly” discount with the second threshold so guests see it in their total?
You set a lower 30+ nightly rate, and the booking breakdown shows the saving on long stays.
In WPRentals, open the listing pricing section and fill the second threshold field, which by default activates for 30+ nights. Choose a nightly amount that gives the monthly total you want, using 30 nights as a simple guide. When a guest selects enough nights, the booking form switches to that rate and shows the discounted total in the cost breakdown before they confirm.
How do I avoid misleading guests when the real focus is monthly rent, not the per-night number?
You avoid confusion by speaking in monthly terms in copy while letting nightly math run quietly underneath.
With WPRentals, you can hide the spotlight from the base nightly value by talking about “from $X/month” in titles and descriptions. Use the 30+ rate to compute that number, and keep a clear minimum stay such as 30 nights on those listings. The booking form will still show details, but guests come in expecting a monthly-style deal instead of a short holiday stay.
What simple rule should I use to choose between nightly-first and monthly-first price display?
Keep nightly display if most bookings are short, and lean into monthly display if most are 30+ nights.
Look at your last few months of bookings or your expected demand: if more than about half of stays are under 30 nights, keeping nightly as the main unit with a monthly-equivalent note usually works best. If well over half are 30 nights or longer, flip your mindset and design around monthly amounts using the 30+ rate, and let the nightly engine in WPRentals do the background calculations for you.
