ChatGPT answers, unedited

If complex international tax + currency localization is the core requirement, I’d narrow the self-hosted field to Adobe Commerce (Magento Open Source) and Medusa.

My practical comparison

Adobe Commerce/Magento Open Source is the more established choice when the localization rules themselves are the difficult part. Its tax engine combines product classes, customer classes, tax rates and geographic regions, and it supports multiple websites/stores/store views with separate currencies and localized configuration. Experience League Experience League Experience League

It also has explicit facilities for international VAT, tax-inclusive/exclusive pricing, tax zones, and country-specific configurations. Experience League Experience League

Medusa is particularly attractive if you have a strong engineering team and want to build a bespoke international commerce stack. Its region model associates countries with currencies, payments, fulfillment and tax behavior; its tax module supports regional tax rules and custom tax providers. Medusa Documentation Medusa Documentation Medusa Documentation

Medusa also supports tax-region inheritance/combination and country-specific tax calculation based on the customer's shipping address, which can be useful when your rules become granular. Medusa Documentation Medusa Documentation

What I'd choose based on your situation

• Hundreds of tax/country combinations, B2B + B2C, multiple storefronts, complicated catalog/pricing: Magento Open Source / Adobe Commerce
• Headless architecture, custom checkout, sophisticated engineering team, tax provider integrations: Medusa
• You want the platform to provide as much of the international-commerce machinery as possible: Magento
• You want the commerce engine to be a programmable foundation that you tailor heavily: Medusa

One important distinction: neither platform should be treated as a source of truth for constantly changing tax law. For serious international operations, I'd architect the store so tax calculation can be delegated to a specialized tax provider where necessary, while the ecommerce platform handles countries, currencies, catalog, customers and checkout.

If you tell me roughly how many countries you sell into, B2B vs B2C, whether prices are tax-inclusive, and whether you need VAT/GST/sales-tax automation, I can compare Magento vs Medusa specifically for your architecture.

Medusa is particularly attractive if you have a strong engineering team and want to build a bespoke international commerce stack. Its region model associates countries with currencies, payments, fulfillment and tax behavior; its tax module supports regional tax rules and custom tax providers.

Medusa also supports tax-region inheritance/combination and country-specific tax calculation based on the customer's shipping address, which can be useful when your rules become granular.

For an international store with many countries, currencies, tax regimes, localized pricing, warehouses, and payment rules, I’d shortlist Saleor, Adobe Commerce (Magento Open Source), and Medusa rather than a simpler WordPress-based stack.

How I’d compare them

Adobe Commerce/Magento has particularly mature tax-rule machinery: tax rules can combine product class, customer class, tax rate and geographic region, and it supports international tax configuration and VAT-related functionality. Experience League Experience League

Saleor is compelling if you're building a custom/headless storefront. Its architecture is designed around multi-channel commerce, and it is frequently used for multi-currency and multi-region catalogs. Macrostack Macrostack

Medusa has explicit multi-region support: regions can have their own currency, tax configuration, payment providers, fulfillment providers and pricing, while its translation functionality handles localized product content. Medusa Docs Medusa Docs

My practical recommendation

If by "lots of tax and currency rules" you mean things like:

• EU VAT + OSS/IOSS
• US state/local sales tax
• GST/VAT in multiple countries
• tax-inclusive vs. tax-exclusive pricing
• different prices by market rather than simple FX conversion
• tax exemptions and B2B VAT IDs
• different payment methods per country
• multiple warehouses and fulfillment regions
• localized catalogs and languages
• country-specific checkout rules

I'd investigate Adobe Commerce first and Saleor second.

The important distinction is that tax complexity isn't just a feature checkbox. For serious international commerce, you'll probably want a dedicated tax engine/service (such as Avalara, Vertex, TaxJar, etc.) rather than trying to encode every jurisdiction's tax law directly into the ecommerce application.

If your team is primarily TypeScript/Node, Medusa becomes particularly interesting: its official multi-region model already covers currency, tax, pricing, payment and fulfillment configuration. Medusa Docs

If you tell me roughly how many countries you sell into, B2C vs B2B, number of currencies, and whether you need multiple warehouses/legal entities, I can narrow this to a concrete architecture and platform choice.

If complex international tax + currency localization is the main requirement, I’d shortlist Shopware, Saleor, and Medusa—but my default choice would be Shopware if you want a mature merchant/admin experience, and Medusa if you want maximum developer control.

My ranking

🥇 Shopware 6 — my pick for most international stores

Shopware has unusually strong native localization machinery. Its tax system can define rules by country, state/region, ZIP/ZIP ranges, product, and customer group, with effective dates for tax changes. It also supports tax providers for situations where native rules aren't enough. Shopware Docs

Its country configuration can handle things such as B2B/B2C tax-free thresholds and currency-dependent thresholds, while the platform supports multiple currencies and sales channels. Shopware Docs Shopware

That's important if your requirements look like:

• EU VAT / OSS
• US state-level sales tax
• Different B2B vs. B2C treatment
• Country-specific tax exemptions
• Different tax-inclusive/exclusive price presentation
• Multiple currencies
• Different pricing by market
• Multiple storefronts/domains/languages
• External tax engines

I'd choose Shopware if your store is primarily a sophisticated merchant operation rather than a software project.

shopware.com

🥈 Medusa — best if you want to build around the platform

Medusa is particularly attractive if you have a strong engineering team.

Its regions can have their own currency, countries, payment providers, fulfillment providers, tax behavior, and tax-inclusive pricing. Tax regions can also be hierarchical—for example, country → state/province—with combinable rates. Medusa Docs Medusa Docs Medusa Docs

It also explicitly supports custom tax logic and external tax providers, which is valuable when your rules don't fit a conventional ecommerce tax model. Medusa

For example, you could model:

Market
 ├── Country
 │    ├── Customer type
 │    │    ├── B2C
 │    │    └── B2B
 │    ├── Currency
 │    ├── Tax regime
 │    ├── Price list
 │    ├── Payment methods
 │    └── Shipping rules
 └── Localization
      ├── Language
      └── Translated catalog

Medusa also has explicit multi-region and multilingual functionality, although some translation functionality is still evolving. Medusa Docs Medusa Docs

I'd choose Medusa if you expect to have unusual localization rules and want your developers to encode those rules rather than fight a monolithic platform.

medusajs.com

🥉 Saleor — excellent for headless enterprise commerce

Saleor is worth serious consideration if you're comfortable with Python + GraphQL and want a highly composable architecture.

I'd put it ahead of Medusa if your organization values a GraphQL-first, API-oriented architecture and sophisticated multi-channel operations more than having everything easily modified inside a TypeScript codebase.

One important distinction

For international tax compliance, don't choose a platform solely because it has "tax rules."

There's a big difference between:

Platform tax calculation

"Germany = 19% VAT"

and an actual international tax architecture:

customer location + shipping origin + product tax category + customer VAT status + transaction type + tax registration + thresholds + exemptions + effective dates + currency + rounding + tax-inclusive pricing + tax provider.

If your business genuinely has the latter, I'd strongly consider integrating a specialist tax engine rather than making the ecommerce platform your tax authority. Shopware explicitly supports tax-provider integrations, and Medusa supports external tax services/custom tax logic. Shopware Docs Medusa

Bottom line

Choose Shopware if you want the strongest out-of-the-box international commerce administration.

Choose Medusa if you want the strongest developer-customizable international commerce foundation.

Choose Saleor if you're building a serious headless/enterprise system around GraphQL.

Choose Magento/Adobe Commerce if your organization already has Magento expertise and your requirements are exceptionally large/complex; otherwise I'd be reluctant to take on its operational complexity for a new build.

If you tell me roughly how many countries, currencies, languages, B2B vs B2C, and which tax regimes (EU VAT, US sales tax, UK VAT, GST, etc.) you need, I can narrow this to one platform and map out the architecture I'd use.

For a self-hosted international ecommerce store with complex tax, currency, and localization rules, the best choice is usually not the same as the “best ecommerce platform” overall. You want strong multi-market architecture, tax-rule flexibility, local payment support, catalog localization, and the ability to integrate with tax engines and ERPs.

My shortlist:

Hostinger Open Source Groups## My recommendation by scenario

1. Large global operation: Magento Open Source

Choose this if you have:

• Many countries with different tax regimes
• Multiple storefronts
• Complex B2B pricing
• Regional catalogs
• ERP/PIM integrations
• Large product catalogs

Magento’s architecture is built around concepts like:

• Websites / stores / store views
• Multiple currencies
• Multiple languages
• Advanced catalog rules
• Complex customer groups
• Country-specific configurations

The downside: it is expensive to operate. You need experienced developers, proper hosting, and ongoing maintenance.

Best fit: millions in revenue, many markets, dedicated technical team.

2. Best balance for international retail: PrestaShop

For many international merchants, especially those selling across Europe, PrestaShop is a very strong fit. It has native support for:

• Multiple languages
• Multiple currencies
• Country-specific stores
• Tax rules
• Localized catalogs

HostingerAdvantages:

• Easier than Magento
• Designed as ecommerce software rather than a CMS plugin
• Strong VAT/GDPR ecosystem
• Good for medium-to-large catalogs

Weakness:

