Elbuz keeps the catalog in several languages: names, descriptions and attributes are stored per language; the storefront and website export use the right one.
When you need this:
- You launch a version in another language — it appears in translation, exports and the switcher.
- The English version shows prices in euros — the currency follows the language.
- The catalog gets a new main language — one checkbox rebuilds attribute translations, category paths and the catalog grid.
- A language isn't needed on the website now — it leaves the storefront, translations stay.
Where to start: add a language in the “Languages” window, then fill in its code and translation service language.
What the “Languages” window does
- Catalog language and interface language — are set in different places; the app interface exists in three languages.
- A new language is added as a table row and filled with bulk translation.
- Language flags decide separately whether the language is visible on the storefront and whether it goes to your website.
- Changing the main language rebuilds attribute translations, category paths and the catalog grid in one action.
- Deleting a language removes all content in that language; system languages can't be deleted.
- Rollback — switching again brings back the previous main language.
Which language is set where
In the app, two different things are called “language”: the language of the buttons and menus you see, and the language the catalog is filled in. They are set in different places and are barely connected — most questions about languages start with this confusion.
| Interface language | Catalog language | |
|---|---|---|
| What it is | the language of buttons, menus and messages in the app | the language of product, category and attribute names and descriptions |
| Where it's set | in each employee's card | in the “Languages” window |
| For whom | separately for each employee | shared by the whole account and the storefront |
| How many are available | three: Ukrainian, Russian, English | as many as you add |
You can add German to the catalog, but you can't switch the app interface to German: the app itself is translated into only three languages. If the main catalog language isn't one of those three, the interface shows the language chosen when the account was registered, or English.
What each column does
All work with languages happens in one table that you edit right in the row: click a cell, change it, leave it — it's saved. There are more columns than fit in the window, so some are visible only after you scroll horizontally. They look alike but do different things.
| Column | What it actually does |
|---|---|
| Active | the language exists in the system: it appears in translations, exports and directories |
| Main language | the source language: translations are made from it, originals are filled in it. Change it with care, see changing the main language |
| Language name | the label in the language switcher on the website |
| Language code | the technical code (ua, ru, de). While it's empty, the language effectively doesn't work anywhere |
| Site language code | what your website calls the same language (uk-ua, ru-ru). Languages are matched by this code during data exchange |
| Language prefix in URLs | a part of the page address (/ua/…). The app keeps a separate entry for it in the URL list |
| Show on site | the language is visible in the storefront switcher. Without this flag it exists, but customers can't select it |
| Export to website | the language is included in the export to your website through the tunnel |
| Translation service language | the code sent to the translation service. An empty field means the language takes no part in translations |
| Default currency code | the currency that switches on the storefront together with this language |
| Sort order | the order in the language switcher |
The most common reason for “translation doesn't work” is an empty “Translation service language”. Such a language is visible in the “Translate into other languages” window: the “Source language” and “Translation language” lists include all languages with “Active” on, regardless of this field.
But the run itself takes only languages where it's filled in. So you won't see an error: the run finishes and writes “Completed. Total: 1200, translated: 0, skipped: 1200” to the log. Zero in “translated” on a non-empty catalog almost always means this.
Cells in this table have length limits, and the app silently cuts off anything longer: “Default currency code” — 3 characters, “Language code” — 5, “Site language code” — 10, “Language prefix in SEO URLs” — 30, “Language name” — 32. If the cell holds less than you typed after saving, you hit this limit.
“Default currency code” solves a typical task of a multilingual store: Ukrainian means hryvnia, English means euro. A customer who switches the language immediately sees prices in their currency. If they later pick a currency manually, their choice is remembered and takes priority over the language.
How to add a language
- Click “Add” — a “New language” row appears. It's created empty: no code, no prefix, no translation language.
- Enter the name and the language code. Without a code, the language won't work — neither in addresses nor in data exchange.
- Fill in the prefix in SEO URLs if the language should live on separate addresses.
- Specify the translation service language — otherwise you won't be able to translate the catalog into it.
- If needed, set the currency code and the site language code.
- Turn on “Show on site” if the language should be in the storefront switcher.
A new row gets “Active” and “Export to website” already turned on — you don't need to enable them separately. Only “Show on site” comes turned off: until you tick it, the language lives inside the app and customers don't see it.
After this, the catalog in that language is still empty: products and categories get empty records for the new language, which you need to fill in — manually or with bulk translation.
The third button on the window toolbar is “Translate into other languages”: it opens the same bulk translation without leaving the language list. A convenient order is to add the language and start the translation right from here.
Translating again doesn't spoil what you wrote by hand. The translator takes only empty fields: if the name or description in the new language already has something — a translation or your own text, it doesn't matter — the field is skipped and counted as “skipped” in the log.
You can overwrite filled fields only on purpose: with the “Force translation of all values” switch in the translation window. It removes the “value already exists” check completely and translates everything again over the old text.
There's one exception — attribute values. If you correct an attribute value in the main language, the next bulk translation of attributes treats all its translations as outdated: it erases them in the other languages and translates them again, including the ones you edited by hand. This is the only place where a repeat run overwrites your edit without asking.
How to check that the language works
There's no wizard here and no final “done” message either — the language simply appears as a row in the table. You have to check it yourself, and there are four places to check.
- The table row itself. After every cell edit, “Updated” flashes at the bottom, and the window immediately re-reads the row from the database. Whatever stays in the cell after this re-read is what was saved. If the old value came back, nothing was written.
- Language lists in the “Translate into other languages” window. The language appears there as soon as it has “Active” on — both as a source and as a target.
- The translation run log. The last line looks like “Completed. Total: 1200, translated: 1180, skipped: 20”. This is the key number to check: “translated” above zero means the language really takes part in translation.
- The language switcher on the storefront. It's shown only when there are two or more languages with both “Active” and “Show on site” on: with one such language there's nothing to switch to, and the block doesn't appear on the page at all. The storefront picks the flag icon next to the name by the language code; ready-made icons exist only for the eight system codes, so a language with your own code gets a name in the switcher but no icon.
For the eight languages that come with the app — Ukrainian, Russian, English, Polish, German, French, Italian, Spanish — the “Language name”, “Language code” and “Translation service language” columns aren't saved. You can edit the cell and even see “Updated”, but the re-read row shows the old value: the app writes these three fields only for languages you added.
The other columns — both the export and display flags, “Active”, “Main language”, the prefix, the currency and site codes, the sort order — are saved normally for system languages.
You don't need to clear the after edits: saving any row in this table deletes the account's cache files, so the storefront picks up the change by itself.
How to change the main language
This is the heaviest operation in the window, so the app asks for confirmation. The dialog appears only when you mark a different language as main: edits to the sort order, prefix or other cells of the current main language row are saved without it. When you set “Main language” on another language, one action does the following:
- The attribute translation structure is rebuilt while the old language is still the main one. Attribute values in the new main language become originals, and values in the old main language become translations that now point to them.
- The “Main language” flag moves to the new language in a single step: there is never a moment when the account has no main language.
- The language in the store settings changes, and if the new main language is Ukrainian, Russian or English, so does the default admin panel language. An employee who has a language selected in their card keeps seeing the interface in their language: it takes priority over the store settings.
- Category paths are recalculated — the section names in breadcrumbs and addresses.
- The catalog is reindexed — already in the new language, so the product grid, filtered sets and filters work in it right away.
- The cache is cleared.
- Start or end
- Action or result
- Decision: the path depends on the answer
Translate attributes before switching. The value that exists in the new main language becomes the original. If a product's attribute isn't filled in that language, there's nothing to link the old value to — and it stays on its own, outside the translation structure. This is exactly what the confirmation dialog warns about.
Run bulk translation of attributes right before switching. Otherwise, a value you corrected in the main language after the last translation will move to the new main language with an old, outdated translation.
This operation isn't queued. It runs as one request while the dialog with “Migrating data...” is on screen: no background job is created, the run doesn't appear in the work log, and it has no “Stop” button.
The work isn't split into batches and there's no row limit — attributes are relinked with four database queries across the whole catalog at once, however many products it has. So switch the main language when nobody is working, and keep the window open until it finishes.
Only one language can be the main one: the flag is cleared from all the others automatically. So don't clear it by hand — just set it on the language that should become main.
If you clear the flag and don't assign another language, the app makes Russian the main language again, and this isn't a full change: attributes aren't relinked, category paths aren't recalculated, the catalog isn't reindexed. Only settings change: the store and admin panel language becomes Russian, and the cache is cleared. This is an emergency default, not a switch.
If you cleared the flag by accident and the main language wasn't Russian, just set it again on the language you need: this runs as a normal switch from Russian, and category paths and the catalog grid are recalculated.
If you switched too early or the switch broke off, see “What to do if something went wrong”.
What changes after you change the main language
Texts you wrote by hand aren't touched by the switch. Names and descriptions of products, categories and articles are stored separately for each language, and the operation doesn't rewrite any of these records.
What changes is the language that fills the base catalog: the product grid gets the name, descriptions, category name, stock status, product status, units of measure, and weight and dimension units of the main language.
The reindex started by the switch runs in the new language, so the grid moves to it right away; nothing needs to be run separately. Where there's no record in the new language, the “Name” column is empty. The text isn't lost: it waits in its own language, and the base catalog stays empty until the product is translated.
Category paths are recalculated for all languages at once. First the app erases the full name (“Parent / Child / Grandchild”) for all categories in all languages, and then rebuilds it — but only for languages with “Active” on.
For a language with “Active” off, the full name of nested categories stays empty until you turn the language on and recalculate the paths again; for top-level categories it equals their own name.
The next export to your website sends the category tree again. Recalculating paths clears the “already exported” mark on all categories, so even with the “export only changed” mode on, the next run sends all categories to the website again. This doesn't apply to products: the switch doesn't clear their “already exported” mark.
What the website decides. If multilanguage is turned off in the tunnel template, only the main language goes to the website — after the switch, the new one.
The app looks for the website language to write it into by internal ID, by “Site language code” and by matching code; if no pair is found, it takes the website language from the language rule in the tunnel's additional parameters. If Russian is selected there, for example, the Ukrainian text is written into the website's Russian language.
Changing the main language also affects things outside this window: feeds and price lists, OCFilter filter pages, an ElbuzCart website, size charts, storefront prefixes and redirects. All of this is covered, using a move from Russian to Ukrainian as an example, in Switching a store to Ukrainian: tunnel to an OpenCart website, feeds and price lists, storefront and SEO.
Attribute translations aren't treated as outdated after the switch. Exact “original — translation” pairs of the two languages that swap places are simply reversed together with the value checksums, so the next bulk translation of attributes won't rewrite them.
Old-language values without an exact pair are linked by product and attribute, only if the product's attribute has one value in the new language. With several values, the app doesn't guess: they stay outside the translation structure, and the next bulk translation of attributes adds new translations next to the old ones — remove the extras in the product card.
If the catalog has more than two languages, translations in the other languages move to the new original of the same pair and aren't treated as outdated either; the exception is translations of values left without a pair: they stay with the old value, and bulk translation adds a new one next to them.
What happens if you delete a language
Deleting a language deletes all content in that language. Product names and descriptions, category names, attribute names and values, manufacturers, articles, Q&A, SEO generator templates, units of measure and warranty units disappear — everything stored per language. This isn't “hiding a language”, it's deleting data with no recovery.
That's why deletion is restricted: system languages (the ones that come with the app) can't be deleted, the main language can't be deleted, and you can't be left with no languages at all. There are eight system languages — Ukrainian, Russian, English, Polish, German, French, Italian, Spanish — so you can delete only a language you added yourself.
If deletion fails, the window shows a red “Delete error” message, and the language stays in place with all its content. The most common reason is that the language is a system one: this happens even when it isn't the main language.
Check against the list above whether the language is one of the eight system ones. If you no longer need a language, it's almost always better to just turn off “Active” and “Show on site”: the content stays, and the language disappears from the storefront.
What happens to the storefront. A language with “Show on site” off (let alone a deleted one) disappears not only from the switcher: the storefront stops recognizing its code in the address. A visitor following an old link with this language's prefix won't reach the page: the storefront redirects them to the address with the main language prefix.
Those who switched to this language earlier go back to the main one — the language choice is stored in the customer's browser for 30 days, but works only while the language is live.
What happens to your website. The export to your website includes languages with both “Active” and “Export to website” on. Turn off either flag and Elbuz simply stops sending this language: the next export goes without it.
Elbuz never sends a “delete this language” command: the deletion queue the website uses to remove what it no longer needs includes products, categories, photos, manufacturers, attributes and reviews — languages never get there, even when language deletion is turned on in the tunnel settings.
So pages already exported to the website in this language stay there as they were; you'll have to remove them with the website's own tools.
The tunnel settings have a separate multilanguage switch. If it's off, only the main language goes to the website — and the “Export to website” flags of the other languages have no effect.
Scenarios
Launch an English version of the storefront with prices in euros
What to do: In the English row, turn on “Active” and “Show on site”, enter EUR in “Default currency code”, and in “Language prefix in SEO URLs” enter the address part, for example en. Then run “Translate into other languages”: the run includes languages with “Active” on and a filled “Translation service language”.
What you get: English appears in the storefront switcher once two or more languages have “Active” and “Show on site” on. A customer who switches to English sees prices in euros, but only if the euro is active in currencies and shown on the website. Otherwise the storefront uses the currency from their previous visit or the store's default currency.
What won't happen: the flags alone don't translate anything, and a customer who picked another currency themselves stays with it.
Add a language that isn't among the eight system ones
What to do: Click “Add”, enter “Language name”, “Language code”, “Language prefix in SEO URLs” and “Translation service language” — for your own language all four fields are saved.
What you get: the language takes part in bulk translation and, once “Show on site” is on, appears in the storefront switcher — without an icon, because the storefront looks for the image by language code.
What to watch out for: a new row gets “Active” and “Export to website” already on, so if multilanguage is on in the tunnel, the next export also sends this language to your website, even before it's translated. Don't want an empty language on the website? Turn off “Export to website” until the translation is done.
Hide a language from the storefront for a while without losing translations
What to do: Turn off only “Show on site”.
What you get: the language disappears from the switcher, and a customer who follows a link with its prefix gets the page in the main language. Translations stay in the database — only the language delete button removes them.
What won't happen: the language keeps going to your website through the tunnel — the export looks at “Active” and “Export to website”, not at this flag. To stop that too, also turn off “Export to website”. To bring the language back, tick the flag again.
Move a store from Russian as the main language to Ukrainian
What to do: First translate attributes into Ukrainian, then set “Main language” in the Ukrainian row, click “Continue” in the dialog and wait until it closes.
What you get: Ukrainian attribute values become originals, and the catalog grid switches to Ukrainian right away.
What won't happen: product names and descriptions aren't rewritten in any language. What happens to suppliers, feeds, the website and the storefront, how to prepare and check the result — see Switching a store to Ukrainian.
What to do if something went wrong
You switched the main language without translating attributes
Set the previous language as main again. Switching back does the same work in reverse: values in the restored language become originals again, and values in the language you moved to become translations pointing to them again.
Along with this, category paths are recalculated and the catalog is reindexed a second time — in the restored language, so empty names in the grid disappear right away. You can do this as many times as you like — there's no separate “rollback button”; switching again is the rollback.
Values left outside the translation structure (the attribute was filled only in the old language, or a multi-value attribute had no exact pair) are also picked up by switching back: as soon as that language is main again, its values become originals again.
But if you decide to stay on the new language, bulk translation won't link them correctly. With the new main language as “Source language”, it translates its values into the old language and adds them next to the old ones.
If you choose the old language as the source and tick “Values” in the “Attributes” block, the new main language gets translations whose original is still the old values: the structure ends up reversed, and multi-value attributes get duplicates in the new main language. So don't tick “Values” in a run with the old language as the source.
Fill in or correct the attribute in the new main language in the product card, remove extra old values, and everything continues as usual from there.
The switch broke off
If the switch broke off midway — the request was interrupted, the window closed — whatever was already done stays done: this operation has no transaction.
The account won't be left without a main language: the flag moves to the new language in a single step. A closed window or a dropped connection doesn't stop the operation on the server: it keeps running to the end. So before retrying, wait a few minutes, reopen the “Languages” window and check the “Main language” column.
- Still the old one. The break happened while attributes were being moved. Set the new language as main again: the move runs again, and values already relinked won't get mixed up.
- Already the new one. Attributes were moved, but category paths and reindexing may not have run, and switching again to the same language won't start them. First save the new main language's row: change its “Sort order” and put the previous value back — every save of the main language row rewrites the language in the store settings. Then open the “System functions” window and in the “Reindex records” section click “Base catalog categories”, then “Base catalog products”.
Switching again to a language that's already main is safe: the “old — new” pair matches, the dialog doesn't appear, the move doesn't start, and the app only rewrites the language row and the language in the store settings and clears the cache.
You deleted a language with its content
There's no recovery — neither with a button nor through support: description rows are deleted from the database, not hidden. The only way is to add the language again and fill it again with bulk translation from the main language.
Two things won't come back. Attribute values in the deleted language physically remain in the database but are tied to the language's old internal number, while the new language gets a new one, so they can't be reached. And the app doesn't remove the deleted language's rows from the SEO URL table: they stay until someone removes them by hand.
| What you see | Why | What to do |
|---|---|---|
| The language isn't in the switcher on the website | “Show on site” or “Active” is off | turn on both flags |
| Translation finished with “translated: 0” | “Translation service language” is empty — for the source or the target | enter the translation language code in the language row and run it again |
| Language pages open without a prefix | “Language prefix in SEO URLs” isn't filled in | fill in the prefix; the app creates the address entry itself |
| Prices don't switch with the language | “Default currency code” isn't set | enter the currency code in the language row |
| Wrong currency even though the code is set | the customer once picked a currency manually — their choice was remembered | this is by design; a manual choice takes priority over the language |
| The language doesn't reach the website during export | “Export to website” is off | turn on the flag in the language row |
| Website orders arrive in the wrong language | “Site language code” doesn't match | enter the code the way your website names it |
| After changing the main language, attributes “fell apart” | values in the new language weren't filled in before the switch | set the previous language as main again — the links are restored (fix) |
| After changing the main language, product names in the base catalog are empty | these products have no name in the new main language | translate the products or set the previous language as main again |
| After changing the main language, the catalog grid stayed in the old language | the switch broke off after the flag moved to the new language, and reindexing didn't run | save the main language row, then “System functions” → “Reindex records”: “Base catalog categories”, then “Base catalog products” |
| The switch broke off and the old language is still main | the break happened while attributes were being moved | wait a few minutes and check the “Main language” column again; if it's still the old one, set the new language as main again (fix) |
| After bulk translation, a product attribute has duplicate values in the old language | a multi-value attribute had no exact pair, and the old values stayed outside the translation structure | remove the extra old values in the product card |
| An edit in a system language row isn't saved | “Language name”, “Language code” and “Translation service language” are saved only for languages you added | these three fields don't change for system languages; the other columns work |
| The value in the cell is shorter than what you typed | you hit the field length limit | stay within the limit: language code — 5 characters, currency code — 3, prefix — 30 |
| The language was turned off, but its pages are still on the website | Elbuz stops exporting but doesn't ask to delete what's already exported | remove the pages with the website's own tools |
| The interface stayed in the old language | the admin panel language comes from the employee card | change the language in your user card |
| “Delete error” when deleting a language | it's a system language, the main language, or the only language in the account | turn off “Active” instead of deleting; to remove the main one, first make another language main |
| The new language does nothing | “Language code” is empty | enter the code |
FAQ
Can I switch the app interface to German?
No. The app itself is translated into three languages — Ukrainian, Russian and English. The catalog can be in any number of languages.
I'm deleting a language and the app says “Delete error”, even though the language isn't main. Why?
Only languages you added yourself can be deleted. The eight languages that come with the app are system languages: they can't be deleted, even if they aren't main. Turn such a language off instead — clear “Active” and “Show on site” (deletion).
What disappears if I delete a language?
All content in that language: product names and descriptions, categories, attributes and their values, manufacturers, articles, Q&A, SEO generator templates. It can't be restored. System and main languages can't be deleted at all.
How do I remove a language from the website without losing translations?
Clear the “Show on site” flag. The content stays in place, and customers won't see the language. If you don't need the language inside the app either, also clear “Active”.
Why does translation finish but the language stays empty?
The language row has an empty “Translation service language” — either the language you translate from or the one you translate into. The run finishes with “translated: 0”. Enter the translation language code and run it again (columns).
Can I roll back a main language change?
There's no separate button, but switching again is the rollback: set the previous language as main, and the app relinks attributes in reverse, recalculates category paths and reindexes the catalog (fix).
What happens if the main language switch breaks off?
Whatever was done stays done, but the account won't be left without a main language. Wait a few minutes and check the “Main language” column: what to do in each case is in “The switch broke off”.
How do I make the English version show prices in euros?
Enter the currency code in the “Default currency code” column of the English row. A customer who switches the language sees prices in this currency until they pick another one manually.
Where to find it and who has access
- Menu
- Directories → Languages
- Interface language
- the employee card in the users directory — each person has their own
- Language currency
- a currency code from the currencies directory
- Access right
- the “Languages” window
1
Main language column2
Add button- Main language — the checkbox marks the primary language of the store; changing it rebuilds translations and re-indexes the catalog.
- Add — creates a new language row in the grid.
Related topics
- If the language is added and you need to fill the catalog in it — Bulk translation.
- If you're moving from Russian as the main language to Ukrainian — Switching a store to Ukrainian: suppliers, feeds, the website and the storefront.
- If an employee needs a different interface language — Users.
- If the language has separate addresses on the storefront — SEO URLs.
- If the language should go to your website — Export to website.
