You keep guests from seeing and booking a room when the whole property is taken by treating each space as a separate listing, then blocking the room listings on the same dates as the full-property listing. In WPRentals, once dates are booked or unavailable on a listing calendar, guests can’t pick them in search or on the booking form. To keep rooms matched with a full-property booking, you block them by hand or use sync.
How does WPRentals handle full-property versus individual-room bookings?
Each rentable unit has its own calendar, and booked dates don’t show to guests.
In WPRentals, every room, apartment, or full property is its own listing with a separate availability calendar. The booking form checks only that listing calendar, so if dates are blocked there, guests can’t select them for that listing. At first this seems limiting. It isn’t, because the logic stays clear and easy to track.
To offer a “whole villa” and also “Room 1, Room 2, Room 3,” you create one listing for the whole place and one listing for each room. The theme treats each of those as separate units, each with its own prices, rules, and availability. Since each listing acts on its own, you always know which calendar controls what guests can see and book.
Once you or an external calendar sync marks days as booked or unavailable in a listing calendar, WPRentals hides those dates from guest search and from that listing date picker. Guests never see those days as free, and the booking engine won’t accept a request for them. So the hard part isn’t blocking dates, it’s keeping the right calendars lined up.
| Type | Listing Needed | Calendar Behavior |
|---|---|---|
| Single room rental | One listing per room | Blocks only that room dates |
| Full property rental | One separate full-property listing | Blocks only full-property dates |
| Room plus full property | One listing per room plus one whole | Each calendar acts alone |
| External iCal sync | iCal per listing | Imports blocks into that calendar |
| Manual blocks | Use Book Period action | Creates internal booking blocks |
This table shows that control always lives at listing level, so you stop wrong bookings by blocking the correct calendar. When the full-property listing is the “master” for a house, you just need a habit or automation to mirror its booked dates across the room listings.
What practical setup should I use for a property that can be rented by room or as a whole?
Use separate listings for rooms and the full property, then keep their calendars aligned.
The clean setup is simple. Create one listing for the entire property and one listing for each room inside it. In WPRentals, that might mean four listings for a small house with three rooms: “House Entire,” “House Room 1,” “House Room 2,” and “House Room 3.” Each listing then gets its own prices, minimum stay rules, and booking mode.
Use clear names and short descriptions so guests know what they’re getting before they book. For example, use a pattern like “Casa Azul – Entire Villa,” “Casa Azul – Room 1 Balcony,” and “Casa Azul – Room 2 Garden View.” In the description fields, the theme lets you explain if the kitchen or living room is shared, and how many rooms are included. This cuts confusion and lowers the chance a guest books a room thinking it’s the whole place.
Set pricing and rules separately for the full-property listing and each room listing so your setup matches real life. You might want a 3 night minimum for the whole property and only 1 night for rooms, or a discount for renting all rooms at once. WPRentals gives each listing its own pricing panel and booking rules, so you don’t have to share rules across the group.
How can I manually block room calendars when the full property gets booked?
Use the unified calendar view to block all related rooms when the property is reserved.
When a guest books the entire property, you stop new room bookings by blocking the same dates on each room listing calendar. In WPRentals, you can open each room listing from the front-end dashboard and use the calendar to select those dates. Then you click the “Book Period” button, which creates an internal booking block so guests can’t pick that time frame anymore. It’s a little boring, but it works every time.
The faster way, especially when you manage more than 3 rooms, is the All-in-One Calendar from the owner or admin dashboard. This screen shows every related listing in one grid, with colors for booked, pending, and blocked periods. For a full-property booking, you find the correct dates once, then click in each room row to mark those same days as blocked without opening every listing page. It still takes focus, though, and people do forget.
Manual “Book Period” actions act like real bookings in the theme, so they fully block search and the booking form for those dates. WPRentals color-codes manual blocks differently from external iCal blocks, which makes it easier to see what came from you versus another platform. With a short routine of blocking a few listings right after confirming a full-property reservation, you stop guests from seeing a room that shouldn’t be free.
- Open the All-in-One Calendar and locate the full-property booking dates in the timeline.
- Click the same date range on each room row and choose the Book Period action to block them.
- Confirm that room cells change to the manual block color so they’re no longer available.
- Repeat for any extra rooms or annexes tied to the same physical property.
Can I automate blocking rooms using iCal or the WPRentals REST API?
External sync and the API can mirror full-property bookings to room calendars automatically.
You can partly automate mirroring by using iCal sync between your listings. WPRentals lets you export the full-property iCal link and import it into each room listing calendar settings. As a rule of thumb, the sync delay is from a few minutes up to several hours. Once it runs, any full-property booking shows as blocked dates in each room calendar without you clicking anything.
For tighter control or near real-time behavior, developers can use the WPRentals REST API (Representational State Transfer Application Programming Interface) to create bookings or blocked periods on room listings as soon as the whole place gets booked. An external tool can watch for a “new booking” event on the full-property listing, then call the API to post matching blocks to all related room listings. At first that sounds complex, but it uses the theme booking logic as the main source while cutting manual work.
What day‑to‑day workflow keeps me from accidentally double‑booking rooms and the whole property?
Combine manual approval with calendar checks to prevent conflicting room and property bookings.
A safe daily routine is to turn off Instant Booking on all listings that share the same property, then approve each request by hand. In WPRentals, you can switch each related listing to “Request to Book,” so no reservation is confirmed until you click approve. This gives you a chance to look at the All-in-One Calendar before you let any booking pass. It slows booking a bit, but it protects your schedule.
Before approving a new booking, open the All-in-One Calendar and scan all listings from that property for the date range. If you’re about to approve a full-property booking, block the same dates on all room listings right after you confirm it. Using clear internal names such as “Villa Luna – R1,” “Villa Luna – R2,” and “Villa Luna – Entire” makes it easier to find the right rows and avoid mistakes. Then again, naming won’t fix a process that no one follows.
I’ll be blunt for a moment. Most problems here come from rushing approvals without a quick calendar scan. The toolset in WPRentals is fine, the weak part is the habit. So when you design your routine, write it down for yourself or your staff and treat it like a checklist.
FAQ
Can guests ever see dates that I have already marked as booked or unavailable?
Guests can’t select or book dates that you’ve marked as booked or unavailable.
When you block days on a listing calendar, the WPRentals booking form refuses to offer those dates. The date picker skips them, and search results don’t suggest stays that include them. This covers manual blocks, internal bookings, and iCal imported blocks, so your blocked rules stay firm for guests.
What happens if one listing has a pending request for dates that overlap another related listing?
A pending request tentatively blocks dates for that listing, but it doesn’t touch other related listings.
If a guest sends a booking request for a room, WPRentals marks those dates as pending on that room calendar until you approve or reject. Other listings, including the full-property listing, stay free unless you block them yourself. To avoid problems, many owners approve only one of the overlapping requests and then manually block the others right away.
Can I hide room listings completely and only show the full property to guests?
You can hide rooms by unpublishing or not creating separate room listings, leaving only the full property visible.
WPRentals shows to guests only what you publish as listings, so if you don’t want room-only bookings, just skip those listings. You can also move a room listing to draft or change its status if you used it in the past but want to retire it. With only the full-property listing online, there’s no risk that guests will see or book single rooms.
How does blocking work when I use hourly mode instead of daily mode?
Hourly mode blocks time slots on the same listing basis, so you still manage each calendar separately.
In hourly mode, WPRentals lets you set business hours and book by the hour instead of by the night. When you block a period on a listing, those hours become unavailable in the booking form while other listings remain unaffected. For a meeting space with multiple rooms and a full-venue option, you still need the same habit or automation to block related calendars when the entire venue is booked. The pattern is the same, only the time scale changes.
