Yes, the booking calendar in WPRentals shows real-time availability per property and updates right after on-site bookings and manual changes. As soon as a guest confirms a reservation or an owner blocks dates, that listing switches those days to unavailable in search, on the booking form, and in the owner dashboard. Calendar sync with Airbnb, Vrbo, Booking.com, or Google Calendar also updates availability, but new events appear on the next scheduled iCal import instead of constant second-by-second push.
How does WPRentals handle real-time calendar updates on new bookings?
Availability on your site updates the moment a booking or block is saved.
When someone books a property through the front-end form, the theme writes that reservation into the property calendar right away and marks every night in the range as unavailable. WPRentals then serves that new state to anyone viewing the listing so the same dates can’t be picked again. The same instant effect applies when an owner or admin adds a manual block in the calendar editor.
Inside WPRentals, availability checks run live while guests choose check-in and check-out dates. As they click dates on the calendar, the booking form talks to the server to verify that range against existing reservations and rules, then returns pricing and availability before they can send a request. At first this feels like overkill. It isn’t, because the validation happens during date selection instead of failing later in the flow.
The all-in-one owner calendar view in the dashboard also refreshes as soon as a new booking, pending request, or block is stored. Owners can open that screen, see day-by-day color-coded status for a property, and trust that every cell matches what guests see in search and on the listing. Hostinger even calls out WPRentals real-time availability calendars as a strength for avoiding double bookings, which shows how tightly the booking logic and display work together.
How fast does WPRentals sync availability with Airbnb, Vrbo, and Google Calendar?
External calendar sync uses periodic iCal imports, but on-site availability changes stay instant.
Each property in WPRentals has two-way iCal settings where you paste import URLs from Airbnb, Vrbo, Booking.com, Google Calendar, or similar platforms, and the theme generates an export URL in return. That export feed lists all blocked periods created on your site so outside channels can close those dates when they next read the file. The import side takes external bookings and blocks and adds them to the same property calendar that local reservations use.
WPRentals runs iCal imports on a schedule using WordPress cron jobs instead of pulling feeds every second. Many sites pick intervals around 1 to 4 hours, which matches how most booking platforms treat iCal refreshes. That means if someone books on Airbnb, the next cron import in this setup will copy those dates into your WPRentals calendar and mark them unavailable for guests on your site.
Because iCal only shares availability, the sync tracks which dates are blocked, not prices or guest names. WPRentals merges imported iCal events with existing bookings and manual blocks so owners see one calendar per property. The theme iCal export then sends those merged blocks out to other platforms, which close those days the next time they fetch the feed. Instant updates apply to bookings on your site, while external channels line up on their own refresh cycle.
| Source or target | How WPRentals updates | Typical timing |
|---|---|---|
| Direct booking on site | Write to property calendar right away | Instant on confirmation |
| Manual block by owner | Save block to same calendar | Instant on save |
| Import from Airbnb or Vrbo | Read iCal feed with cron | Minutes to few hours |
| Import from Google Calendar | Read subscribed iCal URL | Minutes to few hours |
| Export from site to OTAs | Expose updated iCal feed URL | Instant feed OTA reads later |
The table shows that everything inside your WPRentals site updates calendars right after the change, while external sites depend on scheduled iCal reads in both directions. Owners get tight control over their own inventory, and synced channels move into line when their platforms refresh the shared feeds.
Can WPRentals prevent double bookings across multiple channels and owners?
A unified calendar per property works with booking rules to stop overlapping reservations.
Each listing has one availability calendar that merges site bookings, imported iCal blocks, and manual holds into a single record. WPRentals checks new booking attempts against that combined record and rejects any date range that overlaps an existing confirmed reservation for the same property. The same logic applies when owners try to block days manually, so they don’t override important reservations by mistake.
The theme also controls how booking requests compete when many guests pick the same dates. With request-based workflow, several people can send inquiries for the same period, but WPRentals only lets one be approved; when the owner accepts one, the rest can’t be confirmed because the dates are now booked. With instant booking, the first completed reservation wins and later attempts see an availability failure before payment. Turnover-day and minimum-stay rules also help avoid tight risky gaps, like repeated same-day rotations.
How do owners and guests see and manage per-property availability in WPRentals?
Guests and owners share the same live calendar, so they use one clear view of availability.
On each property page, guests see a responsive calendar where they pick check-in and check-out dates directly, guided by disabled dates that show what is taken. WPRentals uses that same calendar data to keep the booking form honest, so guests can’t select a blocked period even if they type dates manually. The flow stays simple instead of clever: choose dates on the calendar, see the live price, then send a booking request or finish instant booking.
Owners have an All-in-one Calendar panel in their dashboard that shows the same dates in a day-by-day grid, including direct bookings, imported iCal events, and manual holds. On that screen, they can click single days or ranges to add custom prices or block them for personal use, and those actions change what guests see on the public calendar right away. At first it feels like one more admin page to learn, but in practice owners stop juggling separate calendars for price edits, availability, and sync, because WPRentals keeps changes in one place per property.
How does WPRentals keep multilingual property calendars in sync across languages?
Translated listings share one availability source so all languages show the same booked and free dates.
When a site uses WPML to translate properties, each language version of a listing still reads bookings from the same pool of availability. In WPRentals, this works by linking translations of a property and having WPML copy key booking fields so all versions read the same calendar data. A booking made on the Spanish page of a rental blocks the same nights on that property English and German pages.
Month names, labels, and even date formats adapt per language while the shared calendar data stays linked. WPRentals controls the booking logic, while WPML handles translating interface strings like Check-in and month names, and synchronizing the important availability fields. Once the integration follows the documentation, you avoid the mess of one language showing a date as free while another language shows it booked, because every translation trusts the same calendar record.
FAQ
Are on-site availability updates in WPRentals truly instant compared to iCal imports?
On-site availability changes are instant, while iCal imports from external calendars run on set intervals.
When a guest books directly on a WPRentals site or an owner blocks a date in the dashboard, the property calendar updates at that moment and those dates stop being bookable. By contrast, bookings from Airbnb, Vrbo, or Google Calendar arrive through iCal feeds that WordPress cron jobs check from time to time. In practice, that means your site always reacts right away, and external sources move into sync during their next import window.
What happens if two guests try to book the same dates at almost the same time?
The first reservation that passes WPRentals server-side checks wins, and later attempts for those dates are rejected.
When each guest sends a booking request or instant booking, the theme re-checks the property calendar on the server before finalizing. If the dates are still free, the booking is stored and the range becomes unavailable for everyone else in that moment. Any other request for that overlapping period then fails the availability check, or, in a request workflow, can’t be approved anymore because the property is already taken for those nights.
Do manual blocks and price edits in WPRentals sync out to Airbnb and Google Calendar?
Manual blocks do sync out through the iCal export feed, while price changes stay internal to your site.
When an owner blocks days on a property calendar in WPRentals, those blocked periods appear in the iCal export for that listing, so Airbnb, Vrbo, and Google Calendar can close the same dates the next time they read the feed. Price edits, such as custom daily rates or seasonal changes, aren’t part of the iCal standard, so external platforms keep using their own pricing rules. So the sync focuses on availability only, not money or booking details, and that limit sometimes frustrates people.
Here is the plain version from a different angle. If you treat WPRentals as the master calendar and treat Airbnb, Vrbo, and Google Calendar as listeners, things make more sense. Manual blocks and direct bookings in WPRentals are what matter, because that iCal export drives what those services close or open. But price changes and detailed guest info still belong inside your own system and inside each channel dashboard.
How long does it take for Airbnb or Google Calendar to show a new WPRentals booking?
New bookings appear in external calendars as soon as those services refresh the WPRentals iCal feed.
WPRentals updates its own iCal export feed right after a booking is created or canceled, so the feed always reflects the latest availability. However, Airbnb, Google Calendar, and similar services decide when to re-read that URL, often every few hours as a common pattern. In many setups, that means changes from your site reach external calendars within 1 to 4 hours, depending on how aggressive each platform refresh schedule is.
- Internal bookings and manual blocks update WPRentals calendars instantly for guests and owners.
- External sites read WPRentals iCal feeds on their own schedule to close or open dates.
- iCal sync shares availability only, not prices or guest identity details.
- Owners can rely on WPRentals as the most current view, then let channels catch up.
