Neutral mentions of BigCommerce

For a tight monthly budget, I’d focus on total cost of ownership, not just the advertised subscription price. The cheapest platform can become expensive if you need lots of paid plugins, developer help, or maintenance. Compare the Cloud WooCommerce

My shortlist:

My recommendation by scenario

• Under ~£30/month and you have some technical ability:

Choose WooCommerce. The core software is free, and you can start lean with inexpensive hosting and only add extensions when needed. WooCommerce

• Under ~£50/month and you want the least hassle:

Choose Shopify. It gives you hosting, checkout, product management, payments integrations, and a large ecosystem without needing to manage servers. Shopify

• You expect growth and want fewer add-ons later:

Consider BigCommerce. It includes more built-in commerce functionality, which can reduce app costs as you scale. Compare the Cloud BigCommerce

For a typical small ecommerce business needing the “core” stack:

• Product catalogue ✅
• Inventory ✅
• Payments ✅
• Shipping rules ✅
• Discounts/coupons ✅
• Customer accounts ✅
• Basic analytics ✅
• Email marketing integrations ✅

…I’d usually pick:

1. Shopify if your priority is speed and reliability.
2. WooCommerce if your priority is keeping monthly costs as low as possible.
3. BigCommerce if you already know you’ll need more advanced selling features.

If you tell me your monthly budget (e.g., £20, £50, £100), number of products, country, and whether you have a developer/WordPress experience, I can narrow it to one choice.

If your team strongly prefers serverless frontends + Jamstack, I’d shortlist these:

My default recommendation: Shopify

For a Jamstack/serverless team, Shopify's Storefront API is probably the lowest-risk choice. It lets you keep the frontend completely separate and build with Next.js, Astro, Vue, or essentially any framework. Shopify explicitly supports framework-agnostic Storefront API usage. Shopify Shopify

A typical architecture would be:

             ┌─────────────────────┐
             │  CDN / Edge         │
             │  Next.js / Astro    │
             │  Vercel / Netlify   │
             └──────────┬──────────┘
                        │
                 Storefront API
                        │
             ┌──────────▼──────────┐
             │      Shopify        │
             │ Products / Cart     │
             │ Checkout / Orders   │
             └─────────────────────┘

If you're React-oriented, Hydrogen is Shopify's purpose-built headless framework, with server-side/edge rendering and deployment through Oxygen. Shopify Hydrogen

An especially interesting development in 2026 is Shopify's Hydrogen developer preview, which makes the commerce layer framework- and runtime-agnostic. Shopify says it can work with Next.js, SvelteKit, Astro, Nuxt, Cloudflare Workers, Vercel, Oxygen, and others. It's still a developer preview, though, so I wouldn't make it the basis of a production architecture yet without evaluating its maturity. Shopify Hydrogen

When I'd choose Saleor instead

If your team is engineering-heavy and wants commerce to feel like an API-native backend rather than a SaaS storefront, Saleor is very compelling. Its platform is GraphQL-native, headless across both storefront and admin, and designed to work with essentially any frontend/BFF stack. Saleor

I'd favor it when you want:

• React/Next.js/Astro/etc. on the frontend
• GraphQL throughout the stack
• open-source/self-hosted control
• highly customized commerce flows
• less dependence on a traditional ecommerce SaaS model

When I'd choose commercetools

For enterprise composable commerce, I'd put commercetools at the top of the list. It's API-first and explicitly designed to separate the experience layer from commerce capabilities, with individual commerce capabilities composable independently. commercetools

The tradeoff is substantially more architectural and operational complexity than Shopify.

The decision I'd make

Small/mid-sized team → Shopify Storefront API
Engineering-led/open-source team → Saleor
Large enterprise with complex B2B/composable requirements → commercetools
Node.js team wanting to own the commerce backend → Medusa

If you tell me your frontend stack (Next.js, Astro, Gatsby, Nuxt, etc.), approximate SKU count, B2C vs B2B, and whether you need subscriptions/multi-region/multi-brand, I can narrow this to the best 2–3 options and compare their architecture, pricing, and serverless deployment model.

