Options: How to Manage Languages in Wetu

In the Admin Panel you can select the languages that you and your team would like to be able to use when building Itineraries.

This functionality is available for all Operator Packages.
Note: Only users with admin privileges can access the Admin Panel. If you do not see this function on your Dashboard, please contact the person within your team who is in charge of your Wetu Account.

In this Article

Getting Started 
Selecting Languages 
Admin Panel Translations 
Itinerary Builder Translations

Getting Started

On your Dashboard, click on Admin and then select Options

Selecting Languages

In the Options Tab, you will see Languages. Select the languages you would like to work with by clicking on the checkboxes. Then scroll down and select Update.

Note: The Beta language options are new to our system and we are still ensuring correct translations.

Admin Panel Translations

From the Admin Panel, you are able to add translations for all the Supplier and Destination information. You will only be able to add translations for the languages you have selected in Options. 

If you have Machine Translations enabled on your account, the German, Spanish, French, Italian, Danish, Dutch, Portuguese, Swedish, Norwegian and Polish descriptions will populate automatically. Machine Translations do not apply to Beta languages.

Itinerary Builder Translations

In the Itinerary Builder, you are able to select the language of the itinerary in the Itinerary Details Step. If the language you want is missing, set it up from the Admin Panel as described above.

Note: Content that is entered by you in the Itinerary Builder, such as Day Notes and Price, will not be translated. This content will need to be translated manually by you before sending it to your client.

Pre-existing Content such as Supplier descriptions, Destinations Descriptions and Country Descriptions will automatically be translated.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us