Translate PrestaShop Products in Bulk: 5 Methods Compared
You added a language in the Back Office, and now every product page shows the default-language text or empty fields. With 40 products you could retype them. With 4,000 you need a method. This guide compares the five realistic ways to translate a PrestaShop catalog in bulk, shows what each one covers and where it breaks, and ends with a checklist and a cost formula you can run before spending anything.
Disclosure: we make LATW Cloud, which is one of the options below. The other methods are described from their public documentation, not from our own testing.
Key Takeaways
- Translating “products” means more than descriptions: names, short descriptions, meta fields, friendly URLs, categories, features and attributes all live in separate language fields.
- PrestaShop’s CSV import works one language per file, so it is workable but fiddly. Modules, PIM tools and AI services remove the file juggling at different price points.
- Estimate cost before any run: words per product × products × target languages.
- Always test on a staging copy and spot-check a sample before translating the full catalog.
What does “translate products in bulk” actually include?
A product in PrestaShop is not one block of text. Each of these fields is stored per language, and an empty one falls back to nothing useful for the shopper or for search:
- Name, short description and long description (usually HTML)
- Meta title and meta description
- Friendly URL (the “Rewritten URL” field, set per language)
- Categories (name, description, meta, URL)
- Features and their values, attributes and their values (size, color)
- CMS pages and other store content
PrestaShop’s own SEO documentation asks you to fill in the rewritten URL for every language on the shop (PrestaShop docs: SEO & URLs). A bulk method that skips slugs and meta fields leaves those fields in the source language even though the visible descriptions are translated.
Which methods exist, and how do they compare?
| Method | Best for | Covers | Main catch |
|---|---|---|---|
| 1. Manual in Back Office | Under about 50 products | Everything, one field at a time | Time grows linearly with catalog size |
| 2. CSV export/import | One extra language, technical owner | Fields you put in the file | One language per file, separators, HTML care |
| 3. Translation module | Staying inside the Back Office | Depends on module (fields, queue) | Check overwrite behaviour and field coverage |
| 4. PIM or translation platform | Catalogs fed from a central system | Product data, sync to shops | Extra system to run and pay for |
| 5. AI service with a PrestaShop connector | Whole catalog, several languages | Products, pages and SEO titles, per the vendor | Needs QA sampling like any machine translation |
Method 1: Manual translation per product
The baseline: open a product, switch the language selector, paste or type each field. It gives you full control over every word and is a reasonable choice for a handful of flagship products. It does not scale, and a half-finished run leaves a mixed-language catalog.
Method 2: CSV export and import
PrestaShop documentation checked November 2026 (v8 user guide); importer options can differ between 1.7, 8 and 9.
PrestaShop ships an importer under Advanced Parameters > Import. According to the official import documentation:
- Data is imported one language at a time, so multi-language data must be split into separate files, and the target language must already be installed.
- The docs recommend a semicolon as field separator, while the multiple-value separator defaults to a comma.
- Files are expected in UTF-8 (otherwise ISO-8859-1).
- For products, “Use product reference as key” lets you match rows by reference instead of PrestaShop’s internal ID, and “Force all ID numbers” controls whether imported IDs are kept.
A typical workflow is: export the default-language catalog, translate the text columns in a spreadsheet or through a translation service, set the importer to the new language, and import with the reference as the key.
Pitfalls to plan for
- Row matching. Match on product reference, not on a row position. A re-sorted spreadsheet will otherwise write text to the wrong product.
- Separators inside text. The docs note that semicolons in your text clash with the field separator. Descriptions full of semicolons need careful quoting.
- HTML in descriptions. Long descriptions often contain tags. Whatever translates the file must leave tags and attributes untouched. The documentation does not discuss HTML handling, so check a few imported products visually.
- Friendly URLs. If the link_rewrite column (the database name of the Rewritten URL field) is left in the source language, translated pages keep source-language slugs. If you translate it, make sure the result is URL-safe and unique.
- Features, attributes and combinations. These are typically separate imports with their own columns, so plan several passes.
- No safety net. A wrong import overwrites live data. Back up the database first and run the import on a staging copy.
CSV is free and transparent, and it pairs well with an outside translation step. The cost is your time spent on file preparation for every language and every update.
Method 3: Translation modules inside the Back Office
Several modules translate directly from the admin. Webkul’s AI Locale Translator is a documented example. Its store page lists 26 content types, including products, categories, pages, attributes and features, lets you choose the exact fields, supports immediate or background jobs (the page’s example runs every 30 minutes), and connects to AI providers with your own API key. As of November 2026 the page shows $59.00, with installation as an $11.80 add-on. The page does not say whether existing translations are overwritten, which is the first thing to ask before running it on a live catalog.
Crowdin offers a different route: its PrestaShop app requires installing a separate PrestaShop module, then syncs store content to Crowdin manually or on a schedule (daily by default, per the listing). It suits teams that already use a translation management workflow with reviewers.
When evaluating any module, check:
- Field coverage: are meta fields and friendly URLs included, or only descriptions?
- Overwrite rules: can it skip fields that are already translated?
- Queue behaviour: does a large catalog run in the background, and what happens on a timeout?
- Where processing happens: on your server (can hit PHP limits) or externally.
- Cost model: one-off license plus your own AI key usage, or a subscription.
Our separate comparison goes deeper: PrestaShop translation modules compared.
Method 4: A PIM or translation platform
If product data already flows from a PIM, translate there and push to the shop. WISEPIM describes itself as an AI PIM that writes, translates and checks product data and syncs it to shops and marketplaces, with a free plan up to 100 products (as of November 2026). The pages we read list other shop platforms and generic CSV, Excel, XML and API exchange, and do not mention PrestaShop, so confirm a connector exists before committing.
A PIM makes sense when you sell across several channels and need one source of truth. For a single PrestaShop store, it can be more system than the problem needs.
Method 5: An AI service with a PrestaShop connector
Here a hosted service reads your catalog through a connector, translates in the background and writes the results into PrestaShop’s own language fields. LATW Cloud is one such service, and its PrestaShop module is available now for PrestaShop 1.7.8, 8 and 9 (PHP 7.2 or later; friendly URLs must be enabled).
How it works, per the LATW Cloud page:
- Download the module zip from your LATW account and upload it in Modules > Module Manager.
- Open International > LATW Cloud, click “Connect with LATW” and approve the store.
- Pick languages, quality class, glossary and prompt in the LATW panel.
- See an estimate, then run. Translation happens on LATW servers, so you can close the tab.
Things worth knowing before you choose it:
- Billing is per word, counted after HTML and shortcodes are removed, once per target language. You see an estimate first and are billed per word and never more than the estimate.
- Prices (as of November 2026, checked on latw.ai/cloud): per 1,000 words into one language on Pay as you go, Economy is $0.0234, Standard is $0.468 and Premium is $2.34. There is no monthly fee on that plan, and the minimum Credits top-up is $5. Paid plans make Credits cheaper rather than gating access.
- The first connected site gets 10,000 free words on Economy to try it.
- Covers: the LATW Cloud page lists products, pages, menus, strings and SEO titles, and says translated URLs, hreflang and sitemaps are handled natively. Ask the vendor or check the docs for the exact PrestaShop field list (for example meta descriptions and category attributes) before a full run.
- Not covered: page-builder content and texts stored in module settings, such as banners and custom text blocks. Old-style module translation files are not listed either.
- Your store keeps the translations. Uninstalling the module removes only the connection.
- Firewalls: the store must allow requests to its
/latw/v1/cloud/path and the final store address must not redirect.
Like any machine translation, the output needs a sample review. Quality classes (Economy, Standard, Premium) and glossaries help you tune cost against care. For the end-to-end store walkthrough, see translate a PrestaShop store with AI, and for online shops generally, AI translation for ecommerce websites.
A neutral note on alternatives: Weglot has a PrestaShop integration page that describes no-code install, machine translation from DeepL and Google, hreflang tags and translated metadata. Check its current plans on that site and compare how translations are stored before choosing.
How much will a bulk translation cost?
Use one formula for every method:
words per product × number of products × number of target languages = total words
Worked example (illustrative numbers, not a quote): a shop with 2,000 products averaging 150 translatable words each (name, descriptions and any SEO fields you include), translated into 3 languages:
150 × 2,000 × 3 = 900,000 words
At the Pay as you go rates above (as of 6 November 2026), the figures below price only LATW Cloud. For a module such as Webkul’s, add the license fee and your own AI provider usage; for CSV, add your own hours:
- Economy at $0.0234 per 1,000 words: 900 × $0.0234 = $21.06
- Standard at $0.468 per 1,000 words: 900 × $0.468 = $421.20
Your real figure depends on your word count, so take the average from a real export rather than guessing. For the cost logic behind AI translation, see what AI translation costs and batch API cost for whole-site translation. If you are picking an engine, DeepL vs ChatGPT for website translation is a useful read.
Checklist: translate a PrestaShop catalog safely
Before you start
- Back up the database and files, and work on a staging copy.
- Install the target languages under International and confirm friendly URLs are on.
- Export the catalog and count words to run the formula above.
- Build a glossary: brand names, product lines and terms that must stay untranslated.
During translation
- Include name, short and long description, meta title and description, and the rewritten URL.
- Include categories, features, attributes and their values, and CMS pages.
- Keep SKUs, units, sizes and placeholders intact, along with HTML tags.
- Choose whether existing translations are skipped or overwritten, and set it deliberately.
After translation
- Review a sample of 20 to 30 products across categories, including some with long HTML descriptions and some with many attributes.
- Check translated URLs resolve, with no duplicates or broken characters.
- Confirm each language version links to its alternates with hreflang. PrestaShop’s docs for friendly URLs do not cover this, so verify what your theme or module outputs, and see Google Search Central on localized versions for how hreflang annotations should look.
- Submit the updated sitemap and watch search console for errors.
- Decide how new products will be translated from now on.
Which method should you pick?
- Under 50 products, one language: manual, or a small CSV round trip.
- A few hundred products, one extra language, technical owner: CSV import with a careful matching key.
- Large catalog, you want control inside the admin: a translation module, after checking field coverage and overwrite rules.
- Multichannel with a central product database: a PIM.
- Whole catalog, several languages, minimal setup: an AI service with a connector, such as LATW Cloud, or another connector-based service.
To see how a connector handles your own store, the first connected site gets 10,000 free words on Economy. Details are on the LATW Cloud page.
Frequently asked questions
Can I translate PrestaShop products without a module?
Yes. Use the built-in importer: export products, translate the text columns, install the target language, and import with one language per file. It is free but manual for every language and update.
Does PrestaShop translate product descriptions automatically?
Not out of the box. Core handles interface and module strings through its translation tools, which the official docs describe as covering interface and module text, not your product content. Product content needs a module, a service or an import.
What happens to translations if I stop using a tool?
It depends on where the translations are stored. With tools that write into PrestaShop’s language fields, they stay in your database. With hosted layers that serve translations themselves, check the vendor’s terms. For LATW Cloud, uninstalling the module removes the connection only.
Do I need to translate friendly URLs?
It is worth doing. PrestaShop sets the rewritten URL per language, and its documentation asks you to fill it in for every language. Translated slugs keep the address readable for shoppers in each language.
How do I add a new language to existing products?
Install the language under International, then fill its fields using one of the methods above. Untranslated products fall back to empty or default-language text, so run a bulk method rather than waiting for orders to reveal gaps.