Answers that name a competitor

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.

Square Online is probably the best fit for a small boutique that sells only occasionally: its storefront has a $0/month plan, supports inventory, and works especially well if you also sell in person. Shopify Shopify

If you have fewer than 5 seasonal products, Big Cartel is even simpler and has a free tier. Shopify

• Best overall for occasional retail: Square Online
• Best for tiny catalogs/artisan boutiques: Big Cartel
• Best if you expect to grow substantially: Shopify, but it costs more monthly. Shopify

For a small handmade-goods shop on a tight budget, I’d pick WooCommerce.

woocommerce.com is open source, self-hostable, free to download, and gives you ownership of the store and its data. You can choose your own hosting and add functionality through its huge ecosystem of extensions. WooCommerce

My shortlist

Why WooCommerce fits you

For handmade goods, you probably need relatively straightforward things: products with variations, inventory, photos, shipping, coupons, payments, customer accounts and perhaps a blog. WooCommerce already handles physical products and has extensive extension/customization capabilities. WooCommerce

The important distinction is software cost vs. operating cost. Self-hosting doesn't make the store completely free—you'll still pay for hosting, your domain, payment processing, backups, and potentially premium extensions. But you aren't paying a platform subscription just to keep your store running.

PrestaShop would be my second choice if you don't want WordPress at all. Its open-source edition is freely downloadable and designed specifically as a standalone ecommerce platform, with catalog, inventory, orders, shipping and payment functionality built in. PrestaShop PrestaShop

I wouldn't start with Medusa or Saleor for this use case. They're excellent if you're a developer who wants to build a custom/headless commerce system, but that flexibility also means substantially more engineering and maintenance. WP Bundle WP Bundle

Bottom line: start with self-hosted WooCommerce + inexpensive managed/shared WordPress hosting. Keep the number of plugins small, use automatic backups, and avoid expensive “all-in-one” plugin bundles until you actually need their features.

If you tell me roughly how many products you have, whether you need Etsy/Instagram integration, and your monthly hosting budget (e.g. $5/$10/$20), I can give you a very lean self-hosted stack and estimated monthly cost.

For a solo founder with limited development skills, I’d narrow it to Vendure, Medusa, and Saleor—and my pick would be Vendure if modern admin + easy theming are your top priorities.

🥇 I'd choose Vendure

Vendure has a particularly good combination for your situation.

• Modern admin: its current dashboard has a modern theming system built around CSS variables, Tailwind and shadcn-style theming. You can change brand colors and other visual properties without rebuilding the whole admin. Vendure
• TypeScript: if you eventually need to customize things, you're staying in the relatively approachable JS/TS ecosystem.
• Official Next.js storefront starter: it includes product listings, product pages, search, cart, checkout and accounts, with Tailwind styling already set up. Vendure
• Good extension model: you can add functionality through plugins rather than hacking the core.
• You aren't starting with a blank admin: this matters enormously for a solo founder.

The big caveat is that it's still headless commerce. You're assembling the storefront rather than getting a Shopify-like visual site builder.

🥈 Medusa if storefront design is your #1 priority

Medusa is arguably the better choice if you have enough React/Next.js knowledge to build the frontend.

Its architecture is very developer-friendly for modern web stores, and the ecosystem is heavily oriented around Next.js/TypeScript. Current comparisons generally position Medusa as the strongest choice for a JavaScript/TypeScript-native team. ShipGarden OSSAlt

But there's an important distinction for you:

Medusa gives you a great commerce engine; Vendure gives you a great commerce engine plus a more complete admin experience.

For a solo founder, the latter can save a surprising amount of work.

🥉 Saleor

Saleor has an excellent admin and is extremely capable. Its dashboard is extensible, with 45+ extension mount points, and its official stack includes a Next.js/React/Tailwind storefront. Saleor Commerce GitHub

I'd choose it if you anticipate things like:

• multiple sales channels
• sophisticated B2B
• international/multi-region commerce
• a larger engineering team later