• Some advanced capabilities require paid modules
• Less enterprise-oriented than Magento

Best fit: 5–50 countries, retail brands, international DTC.

3. Most flexible: WooCommerce

WooCommerce is attractive if your store needs:

• Heavy content marketing
• Custom workflows
• WordPress ecosystem
• Lots of developer freedom

You can combine it with:

• Tax engines
• Currency plugins
• Translation systems
• Regional payment gateways

But localization is usually assembled from plugins rather than being deeply native. AFCommerce

Best fit: brands where content and customization matter more than enterprise commerce complexity.

4. Modern architecture: Spree Commerce or Saleor

If you have a technical team and want:

• Custom frontend
• Mobile apps
• Market-specific experiences
• API-first architecture

These are worth considering.

Spree Commerce, for example, focuses on multi-region commerce with localized storefronts, currencies, tax rules, and shipping options. Spree Commerce

Best fit: engineering-led companies.

For tax complexity specifically

The platform alone usually should not be your tax system. For serious international selling, look for integrations with:

• Avalara
• Vertex
• Regional VAT/GST services

You need support for:

• EU VAT / OSS / IOSS
• UK VAT
• US state + local sales tax
• Canada GST/HST/PST
• Australia GST
• Import duties and landed cost
• Tax-inclusive vs tax-exclusive pricing
• Tax exemptions

My ranking for your described use case

If you truly have “lots of tax and currency rules”, I would rank them:

1. Magento Open Source — most capable, highest complexity
2. PrestaShop — best international retail balance
3. Spree Commerce — best if you have developers building a custom stack
4. WooCommerce — best flexibility, but more integration work
5. Saleor — excellent architecture, but requires engineering maturity

A key question changes the answer: How many countries/currencies are you supporting, and are you mainly B2C retail, B2B wholesale, or both? For example, 10 EU countries with VAT is a very different problem from 80 countries with duties, local payments, and multiple warehouses.

If complex tax + currency + country-specific pricing/localization is the core requirement, my first choice for a self-hosted store is Magento Open Source (Adobe Commerce).

My ranking

1. Magento Open Source — best for maximum localization complexity

• Strong multi-site/store/store-view architecture for different countries, languages, domains, catalogs, and pricing. Experience League Experience League
• Sophisticated tax model: product classes + customer classes + tax zones/rates, with rules based on shipping/billing address or origin. Experience League Experience League
• Multiple currencies are a first-class feature, and multisite installations can have different base currencies at the website level. Experience League Experience League
• Particularly good if you need different tax treatment for B2B vs B2C, product categories, jurisdictions, VAT/GST, exemptions, and regional storefronts.

Downside: considerably more expensive and technically demanding to operate than WooCommerce or PrestaShop.

2. Shopware 6 — best alternative

• I'd seriously consider it if you're primarily selling in Europe and want a modern, self-hosted stack with strong multi-language/multi-store capabilities.
• It tends to be a nicer developer experience than Magento, while still being substantially more commerce-oriented than WooCommerce.
• A 2026 comparison rates Shopware highly for native multilingual, multi-store, B2B, and headless capabilities. Datafirefly
• PrestaShop — good middle ground

• Attractive if internationalization is important but your requirements aren't at Magento/Shopware enterprise complexity.
• Generally simpler to operate than Magento.
• WooCommerce — excellent if you're already a WordPress shop

• Flexible and highly extensible, but I wouldn't choose it because your tax/currency rules are unusually complicated.
• WooCommerce itself supports multiple tax/shipping zones, but multiple currencies and multilingual operation generally require extensions. WooCommerce WooCommerce
• Its own documentation says its automated tax solution isn't intended for especially complex situations such as extensive international taxation, detailed address-dependent taxes, product-specific tax codes, or automated filing/remittance. WooCommerce

The important distinction

If by "complex localization" you mean something like:

30 countries → different currencies → different price lists → VAT/GST/sales tax → tax-inclusive vs tax-exclusive pricing → B2B VAT exemptions → different product tax classes → country-specific catalogs → local languages → local domains → regional payment methods

then I'd choose Magento Open Source or Shopware, not WooCommerce.

If you're doing something more like:

USD/EUR/GBP + 5 languages + country-specific shipping/tax rates

then WooCommerce or PrestaShop can be considerably easier and cheaper.

One particularly useful Magento capability is that its tax engine explicitly combines product class, customer class, tax rate, and geographic region, which maps well to complicated international tax matrices. Experience League

My pick: Magento Open Source if tax/localization flexibility matters more than operational simplicity; Shopware 6 if you want a somewhat more modern architecture and especially strong European commerce support.

If you tell me roughly how many countries, currencies, languages, B2B/B2C split, and whether you need VAT/GST automation, I can narrow this down to Magento vs Shopware vs PrestaShop and suggest the architecture I'd use.

If complex localization is the main requirement, my shortlist would be:

1. Adobe Commerce / Magento Open Source — best for the deepest built-in localization and tax configuration
2. Saleor — best modern headless option for sophisticated multi-region operations
3. Medusa — best if you want maximum developer flexibility and a TypeScript stack

My pick: Adobe Commerce / Magento

For a genuinely complicated international operation, I'd lean Adobe Commerce / Magento.

It has unusually mature concepts for international commerce: a hierarchy of websites/stores/store views, localized storefronts, country/region-specific tax rules, customer and product tax classes, VAT handling, and website-level base currencies. Experience League Experience League Experience League

It can also accept currencies from 200+ countries and lets different websites have different base currencies. Experience League

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

• EU VAT vs UK VAT vs US sales tax
• Different tax treatment by product category
• B2B vs B2C taxation
• Different prices by market rather than simply converting currencies
• Multiple storefronts/domains/languages
• Country-specific catalogs
• Different currencies and payment methods
• Complex tax integrations

The downside is operational complexity. Magento is substantially heavier to develop, upgrade, secure, and operate than newer headless platforms.

When I'd choose Saleor instead

Saleor is probably my choice if you're building a new, API-first international commerce system rather than maintaining a traditional Magento-style storefront.

Its channel architecture is particularly useful: channels can represent different storefronts/markets and control things such as currency, pricing, product availability and logistics. Saleor also emphasizes localization across currencies, payment methods and content. Saleor Commerce

I'd choose Saleor when you have a strong engineering team and want:

• Headless architecture
• Multiple countries/markets from one backend
• Multiple warehouses
• Multiple currencies
• Multiple storefronts
• Fine-grained permissions
• Custom frontends
• Integration-heavy architecture

Where Medusa fits

Medusa is compelling if your team is primarily TypeScript/Node.js.

Its Region model directly addresses international commerce: regions can have their own currencies, tax settings, payment providers and fulfillment providers, and Medusa supports tax-inclusive pricing by region. Medusa Docs Medusa Docs

The important distinction is that Medusa gives you a lot of flexibility, but you may end up implementing more of your unusual tax/business logic yourself. That's a feature if your business rules are highly bespoke; it's a disadvantage if you want the platform to provide lots of mature commerce machinery out of the box.

Quick decision

One important caveat: none of these should be treated as the authoritative source for every country's tax law. For serious cross-border taxation, I'd architect the ecommerce platform so that tax calculation can be delegated to a specialist tax engine when necessary, while the commerce platform owns the resulting prices, orders and tax records.

If you tell me roughly how many countries you sell into, B2B vs B2C, whether prices are tax-inclusive, and whether you need VAT/GST/sales-tax automation, I can narrow this down to a specific architecture rather than just a platform recommendation.

If complex tax + currency localization is the primary requirement, I’d put Odoo at the top of your shortlist.

My ranking

1. Odoo — best for complex international tax/accounting

• Strongest native model for country-specific fiscal rules.
• Its fiscal positions can automatically map taxes based on customer location, country groups, VAT status, and business type. Odoo Odoo
• Has country-specific fiscal localization packages with taxes, fiscal positions, charts of accounts, and legal statements. Odoo
• Supports multiple currencies and foreign-currency transactions. Odoo
• Ecommerce can independently configure tax-inclusive vs. tax-exclusive displayed pricing by website. Odoo
• Particularly compelling if you also need ERP, accounting, inventory, purchasing, multiple legal entities, and invoicing.
• PrestaShop — best if ecommerce is the center of the business

• I'd consider it if you want a dedicated ecommerce platform rather than an ERP with ecommerce.
• It has a mature ecosystem around international storefronts, currencies, languages, tax rules and localization.
• The tradeoff is that really sophisticated tax compliance can require additional modules/integrations rather than being as deeply integrated into the accounting model as Odoo.
• WooCommerce — best for flexibility/ecosystem

• Extremely extensible and easy to customize.
• Its tax system supports country/state-specific tax rates and tax classes. WooCommerce
• But WooCommerce's core model is less attractive for a business with many jurisdictions, complicated tax determination, multiple entities and accounting requirements. Its own documentation points toward extensions for more sophisticated tax solutions. WooCommerce WooCommerce
• It also has a single base currency per store, with additional currencies generally handled through extensions. WooCommerce

What I'd choose for your situation

If by "lots of tax and currency rules" you mean things like:

