ChatGPT answers, unedited

For an international store with lots of tax, currency, pricing, and localization rules, I’d shortlist Medusa, Saleor, and Odoo—but my default pick would be Medusa if you have a development team.

My ranking

🥇 Medusa — my pick for your scenario

Medusa has a particularly good model for complicated international commerce. It separates regions, currencies, tax regions, tax rates/rules, and tax providers, rather than treating localization as simply translating a storefront. A region can have its own currency, countries, payment providers, fulfillment configuration, and tax-inclusive/exclusive pricing. docs.medusajs.com

The tax system also supports hierarchical tax regions, product/product-type overrides, and custom tax providers. That matters if you eventually need external tax engines or bespoke tax logic. docs.medusajs.com

It also has proper locale support using BCP 47 locale codes such as en-US and fr-FR, rather than conflating language with country. docs.medusajs.com

The biggest advantage is architectural: you can replace or extend the pieces that don't fit your tax model. Medusa explicitly supports custom tax providers and custom workflows. docs.medusajs.com

Medusa documentation

🥈 Saleor — excellent alternative

I'd choose Saleor over Medusa if your team strongly prefers Python/GraphQL and you're building a sophisticated headless/enterprise commerce stack.

Its channels are especially powerful for international operations: a single backend can have independent currencies, languages, pricing, and storefront configurations. Saleor also has a dedicated multi-region architecture. docs.saleor.io

Saleor documentation

🥉 Odoo — consider it if tax/accounting is the center of gravity

If by "complex localization" you mean VAT/GST, fiscal positions, invoicing, accounting, inventory, purchasing, and country-specific financial workflows, rather than primarily storefront localization, I'd seriously investigate Odoo.

The advantage isn't necessarily that its storefront is better than Medusa's; it's that the commerce system and back-office/financial system can be one system.

What I would avoid

I wouldn't make WooCommerce my first choice for a store where international tax logic is one of the hardest parts of the architecture. It can absolutely do international commerce, but complex localization often turns into a collection of plugins/extensions that you then have to keep compatible.

For a greenfield build, I'd rather have the underlying commerce engine model region → country → tax rules → currency → pricing → payment/fulfillment explicitly.

The important distinction

If your requirements look like:

"Sell in 40 countries, 15 currencies, 12 languages, different VAT/GST rules, tax-inclusive pricing in some markets, tax-exclusive in others, different prices by market, and occasionally override tax treatment by product."

Medusa is probably the best starting point. Its documented multi-region model maps unusually well to that problem. docs.medusajs.com

If instead you're saying:

"We need sophisticated tax/accounting compliance integrated with ERP, inventory, purchasing, and financial reporting."

Odoo becomes much more compelling.

And if you're building a large headless commerce platform with multiple storefronts/brands/channels, I'd put Saleor and Medusa essentially neck-and-neck, with the choice driven heavily by your engineering stack.

If you tell me which countries you sell into, approximate number of currencies/languages, B2C vs B2B, and whether you're using an external tax engine like Avalara/TaxJar, I can narrow this down to a specific architecture and platform.

For an international store where tax, currency, country, language, and pricing rules are genuinely complex, my first choice would be Shopware 6 self-hosted.

My ranking

1. Shopware 6 — best overall for complex internationalization
2. Sylius — best if you have a strong engineering team and want maximum customization
3. Odoo — best if ecommerce needs to be tightly integrated with ERP/accounting
4. Medusa — best for a modern headless architecture, but you'll build more localization logic yourself

Why I’d pick Shopware 6

Shopware has unusually strong first-class concepts for international commerce:

• Sales channels can have their own countries, languages, currencies, payment methods, shipping methods and tax calculation. Shopware Shopware
• Multiple domains can each have their own language, currency and localization settings, which is useful for country-specific storefronts. Shopware
• It supports country-specific tax behavior, including B2C/B2B tax-free rules, VAT-ID requirements and tax-free thresholds that can vary by currency. Shopware
• Currencies support country-specific price rounding, which matters when you're selling in markets where psychological pricing or local rounding conventions differ. Shopware
• Languages have proper locale/ISO configurations and inheritance, rather than simply being strings attached to products. Shopware
• Shopware explicitly supports configuring international taxes, currencies, languages, payments and shipping as separate localization concerns. Shopware

That makes it particularly attractive if your rules look something like:

US → USD → sales tax
Germany → EUR → 19% VAT
UK → GBP → VAT rules + different rounding
Switzerland → CHF → different tax + payment/shipping
B2B EU → VAT-ID validation + reverse charge
Japan → JPY → different price display/rounding

You can model a lot of that in the platform rather than turning your storefront into a giant collection of custom if country == ... statements.

Where Sylius beats it

I'd choose Sylius instead if your business has unusually complicated rules that don't fit conventional ecommerce assumptions—for example:

• highly customized tax engines
• complicated B2B pricing
• multiple legal entities
• marketplace functionality
• unusual order/inventory workflows
• sophisticated headless architecture
• developers who want Symfony/PHP and full control of the domain model

The tradeoff is that Sylius gives you a lot of flexibility, but you are responsible for implementing more of the business logic. Shopware is the better choice if you want sophisticated international ecommerce capabilities out of the box.

One important caveat

For a really international operation, I wouldn't make the ecommerce platform the ultimate authority for tax.

I'd architect it roughly as:

Shopware → tax service → accounting/ERP

rather than embedding every country's tax law directly into Shopware.

That's especially important if you're dealing with VAT/GST/sales-tax registration thresholds, exemptions, reverse charge, marketplace facilitator rules, OSS/IOSS, tax-inclusive vs. tax-exclusive pricing, or frequent regulatory changes.

So if you tell me roughly how many countries you sell into, whether you're B2C/B2B, and whether you need ERP/accounting integration, I can narrow this down to Shopware vs Sylius vs Odoo vs Medusa for your particular operation.

rather than embedding every country's tax law directly into Shopware.

That's especially important if you're dealing with VAT/GST/sales-tax registration thresholds, exemptions, reverse charge, marketplace facilitator rules, OSS/IOSS, tax-inclusive vs. tax-exclusive pricing, or frequent regulatory changes.

