2026-09-02
How to write product descriptions in five languages
Selling in five languages is not five times the poetry—it is five times the **consistency risk**. One mistranslated measurement, a false cognate in a material name, or a German sentence that overflows your mobile layout can cost returns and account health across Amazon EU, Etsy, eBay international sites, and Shopify Markets. The goal is not flawless literary translation; it is **the same facts, correctly expressed**, in each locale your catalog targets. This guide assumes five common e-commerce languages—**English, German, French, Spanish, and Italian**—but the workflow applies to any language set you choose. ## Start from one facts-only source language Multilingual chaos begins when each language version is written independently from marketing briefs. Numbers, materials, and compatibility diverge within weeks. Better architecture: - **Master catalog CSV** in your primary language (often English) with columns: SKU, product name, materials, dimensions, weight, contents, care, compatibility, legal disclaimers - **Translation or generation outputs** as separate columns or files: `title_de`, `description_de`, etc. - **Never translate finalized marketing fluff**—translate **structured facts**, then assemble prose per locale template If you use AI for drafting, prompt per language from the **same row JSON**, not from the finished English paragraph alone. Paragraph translation hides which facts were omitted in English. ## Choose your translation method deliberately Three production methods bulk sellers use: **Professional human translation** — Best for regulated categories and brand voice; expensive at scale. **Machine translation + human post-edit** — Common compromise; post-edit must check specs, not just fluency. **Constrained AI generation from facts** — Generate native prose per locale from columns; human reviews sample rows. Avoid raw machine translation of full HTML descriptions without review. Amazon and eBay listings in EU markets still must be **accurate**; garbled MT on safety warnings fails compliance even when "understandable." ## Locale-specific formatting before you write word one | Element | English | German (DE) | French (FR) | Spanish (ES) | Italian (IT) | |---------|---------|-------------|-------------|--------------|--------------| | Decimal separator | 12.5 cm | 12,5 cm | 12,5 cm | 12,5 cm | 12,5 cm | | Thousands | 1,000 | 1.000 | 1 000 | 1.000 | 1.000 | | Dimension order | L × W × H | often same | often same | often same | often same | | Quotation marks | "..." | „..." | « ... » | «...» | «...» | Decide whether listings use **localized units** (cm vs inches) per marketplace region or universal specs from your supplier. Mixing cm in German and inches in English for the same SKU causes returns—pick one spec truth in master data, convert programmatically with rounded values documented in a `units_policy` column. Dates: use locale-appropriate spelling in customer-facing prose ("2 September 2026" vs "2. September 2026") but ISO in machine columns. ## Title and length limits still apply per channel Multilingual text changes **character counts**: - German compounds run long: "Staubsaugerbeutel" vs "vacuum bags" - French and Italian often exceed English length for the same meaning - eBay's **80-character title** limit hits German listings first if you translate English titles word-for-word Build **per-locale title recipes** with truncation priority rules—not translate-then-truncate in panic. Amazon EU listings may share one ASIN across marketplaces with **localized bullets** per seller central tools—verify which fields are language-specific in your upload template. Etsy allows shop language settings; translations should exist for browsing buyers, not keyword-stuff foreign languages into an English primary title against policy intent. ## Keywords are language-specific, not translated synonyms Translating Amazon backend terms with Google Translate does not produce valid search terms for each locale. German shoppers search **German queries**; Italian shoppers use different colloquial terms for the same object. Workflow: 1. Research **locale keywords** independently (marketplace search suggest, competitor listings in that language) 2. Map locale keyword columns separately: `keywords_de`, `keywords_fr` 3. Do not transliterate English brand model codes—they stay as-is when universal False cognates hurt: "gift" in German means poison; English "fabric" vs French "fabrique" (factory). Require native review on high-risk words in titles. ## HTML and typography per locale Shopify and eBay descriptions in HTML need locale checks: - **Non-breaking spaces** before punctuation in French (` :`, ` ;`, ` ?`, ` !`) - **Accented characters** UTF-8 encoded in CSV - **Font and theme support** for all scripts if you expand beyond Latin alphabet later Mobile line breaks differ: German nouns are long; narrow screens wrap awkwardly if bullets are single long sentences. Prefer short clause bullets in DE/FR/IT. ## Legal and compliance text Warranty, GPSR economic operator info, CE markings, and safety warnings often require **legally reviewed** text per EU language—not AI paraphrase. Maintain a `legal_block_de`, `legal_block_fr` column populated from approved snippets, merged into descriptions via template—same text on every applicable SKU. Do not translate US-only claims ("FDA cleared") into EU listings without verifying equivalent compliance. ## Bulk CSV structure for five languages Example schema (abbreviated): ``` sku, title_en, title_de, title_fr, title_es, title_it, description_en, description_de, ..., material_en, material_de, ... (or material master + lookup table) ``` Alternative: one row per SKU per language (long format) with `locale` column—better for some importers, worse for human editing. Pick based on your upload tool. Validation rules per row × locale: - Required fields non-empty for published locales - Title length ≤ channel max - No English leftovers in non-English fields (spot-check with language ID tools) - Identical numeric specs across locales ## Quality gate before publish 1. **Automated:** encoding, length, banned terms, numeric spec equality across locales 2. **Native review sample:** 5 SKUs × 5 languages if budget allows; otherwise rotate language each batch 3. **Pilot listings** on Amazon DE, FR, ES, IT substores or Shopify Markets locales 4. **Customer service prep:** return reasons tagged by language to catch description gaps early Track `translation_version` in CSV. When English master changes, flag dependent locales stale—do not leave German describing old dimensions after English update. ## Common five-language mistakes **English keyword stuffing copied into all locales** — Policy and readability failure. **MT without post-edit on materials** — "Polyester" confused with "polyester satin" trade names. **Mixed languages in one field** — Title half English, half German. **Currency and VAT assumptions** in description prose — Keep pricing out of descriptions; use marketplace fields. **Unicode normalization** — é as one codepoint vs e + combining accent; search matching can break if inconsistent. **Ignoring RTL and future scripts** — Arabic and Hebrew need direction metadata in HTML if you expand beyond five Latin languages. ## RowExact-style bulk generation pattern When generating multilingual copy from one job: 1. Upload master CSV once 2. Map fact columns once 3. Run **locale passes** with locked templates per language 4. Export wide CSV for Shopify Markets or split files per Amazon marketplace 5. Completed rows freeze on pause/resume; locale additions should not regenerate finished EN-only rows unless revising all locales together Side-by-side review: show **master facts | EN | DE | FR | ES | IT** for the same SKU before export. ## Maintenance rhythm Languages are not a launch-day task. Schedule: - **Weekly:** sync new SKUs to all locales before first sale - **Monthly:** audit top-return SKUs for description mismatch across languages - **Quarterly:** refresh legal blocks when regulations update ## Checklist - [ ] Single master fact source per SKU - [ ] Per-locale titles respect channel character limits - [ ] Keywords researched per language, not translated blindly - [ ] Numbers, units, and dimensions consistent after localization - [ ] UTF-8 CSV; accents render correctly - [ ] Legal/safety text from approved snippets only - [ ] HTML typography checked per locale - [ ] Pilot publish per marketplace region - [ ] Translation version tracked when master catalog changes Writing product descriptions in five languages is a **data synchronization problem** dressed as a writing problem. Sellers who treat each locale as an export profile from the same fact row—not five independent creative exercises—ship faster with fewer returns and cleaner bulk uploads.