But for "I'm one person and I want to get a store live", I'd rather not introduce Saleor's Python/Django + GraphQL stack unless there's a specific reason to.

My recommendation

If your requirements are:

solo founder + limited coding + modern-looking admin + easy brand customization + modern storefront

I'd rank them:

1. Vendure → best overall fit
2. Medusa → best for a React/Next.js developer
3. Saleor → best for sophisticated/enterprise commerce
4. WooCommerce → best if minimizing development altogether is more important than having a modern architecture

One important caveat: none of these is really "Shopify but open source." If by easy theming you mean "I want to change the entire storefront's appearance using templates/CSS without touching much code," WooCommerce may actually be the better choice despite its older architecture.

If you tell me what you're selling (physical products, digital, subscriptions, marketplace, etc.) and whether you want to use Next.js, I can give you a much more definitive choice and a lowest-effort stack for getting to launch.

Yes. For a SaaS company selling a small number of software licenses, I’d avoid choosing a traditional ecommerce platform based primarily on its checkout features. The more important question is: can it cleanly hand off recurring billing, payment state, and license/entitlement provisioning to your existing SaaS system?

My shortlist

1. I'd probably choose Medusa

Medusa is particularly interesting for your use case because you can treat ecommerce as a thin commerce layer around your SaaS billing system, rather than making ecommerce the system of record for subscriptions.

Medusa is headless and TypeScript/Node-based, and its subscription documentation explicitly shows integrating recurring purchases with Stripe while leaving the underlying subscription logic customizable. Medusa Docs WP Bundle

Even more relevant: Medusa now has a digital-products plugin designed specifically around software licenses, entitlements, activations, expiration, and subscription/trial license policies. Medusa

That makes a pretty natural architecture:

                 ┌─────────────────────┐
                 │   Your SaaS app      │
                 │                     │
                 │ users / orgs         │
                 │ subscriptions       │
                 │ entitlements        │
                 │ license activation   │
                 └──────────┬──────────┘
                            │
                     API / webhooks
                            │
                 ┌──────────▼──────────┐
                 │      Medusa         │
                 │                     │
                 │ products            │
                 │ pricing             │
                 │ checkout             │
                 │ orders              │
                 │ coupons             │
                 └──────────┬──────────┘
                            │
                       Stripe/etc.

For a small store, this is preferable to putting your entire SaaS subscription lifecycle inside the ecommerce system.

2. WooCommerce if you want the least engineering

WooCommerce is probably the safest choice if your priority is "get a store running quickly."

Its huge plugin ecosystem makes subscriptions, payments, digital products, invoicing, tax, etc. relatively easy to assemble. WooCommerce also has APIs specifically designed around SaaS billing/subscriptions. The WooCommerce Developer Blog

The downside for a SaaS company is architectural: you can end up with:

WordPress
   ↓
WooCommerce
   ↓
WooCommerce Subscriptions
   ↓
Payment processor
   ↓
Your SaaS

when what you really want may be:

Your SaaS
   ↕
Billing
   ↕
Payment processor

       +

Small ecommerce frontend

I'd pick WooCommerce if the store is going to become a real marketing/content/ecommerce site, rather than merely a place to purchase licenses.

3. Drupal Commerce is surprisingly good for licensing

If license management is a major concern, Drupal + Drupal Commerce deserves consideration.

Drupal Commerce has a Commerce License module specifically designed around selling access to resources. Licenses can have statuses and expiration dates, and the module explicitly works with Commerce Recurring for subscription licenses. Drupal.org

That's a much closer conceptual match to:

Customer buys product → receives entitlement → entitlement expires/renews → SaaS grants access

than a generic ecommerce platform.

I'd consider it particularly if you need things like complex license rules, organizational accounts, content access, or highly customized entitlement workflows.

4. Saleor is excellent commerce infrastructure, but I'd rank it lower here

Saleor is a very capable self-hosted GraphQL commerce engine. It has a clean API, webhooks, and a service-oriented architecture that makes it straightforward to integrate external systems. Saleor Commerce