So if you tell me roughly how many countries you sell into, whether you're B2C/B2B, and whether you need ERP/accounting integration, I can narrow this down to Shopware vs Sylius vs Odoo vs Medusa for your particular operation.

For an international store with complicated tax, currency, pricing, and localization rules, the best self-hosted choice is usually:

1. Adobe Commerce (Magento Open Source) — best for maximum complexity

Best fit: enterprise or growing merchants with many countries, catalogs, warehouses, customer groups, and custom tax logic.

Why it stands out:

• True multi-store architecture (separate country sites under one installation)
• Store-view localization (language, currency, content, pricing)
• Complex catalog rules and customer-group pricing
• Strong B2B capabilities (especially with Adobe Commerce)
• Large ecosystem for tax engines, ERP, PIM, shipping, and payments
• Handles very large catalogs and complex workflows www.liquidweb.com

Trade-offs:

• Highest implementation and maintenance burden
• Requires experienced developers and infrastructure
• Extensions can create upgrade complexity www.liquidweb.com

Choose Magento if you have things like:

• Different prices by country/customer tier
• Multiple legal entities
• VAT/GST/sales tax differences
• Regional catalogs
• Complex B2B contracts
• ERP integration

2. Shopware — best modern international alternative

Best fit: mid-market international brands, especially Europe-focused.

Strengths:

• Built-in multilingual and multi-currency support
• Country-specific tax configuration
• Strong sales-channel model for regional storefronts
• API-first/headless architecture
• More modern admin experience than Magento for many teams www.shopware.com

Trade-offs:

• Smaller global ecosystem than Magento
• Some very advanced enterprise workflows may require extensions/custom work

A good choice if you want:

• Several European markets
• Strong localization
• Modern frontend architecture
• Lower complexity than Magento

3. PrestaShop — best value for multilingual international retail

Best fit: smaller-to-mid-sized global stores, especially EU merchants.

Strengths:

• Excellent multilingual capabilities
• Good native localization features
• Strong European market adoption
• Easier to operate than Magento swingintel.com

Trade-offs:

• Less suitable for extremely complex B2B pricing or massive catalogs
• More reliance on modules for advanced workflows

4. WooCommerce — only if content is the priority

Good for:

• Smaller international catalogs
• Businesses already invested in WordPress
• Lower technical budgets

Less ideal for:

• Hundreds of thousands of SKUs
• Complex tax jurisdictions
• Many independent regional storefronts

Localization usually depends heavily on plugins, which increases maintenance risk. swingintel.com

My ranking for your use case

For a store where tax and currency rules are the hardest problem, I would shortlist:

1. Magento Open Source if you have a technical team
2. Shopware if you want strong localization with easier operations
3. PrestaShop if your complexity is mostly languages/currencies rather than B2B logic

A key architectural point: for serious international commerce, don’t make the ecommerce platform your tax engine. Pair it with a dedicated tax service such as Avalara, Vertex, or TaxJar-like tooling, because tax rules change faster than platforms do.

If you share:

• number of countries,
• B2C vs B2B,
• approximate SKU count,
• whether prices differ by country,
• required tax regions (EU VAT, US sales tax, GST, etc.),

I can narrow this to a specific stack.

For an international store with lots of tax, currency, country, language, and pricing rules, my top pick for self-hosting is Shopware 6, with Magento Open Source as the stronger choice if your rules are exceptionally complex.

My ranking

• Especially good when you're willing to implement/customize the business logic yourself.

🥇 Shopware 6 — my default recommendation

Shopware is particularly well suited to cross-border commerce. Its sales-channel model lets you associate languages, currencies, tax rates, shipping costs and customs duties with individual markets, while inheritance lets you maintain common catalog data centrally. Shopware Shopware Documentation

Its country configuration also supports things such as B2C/B2B tax-free thresholds that can vary by currency, VAT registration validation, and country-specific tax behavior. Shopware Documentation

That makes it a particularly good fit if you're thinking in terms of:

One product catalog → dozens of countries → different tax rules, currencies, price lists, languages, payment methods and shipping rules.

I'd choose Shopware if you want sophisticated localization without having to build your commerce engine around custom code.

docs.shopware.com

🥈 Magento Open Source — when rules get really gnarly

Magento (Magento Open Source) is arguably the more powerful choice if your organization has a strong engineering team.

Its hierarchy of websites → stores → store views is useful for substantially different regional businesses, and its tax engine supports combinations of product classes, customer classes, tax zones and rates. Experience League Experience League

Currency handling is similarly mature: multisite installations can have different base currencies at the website level, while accepted/display currencies can be configured separately. Experience League

So I'd lean Magento if you have requirements like:

• different catalogs by market
• different base currencies by legal entity
• complicated B2B/B2C tax treatment
• customer-specific tax classes
• extensive custom pricing
• many regional storefronts
• ERP/PIM/OMS integrations
• sophisticated custom checkout/business logic

The tradeoff is considerably more operational and development complexity than Shopware.

experienceleague.adobe.com

🥉 Sylius — interesting if you're building a custom commerce stack

Sylius is worth serious consideration if you have a development team and want the commerce platform to conform to your business model rather than configuring an enormous prebuilt system.

I'd favor it when your localization rules are unusual enough that you're likely to write substantial custom code anyway.

One important distinction: platform vs. tax engine

For a truly international operation, I wouldn't expect the ecommerce platform alone to be the ultimate authority for tax.

For example, Shopware explicitly supports tax-provider functionality for more sophisticated regional tax/customs calculations, while Medusa allows custom tax providers. Shopware Medusa Documentation

A robust architecture is often:

Shopware/Magento → tax engine → payment → ERP/accounting

rather than encoding every country's tax legislation directly into ecommerce rules.

My recommendation

If I were choosing for a new international store today:

Shopware 6 → best balance of localization depth, maintainability and self-hosting.

Magento Open Source → choose this instead if you have very complex multi-entity/multi-market pricing and tax logic and a dedicated engineering team.

Sylius → choose this if your business model is sufficiently unusual that you're essentially building a custom commerce application.

