Business owner pointing at recovered orders after adding advanced Wix Velo for eCommerce features

Wix Velo for E-commerce: Advanced Features Most Developers Miss

Wix Velo for eCommerce can do far more than the standard Wix Stores dashboard exposes — custom shipping rate logic, abandoned checkout recovery automation, and cart validation rules, to name a few. Most developers configure the built-in app settings and stop there, missing an entire layer of eCommerce APIs sitting underneath.

I’ve inherited more than one Wix store where the previous developer clearly never opened Velo at all. They configured Wix Stores through the dashboard, called it “custom-built,” and moved on. Nothing wrong with that for a simple shop. But it means leaving real revenue-recovery and automation tools completely untouched.

Here’s what those tools actually are, and why they matter more than most agencies let on.

Why Do Most Wix Stores Never Touch These Features?

Wix Stores works well out of the box, which is exactly why most developers never go further. According to Wix’s own eCommerce API documentation, the underlying Wix eCommerce APIs serve as a foundational layer for Wix’s own business solutions, including Stores and Bookings — meaning there’s a genuine developer-level toolkit powering the surface you see in the dashboard.

That toolkit stays invisible unless someone actively builds with it. Most “Wix experts” work entirely within the visual editor and app settings, never touching Velo’s eCommerce backend at all. That’s fine for a basic store. It leaves money on the table for anything more ambitious.

The Feature Nobody Talks About: Abandoned Checkout Recovery

This is the one I bring up first with e-commerce clients, because the numbers behind it are genuinely striking. According to Baymard Institute’s ongoing research, aggregated across dozens of studies, the average online cart abandonment rate sits at just over 70%.

That means roughly seven out of every ten shoppers who add something to their cart never complete the purchase. Wix’s eCommerce APIs specifically include an event handler for abandoned checkout recovery, letting you trigger custom logic — a targeted email, a discount offer, a follow-up automation — the moment a recovered checkout is detected. Most stores never set this up, relying entirely on Wix’s default recovery emails instead of anything tailored to their specific customer behavior.

Custom Shipping Rates: Solving What Wix’s Defaults Can’t

Wix’s built-in shipping options cover flat rates and simple carrier integrations well. They don’t cover every business, though. If you ship internationally with unusual carrier pricing, offer freight-based rates by weight tier, or need to pull live rates from a courier Wix doesn’t natively support, the standard settings hit a wall fast.

This is exactly what Wix’s shipping rate service plugin exists for. It lets a developer write custom logic that calculates shipping in real time, pulling from an external rate source if needed, then feeding that number directly into the checkout. I’d rather build this once, properly, than have a client manually adjusting shipping costs by hand for every unusual order.

Custom Discount Triggers and Cart Validation

Standard discount codes work for the obvious cases — 10% off, a set holiday sale. They don’t handle more specific business logic, like “automatically apply a discount when a customer’s cart crosses a certain value” or “block checkout if an order doesn’t meet a minimum quantity for wholesale pricing.”

Wix’s eCommerce service plugins support custom discount triggers and custom cart or checkout validations for exactly this kind of logic. I’ve used these to build tiered pricing structures and automatic bulk discounts that the default discount rules simply can’t express on their own.

Order Fulfillment Automation: Where Manual Work Quietly Disappears

Here’s a genuinely underused piece: the Wix eCommerce Orders and Fulfillment APIs let you programmatically manage order preparation and delivery status, rather than manually updating each order through the dashboard. For a store processing dozens of orders daily, connecting this to an external inventory or fulfillment system removes a repetitive manual task entirely.

This is the kind of feature that doesn’t show up in a sales pitch, because it’s invisible to customers. It’s entirely about saving the business owner hours of manual admin work every week — which, over a year, adds up to real money even though it never appears as a “feature” on the storefront.

Product Recommendations: Beyond the Default “You Might Also Like”

Wix Stores includes basic upsell and cross-sell display options. The eCommerce Recommendations API goes further, letting a developer build logic tied to actual purchase behavior — recommending items based on what similar customers bought, not just a static “related products” list configured once and forgotten.

For stores with a wide catalog, this kind of behavior-based recommendation genuinely increases average order value. It’s also one of the features I see skipped most often, simply because it requires custom development rather than a dashboard toggle.

What I Actually Do Differently Here

Most developers treat Wix Stores as a finished product you configure, not a platform you build on top of. My approach is different: I treat the standard dashboard settings as the starting point, then look specifically at where a client’s business has unusual needs — pricing logic, shipping complexity, fulfillment volume — and build custom Velo logic to close exactly those gaps.

That’s a deliberate stance, and it means more upfront development time than a pure dashboard configuration. It’s worth it precisely because these gaps are where real revenue quietly leaks out, month after month, without ever showing up as an obvious problem.

[INSERT: a real client example here — e.g., a specific store where adding one of these features (abandoned checkout recovery, custom shipping, discount triggers) changed order completion or average order value]

A Mistake I See Developers Make in the Other Direction

Not every store needs all of this, and that’s worth saying plainly. I’ve also seen developers over-engineer a simple store with custom Velo logic that a native Wix feature already handles perfectly well. Before building anything custom, check whether the standard dashboard genuinely can’t do what you need — I’ve written more about that broader decision in how Velo API integrations actually work, which covers exactly when custom code is worth the investment.

Is This Worth It for a Small Store, or Only Larger Ones?

It depends on your order volume and complexity, not your size on paper. A small store with unusual shipping needs benefits from custom shipping logic immediately. A larger store with simple, uniform products might not need any of this at all. The right question isn’t “how big is my store,” it’s “where specifically am I losing time or revenue to a gap the dashboard can’t fill.”

