Answers that do not mention BigCommerce

For a small handmade-goods shop and no coding experience, I’d look first at Shopify, Wix, and Squarespace.

My practical recommendation

Shopify is a strong default if your primary goal is selling products, rather than simply building a website. It includes hosting, payment processing, inventory/order tools, customizable themes, and an app ecosystem, and its store builder doesn't require coding. Shopify Shopify

If you have a small catalog—say 5–30 handmade products—and want something especially straightforward, Wix is worth considering. Its drag-and-drop editor is designed for non-technical users and includes ecommerce functionality on its paid plans. Shopify

If photography and the visual presentation of your handmade work are especially important, Squarespace is another natural fit; it emphasizes polished templates and straightforward visual editing. Shopify

One other option: Big Cartel is specifically aimed at artists and makers and can be simpler than a full Shopify setup, particularly if you have a small inventory. Shopify

If you tell me roughly how many products you sell and your monthly budget (e.g. under $20, $20–50, or $50+), I can narrow this down to the most suitable option and explain exactly what you'd pay.

For a small handmade goods shop with no coding skills, I’d usually narrow it down to these hosted options:

My quick recommendation:

• Just starting and testing demand: Etsy
• Want your own branded storefront: Shopify
• Selling a small collection of premium handmade items: Squarespace
• Want to design everything yourself visually: Wix
• Have 5–50 products and want simplicity: Big Cartel

For most handmade shops planning to build a recognizable brand, I’d start with Shopify and connect it to social channels or marketplaces later. It avoids needing to rebuild your store if your product line grows. Shopify

If you tell me:

1. roughly how many products you sell,
2. whether you already sell on Etsy/social media, and
3. your monthly budget,

I can narrow it to one best fit.

Yes. If you sell both one-time digital downloads and recurring subscriptions, there are several platforms that can handle both without you stitching together separate systems.

The important distinction

Podia is worth looking at if your business is more creator/content-oriented. It puts downloads, recurring memberships, courses, community, email marketing, checkout, and customer accounts in one system. Its current offering explicitly supports both instant digital downloads and monthly/yearly subscriptions. Podia

Lemon Squeezy is particularly interesting if your "subscriptions" are more like software/SaaS subscriptions or you sell internationally. It supports one-time purchases, subscriptions, license keys, and merchant-of-record tax handling. GumKit StackDrawer

Fourthwall is aimed heavily at creators who want a branded storefront combining digital products, memberships, and potentially physical merchandise. Fourthwall

So, for a startup like yours, I'd narrow it to:

• Downloads + memberships/community/content → Podia
• Downloads + SaaS/software subscriptions → Lemon Squeezy
• Downloads + memberships + merch/creator brand → Fourthwall
• Very simple creator storefront → Gumroad or Payhip

If you tell me what the digital downloads are (ebooks, templates, software, courses, etc.), what the subscription gives customers, and roughly your monthly revenue, I can compare the best 2–3 options on fees, payment processing, taxes, subscription management, customer ownership, and API/integration capabilities.

Podia is worth looking at if your business is more creator/content-oriented. It puts downloads, recurring memberships, courses, community, email marketing, checkout, and customer accounts in one system. Its current offering explicitly supports both instant digital downloads and monthly/yearly subscriptions. podia.com

Lemon Squeezy is particularly interesting if your "subscriptions" are more like software/SaaS subscriptions or you sell internationally. It supports one-time purchases, subscriptions, license keys, and merchant-of-record tax handling.

Yes. If you sell both one-time digital downloads and recurring subscriptions, there are several creator-focused platforms that can handle both under one storefront.

Podia

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. Gumroad Gumroad Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. Gumroad

Fourthwall

fourthwall.com is interesting if you may eventually add physical merchandise alongside downloads and subscriptions. It combines digital products, memberships, and merch in a branded storefront. Fourthwall

What I'd compare before choosing

For a startup rather than an individual creator, I'd specifically look at:

• Transaction fees vs. monthly fees at your expected revenue
• Whether subscriptions can have multiple tiers
• Churn management, upgrades/downgrades, failed payments, etc.
• Whether the platform acts as merchant of record and handles sales tax/VAT
• Customer ownership/export and API access
• Coupons, bundles, cross-sells, and upsells
• Whether subscribers and one-time buyers live in one customer database
• Stripe/PayPal support and payout timing

If you tell me roughly what your downloads are (ebooks, templates, software, courses, etc.), what the subscription provides, and your approximate monthly revenue, I can narrow this to 2–3 platforms and compare their current fees and capabilities.