If you tell me roughly how many countries, currencies, B2B vs B2C, and whether you need EU VAT/OSS, US sales tax, GST/VAT in APAC, or customs/duties, I can narrow this down to a specific architecture and compare Shopware vs Magento vs Sylius for your rules.

For a self-hosted store with genuinely complex international tax, currency, pricing, and localization rules, I’d pick Shopware 6.

My ranking

Why Shopware would be my first choice

Shopware's sales-channel model is particularly well suited to international operations. A sales channel can have its own countries, languages, currencies, payment methods, shipping methods and tax calculation behavior. docs.shopware.com

Its tax engine also goes considerably beyond a simple country → VAT-rate mapping. You can define tax rules by country, state, ZIP code/range and effective date, and Shopware supports external tax providers for jurisdictions that are difficult to model internally. docs.shopware.com

Currency handling is similarly mature: currencies can be configured with country associations and price-rounding behavior, while sales channels can expose different currencies. docs.shopware.comdocs.shopware.comdocs.shopware.comdocs.medusajs.com

The Rule Builder is another major advantage when your business rules get complicated—you can make behavior conditional on things such as sales channel and currency and combine rules for more sophisticated scenarios. docs.shopware.com

Shopware official site

When I'd choose Medusa instead

If your store is heavily custom/headless and you have a strong engineering team, I'd seriously consider Medusa.

Its architecture has explicit concepts for regions, tax regions, tax rates/rules and tax providers. A region can have its own currency, countries, payment providers and fulfillment configuration, while tax regions can have hierarchical rules and product-specific overrides. docs.medusajs.com

That's excellent if you want to build your own localization logic rather than work primarily within an established commerce platform.

Medusa official site

And Sylius?

I'd choose Sylius over Shopware if your localization requirements are so unusual that you're effectively building a bespoke commerce application.

It's particularly attractive for developers who want maximum control over the domain model and business logic rather than a large out-of-the-box admin ecosystem.

Sylius official site

The important distinction

For your description—"lots of tax and currency rules"—I'd separate the problem into two layers:

Commerce platform

• Shopware 6 / Medusa / Sylius
• countries and regions
• currencies
• tax-inclusive vs. tax-exclusive pricing
• customer groups
• price lists
• localization
• shipping/payment availability

Tax compliance engine

• Avalara
• Vertex
• TaxJar
• Sovos
• or country-specific tax infrastructure

Don't choose a platform assuming its built-in tax table will magically handle global tax compliance. Shopware itself explicitly recommends external tax services for particularly complex systems such as US sales tax. docs.shopware.com

Bottom line:
Shopware 6 if you want the strongest combination of mature self-hosting + sophisticated international configuration + admin usability.
Medusa if you're engineering a headless/custom commerce stack.
Sylius if maximum programmability is more important than out-of-the-box functionality.

If you tell me which countries you sell into (e.g. US + EU + UK + Canada + Australia), B2C vs B2B, and whether prices are tax-inclusive, I can narrow this down much more precisely—including which platform handles your particular tax scenarios best.

For an international store with genuinely complex tax, currency, country, and localization rules, I’d put Adobe Commerce / Magento Open Source at the top, with Shopware 6 as the strongest alternative.

My ranking

1. Best overall: Adobe Commerce / Magento Open Source

This is my choice if localization rules are one of the core architectural requirements rather than just "I need translations and a currency selector."

Magento's tax engine can combine product classes, customer classes, tax rates, and geographic zones, with the applicable region determined from shipping address, billing address, or shipping origin. It also supports VAT-related calculations/validation and more specialized tax configurations. experienceleague.adobe.com

Its currency architecture is particularly strong for multinational setups: in a multisite installation, you can have different base currencies at the website level, rather than merely displaying converted prices. experienceleague.adobe.com

The underlying hierarchy—websites → stores → store views—also maps well to businesses that need different countries, catalogs, pricing, currencies, domains, languages, or branding under one installation. experienceleague.adobe.com

I'd choose Magento if you have things like:

• Different tax treatment by country/state/region
• B2B vs B2C tax rules
• VAT/GST/sales-tax complexity
• Multiple legal entities or websites
• Country-specific catalogs/pricing
• Multiple base currencies
• Country-specific domains/languages
• Significant custom tax logic
• External tax engines
• A development team capable of maintaining a sophisticated platform

One important distinction: Magento Open Source is self-hosted, while Adobe Commerce is the commercial version with additional enterprise capabilities.

2. Strongest alternative: Shopware 6

I'd seriously consider Shopware 6 if you want sophisticated internationalization but don't want quite as Magento-heavy an ecosystem.

Shopware supports country-specific tax rules down to country, state, ZIP code, or ZIP-code ranges, and it supports date-based tax rules. It also has integrations for external tax providers when the native rules aren't sufficient. experienceleague.adobe.comexperienceleague.adobe.comdocs.shopware.comhelp-center.prestashop.com

Its country configuration also handles things such as B2B/B2C tax-free thresholds, VAT IDs, and currency-dependent thresholds. docs.shopware.com

Shopware's own internationalization documentation explicitly treats country, taxes, currencies, payment methods, translations, and country-specific pricing as interconnected localization concerns. docs.shopware.com

I'd favor Shopware over Magento when:

• You want a modern European-oriented commerce platform
• EU VAT/OSS is particularly important
• You need sophisticated country/channel configuration
• You want somewhat less Magento-style architectural overhead
• Your team likes Symfony/PHP

3. PrestaShop — surprisingly good for international stores

Don't dismiss PrestaShop. Its localization system is quite appropriate for multinational retail.

Localization packs can populate currencies, taxes, tax rules, languages, units, and geographic information, while tax rules can target countries, groups of countries, and products. help-center.prestashop.com

It also supports multiple currencies and lets you add/configure currencies independently. help-center.prestashop.com

I'd choose it if you're primarily a retail/e-commerce business and your requirements are complicated but don't justify Magento's level of infrastructure.

4. WooCommerce — great flexibility, weaker tax architecture

WooCommerce can absolutely handle international stores, but I wouldn't make it my first choice when complex localization is the primary architectural concern.

Its core supports multiple tax rates and shipping zones, while more sophisticated multi-currency/multilingual behavior generally comes through extensions. WooCommerce's own documentation describes this model explicitly. woocommerce.com

