How Do You Translate Products for Multilingual E-Commerce? Catalog Setup, Automatic Translation Check, Units and Currency, Time Comparison for 30 Products
How do you translate product descriptions for multilingual e-commerce? Catalog setup, an automatic translation checklist, units and currency, and a time calculation for 30 products.
Contents 13 sections
- What is multilingual e-commerce and how does it differ from multi-country e-commerce?
- How many languages do you need for which market?
- How do you set up a multilingual product catalog?
- How does the workflow for translating product descriptions work?
- What does a product card look like before and after translation?
- How are units of measure, currency and number format handled?
- What do you do if the product title does not fit the limit after translation?
- What is the checklist after automatic translation?
- How long does translating 30 products take manually and automatically?
- How do you manage multilingual products with NetKasam?
- How do you keep translations up to date?
- What are the most common mistakes in multilingual e-commerce?
- Frequently Asked Questions About Multilingual E-Commerce
If your product card is written in Turkish, it is invisible to a buyer in Germany or the UK. Setting up multilingual e-commerce is the way past this invisibility; but most sellers think the job is "pasting the text into a translation tool" and run into problems with the very first product: the unit of measure stays wrong, the title does not fit the limit, the price appears in the wrong currency, and the same product stays live on two different marketplaces with two different translations.
This article explains how to set up multilingual e-commerce as a workflow: which language is needed for which market, how to keep the product card in a single source with a language layer, how to check an automatic translation draft, and how to handle currency and units of measure separately. You will also find a before-and-after translation table for a sample product and the time difference between manual and automatic work for 30 products. Which fields are translated, word volume and local keywords are covered in detail in the product translation for international marketplaces training, so they are not repeated here; instead, this article focuses on workflow and operations.
What is multilingual e-commerce and how does it differ from multi-country e-commerce?
In short: Multilingual e-commerce is offering product information and store content in more than one language. Multi-country e-commerce, on the other hand, is selling in different countries; the two can go together or separately.
A single-language store sells only to Turkish-speaking buyers. In a multilingual setup, the product name, description, attributes and category name also exist in the target languages. Multi-country selling additionally brings currency, shipping, tax and invoicing; these are independent of language. With an English product card you can sell in several countries at once, but you may need to show the price in each of those countries in its own currency.
For the general framework of cross-border selling, see the article what is e-export and the e-export glossary entry. This article does not cover selling as a whole, but the multilingual management of product content.
How many languages do you need for which market?
In short: The number of languages is not the same as the number of countries you want to sell in. The 22 countries on NetKasam's Amazon integration page cover 12 different listing languages; 9 stores work in English.
This simplifies the language plan. A single English source text covers the listing language of the UK, US, Canada, Australia, India, Singapore, United Arab Emirates, Saudi Arabia and South Africa stores. German, French, Italian and Spanish are the four major language groups in Europe.
- English9 stores40.9%
- French2 stores9.1%
- Spanish2 stores9.1%
- German1 store4.5%
- Italian1 store4.5%
- Dutch1 store4.5%
- Polish1 store4.5%
- Swedish1 store4.5%
- Arabic1 store4.5%
- Portuguese1 store4.5%
- Japanese1 store4.5%
- Turkish1 store4.5%
Source: country cards on the NetKasam Amazon integration page (listing language field).
The table below shows that language alone is not enough. Countries sharing the same listing language have different currencies.
| Sign-up language | Sample stores | Currencies |
|---|---|---|
| English | UK, US, Canada, Australia, Singapore | GBP, Dollar, CAD, AUD, SGD |
| French | France, Belgium | EUR |
| Spanish | Spain, Mexico | EUR, MXN |
| German | Germany | EUR |
A practical order for your first language choice is: English first, then the language of the first European market in your sales plan. For country details, see the Amazon Germany, Amazon UK and Amazon France pages.
How do you set up a multilingual product catalog?
In short: The product card stays single; the name, description, attributes and category name are kept in separate fields per language. Stock code, barcode, inventory and variant structure are independent of language and managed in one place.
The most common mistake is opening a separate product card for each language. In that case inventory is kept in two places, when one sells the other is not updated, and the risk of overselling arises. In the correct structure, language is just another view of the product. You can find how to preserve size and color matching for variant products in the article managing variant products on marketplaces.
- 01Simplify the source textShort sentences, clear meaning, no abbreviations.
- 02Write the term listFixed equivalents for brand, model and product type.
- 03Produce the automatic draftProduct name, description and attributes for the target languages.
- 04Check field by fieldUnits, title length, numbers and claim sentences.
- 05Publish by countryEach store in that country's language and currency.
- 06Refresh when the source changesReview the translation again when the Turkish text changes.
For the inventory side, the inventory management page should be read together with the multiple languages page, which explains how the language panel works with a single inventory.
How does the workflow for translating product descriptions work?
In short: First the source text is simplified, then a term list is prepared, an automatic draft is produced, and it is checked field by field and published. If the order is broken, the cost of correction rises.
The quality of the source text determines the quality of the translation. Sentences that leave the subject vague, such as "Stylish and practical, just right for you", lose meaning in automatic translation. Instead, use short sentences that carry information, such as "Handmade ceramic mug, 350 ml, dishwasher safe". When each sentence contains a single piece of information, both automatic and human translation get easier.
The term list is prepared once and is useful for every product: the brand name is not translated, the product type is written with a fixed equivalent, and unit abbreviations are kept in a single form. This list is the most effective preparation for shortening review time; you will see this in numbers in the time comparison later in the article.
What does a product card look like before and after translation?
In short: The automatic draft carries the meaning to a large extent, but needs correction in the unit of measure, the product type equivalent and the title structure. The table below shows the difference field by field for a sample product.
Sample product: "El Yapımı Seramik Kupa 350 ml Mat Beyaz". The draft column is an example representing typical automatic translation output; actual output varies by tool and text. The English target market is assumed to be the US.
| Area | Source (Turkish) | Automatic draft (example) | After review | Why was it corrected? |
|---|---|---|---|---|
| Title | El Yapımı Seramik Kupa 350 ml Mat Beyaz | Handmade Ceramic Cup 350 ml Matte White | Handmade Ceramic Mug, 11.8 fl oz, Matte White | "Mug" is the more accurate product type for a drinking vessel with a handle; in the US, volume is written in fl oz |
| Volume | 350 ml | 350 ml | 350 ml (11.8 fl oz) | 350 ÷ 29.57 = 11.8; both units are given together |
| Height | 9 cm | 9 cm | 9 cm (3.5 in) | 9 ÷ 2,54 = 3,54 |
| Weight | 420 g | 420 g | 420 g (14.8 oz) | 420 ÷ 28,35 = 14,8 |
| Care | Bulaşık makinesinde yıkanabilir | Can be washed in the dishwasher | Dishwasher safe | This is the set phrase buyers search for |
| Number format | 1,250 adet satıldı | 1,250 pieces sold | Sentence removed | A claim sentence is not published where it cannot be verified |
The calculations in the table have been verified by hand. What there is to learn here is less about mistranslation and more about incomplete localization: the draft preserves the meaning but does not adapt the unit and search phrasing used in the buyer's country.
How are units of measure, currency and number format handled?
In short: Units and number format vary by country; currency, on the other hand, is independent of language and is set by the store. All three are separate lines checked together with the translation.
| Topic | In Turkey | Watch out in the target market |
|---|---|---|
| Decimal and thousands separator | 1.299,90 | In many English-speaking markets 1,299.90 is written; in the wrong order it becomes two different numbers |
| Length | cm | Inches are expected in the US; giving both units together is safest |
| Weight and volume | g, kg, ml, l | oz, lb and fl oz are used in the US |
| Size | Letter or European number | A separate size chart is given per country; translating is not enough |
| Currency | ₺ | Shown in the store's currency, calculated separately with exchange rate and commission |
Currency and exchange rate calculation are a separate topic from language. Converting the price at the exchange rate and publishing it without deducting commission, shipping and tax costs leads to losses; you can find this calculation step by step in the article how to set prices on international marketplaces. The currency risk entry is also worth reading for exchange rate fluctuations.
What do you do if the product title does not fit the limit after translation?
In short: The title length limit varies by marketplace and product group; the title can get longer after translation. If the limit is exceeded, the words carrying the least information are removed first, while the brand and product type are kept.
Marketplace title rules change from time to time; check which character count applies not from this article but from the marketplace's current seller help page. Text length also changes with the language: in languages that use compound words, such as German, the word count may drop but individual words get longer, so title length needs to be measured separately in each language.
- Count the characters of the title after translation and compare it with the marketplace's current limit.
- If it exceeds the limit, remove repeated adjectives ("stylish", "practical") and decorative phrases.
- Keep the brand name, product type and distinguishing attribute (size, color) in the title.
- Move the removed information to the description or attribute field so it is not lost.
What is the checklist after automatic translation?
In short: Eight things are checked before publishing: product type, measurements, brand name, number format, title length, claim sentences, shifts in meaning and the language of the target market. Apply the list exactly for every translation batch.
- Product type: Does the draft give the correct product name, or a near equivalent?
- Measurements and volume: Is the unit suitable for the target market, and are both units written together?
- Brand and model: Have they been left untranslated?
- Number format: Are the decimal and thousands separators right for the target language?
- Title length: Has the current limit not been exceeded?
- Claim sentences: Have unverifiable phrases such as "best", "first" and "guaranteed" been removed?
- Shift in meaning: When the translated text is translated back into Turkish, is the meaning preserved?
- Target market language: If the same language uses different spellings and terms in two countries, was the right one chosen?
The accuracy of the translation is the responsibility of the seller who publishes the content; automatic translation is a draft. So if legal content such as legal notices, warranty periods and return conditions is needed, have it checked by an expert or a translator.
How long does translating 30 products take manually and automatically?
In short: With sample assumptions, publishing 30 products in English and German takes 36 hours manually, but drops to 10 hours with an automatic draft and a term list. The times are examples; your own time will vary by product type.
The assumptions are: 30 products, 2 languages, so 60 product-language pairs. In manual work, translation takes 30 minutes per pair and pasting into the marketplace 6 minutes. With an automatic draft, translation takes 2 minutes and full review 10 minutes. Once the term list is prepared, review drops to 6 minutes, and transfer via integration brings pasting time down to zero; preparing the term list takes 2 hours, once.
- Product-language pairs = number of products × number of languages
- Unit time = draft + review + transfer (minutes)
- Total time = number of pairs × unit time + one-time preparation
| Scenario | Draft or translation | Control | Transfer | Unit time | 60 pairs | Preparation | Total |
|---|---|---|---|---|---|---|---|
| A: Fully manual | 30 min | 0 min | 6 min | 36 min | 2,160 min | 0 | 36 hours |
| B: Automatic draft, full review | 2 min | 10 min | 6 min | 18 min | 1,080 min | 0 | 18 hours |
| C: Term list and integration | 2 min | 6 min | 0 min | 8 min | 480 min | 120 min | 10 hours |
- A: Fully manual36 min
- B: Automatic draft, full review18 min
- C: Term list and integration8 min
Prepared with sample values; measure your own times with pilot products.
- A: Fully manual (60 pairs)36 hours
- Automatic draft and full review instead of manual translation−18 hours
- Review shortened by the term list−4 hours
- Transfer via integration instead of pasting−6 hours
- Term list preparation (once)2 hours
- C: Term list and integration10 hours
Prepared with sample values.
Note that the biggest gain does not come from the term list: the real difference is the speed of the draft. The term list and integration, for their part, eliminate repetitive work. No scenario brings review time down to zero, because review is the guarantee of quality.
- 60product-language pairs (30 products × 2 languages)
- 36 hoursfully manual work
- 10 hourswith a term list and integration
- 8 minunit time per pair (C)
How do you manage multilingual products with NetKasam?
In short: In NetKasam, multi-language and multi-currency support is included in the Global Plus plan. The product name, descriptions, attributes and category name are translated and edited from the language panel; inventory and the product card are single.
- Automatic and manual translation: You decide which languages to translate into, use automatic translation and edit the content by hand when needed.
- Language panel: You can translate and edit product descriptions and category names through the language panel; the multiple languages page summarizes the scope.
- Global marketplaces: The Amazon integration opens up 22 countries; for each country you can list products in that country's language.
- Plan scope: The Global Plus plan lists multi-language and multi-currency support, an automatic currency conversion module and support for 12+ languages. For the current scope and price, see the pricing page.
Bookkeeping and the e-Invoice system are free in every plan. For clear information on whether the multi-language feature has an extra charge or on language coverage, contact a customer representative.
Recommended readingHow to Open an Amazon Seller Account?How do you keep translations up to date?
In short: When the Turkish source text changes, the related translation is reviewed again. Price and inventory updates, however, do not change the language text and are managed separately.
There are three kinds of changes in a multilingual catalog, and each requires a different action. A text change (product attribute, care instructions) calls for refreshing the translation. An inventory or variant change is independent of language and made in a single source. A price change is calculated separately with the target store's currency and commission.
A simple rule works: whenever you change a product's source text, mark that product as "awaiting translation" and clear these in your weekly routine. One extra column is enough to keep track. If you use a supplier feed, the article XML integration helps you understand which fields are affected when the feed changes.
What are the most common mistakes in multilingual e-commerce?
In short: Most mistakes come not from translation quality but from gaps in the process: copying the product card per language, not converting units and writing the translation once and leaving it.
- Opening a separate product card for each language. Inventory is kept in two places, and the risk of overselling arises.
- Not converting the unit of measure. A buyer in the US may not know what 350 ml is.
- Mistaking currency for language. English text is published in stores with different currencies.
- Translating the brand name. The brand name does not change in any language.
- Not checking title length. After translation the title can exceed the limit and the listing can be rejected.
- Not reflecting source changes in the translation. The Turkish is updated while the old information stays live in the foreign language.
- Translating unverifiable claim sentences as they are. The phrase "best-selling" can carry legal risk in the target market.
Frequently Asked Questions About Multilingual E-Commerce
What is multilingual e-commerce?
It is offering product information and store content in more than one language. The product name, description, attributes and category name also exist in the target languages. Topics such as currency and shipping are managed separately from language.
How do you translate product descriptions?
The source text is simplified, a term list is prepared, an automatic draft is produced and checked field by field. It is not published until the unit of measure, product type and title length have been reviewed by hand.
Is automatic translation enough?
It provides a quick draft but does not guarantee accuracy. Brand names, measurements, number formats and claim sentences must be checked. The person who publishes it is responsible for the accuracy of the translation.
How many languages do you need for product listings on international marketplaces?
It depends on the listing languages of the countries you want to sell in. The 22 countries in the Amazon integration cover 12 listing languages, and 9 stores are in English; so a single English source covers most stores.
Are language and currency the same thing?
No. The same English text is used in stores with different currencies. The price is calculated separately with the exchange rate and commission.
What do you do if the title does not fit the limit after translation?
First the decorative phrases are removed, while the brand name and product type are kept. The removed information is moved to the description or attribute field. Check the current limit on the marketplace's seller help page.
Which NetKasam plan includes multiple languages?
The Global Plus plan includes multi-language and multi-currency support, an automatic currency conversion module and support for 12+ languages. For the current scope and price, see the pricing page.
As a first step, pick your 5 best-selling products, prepare the term list for each, produce the draft in a single language and check it with the eight-item list above. Once you have measured the time, you plan the remaining products with your real numbers.
Bookkeeping Is Now Completely Free
Manage your bookkeeping and e-Invoice operations with NetKasam without paying a thing. Customer and supplier accounts, inventory, collections and more in one panel, completely free.