If you’re weighing whether Velo-level eCommerce customization is worth it compared to switching platforms entirely, I’ve broken down that broader comparison in Wix Velo vs. WordPress. For a realistic cost estimate on your specific project, my website cost calculator gives you a grounded starting number.

Frequently Asked Questions

Can Wix Velo recover abandoned carts automatically?
Yes. Wix’s eCommerce APIs include an event handler for abandoned checkout recovery, letting developers build custom follow-up logic, such as targeted emails or discount offers, beyond Wix’s default recovery messaging.

Does Wix support custom shipping rates through Velo?
Yes. Wix’s shipping rate service plugin allows developers to calculate shipping costs using custom logic, including pulling live rates from external carriers not natively supported by Wix’s standard shipping settings.

What is the average cart abandonment rate for online stores?
According to Baymard Institute’s ongoing research aggregating dozens of studies, the average cart abandonment rate sits at just over 70%, meaning most shoppers who add items to a cart don’t complete the purchase.

Can Wix Velo automate order fulfillment?
Yes. The Wix eCommerce Orders and Fulfillment APIs let developers programmatically manage order status and connect to external inventory or fulfillment systems, reducing manual dashboard work.

Do I need custom discount logic if Wix already has discount codes?
Only if your pricing rules go beyond simple percentage-off codes. Custom discount triggers are useful for automatic tiered pricing, bulk discounts, or cart-value-based rules that standard discount codes can’t express.

Is it worth building custom Wix Velo eCommerce features for a small store?
It depends on your specific needs, not your store’s size. A small store with unusual shipping or pricing requirements benefits significantly, while a simple, uniform product catalog may not need custom features at all.

Curious What Your Store Is Missing?

If you want an honest look at whether your Wix store is leaving revenue on the table, message me on WhatsApp and I’ll walk through it with you. Start the conversation here.

Restaurant manager exporting order data during a GloriaFood to WooCommerce migration

How to Migrate from Gloria Food to WooCommerce Without Losing Orders

A GloriaFood to WooCommerce migration means moving your menu, customer list, and delivery settings to a platform you actually own, before Oracle shuts GloriaFood down on April 30, 2027. You won’t “import” old orders into WooCommerce as live transactions — you’ll archive them for records and rebuild your live menu and ordering flow from scratch on WooCommerce.

If you’re reading this because you got an email or saw a banner inside your GloriaFood dashboard, you’re not imagining it. Oracle acquired GloriaFood back in 2021, and it’s now retiring the entire platform. This isn’t a price increase or a forced upgrade — it’s a full shutdown, with no Oracle-built replacement and no official migration tool.

I’ve been getting questions about this from restaurant clients, so here’s the actual plan I’d recommend, not just a generic “how to switch platforms” checklist.

Why Is This Migration Suddenly Urgent?

GloriaFood built a loyal following of independent restaurants because it offered commission-free online ordering for free. That’s exactly why so many small businesses leaned on it for years without a backup plan.

According to an independently maintained shutdown timeline, GloriaFood has already stopped accepting new signups and is running in maintenance mode with no new features. April 30, 2027 is the confirmed final date, and after that, ordering pages, QR codes, and connected POS integrations all stop working at once — with no data recovery available afterward.

That deadline sounds distant, but here’s the catch: a clean migration takes real planning time, not a weekend. Menu mapping, testing, and running both systems in parallel for a couple of weeks all add up. Starting in early 2027 is starting too late.

What Actually Happens If You Wait Too Long?

If your account isn’t migrated before the cutoff, you lose access to your entire menu setup, your customer contact list, your delivery zone configuration, and your order history — all at once, with no advance warning beyond what’s already been communicated. There’s no “read-only” grace period once the platform goes dark.

The customer list is the part I’d worry about most. Menus and photos can be rebuilt slowly on a new platform. A list of customers built from years of repeat orders cannot be recreated once it’s gone.

The Migration Checklist I’d Actually Follow

Here’s the order I’d tackle this in, based on what actually breaks when people rush it.

1. Export Everything From GloriaFood First

Before touching WooCommerce, pull every piece of data GloriaFood lets you export: menu items, categories, modifiers, prices, photos, delivery zones, hours, and your customer contact list. Do this now, regardless of when you plan to actually launch on WooCommerce, because export access could tighten as the shutdown date approaches.

2. Set Up WooCommerce and Map Your Menu

This is usually the most time-consuming part, not the most technical. Every menu item, variation, add-on, and modifier group needs to be manually mapped into WooCommerce’s product structure, since there’s no direct one-click importer between the two platforms. WooCommerce’s own CSV import/export documentation covers the bulk-upload process once your menu data is formatted correctly.

3. Decide What Happens to Historical Orders

Here’s the nuance most migration guides skip entirely: you’re not actually “importing” your old GloriaFood orders into WooCommerce as live transactions. WooCommerce’s order system expects orders created through its own checkout flow, so forcing historical GloriaFood orders into that structure creates messy, unreconciled records that don’t match your payment processor or accounting software.

What I actually recommend instead: export your GloriaFood order history as a CSV or PDF archive for your own records and accounting, and start WooCommerce with a clean order table going forward. You’re not losing your order history — you’re separating “records you need to keep” from “orders your new system needs to process.” That distinction saves hours of unnecessary cleanup.

4. Reconnect Payments and Delivery Zones

Confirm your Stripe or payment gateway connects cleanly to WooCommerce, since GloriaFood’s payment integration doesn’t carry over automatically. Rebuild your delivery zones and radius settings directly in WooCommerce or your chosen delivery plugin, testing each zone before launch.

5. Run Both Systems in Parallel Before Cutover

