Yes, WPRentals supports multi-language and multi-currency while staying clear for APIs, payment gateways, and tax tools. The site shows many languages and currencies, but all stored prices use one base currency. That base currency runs through bookings, taxes, and exports. So external systems see stable IDs, prices, and tax fields, no matter the guest language or display currency.
How does WPRentals handle multi-language content for global rental sites?
WPRentals works with leading translation plugins to power multilingual rental marketplaces without breaking integrations.
The theme runs as a single-site, multi-language setup, so all languages share one WordPress backend and booking database. You connect a translation plugin like WPML or Weglot, and the theme exposes its custom post types, fields, and booking strings for translation. That setup keeps one source of truth for listings and bookings but still gives guests language-specific pages, emails, and search labels.
With WPML, WPRentals ships a wpml-config.xml file that lists custom fields and booking-related meta to translate. This covers custom price labels, amenities, and advanced search labels, not just page text. Each property becomes a main listing with linked translations, so translators can add, for example, English, Spanish, and German versions. The calendar and booking rules stay shared across those versions.
Weglot is often used for teams that want a very fast setup, since it can auto-translate most front-end output in minutes. Owners keep working in one base language in the dashboard, and Weglot handles inline translation for property pages, booking forms, and menus. Because the theme still stores one copy of each field in the database, external APIs and CRMs always see consistent content IDs and structures. Guests see translated text, but the raw records stay the same.
The theme also lets you localize datepickers, search widgets, and booking emails per language. With WPML, you can translate email templates so a French guest gets full French confirmation emails, while a US guest gets English ones. AJAX search labels and date formats can be set per locale, like dd-mm-yy for much of Europe or mm-dd-yy for the US. At first this feels complex. It isn’t, because booking logic and the REST API stay language-agnostic, so external systems just get clean data.
Can WPRentals show prices in multiple currencies while keeping accounting consistent?
WPRentals lets guests browse in many currencies while your records stay in a single base currency.
The money model is simple: one base currency is used for all bookings, invoices, and owner earnings in the database. You set that currency in Theme Options, and the booking engine always saves nightly rates, fees, and deposits in that unit. Because of this, exports to CRMs, accounting tools, or custom APIs don’t juggle mixed currencies. That keeps reports and tax work far easier.
On the front-end, WPRentals adds a multi-currency widget that shows prices in several display currencies. In the admin, you define each extra currency with its code, symbol, and formatting such as thousands and decimal separators. Many sites use three to five visitor-facing currencies, but the theme doesn’t hard-limit the count. The symbol position is adjustable too, so you can show formats like “€120” or “120 Kč” to match local style.
For conversion, the theme supports automatic daily exchange-rate updates using a free external rates API such as CurrencyLayer. You enter an API key and WPRentals refreshes the rates about once every 24 hours, which is usually enough. When a guest switches currency, JavaScript recalculates all price outputs from the stored rate, including search results and single property pages. No extra database writes happen during that switch, so speed and data integrity stay solid.
| Aspect | Stored in database | Shown to guest |
|---|---|---|
| Base currency | Single global currency | Named in checkout and invoices |
| Extra currencies | Codes symbols conversion rates | Switchable via front end widget |
| Exchange rates | Daily updated numeric values | Used in on page conversion |
| Invoices and earnings | Base currency amounts only | Same figures in all languages |
| API and CRM exports | Same base currency fields | Not changed by visitor currency |
This structure keeps the accounting layer in one clean currency while visitors can browse in their own currencies. WPRentals remembers the selected currency in a session or cookie so guests see consistent prices as they move. Caching plugins can be tuned to respect that cookie so pages don’t mix currencies by mistake. External APIs, channel managers, and tax tools always receive base-currency amounts, which avoids a common integration problem.
How can we take real multi-currency payments and still integrate external gateways?
You can pair the booking engine with WooCommerce to enable real multi-currency payment processing without losing gateway options.
On its own, WPRentals collects online payments with built-in Stripe and PayPal support, always charging in the base currency. That works well when guests see converted prices but get charged in, for example, EUR only. The booking system keeps full control of availability, deposits, and invoices, and external gateways just see a single currency. Refunds and disputes stay simpler too.
When you want to actually charge guests in several currencies, you can switch WPRentals into WooCommerce checkout mode. In that mode, the booking engine passes the booking amount and context into WooCommerce as an order, and WooCommerce takes over payment handling. This lets you use many payment gateways and advanced rules through WooCommerce extensions while WPRentals still manages rental logic, booking dates, and calendars.
Because WooCommerce is optional, you only enable it when your site truly needs extra gateways or complex tax and currency rules. With WooCommerce multi-currency plugins or WooCommerce Payments, you can charge customers per chosen or detected currency without changing the booking data model. WPRentals simply hands over a base-currency price, and WooCommerce applies its currency rules at checkout. That keeps external gateway and tax integrations aligned with normal WooCommerce behavior.
Does WPRentals play nicely with external APIs, CRMs, and automation tools?
The system exposes its data through the WordPress REST API that external platforms can read and update.
WPRentals uses the WordPress REST API to provide endpoints for listings and bookings, so external apps can use normal GET, POST, PUT, and DELETE calls. A CRM, channel manager, or custom back office can pull properties, create bookings, or update reservation status with standard HTTP patterns. Because amounts stay in one base currency and language sits on a separate layer, API clients see stable schemas and predictable numeric fields.
The theme also ties its booking flow into normal WordPress action hooks that developers can use for custom outbound calls. For example, when a booking is confirmed, a small custom plugin can call an external API to sync the reservation into a property management system (PMS). Some site owners connect those hooks to webhook tools so booking data reaches services like Zapier or an internal ERP. They do this without changing WPRentals core files, which matters for updates.
For less technical setups, automation plugins can watch WPRentals post types and then push data where needed. Because the REST endpoints and post types behave like regular WordPress objects, tools that already support WordPress usually work right away. Actually, this is the real benefit. The REST API and base-currency storage model mean multi-language and multi-currency display settings never twist the raw data that CRMs, analytics tools, and tax systems read.
What options exist for handling international tax rules and compliant invoices?
For complex tax setups, you can hand checkout to WooCommerce’s tax and invoicing system while WPRentals tracks bookings.
The theme includes per-listing tax percentage fields used to calculate owner-side tax amounts inside internal invoices. Each owner or property can store a percentage like 10 or 21, and WPRentals shows that portion as tax on the owner invoice, lowering net earnings for that booking. Guest-facing totals stay clear. Internal reports give a simple view of tax-related amounts per booking, per owner, or per period.
When you need country-based guest taxes, VAT rules, or formal tax documents, enabling WooCommerce mode is the practical route. WPRentals passes the booking amount to WooCommerce, and WooCommerce applies its tax engine with country, state, or VAT-ID rules. Guest and owner dashboards still show HTML invoices with price, fee, and tax breakdowns, and you can add a WooCommerce PDF invoice plugin if you need downloadable tax documents. This way, the booking system and tax engine stay separated but still work together.
I’ll be blunt here. Tax rules change, and they cause stress. WPRentals avoids trying to copy every tax edge case and instead lets WooCommerce handle it. You might still need an accountant, and maybe a country-specific tax plugin. But the line between bookings and tax rules stays clear, which is worth a lot long term.
FAQ
Does using multiple languages or currencies affect the WPRentals REST API data?
Multi-language and multi-currency display settings don’t change the structure or base values returned by the REST API.
The API always exposes bookings, prices, and fees in the single base currency you chose in WPRentals settings. Translation plugins handle only front-end text, and the multi-currency widget affects on-page display only. External tools that read from the REST API see one clean currency and stable fields, which keeps integrations simple and safe.
How do translation plugins work with CRMs or channel managers that pull data?
Translation plugins sit on top of the core data, so external systems can still read and sync the main records reliably.
WPRentals stores each property and booking once, then links language versions through tools like WPML without duplicating logic. A CRM or channel manager can pull the base listing and booking data via the REST API or direct database access. If you need translated fields in those external systems, you can map specific language versions, but IDs and calendars stay consistent across languages.
Will owner earnings and commissions stay correct if guests browse in other currencies?
Owner earnings, commissions, and invoices always use the site’s base currency, no matter which display currency guests choose.
The multi-currency widget simply converts numbers on the page using the stored exchange rate, without changing booking records. When a reservation is confirmed, WPRentals saves the total, fees, and owner earnings in the base currency and builds invoices from that. Reports, exports, and manual payouts all work from those base-currency figures, so nothing drifts due to visitor currency choices.
When should we combine translation plugins, WooCommerce, and multi-currency extensions?
You combine them when you need deep localization and real multi-currency charging on top of WPRentals bookings.
A common advanced stack is WPRentals for booking logic, WPML or Weglot for language, WooCommerce for checkout, and a WooCommerce multi-currency extension. That setup lets guests browse in many languages, see local currencies, and pay in their own currency, while you still store bookings in one base currency. It takes careful configuration. But done right, it supports a global audience without breaking APIs, gateways, or tax workflows.
