Yes, WPRentals lets you turn off its booking engine and still keep property listings active. You can switch each listing, or your whole site, to use inquiry or external links instead of the built-in booking box. In that case, listings still show photos, details, maps, reviews, and search works as usual, while real reservations go through your other system.
Can I turn off the built‑in booking form and still show properties?
You can keep full property pages while switching the booking form to a simple inquiry form.
In WPRentals you can show a contact or inquiry form instead of the booking box on the listing page. The date picker, price breakdown, and Book Now button stay hidden, but the page layout itself stays the same. Agencies use this when they confirm stays by phone or another system but still want a clean catalog on site.
When you run in inquiry-only mode, WPRentals keeps the full property presentation. Image galleries, descriptions, amenities, maps, reviews, and sidebar widgets stay in place. Search, advanced filters, and archive pages keep working, and guests can sort and filter by price, location, or features. The real change happens on the side of the page where the booking panel used to be.
The inquiry form sends messages into the front-end dashboard so owners or the main admin can answer from one place. WPRentals lets each listing owner receive and reply to those messages under their own account, even if payment happens somewhere else. From the guest view, nothing looks broken. They still see a clear call to action, just focused on Contact instead of Book.
- You can flip a setting so listings use a contact form instead of the booking box.
- All listing content like galleries, amenities, maps, and reviews keeps showing with booking disabled.
- Inquiry messages are delivered to the owner or admin through the front-end dashboard messaging.
- Search, filters, and archive pages keep working so you still have a full directory.
How can I plug in an external booking engine or custom checkout flow?
You can redirect booking actions to an external engine while using the theme for display.
The simple way to hook an outside system into WPRentals is to hide the built-in booking box and place your own button, shortcode, or widget there. WPRentals layouts work with Elementor and theme templates, so developers can drop custom HTML or an external booking snippet into the property sidebar. At first it feels complex. It is not.
This lets you show a third-party widget where the booking form used to sit, while the rest of the page uses the standard design. Many teams prefer a separate checkout route, and the theme supports that flow. You can change the main Book or Reserve call to action into a link that opens a URL from your PMS (Property Management Software), channel manager, or SaaS booking page.
In that case, WPRentals handles search, listing display, and user accounts, while the external system takes care of payment, taxes, and final confirmation. Often this is set once per template and then reused across many listings. Sometimes people overthink it. Usually a single template edit is enough.
If you want the external flow to still live inside WordPress, WooCommerce is the natural add-on. WPRentals can send bookings into WooCommerce so checkout, taxes, and payment gateways are handled by WooCommerce instead of the built-in screens. You only need WooCommerce if you require special gateways or advanced tax rules. Otherwise the native payment tools work fine, but WooCommerce gives more control over custom checkout steps.
For deeper control, a child theme is the right place to override specific templates and insert third-party booking widgets. Developers often override the single property sidebar template and paste in shortcodes or script tags from their own engine. In that setup, WPRentals keeps its booking logic out of sight, but its listing model, search engine, and owner dashboards still run the site. You end up with a clear split. Your code handles reservations, the theme handles everything guests see before clicking Book.
What happens to availability calendars and pricing tools if I disable booking?
You can keep calendars and pricing visible even if guests can’t book on the site.
Turning off live booking requests doesn’t force you to hide the calendar or prices, unless you choose to. In WPRentals each listing layout can show the availability calendar for guests as guidance. That calendar can still show booked and free dates even if guests cannot send a booking from that screen. This matters when real reservations finish elsewhere.
All the pricing tools in WPRentals can stay active as display-only. Seasonal prices, length-of-stay discounts, extra fees, and security deposits can show in the price breakdown without powering the final charge. iCal sync keeps working too, importing blocks from sites like Airbnb and exporting your own blocks so other systems can read them.
Owners can keep blocking dates from their dashboard so the calendar reflects the real schedule even if payment flows are external. Sometimes this double work feels annoying. But it keeps guests from asking for dates that are already sold on another platform.
Can owners still use their dashboards if bookings are handled elsewhere?
Owners can keep using the same dashboard to manage listings even if reservations run in another system.
Turning off the built-in booking request doesn’t remove the owner tools. It just changes what they’re used for. WPRentals keeps the full front-end owner dashboard online so hosts can edit titles, descriptions, photos, amenities, and locations at any time. Owners can upload new media, fix text, and improve listing quality without opening the WordPress admin.
The messaging center can stay central even when you move payments out of the theme. Owners and guests can send questions and answers through the internal chat tools, using WPRentals as the shared inbox for everything that happens before a stay. Some sites tell owners to treat this messaging as the official record, while the external booking engine is only for card details and invoices.
Calendars in the owner dashboard remain useful because hosts can record or block stays that were confirmed somewhere else. An owner might block three nights for a bank transfer or a call-in booking by clicking those days and saving. The booking, invoice, and report screens in WPRentals can work as internal tracking, helping admins see what happened in a given month or year, even if another system processed payment.
This setup lets you grow in stages instead of forcing a hard switch. You can start with WPRentals handling everything, then plug in an outside engine for payments while owners keep the same dashboard habits. For larger teams with many owners, this mix avoids retraining everyone on new tools at once. Sometimes that halfway state lasts for years, and that is fine.
How does the REST API help when using a custom booking backend?
The REST API lets developers sync listings and reservations with external booking platforms.
WPRentals exposes a REST API that developers can call from custom apps, channel managers, or in-house booking systems. Through these endpoints you can read and update property data, including titles, prices, and metadata, so your external backend always sees the latest details. Then you can also write back changes when you manage content or rules in another tool. At first this looks like extra work. It usually saves time later.
| API area | Main purpose | Typical use case |
|---|---|---|
| Property endpoints | Read or update listing details | Sync titles photos and amenities |
| Booking endpoints | Create and fetch reservations | Store external bookings in WordPress |
| Availability endpoints | Block or free calendar dates | Mirror external engine availability |
| Authentication layer | Secure API access | Limit actions to trusted systems |
| Postman documentation | Speed up developer onboarding | Test calls in minutes |
Developers can combine these API tools with a custom backend that owns the booking and payment logic. The theme handles front-end views and search, while your service uses the API to push bookings, blocks, or listing changes on a schedule. Official Postman collections and standard WordPress authentication make this integration faster, often cutting setup from weeks to days. For some teams that gap is the whole reason they choose WPRentals.
FAQ
Can I disable the booking engine for some listings but keep it for others?
Yes, you can control booking vs inquiry per listing.
Each property in WPRentals can have its own setting for using the booking form or the contact form. You can keep instant or request booking active on some listings while switching others to inquiry-only. This mix helps when some owners rely on an external system and others like the built-in flow.
Do I have to use WPRentals payments, deposits, and invoices if I move checkout elsewhere?
No, you can ignore the built-in payments and let your external checkout handle money.
When you hide the booking box or send guests to another checkout, WPRentals invoice and payment tools become optional. You can still use them as internal records if you want, or leave them off while your other gateway handles charges, deposits, and refunds. WooCommerce support is available when you need a more advanced checkout funnel inside WordPress.
Can I run the whole site with only inquiry forms and no online payments at all?
Yes, you can run a pure inquiry site with no online payments.
By switching the booking form to a contact form for all listings, guests only send questions or requests, not firm reservations. WPRentals then sends those messages into the owner or admin dashboards so replies stay organized. Many agencies like this mode when they prefer bank transfers, phone approvals, or offline contracts instead of instant cards.
Is WPRentals compatible with external PMS and channel managers?
Yes, it works well alongside external systems using iCal, WooCommerce, and the REST API.
You can keep availability in sync with other platforms through iCal import and export, which most PMS (Property Management Software) tools accept. For deep linking or custom flows, the WPRentals REST API and WooCommerce integration give developers the hooks they need to connect a PMS or custom engine. In that setup, the theme is your front-end hub while the external system stays the source of truth for bookings.
