Skip to main content

Product translation

AI Product Translation for Ecommerce in 70+ Languages

Translate products into more than 70 languages Your brand voice survives translation

Titles, descriptions, SEO fields and attributes, translated against your own dictionary and tone settings, with Quality Guard rules that can hold a product back from export.

  • 70+ languages
  • Per-field translation rules

Key features

  • Teach the AI your terminology

    Your dictionary fixes how each term translates per language, and your tone, formality and per-language instructions apply to every run.

  • Hold back what fails a rule

    Quality Guard rules, such as a required translation or a length limit, can warn, skip a product or block its export, so a product that breaks one is not pushed.

  • Enrich and translate in one run

    Fill missing attributes and write the description first, so the translator has something worth translating.

Why it reads differently

Translation that knows the product

Most AI translates word-for-word. WISEPIM translates a product it already knows: its attributes, your terms and your tone.

  • Keep your brand voice

    Set your tone, formality per language and the terms that must translate one way, once. Every run applies them and translation memory keeps phrases consistent, so high-end fashion copy and technical B2B specs each read the way that trade writes.

  • Check before you publish

    Bulk translation is risky without a safety net. Translations save to the product, and Quality Guard rules can warn, skip or block a product at export when a translation is missing or breaks a rule. Read a sample per language before you push.

  • Enrich and translate in one workflow

    A thin product translates into thin product data in another language. Fill missing attributes and write the SEO description in the source language first, then translate the finished product in the same run.

How it works

Three steps to a translated catalog

Set the vocabulary once, translate in bulk, and check the result before you push it.

  1. 01

    Set up your vocabulary

    Add your terms to the translation dictionary, mark brand and product names to keep as they are, and set tone and formality per language.

    Every later translation is written against that vocabulary, not a generic one.

  2. 02

    Select and translate

    Pick the products, choose the target languages, and start. Titles, descriptions, SEO fields and attributes are translated in the background.

    The translations exist in WISEPIM; nothing has reached your storefront yet.

  3. 03

    Review and push

    Read the translations side by side in the product editor, and let Quality Guard rules hold back products that miss a translation or break a limit. Then push with an export, an automation or a catalog job.

    Only what you pushed is live in the new language.

Two translations of the same product

Generic AI tools translate words. WISEPIM translates a product it has the attributes for, so specs, units and certifications survive the trip.

Generic AI

Generic AI Translation

24 words

WISEPIM
AI Enhanced

WISEPIM Translation

39 words

Field
Generic AI

This jacket is made of real leather. It has a zip. The leather is soft. Good for cold weather. Available in black and brown.

WISEPIM

Crafted from premium full-grain Italian leather, this tailored jacket features a brushed antique brass YKK zip and silk-lined interior. The supple hand-finished leather develops a rich patina over time. Perfect for transitional seasons. Available in Midnight Black and Cognac.

Highlighted text was added during enrichment.

Brand voice preserved, technical specs accurate, SEO fields written for the market

What it costs, what it touches

One more language is one more run

Translation runs on the catalog you already have, for a few cents per product, and lands back in the same products your channels read.

  • A few cents per product

    You are charged per product per language on your plan's rate, so a second market costs what the first one did rather than a new quote.

  • Runs as a background job

    Queue a hundred products or a hundred thousand and keep working; the run reports back per product, not as one pass or fail.

  • Pushes to the webshop

    Magento gets names, descriptions and meta fields per store view, Lightspeed and CCV Shop get multilingual content, WooCommerce works through WPML or Polylang, and Shopify gets the translated title and description. No CSV in between.

  • SEO fields travel too

    SEO titles and meta descriptions are translated as their own fields, and Magento store views receive them, so a market page there is not left with source-language metadata.

Fast costs one credit per language and Pro costs five, and both run against your glossary and translation settings in full.
Global Coverage

Every major market in its own language

Reach customers in their own language across every major market. WISEPIM handles local nuances, regional formatting, and SEO optimization for local search engines.

Europe & Eurasia

93+
Languages
4
Regions
195+
Countries

Your products, understood everywhere

Reach customers in more than 70 languages without losing what makes your brand unique. WISEPIM localizes your products with brand voice, technical accuracy, and cultural context built in.

How it works

How AI product translation works in WISEPIM

