A multilingual WooCommerce store involves two separate decisions: which languages the store speaks and which countries it sells to. Ready-made plugins can translate the content and suggest the right version to customers from each country. Prices in different currencies, taxes, shipping and stock levels for several markets are a matter of architecture, and you need to plan them before launch. Below you will find a list of things to decide, an example of a store selling to several countries and the line between a plugin and custom work.
Table of contents
Language is not country: what to decide before launch?
Before you install any plugin, write down whether you are changing only the language or also the terms of sale. A customer from Austria and one from Germany speak the same language but may get different delivery options, while a customer from Belgium may want French or Dutch.
Questions worth answering in writing:
- Languages. Which language versions launch right away, which come later, and who will translate the product descriptions.
- URLs. Separate country domains, subdirectories such as /de/ or subdomains. This affects SEO and maintenance costs.
- Currencies and prices. One currency for everyone or separate price lists for each market.
- Taxes. How the store charges VAT when selling to other EU countries; discuss this with your accountant before anything is configured.
- Shipping and returns. Who ships, how much it costs and how a customer abroad sends goods back.
- Customer service. Which language you use to answer emails and complaints.
Your answers decide whether one store with translations is enough or whether you need a multisite setup or separate instances. If you run several brands or markets, read our article on scaling multiple brands on WordPress.
How should customers choose their country and language?
Ideally on their own, with a sensible suggestion. Automatically sending customers to another version without asking may be convenient for the store, but it frustrates people and makes life harder for search engines.
In its guidelines for multilingual and multi-regional sites, Google recommends avoiding automatic redirects between language versions based on what language users might know, and letting them switch versions themselves. The reason is simple: a redirect can block both customers and search engine crawlers from reaching the other versions.
In practice, a suggestion works well: the store detects the visitor’s country and offers to switch to the matching version, while the decision stays with the customer. This is what the Country Selector Pro plugin is for. According to the vendor’s description, it:
- detects the visitor’s country based on their IP address,
- shows a popup suggesting a language change when someone visits from outside the country whose language the page is in,
- lets you choose in the settings which countries should get a switch suggestion and edit the message text,
- lets you set redirects to specific pages, categories or domains for a given country,
- lets you turn off automatic redirects on selected pages and posts,
- keeps popup and cookie settings in one panel.
A sensible setup is a popup with a suggestion instead of a hard redirect. If you do use redirects, turn them off at least on the terms, contact and returns pages, so everyone can reach them.
Example: a cycling gear store selling to three countries
Take a WooCommerce store from Poland that also wants to sell to Germany and the Czech Republic. It has Polish, German and English versions, because it will not have a Czech translation ready at launch.
- It settles the URLs: one domain with subdirectories for languages.
- It translates the menu, categories, key product pages, terms and shipping pages.
- It adds hreflang tags so the search engine shows the right version, as we describe in our article on how to mark language versions.
- It configures version selection: a customer from Germany sees a suggestion to switch to the German version, a customer from the Czech Republic to the English one, and the language switcher in the header always stays visible.
- It sets shipping costs for each country and shows them before the cart, in line with what we write about how to show shipping costs.
- It tests a purchase from each country, ideally through a VPN, and checks that the popup does not cover the cart.
In this scenario, the multilingual WooCommerce store is built without writing code, and all the work comes down to configuring ready-made tools and doing proper translations. A developer is needed at most to polish the popup design and help with testing.
Multilingual WooCommerce store: where does the plugin end?
The line runs where markets differ not in language but in sales logic. Plugins are good at translating content and sending customers to the right version, but they will not set your business rules for you.
- Separate price lists and currencies. Prices set by hand for each market, rather than converted at an exchange rate, require thinking about where they live and who updates them.
- Separate warehouses. When goods for Germany ship from a different warehouse than goods for Poland, stock and orders have to be split, often together with an ERP integration.
- Different product ranges. Products that cannot be sold in a given country must disappear from the catalog, search and product feeds.
- Marketplace and wholesaler integrations. Each market has different channels and data formats.
- Performance. Several language versions multiply the number of pages and database queries, so a large catalog calls for a review of hosting and cache.
We make these decisions with the client at the project stage, because changing the structure after launch costs much more. If you are planning such a store, we describe our approach on the page about online stores built on WooCommerce, and you will find an overview of translation tools in our article on building a multilingual WordPress site.
Frequently asked questions
Is detecting the country by IP address always accurate?
No. A customer who is travelling, a company with a single internet gateway in another country or a VPN all change the result. That is why it is better to suggest a version than to force it, and to always keep the language switcher in a visible place.
Is it enough to translate the product descriptions?
At launch, yes, but a customer from abroad will quickly reach the terms, shipping and returns pages. These pages should be translated together with the cart and the order messages.
Country domain or subdirectory?
Subdirectories are easier to maintain because it is one site. Country domains send a strong local signal, but each one needs its own work on visibility. The choice depends on how much the markets differ.
Start your multilingual WooCommerce store with the list of decisions from this article, and use a ready-made tool to suggest the right language version to customers instead of writing your own. You will find a description of the popup, country and redirect settings on the Country Selector Pro plugin page.