podia.com is probably worth a close look if digital products are the core of the business. It supports downloads, recurring subscriptions/memberships, bundles, upsells, email marketing, a website, and community in one system. Podia Podia

Gumroad

gumroad.com is the simpler option. You can sell files and create recurring memberships/subscriptions, including multiple tiers and billing frequencies. gumroad.com gumroad.com Its tradeoff is that it charges transaction fees rather than a monthly platform fee; its current pricing page lists a 10% + $0.50 fee on direct sales. gumroad.com

Fourthwall

For an enterprise catalog with thousands of SKUs and genuinely complex pricing, I’d shortlist platforms based less on SKU count and more on how complicated your customer-specific pricing, catalogs, contracts, ERP integration, and buying workflows are.

One I'd investigate first: Adobe Commerce

Based solely on what you've described, Adobe Commerce is worth putting near the top of your evaluation list. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, customer groups, negotiated quotes, and multiple websites/price scopes. Experience League Experience League Experience League

For example, Adobe's shared catalogs let you expose different product selections and pricing to different companies, while its pricing system supports fixed or percentage custom prices and quantity-based tiers. Experience League

That said, if your pricing is more like "every customer has a contract, price depends on customer + SKU + quantity + region + currency + effective dates + negotiated agreement, with ERP as the ultimate source of truth," I'd put SAP Commerce, commercetools, and Elastic Path into the evaluation alongside Adobe rather than assuming a traditional commerce platform is sufficient. Current enterprise-platform comparisons similarly distinguish integrated suites from composable platforms and emphasize the integration/operating-model tradeoff. CIOPages Elastic Path

The questions I'd use to narrow it down

The most important thing is your pricing model. For example:

• How many SKUs? 10k, 100k, 1M+?
• How many customers/accounts?
• Is pricing customer-specific, contract-specific, or mostly volume-based?
• Do you have customer-specific catalogs where customers can only see certain SKUs?
• Does pricing depend on quantity, geography, currency, channel, contract, dates, or promotions?
• Do prices originate in SAP, Oracle, Dynamics, Salesforce, or another ERP/CPQ?
• Do buyers need quotes, approval workflows, requisitions, purchase orders, or punchout?
• Do you need multiple storefronts/brands/countries?
• Do you want a headless/composable architecture, or would you rather have more functionality built into the platform?

If you give me those details—especially SKU count, number of customers, pricing rules, ERP/CRM, and whether this is B2B or B2C—I can make a much more useful side-by-side architecture comparison of Adobe Commerce vs. SAP Commerce vs. commercetools vs. Salesforce vs. Elastic Path.

Based solely on what you've described, Adobe Commerce is worth putting near the top of your evaluation list. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, customer groups, negotiated quotes, and multiple websites/price scopes. Experience League Experience League Experience League

For example, Adobe's shared catalogs let you expose different product selections and pricing to different companies, while its pricing system supports fixed or percentage custom prices and quantity-based tiers. Experience League

That said, if your pricing is more like "every customer has a contract, price depends on customer + SKU + quantity + region + currency + effective dates + negotiated agreement, with ERP as the ultimate source of truth," I'd put SAP Commerce, commercetools, and Elastic Path into the evaluation alongside Adobe rather than assuming a traditional commerce platform is sufficient. Current enterprise-platform comparisons similarly distinguish integrated suites from composable platforms and emphasize the integration/operating-model tradeoff.

The questions I'd use to narrow it down

The most important thing is your pricing model. For example:

If flexibility + API quality are your top criteria, I’d shortlist Medusa, Saleor, commercetools, and Shopify. They make different tradeoffs.

My take

For a developer building a genuinely custom frontend, I'd look hardest at Medusa and Saleor.

• Medusa is particularly attractive if you want the backend itself to be customizable. Its storefront is completely separate from the commerce application, and its Store API is REST-based; you can also add custom API routes/modules. Medusa Docs Medusa Docs Medusa Docs
• Saleor is compelling if you prefer GraphQL everywhere. Its core API is GraphQL, and its architecture emphasizes headless storefronts, channels, checkout, extensions, and custom admin apps. Saleor Documentation Saleor Commerce
• commercetools is probably the strongest choice when you're building a larger composable/enterprise system. It exposes both HTTP and GraphQL APIs and is designed around composing commerce capabilities with other systems. commercetools Documentation commercetools Documentation
• Shopify gives you considerably more out-of-the-box commerce infrastructure. Its Storefront API is GraphQL and supports custom web, mobile, game, and other experiences, while the Admin API handles backend management. Shopify Shopify

