Switching your store to Ukrainian in Elbuz takes one checkbox: Ukrainian replaces Russian as the main language, and the grid, feeds and everything new without a set language turn Ukrainian. Existing texts stay put.
When you need this:
- The catalog is in Russian, the website must be Ukrainian — statistics show what's left.
- Suppliers send price lists in Russian — the price list language keeps their texts out of the Ukrainian fields.
- Rozetka and Prom feeds must be Ukrainian — templates without a language switch on their own.
- You switched too early — switching again makes Russian main once more.
Where to start: check how much is still untranslated.
What the switch changes
- The base catalog grid becomes Ukrainian right away — names, descriptions, categories, units of measurement.
- Price lists, imports and parsers with no explicit language write texts into the Ukrainian fields.
- Feeds and price lists for customers with no language selected go out in Ukrainian.
- A website connected through a tunnel without multilingual mode receives Ukrainian.
- The Elbuz storefront shows Ukrainian to visitors who haven't chosen a language.
The main language is the language Elbuz uses to fill the base catalog, to store everything that arrives without an explicit language, and to translate from by default. Texts in each language are stored separately, so the switch doesn't overwrite any text you've already written. What changes is where Elbuz takes text from and where it writes new text.
| What | Before (Russian is main) | After (Ukrainian is main) |
|---|---|---|
| Base catalog grid: name, descriptions, category | in Russian | in Ukrainian right after the switch; where there's no Ukrainian name, the column is empty |
| New products from a price list with the language set to “---” and from the general “Updating base catalog” run | texts are written into Russian | texts are written into Ukrainian, whatever the language of the price list |
| with no language selected in “Write into language”, 1C, without Ukrainian fields, marketplaces | write into Russian | write into Ukrainian |
| YML, Rozetka, Prom and Google export templates and price lists for customers with no specific language selected in the “Language ID” field; Prom XLS | in Russian | in Ukrainian; the {name_ua} macro becomes empty |
| Export templates with a language explicitly selected | in the selected language | no change |
| Tunnel to a website without multilingual mode | sends Russian | sends Ukrainian — into whichever website language it matches |
| Elbuz storefront for a visitor who hasn't chosen a language | Russian | Ukrainian; addresses without a prefix may redirect to /ua/… |
| Batch translation, source language in the window | the language auto-translation was saved with; if it was never saved, Russian | the language auto-translation was saved with; if it was never saved, Ukrainian |
| New documents, AI consultant | in Russian | in Ukrainian |
How the “Languages” window works — its columns, checkboxes and rollback — is described in How to add a catalog language and change the main one.
How to check that the catalog is ready
The key condition for the move: everything currently filled in Russian must also be filled in Ukrainian. Otherwise, after the switch, gaps will appear in the catalog grid, in feeds and on the website.
To see how much is untranslated, open the “Translate into other languages” window, the “Statistics” tab. Statistics load as soon as you open the tab; to refresh them, click the icon with the “Get statistics” tooltip.
The “Translation coverage” section has “Categories”, “Products”, “Manufacturers”, “Attributes” and “Articles” blocks: rows are fields, columns are languages. Red numbers show how many records in each language are still empty compared to the main language. While Russian is the main language, the red numbers in the Ukrainian column are your workload.
1
Get statistics button2
“Categories” block- Get statistics — recalculates how many records are filled in each language; it only counts and changes nothing.
- The “Categories” block shows the number of filled records per field, next to the “Products” block.
Statistics count non-empty fields, not translations. They miss two things. First, text copied into a Ukrainian field without translation: a Russian name in the Ukrainian language counts as filled. You can spot such names only in the product card, on the Ukrainian tab. Second, manufacturer names: they don't depend on language and don't need translating.
Separately check what statistics show incompletely:
- Categories, including top-level and disabled ones. A category without a Ukrainian name becomes a nameless node in the tree after the switch. If a top level has an empty name, it drops out of the full category name: the path “Root / Catalog / Laptops” turns into “Laptops” for every product in that branch. This full name goes into the “Category” column, into exports and to the website.
- Attribute values. For the main language, statistics count only the original values; for other languages, all non-empty ones. So the most reliable check is a few products with many attributes, opened in the card on the Ukrainian tab.
- Directories. Units of measurement, weight and length units, stock statuses, product work statuses: without a Ukrainian record, the grid columns with the unit of measurement name, weight unit, length unit and product work status become empty, and the stock status stays in Russian. The unit of measurement code column doesn't depend on language.
- SEO fields. The “Content coverage stats” tab of the “Text generator” window counts only the main language: the cards show the fill percentage, and the “Empty” count is in the tooltip above the percentage. Before the switch it shows gaps in Russian, so for Ukrainian it's handy only after the switch.
The base catalog grid has no “translated” column or filter, and you can't choose the grid language there: the grid always shows one language — the main one.
What to do before the switch
The order matters: translate while Russian is still the main language. At the moment of the switch, attribute values are relinked only where a Ukrainian pair already exists.
Before switching the main language
Each item is covered below, in the section on the matching data flow. Translation itself is a paid operation of the translation service; how it's billed and where to see the log is described in Batch translation.
A repeated run doesn't touch fields that are already filled, so you can translate in parts. The exception is the “Force translation of all values” switch: when it's on, the run translates again and overwrites filled fields, including manual edits, and each such translation is paid for.
A Ukrainian value translated in Elbuz from Russian remembers its original, and at the switch such a pair is simply reversed.
A value that got into Ukrainian another way (typed in by hand, imported) has no pair. Elbuz links its Russian value by product and attribute only when that product's attribute has a single Ukrainian value.
Attributes with several values (several colors, a list of compatible models) without a pair stay outside the translation structure, and the next Ukrainian-to-Russian translation adds a second set of Russian values next to the old ones. If you have such attributes, translate them from Russian in Elbuz before the switch, or check a few products on the Russian tab afterwards.
How to switch the main language
In the “Languages” window, tick “Main language” in the Ukrainian row. The “Changing the main language” dialog appears; after “Continue” you'll see “Migrating data...”. The order of steps, rollback and what happens if the operation breaks off are covered in How to change the main language; in short:
- Attribute values are relinked: Ukrainian values become originals, Russian ones become their translations. Pairs translated in Elbuz are reversed exactly; other Russian values are linked by product and attribute if that attribute has a single Ukrainian value (see before the switch).
- The main-language flag moves from Russian to Ukrainian in one step, and Ukrainian becomes the store language in the settings.
- Full category names are recalculated in all active languages, and the “Exported” flag is cleared on all categories.
- The base catalog is reindexed — now in Ukrainian.
- The is cleared.
So right after the switch the catalog grid is in Ukrainian: name, descriptions, the “Category” column, units of measurement. You don't need to run reindexing separately. Where there's no Ukrainian name, the cell is empty.
The operation runs as a single request, without a background job; wait until the dialog closes. Closing the window doesn't stop it on the server. If it breaks off, there's still exactly one main language — Russian or already Ukrainian; what to do in each case is described in “The switch broke off”.
The interface language doesn't change for everyone. If an employee's card has a language set, their interface stays in that language.
Along with the interface, the article lists and the candidate names shown by AI matching of a price list to the catalog stay in that language; the matching itself doesn't depend on the interface language. The interface language is a personal setting in the user card.
What happens to suppliers and imports
There's one rule for all incoming flows: whatever arrives without an explicitly set language is written into the Ukrainian fields after the switch, whatever language the text is in.
Supplier price lists
In the price list card, in the “Products” section, “New products” group, there's a “Link products to language” field. The value “---” means “main language”. After the switch, such a price list writes the names, descriptions and attribute values of new products into Ukrainian.
Leave price lists with Ukrainian texts at “---”. If a price list is in Russian, set it to “Русский” before the switch: then a new product gets texts only in Russian and has no Ukrainian record at all. It still needs translating — and before the “Database integrity check” runs (see below).
1
Link products to language- Link products to language — “---” means the main language; choose a language here so products from this price list are loaded in it.
What this setting doesn't cover:
- The general “Updating base catalog” run. The price list language is respected only by a catalog update from a single price list — the “Update my catalog” button in the selected price list. The general run across all price lists — from the price lists window menu, right after all price lists are imported, or on schedule — uses the main language. In it, names and descriptions of new products, attribute values and, if enabled, text field updates of existing products are written into Ukrainian, even if the price list is set to “Русский”.
- Categories from a price list are always created with the supplier's name in the main language. After the switch, the supplier's Russian category names end up in the Ukrainian fields.
- Matching by name compares the name from the price list with the name in the main language. For a Russian-language supplier these matches disappear, the product looks new — and “Add new products to catalog” can create a duplicate. Links made by hand or by a price list row match don't depend on the switch. The candidate search in AI matching also uses names from the grid, so there will be fewer candidates for Russian names.
- Attributes. A price list looks up an existing attribute by name in the price list language, and with “---” and in the general run — in Ukrainian. A Russian name is still found only for attributes the price list itself once created. Attributes created by hand or by import won't be found by their Russian name anymore, and the price list creates a duplicate — a new attribute with a Russian name in the Ukrainian language. With “Русский”, new attributes are created with a Russian name in the Russian language.
How to finish products from a price list set to “Русский”. Translate them from Russian: in “Translate into other languages”, set “Source language” to “Русский”, or keep that language in the auto-translation schedule.
Translation fills only empty fields, so the order is decisive.
If the “Database integrity check” ran first, it already created a Ukrainian record with the supplier's text, which translation skips. Then, in that window, turn on “Force translation of all values” and enter a “Product ID” or “Category ID” in “Test on a single record”. This overwrites all Ukrainian texts in the selection, manual edits included, and is billed as new.
Import into the base catalog
Import templates have no language choice. What happens after the switch:
| Source | Where it writes texts |
|---|---|
YML with name_ua / description_ua fields | splits explicitly into Russian and Ukrainian, doesn't depend on the main language |
| YML without Ukrainian fields | into the main language, i.e. Ukrainian; on update, overwrites Ukrainian names and descriptions with text from the file |
| CommerceML (1C) | into the main language; names and descriptions of existing products are overwritten on every run |
| Prom.ua XLS | takes the Ukrainian columns, and where they're empty — the Russian ones; the Russian columns themselves are no longer imported into the Russian language |
| Universal import, Allegro, eBay, Amazon, Etsy, OLX, Shopify, WooCommerce and other marketplaces | into the main language |
| Rozetka | requests content in the main language, i.e. Ukrainian, and writes into the main language — consistently |
| Horoshop | explicitly into Russian and Ukrainian, doesn't depend on the main language |
| Import from a website through the tunnel | by the website's language code; anything unrecognized goes into the main language |
| API | into the language from the language_id parameter, without it — into the main language |
If 1C, YML without Ukrainian fields or a marketplace sends Russian text, after the switch it overwrites the Ukrainian names on every run.
Import templates have no separate “don't update names and descriptions” setting. Options: mark the products “Do not update” in the card (YML, CommerceML and Prom.ua XLS imports respect this flag), or agree with the YML supplier on name_ua fields.
Order, payment and delivery statuses from marketplaces are matched by a code map that doesn't depend on language. But Elbuz takes the status name for the document from the directory in the main language, so without a Ukrainian record the status is set with an empty name — fill these directories in Ukrainian.
The “Database integrity check” looks for products without a main-language record and creates one with the name and descriptions from the price list, or, if there's no price list row, with the name from the grid. It also fills empty main-language names with the name from the price list.
It runs from a button in “System functions”, and also on its own — after a template import in some formats and after cleaning up empty or deleting unused attributes.
After the switch, a product with an empty Ukrainian name or no Ukrainian record (such as a new product from a price list set to “Русский”) gets the supplier's Russian text in its Ukrainian fields, and batch translation skips it as filled. Fill empty Ukrainian names beforehand; translate new products from Russian price lists at once (see price lists).
Parsers, translation, generators
- The site parser writes the name, short and full description into the language from the “Write into language” field in the parser window, and if no language is selected — into the main one, i.e. Ukrainian after the switch. Attributes always go into the main language. Auto-completion after price list processing uses the same parser window settings: texts go into “Write into language”, attributes into the main language. For a Russian-language source site, set “Write into language” to “Русский” and translate what's found from Russian; attributes from such a source still end up in Ukrainian, so for them it's better to use the Ukrainian version of the site.
- Batch translation puts into “Source language” the language auto-translation was saved with; if it was never saved — the main one, i.e. Ukrainian after the switch. You can still translate from Russian: set “Source language” to “Русский”. Auto-translation — on schedule and after a catalog update — remembers the source language it was saved with and keeps translating from it until you open the window, choose the source language and save the settings again with “Save for auto-translation” or the schedule button. Which language to keep there depends on where your suppliers write (see the bilingual store scenario).
- The “Text generator”, in its window and in bulk runs, generates only in the main language and takes prompts from that language's row. Generating a single field from the product card writes into the language of the open tab. After the switch, the Ukrainian prompts are used: if auto-prompt is off, fill them in beforehand.
- The SEO URL generator builds the address from the name in the main language and transliterates it. With “Update only empty fields” turned off, the “Update URL in base catalog” button rewrites all addresses with transliterations of the Ukrainian names, and Elbuz doesn't create redirects from the old addresses on its own.
What happens to your website and feeds
Tunnel to an OpenCart website
The key setting is the “Languages” checkbox in “What to export” (the “Select data to export” card) of the tunnel template — multilingual mode. If it's on, every language with “Export to website” goes out into its own website language, and the switch swaps nothing. If it's off, only the main language goes out — Ukrainian after the switch.
1
Languages chip- Languages is on — each language is exported into its own site language.
Elbuz matches an Elbuz language to a website language in turn: by internal ID, by the “Site language code” field, by matching code (ua finds uk-ua).
When multilingual mode is off and no match is found, the main language gets the website language selected in the language rule under “Additional settings” of the tunnel template. If there's no such rule, descriptions of new products and categories aren't written to the website.
- Start or end
- Action or result
- Decision: the path depends on the answer
What else changes on the website:
- Categories are exported again. The switch clears the “Exported” flag on all categories, so even with “Only export new data” turned on, the next run sends the whole tree.
- Products aren't exported again: the switch doesn't clear their “Exported” flag. With multilingual mode on, this changes nothing — texts in each language are stored separately and didn't change with the switch. With multilingual mode off and “Only export new data” on, Ukrainian texts reach the website only with new and changed products; other products stay on the website as they were. To send all of them, run the export with “Only export new data” turned off.
- SEO addresses on the website don't change. On OpenCart the tunnel writes an address only for products and categories that don't have one on the website yet. On ElbuzCart it rewrites addresses on every run, but takes them from Elbuz, and there the switch doesn't change addresses.
- OCFilter. The filter value ID is calculated from the value text in the main language. After the switch all IDs are recalculated from the Ukrainian values, and with them the addresses of filter pages change — landing pages, bookmarked ones, indexed ones. With “Only export new data” on, value links are rebuilt only for changed products.
- Size charts go out only in the main language, even with multilingual mode on. A size chart without a Ukrainian description won't go to the website after the switch.
- The website's own main language doesn't change on regular OpenCart. The exception is a website on ElbuzCart: after the very first export, Ukrainian becomes its main language.
- WooCommerce has no language versions, and the product name is updated on every export by default: in the “Export fields” window of the tunnel template, the name row is set to “Update”. After the switch, the names of existing products are overwritten with Ukrainian ones — at once when you export all products, and with “Only export new data” — as products change. Descriptions aren't updated by default and stay in Russian. To keep the Russian names, clear “Update” in the name row before the first export after the switch.
Feeds and price lists for customers
A feed's fate is decided by the “Language ID” field in its template, found in YML templates (including Rozetka, Prom , Hotline, Epicentr, Kasta), Google Merchant, customer price lists, the OpenAI feed and CommerceML2. Check each active template:
- “Default catalog language” (in YML and Google) or “...” (in the price list and CommerceML2) — the template follows the main language and will go out in Ukrainian after the switch.
- A specific language, such as “Русский” — the template doesn't change with the switch: texts, macros and filter rules stay in that language. If the marketplace expects Ukrainian, select “Український” (Ukrainian).
- Prom XLS and API exports don't have this field: everything in them not explicitly tied to a language is taken in the main language.
The main trap in templates that follow the main language is language macros. {name_ua}, {description_full_ua}, {name_ru} are filled for all active languages except the template language; the macro of the template language is cut out as empty.
In a template with no language selected, the template language is the main one. After the switch, in such a template <name>{name}</name><name_ua>{name_ua}</name_ua> the first tag becomes Ukrainian, the second empty, and {name_ru} starts being filled. The same goes for attributes in the form {Атрибут: Назва_ua}. Rewrite such templates before the switch: Ukrainian — {name}, Russian — {name_ru}.
- Filter rules based on attribute values compare values in the template language, and in Prom XLS and API exports — in the main language. In a template with no language selected, the rule “Color = Красный” (Russian for “red”) will be compared with the Ukrainian value after the switch and silently change the feed's contents. Enter the values in such rules in Ukrainian.
- Prom XLS: the group columns
Название_группыandНазва_групи_укрboth become Ukrainian, and no Russian group names remain in the file.Название_позиции_укрin the default template is a custom product field, not a translation. - The default Epicentr template marks the name and description as Ukrainian. If the template has no language selected, Russian text went there before the switch, and Ukrainian — the correct one — after it.
- Rozetka via API updates only price and stock and doesn't send names: product pages on Rozetka don't change with the switch, content goes through the feed.
- Horoshop and other API exports: a “name” field mapped to a field without a language sends the Ukrainian name after the switch. Separate fields for Russian and Ukrainian take their own language regardless of the main one.
What happens to the storefront, documents and search
Storefront and SEO
This section is about the Elbuz storefront. It determines the visitor's language like this: a language prefix in the address beats everything; without a prefix — the saved choice, a parameter in the address, the browser language — and only then the main language. The switch changes only the last link, and that leads to the following.
- The saved choice lasts 30 days. Visitors who've already been to the website keep seeing Russian until they switch the language or this period runs out.
- Ukrainian browsers without Russian in their language list start seeing Ukrainian. The storefront, which uses the code
ua, doesn't recognize the browser language codeuk, so such visitors always got the main language — Russian before, Ukrainian now. The storefront goes through the browser's whole language list, so a browser with Russian after Ukrainian is recognized by Russian and shown Russian — both before and after the switch. A Russian browser is likewise recognized on an address without a prefix and keeps getting Russian. - Language prefixes don't change. Usually Russian has an empty prefix and Ukrainian has
ua. After the switch, a search bot without a saved choice on the old address/productgets the main language, which has a prefix, and the storefront responds with a 302 redirect to/ua/product. For search engines, the Russian pages turn into temporary redirects. - hreflang. On the home page, the storefront points the main language and
x-defaultto the site root, and with theuaprefix the root redirects to/ua. On inner pages, the alternate for Russian is the address without a prefix, which after the switch answers a visitor without a saved choice with a 302 redirect to/ua/…. The markup and the way addresses behave no longer agree. - The sitemap doesn't depend on the main language: an address without a prefix plus alternates for each language with its prefix.
The consistent option is to change the prefixes together with the main language: remove Ukrainian's prefix and give Russian ru, in the “Language prefix in SEO URLs” column of the “Languages” window. The other option is to leave everything as is, knowingly accepting 302 redirects.
If you remove Ukrainian's prefix, the storefront code returns a “not found” page (404) for old /ua/… addresses: it looks for the ua segment among addresses and doesn't find it. The storefront checks “URL redirect” rules earlier, so set them up for the old addresses before changing the prefixes.
Elbuz doesn't create permanent 301 redirects from old addresses on its own; you set them by hand in “URL redirect” in the “SEO URL generator” window. How prefixes and addresses work is described in SEO URLs.
Documents, AI consultant, search
- Documents. A new document gets the main language — Ukrainian. The product name in a document line is a snapshot taken when it was added, so old documents don't change and print as before. To add a product to a document, it must have a main-language record: without a Ukrainian record Elbuz responds “Item not found”, and with an empty Ukrainian name the line is added without a name. Printing uses the template variant in the document language if it's filled in.
- The AI consultant searches and shows products, categories and the catalog in the main language. A product without a Ukrainian name doesn't exist for search by name.
- Smart search indexes all active languages, so Ukrainian texts were in the index before the switch too. Search understands Ukrainian morphology just as it does Russian and English: it reduces different case forms of a word to a common stem, so “чохла” (“case”, genitive) finds “чохол” (“case”).
How to check the result
- The “Name” column in the catalog grid is in Ukrainian for all products; empty cells are products without a Ukrainian name. If some names are in Russian, open such a product on the Ukrainian tab: most often the Russian text is right there. If there's a Ukrainian name there, the reindexing at the switch didn't complete — see “The switch broke off”.
- The category tree has no nameless nodes, and the “Category” column shows the path you expected.
- In the “Text generator”, on the “Content coverage stats” tab, percentages are now counted for Ukrainian: the shortfall is the remaining work on SEO fields.
- Open the file of every active feed: each goes out in the language you intended for it, and where you put
{name_ru}— in Russian, with no empty tags. - After the next tunnel export, open the website in both languages, a filter page and a product with a size chart.
- After the next price list processing, open the card of a new product from a Russian-language price list: the Russian text is on the Russian tab, and the Ukrainian tab has a translation, not the supplier's text.
- Open an old storefront address in a window with no saved language choice and see which language and which address it returns.
Scenarios
- The store will be Ukrainian onlyRussian is no longer updated and isn't needed on the website
- Bilingual storeRussian stays as a second language and must be kept up to date
- OpenCart website with a tunnelTexts go to your website through the tunnel
- Sales only through feeds and marketplacesNo website; the catalog goes to Rozetka, Prom, Epicentr
The store will be Ukrainian only
Translate the catalog and switch the main language. Still set Russian-language price lists to “Русский” in “Link products to language”: that way the supplier's text doesn't get into the Ukrainian fields, and you translate names and descriptions of new products in “Translate into other languages” with “Source language” set to “Русский”.
Update the catalog from such price lists with the “Update my catalog” button and translate new products before the “Database integrity check” runs (see price lists).
Check the attribute values of new products from such price lists separately: after the switch they have no Ukrainian pair, and translation from Russian links them the other way round — the Russian value becomes the original. To hide Russian from the storefront, clear its “Show on site” (see Languages).
Bilingual store
Russian-language price lists — set to “Русский”, Ukrainian-language ones — to “---”.
Keep the auto-translation schedule with source language “Русский” if most new texts arrive in Russian: it will keep translating only empty fields from Russian into Ukrainian. If new texts arrive mostly in Ukrainian, save the schedule again with the source “Український”.
On the storefront, settle the prefix question. In feed templates with no language selected, replace {name_ua} with {name} and add {name_ru} wherever the marketplace expects Russian; a feed that must stay fully Russian is easier to set to “Русский” in the “Language ID” field.
OpenCart website with a tunnel
With the “Languages” checkbox on, texts on the website don't swap, and the website's main language stays what it was. Check three things: size charts have a Ukrainian description, OCFilter filter pages change their addresses after the first export, and the category tree is exported in full.
With the checkbox off, make sure the website has a Ukrainian language and its code matches the “Site language code” in the Ukrainian row.
Otherwise the Ukrainian text goes into the website language selected in the tunnel's language rule — if that's Russian, into Russian — and without a rule, descriptions of new products and categories aren't written to the website. A website on ElbuzCart becomes Ukrainian by default on its own after the first export.
Sales only through feeds and marketplaces
Open each template and check the “Language ID” field. Templates with no language selected, as well as Prom XLS, go out in Ukrainian after the switch with no extra setup; templates with a selected language stay in it — if it's “Русский” and the marketplace expects Ukrainian, select “Український”.
In templates that follow the main language, check the _ua} and _ru} macros and the filter rules based on attribute values, and in Prom XLS — the group columns. Prices and stock on Rozetka via API don't depend on the switch.
What to do if you've already switched
Put things back as they were
Set “Main language” to Russian again: switching back does the same work in reverse, and the grid returns to Russian right away. There's no separate rollback button; switching again is the rollback (how rollback works).
The switch broke off
A closed window or lost connection doesn't stop the operation on the server. Wait a few minutes, reopen the “Languages” window and check the “Main language” column: still on Russian — set it to Ukrainian again; already on Ukrainian — save the Ukrainian row and run “Base catalog categories” and “Base catalog products” in “System functions” → “Reindex records”.
Step by step — in “The switch broke off”. Do the same if some names in the grid are in Russian while these products have a Ukrainian name on the Ukrainian tab.
Stay on Ukrainian and finish the job
You can still translate names and descriptions now: in “Translate into other languages”, set “Source language” to “Русский”. Translated names appear in the grid on their own; you don't need to run reindexing separately.
In the “Attributes” block, don't tick “Values” for this run: Russian values without a pair would be translated into Ukrainian as translations of the Russian ones, and attributes with several values would get duplicates, now in Ukrainian. Attribute values filled only in Russian have stayed outside the translation structure; fill them in Ukrainian in the product card.
| What you see | Why | What to do |
|---|---|---|
| Empty “Name” in the base catalog grid | The product has no Ukrainian name | Translate names with “Source language” set to “Русский”, without ticking “Values” in the “Attributes” block; the names appear in the grid on their own (finish the translation) |
| Some names in the grid are in Russian, some in Ukrainian | Most often these products have Russian text on the Ukrainian tab — copied, from a price list or from the “Database integrity check”. Less often the reindexing at the switch didn't complete, and products move to Ukrainian one by one — when the card is saved, a price list is processed or an import runs | Open such a product on the Ukrainian tab. Russian text — translate or fix it (below); a Ukrainian name — run “Base catalog categories” and “Base catalog products” in “Reindex records” (the switch broke off) |
| On the Russian tab, a product has two sets of values for one attribute | The attribute has several Ukrainian values without a Russian pair, and translation from Ukrainian added its own Russian values next to the old ones | Delete the extra Russian values in the product card (before the switch) |
| “Item not found” when adding to a document | The product has no Ukrainian record | Fill in the Ukrainian name in the card or translate it (documents) |
| Top levels of the path disappeared from the “Category” column | The top-level categories have no Ukrainian name | Give them Ukrainian names or accept a shorter path, then run “Base catalog categories” (readiness check) |
| New products from a price list have Russian names on the Ukrainian tab | The price list has “Link products to language” set to “---”; or the products came through the general “Updating base catalog” run; or the “Database integrity check” wrote the supplier's text into a product without a Ukrainian record | Set “Русский” and update the catalog with the “Update my catalog” button; fix already created products in the card, and if they also have Russian text on the Russian tab — translate with “Force translation of all values” by “Product ID” or “Category ID” (price lists) |
| Supplier products that used to match have become new | Matching by name compares with the Ukrainian name | Don't add new products blindly; match them by hand (price lists) |
An empty tag with {name_ua} in the feed |
The template has no language selected, it follows the main language, and the template language macro is cut out | Ukrainian — {name}, Russian — {name_ru}; or select the template language in the “Language ID” field (feeds) |
| The number of products in the feed changed | The template has no language selected, and the filter rule based on an attribute value now compares with the Ukrainian value | Enter the value in the rule in Ukrainian (feeds) |
| Ukrainian text appeared in the Russian version of the website | The tunnel's multilingual mode is off, the website has no Ukrainian language, and the tunnel's language rule points to Russian | Turn on “Languages” in the tunnel template or add Ukrainian on the website (tunnel) |
| Product names on the WooCommerce website became Ukrainian | The product name is updated on every export | Clear “Update” in the name row in “Export fields” of the tunnel template (tunnel) |
| The addresses of OCFilter filter pages changed | Value IDs are calculated from the text in the main language | Check filter landing pages and links to them — in menus, ads, bookmarks (tunnel) |
| Size charts disappeared from the website | They're exported only in the main language | Fill in the size chart description in Ukrainian (tunnel) |
Old storefront addresses redirect to /ua/… |
Ukrainian kept its prefix, and it's now the main language | Change the prefixes or leave them knowingly (storefront) |
| Auto-translation translates from the wrong language | The schedule remembers the source language it was saved with | Choose “Source language” and click “Save for auto-translation” (translation) |
| A colleague's interface stayed in Russian | The interface language is set in the employee card | Change the language in the user card |
FAQ
Will the Russian texts disappear after the switch?
No. Texts in each language are stored separately; the switch doesn't delete or overwrite them. Only the language used to fill the catalog grid, feeds and everything new that arrives without a set language changes.
What must be translated before the switch?
Attribute values: at the moment of the switch, only Russian values that already have a Ukrainian pair are linked to Ukrainian ones. The rest can be translated later, but until then there will be gaps in the grid and feeds (before the switch).
Do I need to run reindexing after the switch?
No. The switch reindexes the catalog in Ukrainian by itself. You need to run indexing in “System functions” only if the switch broke off and Ukrainian has already become the main language (the switch broke off).
What should I do with price lists from Russian-language suppliers?
Before the switch, set “Link products to language” to Russian in their cards and update the catalog with the “Update my catalog” button. Translate new products right away, before the “Database integrity check” fills the Ukrainian fields with the supplier's text (price lists).
Do I need to redo feeds for Rozetka and Prom?
Check the “Language ID” field in the template. If a language is selected, the template won't change. If not, as well as for Prom XLS, the feed goes out in Ukrainian and the {name_ua} macros become empty: Ukrainian goes into {name} (feeds).
Will the language of my OpenCart website change?
The website's main language won't, except on ElbuzCart. With the tunnel's multilingual mode on, texts don't swap; with it off, only Ukrainian goes to the website — into whichever website language it matches (tunnel).
Can I make Russian the main language again?
Yes, by switching again: attribute values are relinked in reverse, and the grid returns to Russian right away (put things back as they were).
Where to find it and who has access
- Menu
- Directories → Languages → the “Main language” column
- Translation workload
- the “Translate into other languages” window → the “Statistics” tab
- Access rights
- the “Languages” window; for the preparation — “Batch Translation”, “Price Lists” and “Export”
- Prepare
- names, descriptions, categories and attributes translated into Ukrainian; a time when nobody is working
“Batch Translation” is what the access rights call the “Translate into other languages” window.
Related topics
- If you need the mechanics of the “Languages” window — columns, deletion, rollback — How to add a catalog language and change the main one.
- If you need to translate the catalog before the switch — Batch translation.
- If you're translating attribute names and values — Attribute translation.
- If you need to set up the tunnel's multilingual mode — Export to your website.
- If you're changing language prefixes on the storefront — SEO URLs.