Don’t switch overnight. Keep GloriaFood live while your WooCommerce ordering page runs in a soft-launch mode for at least one to two weeks. That overlap window catches configuration mistakes before real customers hit them.

6. Redirect Old Links and Update Every Mention

Set up 301 redirects from your old GloriaFood ordering URL to your new WooCommerce ordering page, since skipping this step causes both an SEO hit and confused customers hitting a dead link. Update your Google Business Profile, social media bios, and any printed menus or QR codes pointing to the old system.

What I’d Do Differently Than a Generic Migration Guide

Most guides treat this as a pure data-export exercise. I treat it as a chance to fix what GloriaFood never let you control in the first place — your site’s design, your menu presentation, and your page speed. If you’re already rebuilding your ordering flow, it’s worth pairing this migration with a proper look at your site’s theme and performance rather than just bolting WooCommerce onto whatever you had before. I’ve written separately about choosing the right WordPress theme for a restaurant, which matters even more once ordering, not just browsing, happens directly on your site.

If your restaurant has unusual modifier logic, loyalty rules, or a delivery-zone setup GloriaFood handled in a way WooCommerce doesn’t natively support, that’s often where custom plugin development actually earns its cost — rebuilding one specific missing piece, not the whole system.

[INSERT: a real client migration example here — e.g., a specific restaurant’s GloriaFood-to-WooCommerce switch, what broke, and how long it actually took]

Common Mistakes That Cause Real Problems

  • Waiting until early 2027 to start. The last few months before any platform shutdown always get chaotic, as support slows and other restaurants scramble simultaneously.
  • Skipping the parallel-running period. Switching overnight risks a gap where customers simply can’t place orders.
  • Forgetting 301 redirects. This causes an immediate, avoidable SEO and traffic loss on your ordering page.
  • Not exporting the customer list separately. Menu items can be rebuilt. A customer contact database built over years cannot.

Should You Migrate This Yourself or Hire Someone?

If your menu is small and simple, a motivated business owner can handle this migration solo with a weekend of focused work. If you’re running complex modifiers, multiple delivery zones, loyalty promotions, or integrations with a POS system, I’d bring in a developer who’s done a WooCommerce food-ordering setup before, since those are exactly the details that go wrong when rushed.

If you want a realistic estimate of what a proper migration and rebuild would cost for your specific setup, my website cost calculator gives you a starting number in a couple of minutes.

Frequently Asked Questions

Why is GloriaFood shutting down?
Oracle, which acquired GloriaFood in 2021, has confirmed the platform will be permanently retired on April 30, 2027. New signups have already closed, and no official replacement or migration tool has been announced.

Can I import my GloriaFood order history directly into WooCommerce?
Not cleanly. WooCommerce’s order system is built for its own checkout flow, so historical GloriaFood orders should be archived as a CSV or PDF for your records rather than force-imported as live WooCommerce orders.

How long does a GloriaFood to WooCommerce migration take?
A careful migration typically takes several weeks, covering menu mapping, testing, and a parallel-running period before full cutover. Rushing it into a few days increases the risk of missed data or broken ordering flows.

What data will I lose if I don’t migrate before the shutdown?
You’ll lose access to your entire menu setup, customer contact list, order history, and delivery zone configuration once GloriaFood goes offline, with no data recovery available afterward.

Does WooCommerce charge commission on orders like GloriaFood does?
No. WooCommerce itself doesn’t charge order commissions, though you’ll still pay standard payment processing fees through whichever gateway (like Stripe) you connect.

Do I need a developer to migrate from GloriaFood to WooCommerce?
Simple menus can be migrated by a business owner directly. Complex setups with custom modifiers, multiple delivery zones, or POS integrations usually benefit from a developer experienced with WooCommerce food-ordering builds.

Want This Migration Handled Properly?

If you’d rather not risk losing your menu or customer data before the 2027 deadline, message me on WhatsApp and I’ll walk through your specific setup. Start the conversation here.

Business owner setting up multi-currency support WooCommerce dashboard on a laptop

How to Add Multi-Currency Support to WooCommerce

Quick answer: Adding multi-currency support to WooCommerce means letting shoppers see and sometimes pay in their own currency instead of just yours. The easiest route in 2026 is WooPayments’ built-in switcher, which supports 135 currencies for free. For more control over rounding, rates, or checkout currency, a dedicated plugin like Aelia or FOX Currency Switcher does more.

I get this request constantly from clients selling to the US, UK, and EU at once. A Danish restaurant client only needed one currency. A store selling digital products worldwide needed six. The setup looks similar either way, but the decision behind it isn’t.

Why Bother With Multi-Currency at All?

Showing a price in dollars to a shopper in Germany creates friction, even if the conversion math is simple. They have to stop, calculate, and trust that your number is accurate. That tiny pause is often enough to lose the sale.

Research from currency-conversion providers consistently links local pricing display to higher trust and better conversion, because shoppers no longer need to guess. It’s not a huge technical lift either — WooCommerce made this easier in 2024 when it expanded WooPayments across Spain, Italy, France, and Germany and added native multi-currency support covering 135 currencies, according to TechRadar’s coverage of the rollout.

That’s the real starting point for most stores now: check what’s already built in before installing anything new.

Option One: WooPayments’ Native Currency Switcher

If you already use WooPayments as your payment gateway, you likely have multi-currency support sitting unused in your dashboard. It lets shoppers browse and check out in whichever currency they select, while you continue receiving settlement in your base currency.

Here’s what it includes:

  • Prices convert automatically using rates pulled from a live exchange rate API
  • A currency switcher widget you can place in your header, footer, or sidebar
  • Rounding controls, so converted prices don’t end up looking like $19.73 instead of $19.99
  • A fallback currency, so shoppers whose currency isn’t enabled still see something sensible, usually your default