If I were choosing based specifically on frontend freedom

I'd think about it this way:

Maximum control → Medusa

You can treat commerce as your backend and build essentially whatever frontend/BFF architecture you want. This is especially attractive if you're comfortable owning infrastructure and commerce logic. Medusa Docs

Best GraphQL-native experience → Saleor

If your frontend is heavily typed and you want clients to request exactly the data they need, Saleor's GraphQL-first approach is very appealing. Saleor Documentation Postman

Enterprise composability → commercetools

If the frontend is only one component of a larger architecture involving ERP/PIM/CMS/search/payments/etc., commercetools is worth serious consideration. commercetools Documentation

Least backend work → Shopify

You sacrifice some backend-level freedom, but you get a mature commerce engine while retaining control over the frontend. Shopify explicitly supports bringing your own stack and using its Storefront API for custom experiences. Shopify Shopify

One important distinction

"Headless" doesn't necessarily mean fully customizable commerce logic.

For example, Shopify is excellent if your architecture is:

Custom React / Next.js frontend
            ↓
       Shopify APIs
            ↓
Products / Cart / Checkout / Orders

Whereas Medusa is more like:

Custom frontend
       ↓
Your BFF / API layer
       ↓
   Medusa backend
       ↓
Custom commerce modules
       ↓
Payments / fulfillment / ERP / etc.

That second model gives you substantially more control over how commerce works, not merely how it is rendered.

So if your phrase "flexibility and APIs" means I want to build unusual commerce behavior and don't want the platform fighting me, I'd start with Medusa and Saleor. If you tell me your stack (e.g. Next.js + TypeScript + Postgres, B2B/B2C, subscriptions, multi-vendor, etc.), I can narrow this down to the architecture I'd use.

If flexibility + API control are your top criteria, I’d shortlist Medusa, Saleor, Vendure, and commercetools. For a developer building a genuinely custom frontend, the choice mostly comes down to how much of the commerce backend you want to own.

Medusa

For a TypeScript/Next.js developer, I'd look particularly closely at Medusa.

Its current architecture is modular: products, carts, pricing, inventory, orders, payments, fulfillment, promotions, etc. are separate commerce modules, and you can extend their data models and build your own workflows. Medusa Docs Medusa Docs

The API is also straightforward for a custom frontend: Medusa exposes separate Store and Admin REST APIs, provides a JS SDK, and publishes an OpenAPI specification. Medusa Docs Medusa Docs

Most importantly for your use case, the storefront is completely separate from the backend. You can build it from scratch with Next.js, React, mobile, or another frontend rather than adapting your UI to a platform's storefront model. Medusa Docs

I'd choose Medusa when you want:

• TypeScript end-to-end
• Full control over checkout/business logic
• Custom product/catalog models
• Custom pricing/promotions
• Custom APIs and integrations
• Self-hosting
• A backend you can actually modify rather than merely configure

Saleor

Saleor is particularly interesting if you prefer GraphQL.

Its API is GraphQL-first, and its architecture is deliberately headless: storefront and admin experiences are API-driven, with extensions through APIs and webhooks rather than requiring platform-specific frontend plugins. Saleor Documentation Saleor Commerce

I'd investigate Saleor if your frontend/BFF architecture is heavily GraphQL-oriented or you need sophisticated multi-channel, international, B2B, or marketplace capabilities.

Vendure

Vendure is another strong option if you want TypeScript on the backend but prefer a GraphQL/plugin-oriented architecture.

It's worth comparing directly with Medusa if your team wants to own the commerce backend rather than use a SaaS commerce service.

commercetools

commercetools is the one I'd examine for a larger enterprise project.

Its APIs include both HTTP and GraphQL, and its documentation specifically recommends using general APIs behind a middleware/BFF layer for custom frontends to maximize control. commercetools Documentation commercetools Documentation

The tradeoff is that you're buying into a much more enterprise-oriented platform rather than getting a lightweight codebase you can freely modify.

My practical decision tree

If you're a JS/TS developer building a custom Next.js frontend:
→ Medusa

If you want GraphQL everywhere:
→ Saleor

If you want TypeScript + GraphQL + a plugin architecture:
→ Vendure

If this is a large enterprise/composable-commerce project:
→ commercetools

If you mainly want a managed backend and don't want to operate commerce infrastructure:
→ Shopify headless

