Multilingual Ecommerce Website: How to Sell Internationally with WooCommerce, Shopify and Webflow

A successful multilingual ecommerce website rests on four pillars: a separate URL for each language or market (ideally subfolders such as /fr/ or /de/), correct hreflang tags, fully translated product pages, checkout and emails, and an offer that is genuinely localized for each country (currency, shipping, VAT and payment methods). Shopify handles most of this out of the box, WooCommerce gets there with plugins, and Webflow currently has a significant limitation for online stores.

Expanding abroad is often the fastest growth lever for a brand that has hit a ceiling at home. But a machine translation bolted on at the last minute will not do the job. Shoppers buy in their own language, Google needs to know which version to show to whom, and the cart must display consistent prices, shipping costs and taxes.

This guide is for store owners, startups and marketing teams that want to sell in France, Germany, the wider EU or beyond. It covers the technical decisions, the SEO pitfalls and the practical differences between WooCommerce, Shopify and Webflow.

Why a multilingual ecommerce website sells more

The most widely quoted figures come from CSA Research's "Can't Read, Won't Buy" study (2020, 8,709 consumers in 29 countries):

In other words, an English-only store misses a large share of German, French or Dutch buyers, even those who read some English. The same study found that 75% of customers are more likely to buy again when customer care is in their language, so localization does not stop at the product page.

Language, country or market: define your targets before you translate

The most common mistake is thinking only in languages. A French-speaking Swiss customer and a French customer read the same language, but they pay in different currencies, use different carriers and fall under different tax rules. Before any development, separate:

• Language versions: English, French, German, Arabic.
• Markets: UK, France, Germany, Switzerland, Belgium, Tunisia.
• The combinations that matter: for example "German for Germany and Austria" or "French for France and Belgium".

Start with two or three markets where you already see demand: international sessions in your analytics, shipping requests, interested resellers. A focused, well-localized launch beats a store translated into eight languages badly. Capture these decisions in your ecommerce requirements document from day one.

URL structure and hreflang: the SEO foundations of a multilingual store

Which URL structure should you choose?

Google compares the options in its guide to managing multi-regional and multilingual sites:

For most small and mid-sized businesses, subfolders are the best option. That is also what Shopify recommends for international SEO.

Hreflang and canonical tags: connecting your versions correctly

Hreflang tells Google that /product/leather-bag/, /fr/produit/sac-cuir/ and /de/produkt/ledertasche/ are the same page in three languages. Every version must reference itself, list the others and receive a return link. Add an x-default value for visitors whose language you do not cover. Google's documentation on localized versions explains the three implementation methods (HTML, HTTP headers, sitemap).

A frequent ecommerce mistake is pointing the canonical tag of every translation at the main-language page. Google then treats the translations as duplicates and stops showing them. Each translated version needs a self-referencing canonical.

Do not auto-redirect by IP address

Google is explicit: avoid automatically redirecting users from one language version to another, and do not use IP analysis to adapt content, because IP location is unreliable. A German expat in London should still be able to browse in German. Show a subtle banner instead ("Looks like you're in Germany. Switch to the German store?") and remember the visitor's choice.

Translate and localize the entire shopping experience

A store is only truly multilingual if customers can complete a purchase from start to finish in their language. The list of elements to translate is longer than most teams expect:

• Catalog: titles, descriptions, attributes (size, color, material), categories, filters and URL slugs.
• Checkout: cart, forms, error messages, shipping options, terms and conditions.
• Transactional emails: order confirmation, shipping notification, abandoned cart reminders, invoices.
• SEO elements: title tags, meta descriptions, image alt text, structured data.
• Trust content: returns policy, delivery times, customer service contacts, reviews.

Machine, human or hybrid translation?

Machine translation (DeepL, Google, AI built into CMS platforms) can translate a large catalog quickly. The pages that drive revenue still need a native review: home page, main categories, best sellers and checkout. A hybrid approach works well: machine translation for the long tail of the catalog, native copywriting for strategic pages.

Run keyword research for each market

People do not search for literal translations of your keywords. A British shopper searches for "trainers" where an American types "sneakers"; a German looks for "Ledertasche Damen", not a word-for-word translation of "women's leather bag". Build a keyword list per market and adapt category names accordingly. Our SEO copywriting service produces native content in English, French and German.

Currencies, pricing, VAT and shipping: adapting the offer to each country

Show prices in the local currency

A euro price shown to a Swiss or British shopper creates friction: they have to do the math and worry about conversion fees. You have three options:

1. Automatic conversion at the daily rate: simple, but produces awkward prices (CHF 52.37).
2. Fixed prices per currency: EUR 49 / CHF 49 / GBP 45, which read better and convert better.
3. Conversion with rounding rules: a good compromise for large catalogs.

