The booking workflow in WPRentals is flexible through settings, so you can control instant booking, requests, and required info without touching core code. Admins and hosts pick per listing if bookings confirm at once or wait for review, while deposit rules and pay-later choices live in clear panels. For extra questions and checks, a child theme lets you extend forms and logic in a safe way, keeping main theme files clean and update ready.
How much control do admins and hosts have over instant booking per listing?
Each property can use instant booking or request approval through simple built-in controls.
The main control is an Instant Booking checkbox on every listing that hosts can flip on or off whenever needed. WPRentals also gives the site admin a global setting to allow instant booking, block it everywhere, or let owners choose per property. When instant booking is off for a listing, the system turns that property into a request-to-book flow with owner review.
This per-listing toggle makes mixed workflows real on one site, even with many properties. One owner can pick instant booking with a deposit, while another sticks to manual approval and full prepayment. When a guest selects dates, the booking engine checks that property’s mode and applies auto-confirmation or a pending request status.
Hourly versus daily booking type is also property-specific, so a meeting room can use hourly instant bookings while a holiday home uses daily request-to-book. Admins still keep final control through a global option that can force every booking into manual approval if the marketplace needs tighter checks for a while. That mix of site-wide rules and per-listing switches lives in the dashboard and doesn’t need custom coding.
| Control area | Admin setting | Per-listing setting |
|---|---|---|
| Instant booking allowed | Enable or block for whole site | Toggle checkbox per property |
| Approval mode | Force manual approval for all | Auto confirm if instant on |
| Booking type | Enable hourly bookings globally | Select hourly or daily booking |
| Deposit behavior | Define main deposit rule | Override with listing deposit |
| Frontend labels | Set general booking text | Show request or instant label |
The table shows how policy choices live at admin level, while listings still keep their own switches. At first that layering sounds complex. It isn’t, and it lets each property behave differently without touching any code.
Can I run a full request-to-book and manual approval flow without coding?
Manual review and approval for every booking runs from the dashboard with no custom scripts.
When instant booking is off globally or for one property, each new booking becomes a request with a pending status. WPRentals gives each owner a front-end dashboard where they see pending requests, check dates and guest details, then click to accept or reject. Until a host approves and the guest pays any required deposit, the booking stays in that waiting state and doesn’t fully block dates.
The admin can decide that all listings must use this manual approval flow by changing a single option in Theme Options. In that setup, even owners who like instant bookings must vet each guest first, which helps new or careful marketplaces. The theme sends email notices when a request arrives, when an owner approves, and when a booking gets canceled, so guests and owners stay informed.
Status handling and date blocking are tied to this approval process inside WPRentals, so you don’t need to write extra logic. After an owner clicks Approve, the guest must pay whatever deposit rule applies and the calendar blocks those dates as reserved. That’s enough to run a 100 percent request-to-book site at scale using only built-in options.
How customizable are booking form fields, guest details, and required information?
Default settings cover common required fields, while a child theme handles custom questions when needed.
The main controls live in Theme Options, where you pick which listing and booking fields appear and which are required. WPRentals lets you mark key data as mandatory, like guest number, check-in and check-out dates, or phone, so a request can’t be sent with missing basics. You can also show house rules and a terms page so guests view clear rules before sending any booking.
The booking price breakdown supports extra guest-related costs, such as extra person fees, fixed cleaning, and city taxes. That way guests see those costs below the form and the system adds them to totals in real time. In many real setups that mix covers most owner needs, so the built-in fields often work without change.
For advanced setups, WPRentals expects developers to use a child theme to extend the booking form and its checks. With a child theme, you can add new questions like “Purpose of stay” or “Arrival flight number” and connect them to the booking AJAX processing, without risking theme updates. That split keeps the normal interface simple for non technical admins, while still giving a developer room to shape the workflow for special cases.
Can I add my own terms, deposits, and pay-later rules without editing core?
Deposits, security bonds, and pay-later flows use settings panels and per-listing options, not core edits.
The deposit system starts with a global rule, where you define a deposit as a percentage of the booking total or a fixed amount. In WPRentals, setting this value to 0 creates a “pay on arrival” flow, where bookings confirm without upfront payment and balance is due later. You can also let some listings use their own deposit rules, like a higher bond for a luxury villa or special unit.
A separate per-listing deposit field can work as a security bond that appears in invoices and sits in the normal payment flow. When a guest books, the system lists rent, extra fees, and the deposit clearly, so surprises are less likely. After the first payment is made, the system tracks any remaining balance, which helps owners skip messy manual lists.
Custom texts like house rules, cancellation notes, and special policies live on listing edit screens and on dedicated pages. WPRentals shows those texts on the property page and near the booking form, so guests see them before they commit. Since all of this lives in the database instead of templates, you can adjust policies across many listings by changing texts and deposit settings, with no PHP edits.
How far can developers customize the booking workflow safely using a child theme?
Advanced workflow changes belong in a child theme so core files stay untouched and safe during updates.
The booking process uses AJAX functions that read form data, check rules, then create bookings or show errors. WPRentals documents the main functions, so a developer can copy and override them inside a provided minimal child theme. That method lets you add extra conditions, like checking a custom user flag, before a booking gets confirmed or even before it goes pending.
Because custom logic sits in the child theme, site owners stay safe when updates ship for the main theme code. You can also add small client-side checks with custom JavaScript, such as blocking a booking if a new custom field is empty. In practice, many teams extend the workflow in only a few short functions and leave the heavy work to the main booking engine in WPRentals.
Now, from a different angle, this does mean you need someone technical for deep changes. You can tweak text and deposits alone, but real custom flows like special checks or extra approval steps usually need a developer. That split can feel annoying when you first hit the limit, yet it’s what keeps future updates from breaking your whole site.
FAQ
Can I mix instant booking and request-to-book on the same WPRentals site?
You can mix instant booking and request-to-book by toggling settings per listing or globally.
The global theme option decides whether instant booking is allowed at all, while each listing has its own Instant Booking checkbox. With WPRentals, some properties can auto confirm as soon as payment is made, and others can always wait for owner approval. That gives you a hybrid marketplace where pro hosts move fast and more careful owners vet every guest.
Can hosts change booking modes seasonally without technical help?
Hosts can change booking modes seasonally by editing their listing settings in the dashboard.
A host only needs to uncheck or check the Instant Booking box on their property when high or low season starts. WPRentals instantly switches that listing between fast auto confirm and slower request-to-book, with no code and no admin edit needed. Some managers use this to tighten control in busy periods and relax rules when demand drops again.
Can I add new required guest questions without breaking future theme updates?
You can add new required guest questions by placing custom code in a child theme instead of core files.
The usual pattern is to extend the booking form template and the related AJAX handler from a WPRentals child theme. That way, validation and saving of your extra question live in your own files, while the parent theme stays untouched. When you later update the theme, WordPress keeps your child logic in place, which avoids painful file merges.
Is it possible to add document checks or extra approval steps to bookings?
Extra checks like document requirements are possible by extending the booking logic in a WPRentals child theme.
A developer can hook into the same booking AJAX flow that WPRentals uses and add custom conditions before approval. For example, you could block confirmation until an ID upload flag is stored on the user or until an admin sets a meta field. Those advanced flows stay separate from core code, so you gain control without losing update safety.
- Most booking options sit in WPRentals settings instead of editing any PHP files.
- Per-listing switches let owners choose instant booking or request-to-book whenever they need.
- New custom checks and fields should live in a child theme to keep updates smooth.
- Complex approval chains need developer work using the documented booking functions in WPRentals.