It's an excellent choice when your store is fundamentally a WordPress site with commerce attached. I'd be more hesitant if you're building a large multinational commerce operation where tax/currency rules are among the hardest parts of the system.

What I'd pick for your situation

If "lots of tax and currency rules" is the key requirement:

1. Magento Open Source — maximum flexibility and deepest rule model
2. Shopware 6 — probably the best balance of sophistication and maintainability
3. PrestaShop — very good international retail functionality with lower complexity
4. WooCommerce — best when WordPress is already central to the business

There's also an important caveat: no self-hosted platform should be expected to be the authoritative source for worldwide tax law. Once you're dealing with US state/local sales tax, EU VAT, Canadian GST/HST/PST, Australian GST, marketplace rules, exemptions, registrations, etc., I'd architect the commerce platform to integrate with a dedicated tax provider rather than encode every jurisdiction's legislation yourself. Shopware explicitly supports tax-provider integrations, and Magento supports integrations with external tax systems as well. experienceleague.adobe.comdocs.shopware.com

If you tell me roughly how many countries you sell into, whether you're B2B/B2C, and whether prices are tax-inclusive or tax-exclusive, I can narrow this down to Magento vs Shopware and describe the architecture I'd use.

For a self-hosted international store with genuinely complex tax, currency, country, and localization rules, I’d put Shopware first.

My ranking

Why Shopware: its localization model goes beyond simply translating a storefront. You can configure countries, currencies, languages, sales channels, customer groups, and country/region-specific tax rules. Tax rules can even target individual countries, states, ZIP codes/ranges, and effective dates. docs.shopware.com

That matters if your rules look like:

• EU VAT/OSS vs. non-EU sales
• US state-level sales tax
• different tax treatment by product/category
• tax-inclusive vs. tax-exclusive pricing
• different prices by country
• multiple currencies with different rounding
• country-specific payment/shipping methods
• multiple storefronts/domains/languages
• B2B customers with VAT IDs
• rules that change effective on particular dates

Shopware also has a tax-provider integration layer, which is important if you eventually need an external tax engine rather than trying to encode every jurisdiction yourself. docs.shopware.comdocs.shopware.com

And importantly for your requirement, Shopware explicitly supports self-hosting; its documentation says self-hosted is intended for businesses with an expert development team that need control over their infrastructure. www.shopware.com

Where I'd choose something else

Choose Sylius if you have a strong Symfony/PHP engineering team and want the commerce platform to be a highly customizable building block. It's particularly attractive when your localization rules are so unusual that you'll be writing substantial domain logic anyway.

Choose Medusa if your team is primarily TypeScript/Node and you want a headless architecture. Medusa has first-class regions, currencies, tax regions, tax rules, and tax-inclusive/exclusive pricing. docs.medusajs.com Its region model is especially useful because regions can have their own currency, countries, and tax settings. docs.medusajs.comdocs.medusajs.com

The catch is that Medusa is more of a composable developer platform. Its documentation explicitly notes that broader content localization can require its Translation Module or external CMS integration. docs.medusajs.com

My practical recommendation

If you're asking "Which one minimizes the amount of custom localization/tax infrastructure I have to build?":

Shopware 6 → best choice.

If you're asking "Which gives my engineering team the most freedom to build our own international commerce domain?":

Sylius → strongest candidate.

If you're asking "We're a modern JS team and want headless + composable.":

Medusa → probably the better fit.

One important caveat: none of these should be treated as a complete global tax-compliance engine out of the box. For a store operating across many jurisdictions, I'd design the architecture so the ecommerce platform owns products, orders, prices, currencies and customer context, while a specialized tax service handles jurisdictional tax determination where necessary. Shopware's tax-provider architecture makes that particularly straightforward. docs.shopware.comdocs.shopware.com

If you tell me roughly how many countries you sell into, B2C vs. B2B, and whether you need headless, I can narrow this to a specific recommendation and architecture.

For a self-hosted store with genuinely complex international tax, currency, pricing, and localization rules, my first choice would be Adobe Commerce / Magento Open Source—assuming you have the technical team to operate it.

My ranking

\* WooCommerce can become much more capable with extensions, but that's also its weakness: sophisticated internationalization tends to turn into a collection of plugins that you have to keep compatible.

1. 🥇 Adobe Commerce / Magento Open Source

This is the one I'd investigate first for your situation.

Its tax engine lets you combine product tax classes, customer classes, tax rates and geographic regions, with the region determined from shipping/billing address or origin. It also supports compound taxes, VAT handling, tax-rate imports, and cross-border pricing behavior. experienceleague.adobe.com

Currency handling is similarly deep: you can accept currencies from 200+ countries, and in a multisite installation you can configure different base currencies at the website level. experienceleague.adobe.com

The really important feature for a complicated international business is its website → store → store view hierarchy. That lets you structure, for example:

One installation
├── US website
│   ├── English / USD
│   └── Spanish / USD
├── EU website
│   ├── English / EUR
│   ├── French / EUR
│   └── German / EUR
└── UK website
    └── English / GBP

Localization can apply to commerce data such as products, prices and currencies as well as editorial content. experienceleague.adobe.com

Downside: it's considerably more expensive and technically demanding to operate than PrestaShop or WooCommerce. Adobe's own comparison describes it as aimed at large businesses with in-house technical teams. www.shopify.com

2. 🥈 Shopware

I'd seriously consider Shopware 6 if you want something more modern/API-oriented than Magento.

Its sales-channel model is particularly nice for internationalization: each channel can define its countries, languages, currencies, payment methods, shipping methods and tax calculation. docs.shopware.com

It also supports country-specific tax-free rules and thresholds, including currency-dependent thresholds and VAT-ID validation for B2B. docs.shopware.com

I'd favor Shopware over Magento when you have a development team that prefers a modern architecture and you're building a fairly sophisticated headless/composable commerce stack.

3. 🥉 PrestaShop

PrestaShop is an excellent middle ground, particularly if you're heavily exposed to European markets.

Its localization packs can bring in country-specific currencies, taxes, tax rules, languages and units, and you can customize them afterward. help-center.prestashop.com

