Module languages and currencies

Ce contenu n’est pas encore disponible dans votre langue.


Why	Guests book in their own language and in a currency they understand — no mental math at check-in.
Who	Hotel owners and administrators who set up the booking module and the widget.
What you’ll get	A set of languages you have chosen for the module, a widget button translated into each language, and a clear money scheme: prices are set in the hotel’s currency, viewing is available in others.
Limitations	Multi-currency is for viewing only: the charge always happens in the hotel’s currency. There is no currency parameter in the module link — guests pick the currency themselves.

The booking module speaks the guest’s language: its guest-facing pages are translated into eight languages, and you choose which of them to offer. Prices are set in the hotel’s currency, but the guest can view them in another one — with an honest “approximately” mark on the conversion. Everything is configured in the PMS, without a developer.

The eight languages of the module

The guest-facing pages of the module are translated into eight languages: English, Russian, Ukrainian, German, French, Spanish, Italian, and Polish. A language switcher sits in the module header — the guest can change it at any moment while picking a room or filling in details. Each language in the menu is listed under its own name: English, Русский, Українська, Deutsch, Français, Español, Italiano, Polski — guests spot theirs at a glance, without deciphering an unfamiliar script.

You narrow the set yourself: keep all eight, or only the ones your guests speak. The rest stay out of the menu — the module never offers a guest a language you have not enabled.

The switcher is the guest’s choice: you define which languages are available, the guest uses any of them. Currencies work the same way — the viewing currencies are defined by the available exchange rates, not by the guest’s wishes.

How to set the languages

The module’s languages are configured in the Online booking section:

Open the Settings page, the General tab.
Find the Localization and currency block. The Default language field is the language the module opens in until the guest picks their own.
In the Available languages field, tick the languages guests will be able to choose in the booking module. Unticked ones are not shown in the menu.

The compact widget has its own language settings, on the Widget page of the same section:

In the Text and language block, the Widget language field is set to Auto (browser): the widget opens in the visitor’s browser language. You can pin a specific language instead.
The label on the widget button is set by the Button text field. Each language gets its own label — set them via the Customize button translations button.

Outcome: the module offers guests only the languages you have chosen, the widget opens in the browser language or a pinned one, and the widget button speaks each of them.

Where the settings live, at a glance:

Where	What it sets
Online booking → Settings, General tab, Localization and currency block	Default language, Available languages, Currency format
Online booking → Widget, Text and language block	Widget language, Button text and button translations

A language can also be baked into a link to the module — for a German newsletter that opens the module already in German. How to build such a link is covered in the article on link parameters (see “See also”).

Viewing currency

Prices in the module are set in the hotel’s currency — that is the currency guests pay in. Viewing prices, however, can happen in a convenient one: next to the language switcher in the header there is a currency selector, and the guest picks from the available options. Language and currency are two independent choices: a guest can read the page in German while viewing prices in euros, or the other way around.

The conversion rules are simple:

The conversion is approximate. Prices in a foreign currency carry an ”≈” mark: the viewing exchange rate is indicative, and the exchange rates refresh once a day.
The charge always happens in the hotel’s currency. The guest compares prices in their own currency but pays in the hotel’s currency — exactly the total built from your rates and the cart.
No rate, no conversion. If a currency has no rate available, prices are simply not shown in it: the guest sees the hotel’s currency price without conversion.
Viewing changes nothing. Rates are set in the hotel’s currency and counted in it in the PMS; the conversion is visible only to the guest — in their browser, in their session.

The price format is configured in the same Localization and currency block: the Currency format field sets what a price looks like — for example, the Symbol (€ 120) option.

Outcome: the guest estimates the cost in their own currency, while the payment goes through in the hotel’s currency — the amounts in the confirmation and on the charge match.

There is no separate currency parameter in the module link: a link can open the module with a chosen language, arrival date, or promo code, but the currency is always picked by the guest.

Three different numbers: 8, 10, and 2

HotelsCalendar materials mention three counts of languages. Each one is about a different surface, and they should never be folded into a single claim:

8 — the languages of the booking module: what guests book in on your website.
10 — the languages of the HotelsCalendar website: what these documents and product materials run in.
2 — the languages of the PMS interface: Russian and English — what you work in as a hotel employee.

If one sentence says “HotelsCalendar speaks ten languages,” a reader will assume the module does too. So in your own texts, spell out which surface you mean: the module, the website, or the PMS interface.

The rule is simple: writing about the hotel website and bookings — take eight; about the management interface — two; about the HotelsCalendar website — ten.