Make sure the currency displayed is the one your payment provider actually charges. Showing Swiss francs and charging euros is a reliable way to generate disputes.

EU VAT and the One-Stop Shop

For a business established in the EU, distance sales of goods to consumers in other member states are taxed at the customer's local VAT rate once they exceed EUR 10,000 per year (a single EU-wide threshold). The One-Stop Shop (OSS) lets you report that VAT in one return, as explained by the Netherlands Chamber of Commerce (KVK). Country rates are listed in the European Commission's VAT database. Your store therefore has to calculate VAT from the delivery address, and gross prices may differ by country. Have these rules validated by your accountant.

Sellers outside the EU: plan for customs rules

A business based in Tunisia, the UK or elsewhere outside the EU that ships directly to European consumers must also consider the IOSS scheme for low-value shipments and the changing customs rules for small parcels, which the same KVK guide summarizes. For Tunisian brands, collecting foreign-currency payments is an additional challenge; our comparison of Konnect, Flouci and Click to Pay covers the online payment options available.

Local shipping and payment methods

Payment habits vary widely. Cards and PayPal work almost everywhere, but many German shoppers like paying by invoice, Dutch customers rely heavily on iDEAL and Belgians on Bancontact. Show delivery times and shipping costs per country on the product page: surprise costs at checkout remain a leading cause of abandonment, as we explained in our WooCommerce checkout optimization guide.

WooCommerce, Shopify or Webflow: which platform for a multilingual store?

Shopify: the most integrated

With Shopify Markets, you create markets (countries or groups of countries) and assign them languages, currencies, prices and domains. According to Shopify's documentation, the platform automatically generates hreflang tags, canonicals and market-specific sitemaps, and excludes known crawlers from its automatic redirects. The free Translate & Adapt app lets you translate content and adapt it per market. It is the fastest route to launch, with less control over some details (certain URL structures, features reserved for higher plans).

WooCommerce: the most flexible

WooCommerce is not multilingual out of the box. It is usually paired with WPML and its WPML Multilingual & Multicurrency for WooCommerce add-on, or with Polylang and its WooCommerce extensions. WPML's multicurrency features are free (manual prices per currency, shipping rates per currency), while translating the catalog requires a paid WPML license. The upside is full control over translated URLs, theme, tax rules and payment gateways. The trade-off is more plugins to maintain and closer attention to performance and updates.

Webflow: be careful with stores

Webflow Localization is excellent for marketing sites and CMS content: language subfolders, assisted translation and locale routing on higher plans. However, according to the Webflow Help Center (checked October 2026), Webflow Localization is not compatible with Webflow Ecommerce: products, categories and store pages cannot be localized. A multilingual store on Webflow therefore needs a third-party translation layer or an external ecommerce engine. Our guide to Webflow Ecommerce limitations and pricing covers these constraints in detail.

For a deeper platform comparison, read Shopify vs WooCommerce in 2026.

Example: a natural skincare brand expanding into Germany

Illustrative case: a skincare brand sells in English and French on WooCommerce. Its analytics show steady traffic from Germany and Austria, plus regular shipping requests from Switzerland.

1. Scoping: three priority markets (France/Belgium in French, Germany/Austria in German, Switzerland in French and German with CHF pricing).
2. Structure: /de/ and /ch-de/ subfolders, hreflang with region codes, self-referencing canonicals.
3. Content: native translation of the 40 best sellers, categories and checkout; reviewed machine translation for the rest of the catalog; German keyword research.
4. Offer: fixed EUR and CHF prices, VAT by delivery country, carrier and delivery times shown per country, invoice payment added for Germany.
5. Measurement: clicks per folder in Search Console and conversion rate per language tracked over three months.

Checklist: launching your multilingual ecommerce website

• Priority markets defined (language + country + currency).
• One URL per version, preferably in subfolders.
• Reciprocal hreflang, x-default and self-referencing canonicals.
• No automatic IP redirects; a visible language switcher.
• Catalog, filters, checkout, emails and legal pages translated.
• Keyword research completed for each market.
• Prices, VAT, shipping and payments localized per country.
• Customer service and reviews available in every language.
• Performance tracked per language in Search Console and analytics.

If you are converting an existing store, treat it like a migration: our ecommerce migration SEO checklist will help you protect your current traffic.

Conclusion: an international project, not just a translation

A high-performing multilingual ecommerce website is built like a new store for each market: a clean technical structure for Google, a complete shopping experience in the customer's language, and an offer adapted in pricing, tax, shipping and payment. Shopify speeds up launch, WooCommerce offers the most freedom, and Webflow requires careful architecture as soon as a store is involved. The right choice depends on your markets, your catalog and your in-house resources.