• EU VAT / OSS and reverse charge
• US state/local sales tax
• GST/HST
• B2B vs. B2C tax treatment
• VAT-number validation
• tax-inclusive pricing in some markets and exclusive pricing in others
• different tax rules based on shipping/billing destination
• multiple legal entities
• different accounting localizations
• dozens of currencies
• exchange-rate accounting
• tax-exempt customers
• import/export duties
• country-specific invoices and reporting

I'd choose Odoo unless there is a strong reason not to. Its tax architecture is much closer to what you need than simply adding a bunch of ecommerce tax plugins. Odoo explicitly supports tax mapping and automatic fiscal-position selection based on localization and customer characteristics. Odoo Odoo

One important caveat: no ecommerce platform should be treated as the source of truth for international tax liability. Even Odoo's documentation distinguishes between configuring tax mechanics and the underlying legal obligations. For a large international operation, I'd pair the platform with a tax engine/compliance provider where appropriate.

If you tell me roughly how many countries you sell into, whether you have multiple legal entities, B2B vs B2C mix, and your approximate order volume, I can narrow this down to Odoo vs PrestaShop vs WooCommerce vs Medusa/Saleor and recommend an architecture.

For a genuinely international store with complicated tax, currency, pricing, and localization rules, I’d shortlist Saleor and Medusa, with Saleor as my first choice if complexity is the dominant requirement.

My ranking

*Usually requires extensions and careful integration.

🥇 Saleor — my default recommendation

Saleor is particularly attractive when your internationalization isn't just "show EUR instead of USD."

Its channel model can represent different markets/sales contexts, with each channel having its own currency, pricing, availability, etc. Its documentation also explicitly supports multi-region commerce. Saleor Documentation

That makes it a strong foundation for scenarios like:

• US → USD + US tax treatment
• EU → EUR + VAT
• UK → GBP + UK VAT
• Japan → JPY + Japanese tax rules
• B2B EU → different prices and VAT handling
• Different catalogs/availability by country
• Different warehouses and fulfillment rules
• Market-specific payment methods
• Market-specific promotions

The big advantage is that internationalization is part of the commerce model rather than something you bolt onto a basic store.

The downside is that Saleor is a serious engineering platform: Python/Django + GraphQL, with a steeper operational/development curve. Saleor Documentation OSSAlt

🥈 Medusa — better if your rules are highly bespoke

Medusa would be my choice if your team is primarily TypeScript/Node.js and you expect to implement lots of unusual commerce logic.

Medusa has first-class multi-region support: regions can define currency, tax configuration, shipping and payment options, and its documentation explicitly describes using it for country-specific tax rules and currencies. Medusa Documentation

Its big advantage is programmability. If you have rules such as:

"If customer is in country X, buying product category Y, from warehouse Z, and has tax status A, calculate price according to rule B..."

I'd be very comfortable building that in Medusa.

It's more of a commerce framework than an all-encompassing international commerce suite. That's a feature if you have good developers; it's a liability if you want lots of sophisticated functionality prebuilt. ShipGarden Eryx Innovations Lab

🥉 Sylius — don't overlook this one

Sylius is especially compelling if your engineering team is PHP/Symfony.

For a business where the commerce rules themselves are unusually complicated, Sylius deserves a serious evaluation. It's more framework-oriented and highly customizable than something like WooCommerce.

I'd put it ahead of Medusa if your team already has deep Symfony expertise.

What I would not optimize for

For your use case, I wouldn't choose a platform simply because it has:

• "100+ currencies"
• "multi-language support"
• a tax-rate table
• currency conversion
• country-specific storefronts

Those are relatively easy.

The difficult part is the interaction between localization dimensions:

customer location × tax nexus × customer tax status × product tax class × fulfillment origin × destination × currency × price list × channel × payment method × rounding rules

That's where platform architecture matters.

My recommendation

If you told me:

"We operate in 20–50 countries, have complicated VAT/GST/sales-tax requirements, multiple currencies, multiple warehouses, different B2B/B2C pricing, and expect the rules to keep getting more complicated."

I'd start a proof-of-concept with Saleor and Sylius, and use Medusa as the alternative if your team is TypeScript-heavy.

If you're a JavaScript/TypeScript team, I'd probably choose Medusa.

If you're a Python/GraphQL team or enterprise team, I'd lean Saleor.

If you're a Symfony/PHP team and tax/pricing logic is exceptionally bespoke, I'd seriously consider Sylius.

And importantly: don't expect the ecommerce platform itself to be your tax engine. For serious international commerce, I'd architect the platform so tax calculation can be delegated to a dedicated tax service when necessary, while the commerce platform remains responsible for orders, prices, carts, channels, customers, fulfillment, etc.

If you tell me roughly how many countries, currencies, B2B vs B2C, and whether you need VAT/GST/sales-tax calculation, I can narrow this down to a specific architecture and platform. Saleor Documentation Medusa Documentation

For an international store where tax, currency, country, and pricing rules are genuinely complex, I’d shortlist Medusa and Saleor, with Medusa as my default choice if localization logic is a major differentiator.

My ranking

🥇 I'd pick Medusa

medusajs.com is particularly attractive when your localization requirements go beyond simply "show EUR in France and USD in the US."

Its commerce model has explicit regions, currencies, tax regions, tax rates/rules, payment providers, fulfillment providers, and localized pricing. A region can contain multiple countries, while tax regions can go down to subnational levels such as US states or Canadian provinces. Medusa Docs Medusa Docs Medusa Docs

The particularly important part for your use case is that Medusa supports custom tax providers. That means you aren't forced to encode every country's tax system directly into the ecommerce application—you can integrate a tax engine or your own tax service. Medusa Docs Medusa Docs

It also supports tax-rate overrides based on conditions such as product type, and parent/child tax regions can combine rates. Medusa Docs

So I'd choose Medusa if you have things like:

• Different VAT/GST/sales-tax treatment by country or subregion
• Tax-inclusive pricing in some markets and tax-exclusive in others
• Product-specific tax treatment
• Different currencies and price lists by market
• Country-specific payment and fulfillment methods
• Complex rules that don't fit a standard ecommerce configuration
• A development team capable of owning the system

Medusa's own multi-region architecture is explicitly designed around this model: currency, taxes, payments, fulfillment, shipping and pricing can all vary by region. Medusa Docs

🥈 Saleor is the strongest alternative

saleor.io would be my choice if you want a very sophisticated headless/multi-channel architecture and your international markets map cleanly to channels.

Saleor makes channels a fundamental concept: a single backend can have storefronts with independent currencies, languages and pricing. Its documentation also has a dedicated multi-region approach. Saleor Documentation Saleor Commerce

Its open-source version is self-hostable, and Saleor has an extension/app architecture for things such as tax services. Saleor Commerce

I'd favor Saleor over Medusa if you have, for example:

US storefront + EU storefront + UK storefront + wholesale storefront + several localized brands, all sharing one underlying catalog.

I'd favor Medusa if the harder problem is:

"Our tax/pricing/localization rules are unusual and we need to build exactly the logic we want."

What I would not choose purely for localization

PrestaShop can be very capable for international stores, and Odoo becomes especially compelling if your ecommerce operation is tightly coupled to accounting, inventory, purchasing and ERP.

But if your primary requirement is a highly customizable localization/tax engine, I'd rather start with the more developer-oriented architecture of Medusa or Saleor than accumulate plugins and customizations around a conventional storefront.

Bottom line

For a technically capable team: Medusa
For sophisticated multi-channel/headless commerce: Saleor
For ecommerce + full ERP/accounting: Odoo
For a more conventional PHP ecommerce deployment: PrestaShop

One important caveat: no ecommerce platform should be your sole source of truth for international tax compliance. For dozens of jurisdictions, I'd architect the store so the ecommerce platform determines the commercial context (customer location, products, prices, exemptions, etc.) and a dedicated tax service determines the legally applicable tax.

If you tell me roughly how many countries you sell into, whether you are B2C/B2B, and whether you need VAT/GST/sales-tax calculation at checkout, I can narrow this down to a specific architecture and compare Medusa vs Saleor vs Odoo for your situation.

If complex tax, currency, and regional rules are the main reason you're choosing a platform, my shortlist would be:

1. Magento Open Source / Adobe Commerce — best overall for maximum localization complexity.
2. Saleor — best modern/headless choice if your engineering team is comfortable with Python + GraphQL.
3. Medusa — best if you're a TypeScript/Node.js team and want maximum architectural flexibility.
4. PrestaShop — worth considering if Europe is a major part of your business and you want a more conventional ecommerce admin.

My pick: Magento Open Source

For your particular description, I'd lean Magento Open Source.

It has unusually deep native support for international store structures: one installation can operate multiple websites, stores, and store views with different languages, domains, catalogs, currencies, and configurations. Experience League Experience League

Its currency model is also quite granular: you can configure accepted/display currencies and, in a multisite installation, have different base currencies at the website level. Experience League

Tax configuration is similarly tied into the store/site configuration, customer groups, product tax classes, shipping origin, etc. Experience League

That makes Magento particularly attractive when your localization isn't simply:

"Translate the storefront and show EUR instead of USD."

but more like:

"Customers in Germany see one catalog and VAT treatment; Canadian customers see another tax regime and CAD pricing; the UK has different pricing/shipping rules; B2B customers have different tax exemptions; and some products have jurisdiction-specific treatment."