Setup takes maybe fifteen minutes. Go to WooCommerce → Settings → Payments → WooPayments, enable multi-currency, then choose which currencies to activate. That’s genuinely most of it. For a straightforward store without complex pricing rules, this is usually all you need.

Option Two: A Dedicated Multi-Currency Plugin

WooPayments’ switcher has one real limitation — it works best when WooPayments is also your payment processor. If you’re using Stripe, PayPal, or a regional gateway instead, a standalone plugin often integrates more cleanly.

Plugins like Aelia Currency Switcher or FOX – Currency Switcher Professional add more granular control: per-product manual pricing overrides, multiple exchange rate sources, and geolocation-based currency switching that activates before a visitor even clicks anything. That extra control costs more setup time and, usually, a yearly license fee.

Choose this route if any of the following apply to your store:

  1. You use a payment gateway other than WooPayments
  2. You need to set exact manual prices per currency instead of pure conversion
  3. You sell high-value items where rounding errors on live rates actually matter
  4. You want automatic currency detection based on visitor location

The Setup Mistake That Costs Sales

Here’s something most guides skip. Adding currencies to the switcher isn’t the same as making sure your customer can actually pay in that currency. If your payment gateway only settles in USD, a customer who selects EUR still sees EUR prices, but their bank statement may show a converted USD charge with a foreign transaction fee attached. That mismatch generates support tickets and, sometimes, chargebacks.

Before you launch multi-currency, confirm your payment gateway processes native settlement in the currencies you’re offering, not just currency display. WooPayments and Stripe both support multi-currency settlement in many regions, but always check per-country before assuming.

If your store is already live and conversions still feel low after adding multi-currency, the currency switcher probably isn’t the actual problem. I’ve broken down the more common causes in why a WooCommerce store isn’t converting.

Does Multi-Currency Affect SEO or Page Speed?

Not meaningfully, if it’s set up correctly. Currency conversion happens client-side or via a lightweight geolocation check, so it shouldn’t slow down page load in any way a visitor notices. The bigger risk is duplicate content from currency-specific URLs, which some plugins generate. Stick to a single URL with a JavaScript-based switcher unless you specifically need separate country pages for other reasons.

How Exchange Rates Stay Accurate

Most multi-currency tools pull rates from a live API and refresh them on a schedule — commonly every twelve hours on free plans, faster on paid tiers. That’s frequent enough for nearly every small business, since exchange rates rarely swing enough in half a day to matter at typical order values. If you sell high-ticket items where a currency shift changes your margin meaningfully, look for a plugin with more frequent rate refreshes or manual override pricing.

Frequently Asked Questions

Is WooCommerce multi-currency free? Yes, if you use WooPayments as your gateway, the native currency switcher is included at no extra cost and supports 135 currencies.

Do I need a plugin if I already use WooPayments? Not necessarily. WooPayments includes its own currency switcher, so a separate plugin only makes sense if you need features it doesn’t offer, like manual per-currency pricing.

Will multi-currency slow down my WooCommerce store? No, in most setups conversion happens quickly through an API call or stored rate, and it shouldn’t add noticeable load time to your pages.

Can customers pay in a currency different from my store’s base currency? Yes, as long as your payment gateway supports settlement in that currency. Check your gateway’s supported currencies before enabling the option in WooCommerce.

How often do exchange rates update in WooCommerce multi-currency plugins? It depends on the plugin, but many refresh every 12 hours on free tiers and more frequently on paid plans.

Does adding multiple currencies hurt my store’s SEO? It can, only if the plugin generates separate URLs per currency without proper canonical tags. A JavaScript-based switcher on a single URL avoids that risk entirely.

Getting multi-currency working cleanly, without breaking your checkout or your SEO, usually takes an experienced hand the first time through. If you’d rather have someone set it up correctly than troubleshoot it later, reach out on WhatsApp and I’ll take a look at your store.

Small business owner and developer comparing payment gateways for small business checkout options on a laptop

Best Payment Gateways for Small Business in Europe

Quick answer: The best payment gateways for small business in Europe are Mollie, Stripe, and Adyen, each with no monthly fee and per-transaction pricing between roughly 1.1% and 1.9%. The real decision isn’t the processor’s brand name. It’s whether the gateway supports local methods like iDEAL, Bancontact, and SEPA Direct Debit, since those often convert better than cards alone.

I’ve built checkout flows for clients across Denmark, the Netherlands, and the wider EU, and the question I hear most is “just tell me which one to use.” Fair enough. But the honest answer depends on where your customers actually bank, not on which gateway has the flashiest homepage.

Why “Which Gateway Is Cheapest” Is the Wrong First Question

Every small business owner starts by comparing percentages. That instinct makes sense — nobody wants to lose margin on every sale. However, a 0.3% fee difference rarely moves the needle as much as a missing payment method does.

Here’s why. If a Dutch customer reaches your checkout and doesn’t see iDEAL, many will simply leave. Recent industry research from payments platform payabl. found that regional preference varies sharply: debit cards dominate in the UK, PayPal leads in Germany at 71%, and iDEAL takes the top spot in the Netherlands. A gateway that only processes cards well is quietly turning away buyers in exactly the markets you’re trying to reach.

That’s the real starting question: does this payment gateway support the methods your specific customers already trust?

The Three Gateways Worth Comparing in 2026

For most European small businesses, the shortlist comes down to Mollie, Stripe, and Adyen. All three plug into WordPress, WooCommerce, and custom-built sites without needing a merchant account elsewhere.