Product translation is not one long text. It is short, repetitive fields full of brand names, units and terms that must come out the same every time.

WISEPIM translates each product field by field into every language you set up for the project, and stores each language separately on the product. Each run reads your translation settings (tone, formality, per-field rules and your dictionary) and checks its own translation memory, so a phrase that was translated one way last month comes out the same way today.

The source is the best version of the copy you have. When a field has enriched or reviewed content, translation uses that instead of the raw supplier text, which is why enriching before translating pays off twice. Fields where the model hands back the source text unchanged are dropped instead of saved, and when one of your content rules fails, the translation is retried once with that rule spelled out.

Runs happen in the background as a task, per product and per language, so you can queue a whole catalog and keep working. A language is skipped for a product when it was translated recently from the same source text with the same settings, and translated again as soon as the source changes.

Languages and locales

More than 70 languages, with regional variants kept apart

WISEPIM supports 94 language and region codes. Regional variants are translated and stored as their own language, not as a copy of the parent.

Regional variants WISEPIM keeps separate
LanguageRegional variantsWhy it matters
EnglishUS, UK, Canada, Australia, New Zealand, Ireland, South AfricaSpelling (color or colour), sizes and units differ per market
SpanishMexico, Argentina, Colombia, Chile, Peru, VenezuelaVocabulary and forms of address differ from Spain
FrenchCanada, Belgium, SwitzerlandProduct terms and number formats differ from France
GermanAustria, SwitzerlandSwiss German spelling has no ß
DutchBelgiumFlemish word choice differs from the Netherlands
Portuguese and ChineseBrazil; Traditional Chinese (Taiwan)Different vocabulary, and a different script for Chinese
ItalianSwitzerlandSwiss Italian conventions
Every plan includes every language, with no language add-ons. You pay for translation in AI credits.

What gets translated

Which fields translate, and which stay as they are

Translation covers the copy a shopper reads. Codes, numbers and identifiers stay untouched.

Product data and how translation treats it
DataTranslatedNotes
Name and long nameYesBrand and model names can be protected from translation
Description and short descriptionYesHTML and list formatting are kept
Meta title, meta description, meta keywordsYesEach is its own field, so a market page does not keep source-language metadata
Product FAQsYesQuestions and answers per language
Text attributesYesText and long-text values; placeholders such as N/A are skipped
Select and multi-select optionsLabels onlyOption labels and attribute names are translated where a label is missing
Numbers, codes and identifiersNoSKU, EAN, prices and numeric values stay exactly as they are
Category names, descriptions and FAQsYes, separatelyThrough category translation, 1 credit per category per language
Image alt textNoAlt text is not stored per language today
Product data and how translation treats it

Before the first run

Set up translation in six steps

Thirty minutes of setup decides whether the first market reads like your brand or like a dictionary.

  1. 01

    Add the project languages

    Add each target language or regional variant under Settings > General. Translation only offers languages the project has.

  2. 02

    Choose Fast or Pro

    Fast costs 1 credit per product per language and is the right default. Pro uses a much larger model at 5 credits per product per language, for lines where nuance or technical precision really matters.

  3. 03

    Decide on strict mode

    Strict mode is on by default and translates close to the source with no style changes, which suits technical and regulated products. Turn it off to set a tone of voice and a style from literal to creative.

  4. 04

    Set formality per language

    Choose formal, informal or neutral address per language, such as du or Sie in German, and add instructions for one language only, such as British spelling.

  5. 05

    Fill the dictionary

    Add the terms that must translate one way, with a translation per language and context for ambiguous words, and mark brand and product names to keep as they are.

  6. 06

    Add field and category rules

    Switch translation off for fields you keep in one language, cap a field's length, and give a category its own terminology notes, such as technical terms for tools and a lighter tone for toys.

Units can stay as they are, be converted to the target market's standard, or be shown both ways. Brand names and formatting are preserved by default.

Terminology

Keep your terms the same in every language

Inconsistent terms are the most visible sign of machine translation. WISEPIM has four tools against them.

  • The dictionary

    Source terms with a fixed translation per language, optional context, and a keep-as-is flag for names and codes. Entries can apply to the whole project or to chosen categories.

  • Bulk edit and import

    Edit many terms as text, or import a file. Before anything changes, WISEPIM shows how many terms are new and how many update existing entries.

  • Translation memory

    Phrases already translated come out the same way across products, chunks of a large run and runs weeks apart.

  • Auto-learn from reviews

    Switch it on and confident findings from a linguistic review become dictionary entries. It never overwrites terms you added yourself. Off by default.