Where Saleor gets interesting

docs.saleor.io

Saleor would be my second choice—and potentially first if you're building a heavily customized headless storefront.

Its architecture explicitly supports channels and multi-region commerce, including regions, currencies, and storefronts. It is GraphQL-first and designed to be extended through apps/integrations. Saleor Documentation

I'd choose Saleor over Magento if:

• You want a modern headless architecture.
• Your team is strong in Python/GraphQL.
• You want to model commerce logic in your own applications.
• You expect multiple storefronts/channels/warehouses.
• You don't want Magento's comparatively heavy legacy architecture.

The tradeoff is that you may need to build more of your localization/tax integrations yourself.

Medusa

medusajs.com

I'd choose Medusa if your engineering organization is primarily TypeScript/Node.js.

Its modular architecture makes it particularly attractive when your tax engine, pricing engine, fulfillment logic, or regional rules are unusual and you expect to replace/customize those components. Current comparisons generally position Medusa as the more developer-friendly option, while Saleor provides more built-in enterprise commerce machinery. Eryx Innovations Lab ShipGarden

But for "I have lots of complicated international tax rules", I wouldn't pick Medusa solely because it's easier to customize. You're potentially signing yourself up to build and maintain quite a bit of commerce infrastructure.

How I'd rank them for your use case

• WooCommerce can handle very sophisticated localization, but complicated international setups often become a collection of extensions rather than one coherent commerce model.

The important caveat

For genuinely international commerce, don't evaluate the platform's "tax support" checkbox. Evaluate whether it can represent your actual tax model.

I'd specifically test these scenarios before committing:

• Tax-inclusive vs tax-exclusive pricing by country.
• VAT/GST/sales-tax registration in multiple jurisdictions.
• Customer-specific tax exemptions.
• B2B VAT IDs and reverse charge.
• Digital vs physical products with different tax rules.
• Product-specific tax classes.
• Shipping-tax differences.
• Import duties and landed cost.
• Tax calculated from billing vs shipping vs warehouse origin.
• Different tax rules for the same SKU in different countries.
• Tax rounding requirements.
• Currency-specific price lists rather than simple FX conversion.
• Fixed regional prices despite exchange-rate fluctuations.
• Multiple currencies per market.
• Refunds when exchange rates have changed.
• Country-specific catalogs and payment methods.
• Multiple legal entities and tax registrations.

If several of those are "yes," I'd start with Magento Open Source vs Saleor, not WooCommerce vs Shopify alternatives.

If you tell me roughly how many countries you sell into, whether you're B2C/B2B, your main regions (US/EU/UK/Canada/etc.), and whether you need headless, I can narrow this down to a specific architecture and tax stack.

But for "I have lots of complicated international tax rules", I wouldn't pick Medusa solely because it's easier to customize. You're potentially signing yourself up to build and maintain quite a bit of commerce infrastructure.

How I'd rank them for your use case

• WooCommerce can handle very sophisticated localization, but complicated international setups often become a collection of extensions rather than one coherent commerce model.

The important caveat

For genuinely international commerce, don't evaluate the platform's "tax support" checkbox. Evaluate whether it can represent your actual tax model.

I'd specifically test these scenarios before committing:

• Tax-inclusive vs tax-exclusive pricing by country.
• VAT/GST/sales-tax registration in multiple jurisdictions.
• Customer-specific tax exemptions.
• B2B VAT IDs and reverse charge.
• Digital vs physical products with different tax rules.
• Product-specific tax classes.
• Shipping-tax differences.
• Import duties and landed cost.
• Tax calculated from billing vs shipping vs warehouse origin.
• Different tax rules for the same SKU in different countries.
• Tax rounding requirements.
• Currency-specific price lists rather than simple FX conversion.
• Fixed regional prices despite exchange-rate fluctuations.
• Multiple currencies per market.
• Refunds when exchange rates have changed.
• Country-specific catalogs and payment methods.
• Multiple legal entities and tax registrations.

If several of those are "yes," I'd start with Magento Open Source vs Saleor, not WooCommerce vs Shopify alternatives.

If you tell me roughly how many countries you sell into, whether you're B2C/B2B, your main regions (US/EU/UK/Canada/etc.), and whether you need headless, I can narrow this down to a specific architecture and tax stack.

If complex international tax + currency localization is the core requirement, my first choice would be Magento Open Source / Adobe Commerce, with Shopware 6 as the strongest alternative.

My ranking

🥇 Magento Open Source — best overall for your use case

Magento's architecture is unusually well suited to businesses where country/region isn't just a translation but changes the commercial rules.

It has a hierarchical website → store → store view model, allowing different domains, catalogs, languages, currencies and configuration from one installation. Experience League Experience League

Its tax engine also combines:

• Product tax classes
• Customer tax classes
• Tax zones/rates
• Shipping/billing/origin-based calculations
• Tax-inclusive or tax-exclusive pricing
• Multiple tax priorities/compounding
• Cross-border price consistency
• VAT-related functionality

Experience League Experience League Experience LeagueCurrency handling is similarly mature: base currency can be scoped at the website level, while display/accepted currencies can be configured per store view, and Magento supports currencies from 200+ countries. Experience League Experience League Experience League

That makes it particularly attractive if your requirements look like:

US → USD + sales tax
EU → EUR + VAT, potentially different VAT treatment by country
UK → GBP + VAT
Canada → CAD + GST/HST/PST
Japan → JPY + consumption tax
Switzerland → CHF + Swiss VAT
B2B customers → tax-exempt/reverse-charge rules
Different countries → different price presentation, payment methods and shipping rules

You can model a lot of that natively, while specialized tax providers can handle the jurisdictions where hard-coded tax tables aren't sufficient. Adobe specifically documents integrations/extensions for services such as Vertex. Experience League

The downside: Magento is powerful partly because it's complicated. Its operational, development and upgrade burden is considerably higher than something like Shopware.

🥈 Shopware 6 — probably the better modern alternative

I'd seriously consider Shopware 6 if you want sophisticated internationalization but don't want to inherit Magento's ecosystem complexity.

It's especially compelling if you're building a headless/composable architecture or have developers comfortable with Symfony/PHP.

I'd choose Shopware over Magento when:

• Your catalog isn't enormous or exceptionally complicated.
• You want a cleaner modern development experience.
• Headless storefronts are important.
• You need multiple sales channels/markets.
• Your team values developer productivity over Magento's enormous extension ecosystem.

🥉 Sylius — best if your business rules are genuinely unusual

If by "lots of tax and currency rules" you actually mean highly bespoke business logic, Sylius deserves serious consideration.

It's less of an all-in-one merchant platform and more of a commerce framework. That's a disadvantage if you want everything ready-made, but an advantage if your developers need to implement unusual rules such as:

Customer nationality + shipping country + warehouse + product classification + customer type → determine tax treatment, price list and currency.

For that kind of business, I'd rather have a clean domain model that we can customize than fight a conventional ecommerce platform's assumptions.

What I would pick

If I were responsible for the architecture:

1. Magento Open Source — best default for maximum built-in international commerce capability.
2. Shopware 6 — best balance of sophistication and maintainability.
3. Sylius — best for a heavily customized/headless operation.
4. PrestaShop — good if complexity is moderate.
5. WooCommerce — I'd avoid it for a genuinely tax-heavy multinational operation unless WordPress is a major requirement.

One important distinction: don't choose a platform solely because it has a tax-rate table. For serious international commerce, you need to separate commerce configuration from tax determination. The latter can involve VAT registration status, exemptions, product taxability, place of supply, nexus, thresholds, address validation, rounding and changing legislation.

For your description, Magento Open Source + a dedicated tax engine/provider would be my starting architecture rather than trying to make the ecommerce platform itself the authoritative source of every country's tax law. Magento's own documentation acknowledges that complex cross-border scenarios can require a tax-calculation extension such as Vertex. Experience League

If you tell me roughly how many countries you sell into, B2B vs B2C, number of SKUs, and whether you need headless, I can narrow this down to Magento vs Shopware vs Sylius for your specific architecture.

• Your catalog isn't enormous or exceptionally complicated.
• You want a cleaner modern development experience.
• Headless storefronts are important.
• You need multiple sales channels/markets.
• Your team values developer productivity over Magento's enormous extension ecosystem.

🥉 Sylius — best if your business rules are genuinely unusual

If by "lots of tax and currency rules" you actually mean highly bespoke business logic, Sylius deserves serious consideration.

It's less of an all-in-one merchant platform and more of a commerce framework. That's a disadvantage if you want everything ready-made, but an advantage if your developers need to implement unusual rules such as:

Customer nationality + shipping country + warehouse + product classification + customer type → determine tax treatment, price list and currency.

For that kind of business, I'd rather have a clean domain model that we can customize than fight a conventional ecommerce platform's assumptions.

What I would pick

If I were responsible for the architecture:

1. Magento Open Source — best default for maximum built-in international commerce capability.
2. Shopware 6 — best balance of sophistication and maintainability.
3. Sylius — best for a heavily customized/headless operation.
4. PrestaShop — good if complexity is moderate.
5. WooCommerce — I'd avoid it for a genuinely tax-heavy multinational operation unless WordPress is a major requirement.

