Multilingual WooCommerce and multiple currencies after migration
An IT expert explains how to set up languages, currencies, tax and checkout in WooCommerce after converting an AI-built shop.
Convert2WP – convert your AI website to WordPressClick here
A shop design is not a shop
AI builders make it easy to design a shop page with product cards, a cart icon and a checkout button. Behind it there is often a payment link or an external service. After conversion to WordPress you get the design, but the shop logic has to be rebuilt in WooCommerce. For international shops that includes languages, currencies and tax.
This is where planning matters most. Mistakes in prices or tax are not cosmetic glitches; they cost money and trust.
Deciding the market strategy first
Before installing anything, I ask which countries the shop will sell to, in which languages and in which currencies. Selling in English to the whole world in euros is very different from having separate German, French and Polish stores with local prices.
The answers decide the architecture. One store with language and currency switchers works for most small and medium shops. Separate stores per region make sense when assortment, pricing and legal requirements differ strongly.
Translating products properly
A multilingual plugin that integrates with WooCommerce translates products, categories, attributes and checkout texts. I make sure each product translation shares the same stock and SKU, so you do not sell an item in French that is already sold out in Dutch.
Product descriptions deserve real translation, not just machine output. Search engines and customers notice the difference, and conversion rates in local languages improve noticeably with natural wording.
Currencies and rounding
Automatic currency conversion is convenient, but it produces prices like 47.83 that look odd to customers. I prefer either fixed prices per currency for key products or conversion with rounding rules, such as ending on .95 or whole numbers.
Payment providers must support every currency you show. Displaying a price in Swiss francs and then charging in euros at checkout is confusing and generates support tickets and chargebacks.
Tax rules across borders
Within the EU, consumer sales of goods follow the destination country's VAT once you exceed the threshold, usually handled through the OSS scheme. WooCommerce can calculate this with the right tax tables, but the store owner must confirm the setup with their accountant.
I also decide whether prices are shown including or excluding tax per market. Consumers in Europe expect prices including VAT. Business customers often want to see net prices and enter a VAT number for reverse charge.
Shipping zones and checkout fields
Shipping zones are configured per country or region, with their own methods and prices. I keep them simple at launch and refine after real orders show which options customers use.
Checkout fields vary by country: postal code formats, state fields, house number placement. WooCommerce handles much of this, but I always place test orders for each main market to confirm the address forms make sense.
SEO for a multilingual shop
Each language version of a product needs its own URL, translated slug, canonical tag pointing to itself and hreflang links to the other versions. Category pages need the same. Without this, search engines treat translations as duplicates.
I check the raw HTML of a few product pages in each language to confirm these tags are present without JavaScript. It is the single most important technical check for an international shop.
Launching in steps
I rarely launch all markets at once. Starting with the home market and one or two others lets you fix issues in a controlled way. Additional languages follow when the processes around orders, returns and support work smoothly.
Order data and customer accounts from the old builder are not converted automatically, since backends are not part of the conversion. Plan a separate import if you need them. Small issues in the first weeks are normal and are usually solved with a setting or a plugin.