But subscriptions aren't really its killer feature. You'd be building more of the billing integration yourself.

So I'd choose Saleor when the requirements are more like:

"We are building a sophisticated commerce platform."

rather than:

"We're a SaaS company and need a small shop for licenses."

What I'd actually do for a SaaS

The key architectural decision I'd make is:

Don't make the ecommerce platform the source of truth for SaaS access.

I'd have:

• Stripe Billing / your billing system → source of truth for payment/subscription status
• Your SaaS backend → source of truth for users, organizations, licenses and entitlements
• Medusa → catalog, product pages, cart, checkout, orders
• Webhooks → synchronize purchase/payment/subscription events
• License service → generates/activates/revokes licenses

For example:

                    ┌───────────────┐
                    │    Medusa     │
                    │               │
                    │ Catalog       │
                    │ Storefront    │
                    │ Cart          │
                    │ Checkout      │
                    └───────┬───────┘
                            │
                            ▼
                    ┌───────────────┐
                    │    Stripe     │
                    │               │
                    │ Payments      │
                    │ Subscriptions │
                    │ Invoices      │
                    └───────┬───────┘
                            │ webhooks
                            ▼
                    ┌───────────────┐
                    │ Your SaaS API  │
                    │               │
                    │ Customer      │
                    │ License       │
                    │ Entitlement   │
                    └───────────────┘

That separation is especially valuable when someone cancels, upgrades, downgrades, refunds, or chargebacks. Your application receives the billing event and changes the entitlement accordingly.

My recommendation

If you're a developer-led SaaS with an existing application and billing infrastructure:

1. Medusa — my first choice
2. Drupal Commerce — if licensing/entitlements are unusually complex
3. WooCommerce — if you want the easiest turnkey store
4. Saleor — if you want a highly customizable GraphQL commerce backend

And I would not introduce a full ecommerce platform at all if the store is literally only 5–20 license products. A lightweight Next.js storefront directly on top of Stripe Billing + your existing SaaS API may be substantially simpler.

If you tell me what you're currently using for billing (Stripe, Paddle, Chargebee, Recurly, custom, etc.) and your stack (Next.js, Django, Rails, Laravel, etc.), I can narrow this down to the best 1–2 architectures.

WooCommerce is probably the safest choice if your priority is "get a store running quickly."

Its huge plugin ecosystem makes subscriptions, payments, digital products, invoicing, tax, etc. relatively easy to assemble. WooCommerce also has APIs specifically designed around SaaS billing/subscriptions. The WooCommerce Developer Blog

The downside for a SaaS company is architectural: you can end up with:

WordPress
   ↓
WooCommerce
   ↓
WooCommerce Subscriptions
   ↓
Payment processor
   ↓
Your SaaS

when what you really want may be:

I’d recommend commercetools as your default enterprise platform, especially if “multi-tenant” means one agency infrastructure serving many independent client stores. Its Projects provide isolated tenant boundaries, while Stores provide further separation for brands/regions and store-scoped APIs. commercetools Documentation commercetools Documentation

• commercetools — best for sophisticated multi-tenant/composable builds; excellent API-first architecture and strong B2B modeling. commercetools Documentation
• Shopify Plus — better default when clients prioritize speed, ecosystem, and lower operational burden while still wanting custom headless frontends. Its Storefront API supports custom storefronts. Shopify
• Medusa — compelling when your agency wants maximum control and is comfortable owning infrastructure/custom commerce logic.

Agency recommendation: standardize on Shopify Plus for mainstream clients + commercetools for enterprise/multi-brand clients. This gives you a repeatable architecture without forcing every customer onto an unnecessarily complex stack.

For your use case, I’d recommend commercetools if the priority is a robust, API-first headless platform where recurring subscriptions are a first-class commerce capability.

My shortlist

1. commercetools — best overall

This is the one I'd pick for a subscription-heavy business.