One important distinction: don't choose a platform solely because it has a tax-rate table. For serious international commerce, you need to separate commerce configuration from tax determination. The latter can involve VAT registration status, exemptions, product taxability, place of supply, nexus, thresholds, address validation, rounding and changing legislation.

For your description, Magento Open Source + a dedicated tax engine/provider would be my starting architecture rather than trying to make the ecommerce platform itself the authoritative source of every country's tax law. Magento's own documentation acknowledges that complex cross-border scenarios can require a tax-calculation extension such as Vertex.

If complex international tax + currency localization is the core requirement, my first choice would be Shopware 6, with Medusa as the better choice if you have a strong engineering team and want a highly customized/headless architecture.

My ranking

🥇 Shopware 6 — best overall

I'd pick Shopware if you want a relatively complete commerce system rather than building substantial localization infrastructure yourself.

Shopware's sales-channel model lets you associate countries, languages, currencies, payment methods, shipping methods and tax calculation with individual channels. Its self-hosted edition also supports different domains with their own language/currency configuration. Shopware Documentation Shopware Documentation

The tax system is particularly relevant to your situation: you can define tax rules by country, state/province, ZIP code and effective date, and Shopware explicitly supports external tax providers for complicated tax systems such as the US. Shopware Documentation

It also handles things like:

• B2C vs. B2B tax treatment
• Gross vs. net pricing
• VAT rules
• Country/state-specific taxes
• Multiple currencies and currency-dependent thresholds
• Multiple languages/locales
• Different prices by sales channel
• Separate international storefronts/domains

For example, Shopware documents a US configuration involving state-specific sales tax, US localization and a separate customer group for net pricing. Shopware Documentation

shopware.com

🥈 Medusa — best if you're engineering the commerce platform

Medusa is extremely compelling if you have developers and don't mind assembling a more customized stack.

Its architecture has explicit Region and Tax modules. Regions can have their own currency, countries, payment providers, fulfillment providers and tax-inclusive/exclusive pricing. Medusa Docs Medusa

More importantly for complicated tax jurisdictions, Medusa supports hierarchical tax regions—for example, a country with state/province subregions—and tax rules can override defaults for particular products/product types. It can also delegate calculation to a custom/external tax provider. Medusa Docs Medusa Docs

That's excellent if your actual requirement is something like:

US → state → city → product tax category + customer type + nexus + destination

rather than simply:

Germany → 19% VAT.

Medusa also has BCP-47 locale support such as en-US and fr-FR. Medusa Docs

medusajs.com

The important distinction

For your use case, I wouldn't choose based primarily on the number of supported currencies or languages. Tax architecture is the harder problem.

I'd evaluate the platform against these requirements:

1. Destination-based taxation — customer location vs. billing/shipping address.
2. Tax jurisdiction hierarchy — country → state/province → county/city/ZIP.
3. Product tax categories — different rates for different products.
4. B2B VAT/GST handling — VAT IDs, exemptions, reverse charge.
5. Tax-inclusive vs. tax-exclusive pricing by market.
6. Tax-provider integration — Avalara, Vertex, TaxJar, etc.
7. Effective-dated rules — tax changes shouldn't corrupt historical orders.
8. Currency-specific price lists rather than simply converting USD at checkout.
9. Rounding rules per currency/jurisdiction.
10. Country-specific payment/shipping/customs rules.
11. Separate storefronts/domains where legal/commercial requirements differ.
12. Auditability — you need to be able to explain why a particular tax was charged on an old order.

On those criteria, Shopware is the safer default. Medusa becomes more attractive if your team wants to own the architecture and integrate specialized services.

My recommendation:

• Shopware 6 → best balance of mature international commerce + self-hosting + configurable tax/localization.
• Medusa → best if you're building a highly customized/headless global commerce stack.
• WooCommerce → excellent ecosystem, but I'd be less enthusiastic for very complex multinational tax logic because you can end up depending heavily on extensions.
• Saleor → strong technical/headless option, but I'd put it behind Shopware/Medusa for your particular localization-heavy requirement.

If you tell me roughly how many countries you sell into, B2B vs B2C, and whether you're headless, I can narrow this down to a specific architecture—including which tax engine I'd pair with it.

That's excellent if your actual requirement is something like:

US → state → city → product tax category + customer type + nexus + destination

rather than simply:

Germany → 19% VAT.

Medusa also has BCP-47 locale support such as en-US and fr-FR.

For an international store with serious tax, currency, regional pricing, and localization complexity, I’d put medusajs.com at the top of the shortlist.

My ranking

1. Medusa — best overall for complex localization

• Strong concept of regions, with each region able to have its own currency, countries, tax configuration, shipping, payments, and fulfillment. Medusa Docs Medusa Docs
• Supports hierarchical tax regions, including country → state/province/canton structures, and product-specific tax overrides. Medusa Docs
• Lets you plug in custom tax providers, which is important if you need something like Avalara/TaxJar or your own tax engine rather than a simple percentage table. Medusa Docs
• Supports tax-inclusive pricing by region or currency—useful when, for example, EU prices need to be VAT-inclusive while US prices are displayed pre-tax. Medusa Docs
• Current versions also have explicit store locale/translation support. Medusa Docs
• The big advantage is that its architecture is designed to let you replace or extend commerce logic, rather than forcing every country's rules into a rigid configuration model.
• Saleor — best if you want a polished GraphQL/headless architecture

• saleor.io has a strong multi-region/multi-channel model. Channels can have independent currencies, languages, and pricing. Saleor Documentation Saleor Commerce
• I'd favor it if your team is particularly comfortable building a sophisticated headless storefront around GraphQL.
• Its extension/app architecture is attractive when localization involves external services.
• Sylius — best for maximum PHP/Symfony customization

• I'd consider sylius.com especially if your organization is already heavily invested in Symfony/PHP.
• It's a very good choice when you want the commerce engine to become a deeply customized business application rather than primarily configuring an off-the-shelf store.

The important distinction

For your use case, I wouldn't choose based on "how many currencies does it support?" That's relatively easy.

I'd evaluate whether the platform can model:

Customer location → legal entity → tax jurisdiction → product tax classification → tax registration → currency → price list → tax-inclusive/exclusive presentation → payment method → shipping rules → invoicing

That's where international ecommerce gets difficult.

Medusa is particularly compelling here because its region/tax architecture explicitly supports nested jurisdictions, conditional tax rates, different currencies, tax-inclusive pricing, and replaceable tax providers. Medusa Docs Medusa Docs Medusa Docs

One caveat

If by "lots of tax rules" you mean hundreds/thousands of jurisdictions with constantly changing VAT/GST/sales-tax rules, I would not try to encode all of that directly into the ecommerce platform.

I'd use:

Medusa → dedicated tax engine → tax calculation → Medusa order

Medusa explicitly supports custom/third-party tax providers, making that architecture practical. Medusa Docs

So my short answer is:

Medusa for maximum localization flexibility; Saleor for a sophisticated headless/GraphQL implementation; Sylius if you're a Symfony-heavy organization.

If you tell me which countries you sell into, whether prices are tax-inclusive, and roughly how many SKUs/orders you have, I can give you a much more concrete Medusa vs Saleor vs Sylius architecture recommendation, including the tax engine I'd pair with it.

For an international store with complex tax, currency, language, pricing, and regional rules, the strongest self-hosted choices are usually:

1. Adobe Commerce (Magento Open Source) — best for maximum complexity
2. Shopware — best modern international commerce stack
3. Odoo — best if tax/accounting/ERP integration is the core challenge
4. PrestaShop — best for many European markets with lighter complexity

Bemeir Odoo## My ranking for your use case

Data Firefly Odoo## 1. Magento / Adobe Commerce — choose this if rules are truly complicated

This is usually the safest choice when you have things like:

• Different catalogs by country
• Customer-group pricing
• Wholesale vs retail pricing
• Multiple tax regimes
• VAT/GST/sales tax differences
• Complex promotions
• Regional inventory
• Multiple storefronts under one installation
• Custom checkout logic
• ERP integration

Magento’s architecture is built around multiple websites, stores, and store views, which maps well to a global operation. It also has a large ecosystem for tax services, payment gateways, ERP connectors, and localization modules. Bemeir Liquid Web

Downside: it is expensive to operate well. You need strong developers, DevOps, caching/search infrastructure, and ongoing maintenance.

Best if you are doing:

• 10+ countries
• thousands of SKUs
• B2B + B2C
• complex pricing logic
• high transaction volume

2. Shopware 6 — probably the best balanced choice

Shopware is a strong alternative if you want:

• Modern API-first architecture
• Headless commerce options
• Multiple sales channels
• Good multilingual support
• Country-specific tax rules
• European localization
• Easier merchant administration than Magento

It supports multiple languages, currencies, and country-specific tax configurations, and is popular among internationally operating European merchants. Shopware Shopware

I would seriously consider Shopware if:

• you are Europe-heavy
• you want easier daily operations
• you want a modern frontend stack
• you do not need Magento-level customization

3. Odoo — best when tax complexity is really an accounting problem

If your biggest pain is:

• VAT registrations
• invoices
• accounting rules
• inventory valuation
• warehouses
• subsidiaries
• purchasing
• CRM

