Cancellation and refund rules for multi‑month bookings in WPRentals are clear per‑listing policies that you write. Actual refunds stay manual and go through Stripe, PayPal, bank transfer, or WooCommerce. You can describe almost any long‑stay rule you need, including deposits and late cancellations close to arrival. In practice, the rules can be as flexible as many competing tools, and often more detailed, while you keep full control of every payout and refund step.
How do multi‑month bookings and long‑stay pricing work in this system?
The system can apply discounted pricing for long stays while still charging a set upfront deposit.
WPRentals lets guests pick long date ranges in the calendar, with no fixed cap on nights as long as dates stay open. Owners can set minimum nights, but a 45‑night or 120‑night stay works like a normal booking from the guest’s point of view. The quote box uses the dates to show one total that already includes cleaning, city fees, and extras.
Here, long‑stay pricing is simple because you enter normal nightly prices plus weekly and monthly discounts. Once a guest selects at least 7 nights, the weekly rate kicks in, and at 30 nights or more the monthly rate can apply instead. The math happens instantly in the booking form, so a 35‑night stay shows the discounted total without the guest asking for a custom offer.
WPRentals also lets the admin define a deposit rule, such as 30% of the total or a fixed amount like 500. If someone books three months and the total is large, the same rule still applies, so you don’t adjust it by hand. The remaining balance appears in both guest and owner dashboards and can be billed by a second invoice or handled offline if that fits your long‑term model.
| Feature | Where to set it | Effect on multi‑month stays |
|---|---|---|
| Weekly discount after 7 nights | Listing price settings | Lower rate applies to 7 plus night bookings |
| Monthly discount after 30 nights | Listing price settings | Monthly rate used for 30 plus night stays |
| Deposit percentage or fixed value | Global booking options | Same rule used even for long totals |
| Remaining balance tracking | Invoices and dashboards | Shows what is still due per booking |
| Cleaning and city fees setup | Per listing fee settings | Fees scale correctly for longer stays |
The table shows how most long‑stay behavior in WPRentals comes from normal listing and global price settings. You don’t need special long‑term tools, which keeps large multi‑month reservations predictable. But you still get room to tune discounts and deposits to match how you prefer to work.
How are cancellation rules defined for long or multi‑month reservations?
Each property can publish its own clear cancellation rules that guests see before confirming a booking.
WPRentals adds cancellation fields to every listing, so owners can write rules that match how they handle long stays. You can set how many days before arrival a guest can cancel and still get a refund and what refund percentage applies. These settings work the same for a 3‑night weekend or a 90‑day booking, so your long‑stay logic stays in one simple policy block.
In this theme, those rules appear on the listing and again during the booking flow, before guests send a request or pay a deposit. That keeps expectations clear, especially if a multi‑month booking uses stricter numbers, like “no refund inside 30 days” or “50% kept on early cancellation.” Guests must agree to the terms to move forward, which helps avoid some debates later.
When a host or admin cancels or updates a long reservation in WPRentals, the booking status change triggers branded emails to everyone involved. The text is fully editable, so you can restate long‑stay cancellation rules in plain language inside those notices. Different listings on the same site can each use their own long‑stay wording, so a city studio can use lighter rules while a seasonal villa keeps a firm cut‑off for refunds.
How are refunds, deposits, and security deposits handled for cancellations?
Refunds and deposit returns are done by the site owner, which gives full control over each payout.
WPRentals is built so that all payments land in the admin’s accounts, not in separate owner wallets. That makes money control simple, even if some people dislike doing refunds by hand. When a guest pays for a multi‑month booking, the funds arrive through Stripe, PayPal, bank transfer, or WooCommerce gateways you connect. If the booking needs to be canceled or changed, you decide how much to send back based on the written policy, then process that refund in the same payment tool.
This theme separates security deposits as their own line item in the price breakdown, which helps with long stays where a higher damage deposit, like 300 or 500, is common. That amount is collected with the rest of the payment according to your deposit rule, and the invoice clearly marks it as “security deposit” so no one confuses it with rent. After the stay, you manually decide to return all, some, or none of that deposit, again using your payment provider’s refund controls.
In WPRentals, there is no automatic refund engine that tries to guess amounts from your policy text. At first that sounds like a missing feature. It isn’t. You stay free to look at special cases such as early move‑out, minor damage, or local rules before sending money back. The booking record keeps the full history of what was charged, which policy applies, and what you chose to refund, so you have a clear paper trail for each long‑term reservation.
How does flexibility of cancellation terms compare with other booking options?
The policy fields are open so you can copy almost any cancellation pattern used elsewhere.
In WPRentals, cancellation rules aren’t stuck in a few fixed “flexible / moderate / strict” styles. Instead, you get text and number fields per listing where you explain long‑stay behavior in your own words and choose exact days and refund percentages. That means you can mirror the main ideas from other channels while still adjusting details to protect your business.
The theme also lets owners treat short stays and multi‑month stays differently by describing that difference in the listing cancellation text. For example, one property could write “under 28 nights” and “28 nights or more” with distinct refund windows and percentages, even though the booking engine is the same. In a marketplace built on WPRentals, each owner can pick a pattern, so one might be generous and another strict, and the site still handles those variations without extra plugins.
How does this approach fit with partial payments and offline balance collection?
Long‑stay balances can be taken in stages while the system keeps a clear record of what’s owed.
WPRentals lets the admin set deposits anywhere from a small share of the total up to 100%. That’s useful for multi‑month bookings where you might not want full prepayment. After a guest pays the deposit, the system marks the booking as confirmed and shows both guest and owner how much remains unpaid. That amount can then be settled outside the site, for example by bank transfer on arrival, or through a second online invoice from the same booking.
- Deposits for long stays can be smaller upfront while the full amount stays tracked.
- Admins can send a second online invoice or collect balances in person.
- Guests and owners see the remaining balance figure inside their dashboards.
- WooCommerce support lets you route deposits and later payments through extra gateways.
FAQ
Can guests cancel a multi‑month booking themselves from their account?
Guests can request cancellation from their account area, but final status and refunds are handled by admin.
In a WPRentals site, guests see their bookings in a dashboard and can cancel or send a message about plans. When they act, the booking status updates and emails go out so hosts and admin know what changed. The actual refund, if any, stays a manual step you perform using Stripe, PayPal, bank transfer, or WooCommerce tools.
How is early departure on a long stay usually handled in practice?
Early departures are usually handled by applying the written cancellation rules and then sending any agreed refund manually.
For long multi‑month bookings in WPRentals, you normally explain in the listing what happens if guests leave early. When someone wants to leave before the checkout date, they contact the host or admin and you review the policy, local laws, and real situation. Based on that, you decide whether to refund unused nights, keep a part of the total, or only return the security deposit, and process that in your payment gateway.
Are mid‑stay date changes for long bookings automated?
Mid‑stay changes are handled by hosts or admin by editing or replacing the booking, not by guest tools.
WPRentals doesn’t give guests a button to move dates around during an active multi‑month stay. Instead, the guest reaches out, and the host or admin decides whether to shorten, extend, or cancel and rebook the stay. You can adjust the booking in the back end and, if needed, collect extra payment or send a partial refund using the payment provider.
Can I align my long‑stay policies with what guests see on OTAs?
You can write cancellation and refund rules that match the terms used on major travel platforms.
Because WPRentals uses open policy fields per listing, you can copy the core ideas of your OTA rules, such as a 30‑day cut‑off or non‑refundable long‑term rent. You explain them in your own simple language so guests see the same kind of terms. You still stay in charge of the final refund decision and payment flow on your site built with PMS (Property Management Software) style tools.