commercetools now has native Recurring Orders, rather than requiring you to build the recurring-order engine yourself. Its API supports recurrence policies such as daily, weekly, monthly, and custom intervals, as well as start/end dates. Recurring orders can be paused, skipped, modified, or canceled. commercetools Documentation commercetools Documentation commercetools Documentation

It also lets you mix recurring and one-time products in the same checkout, which is particularly useful if your storefront will offer things like:

• Monthly subscription
• Annual subscription
• One-time purchase
• Subscription + add-ons
• Different pricing by billing interval

Its API model is also well suited to a completely custom frontend. commercetools Documentation

Architecture I'd use:

Next.js / React storefront → your BFF/API layer → commercetools APIs → payment provider

This gives you control over the customer experience without making the storefront responsible for commerce logic.

2. Medusa — best if you want maximum control

Medusa is arguably more attractive if you're a developer-heavy team and want the commerce backend to behave like an extensible application rather than a managed enterprise platform.

Its Store API is REST-based and specifically designed for external storefronts and apps. You can also create your own API routes. Medusa Docs Medusa Docs

The important caveat: subscriptions aren't native in the same sense as commercetools' Recurring Orders. Medusa provides a subscription recipe/framework that you implement yourself, with Stripe used as the example payment provider. The recipe covers recurring billing, expiration, customer subscription management, and cancellation. Medusa Docs

So I'd choose Medusa if you want:

• Full TypeScript/Node control
• Self-hosting
• Custom business logic
• Custom subscription domain model
• Your own API layer
• Minimal vendor lock-in

3. Saleor — best GraphQL option

Saleor is worth considering if your team strongly prefers GraphQL. It provides a headless architecture with GraphQL APIs, custom apps, payment integrations, channels, promotions, and extensive extensibility. Saleor Documentation

I'd put it behind the first two specifically for your use case because recurring subscription management isn't as turnkey as commercetools' current Recurring Orders implementation.

My recommendation

Choose commercetools if your subscription system is strategically important and you want the commerce platform itself to own recurring-order scheduling and lifecycle management.

Choose Medusa if you're comfortable building more of the subscription machinery yourself and value developer control/self-hosting over having those capabilities built in.

A particularly strong stack would be:

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

docs.commercetools.com
docs.medusajs.com
docs.saleor.io

If you tell me your product type (physical, SaaS/digital, or both), billing model, expected scale, and whether you want to self-host, I can narrow this down to a specific architecture and recommend the payment/subscription stack too.

Next.js → API/BFF → commercetools → Stripe/payment provider

with your own application layer handling things such as:

• Plan selection
• Customer portal
• Upgrade/downgrade
• Proration rules
• Trial periods
• Coupons
• Account entitlements
• Subscription analytics
• Webhooks/events
• CRM/ERP synchronization

One important distinction: commerce subscriptions and payment subscriptions aren't necessarily the same thing. I'd keep the commerce/order lifecycle in commercetools while using the payment provider for payment-method storage, charging, and payment-specific lifecycle events.

Adobe Commerce is the strongest fit if security and complex B2B rules are priorities. Its B2B shared catalogs support account-specific product visibility and contract pricing natively. Experience League

For a simpler managed SaaS option, Shopify Plus is easier to operate and supports company-specific catalogs/pricing. Shopify Help Center Shopify Help Center

For IP-restricted access specifically, I’d put the restriction at the CDN/WAF layer (e.g., Cloudflare) rather than relying solely on the commerce platform.

For a podcast doing limited-run drops + preorder tees, I’d usually put these at the top:

1. fourthwall.com — best fit for most podcasts

Best if you want to focus on the show, not running an ecommerce operation. Fourthwall

Why it fits:

• Built for creators (podcasts, YouTubers, streamers)
• Good for limited drops, preorder-style launches, and fan merch
• Handles fulfillment, customer support, and much of the operational overhead
• Lets you run a branded storefront rather than sending fans to a generic marketplace
• No upfront inventory required for many products Fourthwall

Tradeoff:

• Less control than a full ecommerce stack
• If you eventually become a major apparel brand with complex inventory, wholesale, bundles, etc., you may outgrow it