then Odoo can be very compelling because ecommerce is integrated with a broader ERP system. Odoo supports country-specific fiscal localization modules designed around accounting and compliance requirements. Odoo

The tradeoff:

• storefront capabilities are not as commerce-specialized as Magento/Shopware
• you may customize more for a premium ecommerce experience

4. PrestaShop — good international value

PrestaShop is worth considering if you have:

• many languages
• many European customers
• moderate catalog complexity
• smaller technical team

It has strong multilingual/localization capabilities, but for very advanced pricing, B2B, and global workflows you may eventually outgrow it. Data Firefly

What I would avoid for your description

I would be cautious with:

• WooCommerce if tax logic is a core differentiator. It can do almost anything, but often through many plugins that create upgrade and compatibility issues.
• Simple headless carts unless you already have a strong backend ERP/tax system.

My recommendation by scenario

• Global enterprise (US + EU + Asia + B2B): Magento Open Source / Adobe Commerce
• International brand, mostly B2C, modern stack: Shopware 6
• Manufacturer/distributor with complex finance: Odoo
• European multilingual retailer: PrestaShop

A key question: how complex are your rules? For example:

1. How many countries do you sell into?
2. Do you need country-specific catalogs/prices, or only tax/currency changes?
3. Are you B2C, B2B, or both?
4. Do you already use an ERP (SAP, Odoo, NetSuite, Dynamics, etc.)?

Those answers could change the recommendation substantially.

For an international store where tax, currency, pricing, and country-specific rules are genuinely complex, my first choice would be Adobe Commerce (Magento Open Source)—with Medusa as the strongest alternative if you want a more modern, developer-centric architecture.

My ranking

*Usually requires carefully selected extensions for serious international tax requirements.

1. Adobe Commerce / Magento Open Source — best overall for your use case

I'd lean toward Adobe Commerce/Magento if your requirements include things like:

• Different tax rules by country, state/province, customer type, and product class
• VAT/GST/sales-tax combinations
• Tax-inclusive vs. tax-exclusive pricing
• Different pricing/catalogs by market
• Multiple websites, currencies, languages, and domains
• B2B + B2C localization
• Country-specific payment and shipping methods
• External tax engines such as Vertex
• A large catalog and complicated promotions

Magento's tax engine combines product classes, customer classes, tax zones/rates, and tax rules, and its calculation can be based on shipping address, billing address, or origin. Experience League Experience League

Its multi-site architecture is particularly useful: one installation can run multiple websites/stores/store views with different languages, domains, catalogs, currencies, and configurations. Experience League

Currency support is also mature: base currency can be scoped at the website level, with separate accepted and display currencies. Adobe says Commerce supports currencies from more than 200 countries. Experience League Experience League

The downside: Magento is considerably heavier to operate and customize than newer headless platforms. You'll want a competent development/DevOps team.

2. Medusa — best if you want modern and highly customizable

I'd seriously consider Medusa if you're building a custom storefront and don't want Magento's monolithic architecture.

Medusa has a particularly nice concept for international commerce: regions encapsulate country groupings, currencies, payment providers, fulfillment providers, and regional settings. Medusa Docs Medusa Docs

Its tax system supports:

• Tax regions
• Parent/child tax regions
• Different rates by region
• Product-specific tax rules
• Custom tax providers
• Third-party tax engines

Medusa Docs Medusa DocsIts own multi-region documentation explicitly covers country-specific tax, currency, shipping, payment, and fulfillment configurations. Medusa Docs

The big advantage is that you can replace/customize pieces of the commerce engine rather than fighting against a giant pre-existing platform.

I'd pick Medusa over Magento if your store is highly bespoke and you have a strong engineering team.

3. Saleor — excellent headless option

Saleor is another strong candidate if you're going API-first/headless. Its channel/market architecture is well suited to running different storefront experiences for different markets, and you can pair it with a custom localization layer.

I'd put it behind Medusa for your particular requirement because tax/business-rule customization is likely to become more important than simply supporting multiple storefronts.

What I'd choose

If you told me:

"We sell in 30+ countries, have different VAT/GST/sales-tax rules, different tax-inclusive pricing requirements, multiple currencies, country-specific payments, and potentially need a tax engine."

I'd choose Magento Open Source/Adobe Commerce.

If instead you said:

"We have a strong engineering team, want a Next.js/headless storefront, and our international pricing/tax logic is unusual enough that we want to own the architecture."

I'd choose Medusa.

The important distinction is that "supports multiple currencies" isn't enough for your situation. You want the platform to model the relationship between market → customer location → tax jurisdiction → product taxability → price → currency → payment → fulfillment without turning every new country into a pile of custom plugins.

If you tell me roughly how many countries/markets you operate in, B2B vs. B2C, and whether you need VAT/GST/sales-tax calculation at checkout, I can narrow this down to a specific platform + tax-engine architecture.

For complex international tax, currency, and localization rules, my first choice would be Adobe Commerce / Magento Open Source if you truly want self-hosting and have the technical team to operate it.

My ranking

1. Adobe Commerce / Magento Open Source — best for complex localization

• Strong multi-website/store/store-view architecture, so different countries can have distinct catalogs, languages, currencies, pricing, and configuration. Experience League
• Sophisticated tax rules combining product class + customer class + geographic tax rate, with priorities and compounding. Experience League Experience League
• Supports different base currencies at the website level and separate display/accepted currencies. Experience League
• Handles tax-inclusive/exclusive pricing, shipping tax, discount-tax ordering, cross-border pricing, etc. Experience League Experience League
• Can integrate specialized tax engines such as Vertex when native rules aren't sufficient. Experience League

Best if: you sell across many jurisdictions, have B2B/B2C differences, need country-specific pricing/catalogs, and expect substantial customization.

2. Shopware 6 — probably the best alternative

• Particularly attractive if you're European-focused and want a more modern, API-first architecture.
• Strong multi-store, multilingual and B2B capabilities; current comparisons rate its internationalization highly. Datafirefly Datafirefly
• I'd consider it ahead of Magento if your requirements are complex but you want a somewhat cleaner modern platform and don't need Magento's enormous ecosystem.
• PrestaShop — good for European international retail

• Excellent value for multilingual/multistore European commerce and generally easier to operate than Magento.
• I'd choose it for a moderately complex international catalog rather than an organization with extremely intricate tax/pricing logic. Datafirefly
• WooCommerce — best when WordPress/content is central

• Extremely flexible, but for complex localization itself, you're likely assembling multiple plugins/extensions rather than getting the architecture from the core platform.
• That can become painful when tax, currency, invoicing, checkout, ERP, and localization plugins interact.

The important distinction

If by "lots of tax and currency rules" you mean something like:

US + EU + UK + Canada + Australia + Japan, different VAT/GST/sales-tax treatments, B2B VAT IDs, tax-inclusive EU prices, tax-exclusive US prices, country-specific catalogs, multiple currencies, different rounding rules, and different prices by market

then Magento/Adobe Commerce is the strongest fit.

Its tax model explicitly supports combinations of customer class, product class, geographic region, tax rates, priorities, and compound taxes, rather than treating tax as merely "country → percentage." Experience League

It also has a particularly useful concept of website → store → store view, which lets you separate market configurations without necessarily running completely separate installations. Experience League

One caveat

Don't assume the ecommerce platform should be your source of truth for tax rates.

For serious international operations, I'd architect it roughly as:

Commerce platform → tax engine → payment/ERP/accounting

with something like a specialized tax service handling jurisdiction/rate determination. Magento's own documentation explicitly discusses integrations such as Vertex for this purpose. Experience League

So my recommendation is:

Magento Open Source if you want maximum self-hosting/control and can handle the engineering burden.

Shopware 6 if you want a more modern architecture and especially strong European/B2B capabilities.

PrestaShop if you want substantially lower complexity/cost and your tax requirements aren't exceptionally intricate.

If you tell me which countries you sell into, B2B vs B2C, approximate SKU/order volume, and whether you need country-specific catalogs/prices, I can narrow this down to a platform and architecture rather than just a generic ranking.

For an international store with serious tax, currency, catalog, and localization complexity, I would generally rank self-hosted platforms like this:

Spree Commerce AFCommerce## My recommendation by scenario

1. Complex global operation (20+ countries, multiple tax regimes)

Choose Magento Open Source / Adobe Commerce.

It is usually the strongest choice when you need:

• Multiple websites, stores, and store views
• Different catalogs by country
• Regional pricing rules
• B2B pricing and customer groups
• Complex tax integrations
• ERP/PIM/CRM integrations
• Custom checkout logic
• Large product catalogs

The downside: it behaves more like an enterprise application than a simple store. You need experienced developers and DevOps.

2. Europe-first international retailer

Choose Shopware.

Shopware is especially attractive if your complexity comes from:

• EU VAT rules
• Multiple European languages
• Multiple currencies
• Country-specific storefronts
• GDPR-sensitive workflows
• Regional payment methods

Its "sales channels" model maps well to country storefronts. Bemeir

3. Highly customized global commerce platform

Choose Spree Commerce.

Spree is a strong option if you are building a custom stack rather than buying a traditional ecommerce package:

• Headless architecture
• Custom frontend
• Multiple markets
• API-driven integrations
• Custom tax/pricing engines

