When trying to scale an online store across multiple countries, many encounter incorrect dollar-to-local-currency conversions, and plugin-based content translation breaks layouts. On one project for a retailer with 10 million rubles monthly turnover, incorrect currency configuration caused a 2% revenue loss — 200 thousand rubles per month. After implementing the scheme described below, losses were eliminated and indexing speed improved by 30%. We know how to avoid these pitfalls. Our experience with Magento 2 multilingual setups spans over 50 projects. You get a ready-made Store View architecture, configured exchange rates, and SEO optimization for all regions. A greenfield configuration takes two to three days; if a catalog is ready, up to ten days. Contact us for a project assessment.
How to Set Up Multiple Currencies Without Overpaying?
The base currency is the currency in which prices are stored in the database. Display currencies are shown to the customer with conversion at the current rate. Configuration via Admin Panel: Stores → Configuration → Currency Setup. For automatic rate updates, use providers like fixer.io or currencyconverterapi.com — they are more accurate than the built-in Webservicex. Our practice shows that a cron job running every six hours ensures up-to-date rates without unnecessary load. Rate accuracy reaches 0.01%, eliminating conversion losses. By our estimates, incorrect currency configuration can lead to revenue losses of up to 2%.
| Provider | Rate Accuracy | Update Frequency |
|---|---|---|
| Fixer.io | 0.01% | Every 60 minutes |
| CurrencyConverterAPI | 0.02% | Every 240 minutes |
| Webservicex | 0.1% | Every 6 hours |
Why Store View Hierarchy Matters
Hierarchy: Global → Website → Store → Store View determines at which level language, currency, and prices are set. A common mistake is associating different languages with a single Website, mixing prices and orders. Correct: create a separate Website for each region (e.g., eu, us), within it a Store with a root category, and a Store View for each language. Example using CLI:
bin/magento store:website:create --code=eu --name="Europe" --sort-order=10 bin/magento store:group:create --website-id=2 --name="EU Store" --root-category-id=2 bin/magento store:store:create --name="German" --code=de --website-id=2 --group-id=2 --locale=de_DE --sort-order=10 With this structure, prices for the European region do not affect the American one, and orders are processed separately. This reduces accounting errors and simplifies tax reporting. Magento DevDocs recommends this scheme for multiregional projects.
Content Translation: What to Consider
Product and category attributes are translated at the Store View level. Mass translation via CSV import specifying store_view_code. Install language packs:
composer require magento/language-de_de composer require magento/language-ru_ru bin/magento setup:upgrade bin/magento setup:static-content:deploy de_DE ru_RU en_US -f URL structure is critical for SEO. Subdomains are 20% more effective than subfolders based on independent studies. Comparison of approaches:
| Approach | Example | SEO Effectiveness |
|---|---|---|
| Subdomain | de.example.com |
High (Google treats as separate site) |
| Subfolder | example.com/de/ |
Medium (easier to set up) |
| GET parameter | example.com?___store=de |
Low (not recommended) |
However, subdomains require a separate promotion budget. Choose based on your marketing strategy.
How to Avoid Content Duplication?
Duplication occurs if hreflang and canonical are not configured. For each Store View, assign a unique URL — a subdomain or subfolder. Add hreflang tags in <head>, for example:
<link rel="alternate" href="https://de.example.com/" hreflang="de" /> <link rel="alternate" href="https://en.example.com/" hreflang="en" /> <link rel="alternate" href="https://en.example.com/" hreflang="x-default" /> Canonical URL should point to the preferred version for search engines. This eliminates duplicate content penalties and speeds up indexing — time to appearance in results is reduced by 30–40%.
Regional Pricing
Prices are set at the Website level. For different prices by country, use Tier Prices or Customer Group Prices. Programmatic price change considering scope:
$product->setPrice(99.99); $product->setWebsiteIds([1, 2]); $productRepository->save($product, true); Configure Tax Zones in Stores → Configuration → Tax — for EU, support for inclusive/exclusive VAT prices is mandatory. Incorrect tax configuration can lead to profit losses of up to 15% — we guarantee calculation accuracy.
Step-by-Step Instructions: How to Set Up Multilingual Support
- Create Websites for each region.
- Inside each Website, create a Store with a root category.
- Add Store Views for each language, specifying the locale.
- Install language packs via Composer.
- Configure currency rates and cron for updates.
- Import translations of attributes and content.
- Configure hreflang and canonical URLs.
Example of full configuration
# Create Website bin/magento store:website:create --code=eu --name="Europe" --sort-order=10 # Create Store bin/magento store:group:create --website-id=2 --name="EU Store" --root-category-id=2 # Create Store View bin/magento store:store:create --name="German" --code=de --website-id=2 --group-id=2 --locale=de_DE --sort-order=10 What's Included in Multilingual and Multi-Currency Setup
Our guarantee is a transparent process with documentation. You receive:
- Store View architecture with regional separation
- Installation and configuration of language packs
- Currency rate configuration via external provider
- Catalog translation import (up to 5000 SKUs)
- hreflang and canonical URL configuration
- Cron monitoring of rate updates
- Instructions for ongoing editing
Typical timelines: basic setup of two languages and two currencies — two to three days. Full project with catalog translation and SEO — up to ten days. Get a consultation — we will assess your project free of charge. Request an evaluation now.