Languages: Bosnian, Croatian, Serbian and English
Commerce Assistant Free supports Bosnian (BS), Croatian (HR), Serbian (SR) and English (EN) in its built-in Setup Wizard/Audit catalogues and Basic PDF text. These application settings are separate from WordPress’s general site/user language and from any WordPress.org community-translated language packs.
Admin language
In Leanmerce → Commerce Assistant → Setup → Step 1, choose the admin language. The wizard, Audit presentation and related Commerce Assistant navigation use their own selected-language catalogues. The selection does not change the language of WooCommerce, the WordPress dashboard, your theme or other plugins.
An authorized administrator can revisit the language step later. Check labels and critical messages in the chosen language after saving.
Default document language
Step 1 also has an expanded language area where you select a default document language and an allowed set of customer/document languages. At least one language must be enabled. Step 6 uses this set when offering Basic PDF sample previews.
Important limitation: the default Free PDF language resolver reads the saved default document language. It does not inspect each customer’s locale and automatically translate their order into that language. Enabling all four languages makes them eligible for configuration and previews; it does not enable an automatic per-buyer switch.
For example, if your default document language is Bosnian and the customer browses WooCommerce in English, the Free Basic PDF will ordinarily still use Bosnian. Do not promise an English PDF unless your actual installed integration explicitly supports that order-language choice.
My Account and generic WordPress strings
The WooCommerce My Account document area and generic WordPress notices use standard WordPress gettext/locales. As a result, their translation may depend on installed language packs and the WordPress/customer locale rather than the plugin’s admin-language selection.
The Free package includes a translatable POT source and the plugin’s built-in application catalogues. A POT file alone is not proof that a compiled public MO language pack is installed for every WordPress locale. If a customer-visible string remains in English while the wizard is Bosnian, that distinction may explain the behavior.
Legal coverage is not created by translation
Changing the language does not switch the included ruleset to Croatia, Serbia or another country. The current substantive legal scope remains Bosnia and Herzegovina, with local BiH differences as implemented. English here is a UI/document language, not an additional country’s legal framework.
Verify your setup
Preview at least one Basic PDF in an enabled language, confirm characters such as Č, Ć, Đ, Š, Ž, and inspect the actual order’s default PDF. If the site uses a custom translation or customer-language integration, test that separately.
Related guides: Seven-step setup, Configure Basic PDF, Legal scope.