Spree specifically focuses on multi-market setups with localized currencies, languages, tax rules, and market-specific pricing. Spree Commerce Spree Commerce

4. Mid-sized international retailer

Choose PrestaShop.

Good if you need:

• Many languages
• Multiple currencies
• Country-specific tax settings
• European localization
• Faster deployment than Magento

It is a practical choice for many cross-border retailers, although very advanced pricing and compliance requirements can require extensions. AFCommerce BitBag

Features I would require before choosing

For your use case, I would not evaluate platforms only on "multi-currency." Look for:

Tax

• VAT/GST/sales tax rules by jurisdiction
• Tax-inclusive vs tax-exclusive pricing
• B2B VAT number validation
• Tax exemption workflows
• Tax engine integrations (Avalara, Vertex, etc.)

Currency

• Fixed regional price lists (not just FX conversion)
• Currency rounding rules
• Historical exchange rates stored with orders
• Multi-currency accounting exports

Localization

• Separate catalogs by market
• Translation workflows
• Local SEO URLs
• Regional product availability
• Local payment methods

Operations

• Multiple warehouses
• Regional inventory
• Customs/duties handling
• ERP integration
• Audit-friendly order records

My shortlist

If I were choosing for a serious international business:

1. Magento Open Source — maximum capability, highest complexity
2. Shopware — best balance for European/global localization
3. Spree Commerce — best if you have a strong engineering team
4. PrestaShop — best value for mid-market international retail

I would avoid building a highly international operation on WooCommerce unless your localization needs are relatively unusual but manageable, because the tax/currency/plugin stack can become harder to govern over time. AFCommerce

A few details would change the recommendation substantially:

• approximate number of countries you sell to
• B2C only vs B2B + B2C
• product count/SKUs
• whether you need marketplace features
• whether you have developers in-house
• which regions matter most (EU, US, Middle East, APAC, LATAM)

If complex tax, currency, country, and localization rules are the main requirement, my first choice would be Magento Open Source (Adobe Commerce), with Shopware as the strongest alternative.

My ranking

1. Magento Open Source — best for maximum tax complexity

Adobe's Magento/Adobe Commerce ecosystem is probably the safest choice if your store has rules like:

• Different VAT/GST/sales-tax treatment by country, state/province, ZIP/postcode
• Different tax classes for products and customers
• B2B vs. B2C taxation
• Tax-inclusive vs. tax-exclusive pricing
• Cross-border pricing
• Multiple websites/store views with different currencies
• Country-specific catalogs and pricing
• Complex shipping-tax treatment
• External tax engines such as Vertex

Magento's tax engine explicitly combines product class + customer class + tax rate + geographic region, and can calculate based on shipping address, billing address, or origin. Experience League Experience League

Its currency architecture is also unusually strong: you can have different base currencies at the website level and different display currencies at the store-view level. Experience League Experience League

It supports currencies from 200+ countries and lets you configure currency display separately by store/view. Experience League

Big caveat: Magento is powerful but comparatively heavy. You'll want experienced developers/DevOps, particularly if you're maintaining a large catalog and many regional storefronts.

experienceleague.adobe.com

2. Shopware — arguably the better modern alternative

Shopware is what I'd investigate seriously if you're primarily selling into Europe and want something somewhat more modern/developer-friendly.

Shopware lets tax rules vary by country, region, ZIP code, product, and customer group, and supports dated tax rules—useful when rates change at a particular point in time. Shopware Documentation

It also has strong multi-currency and multi-sales-channel capabilities. Shopware

One particularly important point for an international merchant: Shopware explicitly recommends using external tax providers when tax regulations become too complex to practically model internally. Shopware Documentation

That makes a stack such as:

Shopware + Avalara/Vertex/etc. + payment provider + ERP

quite compelling.

shopware.com

What I'd choose for your situation

If by "lots of tax and currency rules" you mean hundreds of combinations across countries, customer types, products, and jurisdictions, I'd choose:

Magento Open Source + external tax engine

rather than trying to encode every tax rule directly into the ecommerce platform.

Magento has particularly mature primitives for tax classes, geographic tax rules, multiple websites/store views, currencies, and cross-border pricing. Experience League Experience League

If you prioritize European localization, modern architecture, and easier day-to-day development, I'd put Shopware very close behind.

I would not make WooCommerce my first choice for this particular problem. It's extremely extensible and localization-friendly, but its international tax architecture tends to become more dependent on plugins as complexity grows. WooCommerce itself is translation-ready, but that's a different problem from having a sophisticated international tax engine. WooCommerce

Bottom line:
Magento Open Source for maximum localization/tax sophistication; Shopware if you want nearly the same class of international capability with a more modern European-oriented stack.

If you tell me roughly how many countries you sell to, B2B vs B2C, and whether you need VAT/GST/sales-tax automation, I can narrow this down to a specific architecture and compare Magento vs. Shopware feature-by-feature.

For an international store with complicated tax, currency, language, catalog, and regional pricing rules, I would generally rank self-hosted platforms like this:

SwingIntel Open Source Groups## My recommendation by scenario

1. Large global operation: choose Magento Open Source

Best if you have:

• Multiple storefronts (US, EU, APAC, etc.)
• Different catalogs by country
• Complex B2B pricing
• Customer groups and negotiated prices
• Multiple warehouses
• Thousands to hundreds of thousands of SKUs
• Heavy ERP/tax/payment integrations

Magento's strongest advantage is its multi-website / multi-store architecture. You can model countries, brands, currencies, languages, catalogs, and pricing rules separately without forcing everything into one simple storefront. Bemeir

Downside: it requires experienced developers and DevOps. It is usually not a "install and configure yourself" platform.

Pick Magento if tax complexity is business-critical.

2. International retail with many languages: choose PrestaShop

PrestaShop is a strong choice when you need:

• Many languages
• Many currencies
• Country-specific tax rules
• Localized product information
• EU VAT workflows

It is more ecommerce-focused than WooCommerce and generally easier to operate than Magento. Open Source Groups

Good fit:

• Fashion
• Consumer goods
• Cross-border retail
• European markets

Less ideal:

• Very complex B2B pricing
• Huge catalogs
• Deep enterprise workflows

3. Modern mid-market + B2B: choose Shopware

Shopware 6 is worth considering if you want:

• API-first architecture
• Headless storefront options
• Strong content/localization workflows
• B2B capabilities
• Regional sales channels

It is particularly popular with European merchants and is a good middle ground between PrestaShop and Magento. Qualimero

4. Avoid WooCommerce for very complex localization unless you have a strong reason

WooCommerce can work, but international complexity often becomes a plugin stack:

• tax plugin
• currency plugin
• translation plugin
• shipping rules plugin
• ERP connector
• payment localization plugin

That can become fragile. WooCommerce is excellent when your advantage is WordPress content and marketing, but it is not my first choice for a tax-heavy global commerce operation. Open Source Groups

Features I would evaluate before choosing

For your case, do not just compare "multi-language" support. Check:

Tax

• VAT/GST support
• Tax-inclusive vs tax-exclusive pricing
• Tax exemptions
• Digital goods rules
• Tax provider integrations (Avalara, Vertex, TaxJar, etc.)
• Import duties and landed cost support

Currency

• Multiple base currencies
• Currency-specific pricing
• Exchange rate automation
• Rounding rules
• Local payment methods

Catalog localization

• Different products per country
• Different availability by region
• Different descriptions/images
• Different SEO URLs

Operations

• Multi-warehouse inventory
• Regional fulfillment
• Returns rules by country
• Local invoices and legal documents

My shortlist

If I were building:

• $10M+ GMV, global, complex tax/compliance: Magento Open Source
• $1M–$20M GMV, international retail: Shopware or PrestaShop
• Europe-heavy multilingual store: PrestaShop
• Custom app-like commerce experience: Saleor/Medusa
• Marketing/content-first store: WooCommerce

Open Source Groups PrintifyIf you share:

1. number of countries you sell in,
2. approximate SKU count,
3. B2C vs B2B,
4. whether you need VAT/GST automation, and
5. your ERP/accounting system,

I can narrow this to a likely best fit.

For an international store with genuinely complex tax, currency, language, and country-specific rules, my top self-hosted choice would be Shopware.

My ranking

Why I'd pick Shopware

Shopware's sales-channel model is particularly well suited to international operations. You can associate countries, languages, currencies, payment methods, shipping methods, and tax calculation behavior with individual sales channels. Shopware Docs Shopware Docs

Its tax system goes beyond a simple country → VAT rate mapping. You can define rules by country, state, ZIP code/ZIP ranges, product/customer circumstances, and effective date. It also supports external tax providers for tax regimes that become too complicated to maintain natively. Shopware Docs

Currency handling is similarly mature: currencies can be configured by country or sales channel, while Shopware's localization architecture supports different language/country combinations. Shopware Shopware

The Rule Builder is another major advantage for your use case. Rules can combine conditions such as sales channel, currency, language, billing country, dates, and other attributes, which is useful when localization logic starts interacting with commercial rules. Shopware

Where Medusa gets interesting

I'd choose Medusa instead if you're technically strong and want a highly customized/headless architecture.

