Best European Alternatives to WooCommerce

Why people leave WooCommerce

WooCommerce is the incumbent on this site that you are already hosting yourself.

The plugin is GPL, it is published by Automattic on the WordPress plugin directory with more than seven million active installations, and Woo's own pricing page commits to a nought per cent revenue share. Your catalogue, your orders and your customer records sit on a server you chose, in a country you chose, under a database you can dump tonight. Whatever is wrong with your shop, it is not that someone else is holding it.

The American part is the rim around the software. Follow the terms of service link on woocommerce.com and it lands on the WordPress.com agreement, where a European customer contracts with an Irish entity — WooCommerce Ireland Ltd for Woo services, Aut O'Mattic A8C Ireland Ltd for Automattic's own — while the agreement itself is governed by the law of California and disputes go to the state and federal courts of San Francisco County.

That is an Irish counterparty under Californian law, which is a stranger arrangement than either a plain US vendor or a plain EU one, and it covers your Woo account, your extension licences and WooPayments.

WooPayments is where it becomes concrete. It is offered during setup as the payment method built for WooCommerce, it runs in thirty-nine countries, and Woo's own documentation names Stripe as the partner whose rules decide which account types a country can have. So the default checkout on a self-hosted European shop is a US processor introduced by a US publisher, on a store that otherwise never leaves your infrastructure.

• The shop is yours and the checkout is not This is the split that makes WooCommerce different from every hosted platform. Nobody can read your product catalogue, nobody throttles your API, nobody raises a plan price on your orders table. But the money runs through whichever gateway you installed, and if that gateway is WooPayments then a US-regulated processor sits between your customer and your bank on an otherwise entirely European stack. Changing it touches one plugin and nothing else.
• WooPayments is Stripe with a Woo badge The documentation is explicit that account availability follows the rules of the partner, Stripe, in each country. The euro card price of 1.50% + €0.25 is the same standard EEA consumer-card price Stripe publishes under its own name, which tells you there is no Woo margin on that line and also that there is no Woo underwriting behind it. If your reason for looking at alternatives was Stripe, installing the plugin Woo recommends does not move you.
• The surcharges live below the headline WooPayments adds 2% when the card was issued outside Europe and 2% again when a currency has to be converted, and a dispute costs €15 in Europe and £15 in the United Kingdom. None of that is hidden — it is in the fees document — and none of it is in the number anybody quotes. A shop selling across borders should price the blended rate rather than the base one.
• Nothing stops you leaving, which removes every excuse Because Woo takes no cut of a sale and charges no penalty for using another gateway, the arithmetic here has only two terms: what your current provider charges and what a different one charges. On a hosted platform that comparison is polluted by a platform fee designed to keep you put. Here it is clean, which is why a WooCommerce merchant paying more than they need to is simply a merchant who never sat down with the fee table.

What you have to replace, not just match

Be precise about what you are swapping, because on WooCommerce three separate things get called "the platform" and only one of them is in question on this page.

The first is the software: WordPress, the WooCommerce plugin, your theme and your hosting. Nothing below replaces any of that, and nothing needs to, because it is already open source on infrastructure you control. The second is the Woo account and the extension licences — a commercial relationship with Automattic governed under Californian law, renewed annually, and separate from the code. The third is the payment layer, which is one plugin, one set of API keys and a test order.

Only the third is a decision you can make this week. The three providers ranked below all plug into the checkout you already have; what separates them is who writes the integration, what a European payment method costs, and whether you are buying a lower rate or a bigger basket.

The alternatives compared

How each alternative compares to WooCommerce

What actually breaks when you switch

Do not delete the old gateway. Switch it to test mode and leave it installed, because refunds, partial refunds and chargebacks on historical orders still have to route back through the processor that took the money. Shops that uninstall on switchover day discover this the first time a customer returns something bought last month.

Recurring orders are the part that needs a plan. Card credentials are stored by the processor that captured them and do not travel to a new one, so a subscription book has to be re-authorised customer by customer. Ask specifically which rails the new plugin supports for WooCommerce Subscriptions, run a handful of live mandates before announcing anything, and move the book in batches.

