Language mapping is one of the simplest steps in the onboarding process.
It mainly helps BeLazy understand how language variants (or sublanguages), like US English vs UK English, correspond between your customer’s system and your own.



How sublanguages work

Many common languages have regional versions — for example:

  • English: US, UK, Australian

  • Spanish: Spain, Latin America, or even custom ones like “Technical Latin American Spanish”

  • Portuguese: European and Brazilian


While these differences exist, they usually don’t require completely separate setups.
A translator who works with English (US) can usually handle English (UK) projects as well - at least on the source side



Why this matters

Language mapping saves time and effort.

Instead of recreating vendor price lists for every single language variant, you can simply link them together.

For example:

  • If your company is based in the US, your translators probably have price lists for English (United States).

  • If your customer sends you projects from the UK, you can map English (United Kingdom) to English (United States) in your system — no need to create new price lists.



How to map languages

On the right side, you’ll see the full list of languages available in your BMS.

On the left side, you’ll see the languages coming from your customer’s system or vendor portal.


Only languages that weren’t automatically matched will appear here, besides specially treated languages such as English, French, German, Spanish and Chinese - these always appear if you receive jobs with such languages.

If BeLazy finds the same language name and code on both sides (for example, “Russian” or “de-DE”), it automatically links them for you.


Your job is to manually match any remaining languages, especially sublanguages, to the right ones in your BMS.

If you don’t see the expected list of languages in Plunet, refer back to the preparation video on how to enable language listing there.