For your particular wording — "I'm a developer building a custom frontend" + "flexibility and APIs" — I'd start by prototyping Medusa vs Saleor, rather than starting with Shopify. The architectural difference is significant: Medusa gives you a TypeScript/REST-oriented backend you can modify deeply, while Saleor gives you a GraphQL-first API boundary with a more API/application-extension-oriented model. Eryx Innovations Lab Saleor Commerce

If you tell me Next.js/React vs another frontend, expected catalog size, B2C vs B2B, and whether you want to self-host, I can narrow this down to the architecture I'd use and show the API flow for product → cart → checkout → payment → order.

For a brick-and-mortar + online business, the right choice depends heavily on where your online store lives and how complex your inventory is. The main platforms I’d put on your shortlist are:

The practical choice

If your website is already on Shopify: I'd generally look at Shopify POS first. Shopify directly connects POS with its admin, so in-store sales update inventory alongside online sales, and it supports separate inventory by location. Shopify Help Center Shopify Help Center

shopify.com

If you're primarily a physical retailer and want a relatively straightforward all-in-one setup: Square for Retail is worth serious consideration. Its inventory system handles multiple locations, transfers, purchase orders, online orders, and in-store sales. Square Square

squareup.com

If you have significant operational complexity—multiple warehouses, marketplaces, wholesale, lots of SKUs, complicated purchasing/fulfillment—I'd investigate Cin7 or Lightspeed rather than relying solely on a basic POS inventory system. Cin7 specifically positions its system around synchronizing inventory across multiple sales channels. Cin7

The biggest thing I'd avoid is having one inventory system for the store and another for e-commerce that merely exchanges periodic updates. You want a genuine inventory source of truth with real-time quantity changes, location-level stock, transfers, returns, reservations, and ideally purchase orders.

If you tell me (1) what your online platform is (Shopify/WooCommerce/etc.), (2) what POS you use today, (3) number of stores/warehouses, and (4) roughly how many SKUs, I can narrow this to the 2–3 platforms that fit your operation and explain the tradeoffs.

For a brick-and-mortar + online business, the “best” platform depends mostly on your complexity: number of SKUs, locations, sales channels, wholesale needs, and whether you need an ERP or just inventory sync. The key is to choose a single inventory source of truth rather than trying to sync multiple systems equally.

Here are the main options I’d evaluate:

Salesforce### My typical recommendations by business stage

1. One store + Shopify store + moderate SKU count

• Shopify + Shopify POS is often enough.
• Keep Shopify as the inventory master.

2. Multiple stores, marketplaces, wholesale, or lots of SKUs

• Look at Cin7, especially if you sell through several channels and need purchasing, transfers, and fulfillment workflows. Cin7 supports integrations with ecommerce platforms, POS systems, marketplaces, accounting tools, and logistics systems. Cin7 Cin7

3. Complex operations (warehouses, manufacturing, financial reporting)

• Consider NetSuite or a similar ERP, possibly with a dedicated ecommerce layer.

What I’d check before choosing

Ask vendors to demo these exact workflows:

• A customer buys an item online → does store inventory update immediately?
• A customer buys in-store → does website availability update?
• Can you reserve stock for online orders?
• Can you transfer inventory between stores?
• Can you handle returns from one channel to another?
• Does it sync purchase orders and receiving?
• How does it handle bundles/kits/variants?
• What happens when two channels sell the last unit at the same time?

A common architecture for growing retailers is:

POS + Ecommerce → Inventory Management System → Accounting/ERP

rather than:

POS ↔ Ecommerce ↔ Marketplace ↔ Spreadsheets (which tends to create inventory mismatches).

If you share:

1. your ecommerce platform (Shopify, WooCommerce, Magento, etc.),
2. POS system,
3. number of stores,
4. approximate SKU count, and
5. whether you sell wholesale/Amazon/eBay,

I can narrow this down to 2–3 realistic choices.

POS ↔ Ecommerce ↔ Marketplace ↔ Spreadsheets (which tends to create inventory mismatches).

If you share:

1. your ecommerce platform (Shopify, WooCommerce, Magento, etc.),
2. POS system,
3. number of stores,
4. approximate SKU count, and
5. whether you sell wholesale/Amazon/eBay,

I can narrow this down to 2–3 realistic choices.

If your core requirement is a marketplace for many independent artisans, where each seller has their own storefront, products, orders, commissions, and payouts, I’d narrow the choice to WooCommerce + a mature multi-vendor extension or Shopify + a multi-vendor app.

How I’d compare them

WooCommerce has particularly good coverage for an artisan marketplace: vendors can apply, be approved, manage their own products, have vendor-specific commission rates, manage shipping, view sales reports, and receive scheduled payouts. WooCommerce WooCommerce

