How to choose a platform for a multilingual online store: products and translations
The contents of a kit have been corrected on the Ukrainian product page, but a Polish customer still sees the old description. The manager does not know whether this is a separate product, an overlooked translation or data from a previous import. A platform for a multilingual online store should help manage changes like these, not just add a language switcher. This is what you should check before commissioning development.
Choose the foundation by how it links a product to its translations, separates shared data and lets you check whether a language version is ready. Then check URLs, integrations and the entire purchasing journey. Compare implementations using a demo catalog; adding a language does not necessarily require replacing your current CMS.
What a platform for a multilingual online store needs to support
You need a manageable model of a single product with language-specific representations, not just a translated screen. It should maintain the link to inventory records and show which data is shared, which is translated and who is responsible for updates.
Language, country of sale and currency are different attributes. A Polish-speaking customer may request delivery within Ukraine, while an English-speaking customer may order in several countries. The rule “one language equals one price list and one warehouse” is therefore suitable only if that is how the business operates. Otherwise, it will create unnecessary copies of the catalog and ambiguity in orders.
Before discussing the CMS, prepare a map of language-dependent fields. The name, description, explanations of specifications and search metadata usually need language-specific values. The SKU and the link to the inventory item must remain consistent. Set a separate rule for photos: an image of packaging with text may differ even if the technical product photo is shared.
This distinction is needed as early as the store design stage. GL.ua (Глянець) specializes in Drupal development and integrations: for this task, it is important to agree on the catalog structure and data exchange before adding content in bulk. However, the name of the CMS alone does not confirm that the required setup is already configured in a particular proposal.
How to compare ways of storing products and translations
Compare models by what happens during a routine update, not by the number of languages in a presentation. Check whether changes to stock, a specification or a description reach the relevant representations without creating a new product in the inventory system.
| Implementation model | When it is suitable | What to check before choosing |
|---|---|---|
| Shared product with translatable fields | The product range is shared; its presentation differs by language | Stable identifier, shared fields, separate text editing |
| Linked separate product records | This is how the chosen system stores language versions | Reliable links between copies, updates to inventory data, no duplicate SKUs |
| Separate storefronts with a shared catalog source | Markets have substantially different product ranges and sales rules | Division of responsibility between the data source and each storefront |
| Translation only when the page is displayed | A supplementary scenario, if its limitations are acceptable | Persistent language-specific URLs, editorial control, availability of translated content |
These are models to evaluate, not a ranking of technologies. Check both the links between separate records and the configuration of shared fields: no model replaces proper configuration.
What to check in Drupal Commerce
Check translation settings for your specific product types, variations and specifications. Drupal Content Translation lets you define whether entities and their fields are translatable; this is a configuration capability, not a ready-made editorial workflow for every store.
Ask to see a single variation with the same SKU and different color names in two languages. Then change a shared specification and a language-specific description. The result should match the agreed field map. Check categories, attribute values, images and search separately: translating a product does not prove that all related elements are translatable.
What to check in a ready-made SaaS storefront
Check the platform, theme and apps that will actually be used in your store together. For example, Shopify supports language-specific URLs and translations, but theme and third-party app compatibility matter for complete localization.
According to Shopify documentation, if a translation is missing, the store may display content in the primary language. The question for the contractor is therefore specific: how will the team identify untranslated elements before publication? This model may be entirely suitable for a simple catalog if rules for the fallback language, editing and app testing are agreed.
What happens to translations after a catalog update
The chosen implementation should let you identify translations that need another review after the original changes. If there is no built-in mechanism, replace it with an agreed process or custom functionality, rather than relying on the manager’s memory.
Distinguish between fixing a typo and changing the substance of a product. Correcting a comma does not always require suspending publication. Changes to kit contents, compatibility or restrictions on use require a review of the corresponding language descriptions. Name these fields in the specification and agree on what happens to an already published version until the review is complete.
Missing and outdated translations are different states. The first has not yet been created; the second exists but no longer matches the approved data. A “translated” label that does not indicate whether the content is up to date will not help an editor plan their work. Ask to see a review queue or another repeatable way to find these records.
You do not necessarily need a separate translation system or PIM straight away. If the team manages one site and a simple catalog, the CMS capabilities and a clear procedure may be enough. Choosing a separate source of product content is discussed in the article on the differences between PIM and MDM; here, we are assessing the suitability of the store platform itself.
How to check language-specific URLs, search and performance
Every planned language page should have a predictable address and open regardless of the previously selected language. The switcher should lead to the corresponding product or clearly explain its absence, rather than silently returning the customer to the home page.
For SEO, agree on URLs, language-specific metadata and links between versions. Google recommends marking localized equivalents with hreflang, including reciprocal links between them. A technical check against Google’s documentation on localized versions helps identify linking errors but does not guarantee indexing or rankings.
In the demo, test searches using a translated name and specification. The product found should match the current interface language, and the selected filter should retain a clear meaning. If full-text search needs a separate index or a language analyzer configuration, this must be included in the scope of work, not discovered after the catalog has been uploaded.
Language-aware caching is tested by repeatedly switching between languages and sessions. A page must not receive a name in the wrong language or an interface fragment from the cache. Compare performance using the same set of products, images and apps; the number of languages alone is not a sufficient explanation for slow responses.
How to run a demo with one product and two languages
The demonstration should show the full cycle: creating a translation, making a sale, changing data and checking again. Use the same test scenario for every proposal so that you compare results rather than presentation skills.
Hypothetical example: a store sells an equipment care kit in Ukrainian and Polish. The kit has a shared SKU, while the text on the packaging and the instructions for use differ. Later, the supplier changes the kit contents. This is not a GL.ua case study: it is intended to test how the proposed solution behaves.
- Create a product and its translation, record the link to the inventory item and check the language-specific URLs.
- Change the stock level in the inventory source. Both representations should receive the agreed availability without duplicating the item.
- Make a purchase in another language. Check the SKU, name, quantity, amount and confirmation language in the order.
- Update the kit contents in the source. Check how the editor finds the language-specific description that needs review.
- Give the editor a restricted role and check whether they can translate text without changing protected commercial fields.
- Repeat the import and open both versions again. Record whether translations, links and the agreed publication status have been preserved.
Before the demo, record the expected result; afterwards, record the actual result and how any gap will be resolved. A single product in an order must remain unambiguous for both the manager and the integration, regardless of the storefront language. This is what separates manageable multilingual functionality from a collection of similar product pages.
What work to include in the budget and schedule
Estimate not just language setup but also data modeling, translation preparation, integrations and testing. The timeline will depend on content readiness and approval rules as much as on technical implementation.
When comparing proposals, separate one-time configuration from ongoing editorial work. A translation app license does not automatically include proofreading, and an automatic translation does not mean a description is ready for sales. Plan support after updates for custom modules and templates; for third-party services, verify the pricing plan and data-processing terms.
- An agreed map of shared and translatable fields, categories and attributes.
- Import without overwriting approved language-specific values.
- Editorial roles, checks that content is up to date and the publication procedure.
- Language-specific URLs, metadata, search and cache testing.
- Translations of the cart, notifications and third-party app elements.
- Repeating the test scenario after dependency updates.
A separate risk is sending non-public product content to an external translation service. Before connecting it, determine which data may be sent, who manages access and how it can be revoked. Do not use customers’ real personal data in a demonstration if anonymized records are sufficient for the test.
What result should guide your decision
Choose an implementation in which the test scenario works with clear rules and an acceptable amount of manual work. If a simple CMS or a ready-made service already meets these conditions, a more complex architecture is not needed merely for a few languages.
The limits of translation automation should be recorded in writing: what the system updates itself, what it flags for review and what the editor checks. Broader questions of cultural adaptation and markets can be explored in the article on localization and entering foreign markets. Choosing a platform, however, ends with evidence that daily catalog updates are manageable.
To discuss online store development with GL.ua, prepare a field map, a sample import and a description of one product change in two languages. This provides a concrete basis for agreeing on the catalog model, required customizations and pre-launch checks—rather than choosing technology solely by the language flags in a demo.
Frequently asked questions
Can a new language be launched for only part of the catalog?
Yes, if the implementation lets you control the availability of language-specific representations without creating misleading links. Agree on what customers see for an untranslated product and how links from categories and search are checked.
Can the primary language be changed after launch?
This depends on the platform and current configuration, so the change needs a separate assessment. Before deciding, check URLs, the fallback language, imports and preservation of translation links; changing a setting alone does not prove that the entire store is ready.
How do you check a third-party review or product-selection widget?
Include the widget in the demo’s language test scenario: check its labels, error messages and links to products. Ask for written confirmation of who is responsible for untranslated content and whether the provider supports the required languages.
Do internal inventory codes need translating?
Usually not: codes are used to match products unambiguously between systems. Customers can see localized names, but the integration must preserve the agreed identifiers rather than match records by text alone.
Is automatic translation enough for the initial content upload?
It can be used as a draft if the data and the service terms permit it. Before publication, check terminology, specifications and restrictions on product use; agree on the scope of human review separately from the technical connection.
Just one step to your perfect website