Medusa has first-class regions, currencies, tax regions, tax rules, and tax providers. Tax regions can have hierarchical relationships, and rates can be overridden based on product/type conditions. Medusa Docs Medusa Docs

Its multi-region model explicitly supports different currencies, taxes, payment providers, fulfillment options, and prices per region. Medusa Docs

The tradeoff is important: Medusa gives developers more architectural freedom, while Shopware gives operators more mature commerce functionality out of the box.

My recommendation by scenario

• Many countries + complicated VAT/GST/sales-tax rules + multiple storefronts: Shopware
• Headless storefront + custom pricing/tax engine + strong engineering team: Medusa
• Extremely unusual business/tax workflows that don't fit conventional ecommerce: Drupal Commerce
• Mostly conventional international retail: WooCommerce or PrestaShop

One important caveat: don't expect the ecommerce platform itself to be your global tax authority. For US sales tax, EU VAT, Canadian GST/HST/PST, Australian GST, etc., I'd architect the system so the platform's tax engine can hand off calculations to a specialized tax provider when appropriate. Shopware explicitly supports this model. Shopware Docs

If you tell me roughly how many countries you sell into, whether you're B2C/B2B, and whether you need things like EU OSS/IOSS, US state sales tax, VAT-inclusive pricing, tax exemptions, and country-specific price lists, I can narrow this down to the best 2–3 architectures for your particular setup.

Its tax system goes beyond a simple country → VAT rate mapping. You can define rules by country, state, ZIP code/ZIP ranges, product/customer circumstances, and effective date. It also supports external tax providers for tax regimes that become too complicated to maintain natively. Shopware Docs

Currency handling is similarly mature: currencies can be configured by country or sales channel, while Shopware's localization architecture supports different language/country combinations. shopware.com shopware.com

The Rule Builder is another major advantage for your use case. Rules can combine conditions such as sales channel, currency, language, billing country, dates, and other attributes, which is useful when localization logic starts interacting with commercial rules. shopware.com

Where Medusa gets interesting

I'd choose Medusa instead if you're technically strong and want a highly customized/headless architecture.

Medusa has first-class regions, currencies, tax regions, tax rules, and tax providers. Tax regions can have hierarchical relationships, and rates can be overridden based on product/type conditions.

Its multi-region model explicitly supports different currencies, taxes, payment providers, fulfillment options, and prices per region.

For complex international localization, my top self-hosted choice would be Shopware 6, with Adobe Commerce / Magento Open Source as the stronger alternative if your tax and catalog logic is exceptionally complex.

My ranking

• WooCommerce can handle sophisticated taxation, but you'll generally assemble more of the localization stack from extensions.

1. 🥇 Shopware 6 — my default recommendation

Shopware is particularly attractive when your international operation has different countries, currencies, tax regimes, prices, languages, domains, payment methods and shipping rules.

Shopware's sales-channel model lets you configure countries, languages, currencies and tax calculation at the channel level. Its self-hosted domains can also have their own language, currency and localization configuration. Shopware Documentation Shopware Documentation

It also supports things such as:

• Country-specific tax rules
• B2B/B2C tax treatment
• Currency-specific thresholds
• Multiple currencies per sales channel
• Different prices by country/currency
• Multiple languages
• Different domains/storefronts
• Country-specific payment and shipping methods
• Tax-provider integrations for especially complicated jurisdictions Shopware Documentation Shopware Documentation

The big advantage is you don't necessarily need a separate store instance for every country. You can maintain common product data centrally and override what differs by sales channel. Shopware

That's a very good architecture for, say:

US + Canada + UK + EU + Australia + Japan, with different VAT/GST rules, currencies, price lists, languages and checkout requirements.

2. 🥈 Adobe Commerce / Magento Open Source

Adobe's Commerce platform is probably the better choice if tax logic and organizational complexity are extreme.

Magento's hierarchy of websites → stores → store views gives you extremely granular separation of catalogs, currencies, locales and storefronts. Experience League Experience League

Its tax engine combines:

• Product tax classes
• Customer tax classes
• Tax rates
• Tax zones
• Customer/shipping/billing geography
• Different tax-display configurations
• VAT-related functionality
• Fixed/compound taxes Experience League Experience League

Currency support is also very mature: Adobe documents support for currencies from 200+ countries, and multi-site installations can have different base currencies at website scope. Experience League Experience League

I'd choose Magento over Shopware if:

• You have dozens of storefronts/websites.
• You have highly customized B2B pricing.
• Your catalog itself differs substantially by market.
• You have sophisticated ERP/PIM/OMS integrations.
• You have a dedicated engineering team.
• You're comfortable with substantially higher operational complexity.

The important caveat: don't make the ecommerce platform your tax authority

If by "lots of tax rules" you mean US sales tax + EU VAT/OSS + UK VAT + Canadian GST/HST/PST + Australian GST + Japanese consumption tax + exemptions + registrations + changing rates, I wouldn't try to encode all of that manually in the ecommerce platform.

Instead, I'd architect it roughly as:

Shopware/Magento → tax engine/provider → checkout → ERP/accounting

The ecommerce platform determines the transaction context; a dedicated tax service can handle jurisdictional calculation and continuously changing tax rules. Shopware itself explicitly recommends tax-provider integrations for complex tax systems such as those encountered in the US. Shopware Documentation

Bottom line

I'd start with Shopware 6 unless you already know you need Magento's enormous ecosystem and architectural flexibility.

• Shopware 6: best overall balance for a sophisticated international store.
• Adobe Commerce/Magento: best when complexity, scale and customization outweigh development/maintenance cost.
• PrestaShop: good if you want considerably less infrastructure complexity.
• WooCommerce: excellent when WordPress is central, but I'd hesitate to make it the foundation of a highly complex multinational tax operation.

If you tell me roughly how many countries, currencies, storefronts, B2B vs B2C, and which tax jurisdictions you operate in, I can narrow this down to a specific architecture rather than just the platform choice.

The ecommerce platform determines the transaction context; a dedicated tax service can handle jurisdictional calculation and continuously changing tax rules. Shopware itself explicitly recommends tax-provider integrations for complex tax systems such as those encountered in the US.

Bottom line

I'd start with Shopware 6 unless you already know you need Magento's enormous ecosystem and architectural flexibility.

For a self-hosted international store with complex tax, currency, and localization rules, the strongest choices are usually:

1. Adobe Commerce (Magento Open Source) — best for maximum complexity
2. Shopware — best modern alternative, especially for Europe
3. Odoo — best if accounting/ERP localization is central
4. PrestaShop — best lower-cost international option

Bemeir Odoo## My ranking for your use case

Datafirefly Odoo## 1. Magento Open Source — my default recommendation for "lots of rules"

Choose Magento if you have things like:

• Different tax rules by country/state/province
• Multiple legal entities
• Separate regional catalogs
• Different pricing per currency
• Wholesale/B2B pricing
• Complex customer groups
• Multiple warehouses
• Custom checkout logic
• ERP integrations

Magento's architecture is designed around websites → stores → store views, which maps well to global operations (for example: US store, EU store, Japan store, each with different currencies, taxes, languages, and catalogs). Bemeir Liquid Web

Downside: it is technically demanding. You need experienced developers, good hosting, and disciplined extension management.

2. Shopware — excellent if Europe is a major market

Shopware is very strong when you need:

• EU VAT handling
• GDPR-oriented deployments
• Multiple languages
• Multiple currencies
• Regional storefronts
• Modern API/headless setups

Its Sales Channels model is a good fit for country-specific storefronts without creating completely separate systems. Shopware Shopware

I would seriously consider Shopware over Magento if:

• your business is EU-heavy,
• your catalog is not extremely complicated,
• your team values easier daily administration.

3. Odoo — best when tax rules are tied to accounting

If your pain point is not just checkout tax but the whole operation:

• VAT/GST compliance
• invoicing
• accounting
• inventory
• subsidiaries
• local fiscal requirements

Odoo becomes very attractive because its fiscal localization modules are designed around country-specific accounting and compliance requirements. Odoo

The tradeoff: Odoo is more of an ERP ecosystem with ecommerce attached, rather than a pure ecommerce engine.

What I would avoid for your scenario

WooCommerce

Great for:

• one/few markets
• content-heavy brands
• simpler tax setups

Less ideal for:

• dozens of jurisdictions
• complex pricing matrices
• enterprise inventory/tax workflows

Pure headless builds (Medusa, Saleor, custom)

Powerful, but you end up building a lot:

• tax logic
• promotions
• localization workflows
• admin tooling

Good for companies with a strong engineering team.

My practical recommendation

• 50+ countries, complex catalog, B2B, multiple legal entities: Magento Open Source
• Europe-first international retailer: Shopware
• Commerce + accounting/ERP complexity: Odoo
• Small-to-mid international seller: PrestaShop

The biggest architecture decision is not currency conversion itself — it is whether your business needs one global catalog with regional rules or separate country operations with different catalogs, taxes, and fulfillment.

If you tell me:

1. number of countries you sell to,
2. B2C vs B2B,
3. ERP/accounting system (SAP, NetSuite, Odoo, QuickBooks, etc.),
4. approximate SKU count,
5. whether you need tax calculation (Avalara/TaxJar/VAT services),

I can narrow this to a specific stack.

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.