There are also third-party WooCommerce marketplace solutions such as Dokan, which provide vendor signup, individual vendor dashboards, order management, earnings withdrawals, and vendor statistics. WooCommerce

On Shopify, apps such as Webkul's Multi Vendor Marketplace provide seller onboarding, seller portals, commissions, automated payouts, shipping/order functionality, and other marketplace features. Shopify App Store

My practical recommendation

If you're building something Etsy-like for artisans, I'd seriously consider:

WordPress + WooCommerce + a multi-vendor marketplace extension

rather than trying to force a normal Shopify store into being a marketplace.

That's especially true if you need things like:

• Hundreds/thousands of independent artisans
• Each artisan gets their own shop page
• Seller application + admin approval
• Seller-specific commissions
• Seller-specific shipping
• Seller inventory management
• Automatic/manual seller payouts
• Artisan profiles and stories
• Product approval/moderation
• Reviews and seller ratings
• Multiple artisans in one customer order
• Your own marketplace fee
• Custom categories, filters and discovery
• Custom marketplace design/UX

WooCommerce's official Product Vendors extension supports many of these directly, including vendor-specific commissions, vendor profiles, vendor product management, sales reporting, and payout schedules. WooCommerce

However, if you want the marketplace itself to be the product rather than an ecommerce store with multiple sellers, I'd also look closely at Sharetribe. Its architecture is designed around marketplace interactions rather than simply adding vendors to a conventional store.

If you tell me (1) roughly how many artisans you expect, (2) physical products vs digital/services, (3) whether you need Stripe Connect/automatic payouts, and (4) your budget, I can give you a much more specific platform recommendation and architecture.

If your core requirement is a marketplace for many independent artisans/sellers, I’d shortlist these:

My recommendation

CS-Cart Multi-Vendor is probably the strongest fit if you expect hundreds or thousands of artisans and want the marketplace itself—not just an online store—to be the core business.

It provides dedicated seller dashboards, seller onboarding/approval, vendor-specific stores, commissions, vendor plans, moderation, shipping, analytics, and marketplace payment functionality. It also explicitly supports managing hundreds or thousands of vendors. www.cs-cart.com/ www.cs-cart.com/

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. Sharetribe Sharetribe

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts. WooCommerce WooCommerce

woocommerce.com

For an artisan marketplace specifically

I'd make sure the platform supports these before choosing:

• Seller application + approval
• Individual artisan storefront/profile pages
• Seller-controlled product listings and inventory
• Product moderation before publication
• Per-seller commissions
• Automated seller payouts
• Returns/refunds with multiple sellers involved
• Seller-specific shipping
• One customer cart containing products from multiple artisans
• Seller ratings/reviews
• Seller messaging
• Coupons/promotions
• Seller analytics
• Tax/VAT handling
• Bulk product import
• API/custom integrations
• Ability to scale from dozens → thousands of sellers

One particularly important distinction is who controls the money flow. For example, CS-Cart supports marketplace commissions, payouts, split payments and Stripe Connect, while WooCommerce Product Vendors processes sales through your store's payment gateways and then manages the vendor's commission/payout. www.cs-cart.com/ WooCommerce

If you tell me your expected number of artisans (e.g. 50, 500, 10,000), whether products are physical handmade goods, and whether you want to build on Shopify/WordPress or are open to a dedicated marketplace platform, I can narrow this down to 2–3 architectures and compare the actual costs and seller-payment workflow.

cs-cart.com

Sharetribe is attractive if you want to get an MVP running quickly without building a lot of infrastructure. It has marketplace payments through Stripe, automatic commission splitting, delayed payouts, seller/customer messaging, and listing/transaction workflows. sharetribe.com sharetribe.com

sharetribe.com

WooCommerce Product Vendors makes sense if you already use WordPress/WooCommerce. Vendors can manage their own products, shipping and profiles, while you control commissions and payouts.

For a one-person print-on-demand shop, I’d optimize for low fixed cost + easy POD integration, rather than choosing the most powerful platform.

My shortlist

Big Cartel is particularly interesting for your situation: it explicitly supports print-on-demand, has 0% platform transaction fees, and its current free tier is intended for very small catalogs; its Platinum plan is $15/month. Big Cartel Big Cartel

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with unlimited products and a large app ecosystem, including POD integrations. Shopify Shopify

WooCommerce itself costs nothing, but WooCommerce estimates typical hosting at roughly $25–$350/month depending on the store, so it's not necessarily the cheapest in practice for a beginner. woocommerce.com

