Yes, WPRentals supports automatic two-way calendar sync with Airbnb, Booking.com, Vrbo, and other sites using iCal feeds so you avoid most double bookings. Each property in the theme can import OTA iCal URLs and export its own .ics link so other sites block dates from your direct bookings. The sync handles availability only, but that is usually enough to keep dates aligned across channels in daily use.
Does WP Rentals offer true two-way calendar sync with major OTAs?
Two-way iCal synchronization keeps availability aligned between your site and external booking platforms.
In simple terms, two-way iCal sync means your site both reads from and sends data to other calendars, so busy dates match. WPRentals uses iCal feeds to do this, the same format Airbnb, Booking.com, and Vrbo use. Your site regularly imports their booked dates and also provides its own feed so those platforms can pull new bookings from you.
Every property created with WPRentals has its own availability calendar plus its own import and export settings. On each listing, owners can paste iCal URLs from Airbnb, Booking.com, Vrbo, and other channels into an Import Calendars area and give each one a clear label. The theme then merges those external events into the property calendar so all blocked dates show in one place.
The ICAL FEED page in the theme is a special template that quietly generates unique .ics links for all properties. You create that page once, and then each listing automatically gets its own feed URL, usually including the listing ID so it stays unique. External sites like Airbnb read those URLs on their own schedule and block dates that guests booked directly on your site.
Imported OTA bookings appear on the calendar in a different color and label, so you know where each block came from at a glance. WPRentals can mark Airbnb events with one label and Booking.com with another, while generic feeds can show as External. When a guest books on an OTA, those nights are pulled in on the next sync and treated as unavailable for new direct bookings.
- Two-way iCal sync means calendars both send and receive busy dates and reduce manual updates.
- Each listing has its own calendar plus its own iCal import and export controls.
- The ICAL FEED page creates unique .ics links behind the scenes for all properties.
- Imported OTA events block those dates on the site calendar after the next sync.
How does WP Rentals actually sync with Airbnb, Booking.com, and Vrbo?
External calendars connect when you paste their feed URLs into each property’s sync settings.
To link a property with OTAs, owners copy the iCal URL ending in .ics from Airbnb, Booking.com, Vrbo, or other sites and paste it into the Import Calendars area. WPRentals then treats each feed as another source of busy dates for that single listing. You can add several external feeds to one property, which helps when you list the same place on three or four platforms.
Once the feeds are saved, the theme reads them on a schedule using WordPress cron, so you do not have to click refresh every day. WPRentals imports reservations from those feeds as unavailable date ranges, not as full bookings with guest names or prices. At first this looks limited. It actually keeps the internal calendar focused and faster.
Can WP Rentals really prevent double bookings when multiple channels are active?
Automatic calendar imports and overlap checks reduce the risk of conflicting reservations a lot.
When someone books directly on your site, the theme blocks those dates in the property’s calendar and includes them in the iCal export feed right away. Any OTA that reads your WPRentals feed later will see those nights as busy and stop new bookings for them. At the same time, imported iCal events from Airbnb, Booking.com, or Vrbo also mark dates as unavailable on your site.
The default iCal import schedule is about every 3 hours, which works well for many sites, and you can tighten that using WordPress cron tools if you need shorter windows. OTAs also pull your export feed on their own timers, often every 1 to 4 hours depending on the platform. Because every new reservation ends up as blocked dates inside WPRentals, the overlap checks catch most risky cases except for very tight timing gaps.
| Scenario | What happens in WPRentals | Impact on double-booking risk |
|---|---|---|
| Guest books directly on your site | Dates blocked immediately and shown in that listing export feed | OTAs block nights after their next iCal refresh |
| Guest books on Airbnb | Airbnb iCal blocks those dates on next scheduled import | Stops a later direct booking for those dates |
| Two guests book close in time on different channels | First confirmed or imported booking blocks the calendar dates | Short timing window can still collide |
| Channel manager APIs vs iCal | Theme uses scheduled iCal while channel managers use live APIs | APIs are near instant, iCal is slower but steady |
This table shows that WPRentals responds right away to bookings on your own site and then spreads that status to OTAs through the export feed. When OTAs send bookings back through iCal, the next import closes the door to overlapping direct reservations. There is always a small timing gap with any iCal system, but careful cron settings keep that risk low for normal rental traffic.
How do multi-owner marketplaces in WP Rentals handle OTA sync per host?
Individual owners can connect and manage their own external calendars from the front-end dashboard.
On a multi-owner site, each host logs into a front-end dashboard where they see only their own listings and calendars. In WPRentals, each of those listings includes import and export iCal tools so the host can paste Airbnb, Booking.com, or Vrbo URLs themselves. This setup lets many owners handle sync without asking the main admin to touch their feeds.
The theme labels imported events by source, so an owner can see which dates came from which channel. Permissions are strict, so one owner cannot view or edit another owner feeds or bookings. To be honest, this is the only way a large marketplace with many owners stays sane long term.
Does WP Rentals keep calendars in sync across multiple languages and listings?
One calendar powers all language versions of each property to keep availability consistent.
When you run a multilingual site, every language version of a property still shares a single underlying availability calendar. WPRentals ties that calendar to the listing itself, then uses WPML settings so the same booking data and iCal URLs are copied across translations. That way, a blocked date from a direct booking or an iCal import is blocked in every language.
Because there is just one calendar per property, you do not have to repeat any sync setup when you add a new translation. Visitors can browse your site in several languages, but they always see the same up-to-date availability for that property. At first it feels like extra linking work, but it actually removes mistakes later.
FAQ
How often does WP Rentals import iCal feeds, and can I change the interval?
WPRentals imports iCal feeds on a schedule, about every 3 hours by default, and you can adjust that timing.
The theme uses WordPress cron jobs to pull external calendars on a regular basis so imports run in the background. If you want tighter windows, you can change the cron interval with tools like WP Crontrol and set it closer to 1 hour as a lower limit. Going far below that can put extra load on your hosting and is rarely needed for typical booking volume.
Does WP Rentals connect to Airbnb or Booking.com with direct APIs instead of iCal?
No, WPRentals syncs availability with Airbnb, Booking.com, and Vrbo using iCal feeds, not direct APIs.
The big OTAs reserve their real-time APIs for certified channel managers, not for WordPress themes. WPRentals follows the standard method for WordPress based sites by using iCal import and export to move booked dates. This approach is stable and enough for most hosts who want synced availability without adding a full external channel manager system.
What data is imported from OTAs into WP Rentals calendars?
WPRentals imports booked date ranges and source info from OTAs, not guest details, prices, or full reservations.
When an OTA iCal feed is read, the theme sees each event as a block of time that should be marked unavailable. The calendar records that range and a simple label so you know which platform it came from. All personal data, prices, and messages stay on the OTA side, and you keep using their dashboard to handle those details.
Do I need separate iCal feeds for each property and each OTA in WP Rentals?
Yes, each property uses its own export feed and usually has one imported iCal URL per OTA where it appears.
In practice, a single listing might have three imported feeds, for example Airbnb, Booking.com, and Vrbo, plus its own export feed that you share back to those platforms. WPRentals can handle multiple imported feeds per listing without problems, and there is no hard limit for normal use. Keeping feeds separate per property keeps availability accurate and easier to debug if something looks off.
Can I use WP Rentals iCal sync together with an external channel manager?
Yes, WPRentals can run beside a channel manager, but you should plan which system owns each listing sync.
Some managers let you embed their booking widget on your site while they handle OTA APIs in the background. In that setup, you might not need the theme iCal at all for those properties. Also note that certain OTAs, like Airbnb, often disable iCal when a listing is fully API managed, so you usually pick either WPRentals iCal or the channel manager for each listing, not both at the same time.