Mollie was built for European small businesses first. There’s no monthly fee and no contract — you pay per transaction, with rates like roughly €0.32 for iDEAL and €0.35 for SEPA payments. It’s simple to set up, and its dashboard is genuinely easy for a non-technical owner to read.

Stripe charges 1.5% + €0.25 for standard EU cards and 1.9% + €0.25 for premium EU cards, with international cards costing more. It has the deepest developer toolkit of the three, which matters if you eventually want custom checkout logic, subscriptions, or marketplace features.

Adyen charges a flat €0.11 processing fee per transaction plus a separate cost per payment method, with no setup or monthly fees. It’s popular with mid-sized and scaling businesses because pricing stays predictable as volume grows, though the interface leans more technical than Mollie’s.

None of these three is objectively “best.” A bakery in Rotterdam taking mostly iDEAL payments has different needs than a SaaS founder in Berlin billing subscriptions monthly.

What Local Payment Methods Actually Change

This is the part generic gateway comparisons skip. In the Netherlands, iDEAL still holds more than 60% of online payment share, according to Stripe’s own payment method data. In Belgium, over 80% of online businesses offer Bancontact because customers expect it by default.

If you’re building or rebuilding a WooCommerce store for a European audience, don’t just install the gateway with the lowest fee. Check which local rails it supports out of the box. I’ve seen stores lose meaningful checkout completion simply because the payment plugin only offered Visa and Mastercard to a Dutch audience that wanted their bank app instead.

If your store already gets decent traffic but conversions feel low, that’s often a checkout problem before it’s a traffic problem — I’ve written more about diagnosing that in why a WooCommerce store stops converting.

How the New Instant Payments Rules Affect You

Something changed in the background of European payments recently, and most small business owners haven’t noticed yet. Under EU Regulation 2024/886, banks and payment institutions across the Eurozone are now required to send and receive SEPA instant payments within ten seconds, at any hour, any day of the year. According to KPMG’s coverage of the regulation, receiving deadlines took effect in January 2025 and sending deadlines followed in October 2025.

For your business, this means bank transfer payments — long considered the slow option — are becoming nearly as fast as card payments in practice. That’s good news if you invoice clients or take SEPA Direct Debit payments, because cash reaches your account faster than it used to. Gateways like Mollie and Stripe are already routing eligible transfers through instant rails, so you may not need to do anything except make sure your provider supports it.

A Mistake I See Often

Business owners frequently pick a gateway based on what a competitor uses, without checking if their own audience matches. A UK-only service business copying a Dutch e-commerce store’s payment stack ends up offering iDEAL to customers who’ve never heard of it, while missing the debit card options their actual buyers expect. Match the gateway to your audience’s country, not to someone else’s setup.

Which Gateway Fits Which Business?

  • Selling mostly to Dutch or Belgian customers? Mollie’s local method coverage and simple per-transaction pricing usually win.
  • Running subscriptions, marketplaces, or need custom logic? Stripe’s developer tools make that far easier to build.
  • Scaling fast across multiple EU countries with growing volume? Adyen’s flat processing fee structure tends to stay predictable as you grow.
  • Not sure what your site even needs yet? Start with our website cost calculator to scope the build before locking in a payment stack.

Whichever gateway you choose, test the actual checkout flow yourself on a phone. A gateway that looks great in documentation can still feel clunky at the point where someone’s about to pay you.

Frequently Asked Questions

Which payment gateway is cheapest for a small business in Europe? Mollie and Adyen tend to have lower baseline transaction costs than Stripe for standard EU cards, though exact savings depend on your payment method mix and country.

Do I need to support iDEAL if I don’t sell in the Netherlands? No. Only add local methods relevant to where your actual customers are based — adding irrelevant options clutters checkout without adding sales.

Can I use more than one payment gateway on the same website? Yes, and some WooCommerce and Wix setups do run two gateways side by side, though it adds complexity to reconciliation and reporting.

Will the EU Instant Payments Regulation affect card payments too? No, it applies to SEPA credit transfers and bank-based payments, not card transactions, which already settle on their own network timelines.

Is PayPal worth adding alongside a main gateway? Often yes. Research shows PayPal remains the most recognized payment brand across much of Europe, and offering it as a secondary option can reduce cart abandonment.

How long does it take to switch payment gateways on an existing site? For a straightforward WooCommerce or Wix Velo setup, a gateway migration usually takes a few days, though anything with saved subscriptions needs more careful planning.

Picking the right payment gateway is a decision you’ll live with for years, and getting the checkout wrong quietly costs more than the fee percentage ever does. If you want a second opinion on which gateway fits your specific market and platform, message me on WhatsApp and I’ll walk through it with you.

Small business owner comparing WooCommerce vs Shopify UK pricing on a laptop screen

WooCommerce vs Shopify UK: 2026 Small Business Guide

Quick answer: For UK small businesses, WooCommerce vs Shopify usually comes down to time versus money. WooCommerce costs less over three years but needs someone to manage hosting and updates. Shopify costs more monthly but handles hosting, security, and support for you. Choose Shopify if you want speed; choose WooCommerce if you want control.

I get asked this question almost every week. A client walks in with a spreadsheet of Shopify app costs, or a WooCommerce site that broke after a plugin update, and wants to know which platform they should have picked. There’s no universal winner. But there is a right answer for your specific business, and I want to walk you through how to find it.

What’s the real difference between WooCommerce and Shopify?

WooCommerce is a free plugin that turns a WordPress site into an online shop. You own the hosting, you control the code, and you’re responsible for keeping everything updated. Shopify is a complete hosted service. You pay a monthly fee, and Shopify handles servers, security patches, and uptime.