Native-speaker feedback usually arrives as a spreadsheet or a marked-up document. Ingest feedback reads such a file (Excel, PDF, Word or text, up to 20 MB), compares it with your current settings and proposes setting changes, conflicts to resolve and corrected terms. Nothing changes until you apply the suggestions.

Running it

Translate a selection or the whole catalog

The same run works for ten products or a filtered catalog of tens of thousands.

  1. 01

    Select the products

    Tick products on the grid, or filter (for example by category or brand) and apply to all matching products.

  2. 02

    Open Enrich with AI and choose Translation

    Pick the fields to translate and the mode. The languages are the ones set up for the project.

  3. 03

    Start and keep working

    The run appears in the process tracker with progress per product. Credits are reserved when it starts; if the balance does not cover the whole selection, it translates the products it can afford and says how many.

  4. 04

    Recover a stopped run

    Resume finishes only the products that were never processed, at no extra cost. Retry failed reruns the failures. Translations that fail are refunded.

To translate without starting runs by hand, add a translate step to an automation, for example after every product import. The Translate a shop catalog job goes further: it translates a whole storefront with a quality hold and a review step before it exports to WooCommerce or a file.

Checking the result

Review translations before a market sees them

Standard translation runs save straight to the product. These are the places to check them before you publish:

  • Language switch and language columns on the product grid, to read a target language or several languages side by side.
  • Side-by-side comparison in the product editor, source and translation next to each other, editable in place.
  • Translation coverage per product, as a grid column and on the product's summary card, so you see which fields are fully, partly or not yet translated.
  • Linguistic review, an AI check of translated products per language that scores them and exports a report, at 1 credit per product per language.
  • Quality Guard rules, such as "a translation exists for German" or a length limit, which can warn, skip a product or block its export. See Quality Guard.
  • A sample read by a native speaker for every new market. Feed what they find back through the dictionary or Ingest feedback, so it is fixed for every later run.

Getting it live

What each channel receives

Translations live in WISEPIM first. How much of them reaches a storefront depends on the connector.

How translated product content reaches each channel
ChannelWhat is sentWhat to know
ShopifyTitle and description per mapped Shopify languageSent through Shopify's translations API. SEO fields and options are not sent as translations today
Magento 2 and Adobe CommerceName, description, short description and meta fields per store viewMap each WISEPIM language to a store view
WooCommerceTranslated products through WPML or PolylangOnly after the shop passes WISEPIM's language check
Lightspeed and CCV ShopMultilingual product contentLanguages that match the shop's languages
PrestaShop and ShopwareOne languageThese connectors write a single language
AkeneoNot sent backThe Akeneo export does not send a locale, so translations stay in WISEPIM
CSV and ExcelExtra languages as separate columnsSet in the export template, for channels without a connector
AI translation runs do not trigger auto-sync. Push translated products with a manual export, an automation or a catalog job.

Credits and plans

What translation costs

Translation is charged per product per language, so a market's cost is easy to work out before you start.

  • Fast: 1 credit per product per language. 2,000 products into three languages is 6,000 credits.
  • Pro: 5 credits per product per language. The same run is 30,000 credits, so most teams use Pro only for selected lines.
  • Categories: 1 credit per category per language.
  • Option labels and attribute names: 1 credit per batch of up to 50 labels.
  • Linguistic review: 1 credit per reviewed product per language.
  • No charge for skipped or failed work: unchanged products are skipped, and failed translations are refunded.
WISEPIM plans, products and AI credits
PlanProductsAI credits per monthPer month, billed yearlyPer month, billed monthly
Free10050€0€0
Lite5002,000€119€149
Starter1,0004,000€299€399
Starter Plus2,50010,000€399€529
Growth5,00020,000€499€649
Growth Plus7,50030,000€599€779
Business10,00040,000€699€899
Business Plus15,00055,000€849€1,099
Scale20,00070,000€999€1,299
Scale Plus30,000100,000€1,149€1,499
Pro40,000120,000€1,299€1,699
Pro Plus50,000150,000€1,499€1,949
Prices in euros, excluding VAT. Every plan includes every language; heavy translation uses more AI credits, and Pro uses more than Fast.