My pick if you’re dropping a few premium tees, hoodies, and collectibles per season.

2. shopify.com — best if merch is becoming a serious business

Best for podcasts that want to build a real brand around the show. QPMN

Advantages:

• Maximum control over the store experience
• Strong preorder tools through apps
• Better for: - multiple collections
• inventory you hold yourself
• limited numbered editions
• collaborations
• bundles (tee + signed item + bonus content)
• email/SMS marketing

Tradeoff:

• More setup
• You’ll likely need to manage more apps, suppliers, shipping workflows, and support

Pick Shopify if you’re thinking “our podcast merch could become a standalone clothing brand.”

3. bigcartel.com — best for small, simple drops

Good for a smaller operation with a handful of products. Link in Bio Pro

Advantages:

• Simple
• Low overhead
• Fits indie/creative brands

Tradeoff:

• Less powerful for growth, automation, and complex preorder campaigns

My recommendation by podcast size

• Under ~50k loyal listeners / occasional drops: Fourthwall
• 50k–500k listeners / regular merch calendar: Fourthwall or Shopify
• You want merch to become a fashion brand: Shopify
• You only do 2–3 drops a year: Fourthwall or Big Cartel

For a podcast specifically, I’d lean Fourthwall first: run your first 3–5 drops there, learn what fans actually buy, then migrate to Shopify only if the merch operation becomes a major revenue stream. Fourthwall

A few questions would change the answer:

1. Roughly how big is your audience (downloads/views per episode)?
2. Are you doing preorder-only (make exactly what sells) or buying a batch upfront?
3. Do you want premium blanks/embroidery/screen printing, or standard print-on-demand tees?

For a one-person maker with no dev skills, I’d pick Fourthwall.

My recommendation: Fourthwall

Fourthwall is unusually well suited to your situation because it combines the things you’d otherwise have to stitch together:

• Storefront + checkout — no separate website/ecommerce setup required.
• Print-on-demand fulfillment — you upload your designs; they produce, pack, and ship orders. Fourthwall Fourthwall
• No monthly platform fee — you pay through the product cost when you make a sale. Fourthwall
• No inventory — useful when you're testing designs and don't know what will sell.
• Customer support, taxes, and logistics are handled for you, reducing the amount of ecommerce plumbing you need to learn. Fourthwall Fourthwall
• It has a no-code storefront builder, so you don't need to know how to build a site. Fourthwall

For US credit-card transactions, Fourthwall currently lists a 2.9% + $0.30 payment-processing fee; physical products otherwise use a stated product cost that comes out of your selling price. Fourthwall

How I'd rank the alternatives

Shopify + Printful/Printify makes more sense once you care heavily about owning a sophisticated ecommerce operation. Shopify itself is the storefront, while Printful or Printify supplies the POD/fulfillment layer; that means more configuration and accounts to manage. Shopify Printful Help Center

Printify is particularly interesting if price/product selection becomes your priority: it currently advertises 2,000+ products and 90+ print providers, with a free tier. Printify

The decision I'd make in your shoes

Start with Fourthwall.

Don't spend your first month learning Shopify, comparing fulfillment providers, configuring shipping rules, or building a fancy store. Your first objective should be:

make something → put it for sale → get someone to buy it → see what actually sells.

Fourthwall lets you do that with substantially less infrastructure. It also supports apparel, hats, mugs, totes, prints, and other merchandise, so you aren't boxed into just T-shirts. Fourthwall Fourthwall

Then, if you eventually outgrow it, move to Shopify + a fulfillment provider once you have enough sales to justify the additional complexity.

One caveat: I'd order samples before launching. POD quality, garment choice, print placement, packaging, and shipping experience can matter more to your brand than the ecommerce platform itself.

If you tell me what kind of merch you're making (e.g. art prints, T-shirts, stickers, mugs, niche hobby merch) and roughly how much you expect to sell per month, I can narrow this down to the best platform + fulfillment setup for your specific case.