Think of it like renting versus owning. Shopify is a serviced office — you pay more each month, but someone else fixes the plumbing. WooCommerce is owning the building — cheaper long-term, but you’re the one calling the electrician.

How much does each platform actually cost in 2026?

This is where most comparisons get vague. Let’s use real numbers.

Shopify’s Basic plan runs about £25 per month on annual billing, with online transaction fees around 2.9% plus 30p per sale unless you use Shopify Payments exclusively. Higher tiers reduce that percentage but raise the monthly fee.

WooCommerce itself is free. But you’ll pay for managed WordPress hosting, typically £10–£50 per month depending on traffic, plus occasional premium plugins for things like advanced shipping or subscriptions.

For a UK store doing roughly £60,000 a year in revenue, industry cost breakdowns commonly put WooCommerce’s all-in yearly cost between £150 and £400, against Shopify’s £900 to £1,800 once apps and transaction fees are included. That gap narrows fast, though, once your time is worth something. If maintaining WooCommerce eats ten hours a year and your time is worth £50 an hour, you’ve quietly spent £500 of the savings already.

There’s also a UK-specific wrinkle worth knowing. Shopify doesn’t add VAT to its payment processing fees for UK merchants, though Shopify Tax may apply once sales cross a threshold that’s usually £100,000 in the UK. That threshold matters if you’re scaling fast — it’s easy to miss until the invoice arrives.

Which platform is easier to manage day-to-day?

Shopify wins here, no contest. You log in, add a product, pick a theme, and you’re selling within an afternoon. There’s no server to configure and no plugin conflicts to debug at 11pm.

WooCommerce demands more from you. You’re choosing a host, installing SSL, picking a theme, and managing plugin updates that occasionally break each other. It’s not hard, exactly. It’s just ongoing. That’s the trade nobody mentions in the glossy comparison charts.

However, “easier” isn’t always “better.” If you already run a WordPress site with blog content driving traffic, bolting WooCommerce onto it keeps everything in one place. Splitting your blog and shop across two platforms creates its own headaches.

Does WooCommerce or Shopify rank better in Google?

WooCommerce generally has the edge for organic search, and here’s why. It inherits WordPress’s flexibility — you control URL structure, page speed optimisation, schema markup, and content architecture down to the smallest detail. That matters if blog content and SEO are part of your growth plan, which they should be for most UK small businesses without big ad budgets.

Shopify’s SEO has genuinely improved since its early years. Site speed is solid out of the box, and basic on-page SEO controls are built in. But you’re still working within Shopify’s structure. Some technical customisations that WooCommerce handles natively require a developer workaround or a paid app on Shopify.

If organic search is central to your customer acquisition strategy, that’s a real point in WooCommerce’s favour. If you’re driving traffic mainly through paid ads or social, the SEO gap matters far less.

Who actually wins for a UK small business?

Here’s my honest take, because I don’t think neutral-to-the-point-of-uselessness comparisons help anyone. If you’re a solo founder or small team selling under 100 products, don’t have technical staff, and want to launch fast, take Shopify. The monthly fee buys you peace of mind that’s worth more than the pounds saved on WooCommerce hosting.

If you already have a WordPress site, sell a growing catalogue, need custom checkout logic, or care deeply about organic traffic, WooCommerce earns its extra setup effort. It scales cheaper as revenue grows, and you’re never locked into a platform’s app marketplace for basic functionality.

One mistake I see constantly: businesses pick WooCommerce because it’s “free,” then discover six months later that nobody on their team can safely update a plugin without breaking the checkout. Free software isn’t free if it needs a developer on standby. Budget for that reality upfront, on either platform.

What about switching later?

Migrating between the two is possible in both directions, but it’s never as simple as an export-import wizard suggests. Product data, order history, SEO rankings, and customer accounts all need careful handling. If you’re unsure which platform fits, it’s worth getting the decision right the first time rather than paying twice for a migration. Our website cost breakdown guide covers what a proper WooCommerce or Shopify build actually costs once development, design, and setup are included.

FAQ

Is WooCommerce cheaper than Shopify for a UK small business?
Usually yes, over one to three years, once you account for hosting and plugins instead of Shopify’s monthly fee and transaction charges. The gap shrinks once you add the cost of your own time spent on maintenance.

Does Shopify charge VAT on transaction fees in the UK?
No. Shopify doesn’t add UK VAT on top of its payment processing fees, though Shopify Tax can apply once your sales pass roughly £100,000 in a calendar year.

Which platform is better for SEO, WooCommerce or Shopify?
WooCommerce generally offers more SEO flexibility because it’s built on WordPress, giving you deeper control over site structure and content. Shopify’s SEO has improved significantly but still works within a more fixed framework.

Can I switch from Shopify to WooCommerce later without losing data?
Yes, migration is possible, but product data, SEO rankings, and customer records all need careful handling by someone experienced with both platforms. A rushed migration risks lost rankings and broken order history.

WooCommerce vs Shopify UK isn’t a battle with one correct winner — it’s a match between your business model and each platform’s strengths. Shopify buys convenience. WooCommerce buys control and long-term savings, at the cost of your own time or a developer’s. Know which one you’re actually trading before you commit.

If you want a second opinion on which platform fits your specific business, or you need a developer to build and configure either one properly, message me on WhatsApp and I’ll give you a straight answer, not a sales pitch.

Do I need a developer to run a WooCommerce store?
Not strictly, but most small business owners benefit from at least an initial professional setup, since plugin conflicts and hosting configuration can get technical fast. Ongoing day-to-day management is manageable without one.

