Multilingual and Multicurrency PrestaShop: Necessity and Benefits
Configuring a multilingual and multicurrency PrestaShop—catalog translation, auto-update of exchange rates, correct hreflang—is critical for entering foreign markets. For example, a client with a catalog of 5000 products added Polish language and złoty—conversion increased by 25%. But incorrect hreflang setup and content duplication could have ruined SEO. We solved both issues comprehensively. Multilingualism is not only about interface translation: it includes correct URLs for search engines, proper price formatting, and automatic exchange rate updates. An error at any stage leads to customer loss and ranking drops. Let's dive into the technical details, typical mistakes, and ready-made solutions for PrestaShop online stores.
Problems We Solve
- Incomplete translations: products, categories, CMS pages—everything must be localized. Otherwise, language mixing in the admin and storefront occurs.
- Incorrect price display: number formatting and currency symbols depend on locale. Example: 1 299,99 ₽ for ru-RU, $1,299.99 for en-US.
- Manual exchange rate updates: currency volatility requires automation. A 0.1% rate error on a 10 million ruble turnover means a 10,000 ruble loss. Automated updates reduce errors by over 90% compared to manual entry.
- SEO penalties from duplicate content: without correct hreflang and language-specific URLs, Google may treat pages in different languages as duplicates.
Step-by-Step Setup Process
- Install and activate languages via admin or CLI, then install language packs for interface translation.
- Configure URL strategy: choose prefix based URLs (e.g., /en/, /ru/) for best SEO.
- Add hreflang tags using the displayHeader hook with alternate links for each language, including x-default.
- Set up currencies: add target currencies programmatically or via admin, configure exchange rate provider.
-
Automate rate updates with a cron job running
php bin/console prestashop:currencies:update-exchange-ratesevery 6 hours. - Translate catalog content using CSV export/import or automatic translation modules (CSV is 5x faster than manual translation for bulk products).
- Verify SEO components: check meta tags, sitemaps, and canonical URLs for every language.
Adding Languages
Languages in PrestaShop correspond to PHP locales and are supplied with language packs. Installation via CLI:
php bin/console prestashop:language:install ru-RU Or programmatically via the Language object:
$language = new Language(); $language->name = 'Русский'; $language->iso_code = 'ru'; $language->locale = 'ru-RU'; $language->language_code = 'ru-RU'; $language->date_format_lite = 'd.m.Y'; $language->date_format_full = 'd.m.Y H:i:s'; $language->is_rtl = false; $language->active = true; $language->add(); After activating a language, you must translate:
- Interface (back-office, front-office) — via language packs.
- Catalog content — via CSV import or programmatically.
URL Strategy for Multilingual SEO
PrestaShop supports several strategies:
| Strategy | URL | Recommendation |
|---|---|---|
| GET parameter | /product?id_lang=2 |
Avoid—bad for SEO |
| Language prefix | /ru/product |
Best option |
| Subdomain | ru.example.com |
Requires Multishop |
| Separate domain | example.ru |
Most complex, but maximum E-A-T |
The prefix strategy is 3 times more effective than GET parameters for ranking—confirmed by Google Search Central. Configure in admin: International → Localization → add language prefix. For Nginx, add rewrite rules (e.g., rewrite ^/ru/(.*)$ /$1?id_lang=2 last;).
Adding hreflang via the displayHeader hook:
public function hookDisplayHeader(): string { $languages = Language::getLanguages(true); $currentController = $this->context->controller; $hreflangs = []; foreach ($languages as $lang) { $url = $this->context->link->getLanguageLink($lang['id_lang']); $hreflangs[] = sprintf( '<link rel="alternate" hreflang="%s" href="%s">', $lang['language_code'], $url ); } $hreflangs[] = '<link rel="alternate" hreflang="x-default" href="' . $this->context->link->getLanguageLink(Configuration::get('PS_LANG_DEFAULT')) . '">'; return implode("\n", $hreflangs); } Configuring Currencies
PrestaShop stores all prices in the base currency. Adding a currency programmatically:
$currency = new Currency(); $currency->name = 'Polish złoty'; $currency->iso_code = 'PLN'; $currency->iso_code_num = '985'; $currency->sign = 'zł'; $currency->conversion_rate = 0.21; // relative to base (EUR) $currency->decimals = 2; $currency->active = true; $currency->add(); Automatic exchange rate updates: use the built-in provider or write a custom one (example with the Central Bank of Russia). Set up a cron job to run php bin/console prestashop:currencies:update-exchange-rates every 6 hours.
Price Formatting by Locale
Each currency is formatted via CurrencyFormatter:
use PrestaShop\PrestaShop\Core\Localization\Locale\Repository as LocaleRepository; $locale = $localeRepository->getLocale('ru-RU'); $formattedPrice = $locale->formatPrice(1299.99, 'RUB'); // → "1 299,99 ₽" $formattedPrice = $locale->formatPrice(99.99, 'EUR'); // → "99,99 €" Why Automate Exchange Rate Updates?
Manual exchange rate updates risk errors and profit loss. PrestaShop's built-in provider uses the European Central Bank, but you can connect any API. Comparison of popular providers:
| Provider | Update Frequency | Free Limit | Currency Support |
|---|---|---|---|
| European Central Bank | Daily | Unlimited | 32 currencies |
| Central Bank of Russia | Daily | Unlimited | 40+ currencies |
| ExchangeRate-API | Daily | 1,500 requests/month | 170+ currencies |
Automatic updates are 10 times more reliable than manual updates. Choose a provider based on geography—for Russia, the Central Bank of Russia is optimal. A typical setup costs $500–$1,500 depending on complexity, and can save up to $200 per month in prevented rate errors.
What Tools for Bulk Translation?
Translating a catalog of 10,000 products manually takes weeks. Use:
- CSV import/export with columns for each language.
- Automatic translation modules (Google Translate API, DeepL).
- Custom scripts on Symfony Console for batch processing.
We prefer CSV—it gives full control and is 5x faster than manual entry for bulk products. Example structure:
| id | name_ru | name_en | description_ru | description_en |
|---|---|---|---|---|
| 1 | Футболка | T-shirt | Хлопок 100% | 100% cotton |
Common Configuration Mistakes
- Ignoring hreflang: Google may not understand which version is for which region.
- Wrong base currency: if you change the base currency after launch, all prices recalculate incorrectly.
- Missing translation of SEO fields: meta-title, meta-description, URL rewritten—must be translated for each language.
- Using deprecated methods: in PrestaShop 8+, some language methods are deprecated (e.g.,
Language::getIdByIso()replaced by repository).
What's Included in the Work
- Analysis of current structure and URL strategy selection.
- Language installation and activation, translation of back-office and front-office.
- Currency configuration with auto-update of exchange rates and correct price formatting.
- SEO optimization: hreflang, sitemap, canonical URLs, meta tags.
- Bulk catalog translation via CSV import/export (up to 10,000 products).
- Testing and verification on real orders.
- Documentation: handover of technical notes and configuration details.
- Training: team session on managing multilingual content.
- Post-launch support: 1 month of assistance for any issues.
- Cost estimate: from $1,500 for basic multilingual setup to $4,000 for comprehensive catalog translation.
Upon completion, you receive full access and documentation. Order turnkey multilingual PrestaShop setup—we deliver quality and on time.
Estimated timelines:
- Adding 1–2 languages + back-office translations: 1 day.
- Configuring 3–5 currencies + auto-update: 1 day.
- SEO configuration hreflang + URL structure: 1–2 days.
- Catalog translation for 1,000–10,000 products: 3–7 days.
Cost is calculated individually after an audit. Typical project cost: $1,500–$4,000. Contact us for a consultation—we'll evaluate your project for free. We guarantee quality work and post-launch support.