It's substantially easier to get running than Magento, but I'd be more cautious if your tax/pricing matrix is extremely complicated or you're operating a large B2B operation across dozens of jurisdictions.

What I would not choose first: WooCommerce

WooCommerce is fantastic when WordPress is central to the business, but for your particular requirement I'd rather have localization, taxation, currencies, stores and customer segmentation represented as core commerce concepts rather than assembled from numerous extensions.

The important distinction

If by "complex localization" you mean something like:

Country → state/province → customer type → VAT registration → product tax category → currency → price list → language → payment method → shipping method → tax-inclusive/exclusive display

then I'd narrow it to:

Magento/Adobe Commerce vs. Shopware.

And if you also need things like B2B price lists, multiple legal entities, different catalogs by region, ERP integration, tax engines, hundreds/thousands of localized storefront combinations, or sophisticated customer-specific pricing, I'd lean Adobe Commerce.

If your requirements are sophisticated but you want a cleaner, more modern development experience, I'd lean Shopware.

One other consideration: don't expect the ecommerce platform itself to be the authoritative source for every country's tax law. For serious international operations, you may want to integrate a dedicated tax service and let the commerce platform orchestrate the resulting tax calculation. Adobe explicitly documents integrations with external tax-calculation services such as Vertex for more advanced scenarios. experienceleague.adobe.comexperienceleague.adobe.comdocs.shopware.comexperienceleague.adobe.com

Bottom line: Adobe Commerce/Magento Open Source is my pick for maximum localization/tax complexity; Shopware is my pick for the best modern alternative. PrestaShop is the pragmatic choice if your complexity is primarily European rather than enterprise-wide.

For an international store with genuinely complex tax, currency, country, and pricing rules, I’d put Shopware 6 at the top of the self-hosted shortlist.

My ranking

\*Often dependent on extensions.

1. Shopware 6 — my first choice

Shopware's architecture is particularly well suited to localization because sales channels can independently define countries, languages, currencies, payment methods, shipping methods, and tax calculation. docs.shopware.com

Its tax system is also unusually flexible: you can create rules by country, state, ZIP/postcode, or effective date, and Shopware supports integrations with external tax providers for jurisdictions where native rules aren't sufficient. docs.shopware.com

That's important if your rules look like:

• US → state/local sales tax
• EU → VAT based on destination
• B2B → VAT-ID validation / tax exemption
• Different tax treatment by product category
• Country-specific tax-free thresholds
• Different prices by market
• GBP/EUR/USD/JPY/etc.
• Separate storefronts/domains per country
• Different payment/shipping methods by market
• Localized languages and SEO

Shopware explicitly supports country-specific tax-free thresholds, including different thresholds per currency and separate B2C/B2B treatment. docs.shopware.com

The big advantage: you can model localization as configuration within the platform rather than building a giant collection of WordPress plugins.

2. Adobe Commerce / Magento Open Source — strongest for extreme complexity

If you're operating at enterprise scale, I'd seriously consider Magento/Adobe Commerce instead.

It's particularly compelling when you have:

• Hundreds of thousands/millions of SKUs
• Multiple brands
• Multiple websites/stores/store views
• Sophisticated customer groups
• Complex B2B pricing
• ERP/PIM integration
• Extensive custom business logic
• A substantial engineering team

The downside is operational complexity. Magento is powerful, but you're effectively choosing an enterprise software platform rather than a simple ecommerce application. A 2026 comparison similarly places Magento toward very large B2B/catalog operations with substantial IT resources. docs.shopware.comdocs.shopware.comwww.datafirefly.comhelp-center.prestashop.comhelp-center.prestashop.com

3. PrestaShop — excellent middle ground

I'd choose PrestaShop if you want substantial international functionality without the engineering overhead of Magento.

Its localization system can import country-specific currencies, taxes, tax rules, languages and units, while its tax rules can be assigned to countries, groups of countries, or product types. help-center.prestashop.com

It also supports geographical zones, which can be useful for grouping countries/regions for shipping and tax purposes. help-center.prestashop.com

For a few thousand to perhaps tens of thousands of products, it's a very reasonable option.

4. WooCommerce — good, but I'd be cautious for your use case

WooCommerce itself handles country/state/postcode tax rules quite well. woocommerce.com

But once you need serious internationalization, you're more likely to assemble a stack of extensions: multilingual, currency, tax automation, pricing, etc. WooCommerce's own documentation, for example, points to separate solutions for multiple currencies and languages/store locations. woocommerce.com

That isn't inherently bad—WooCommerce's ecosystem is enormous—but for a business where tax + currency + localization are core infrastructure, I'd rather have more of that functionality in the underlying commerce platform.

What I'd choose

If you're a serious international merchant but not a huge enterprise:
→ Shopware 6

If you're enterprise-scale with a large engineering/IT organization:
→ Adobe Commerce / Magento

If you're mid-market and want strong international features with less complexity:
→ PrestaShop

If WordPress is already central to your business and localization complexity is moderate:
→ WooCommerce

One important caveat: don't expect the ecommerce platform itself to be the authoritative source of worldwide tax law. For genuinely complex international tax, the architecture I'd favor is Shopware + a dedicated tax engine/provider + ERP/accounting system, with the ecommerce platform responsible for applying the resulting tax decisions at checkout. Shopware itself recommends external tax providers for particularly complex jurisdictions such as the US. docs.shopware.com

If you tell me roughly how many countries you sell into, number of SKUs, B2B vs B2C, and whether prices are tax-inclusive, I can narrow this down to the best architecture rather than just the best platform.

For your use case, I’d shortlist Medusa, Shopware, and PrestaShop, but if complex tax + currency + country-specific rules are the primary concern, my first choice would be Medusa.

My ranking

1. Medusa — best if your rules are genuinely complicated

Medusa treats regions as a core commerce concept. You can give regions their own currency, tax configuration, payment providers, fulfillment options, pricing, and tax-inclusive/exclusive behavior. Its tax system supports regional rules, product-specific overrides, shipping taxes, and custom tax providers. docs.medusajs.com

The particularly important bit for your situation is extensibility: Medusa lets you replace/customize the tax provider and build custom workflows around it. That makes it much more suitable if you have rules like:

• different VAT/GST treatment by country
• product-category-specific tax rates
• tax-inclusive pricing in some markets but not others
• different prices by market/currency
• country-specific payment and shipping
• external tax engines
• unusual tax exemptions or B2B rules

It also supports multiple currencies through regions and localized pricing. docs.medusajs.com

2. Shopware — best if you want a more complete traditional commerce platform

Shopware is probably my choice over Medusa if you want a less developer-centric, more turnkey enterprise ecommerce experience. Its sales channels can define countries, languages, currencies, payment/shipping methods and tax calculation independently. docs.shopware.com

It also has substantial country-specific functionality, including B2B tax-free thresholds and VAT-ID handling. docs.shopware.com

3. PrestaShop — good value for conventional international stores

PrestaShop has strong out-of-the-box localization: localization packs can configure currencies, taxes, tax rules, languages, units and geographic specifics for individual markets. help-center.prestashop.com

I'd favor it when your requirements are complex but mostly fit conventional ecommerce concepts rather than requiring a custom commerce architecture.

The key distinction

If your store's localization looks like:

Country → tax regime → customer type → product category → exemption → currency → price list → shipping method

I'd choose Medusa.

If it looks more like:

Country → language → currency → VAT rules → payment/shipping → storefront

I'd seriously consider Shopware.

And if you're looking for something relatively conventional and economical, PrestaShop is worth considering.

One caveat: none of these should be treated as the authoritative source of tax law. For serious international compliance, I'd architect the ecommerce platform so it can delegate calculations to a tax service where appropriate, while keeping your market/currency/pricing configuration in the commerce platform. Medusa is particularly attractive here because its tax provider abstraction explicitly supports external tax services. docs.medusajs.comdocs.medusajs.com

Bottom line: Medusa for maximum localization flexibility; Shopware for maximum mature-platform functionality.

If complex localization is your primary requirement—many countries, tax regimes, currencies, languages, B2B/B2C rules, and potentially different catalogs/prices by market—I’d put Shopware 6 at the top of your shortlist.

My ranking

\* Sylius is extremely flexible, but much of the complexity is something your development team implements rather than something you get out of the box.

🥇 Shopware 6 — my default recommendation

Shopware has particularly strong native concepts for international commerce: sales channels, countries, languages, currencies and tax calculation can all be configured independently. Its sales channels can specify their available countries, languages, currencies and tax-calculation behavior. docs.shopware.com

Its tax system is also unusually useful for complicated localization. You can define country-specific rules down to states and ZIP/postal-code ranges, including date-effective rules, and Shopware supports integrations with external tax providers for more complicated systems such as US sales tax. docs.shopware.com

Currency handling is similarly sophisticated: currencies have their own pricing/rounding configuration and can be associated with countries and sales channels. docs.shopware.com

I'd choose it if you have scenarios like:

• US → state-specific sales tax
• EU → VAT + OSS
• UK → post-Brexit VAT treatment
• Canada → federal + provincial taxes
• B2B → VAT ID/exemption rules
• Different gross/net price presentation by market
• Multiple currencies with market-specific rounding
• Different languages and country-specific storefronts
• Different payment/shipping methods by country
• Multiple brands or regional stores from one installation

🥈 PrestaShop — excellent if you're retail-focused

PrestaShop is probably the strongest alternative if you want something simpler and more traditionally ecommerce-oriented.

Its localization system provides country-specific currencies, taxes, languages and units, while geographical zones let you group countries/regions for tax, shipping and trade restrictions. help-center.prestashop.com

Its tax rules can also combine multiple taxes for a product—PrestaShop specifically gives Quebec's GST + QST as an example. docs.shopware.comdocs.shopware.comhelp-center.prestashop.com

I'd lean PrestaShop over Shopware if your operation is primarily B2C retail and you don't need particularly sophisticated B2B workflows.

🥉 Adobe Commerce / Magento Open Source

If by "lots of rules" you mean enterprise-level complexity, Magento deserves serious consideration.

It's powerful for multi-store, multi-website, catalogs, customer groups and pricing, but I'd only choose it if you have the engineering budget to operate it properly. It's considerably heavier than PrestaShop and generally not my first choice unless your business complexity genuinely justifies it.

What about Sylius?

Sylius is the interesting choice for a developer-heavy organization.

If you want to build a custom commerce platform around your own domain model—especially headless/API-first—Sylius can be fantastic. But there's an important distinction:

Shopware gives you more localization machinery out of the box; Sylius gives you more freedom to build exactly the localization machinery you want.

So if your tax rules are genuinely unusual and you're comfortable maintaining custom PHP/Symfony code, Sylius could actually become the better long-term architecture.

One important caveat

No self-hosted ecommerce platform should be treated as the source of truth for every country's tax law.

For genuinely complicated international tax, I'd architect it as:

Ecommerce platform → tax engine/provider → authoritative tax calculation

rather than trying to encode every tax jurisdiction manually. Shopware explicitly supports tax-provider integrations for complex systems. docs.shopware.com

My recommendation

If I were choosing for your situation without knowing anything else:

Shopware 6 → best overall balance of localization + tax + currencies + multi-market + B2B + self-hosting.

PrestaShop → best if you're primarily international B2C retail and want lower operational complexity.

Sylius → best if you have a strong engineering team and want a highly customized/headless commerce architecture.

Adobe Commerce → best if you're genuinely operating at enterprise scale and can support its complexity.

If you tell me roughly how many countries/currencies you sell in, B2B vs B2C, annual order volume, and whether you need multiple catalogs/prices per country, I can narrow this down to a specific platform and architecture.

For an international store with genuinely complex tax, currency, language, and regional pricing rules, I’d put Magento Open Source at the top of the self-hosted list.

My ranking

\* Particularly strong if you're willing to implement/customize the tax layer.

1. 🥇 Magento Open Source — best overall

Magento's biggest advantage is its scope model: global → website → store → store view. That maps unusually well to international commerce. A single installation can have different domains, catalogs, languages, currencies and configurations, while sharing the underlying platform. experienceleague.adobe.com

For example, you can structure:

• example.com → US
• example.de → Germany
• example.fr → France
• separate store views → German/French/English
• different currencies per website/store view
• country-specific tax configuration
• different catalogs/pricing where necessary

