Every founder builds their first store on whichever platform their nephew recommends. By year two, they're either re-platforming or wishing they'd chosen differently. Here's the honest version of this comparison — based on dozens of e-commerce builds across the UK, UAE, and India, and the conversations we wish more founders had before they signed up.
The TL;DR
| Shopify | WooCommerce | Headless Next.js (Shopify or commerce-as-API) | |
|---|---|---|---|
| Best for | Launching fast, scaling to ~£5M/year | Tight budgets, content-heavy stores | High-growth brands and bespoke UX |
| Time to launch | 2–6 weeks | 4–8 weeks | 8–16 weeks |
| Annual platform cost | £400 – £24,000+ | £100 – £3,000 | £400 – £24,000+ (still Shopify behind the scenes) plus hosting |
| Frontend speed | OK out of the box | Variable | Excellent (1.2–1.8s LCP achievable) |
| Customisation ceiling | Moderate (Liquid + apps) | High (PHP everywhere) | Effectively unlimited |
| Maintenance overhead | Lowest | Highest | Medium |
That's the cheat sheet. Now the nuance.
Shopify — the right default for most stores
Shopify gets criticised by developers because it's opinionated. It's opinionated for a reason: those opinions are correct for 80% of stores. The defaults work. The checkout converts. The app ecosystem covers everything from subscriptions to fraud detection to multi-currency.
Where Shopify wins:
- Checkout conversion. Shopify's checkout converts ~2–3% higher than custom-built checkouts on equivalent stores. Their team has spent ten years optimising every input field and trust signal. You will not beat them in-house unless you spend a year trying.
- PCI compliance, fraud, taxes. All handled. You don't think about it. Worth thousands a year in either engineering time or vendor fees.
- App ecosystem. Klaviyo for email, Recharge for subscriptions, Postscript for SMS, Loop for returns — the integrations exist, are maintained, and have first-party support.
- Speed of launch. A reasonably-designed Shopify store goes from kickoff to launch in 3–6 weeks. WooCommerce takes twice as long. Headless takes three to four times as long.
Where Shopify gets expensive:
- Plus plan starts at $2,300/month — that's the threshold where you outgrow basic Shopify. Below ~£3M/year revenue, you're on Shopify or Shopify Advanced ($399/month or local equivalent).
- Transaction fees on the basic plan are 2% on top of payment processor fees. They drop to 0.5% on Plus.
- Apps stack up. A typical mid-market store runs 8–15 apps at £20–£200/month each. £500–£1,500/month in apps is not unusual.
Where Shopify is wrong:
- B2B / wholesale with complex pricing rules — Shopify B2B exists but is brittle for 5+ price tiers, custom quotes, or net-30 terms. WooCommerce + B2B plugins or a custom build handles this better.
- Heavy editorial content alongside commerce — the blog is a second-class citizen on Shopify. If 40%+ of your traffic comes from blog content, the SEO and content workflows are painful.
- Sites that need to render thousands of unique product configurations per SKU — Shopify's variant system caps at 100 variants per product.
WooCommerce — the cheap-to-start, expensive-to-maintain option
WooCommerce is a WordPress plugin. That sentence alone explains 80% of its strengths and weaknesses.
Where WooCommerce wins:
- Initial cost. £100/year of hosting plus a £200 theme and you have a working store. Compared to Shopify's £29–$399/month, that's appealing at the founder-bootstrap stage.
- Content + commerce integration. WordPress is the most mature CMS on the planet. If your store is also a content brand (recipes, tutorials, magazine-style content driving product sales), WordPress's editorial tools beat Shopify by a wide margin.
- Total customisation freedom. It's PHP and a database. Anyone with mid-level WordPress chops can change anything.
Where WooCommerce hurts:
- Hosting + performance. Shared WordPress hosting can't handle real traffic. Once you cross ~500 daily visitors, you need managed hosting (£40–£300/month). The "cheap" advantage evaporates.
- Security. WordPress is the largest target on the web for automated attacks. Every plugin you add is another potential vulnerability. Patches must be applied within days of release.
- Plugin chaos. Most WooCommerce stores end up with 30–60 plugins. Each plugin update can break others. Each conflict eats developer hours. We've audited stores that spend more on plugin debugging than they would on a Shopify subscription.
- Checkout conversion. Out-of-the-box WooCommerce checkout converts noticeably worse than Shopify. You can fix this with extensions and custom development — and most stores don't.
When WooCommerce is the right choice:
- You're a content-first brand (cooking blog with recipes that drive cookware sales, a publication with merch, a teaching site with course sales).
- You have specific WordPress experience on the team.
- Total annual revenue is below ~£500K and you genuinely cannot justify Shopify's monthly cost.
- You need a customisation that Shopify and headless explicitly don't support.
Otherwise, Shopify is almost always the better choice. The lifetime cost difference shrinks fast once you factor in maintenance time.
Headless Next.js — when, and only when
"Headless commerce" means decoupling the storefront (what shoppers see) from the commerce backend (cart, checkout, inventory). The commerce engine — usually Shopify, Commerce Layer, BigCommerce, or Saleor — exposes an API. Your storefront is a custom-built Next.js (or Remix, or Astro) app that calls that API.
Why this exists:
- Sub-1.5s page loads on slow connections. Critical for the India market and increasingly for any mobile-heavy site.
- Bespoke product experiences that don't fit Shopify's templates — configurators, 3D viewers, AR try-on, gated B2B catalogs, conditional pricing.
- Multi-region with deep localisation (currency, language, content, promotions) that Shopify Markets doesn't handle elegantly.
- Content-as-commerce: marketing pages, lookbooks, editorials, and product pages all in one fast app with no replatforming.
The real cost:
- Initial build: £25,000 – £120,000+ depending on scope.
- Ongoing maintenance: a developer's attention every couple of weeks at minimum. The system is bespoke; you can't just "install a plugin".
- You're still paying Shopify or a commerce backend on top of build costs.
When it's worth it:
- £2M+ annual revenue where a 5% conversion uplift from speed alone pays the build in months.
- A clear UX vision that the platform templates can't deliver and that you have evidence will move the needle.
- Multi-region with diverging needs (Arabic RTL + LTR English + Hindi/Devanagari).
- Editorial content as a primary acquisition channel and product pages need to live in the same fast frontend.
When it's a vanity project:
- "Our developer wants to use Next.js." Not a reason. The right question is what business outcome justifies the build.
- Annual revenue under £1M. The math doesn't work yet.
- A solo founder with no in-house engineering. You'll be locked into your agency.
We do a lot of headless work for the right kind of client. We've turned away several where the answer was "stay on Shopify, fix three things on your theme, save £80K".
The decision framework
Forget the platform debate for a moment. The actual decision tree:
- Is your annual revenue under £500K? → Shopify Basic or WooCommerce. Build cheap. Stop fiddling with the stack. Spend time on acquisition.
- £500K – £3M annual? → Shopify or Shopify Advanced. Standard theme + maybe one or two custom sections. Don't fall for re-platforming pitches at this stage.
- £3M – £10M annual? → Shopify Plus is usually right. Consider headless only if you have a specific UX problem the platform can't solve.
- £10M+ annual? → Headless makes increasing sense, especially in international markets. The 1–2% conversion uplift from a faster, more bespoke storefront pays the engineering cost.
This framework over-indexes on revenue because revenue maps closely to what you can afford and what's worth optimising. Add nuance for your industry (luxury sees higher headless value at lower revenue; commodity goods see lower).
Region-specific notes
- UAE: Shopify works well. The Markets + multi-currency setup is solid. Cash on Delivery requires an app (we like Easy COD). Arabic RTL needs a theme that supports it natively — most don't, plan for custom dev.
- UK: All three options work. Shopify dominates for SMB; WooCommerce remains common for content-led brands. VAT MOSS post-Brexit needs a tax app (Avalara, TaxJar). Standard.
- India: Shopify is gaining ground but D2C brands often run on WooCommerce or a custom build because Shopify pricing is steep relative to revenue. Razorpay integration is critical. CCAvenue still matters for higher AOV.
Final word
The right stack is the one you can run profitably for the next 24 months without re-platforming. Almost everyone over-engineers this decision. The right move at £500K revenue is Shopify with a good theme. The right move at £5M is Shopify Plus with maybe three custom sections. The right move at £20M might be headless — or might still be Shopify, because the team you have can ship faster on what they know.
Want a stack recommendation specific to your business?
We've built and rebuilt enough stores across the UK, UAE, and India to give you a straight answer. We'll look at your traffic, conversion, AOV, growth trajectory, and team — and tell you whether your current stack is the bottleneck.
Black Arrow Technologies builds e-commerce platforms from Shopify themes to bespoke headless Next.js storefronts. We unlocked ₹2.3Cr of revenue in 6 months for a UAE luxury watch retailer with a headless rebuild. We've also told several would-be headless clients to stay on Shopify and save the money. Both answers are correct in the right context.