PrestaShop Translation Module: 3 Types and How to Choose
Adding a language to PrestaShop is a few clicks. Getting 500 products, your categories and your CMS pages into that language is the real job. A PrestaShop translation module is meant to do that job for you, but modules work in very different ways, and the differences decide what you pay, what you keep and what breaks on big catalogs.
This guide sorts modules into three types, lists what to check before you buy, and walks through a cost example with stated assumptions. We make LATW Cloud, so weigh our view accordingly. It is one of the three approaches below, and we say where the others fit better.
Key Takeaways
- PrestaShop translation modules fall into three types: a live front-end layer, an AI module that runs on your own API key, and a hosted engine that writes translations into your shop.
- The question that matters most is where the translations live, and whether they are still there if you stop paying.
- For big catalogs, check for background processing, cost visibility before a job starts, a glossary, and translated URLs with hreflang.
- Costs differ in shape, not just size: a monthly plan, a one-off licence plus AI usage, or pay per word.
What PrestaShop does on its own
PrestaShop lets you add a language under International > Localization and then edit the interface texts under International > Translations in the back office. PrestaShop’s documentation lists what that page covers: back office, theme, installed modules, emails and other strings.
It does not translate your product names, descriptions, category pages or CMS pages. Those are content, stored per language, and you fill them in one by one in the catalog. With 20 products that is fine. With 2,000 products in three languages it is a very long stretch of copy-paste, which is why people look for a module.
The three types of PrestaShop translation module
1. Front-end layer (Linguise-style)
These tools sit between your shop and the visitor. Your catalog stays in one language, and the visitor sees a translated version served by the vendor.
Linguise is a good example. Its PrestaShop page says it “has a remote cache system and does not duplicate any content on your local database”, and that it generates translated URLs and alternate links, and its FAQ describes hreflang support (as of October 2026). Per the same page, setup is uploading a PHP script to your server root and entering an API key.
Where it fits: you want translated pages live quickly with little setup, and you are happy to keep the translations with a vendor. The trade-off: the translations are not in your database. Linguise’s pricing page says “an active plan is required to give translations to your customers” (as of October 2026). Check with the vendor what happens to your translated pages if you cancel.
2. AI module with your own API key (Webkul-style)
These modules install in the shop, call an AI provider with a key you supply, and store the results in your shop. You pay the module once and the AI provider for usage.
The Webkul AI Locale Translator is an example. As of October 2026, its listing says it translates 26 types of store content, supports PrestaShop 9.x, 8.x and 1.7.x, and connects to providers such as OpenAI, Google Gemini, Anthropic, OpenRouter, Cerebras and DeepSeek, or to a model you host yourself. It can run on a schedule, for example checking for waiting jobs every 30 minutes.
Where it fits: you want to pay the AI provider directly and are comfortable managing keys. The trade-off: you manage the keys, the provider limits and your server’s capacity. The product page does not mention a glossary, so check that before you buy if brand names matter.
3. Hosted engine that writes into PrestaShop (LATW Cloud)
Here the AI work runs on the vendor’s servers, and the module writes the finished translations into your shop natively. LATW Cloud works this way. You install a free module, connect the shop, pick languages and a quality class, and the job runs in the background on LATW servers. You can close the tab.
What this type gives you:
- Ownership. Translations are saved natively in your shop and stay if you stop paying.
- Cost shown first. Each job shows an estimate before it starts, and you pay what it showed.
- Control. A glossary for brand names and untranslated terms, plus custom prompts for tone.
- No timeouts. Large catalogs run off your server, so PHP time limits do not apply.
- SEO handled natively. Translated URLs, hreflang and sitemaps.
Where it fits: large catalogs, ownership of the result, and cost you can see before you commit. The trade-off: your content goes to a hosted service for processing, and the models are currently OpenAI’s (Claude and Gemini are listed as coming soon). If you would rather pay an AI provider directly, type 2 is a better match. If you want zero setup on the front end, type 1 is.
| Front-end layer | Own-key module | Hosted engine | |
|---|---|---|---|
| Example | Linguise | Webkul AI Locale Translator | LATW Cloud |
| Translations live | On the vendor’s cache | In your shop | In your shop |
| AI cost | Inside a monthly plan | Your AI provider, billed to you | Per word (Credits) or your own key on a paid plan |
| Tool price (October 2026) | From $15 a month | $59.00 one-off, excluding optional add-ons | $0 a month on pay as you go |
| Best fit | Fast live pages, little setup | Direct provider billing | Big catalogs, ownership, cost shown first |
Seven things to check before you buy
- Where do the translations live? In your database, or on the vendor’s server? Ask what you keep if you cancel.
- Background or synchronous? A big catalog run inside one web request can hit PHP time limits. Look for queued, resumable jobs.
- Can you see the cost before a job runs? Per-word, per-token and per-plan pricing behave very differently on a 2,000-product store.
- Is there a glossary? Brand names, SKUs, sizes and product-line terms should not be translated. A glossary should be reusable across jobs.
- Tone and prompts. Can you set a voice, such as friendly and informal, once and reuse it?
- SEO output. Translated friendly URLs, hreflang tags and sitemap entries. Google’s guidance is to tell it about every language version with hreflang, and each version should list itself and all the others. For background, see our guide to international SEO for translated sites.
- Version and multistore support. Confirm your PrestaShop version and, if you run several shops, that the module handles them. Not every vendor page states this, so ask.
For a wider view of tools beyond PrestaShop, see our overviews of AI translation for ecommerce websites and multilingual website translation software.
A worked cost example
Costs are easiest to compare on one example. These are our assumptions, not a benchmark:
| Content | Count | Words each | Words |
|---|---|---|---|
| Products | 500 | 120 | 60,000 |
| Categories | 30 | 60 | 1,800 |
| CMS pages | 10 | 400 | 4,000 |
| Per language | 65,800 |
Translate into 3 languages and the total is 65,800 × 3 = 197,400 words. Real stores vary, so replace the counts with your own. Our team checked the prices below on 27 October 2026. LATW prices exclude VAT; check how VAT applies to the other two.
LATW Cloud, pay as you go. The LATW Cloud page lists $0.0234 per 1,000 words on Economy (GPT-6 Luna), $0.468 on Standard (GPT-6 Sol) and $2.34 on Premium (GPT-6 Astra), as of October 2026.
| Quality class | Cost for 197,400 words |
|---|---|
| Economy | $4.62 |
| Standard | $92.38 |
| Premium | $461.92 |
Top-ups start at $5, Credits do not expire, and there is no monthly fee on the pay-as-you-go plan. Pick the class by content: a model that is fine for blog-style text may not be what you want for legal pages. Translate one page first and judge it.
Webkul module, own key. The listing price was $59.00 as of October 2026, a one-off amount (optional install and support add-ons cost extra), plus whatever your AI provider charges for the same 197,400 words. We have not put a figure on that, because it depends on the model and provider you pick.
Linguise. As of October 2026, its pricing page lists Start at $15 a month for 200,000 translated words on one website. It says the limit counts the words of your pages multiplied by the number of languages. Our example, at 197,400 words, would sit just under the Start limit, and the plan renews monthly because the translations are served while it is active.
The shapes differ more than the totals: one-off per job, one-off licence plus usage, or a recurring plan. Which is cheaper depends on how often you re-translate and how long you keep the shop. For more on pricing mechanics, read about how Batch API pricing works and what AI translation costs.
Which type should you pick?
- Choose a front-end layer if you want the quickest route to translated pages and accept that the translations stay with the vendor while you pay.
- Choose an own-key module if you want to pay the AI provider directly and are happy to manage keys and server load.
- Choose a hosted engine if you have a large catalog, want to see the cost first, and want the translations stored in your own shop.
Whatever you choose, AI output needs a quick review on your highest-traffic pages. Our notes on AI translation quality, prompts for website translation and a localization checklist help with that step.
Frequently asked questions
Does PrestaShop translate product descriptions on its own?
No. The built-in tools under International > Translations cover interface and module texts. Product, category and CMS content is entered per language in the catalog, so it stays manual without a module.
Will translations stay if I stop paying?
It depends on the type. A module that writes into your shop database keeps them. A front-end layer serves translations from the vendor, so ask what happens on cancellation. With LATW Cloud the translations are saved natively in your shop and stay.
How do I protect brand names and SKUs?
Use a module with a glossary, and add brand names, product lines and untranslated terms before the first big job. Then translate one page and check it.
Do I need an AI API key?
Not for every type. Own-key modules require one. LATW Cloud does not: you pay per word with Credits, or you can use your own key on a paid plan.
Try it on one page
If you want to test the hosted approach, connect your store to LATW Cloud for free, translate one page, and judge the result yourself. A small top-up, starting at $5, covers a test, and no subscription is required. See LATW Cloud.