PrestaShop Multilingual & Multicurrency Setup

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

1. Install and activate languages via admin or CLI, then install language packs for interface translation.
2. Configure URL strategy: choose prefix based URLs (e.g., /en/, /ru/) for best SEO.
3. Add hreflang tags using the displayHeader hook with alternate links for each language, including x-default.
4. Set up currencies: add target currencies programmatically or via admin, configure exchange rate provider.
5. Automate rate updates with a cron job running php bin/console prestashop:currencies:update-exchange-rates every 6 hours.
6. Translate catalog content using CSV export/import or automatic translation modules (CSV is 5x faster than manual translation for bulk products).
7. 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:

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:

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:

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.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.