Is Shopify better for beginners with no technical background?
Yes. Shopify’s biggest advantage is that hosting, security, and updates are all handled for you, so you can launch and manage a store without touching code or server settings.

Small business owner selecting the best payment gateway option on a checkout tablet

Best Payment Gateway for Small Business (2026)

Quick answer: The best payment gateway for most small businesses in 2026 comes down to three realistic options: Stripe (2.9% + 30¢ online), Square (2.6% + 15¢ in-person, 3.3% + 30¢ online), and PayPal (3.49% + 49¢ standard). Stripe fits online-first businesses best, Square wins for in-person and hybrid models, and PayPal adds conversion trust at a higher cost.

I get asked this constantly during builds, usually right after a client has spent an hour comparing homepage marketing copy instead of actual numbers. Here’s the version with real math.

Stripe vs PayPal vs Square: The Actual 2026 Numbers

Let’s start with what each processor actually charges, because the headline percentage rarely tells the full story.

Stripe charges 2.9% plus 30 cents per successful online card charge in the US, according to Stripe’s own pricing page. There’s no setup fee and no monthly fee on the standard plan, which makes it easy to start with and predictable to scale.

Square charges 2.6% plus 15 cents for in-person transactions and 3.3% plus 30 cents for online payments. Square’s real strength is bundling — point-of-sale hardware, inventory, and booking tools all live under one account, which matters if you sell both in person and online.

PayPal charges 3.49% plus 49 cents on its standard plan, noticeably higher than Stripe or Square. PayPal’s Advanced and Pro plans drop closer to 2.59% plus 49 cents, but those require a monthly fee, so the savings only make sense once your volume justifies it.

Why the Headline Rate Isn’t the Real Cost

Here’s the part that trips people up: the fixed fee matters more than the percentage once your average sale gets small. A $15 sale through Stripe costs you 2.9% plus 30 cents, an effective rate closer to 4.9%, not 2.9%.

That’s why a coffee shop or a service business with lots of small transactions feels the fixed fee far more than a business selling $500 packages. If your average ticket is under $30, run the real math for each processor rather than trusting the advertised percentage alone.

International sales add another layer. Stripe adds 1.5% for international cards and 1% more for currency conversion, which can push a routine international sale’s fees close to 5.4% total. If you’re selling to customers outside the US regularly, that stacking cost deserves real attention before you commit to one processor.

Which Gateway Fits Which Business Model?

If your business is primarily online — services, digital products, e-commerce — Stripe usually wins. Its developer-friendly integration works cleanly with WordPress, Wix, and custom builds, and its checkout experience converts well without feeling generic.

If you’re mostly in-person, or hybrid with a physical location plus online orders, Square typically makes more sense. The bundled point-of-sale hardware and inventory tools save you from stitching together separate systems.

PayPal earns its higher cost through brand recognition. Some customers simply trust the PayPal button more, especially for higher-ticket or first-time purchases, and that trust can offset the extra fee through better conversion. It’s not the cheapest option, but it’s not irrational either — it depends on your audience.

Booking Deposits and Payment Gateways: A Different Problem

Booking-based businesses face a wrinkle none of the standard comparisons cover well: partial deposits and no-show fees. Not every gateway handles authorization holds, partial captures, or automatic cancellation charges equally well.

Stripe’s API generally offers the most flexibility here, letting a developer build custom deposit logic, automatic charge triggers on no-shows, and flexible refund rules. Square’s built-in booking tools handle this more simply out of the box, at the cost of some customization. If your business relies heavily on deposits or cancellation fees, that difference should weigh into your decision more than the base transaction rate.

The Mistake I See Most Often

Business owners frequently pick a gateway based on which one they’ve personally used as a customer, rather than which one fits their actual transaction pattern. That’s an understandable instinct, but it’s not the same evaluation.

A $40-average-ticket local service business and a $400-average-ticket consulting firm shouldn’t necessarily use the same processor, even if both owners personally prefer the same checkout button as shoppers. Run your actual numbers — average ticket size, transaction volume, and whether you sell internationally — before choosing.

What I Recommend for Most Small Business Sites

If I’m being direct: Stripe is my default recommendation for most online-first small business builds I work on, because the developer tooling is clean and the fees are predictable. That said, “default” doesn’t mean “always right” — a business with heavy in-person sales genuinely does better with Square’s bundled ecosystem.

The platform you’re building on matters too. If you’re weighing WordPress against Wix for your build, our WordPress vs Wix comparison covers how payment integration differs between the two, since that affects which gateways are easiest to implement cleanly.

Frequently Asked Questions

What’s the best payment gateway for a small online business?
Stripe is generally the best fit for online-first businesses due to its developer-friendly integration, predictable 2.9% + 30¢ pricing, and clean checkout experience.

Is PayPal more expensive than Stripe or Square?
Yes, on PayPal’s standard plan, which charges 3.49% + 49¢ compared to Stripe and Square’s roughly 2.9% + 30¢ rates. PayPal’s higher-tier plans reduce this but require monthly fees.

Which payment gateway is cheapest for small transactions?
Square tends to perform best for small in-person tickets due to its lower fixed fee (2.6% + 15¢), while Stripe’s fixed fee has a bigger relative impact on very small online sales.

Do payment gateways charge extra for international customers?
Yes. Most processors, including Stripe, add roughly 1.5% for international cards plus another 1% for currency conversion, which can meaningfully raise your effective rate.

Should a booking-based business choose a different gateway than a retail store?
Often, yes. Booking businesses benefit from gateways with strong deposit, authorization hold, and no-show fee handling, which varies significantly between Stripe, Square, and PayPal.