Magento also has a fairly sophisticated tax-rule model: tax rules can combine product class + customer class + tax rate + geographic region, with priorities and compounding. experienceleague.adobe.com

Currency handling is similarly mature; Magento supports currencies from 200+ countries and can use different base currencies at the website level in a multisite installation. experienceleague.adobe.com

The downside: complexity. Magento gives you enormous flexibility, but you'll pay for it in infrastructure, development, upgrades, and operational expertise.

Magento Open Source documentation

2. 🥈 Shopware 6 — potentially better if you're Europe-heavy

I'd seriously consider Shopware if your business is primarily European and you want something somewhat less Magento-heavy.

Its strengths are international storefronts, sales channels, currencies, B2B functionality, and EU-oriented commerce workflows. It's particularly attractive if you're selling across Germany/EU and expect substantial customization.

3. 🥉 Medusa — best if your team is engineering-heavy

Medusa is interesting if "self-hosted" means we want to build our commerce architecture around an API/headless system, rather than wanting a giant prebuilt ecommerce application.

Its current localization model is quite good: regions can have their own currencies, countries, payment providers, fulfillment configuration, tax settings and tax-inclusive pricing. Tax regions can also have hierarchical/sublevel regions and product-specific tax overrides. docs.medusajs.com

It even supports custom tax providers, which is valuable if you're integrating something like a specialized tax engine rather than relying entirely on platform-native calculations. docs.medusajs.com

The catch is important: Medusa gives you building blocks rather than Magento's enormous amount of prebuilt commerce functionality. Its multilingual functionality is also still evolving; current translation support is centered on product-related resources. docs.medusajs.com

4. PrestaShop

Don't overlook PrestaShop if you want something simpler. Its localization packs can bring in country-specific states, taxes/tax rules, currencies, languages, date formats and units, which makes initial international setup convenient. docs.prestashop-project.org

I'd choose it over Magento when the business is international but the underlying pricing/tax model isn't exceptionally complicated.

What I'd choose for your situation

If you have lots of tax and currency rules, I'd narrow it to:

Magento Open Source → if you want the most mature all-in-one self-hosted platform.

Shopware 6 → if you're heavily EU-focused and want a somewhat cleaner operational experience.

Medusa → if you have a strong development team and want to make your own highly customized commerce/tax architecture.

One particularly important distinction: don't assume "supports multiple currencies" means it handles international pricing well. For your use case, I'd evaluate whether the platform can independently model:

country → state/province → customer type → product tax class → VAT/GST/sales tax → tax-inclusive/exclusive pricing → currency → price list → rounding → shipping tax → payment method → storefront/language

That's where Magento has a major advantage. Its official documentation explicitly covers country-specific tax configurations and examples for complicated jurisdictions such as the US and EU. experienceleague.adobe.com

If you tell me roughly how many countries you sell into, whether you do B2B, and whether prices differ by country rather than merely being currency-converted, I can give you a much more decisive Magento vs. Shopware vs. Medusa recommendation.

For an international store with lots of tax, currency, and market-specific rules, my top self-hosted pick would be Saleor, with Medusa as the strongest alternative.

My ranking

\*Usually dependent on extensions/plugins, which can make complex international setups harder to govern.

Why I'd lean Saleor

Saleor documentation treats channels, currencies, regions, payments, and tax logic as core commerce concepts. Its checkout supports currency-specific channels, tax exemptions, tax classes, and dynamic tax calculation through services such as Avalara or custom webhooks. saleor.io

That matters if, for example, you need:

• EU VAT rules that differ from UK VAT
• tax-inclusive consumer pricing in some markets but tax-exclusive B2B pricing elsewhere
• different currencies and price lists by market
• country-specific payment methods
• different catalogs or products by jurisdiction
• tax-exempt customers
• external tax engines
• multiple storefronts sharing one backend
• different fulfillment/shipping rules by country

Saleor's channel model is particularly attractive when "market" isn't simply "country." You can model different commercial configurations without creating a completely separate store. Saleor explicitly supports localizing product information, currencies, payment methods, and other aspects across storefronts/channels. saleor.io

When I'd choose Medusa instead

Medusa is arguably the better choice if your localization rules are unusually bespoke. Its architecture is extremely modular, and its Region and Tax modules are designed to be extended or replaced.

For example, Medusa supports:

• regional currencies and pricing
• country-specific tax calculation
• tax-inclusive pricing
• tax rules that override defaults for particular products
• tax treatment of shipping and gift cards
• external tax providers
• completely custom tax-provider logic medusajs.com

Its tax system can even combine parent/child tax regions and apply conditional tax-rate overrides—for example, a different rate for a particular product type. saleor.iosaleor.iomedusajs.comdocs.medusajs.comacademy.sylius.comdocs.medusajs.com

That's compelling if you're effectively saying "our tax engine is a business application in its own right."

The key distinction

I'd frame the choice this way:

Saleor → choose this if your priority is sophisticated international commerce modeling out of the box.

Medusa → choose this if your priority is having a highly programmable commerce backend that you can bend around unusual business rules.

Sylius → choose this if your team is strong in PHP/Symfony and wants maximum control at the application level. Sylius channels can independently configure currencies, languages, taxes, shipping, and payment methods, making it a serious option for complex localization. academy.sylius.com

One important caveat: none of these platforms should be treated as the authoritative source for worldwide tax compliance by themselves. For serious international operations, I'd architect the ecommerce platform to delegate jurisdiction/tax determination to a specialized tax service where appropriate, while keeping your market, pricing, catalog, and checkout rules in the commerce platform. Medusa explicitly supports this architecture, and Saleor supports dynamic tax calculation through apps/webhooks. saleor.iodocs.medusajs.com

If you tell me roughly how many countries you sell into, whether you're B2C/B2B, and whether you need EU/UK/US sales-tax complexity, I can narrow this to Saleor vs. Medusa vs. Sylius and give you an architecture recommendation.

For complex international localization, I’d put Medusa at the top of the shortlist—especially if you have a strong engineering team and want maximum control.

My ranking

1. Medusa — my pick for maximum flexibility

