Elbuz translates your site: products, categories, attributes, manufacturers and articles into other account languages via Elbuz Translate, Google Translate or DeepL — by button, on schedule or after a catalog update.
When you need this:
- Your site gets a new language — one run translates the whole catalog, disabled products included.
- New price list products reach marketplaces untranslated — the post-update step translates them before export.
- An editor hand-fixed a translation — auto-translation fills only empty fields, edits stay.
- Unclear what is untranslated — “Statistics” shows gaps by field and language.
Where to start: Directories → Languages → the “Translate into other languages” icon, then languages, service, fields and “Run”.
What translation can do
- Manual run — translates what you ticked right now; only here can you retranslate over existing translations and limit the run to one record or category.
- Scheduled translation — one task per account at the set time; existing translations are not changed.
- Translation after a catalog update — a step between the catalog update from price lists and building exports: new products reach marketplaces already translated.
- One auto-translation setting — the schedule and the step after the update use the same languages, service and fields.
- Statistics — how many records of each field still lack a translation in each language.
All methods translate fields by the same rules.
How to choose languages and the service
At the top are three tabs: “Settings”, “Log” and “Statistics”. Next to them are three buttons — to the right on the same row in a wide window, on a row below the tabs in a narrower one, with “Run” first:
- “Run” — translates what you ticked right now.
- “Save for auto-translation” — remembers the languages, service and ticked fields for translation without a person. The button tooltip: “Keep the languages, service and ticked fields for automatic translation — on schedule and after the catalog update. Only empty fields are translated.” After you click it, Elbuz replies “Auto-translation fields saved”.
- A clock icon without a caption, tooltip “Schedule” — saves the same selection and opens the translation schedule (scheduled translation).
If no translation service is available, these three buttons are not there at all — instead, the “Languages and service” card shows a yellow hint (what to do about it). At the bottom of the window is the auto-translation status line: whether the schedule and the step after the catalog update are on.
1
Tab row2
Run3
Save for auto-translation4
Translation language field5
Force translation toggle- Settings, translation progress and what is still untranslated.
- Translates the selected fields right now.
- Remembers the selection for the schedule and the post-update step.
- The “All languages” option covers every active language except the source.
- Overwrites ready translations — only during a manual run.
“Source language” — the language to translate from. The list shows only active languages. The is selected at first, or the one saved for auto-translation if it differs.
“Translation language” — the language to translate into. With more than one active language, the list also has “All languages”: the translation goes into every active language except the source language.
A language is included in translation only if the “Languages” window grid has its “Translation service language” column filled in. There you pick from a list what the translation service calls this language; a language without this value is not translated.
“Select translation service” — Elbuz Translate, Google Translate or DeepL. A service you can't use is visible in the list but grayed out and can't be selected. Selected is the first available service or the one saved for auto-translation.
- Elbuz Translate is on right away, no key needed. It is paid from your balance by the volume of translated text; a failed translation, when the service returned nothing, is not charged.
- Google Translate and DeepL work with your own key. Enter it in “System settings” → “Other settings” → the “External services and integrations” tile: the service's entry holds the token and status.
How to retranslate over existing translations
Below the service selection is the “Force translation of all values” toggle. Without it, fields already filled in the translation language are skipped. With it, all are translated, overwriting existing ones. The note under the toggle: “Useful when values in the source field have changed and need to be translated again: old translations are overwritten with new ones.”
The exception is “Attributes” → “Values”: only attribute values without a translation yet are translated, and the toggle doesn't affect them. But when a value changes in the source language, its old translation is reset and the value is translated again.
You turned on “Force translation of all values” to update a few descriptions, and Elbuz rewrote the translations of all ticked fields, including hand-edited ones. Use it only when source texts really changed, ticking only the fields to retranslate. The toggle is never saved to or used by auto-translation: the schedule and the post-update step translate only empty fields.
If translations are already overwritten, there is no undo. Translation writes new text over the old one with no change history, and Elbuz keeps no copy of the previous text. You can restore it only by hand, in the record's card. What exactly was overwritten:
- all records of the ticked fields where the source-language field is filled in, or, if “Test on a single record” held an ID, only that record or category;
- where the service returned nothing, the old translation stayed;
- after “Stop translation” — only what was written before the stop: each record is saved separately, right after it is translated.
How to choose fields and test on a single record
The “What to translate” card holds field checkboxes grouped by section. On the right of the card header are the “Select All” and “Clear selection” links. When the window opens, the fields saved for auto-translation are already ticked, so before a manual run check that exactly the right ones are ticked.
- Categories: Name, Short description, Full description, HTML tag, HTML title tag, Description meta tag, Keywords meta tag, Tags.
- Products: the same eight fields plus Reviews.
- Attributes: Name, Description, Values.
- Manufacturers: Short description, Full description, HTML H1 tag, HTML title tag, Description meta tag, Keywords meta tag, Tags. The manufacturer name is not among the fields.
- Articles: eight fields, as for categories, plus Reviews and Tests.
Not all sections are shown, only those that match where you opened the window from (entry points).
1
Select All / Clear selection2
Products — Reviews3
Manufacturers4
Pre-ticked field- Tick or clear all fields with one click.
- For products, review texts are translated too.
- Manufacturers have no Name field — only descriptions, meta tags and tags.
- Pre-ticked fields are the ones saved for auto-translation.
Test on a single record
Below the checkboxes is the collapsed “Test on a single record” section. Its note reads: “Enter a record or category ID to check the result on a small set first. Leave it empty to translate all records of the section.” Fields by section:
- Categories: “Category ID” — only this category is translated.
- Products: “Product ID”; “Category ID” — only products whose main category it is. Products of subcategories are not included.
- Attributes: “Attribute ID” and “Product ID” — the latter applies only to the “Values” field.
- Manufacturers: “ID”.
- Articles: “ID”; “Category ID” — articles located directly in this category.
These fields are not saved to auto-translation: the schedule and the step after the update always translate the whole section.
You opened translation from the base catalog's “Products” window, clicked “Run”, and only one category got translated. This window shows your with a category tree, and translation opens with the category selected in the tree: “Test on a single record” expands by itself, its number already in “Category ID”. To translate all products, clear “Category ID” first.
1
Explanation text2
Category ID under Products3
Product ID under Attributes- An empty field means the whole section is translated.
- Only products whose main category is this one, without subcategories.
- Applies to the Values field only.
How to translate manually and track progress
Choose the languages and service, tick the fields and click “Run”. The window switches to the “Log” tab by itself: a progress bar runs there with the heading “Translate into other languages…” and a “Stop translation” button, while “Run” is grayed out during translation.
Before the first run the tab says “The log is empty” and “Translation progress will appear here after you click “Run”.” While products are being translated, the lines go like this:
- “‹Section› - ‹field› ‹language code› > ‹language code›” — what is being translated now, for example “Products - Name ru > ua”;
- every 100 records — “‹N› / ‹total› (‹field›) | translated: ‹N›, skipped: ‹N›”;
- after each field — “Completed. Total: ‹N›, translated: ‹N›, skipped: ‹N›”, for example “Completed. Total: 1, translated: 1, skipped: 0”;
- at the end — “Translation completed - ‹min›m ‹sec›s”.
For categories and articles the log lines look different. When translation is over, the log stays on screen, and the progress bar and “Stop translation” are hidden.
“Translated” means the service's translation was written; “skipped” means no translation: one already existed, the value is digits only (it is copied as is) or the service returned an empty response. If many are skipped and “Statistics” still shows a red “−N”, the cause is the service (troubleshooting).
“Stop translation” stops not only your run but any translation currently running in the account, including the nightly scheduled one and the step after the catalog update. “Stop import” in the list of price lists (the “Import sources” menu) does the same. The log of a stopped translation shows “Translation canceled”. The next run works as usual.
A manual run is not placed in the background job queue: the window sends one request, and translation goes on while that request runs. Closing the translation window doesn't cancel it — only “Stop translation” or “Stop import” stops it. Besides the “Log” tab, progress is recorded in “Account” → “Operation log”.
There is no limit on the number of records per run, and texts are not sent to the service in batches: each ticked field of each record is translated with a separate request to the service, and so for each translation language.
The exception is attribute values: identical values are translated once per run, and if the same value is already translated in another product, the existing translation is reused without calling the service. With “All languages”, languages are translated one after another. The “Statistics” tab shows how many records are still waiting for translation.
Two runs never go at once. Reopen the window during translation and click “Run”, and Elbuz replies “A translation is already running (in another window or on schedule). Wait for it to finish.” Same right after “Stop translation”: the server first finishes the current record, then ends the run. Scheduled or post-update auto-translation also won't start during another run.
What translation does with each field and what is left
The rules are the same for a manual run, the schedule and the step after the update.
- Only records whose source-language field is filled in are taken.
- If the field is already filled in the translation language, the record is skipped and counted as “skipped”. The exception is a manual run with “Force translation of all values” on (except attribute values).
- For products, categories, manufacturers and attributes the status is ignored: disabled records are translated too. Articles are translated only if active.
- An attribute value that changed in the source language is translated again: its old translation is reset — both in a manual run and in auto-translation.
- A value that, without punctuation, is digits only or empty is not sent to the service but copied as is and counted as skipped. This applies to categories, products, manufacturers, articles and attribute names. Digit-only attribute values aren't sent to the service either: they are copied into all translation languages but counted not as “skipped” but as “cache” in the progress line. For categories, products and manufacturers such a value is copied into all translation languages where the field is still empty, and an existing translation stays as it was. With “Force translation of all values” it is copied into all translation languages.
- If the service returned an empty response — a failure, an exhausted limit, no key — the field is not written and is also counted as skipped. There is no separate error line in the log, and in Elbuz Translate such a translation is not charged.
- When Elbuz Translate is unavailable, each record gets up to five attempts with a 30-second wait, so a run can drag on for hours.
- HTML markup in descriptions is preserved.
- Action or result
- Decision: the path depends on the answer
Some checkboxes translate more than their names suggest:
- Attributes, “Name” — also attribute groups and the attribute's short name.
- Attributes, “Values” — attribute values in products.
- Attributes, “Description” — the attribute description and value descriptions.
- Articles, “Name” — also the article's service fields not shown in the window: hashtags, target audience, goal, format, style, brief, slogan, subcategory.
- “Reviews” for products and articles — review texts.
- “Tests” for articles — test questions and answers.
How to see what is not translated yet
The “Statistics” tab loads by itself the first time you open it. The “Translation coverage” card explains itself: “How many records are filled in each language. Red shows how many records still lack a translation compared to the main language.” The refresh icon in the card, tooltip “Get statistics”, recalculates the numbers.
Each section of the window gets its own panel: a “Translated” percentage with a bar and a “field × language” table. A cell shows how many records have the field filled in that language. The first column is the main language. If another language has fewer records, a red “−N” appears next to it: that many are still untranslated.
The “Translated” percentage is not the share of translated records but the share of all “field × language” cells in the section. Gaps are summed over all fields and languages and compared with what is filled in the main language. So one untranslated field, say “Tags”, pulls the percentage down even if names and descriptions are fully translated.
In attributes, the “Values” field counts only originals in the main language and all values in translation languages. On a large catalog statistics take a few seconds to calculate.
1
Translated 0%2
EN column3
Red −8 279- The share of all field × language cells, not of records.
- The main language — the other languages are compared against it.
- How many records still have no translation in this language.
How to set up auto-translation and the schedule
What to translate without a person, Elbuz takes from one record per account. Both automatic methods read it — the schedule and the step after the catalog update. There are deliberately no two separate settings: otherwise it would be unclear why one thing got translated overnight and another after the catalog update.
The record holds the source language, the translation language or “All languages”, the translation service and the ticked fields by section. Two buttons write it: “Save for auto-translation” and the “Schedule” clock icon. The “Force translation of all values” toggle and the “Test on a single record” fields are not saved.
If the window is open with only some sections — say, from the base catalog's “Products” window, with only “Products” and “Attributes” — only those sections are saved. Fields of other sections saved earlier stay as they were.
In “System settings” this setting is the “What to translate automatically” row with a “Configure” button. The row description: “Languages, service and fields for automatic translation — both after the catalog update and on schedule.” The button opens the “Translate into other languages” window with all five sections.
The auto-translation status is shown at the bottom of the translation window: “Scheduled translation: ‹when›” or “Scheduled translation is off”, then after a dot — “After catalog update: translate” or “After catalog update: do not translate”. The icons turn green when a mode is on. “When” is the schedule rule in words, for example “At 03:00”.
The line is built when the window opens and doesn't refresh by itself: if you changed the schedule, close and reopen the translation window.
1
Scheduled translation is off2
After catalog update: do not translate- When translation will run by itself — or that the schedule is off.
- Whether new products are translated right after a catalog update.
Scheduled translation
Tick the fields and click the “Schedule” clock icon. It saves the selection for auto-translation just like “Save for auto-translation” and opens the usual schedule window. The scheduled translation task is created only with this icon.
There is one task per account. On the first click it is created disabled, with the default rule — 17:10 Monday to Friday, like all schedules in Elbuz. For translation to run, tick “Active” in the schedule window and set your time. The schedule window has no “Save” button — it saves by itself (how the schedule window works).
In the general “Job schedule” list — Account → System settings → the “Other settings” section → the “Job schedule” tile — the task is named “Translate into other languages”. This list has no “Add” button.
The clock icon needs two rights: “Batch Translation” and “Job schedule”. Without the second, Elbuz replies “You don't have permission for this operation!”. If you click the clock without ticking any checkbox, the run adds the line “Auto-translation: no fields or source language selected…” to the “Operation log” (troubleshooting).
On schedule, existing translations and manual edits are not changed. Translation runs are shown in “Account” → “Operation log”: type “Language” or the section's type with the subtype “Translate into another language”.
How to translate right after a catalog update
The schedule starts translation at a set time, while price list imports take a different time each run. If an import runs late, scheduled translation finishes before the new products appear in the catalog, and the export again goes out untranslated. The step after the update keeps the order: catalog updated → translated → exported.
Turn on “Translate texts after update”. It is off by default and active only when “Update catalog after import” is on. What to translate is set by the “What to translate automatically” row a little lower (auto-translation).
Where: Account → System settings → “Catalog update” → “Run and general rules”, between “Update catalog after import” and “Build exports after update”.
1
Update catalog after import2
Translate texts after update3
Configure4
Build exports after update- Without it the translation step does not run.
- Translates empty fields between the catalog update and the exports.
- Opens the translation window with all sections.
- Exports are built after translation is done.
Where the step runs:
- right after the that follows importing all price lists — on schedule or by a manual run;
- after a deferred update — when the update waited for to finish.
Where the step doesn't run:
- after importing a single price list on its own schedule;
- after the manual “Update” button in the catalog update window;
- from Elbuz Flows — there is no translation block there.
The order: catalog update → translation → building exports, if “Build exports after update” is on.
Exports themselves aren't tied to the catalog update: they run after all price lists are imported even when “Update catalog after import” is off — but then without translation, since translation runs only after a catalog update. When the update waited for parsing to finish, the export waits too and runs once — after the update and translation.
- Action or result
- Decision: the path depends on the answer
The step translates only empty fields; “Force translation” doesn't apply here. Failures don't break the chain:
- the translation service is unavailable — untranslated fields stay empty and count as “skipped”, the export runs as usual, and the next run tries them again;
- Elbuz Translate specifically is unavailable — each record gets several attempts with waiting (translation rules), and all that time the step holds back the export;
- fields or the source language for auto-translation aren't saved — the line “Auto-translation: no fields or source language selected…” appears in the “Operation log” (troubleshooting), and the chain goes on.
XLSX/CSV price lists and direct connections have another reason to translate before export: there a category needs a name in the export language, or all its products drop out of the file. In XML and Google feeds such a category just goes out unnamed. Other conditions export templates use to select products — in the article on product exports.
The products dropped from the file this way stay unchanged in the catalog: once the category gets a name in the export language, they come back with the next export.
Before turning on “Translate texts after update”, translate everything manually once in the “Translate into other languages” window. Otherwise the first run after an update will translate the whole catalog and hold back the export. The help next to the setting warns about this too.
What to do so translation runs by itself
Scenarios
New products from price lists must reach marketplaces already translated
What to do. Translate the catalog manually once: open “Translate into other languages” from the “Languages” window, choose “Source language”, “Translation language” and the service, tick the fields and click “Run”. Then click “Save for auto-translation”. In “System settings” → the “Catalog update” section, turn on “Update catalog after import”, “Translate texts after update” and “Build exports after update”.
What you get. After all price lists are imported — on schedule or manually — Elbuz updates the base catalog, translates empty fields per the saved selection and only then builds exports. If the update waited for parsing to finish, the export waits too and runs once, after translation.
What won't happen. There is no translation step after importing a single price list on its own schedule, after the “Update” button or in Elbuz Flows. The step doesn't change existing translations. If the translation service doesn't respond, the export is still built, and untranslated fields stay empty until the next run.
Your site gets a new language
What to do. In “Directories” → “Languages”, make the new language active and pick its “Translation service language” value. From there, open “Translate into other languages”: “Source language” — the main one, “Translation language” — the new one. Tick the fields in all five sections, make sure the “Test on a single record” fields are empty and click “Run”.
What you get. Every record whose source-language field is filled in gets text in the new language — including disabled products, categories, manufacturers and attributes. A red “−N” on the “Statistics” tab shows what remains untranslated.
What won't happen. Inactive articles and manufacturer names are not translated. Fields for which the service returned an empty response stay empty — another “Run” takes only those, since filled fields are skipped.
Source-language descriptions were rewritten and the translation needs updating
What to do. Tick only the changed fields, for example “Full description” in the “Products” section, and turn on “Force translation of all values”. To cover only part of the catalog, enter a “Product ID” or “Category ID” in “Test on a single record”. Click “Run”.
What you get. The translation of the ticked fields is overwritten in all records where the source-language field is filled in, or only in the specified record or category.
What won't happen. There is no undo: Elbuz doesn't keep old translations (what exactly is overwritten). The toggle isn't saved to auto-translation, so the schedule and the step after the catalog update will keep filling only empty fields. The toggle doesn't affect attribute values — their translation updates by itself when the source-language value changes.
The catalog isn't updated after all price lists, but you need regular translation
What to do. Tick the fields and click the “Schedule” clock icon — it needs the “Batch Translation” and “Job schedule” rights. In the schedule window, tick “Active” and set the time.
What you get. The “Translate into other languages” task translates empty fields at the set time per the selection saved for auto-translation, whole sections at a time — regardless of how and when the catalog was updated.
What won't happen. Without the “Active” checkbox translation won't run: the task is created disabled, with the rule 17:10 Monday to Friday. Products added to the catalog after a run wait for the next one. The schedule doesn't change existing translations or manual edits.
Preview the translation on one product first
What to do. Expand “Test on a single record”, enter the “Product ID” in the “Products” section, tick the fields and click “Run”.
What you get. Only this product is translated; the result is visible in its card and in “Log”.
What won't happen. Fields of this product that are already filled won't change without “Force translation of all values”. The ID isn't saved to auto-translation: the schedule and the step after the catalog update always take the whole section.
What to do when translation fails
| What you see | Why | What to do |
|---|---|---|
| “Specify the access token in the API settings for the external Google Translate service!” — in yellow in the “Languages and service” card, no “Run” button | No translation service is available: the Elbuz Translate entry in “External services and integrations” is turned off, and there is no Google Translate or DeepL key | Turn on Elbuz Translate or enter the service key: “System settings” → “Other settings” → “External services and integrations” (translation services) |
| “Auto-translation: no fields or source language selected. Open “Translate into other languages”, choose the source language, tick the fields and click “Save for auto-translation”.” — a line in the “Operation log”, type “Language” | ran, but fields or the source language weren't saved: “Translate texts after update” was turned on without ever saving fields, or the clock icon was clicked with no checkbox ticked | Open the translation window, choose the source language, tick the fields and click “Save for auto-translation” (auto-translation) |
| “You don't have permission for this operation!” after clicking a button in the translation window | The group lacks a right: the window's buttons need “Batch Translation”, the clock icon also needs “Job schedule” | Ask an administrator to give your group these rights, or set up the schedule as an administrator (who has access) |
| “Translation canceled” in the log | Someone clicked “Stop translation” or “Stop import” in the list of price lists — both buttons stop any translation in the account, including the nightly one | Run translation again — the next run works as usual (manual run) |
| “Scheduled translation is off” at the bottom of the window, though the time is set | “Active” isn't ticked in the schedule window — the task is created disabled. Or it was ticked, but the translation window wasn't reopened: the status line doesn't refresh by itself | Tick “Active” in the schedule window, then close and reopen the translation window (scheduled translation) |
| A red “−N” in “Statistics” after a run, and many “skipped” in the log | The service returned an empty response — a failure, a limit, no key or no balance; such fields are not written | Check the service, key and balance and run again — only the fields that stayed empty get translated (translation rules) |
| Products went to the export untranslated, though “Translate texts after update” is on | The price list was imported on a single source's own schedule, or the catalog was updated with the “Update” button — there is no translation step there. Or “Update catalog after import” is off | The step works only after all price lists are imported; for other cases set up scheduled translation (translation after an update) |
| Manual translation edits were overwritten | Translation was run with “Force translation of all values”. Or it's an attribute value that changed in the source language — then it is translated again | Elbuz doesn't keep previous texts, there is no undo — fix the translations by hand in the cards (what exactly was overwritten). From now on, don't turn on the toggle without need; auto-translation never uses it |
| Only one category's products were translated | Translation was opened from the base catalog's “Products” window with a category selected in the tree — its number went into “Test on a single record” → “Category ID” | Clear “Category ID” before the run (test on a single record) |
FAQ
How do I translate my site into another language?
Make the language active in “Directories” → “Languages” and fill in its “Translation service language”. Open “Translate into other languages” from there, tick the fields in all five sections and click “Run”. Then click “Save for auto-translation” (scenarios).
Will auto-translation overwrite what an editor fixed by hand?
No. Auto-translation fills only empty fields, and the “Force translation of all values” toggle doesn't apply to it. Edits are overwritten by a manual run with this toggle, and for attribute values — by a change of the value in the source language (what is overwritten).
Why translate after a catalog update if you can set a schedule?
Price list imports take a different time each run, and the schedule may finish before new products appear in the catalog. The step after the update keeps the order: updated → translated → exported (translation after an update).
Can I translate some fields on schedule and others after a catalog update?
No. There is one auto-translation setting per account, shared by both methods (auto-translation).
What happens if the translation service is unavailable during a catalog update?
The chain won't break: untranslated fields stay empty, the export runs as usual, and the next run tries them again. An unavailable Elbuz Translate delays the step with repeated attempts (translation rules).
Is translation paid?
Via Elbuz Translate — yes: it works without a key and is paid from your balance by the volume of translated text; a failed translation is not charged. Google Translate and DeepL work with your own key (translation services).
Why was only one category translated?
The window was opened from the base catalog's “Products” with a category selected in the tree, and its number went into “Category ID”. Clear this field and run translation again (test on a single record).
Are disabled products translated?
Yes. For products, categories, manufacturers and attributes the status is ignored. Articles are translated only if active.
Where it is and who has access
The “Translate into other languages” window has no menu item of its own. Which sections it shows depends on where you opened it from.
- From the “Languages” window
- Directories → Languages → the “Translate into other languages” icon; all five sections
- From categories
- Directories → Categories → “Catalog tools” → the “Translate into other languages” tile; the “Categories” section
- From products
- Base product catalog → Products → “AI & content” → “Translate into other languages”; “Products” and “Attributes”
- From attributes
- Base product catalog → Attributes → “Maintenance” → “Translate into other languages”; the “Attributes” section
- From manufacturers
- Directories → Product manufacturers → “Additional operations” → “Translate into other languages”
- From articles
- Directories → Articles → “Additional operations” or the icon in the articles form; the “Articles” section
- From system settings
- System settings → “Catalog update” → “What to translate automatically” → “Configure”
- Access right
- “Batch Translation”; for the schedule — also “Job schedule”; for the step after the update — “System settings”
- Prepare
- two or more active languages with “Translation service language” filled in; a translation service
1
Translate into other languages icon- Opens translation right away with all five sections.
To see and save the selection for all sections at once, open the window from “Languages” or from system settings. A window with only some sections saves just its own sections for auto-translation and leaves the rest as they were.
Without the “Batch Translation” right you get a no-access message instead of the window, and the window's buttons reply “You don't have permission for this operation!”. Auto-translation itself — on schedule and after a catalog update — does not check rights: it runs without a user.
For a store with one active language the window does nothing: there is nothing to translate into. To translate one field or all empty fields of a language in a single card, use the product card and the manufacturer card.
Related topics
- If translation should run after a catalog update, but the update doesn't start by itself yet — Updating the base catalog from supplier price lists.
- If a schedule task doesn't start or you need to change its time — Schedule and job queue.
- If products of an untranslated category dropped out of the export file — Exporting products to marketplaces, websites and files.
- If you need to translate one field of one product — Product card.
- If the new language isn't set up in the account yet — Catalog and interface languages.
- If you're building a single product catalog for your site and marketplaces — what it gives your store.
- If your site needs to be filled with products and descriptions — how to fill a site with content.