Can I use more than one payment gateway on my website?
Yes, and some businesses do, offering both Stripe and PayPal at checkout to capture customers who prefer one over the other. This adds development complexity but can improve conversion.

If you’re not sure which gateway fits your specific setup, that’s a quick conversation before you build anything. Message me on WhatsApp and I’ll help you figure out what actually makes sense for your business.

Business owner reviewing why their WooCommerce store is not converting on a laptop dashboard

WooCommerce Store Not Converting? Try These Fixes

Quick answer: A WooCommerce store not converting usually comes down to checkout friction, not traffic quality. Unexpected costs, too many form fields, and a slow mobile checkout push shoppers away before they finish. Fix those three areas first. They cause the majority of documented cart abandonment, well before your ads or product pages matter.

Why “Not Converting” Usually Means “Checkout Problem”

Business owners almost always blame the wrong thing first. They assume weak traffic, bad product photos, or pricing issues. However, the real problem often sits one step later, at checkout.

Baymard Institute, the leading research firm for ecommerce checkout usability, tracks this closely. Their aggregated data across 50 studies puts the average cart abandonment rate at 70.22%. That means roughly seven out of every ten shoppers who add something to their cart never actually buy it.

That statistic isn’t a reason to panic. Most stores sit somewhere near that average. It’s a reason to look specifically at checkout, rather than rebuilding your whole store from scratch.

What’s Actually Causing Shoppers to Leave?

Baymard’s research identifies specific, documented reasons for checkout abandonment, and most of them are fixable without a full redesign.

  • Unexpected extra costs. Shipping fees, taxes, or handling charges that appear late in checkout push shoppers to abandon fast.
  • Too many form fields. The average checkout asks for more information than it actually needs, and every extra field adds friction.
  • A forced account creation step. Requiring signup before purchase turns a quick sale into a chore.
  • A slow or confusing mobile checkout. Mobile traffic keeps growing, yet many WooCommerce checkouts still feel built for desktop first.
  • Limited payment options. Shoppers who don’t see their preferred payment method often leave rather than switch.

None of these require touching your product catalog. They require touching the three or four screens between “add to cart” and “order confirmed.”

How Do You Actually Fix a WooCommerce Store That’s Not Converting?

Start with the cheapest, fastest fixes before considering a bigger rebuild.

Show total cost early. Add a shipping estimator or flat-rate shipping visible on the product page, not buried at the final checkout step. Surprise costs remain one of the single biggest causes of abandonment.

Cut form fields aggressively. Most WooCommerce checkouts ship with more fields than necessary. Combine name fields, remove rarely used ones, and mark optional fields clearly.

Enable guest checkout. If your store still forces account creation, that single change often recovers sales within days of turning it on.

Add trust signals near the buy button. Security badges, clear return policies, and visible customer reviews reduce hesitation right where it matters most.

Test your mobile checkout yourself. Actually buy something on your phone. If you hesitate anywhere, your customers likely hesitate there too.

The Mistake Most WooCommerce Owners Make

Here’s where I’ll push back on generic advice: don’t start with a plugin. Business owners often install three or four “conversion booster” plugins before checking what’s actually broken.

That approach usually adds page weight and slows your checkout further, which makes the underlying problem worse, not better. Diagnose first. Watch a real session recording of someone abandoning their cart first. Or check your checkout funnel report in WooCommerce Analytics before adding anything new.

Speed matters here too, and it’s often overlooked. A checkout page cluttered with unnecessary scripts loads slower on mobile, and that delay alone can push hesitant shoppers away. If your broader site has performance or design issues beyond checkout specifically, that’s worth a look too. Our guide on why your website isn’t converting covers the wider set of common culprits.

Is a Full Checkout Redesign Ever Worth It?

Sometimes, yes, but not as often as agencies suggest. If your checkout runs the WooCommerce default flow with a few sensible tweaks, incremental fixes usually outperform a full rebuild.

A full custom checkout redesign makes more sense when your product setup is unusually complex. Think heavy customization options, subscriptions mixed with one-time purchases, or multi-step configurators the default flow can’t handle. In those cases, custom development pays for itself through recovered sales.

For most standard product stores, though, the fixes above solve the majority of the problem. Baymard’s own research backs this up directly. Checkout usability improvements alone can lift conversion by up to 35.26% on tested sites. No full platform change required.

Frequently Asked Questions

Why is my WooCommerce store getting traffic but no sales? Traffic and conversion are separate problems. Checkout friction, unexpected costs, and forced account creation commonly cause visitors to abandon carts, even with strong, relevant traffic.

What’s the average conversion rate for a WooCommerce store? Rates vary by industry, but most ecommerce sites convert between 1% and 3% of visitors. Most stores treat a cart abandonment rate near 70% as typical, not necessarily a sign something’s badly broken.

Does guest checkout actually improve conversions? Yes, in most cases. Forcing account creation before purchase adds friction at the exact moment a shopper is ready to buy. Many stores see a measurable lift after enabling guest checkout.

How many form fields should a checkout page have? Fewer than most default setups include. Combine redundant fields, mark optional ones clearly, and remove anything not strictly needed to complete the order.

Should I redesign my whole store or just fix checkout first? Fix checkout first. It’s cheaper, faster, and addresses the documented top causes of cart abandonment. A full redesign only makes sense for genuinely complex product setups.

Can slow page speed really hurt WooCommerce conversions? Yes. A slow-loading checkout, especially on mobile, adds friction at the worst possible moment. That delay alone can push already-hesitant shoppers to abandon their cart entirely.

If your WooCommerce checkout is quietly losing you sales, that’s usually a fixable, specific problem. Message me on WhatsApp with your store link, and I’ll tell you honestly what’s likely costing you the most conversions.