Medusa is particularly well suited to a store where tax rules aren't just "VAT by country."

Its architecture has explicit regions, tax regions, tax rules, currencies, and tax providers. Tax regions can be hierarchical, allowing things such as country → state/province overrides, and tax rules can vary by product/product type. You can also replace the built-in tax calculation with a custom tax provider. docs.medusajs.com

It also supports:

• different currencies and settings by region
• tax-inclusive vs. tax-exclusive pricing
• region-specific prices
• region-specific payment and fulfillment providers
• custom tax providers
• multiple countries within a region
• custom commerce workflows docs.medusajs.comdocs.shopware.com

Medusa documentation

Why I'd choose it: if your requirements include things like "Germany has one pricing/tax behavior, California another, Japan another, and certain SKUs have special tax treatment" and you expect those rules to keep evolving, Medusa's modular architecture gives your developers a lot of room to model that cleanly.

2. Shopware 6 — best if you want more out-of-the-box administration

Shopware is arguably the stronger choice if you want sophisticated localization without building as much of the commerce administration yourself.

Shopware supports country/region/customer-specific tax rates and currencies, multiple languages, and multiple sales channels. A sales channel can independently specify countries, languages, currencies, payment methods, shipping methods and tax calculation behavior. docs.shopware.com

Its tax system also supports tax providers for complex jurisdictions where native rules aren't enough. docs.shopware.com

Shopware official site

I'd pick Shopware over Medusa if your business team needs a mature admin interface for managing a large international catalog and many sales channels, rather than having developers encode much of that behavior.

3. Saleor — excellent headless alternative

Saleor is another very strong option if you're building a modern headless stack. Its architecture is API/GraphQL-centric and it explicitly supports multi-region setups involving currencies and storefronts. docs.saleor.io

Saleor documentation

I'd lean toward Saleor when API-first architecture and frontend flexibility matter more than having the deepest built-in tax-rule modeling.

The important distinction

For your use case, I wouldn't choose based simply on "supports multiple currencies and languages." Almost every serious platform does.

I'd evaluate whether it can handle this sort of matrix:

Customer country → shipping country → tax jurisdiction → customer type → product tax class → currency → price list → tax-inclusive/exclusive display → exemption status → payment method → fulfillment location

That's where Medusa and Shopware become especially interesting.

My recommendation:

• Medusa if you have developers and your localization rules are unusually complex/custom.
• Shopware 6 if you want the most mature combination of internationalization + administration + B2B/B2C capabilities.
• Saleor if you're committed to a headless/API-first architecture.

One caveat: for serious international tax compliance, I'd integrate a dedicated tax engine rather than treating the ecommerce platform's native tax tables as your ultimate source of truth. Shopware explicitly supports external tax providers, while Medusa supports custom tax providers. docs.medusajs.comdocs.shopware.com

If you tell me roughly how many countries, currencies, tax jurisdictions, B2B vs B2C, and whether you need OSS/IOSS, US sales tax, GST/HST, etc., I can narrow this down to a specific architecture and platform.

For complex international localization, I’d shortlist Shopware 6 and Magento Open Source, with Shopware 6 as my default recommendation unless you have unusually complex enterprise requirements.

🥇 Shopware 6 — best overall fit

I'd pick Shopware if your store has many countries, currencies, languages, tax jurisdictions, and region-specific pricing.

Its sales-channel architecture is particularly useful: you can associate countries, currencies, languages, domains, and localized content with different sales channels. Its tax system can apply rates by country and even by state/ZIP, while supporting B2B VAT-exemption scenarios. docs.shopware.comdocs.shopware.com

For example, you could structure:

• 🇺🇸 US → USD → English → US tax rules
• 🇬🇧 UK → GBP → English → UK VAT
• 🇩🇪 Germany → EUR → German → German VAT
• 🇫🇷 France → EUR → French → French VAT
• 🇯🇵 Japan → JPY → Japanese → Japanese consumption tax
• 🇦🇺 Australia → AUD → English → GST

And use separate domains, currencies and language configurations where appropriate. docs.shopware.comdocs.shopware.com

Shopware itself specifically highlights country-specific tax, customs, language and currency handling as core requirements for cross-border commerce. www.shopware.com

Shopware documentation

🥈 Magento Open Source — best for extreme complexity

Magento / Adobe Commerce is arguably more powerful if your localization requirements become an enterprise architecture problem.

Its multi-website/store/store-view model is exceptionally flexible. You can build separate regional storefronts while sharing catalog infrastructure, and it is highly extensible when tax, pricing, ERP, payment, fulfillment or customer-specific rules become unusual.

The downside is substantial: Magento is considerably more expensive and technically demanding to build and maintain. Current comparisons continue to position it as the heavyweight option for complex B2B/B2C international deployments. www.datafirefly.com

Magento Open Source documentation

🥉 PrestaShop — good if you're EU-heavy

PrestaShop is attractive if most of your complexity is European: multiple EU countries, languages, currencies, VAT and multiple stores.

It's easier to operate than Magento and has strong native multistore/multilingual capabilities. www.datafirefly.com

I'd choose it over Shopware if cost and operational simplicity matter more than having a highly sophisticated commerce architecture.

What I'd avoid

I wouldn't make WooCommerce the first choice if your defining problem is complex localization. It can absolutely handle international commerce, but once you combine dozens of tax jurisdictions, customer-specific pricing, multiple currencies, localized catalogs, regional payment methods and complicated fulfillment, you're likely assembling a fairly large plugin/integration stack.

My recommendation

If I were designing your stack:

Shopware 6 + dedicated tax engine + payment providers appropriate to each region

rather than trying to make the ecommerce platform itself the authoritative source for every tax rule.

For genuinely complicated tax compliance, I'd evaluate integrations with Avalara, Vertex, TaxJar, or local tax specialists, depending on your countries and whether you need VAT/GST, US sales tax, duties/import taxes, B2B exemptions, etc.

The key question is how complex your localization actually is. If you tell me roughly how many countries, currencies, languages, B2C vs B2B, and whether you need country-specific catalogs/prices/tax rules, I can narrow this to Shopware vs Magento vs PrestaShop and recommend an architecture.