The power of our translation tool
We give you the right tools to ensure that you no longer lose international customers, but turn them into paying customers instead. The configuration in bookingkit is really easy and in this article we explain how you can increase your reach and turnover in just a few steps!
Important notice:
Activating this module will extend which of your content in the bookingkit webapp will be updated and with what regularity.
Changes and updates to the content in the default language are made immediately.
Changes and updates in other languages can take up to 24 hours.
Activate the module
First have to activate the Content Localization module under Settings -> Modules :
Manage your languages
After activating the module you can view and manage the status of your translations under Settings -> Translations. Please note that it may take a few minutes until everything is set up and ready for configuration right after the activation of the module!
The translation overview appears once all the settings are successfully loaded. The default language is always the language setting for your account. Then you can choose from up to sixteen different languages, which ones should be available to your international customers. How exactly all this works is explained in the following points.
Add more languages
Once you have added another language to your account, you can adjust some settings:
Would you like an overview of all the translated content? No problem, you are only one click away. Tip: You can simply send this file to an agency for translation if needed!
You can either translate your content manually or, as mentioned in the first point, translate the whole content or have it translated by professionals and then upload the file.
As soon as you have translated 100% of all content, you can also select this language as your default one. What is the point? The default language serves as a reference for all other translations.
You do not want to offer have your content in this a language in the future? Then deactivate it here with just one click.
Add translations
If you decide against translating your content in bulk (refer to point 2), you can also do the translations manually. Just look for the globe symbol in your bookingkit backend. If you have not yet translated all elements at a certain point, you will be notified by a red exclamation mark next to the globe and can add the corresponding translation with just one click:
On the other hand, if a green check mark appears next to the globe, you can sit back and watch as you receive bookings from all around Europe and the world!
Now you might ask yourself at where translation may be necessary! You can either make an export (please refer to point 1) or you manually check all existing content such as your experiences, products, flexible tickets, after-sales mail, company data, etc.
Good to know
bookingkit automatically translates the buttons in all your widgets as well as all customer correspondence via email such as ticket and invoices.
💡 Special Case: Widget behavior for unsupported languages (e.g., Japanese)
When an end customer opens or selects a language in the widget that is not configured for the respective experience or is not supported by the system, the behavior varies depending on the widget type (Classic vs. Floating).
There is no uniform automatic fallback to a fixed default language of the vendor.
1. Classic Widget (Behavior based on Session Persistence)
The Classic Widget does not have a fixed fallback. Instead, session persistence takes effect – the widget simply retains the language that the user had actively and successfully loaded directly before.
How does the free text (e.g., titles & descriptions) behave?
Scenario A: The user first loaded the widget in English and then switches to an unsupported language (e.g., Japanese) ➡️ The free text remains in English.
Scenario B: The user first loaded the widget in German and then switches to an unsupported language ➡️ The free text remains in German.
Behavior when the language parameter (lang=) is missing: Even if the lang= parameter is completely removed from the URL and the page is reloaded, the Classic Widget does not automatically revert to the vendor's default language. It continues to load in the language that was last successfully active in the user's session (e.g., if Norwegian was previously displayed, it stays in Norwegian upon reload without the parameter).
2. Floating Widget (Differentiation between UI and Content)
With the Floating Widget, the system behaves slightly differently when an unsupported language is requested, separating user interface (UI) elements from vendor-entered content:
Widget UI elements (buttons, labels, etc.): A system fallback applies here. If a language is unsupported, these elements automatically fall back to English (en-GB).
Free text / Content (experience titles, descriptions): The vendor's logic applies here. In this case, the free text falls back to the primary default language of the respective vendor (Vendor Default) (e.g., if the vendor's default language is German, the text will be displayed in German).
⚠️ Summary:
Classic Widget: "It stays what was there before." The widget remembers the user's last valid language (session values).
Floating Widget: UI elements fall back to English; free texts/content fall back to the vendor's default language.