Yes, WPRentals handles both instant bookings and request‑to‑book in one system, and you choose the mode per listing. Each property can run as instant booking or request‑to‑book through a simple setting. So you can mix styles across your site. Owners and admins get clear controls to switch modes whenever they need.
How does WPRentals support both instant booking and request-to-book?
WPRentals supports both instant booking and manual booking requests as built-in workflows with no extra plugins. Both flows work from day one, since the booking engine is part of the core theme. When instant booking is off for a listing, every booking attempt becomes a request that waits for the owner’s decision.
Owners see booking requests in their built-in owner dashboard, where they can approve or reject with a couple of clicks. WPRentals then updates the calendar, shows the new status, and sends emails so the guest knows what happened. This setup keeps owners in control without forcing them into a separate admin area.
Payment logic works with both flows in a clear way. WPRentals can require full payment, a fixed deposit, a percentage deposit like 30%, or even 0 dollars at booking time. When an owner approves a request, the theme can generate an invoice and ask the guest to pay the deposit online. If you want to run a “request booking and pay later” style, you can do that with the same tools.
- Instant booking and request-to-book both run on the same booking engine.
- Turning off instant booking on a listing converts new attempts into approval requests.
- Owners approve or reject requests directly from their WPRentals owner dashboard.
- Each confirmed stay can use full payment, a deposit, or 0 dollars upfront.
Can I choose instant booking or request-to-book separately for each property?
Each property can switch between instant booking and request-based reservations at any time through its own settings. Inside every listing edit screen, there is an “Instant Booking” checkbox that controls the mode for that single property. WPRentals reads that checkbox when a guest hits the booking button and changes the front-end flow.
When the box is checked, guests see a “Book now” action and the reservation confirms as soon as payment rules are met. When the box is unchecked, the same listing turns into a request‑to‑book flow. In that state, the button label changes to “Request booking,” and the system records a pending request instead of an instant confirmation. WPRentals then waits for the owner or the admin to press approve.
Global behavior is also under your control. In Theme Options, you can forbid instant booking site‑wide, allow it everywhere, or let each owner decide per listing. That means you can launch in a safer mode where all stays are requests, and later open instant booking only for trusted owners. Changing modes is just a settings change, not a code edit, so hosts can adapt between peak and low season.
How do payments, deposits, and pay-later options work with both modes?
Flexible deposit and pay-later options work with both instant and request-based bookings inside the same payment rules. In WPRentals, the admin sets one set of deposit rules, and those rules apply in both booking modes. You can require a fixed fee, a percentage like 20% of the total, or set the deposit to 0 so guests pay nothing upfront.
The theme then treats that amount as the trigger for a confirmed booking in instant mode, or as the next step after approval in request‑to‑book mode. For request‑to‑book, the flow is simple to follow. The guest sends a request with no payment, the owner approves from the dashboard, and WPRentals automatically issues an invoice for the deposit. Once the guest pays, the booking becomes fully confirmed and the calendar is blocked.
Balance payments are tracked in the system, and reminders can be sent before check‑in so owners know if money is still due. Offline and pay‑on‑arrival cases follow the same logic. You can pick gateways that support pay later, or set the deposit to 0 and mark bookings as paid by other means. This handles guests who want to pay by bank transfer, at the front desk, or on arrival.
Can I mix different booking rules and experiences across owners and listings?
Different owners can run different booking styles on the same marketplace without conflict or double-booking problems. Each owner account gets its own dashboard where that owner controls booking rules for their listings. At first this sounds like it might clash everywhere. It doesn’t.
WPRentals treats rules separately, so one host can use strict request-only bookings while another runs instant booking on several properties. The theme reads the per-listing settings at booking time, so guest experience matches the host’s choices. That part is predictable. Owners like that.
Per-listing options also reach beyond just the booking button. You can vary security deposits, daily versus hourly mode, and minimum stays, so one listing can be a 2‑night apartment while another is a 3‑hour meeting room. If the marketplace needs tighter control, the site admin can open a listing in the backend and override values for that one property.
Owners can also add manual bookings to block dates when they close a deal offline, keeping calendars in sync across at least 2 channels. I know, that offline part can feel messy in real life. But here the main thing is simple enough. You add the manual booking, block the dates, and move on.
| Who controls it | What can differ | How WPRentals applies it |
|---|---|---|
| Owner per listing | Instant vs request booking | Reads instant checkbox for listing |
| Owner per listing | Security deposit amount | Uses listing deposit in price |
| Owner per listing | Minimum stay and booking type | Enforces nightly or hourly per property |
| Admin per listing | Override booking preferences | Edits listing settings in backend |
| Owner per listing | Manual blocking for offline deals | Adds manual bookings to block dates |
The table shows how control is split between owners and admin while the engine stays one piece. WPRentals always checks the listing’s own settings first, which is why different booking styles can live together on one marketplace.
FAQ
Can I disable instant booking across the whole site for a cautious launch?
Yes, you can turn off instant booking globally so every new booking works as a request first.
In the Theme Options panel, WPRentals lets the admin force manual approval for all listings in one switch. When that is active, even if owners tick the instant booking box, the theme still treats new attempts as requests. This makes it safer to launch while you are still learning your owners and guests.
Do I need a developer to change modes for different seasons?
No, switching between instant booking and request-to-book by season only needs simple setting edits.
Each listing has its own instant booking checkbox that owners or admins can change whenever they want. You can tell your hosts to enable instant booking during quieter months and then turn it off during high‑risk dates. WPRentals applies the new mode right away, so you can adjust in minutes without touching code.
Can I build more complex, multi-step approvals on top of WPRentals?
Yes, developers can add extra approval steps with custom code while keeping WPRentals main booking logic.
Out of the box, the theme supports a single approval step where the owner accepts or rejects. If you want manager reviews, document checks, or other custom rules, a developer can hook into the booking process in a child theme. That way the core update path stays clean while the custom workflow runs before final confirmation.
Do I need extra plugins to run instant booking and request-to-book together?
No, WPRentals runs instant and request-style reservations side by side without extra booking plugins.
The booking engine, owner dashboards, and payment rules all live inside the theme’s own system. You only add WooCommerce if you need more payment gateways, not to control booking modes. At first that might sound limiting, but in practice it keeps setup simpler.
