WPRentals doesn’t include a special “parent listing” type that directly manages several “child” calendars. But you can still connect a whole property with its rooms by using separate listings and iCal calendar feeds between them. In practice, you create the main apartment or B&B as one listing, each room or bed as its own listing, then cross-import and export their iCal URLs. Over time, bookings in one unit block dates in the related ones, as long as you accept normal iCal sync delays.
How does WPRentals handle parent–child style relationships between listings?
Each rental unit works as an independent listing with its own calendar, pricing, and booking rules.
In WPRentals, a “parent” like a whole apartment and a “child” like a single room are both normal listings. The theme doesn’t create automatic hierarchy logic between them, so every unit stands on its own with its own settings and availability. At first this sounds limiting. It isn’t. This design keeps the booking engine focused, because each listing’s calendar only cares about its own reservations.
Every listing in WPRentals has its own calendar and price settings, and the theme blocks dates as soon as you confirm a booking on that specific listing. You can add a whole villa, a full B&B, and each separate room or bed as different listings that all live side by side. So a five-room guesthouse can work as six listings: one for the entire place and one for each room, each with fully independent control.
The theme’s pricing tools always work per listing, so you can tune how every unit behaves without changing the others. One room can have nightly pricing, another room weekly discounts, and the whole property a special monthly rate, all as separate listings in the same WPRentals site. Because the booking engine is listing based, any parent–child style structure starts from how you model those listings and calendars, not from a special “parent” object.
Can I link an entire property with rooms and keep calendars in sync automatically?
Calendar feeds can be cross-linked so related listings share updated availability data with iCal import and export.
WPRentals keeps each listing’s own availability solid, then uses iCal feeds so those calendars can talk to each other. Inside a listing, once a guest books, the theme blocks those dates right away, so you can’t double-book that same listing from your own site. From there, you wire calendars together by importing and exporting iCal URLs between your whole-property listing and its room listings.
The iCal feature lets any listing import external calendars and export its own feed, which you can reuse inside the same WPRentals install. That means the “Entire House” listing can import the calendars of Room 1, Room 2, and Room 3, so when a room is booked, the whole-house calendar sees those dates as blocked after the next sync. You can then export the whole-house calendar into each room to mirror whole-property bookings back down. At first this cross-linking feels complex, then it becomes routine.
| Scenario | What you configure | Resulting behavior |
|---|---|---|
| Room booked on site | Room listing exports iCal feed to whole property | Whole property blocks those dates after iCal refresh |
| Whole property booked | Whole property exports iCal feed to each room | All room calendars block the full stay range |
| External OTA booking in a room | Room listing imports Airbnb or Booking iCal calendar | Room locks dates, whole property syncs that feed |
| Manual admin block | Admin blocks dates in one listing calendar | Blocked dates appear in linked listings via iCal |
| Mixed whole and per room strategy | Cross-linked feeds plus clear rules per listing | Availability approximates parent child style logic |
The table shows that by piping iCal feeds between listings, you build a network of related calendars that share blocks. WPRentals still treats every unit separately. But careful cross-linking keeps your “parent” listing and its “child” units close enough for daily work, as long as you accept standard iCal delays of minutes to a few hours.
What practical setups work for whole-apartment versus per-room bookings in one site?
Many owners mix separate listings and booking rules to balance whole-property and per-room sales on one platform.
A common pattern in WPRentals is one listing for the entire property and one listing for each rentable room or bed. The theme lets you give each listing a different minimum stay, price, and booking mode, so you can push guests toward the mix you want. For example, you might set stricter rules on the whole-property listing so it doesn’t often clash with busy room calendars.
Some owners decide that room bookings should win by default and treat whole-property bookings as a bonus. In that setup, you use longer minimum stays or more advance notice on the whole-property listing, using per-listing booking rules. You can add simple text on the whole-property listing telling guests that those bookings depend on rooms being free. Sometimes that still feels risky if you’re worried about very tight gaps or late bookings.
I’ll be blunt for a moment here. Many people try to make one “perfect” structure and expect the system to solve every clash. It won’t. You’re still choosing rules. You’re still deciding if you’d rather lose one big booking or a few smaller ones. The software just follows the rules you set.
How does WPRentals prevent double-bookings and sync availability with external channels?
The system uses per-listing instant calendar blocking with two-way iCal sync to cut double-booking risk across channels.
When a reservation is confirmed on any listing, WPRentals blocks those dates on that listing’s calendar right away. That removes overlap risk inside your own site. You can switch between instant booking and request-to-book per listing, so some units might need approval before dates lock. Owners and admins can also open the calendar and manually block days or ranges, which helps for maintenance or offline bookings taken by phone.
Each listing in the theme can import and export iCal feeds, so availability stays aligned with Airbnb, Booking.com, or VRBO. The same mechanism can sync different listings with each other, such as sharing calendars between a parent-style whole property and its child-style rooms. iCal sync isn’t real time in any system, including big platforms. But WPRentals follows the common pattern where updates usually land within minutes to a few hours, which works for most vacation rentals.
- Each listing calendar blocks dates at once when a confirmed booking is created on your site.
- Two-way iCal sync lets every listing both import and export availability feeds to other calendars.
- Admins and owners can block dates directly in the calendar for maintenance or offline reservations.
- Per-listing instant or request booking modes control how fast dates get locked to new guests.
FAQ
Does WPRentals have a true parent listing that automatically controls all child calendars?
No, WPRentals doesn’t include a special parent listing type that directly owns and controls child calendars.
Each property, whether a whole house or a single room, is a standard listing with its own calendar. To approximate a parent–child setup, you create separate listings and cross-link their calendars using the built-in iCal tools. That way, bookings in one listing can block dates in related listings after the next calendar sync.
How fast does iCal sync run when I link a whole property and room listings?
iCal sync in WPRentals usually runs on a schedule with delays from several minutes up to a few hours.
The theme uses the same iCal method that large booking platforms use, and that format isn’t built for instant updates. You can still keep whole-property and room calendars in good shape by importing and exporting their feeds and letting the system poll them. For very time-sensitive cases, you can trigger manual syncs or add manual calendar blocks when needed.
Can one guest book several rooms or units in a single combined booking in WPRentals?
No, guests normally need to book each room or unit as a separate reservation in WPRentals.
The booking engine works at the listing level, so a reservation refers to one listing at a time, whether that’s a room or the whole apartment. Guests can still place multiple bookings in a row for different listings on the same site, using the same user account. Service fees, deposits, and availability all calculate per booking and per listing, which keeps calendars and reporting clear.
How do pricing, deposits, and service fees work when I use both whole-property and per-room listings?
All pricing, deposits, and service fees are set and charged separately on each listing in WPRentals.
You can set different base prices, weekly or monthly rates, and long-stay discounts for the whole property and each room listing. The theme’s service fee and deposit options also apply per booking, so a whole-house reservation can use one deposit rule while rooms use another. This per-listing approach lets you tune margins and conditions for each unit, even when you connect their calendars as a parent–child style group.