Square has a genuinely $0/month online-store plan, with payment processing as the main cost; however, I'd put it behind Big Cartel for a POD-first business. squareup.com squareup.com

What I'd do in your shoes

Start with Big Cartel if you're testing the business. You can keep your fixed software cost essentially at zero while you figure out whether your designs actually sell. Once you have enough traction that you need more sophisticated marketing, analytics, apps, or automation, move to Shopify.

If you already have a fairly large catalog and you're serious about building a brand from day one, I'd skip the ultra-cheap option and start with Shopify Basic.

One important wrinkle: the POD supplier can matter more to your economics than the storefront software. Product base cost, shipping, fulfillment location, print quality, returns, and integration fees can easily overwhelm a $15–$30/month platform difference.

If you tell me roughly what you're selling (shirts, mugs, posters, stickers, etc.), expected monthly sales, and whether you're starting with Etsy or your own website, I can work out the cheapest setup—including the POD supplier—and estimate your break-even point.

For a one-person print-on-demand (POD) shop, the most cost-effective choice depends on whether you mean lowest upfront cost or best value once you start getting sales.

A practical shortlist:

Tee Verdict CloudLaunch## My recommendation for a solo POD beginner

Start with: Etsy + a POD fulfiller

For most one-person shops starting from zero, I’d begin with:

• Etsy for the storefront
• Printify or Printful for fulfilment
• Free design tools initially (for example, Canva's free tier)

Why:

• No monthly store bill while you test whether designs sell.
• Etsy already has shoppers searching for products.
• You avoid spending £20–£30+/month before you know you have demand. Tee Verdict Startup Costs

The trade-off: marketplace fees reduce your margin, and you are building on someone else's platform. Tee Verdict

When to move to Shopify

Move to Shopify when you have:

• consistent sales,
• a recognisable niche/brand,
• repeat customers,
• traffic from TikTok, Instagram, Pinterest, ads, email, etc.

Shopify is easier operationally because hosting, security, and much of the ecommerce infrastructure are handled for you, but the subscription cost makes less sense before you have sales volume. CloudLaunch

When WooCommerce makes sense

Choose WooCommerce if:

• you already use WordPress,
• you enjoy tinkering with websites,
• you want maximum control,
• you expect content/SEO to drive traffic.

The software itself is free, but you still pay for hosting, domains, and possibly plugins. CloudLaunch

A lean solo POD stack

A cost-conscious setup would look like:

1. Marketplace: Etsy
2. POD supplier: Printify/Printful
3. Design: Canva or Affinity Designer
4. Mockups: POD supplier tools or free mockup generators
5. Marketing: Pinterest/TikTok/Instagram organic content
6. Upgrade later: Shopify once sales justify it

For a one-person operation, I’d avoid paying for a full ecommerce subscription until you’ve proven that at least a few designs can sell. The biggest risk in POD is usually not the software cost — it’s paying for tools before finding products customers want.

If you're launching a physical subscription box, I’d narrow the field to Shopify + a subscription app rather than choosing a standalone billing system. Shopify handles the underlying store, inventory, shipping, and fulfillment, while the subscription layer handles recurring orders. Shopify Help Center Shopify

What I'd look at for a box business

Shopify Subscriptions is the simplest starting point. It supports recurring plans, customer self-service (skip/pause/cancel), discounts, and subscription analytics. Subscription orders flow through Shopify's normal fulfillment system, including different fulfillment locations and shipping profiles. Shopify Help Center Shopify Help Center

Bold is worth considering if your box is customizable—for example, "choose any 5 of these 15 products." Shopify specifically highlights Bold's build-a-box capabilities and gives a weekly produce-box business as an example. Shopify

Skio supports Build-a-Box, prepaid subscriptions, and standard Subscribe & Save, with configurable shipping profiles. It also automatically generates orders and handles recurring billing and payment retries. Skio Help Skio Help

One important current-market wrinkle: Recharge acquired Skio in April 2026, so I'd verify the current product roadmap, pricing, and migration implications before committing to either brand. Uncover Commerce

My practical shortlist:

• Simple fixed box: Shopify Subscriptions
• Customer chooses what's inside: Bold or Skio
• Larger/scaling subscription operation: Recharge/Skio ecosystem
• Prepaid multi-month boxes: Skio or Shopify's prepaid subscription functionality

If you tell me (1) fixed vs. customizable box, (2) expected subscribers in your first year, and (3) whether you're already on Shopify, I can compare the likely costs and fulfillment workflow for your specific setup.

Shopify Subscriptions is the simplest starting point. It supports recurring plans, customer self-service (skip/pause/cancel), discounts, and subscription analytics. Subscription orders flow through Shopify's normal fulfillment system, including different fulfillment locations and shipping profiles. Shopify Help Center Shopify Help Center

Bold is worth considering if your box is customizable—for example, "choose any 5 of these 15 products." Shopify specifically highlights Bold's build-a-box capabilities and gives a weekly produce-box business as an example. Shopify

Skio supports Build-a-Box, prepaid subscriptions, and standard Subscribe & Save, with configurable shipping profiles. It also automatically generates orders and handles recurring billing and payment retries.

One important current-market wrinkle: Recharge acquired Skio in April 2026, so I'd verify the current product roadmap, pricing, and migration implications before committing to either brand.

My practical shortlist:

For a subscription-box business, I’d narrow it to Shopify + a subscription app, Skio + Shopify, or WooCommerce Subscriptions. The right choice depends heavily on how complex your box assembly and fulfillment process is.

My practical shortlist

• Shopify + Appstle — Shopify's App Store specifically categorizes Appstle as supporting subscription boxes, bundles, recurring billing, and customer retention. Shopify App Store This is attractive if you want to get launched quickly without building a complicated system.
• Shopify + Skio — particularly interesting if subscriptions are the core of your business. Skio handles recurring billing, automatic order generation, payment retries, and a customer portal where customers can skip, pause, swap products, or update payment details. Skio It also supports Build-a-Box, prepaid subscriptions, and Subscribe & Save plans. Skio
• WooCommerce Subscriptions — a good choice if you need more technical control over the store. It supports recurring billing, 25+ payment gateways, failed-payment rebilling, subscriber self-service, and shipping/renewal scheduling specifically suited to recurring physical shipments. WooCommerce

One important distinction

If by fulfillment you mean “customers choose several products to make their own box, then I need the system to turn that into a recurring order that my warehouse/3PL can fulfill,” I'd lean toward Skio or a Shopify subscription setup with a strong box/bundling app rather than choosing based purely on recurring billing.

If you tell me (1) what you're selling, (2) whether customers customize the box, (3) approximate monthly order volume, and (4) whether you'll use a 3PL, I can narrow this down to the most suitable setup and explain the expected software costs.

If your priorities are self-hosting + full source-code access + deep customization, I’d narrow it to Medusa, Vendure, Saleor, and WooCommerce.

My recommendation: Medusa

medusajs.com is probably the best fit if you’re comfortable developing the store yourself. It’s a developer-oriented commerce engine with an MIT-licensed core, and its architecture is designed around customizing commerce logic rather than fighting a prebuilt storefront. GitHub OSSAlt

A typical stack would be:

• Medusa — products, carts, orders, customers, payments, promotions, etc.
• Next.js/React — completely custom storefront
• PostgreSQL — database
• Redis — caching/background jobs where appropriate
• Docker — deployment
• Your own VPS/cloud — hosting

That gives you essentially complete control over the UI and backend behavior.

The alternatives

vendure.io is particularly interesting if you want TypeScript but expect complicated business rules, B2B, marketplaces, multiple channels, or custom workflows. Its plugin architecture lets you extend or override core behavior without modifying the core itself, and it can be self-hosted. GitHub Vendure

saleor.io is another excellent choice if you like GraphQL and a headless architecture. It explicitly supports self-hosting and provides an open-source commerce engine, dashboard, APIs, and extensibility mechanisms. Saleor Commerce

woocommerce.com makes more sense if you want a ready-to-run traditional website rather than building a commerce application. Its enormous WordPress ecosystem means you can get a store running much faster, but the architecture is less clean if your goal is to build something radically custom. Open Source Groups

What I'd choose

If you told me:

"I want to own the server, own the code, change basically anything, and I'm willing to code."

I'd start with Medusa + Next.js + PostgreSQL + Docker.

If you told me:

"I want maximum customization but expect complicated B2B/marketplace/business workflows."

I'd seriously consider Vendure.

If you told me:

"I want something I can install, configure, add plugins to, and have a conventional ecommerce site without building the whole frontend."

I'd choose WooCommerce.

One important distinction: "open source" doesn't necessarily mean every commercial/enterprise feature of a project is open source, so check the current license and edition boundaries before committing. For example, Vendure's core is GPLv3, while its commercial Platform adds additional capabilities. Vendure

If you tell me what you're selling, approximate number of products, whether you need subscriptions/B2B/marketplace, and your preferred programming language, I can narrow this down to one and give you the exact self-hosted architecture I'd use.

If your priorities are self-hosting, full source-code access, and deep customization, I’d narrow it to Medusa, Saleor, Vendure, and WooCommerce. The biggest decision is whether you want a traditional store you can customize, or a headless commerce engine where you build the storefront yourself. OpenReplay Blog Toolradar

My shortlist

If I were building a new custom store

I'd look at Medusa first.

It gives you a commerce backend rather than forcing your storefront into a particular theme/CMS. You can build the customer-facing site with Next.js/React, while Medusa handles products, carts, orders, payments, fulfillment, regions, etc. Its Node/TypeScript architecture is particularly attractive if you want to write your own business logic. OpenReplay Blog OpenSourceProjects.cc

A typical architecture would be:

                 ┌─────────────────────┐
                 │   Next.js Storefront│
                 │   Your design/UI    │
                 └──────────┬──────────┘
                            │
                         API/SDK
                            │
                 ┌──────────▼──────────┐
                 │       Medusa        │
                 │                     │
                 │ Products            │
                 │ Cart                 │
                 │ Orders               │
                 │ Customers            │
                 │ Pricing              │
                 │ Promotions           │
                 │ Payments             │
                 │ Fulfillment          │
                 └──────────┬──────────┘
                            │
                    ┌───────▼───────┐
                    │  PostgreSQL   │
                    └───────────────┘

That gives you much more architectural freedom than something like Shopify.

When I'd choose the others

Saleor — I'd investigate this if you have a Python team or need sophisticated multi-channel, multi-region, B2B, or GraphQL-driven commerce. Its documentation specifically covers multi-region commerce, marketplaces, custom shipping, digital products, and dashboard extensions. Saleor Documentation

Vendure — particularly interesting if you're already a TypeScript developer and want a strongly structured plugin architecture with GraphQL. Kryeo

WooCommerce — choose this if you want to get a conventional store running quickly and benefit from the enormous WordPress ecosystem. It's explicitly open-source and customizable, with a large extension ecosystem. WooCommerce The tradeoff is that you're building on WordPress/PHP rather than a clean, modern headless commerce architecture.

The important distinction

I'd divide your options like this:

"I want a store I can install and customize."

→ WooCommerce / PrestaShop

"I want to build my own ecommerce product and control essentially everything."

→ Medusa / Vendure / Saleor

If by "customize fully" you mean things like custom checkout logic, unusual product configurations, subscriptions, custom pricing rules, multiple storefronts, custom customer accounts, integrations with your own backend, mobile apps, etc., I'd lean toward the headless group rather than WooCommerce.

If you tell me what you're selling, your expected scale, and what tech stack you prefer (Node/TypeScript, Python, PHP, etc.), I can narrow this down to 1–2 options and give you a recommended architecture and hosting setup.

For a mobile app storefront, the “most developer-friendly” commerce API depends on whether you want a full commerce backend, a headless storefront, or just payments. The strongest options today are usually:

My shortlist by app type

1. Consumer shopping app (Amazon-style storefront)

Pick Shopify.

Why:

• Product catalog, search, collections, carts are already modeled.
• Checkout is handled securely through Shopify’s checkout stack.
• You avoid building tax, payment, order, and fulfillment flows from scratch. Shopify Shopify

Typical stack:

• iOS: Swift + Shopify Storefront API
• Android: Kotlin + Shopify Storefront API
• Cross-platform: React Native + Shopify APIs

2. Marketplace app (many sellers)

Consider Stripe Connect + a commerce backend.

Why:

• Strong payment routing and seller payouts.
• Better fit when you need your own seller model, commissions, onboarding, and custom workflows.

3. Retail app tied to physical stores

Pick Square.

Why:

• Catalog, inventory, orders, payments, and customer APIs are already connected.
• Good fit for omnichannel apps where stores already use Square. Square Square

4. You want maximum control

Pick Medusa (or another headless commerce backend).

Why:

• Your mobile app becomes the primary experience.
• You own the data model and integrations.
• More engineering effort, but fewer platform constraints. Medusa Docs

If I were choosing for a new mobile storefront

• Fastest MVP: Shopify
• Best developer ergonomics: Shopify or Stripe (depending on whether you need commerce vs payments)
• Most customizable long-term: Medusa
• Best retail/POS integration: Square

A few details would change the recommendation: are you building a single-brand store, a marketplace with multiple sellers, or a platform where merchants plug their own stores into your app? Also, are you using native iOS/Android, React Native, or Flutter?