Yes, WPRentals supports both multi-currency and multi-language so you can work from one backend. You run a single WordPress site, connect WPML or Weglot, and enable the built-in multi-currency widget so prices show in the visitor’s own money. Bookings, invoices, and owner tools still stay in one dashboard, so you are not juggling several sites or manual exports.
How does WPRentals handle multi-language sites from a single backend?
The platform lets you run several languages from one backend without separate sites. At first this sounds messy. It is not.
WPRentals is fully tested with WPML (WordPress Multilingual Plugin), so you manage all languages in one WordPress dashboard. The theme ships with a dedicated wpml-config.xml file that tells WPML which custom fields, booking labels, and widgets need translation. Property details, search labels, and booking steps each get their own language version. You work in one admin area and just switch language when you edit content.
With WPRentals and WPML, every key element lives in one install, including listings, custom fields, emails, and theme strings. You translate properties like normal posts, link language versions, and keep one shared calendar and booking logic behind them. The same rule applies to pages like Terms, FAQs, and contact forms, which you translate through WPML’s String Translation and Translation Editor tools. This setup keeps structure simple, even if you run several languages at once.
The theme also works with Weglot if you want automatic machine translation instead of manual work. In that case, WPRentals sends front-end content through Weglot, which builds translated versions on the fly in many languages. You still have one backend and one listing set, but guests see the version that matches their choice. WPML’s own directory lists WPRentals as a recommended multilingual booking theme, which suggests stable support over time.
What is the international guest experience like with WPRentals translations?
A fully translated interface can increase trust and booking conversions for international guests. Half-translated pages often do the opposite.
WPRentals lets you translate dynamic content so guests do not hit mixed-language pages. Property titles, long descriptions, amenities, house rules, and custom fees all get a language version through WPML or Weglot. Booking and reminder emails can be translated too, so a French guest receives French text and a German guest sees German content. That cuts confusion at key steps like check-in info and payment notices.
The theme works with language switchers from WPML or Weglot that you can place in the menu or header. Many setups also use automatic language redirection based on browser locale, so a visitor from Spain lands on Spanish content. Datepickers and calendars in WPRentals can load localized month and weekday names per language, so the booking calendar feels normal, not foreign. This detail matters more than people expect at the booking step.
Industry studies show localized travel sites can see strong conversion bumps compared with one-language sites. WPRentals helps by letting you localize fixed labels, the booking flow, and system emails together. Guests read in their own language, see dates in a familiar format, and are less likely to abandon payment. For agencies working across at least two regions, that extra trust often turns into steady extra income.
How does WPRentals support multi-currency price display for global visitors?
Guests can browse all properties in their preferred currency while you keep one main accounting currency. The two views stay linked.
WPRentals includes a Multi-Currency widget that shows a currency dropdown on the front-end. You pick one base currency in Theme Options, then add extra display currencies such as EUR, GBP, or CAD. For each extra currency, you set code, symbol, and rate against your base. The theme then converts every visible price on listing cards, single pages, and search results using that rate.
In the WPRentals admin panel, you can define many currencies and choose how they look. The theme lets you place the symbol before or after the amount and choose decimal and thousand separators. You can set rule-of-thumb rates manually or let them refresh daily by entering a free exchange-rate API key. When that runs, the site pulls new rates once every 24 hours, so visitors are not looking at very old numbers.
Once a guest picks a currency, the widget stores that choice in a cookie or session. That way they can open many property pages and still see prices in, say, AUD without picking again. The base logic in WPRentals still keeps bookings, invoices, and reports in your main currency, which keeps accounting simple for you and your accountant. At first, separate display and base units seem odd, but that balance usually works best.
| Feature | Admin control | Guest effect |
|---|---|---|
| Base currency | Set once in Theme Options | Used for every real booking |
| Extra currencies | Add unlimited codes and symbols | Appear in the currency dropdown |
| Exchange rates | Manual control or daily API refresh | Display prices stay roughly current |
| Formatting options | Choose separators and symbol position | Numbers look normal for each region |
| Session storage | Cookie based preference tracking | Chosen currency follows each visitor |
The table shows how you keep strong control while guests still get a local-feeling view of prices. You set one base and a few common visitor currencies, tweak formats, and let the widget handle conversion. That keeps front-end comfort high without turning the backend into a complex multi-ledger system.
Can I accept true multi-currency payments and taxes while still using one backend?
Connecting a flexible checkout system lets you charge guests in several currencies while keeping management centered in one place. It sounds more complex than it usually is.
WPRentals itself stores all bookings, invoices, and owner earnings in one base currency only. Every reservation record uses the same money unit, which keeps logs and reports clear. The display widget can still show other currencies, but when the booking is saved and invoiced, it goes back to the base. For many sites working mostly in USD or EUR, this design is enough and avoids confusing accounting.
If you want to charge cards in several currencies, you can plug WPRentals into WooCommerce and let that handle payment logic. WooCommerce is optional and mainly needed when you want extra gateways, detailed tax rules, or real multi-currency order handling. In that mode, bookings pass totals to WooCommerce checkout, where you can run multi-currency or geolocation rules with the right extensions. Taxes like VAT or regional sales tax can be set as WooCommerce tax classes and applied by country or state.
The theme also includes a per-listing tax percentage field that affects owner-side earnings, not guest-facing lines. WPRentals uses that field to show how much tax an owner owes based on the booking, which helps when you track net payout expectations. The guest still sees a simple price unless you push tax detail into WooCommerce and its invoices. In practice, many international agencies run one base currency, let WooCommerce add country taxes, and only enable full multi-currency charging when there is clear demand.
How does WPRentals keep international pricing, formatting, and UX consistent across markets?
Consistent local formats for dates, numbers, and currencies reduce confusion for guests from different regions. When formats drift, support tickets grow.
The theme lets you match number and price formats to the habits of your main visitors. In WPRentals options, you can pick thousand and decimal separators and decide where the currency symbol shows. A French user can see 1 200,50 € while a US user sees $1,200.50, even if both read the same base price. You set these rules once in the backend, then mostly forget them.
- You choose date formats like dd-mm-yy or mm-dd-yy so calendars feel normal for guests.
- Datepickers and booking calendars follow the active language, including month and weekday names.
- Number and currency formatting options keep prices readable for at least three major regions.
- Careful caching rules stop stored pages from showing the wrong currency or language to visitors.
To be honest, this part can feel fussy. Tiny format changes can trigger long email threads with owners or staff. Then you adjust a separator or symbol and the problem just stops. It is boring work, but once you lock your rules, the site looks more stable in every market.
FAQ
Does the multi-currency widget change the payment currency or only the display?
The multi-currency widget in the theme changes display values only, not the actual payment currency.
Inside WPRentals, all bookings and invoices are stored in your single base currency, like USD or EUR. The widget simply reads that base price and shows a converted value for visitor comfort. At checkout, the real charge still uses the base currency unless you pass payment through WooCommerce and a multi-currency gateway.
Can I manage all languages and currencies from one WordPress dashboard?
All languages and all currency settings are managed from a single WordPress dashboard.
With WPRentals, you run one site and connect WPML or Weglot for translations, plus the built-in currency tools. You add and edit listings once, then attach translations, and adjust the multi-currency widget from Theme Options. There is no need for several separate sites for several languages, which cuts maintenance time and reduces sync mistakes.
How do owners and renters see language and currency inside their dashboards?
Owners and renters see dashboard screens in the active site language and with prices formatted to the chosen currency display.
On a WPRentals site using WPML, the front-end dashboards share the same translated strings and labels as public pages. If a guest browses in Spanish, their booking list and invoices show Spanish labels and the display currency they picked. Owners see their earnings in the same base currency you use internally, but the interface language still matches their chosen locale.
What is a common setup for agencies targeting several countries?
A common setup is WPML for two to four languages, one base currency, and the multi-currency widget for display.
Many agencies running WPRentals choose a strong base currency like EUR, translate the site with WPML or Weglot, and enable several visitor currencies. Payments are typically charged in that base currency through Stripe or PayPal, sometimes via WooCommerce when tax rules become complex. This pattern keeps reporting simple while still giving each guest a localized experience across language, dates, and prices.