Then test the methods rather than the plugin. Every payment method you intend to offer needs a real transaction, a real refund and a real look at what lands in the payout report, because a gateway that works perfectly for cards can be misconfigured for a single local method and nobody notices until a country stops converting.

Does the usual jurisdiction argument apply to WooCommerce at all?

Not to the store, and that deserves saying plainly rather than fudging. WooCommerce is a GPL plugin you install on hosting you picked. If that hosting is in Frankfurt or Amsterdam then your orders, your customer records and your product data are processed there, by you, as controller. No American company holds a copy because there is no copy to hold.

It applies to two things around the edge. Your commercial relationship with Automattic — the account, the marketplace purchases, the licence renewals — sits under the WordPress.com terms with California as the governing law. And any service you install into the store carries its own jurisdiction with it, which is exactly what WooPayments does.

The useful conclusion is that a WooCommerce merchant has a smaller problem than most people on this site, and a much cheaper fix. You are not replatforming. You are changing a gateway.

Is WooPayments worse than installing a provider directly?

Worse is the wrong axis. It is convenient, it is priced at Stripe's standard European card rate rather than above it, and everything appears inside wp-admin next to the order, which is genuinely pleasant. If your objection to it is that it is expensive, the fee table does not support you.

The objection that does hold is what it is. The processing, the underwriting and the account rules are Stripe's, and Woo's documentation says so. A merchant who went looking for a European payment relationship and accepted the setup wizard's suggestion has ended up with an American one by default, which is a worse outcome than choosing it deliberately.

The second objection is method coverage. A card rate is the right unit for a card, and half of European e-commerce is not cards. That is a conversion question rather than a fee question, and it is the one that actually moves revenue.

Who maintains the plugin, and why should that decide anything?

On a self-hosted shop it decides more than the rate does. A payment plugin has to survive a WordPress major release, a WooCommerce major release and a PHP upgrade, several times a year, without dropping an order. Who ships those updates is a real operational question and it is knowable before you commit: the WordPress plugin directory shows the author, the install count, the last update and the support forum.

The three providers here sit in three different places. Mollie publishes its own plugin, over a hundred thousand active installations, last updated in September 2026. Klarna publishes its own too, past twenty thousand installations, and its rating sits at 2.3 out of 5 with compatibility complaints in the reviews. Adyen does not publish one at all; its documentation lists WooCommerce under partner-built integrations, maintained by Woosa.

None of that makes Adyen a bad processor. It means that on WooCommerce specifically, you are adopting somebody else's connector, and you should know whose before the first upgrade weekend.

What about the extension bills rather than the transaction fees?

For plenty of shops the marketplace is the larger annual number and nobody audits it. Extensions are sold as yearly licences per site, and a store accumulates them — shipping rules, subscriptions, bookings, tax, a currency switcher — until the renewal total quietly exceeds what the payment processing costs.

That spend is also the part contracted under Californian law rather than Irish or Dutch law, so it is the piece of a WooCommerce setup where the vendor relationship most resembles a normal US SaaS purchase.

It is not what this page replaces, and no payment provider will help with it. But if you are opening the books to compare gateway rates, open the renewals list in the same sitting. The saving there is often larger and requires no migration at all.

Which one to pick

Start by dropping the reason you were probably given. WooCommerce is GPL software on your own server, Automattic takes no share of your sales, and there is no platform fee pushing you towards any particular gateway. The store is not the thing to fix.

What is worth fixing is a default. If your checkout is WooPayments, the processing is Stripe's and the agreement is governed by Californian law, and you very likely arrived there by accepting a suggestion in the setup wizard rather than by choosing it. Mollie is the straightforward replacement: a Dutch counterparty, a plugin its own engineers maintain, and a price per method rather than a price per basket.

At the top of the market Adyen is the better processor and the harder install, because on WooCommerce it comes through a partner-built connector rather than one Adyen supports. That is a fair trade for a merchant with an agency and volume, and a poor one for a shop of three people.

And if your problem is the size of the order rather than the cost of taking it, Klarna is the only tool here aimed at that — with the useful twist that WooPayments already publishes a resold price, so you know what you are negotiating against before you pick up the phone.