Yes, you can manage separate translated versions of the same property in WPRentals and still keep availability and bookings in sync. Each language can have its own text and even different photos, while one shared booking engine tracks the real calendar. WPRentals uses WPML-ready linking so all translations point to the same internal property, which means one pool of dates, one set of bookings, and no double-booking risk across languages.
How does WPRentals keep one availability calendar across all translations?
One master calendar can serve every translated version of the same property when WPRentals is linked with WPML (WordPress Multilingual Plugin). At first this feels complex. It isn’t.
In WPRentals, each property has a single booking engine and availability calendar, and every translation connects back to that same property record. WPRentals is officially listed as a WPML recommended theme, and the combo keeps the booking data in one place while pages in different languages just view that data. You don’t create a new calendar for every language, only new translated pages that use the same one.
To keep everything lined up, WPRentals works with WPML’s Multilingual Content Setup so key custom fields stay shared. In WPML you mark WPRentals booking meta such as availability data, booking status, and iCal URLs as Copy or Copy once. After that, any new booking written to the main property is mirrored to all its translations because they all read those copied fields. The same iCal links are also shared, so external channels see one master feed per property, not separate feeds per language.
Owners and admins still work from one place. The owner or admin dashboard in WPRentals shows each booking only once, no matter which language page the guest used. A booking created on the Spanish version appears in the same central calendar view as a booking from the English version. From there you can block dates, confirm requests, and manage pricing, and every change is reflected on all translated listing pages that point to that property’s calendar.
| Element | Where it lives | How translations see it |
|---|---|---|
| Availability calendar | Single master property | Shared across all language pages |
| Bookings and blocks | Core booking meta fields | Copied via WPML Copy settings |
| iCal import URLs | Property-level settings | Same URLs reused per translation |
| Owner dashboard view | Main WPRentals account | Shows bookings from every language |
| Language content | Separate translated posts | Unique per language no effect on dates |
The table shows a clear split. Booking logic and availability live in one master record, while translated pages simply read that shared data. With WPRentals and WPML configured this way, you avoid parallel calendars and keep booking control in one stable source of truth.
Can each language version show different photos, descriptions, and amenities in WPRentals?
Each language can customize content while still sharing the same property inventory and calendar in WPRentals. This is where the system feels flexible instead of rigid.
With WPRentals connected to WPML, each translation of a property is its own post for content, but they all map to the same internal listing. You can translate the title, the long description, and every visible custom field using WPML’s translation editor, so French guests read native text instead of a copied English block. The theme pulls availability from the shared booking fields, so these content changes never fork your calendar.
Media is flexible too. You can reuse the same images from the WordPress media library in every language, or upload language-specific photos, like a floor plan with translated labels. Amenities and house rules can be translated independently per language while the underlying property ID stays the same. The checklist a German visitor sees can use German names, but the choice itself still matches the same amenity in the shared booking data.
How are bookings kept in sync when guests book from different language versions?
A reservation on one language version updates availability on all other languages that show that property. That sync doesn’t wait.
When a guest sends a booking request or instant booking on any translated page, the WPRentals booking engine writes that reservation into the single calendar that belongs to that property. Because every translation pulls availability from those shared meta fields, the dates are blocked right away everywhere. If someone books July 10–15 on the French page, the English, Spanish, and German pages will no longer offer those nights in the same second.
Status also stays aligned. When you move a booking from pending to confirmed or to canceled in WPRentals, that change hits the shared record. Every language page that shows that property reads the same updated status and calendar, so there is no risk that one translation still behaves as if dates are free. For external channels, the property still uses a single iCal import and export set, so Airbnb or Booking.com see the same availability, no matter which language the guest used on your site.
This unified design also prevents ghost bookings in your admin area. In the WPRentals owner or admin dashboard, each booking is listed once with its full date range, price, and guest info. The language of the front-end where the booking was created doesn’t create a separate booking row. That keeps accounting, reporting, and manual changes simple, even if you support many languages on the same rental website.
What is the correct way to configure WPRentals and WPML for linked translated listings?
Correct WPML field settings ensure all translations share one booking and availability dataset inside WPRentals. The setup itself is simple, but details matter.
The clean workflow is to first create the original property in one language, set up its prices, iCal, and booking rules in WPRentals, and only then build translations. Using WPML, you duplicate that property into other languages so the posts are linked as translations, not random copies. That link lets WPML decide which custom fields to sync, and WPRentals expects this link so the booking engine treats all versions as the same property.
The key step is in WPML’s Multilingual Content Setup, where you mark the WPRentals booking fields, availability meta, and iCal URLs as Copy or Copy once. That tells WPML to keep those values the same across translations while letting text fields be translated. After this setup, new bookings are written to the original property and WPML shares the updated data so all languages see the same blocked dates. If you had bookings before translations existed, you can push that history into translations by updating and resaving those translated posts one time.
- Create the main property in your base language and finish all WPRentals booking settings first.
- Use WPML to duplicate the property so translations are linked, not manually recreated.
- In WPML Multilingual Content Setup, set booking and availability custom fields to Copy or Copy once.
- Follow the WPRentals and WPML guide that lists the exact fields for correct availability.
How does WPRentals handle multilingual calendars, date formats, and currencies?
Localized calendars show familiar formats without changing the underlying shared availability in WPRentals. Here the system behaves more like a display layer.
The calendars and booking forms in WPRentals follow your WordPress locale and language settings, so month and weekday names change with each language. An Italian version of the site shows Italian labels and can use a day-month-year display, while the same property in English can follow a month-day-year style. All of that is just presentation, because the theme still uses the same internal date ranges to store bookings for that property.
Week start day and date format are taken from WordPress or language-specific settings, which keeps things clear for guests from different regions. WPRentals also includes a multi-currency display widget that lets visitors switch the shown currency while the booking engine runs in one base currency. Prices guests see are adjusted for their picked currency, but the shared calendar and booking records stay tied to consistent internal values.
I should add one more thing. Some users expect currency changes to change the stored values, but here they don’t. Only the view changes, which is usually better for reports and payouts.
FAQ
Do I need to create separate properties per language, or just one property with translations?
You should create one property in WPRentals and then add linked translations for each language.
The correct pattern is to make a single listing with full booking setup, then use WPML to duplicate and translate it. That way, all language versions point to one shared property ID and booking dataset. You get different text per language but keep one calendar, one iCal feed, and one set of rules to manage.
Does an owner have to manage availability separately for every language version?
No, owners manage availability once per property and WPRentals shows the same calendar on every language page.
Owners and admins work only with the master calendar in the WPRentals dashboard when they block dates or change prices. Each translated listing simply reads that same availability data, so there is no French calendar or German calendar to update. This keeps daily work simple even when the front-end supports many languages.
Will Airbnb or Vrbo bookings sync to all languages automatically from one iCal feed?
Yes, a single iCal feed per property in WPRentals syncs availability for all translated versions of that listing.
You set up iCal import and export once for the property, and that calendar is the same one used by every language version. When Airbnb or Vrbo sends new blocked dates, WPRentals updates the master calendar, and all translations show those dates as unavailable. There is no need to configure separate iCal links per language page.
What happens if an admin edits availability from the backend on one language?
Any availability change in the WPRentals backend affects the shared calendar and all language versions at once.
If you block dates, add a booking manually, or cancel one from the admin side, the master calendar is updated. Because each translation reads from that same data, guests on every language page see the new state without extra steps. You don’t have to repeat the same change on translated listings.
Can I use other translation tools like Weglot or TranslatePress with WPRentals?
Yes, WPRentals can work with tools like Weglot or TranslatePress for simpler single-post multilingual setups.
In those tools, you usually keep one property post and translate strings on the front-end instead of duplicating posts. That means the availability calendar is naturally shared, because there is only one property record. If you want more control over per-field sync and many properties, WPML plus WPRentals is still the most structured approach.