If your team is engineering-heavy and wants commerce to feel like an API-native backend rather than a SaaS storefront, Saleor is very compelling. Its platform is GraphQL-native, headless across both storefront and admin, and designed to work with essentially any frontend/BFF stack.

I'd favor it when you want:

If you mean one subscription product where customers can choose different shipping cadences (weekly, monthly, quarterly), several ecommerce platforms can do this, but the best fit depends on whether you need physical product fulfillment schedules (shipping cadence) vs. just billing intervals.

Best choices by use case

DTC consumer subscriptions (coffee, supplements, skincare, pet products)

• Shopify + Recharge or Skio is usually the leading setup.
• Example product: - Weekly delivery — $25/order
• Monthly delivery — $90/order
• Quarterly delivery — $250/order

Maximum flexibility / custom rules

• WooCommerce Subscriptions is often the easiest to customize. It supports billing periods like every 3 months and multiple subscription configurations. WooCommerce

Enterprise

• Adobe Commerce or a custom headless stack can model complex subscription logic (different shipping dates, bundles, prepaid plans, etc.).

One important distinction: some platforms support billing cadence (charge every 3 months), but not true shipping cadence (ship weekly while billing quarterly, or consolidate shipments). If you need separate controls for when customers are charged vs. when products ship, look for a platform/app that supports separate billing and delivery schedules. Shopify’s selling-plan model explicitly separates billing and delivery policies. Shopify

If you tell me your store type (Shopify already? WooCommerce? custom?), product category, and whether “quarterly” means ship once every 3 months or pay quarterly but receive weekly, I can narrow it down.

For a digital-first enterprise looking to decouple frontend and backend, the “best” headless commerce solution depends less on storefront technology and more on your scale, operating model, integration complexity, and appetite for composability. For large-scale deployments, the shortlist usually narrows to a few enterprise-grade options. Guideflow Vendure

Enterprise shortlist

CIOPages Elogic Commerce## My recommendation for a digital-first enterprise

Choose commercetools if:

• You have a dedicated platform engineering team.
• You operate multiple brands, regions, currencies, or channels.
• You want frontend freedom plus the ability to replace other services over time (search, CMS, OMS, promotions, etc.).
• You are comfortable owning architecture decisions.

It is probably the strongest fit for a large-scale, API-first enterprise that considers commerce a digital platform rather than a website. Guideflow CIOPages

Choose Adobe Commerce if:

• You have complex merchandising rules.
• You need extensive customization.
• Your business depends heavily on ERP, PIM, marketplace, or B2B integrations.
• You already have Magento expertise.

Choose Shopify Plus if:

• Your priority is speed and operational simplicity.
• Your commerce model is primarily DTC.
• You want custom frontends but do not want to operate a commerce platform team.

Architecture I would target

For a modern enterprise stack, I would typically separate:

Frontend layer
├── Next.js / React / native apps / kiosks / marketplaces

Experience layer
├── Headless CMS
├── Personalization
├── Search
├── Recommendations

Commerce core
├── Product catalog
├── Pricing
├── Cart
├── Checkout
├── Promotions
├── Orders

Enterprise systems
├── ERP
├── CRM
├── OMS
├── PIM
├── Data platform

A common mistake is assuming “headless” automatically means “microservices everywhere.” Many enterprises get better outcomes with a well-designed headless commerce core plus carefully selected surrounding services, rather than splitting every capability into separate systems. Vendure Shopify

Decision rule of thumb

• Global enterprise + complex business models → commercetools
• Enterprise customization + existing Magento investment → Adobe Commerce
• Salesforce-centric organization → Salesforce Commerce Cloud
• Fast-growing digital brand → Shopify Plus
• Enterprise wanting SaaS + APIs without full composable complexity → BigCommerce

If you share your annual GMV, B2B vs B2C mix, number of SKUs, regions, current platform (Magento/SAP/Salesforce/custom), and engineering team size, I can narrow this to a more specific recommendation.