Setting up Bitrix24 interface localization

Our company is engaged in the development, support and maintenance of Bitrix and Bitrix24 solutions of any complexity. From simple one-page sites to complex online stores, CRM systems with 1C and telephony integration. The experience of developers is confirmed by certificates from the vendor.
Our competencies:
Development stages

Setting up Bitrix24 Interface Localization

The company translated the portal to English, but half of the CRM stages still display in Russian. Date format is Russian, thousands separator in amounts is a space instead of a comma, and automatic emails to clients arrive with corrupted encoding. Standard language switching changes only the system interface. Everything else — stages, fields, notifications, formats — needs manual localization.

System Language Settings

B24 Cloud uses language packs that switch at the user level. An administrator manages:

  • Portal default language — applied to new users and system notifications.
  • Available languages — list of languages users can select in their profile.
  • Notification language — language for system push notifications and emails from the portal.

For B24 On-Premise (self-hosted), you can edit language files — full translation customization at the source code level.

Localizing CRM Stages and Dictionaries

System dictionaries — deal stages, lead stages, contact types, sources — are created in one language. On language switch, they are not translated. Localization:

Element Localization Method
Deal funnel stages Manual rename via REST API crm.status.update or UI. For multilingual — middleware wrapper with substitution
Contact types Same as stages
Lead sources Dictionary crm.lead.source.list
Custom fields B24 supports multilingual names for custom fields: EDIT_FORM_LABEL, LIST_COLUMN_LABEL with language suffix

For custom fields, when created via API, you can specify names in multiple languages:

EDIT_FORM_LABEL[ru] = "Region"
EDIT_FORM_LABEL[en] = "Region"
EDIT_FORM_LABEL[de] = "Region"
LIST_COLUMN_LABEL[ru] = "Region"
LIST_COLUMN_LABEL[en] = "Region"

User sees field name in their interface language.

Date, Number, and Currency Formats

B24 pulls formats from the user's language settings, but not always correctly — especially for custom fields and generated documents. Configure:

Parameter RU Format EN Format DE Format
Date DD.MM.YYYY MM/DD/YYYY DD.MM.YYYY
Time 24-hour 12-hour (AM/PM) 24-hour
Number 1 000 000,50 1,000,000.50 1.000.000,50
Currency 100 000 ₽ $100,000 100.000 €

For document generator — format is set in template. Middleware or business process substitutes values in correct format based on client language (field UF_LANGUAGE).

Custom Translations for On-Premise

On the self-hosted version, language files are in /bitrix/modules/*/lang/. Structure:

/bitrix/modules/crm/lang/ru/
/bitrix/modules/crm/lang/en/
/bitrix/modules/crm/lang/de/

Each file contains $MESS array with keys and translations. For customization:

  1. Find the key of the needed phrase via developer tools (displayed in HTML as data-bx-msg or in JS variables).
  2. Create an override file in /bitrix/php_interface/user_lang/ or via module customization mechanism.
  3. Specify your translation for the needed key.

This approach lets you rename any interface element: buttons, headers, hints, error messages.

Localizing Business Processes

Names of stages, buttons, and notifications in business processes are set on creation. For a multilingual portal:

  • Stage names — use neutral designations or dual language: "Approval / Согласование".
  • Notification texts — business process checks recipient language and sends text in their language. Implemented via condition (if/else) on user language field.
  • Forms — for universal business process forms, field names are set in portal language. Customization — via form parameters.

Timezones

A related setting: in international teams, employees work in different timezones. B24 supports:

  • Portal timezone (default).
  • User timezone (in profile).
  • Time display in tasks, calendars, and CRM — in the viewing user's timezone.

Administrator sets portal timezone, each user sets their own. Task deadlines, calendar events, and CRM timestamps automatically convert.

What We Implement

  • Language interface and format setup
  • Localization of CRM stages, dictionaries, and custom fields
  • Correct date, number, and currency formats for each locale
  • Custom interface translations (for On-Premise)
  • Multilingual business process and notification logic
  • Timezone configuration for international teams