International SEO

Translated pages still need to be found

A translated product only earns traffic when search engines can tell the language versions apart.

Translate the meta title and meta description as their own fields, not just the description. A product page in German with an English search snippet loses the click even when it ranks. Where your channel accepts translated meta fields, such as Magento store views, WISEPIM sends them along.

Language versions of a page are tied together on your storefront with hreflang annotations, and Google is clear that every version must list itself and all the others. That is a storefront setting, not something product data controls, so check it with your shop platform when you open a market.

Finally, machine-written does not mean unchecked. Google's guidance on AI-generated content asks for accuracy and real value, and a native speaker's read of a sample in each new language is the cheapest way to meet it. Browse what is involved per market in the translation language directory.

Sources

Search and platform facts on this page

Search guidance and platform facts come from Google's and Shopify's own documentation, checked in October 2026.

FAQs

Product translation: frequently asked questions

Cost, quality control, and what actually gets translated.

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

WISEPIM translates products into more than 70 languages, across 94 language and region codes, so regional variants such as Belgian Dutch or Canadian French are stored as their own language. Each translation follows your dictionary, tone and formality settings, and SEO fields are translated as their own fields. It does not create a new storefront for you, so the language has to exist on the channel you sync to.

Quality Guard rules check products against your standards, for example that a German translation exists or that a field stays within a length limit. A rule can warn, skip a product or block its export, so a product that fails is not pushed until you fix it. Translation runs save straight to the product, so Quality Guard acts at export rather than as an approval step.

In the translation settings. The dictionary holds the terms that must translate one way, with a translation per language and a keep-as-is flag for brand and product names. Tone, formality and extra instructions are set per language. The Knowledge Library steers AI enrichment of your source copy; the translator works from the dictionary and these settings.

WISEPIM charges a few cents per product per language, at the rate on your plan, and the pricing page has the exact figure. Agencies typically quote per word or per product and expect a review cycle. The two are not the same product: WISEPIM gives you a first pass you review yourself, not a human translator's sign-off.

Yes. Missing attributes and SEO descriptions can be generated first and translated in the same automated workflow, so you are not translating a half-empty product. You can also run the two separately if you want to approve the source copy first.

Product titles, descriptions, short descriptions, SEO titles, meta descriptions, product FAQs and text attributes. You switch translation off per field and add instructions per target language. SKUs, EANs, prices and other numbers are never translated, and brand names are kept as they are by default.

Not automatically. Translation runs do not trigger auto-sync; you push translated products with a manual export, an automation or a catalog job. Magento receives names, descriptions and meta fields per store view, Lightspeed and CCV Shop receive multilingual content, WooCommerce works through WPML or Polylang after WISEPIM's language check, and Shopify receives the translated title and description.

Translations run in the background as a queued job, so you keep working while the catalog is processed and each product reports back on its own. How long a run takes depends on how many products and languages you queued.

AI product translation uses a language model to translate product titles, descriptions, SEO fields and attributes into other languages, field by field. WISEPIM adds your dictionary, translation memory, tone and formality settings, so the same terms come out the same way across the catalog.

Yes. Brand names are preserved by default, and dictionary entries marked keep as-is are passed to the AI as terms to leave unchanged. Check them in your first sample, because the dictionary guides the model rather than overriding every word after the fact.

Standard runs save translations to the product straight away, so review happens afterwards in the product grid and editor, with Quality Guard able to hold a product back from export. The Translate a shop catalog job adds a quality hold and a review step before it exports.

Fast uses 1 credit per product per language and handles normal product copy well. Pro uses a much larger model at 5 credits per product per language, for luxury, regulated or technical lines where nuance matters. Both use your dictionary and settings.

You set formality per language: formal, informal, neutral or default. That covers choices such as du or Sie in German and je or u in Dutch. A project has one setting per language, so you cannot keep two registers of the same language side by side.

Yes, separately from products. Category names, descriptions, meta fields and FAQs translate through category translation at 1 credit per category per language, and translated categories go to shops that support languages.

Next step

Pick one marketand translate the catalog

Set the vocabulary once, run the first language, and read a sample before anything reaches a storefront.

4.7