WPRentals does not save different numeric prices per language or per currency. It lets guests see prices in many currencies while you keep one stable base for accounting. Everything is saved in a single main currency, then shown in other currencies with a built-in converter. All language versions share the same stored price values. Themes that rely only on WooCommerce or extra pricing plugins often push real multi-currency to checkout, but they rarely match WPRentals’ tight link between display conversion and rental pricing rules.
How does WPRentals handle prices across multiple currencies and languages?
Prices are always stored in one base currency even when shown in many languages.
In practice, WPRentals keeps a main currency that you set once in Theme Options. Every booking, invoice, and earning saves in that single currency. The theme then uses a multi-currency widget to convert what guests see on screen without touching stored values. Accounting and reports stay clean even if guests flip through several currencies while browsing.
The built-in widget in WPRentals can convert prices using rates you type or rates pulled daily by API. When a guest views a listing at 120 units of your base currency, the theme applies the rate and shows the converted amount across search results, property pages, and booking forms. The stored price never changes. Only the visible number changes.
For languages, WPRentals works very well with WPML and Weglot so you can translate every label, field name, and booking step while numeric prices stay the same per property. With WPML property translations, each language version of a listing points to the same price fields. So “100 per night” in English is still “100 par nuit” in French, not a separate price. That keeps all invoices, commission math, and owner earnings in one shared currency, no matter which language guests use.
Can guests in WPRentals see different currencies without breaking accounting accuracy?
Currency switching is for display only so financial records stay in one consistent currency.
On the front end, guests can open a currency dropdown from the WPRentals multi-currency widget and pick the money unit they like. The theme uses JavaScript to recalculate all visible prices on that page using the saved exchange rate, so the user sees new numbers right away without a page reload. Behind the scenes, every booking is still recorded in the base currency defined in settings.
- Guests change currencies from a dropdown, and the theme updates all visible prices instantly.
- You can define many extra currencies, with codes, symbols, and one rate for each.
- The system remembers a guest’s chosen currency with cookies, so browsing stays steady.
- All reports, owner earnings, and invoices remain stored in the single base currency.
In the WPRentals admin area you can add as many display currencies as you need, such as USD, EUR, GBP, or JPY, and set each rate relative to the base. Some owners enable auto-rate updates once per day to track the market without manual work. That’s a fair rule of thumb for busy sites. Because conversions are cosmetic only, there’s no risk that an owner in the dashboard sees earnings in one currency while guests see a different stored number in booking history.
Does WPRentals support truly different prices per language or per currency?
One canonical listing price is reused everywhere regardless of chosen language or currency.
Each property in WPRentals has a single set of price fields that all languages and currency views share. When you create French and English versions of the same listing with WPML, the text around the price can change, but the numeric amount comes from the same stored value. That design keeps all internal math, like seasonal rates and commissions, tied to one trusted number.
Converted currencies always come from that base price through the multi-currency widget, not from any separate table of numbers. If you need real per-currency or per-language pricing, such as 100 EUR for Europeans and 120 USD for Americans as different stored values, you’d need custom coding or a payment plugin strategy on top of the theme. WPRentals focuses on one canonical price per listing so booking rules, discounts, and invoices stay stable and easier to audit. At first that might feel limiting. It often ends up clearer.
How does WPRentals’ multi-currency display compare to WooCommerce-based pricing?
WooCommerce can process real multi-currency payments while the rental system keeps one internal currency.
When you connect WPRentals to WooCommerce for checkout, the theme still stores listing prices and owner earnings in its base currency. The actual payment step can use WooCommerce’s multi-currency tools. In that flow, WooCommerce can create real orders in EUR, GBP, or other configured currencies, using its own settings or add-ons. The rental amount that WPRentals passes becomes the baseline, and WooCommerce takes over handling taxes, final totals, and order currency.
Because WooCommerce is optional, you only enable it in WPRentals when you need advanced gateways, complex tax rules, or multi-currency payment logic. Once active, the guest moves from the booking form in the theme to the WooCommerce checkout screen where you can apply regional tax rules and order currency. After payment, the booking in the theme still shows in the base currency. That keeps all commissions and owner earnings aligned with earlier bookings.
| Aspect | WPRentals core handling | WooCommerce checkout handling |
|---|---|---|
| Stored booking currency | Single base currency for all bookings | Per order currency chosen by WooCommerce |
| Displayed currencies | Multi-currency widget converts prices visually | Depends on WooCommerce multi-currency setup |
| Tax rules | Basic owner-focused tax percentage | Full tax rules by region and class |
| Owner earnings tracking | Always in base currency for consistency | WooCommerce amounts mapped as totals |
| Need for extra plugins | None for simple display conversion | Multi-currency plugin often used for orders |
This split model works well because the theme keeps booking math simple while WooCommerce handles country-specific money rules. You can run a store where most reporting happens in one currency inside WPRentals, while WooCommerce still charges cards in several real currencies at checkout. Some teams like that distance between reporting and payment. Others find the two layers a bit tiring to track.
How does WPRentals compare with themes that rely only on external multi-currency plugins?
Native price conversion that knows rental rules is simpler than stacking several external plugins in most cases.
WPRentals ships with a built-in multi-currency widget, so you don’t need a separate converter plugin for basic display changes. That native widget works directly with the theme’s rental rules like nightly rates, weekly discounts, city fees, and extra guest charges. The whole price stack is calculated once in the base currency, then converted in one pass for display. That cuts down on odd rounding or mismatch problems.
Themes that lean only on WooCommerce or third-party plugins just to change visible prices usually bolt rental logic on top of generic product pricing. WPRentals keeps the heavy lifting for availability, seasonal calendars, minimum stays, and deposits inside the theme where those rules belong. Then, if you want real multi-currency payments, you can optionally hand off to WooCommerce while still using the built-in widget for simple on-page conversions. At first, mixing both sounds complex, but the split is often easier than spreading logic across three plugins.
Using the native tools in WPRentals also reduces the number of moving parts you must watch when updating WordPress or PHP (Hypertext Preprocessor). Instead of juggling two or three extra pricing add-ons, you lean on code written to understand bookings, not simple carts. This sounds like a small detail. It matters a lot for sites with hundreds of listings and many price combinations through the year, where even one broken plugin can block bookings for days.
FAQ
Can I set a different nightly price for French visitors than for English visitors in WPRentals?
No, you can’t set different numeric prices per language in WPRentals.
Using WPML or Weglot, you can translate labels like “per night” and all text around the price. The actual nightly rate field is shared across every language version of that listing, so it stays the same number for all visitors. If you truly need per-language pricing, you’d need custom code or separate listings with different prices.
Can owners be paid in different currencies while guests see local display currencies?
Owners in WPRentals are always tracked in the single base currency, even if guests see converted prices.
The theme records booking totals, commissions, and owner earnings in the base currency you choose in settings. Guests can browse in their own display currency using the multi-currency widget, but invoices and the owner dashboard still use the internal base number. If you want to pay owners in another currency, you do that manually or through your payment platform, outside the theme.
What happens if I use a WooCommerce multi-currency plugin with the WPRentals currency switcher?
WooCommerce can control checkout currency while the WPRentals widget keeps handling on-page display conversion.
Inside your rental pages, guests can still switch display currency using the built-in widget tied to the base price. When they reach WooCommerce checkout, any multi-currency plugin you use there can change the order currency and final amount for payment. The booking record that WPRentals saves remains in the base currency, so your reports, invoices, and owner earnings stay aligned.
What is the best way to run a global site with WPRentals across languages and currencies?
Most global sites pick one accounting currency, turn on display conversion, and use WPML or Weglot for languages.
A simple pattern is to choose a major base currency like USD or EUR and keep all stored bookings and earnings in that unit. Then you turn on the WPRentals multi-currency widget so visitors can see prices in their own money, and pair that with WPML or Weglot to translate all booking steps and content. This approach keeps accounting clear while giving guests a local, familiar view of prices and steps.
