Answers that do not mention BigCommerce

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

My recommendation: CS-Cart Multi-Vendor

For artisans, I'd lean toward CS-Cart Multi-Vendor if you're expecting hundreds or thousands of sellers.

It is designed specifically around independent vendors rather than trying to turn a normal ecommerce store into a marketplace. It supports vendor onboarding/approval, vendor-specific permissions, commissions, vendor plans, product management, shipping, and vendor storefronts. docs.cs-cart.com

It also has capabilities particularly useful for a marketplace where different artisans sell similar products—for example, multiple vendors can offer the same product at different prices, allowing customers to compare offers. docs.cs-cart.com

CS-Cart Multi-Vendor marketplace builder

When I'd choose Sharetribe instead

Choose Sharetribe if you're building a new marketplace and want to validate the concept before investing heavily in development. It has built-in supplier onboarding, listings, payments, automated payouts, commissions, reviews, messaging, and approval workflows. www.sharetribe.com

Sharetribe marketplace platform

For an artisan marketplace, I'd specifically want these capabilities:

• Seller self-registration + admin approval
• Individual artisan storefronts
• Seller dashboards
• Product/listing management
• Commission per sale
• Automated seller payouts
• Stripe Connect or equivalent marketplace payments
• Seller-specific shipping
• Reviews/ratings
• Seller verification/KYC
• Product moderation
• Coupons/promotions
• Vendor subscriptions or listing fees
• Bulk seller onboarding
• Search/filtering by artisan, category, location, material, etc.
• Ability to scale to thousands of sellers

If you tell me roughly how many artisans you expect (e.g. 100, 1,000, or 10,000+), whether they're selling physical handmade products, and your budget, I can narrow this to the best 2–3 platforms and compare their actual costs and limitations.

For a two-person boutique on a tight budget, I’d start with Big Cartel.

My pick: Big Cartel

It’s particularly well suited to small, curated catalogs rather than huge inventories:

• $0/month on its Gold plan, with up to 5 products. www.bigcartel.com
• $15/month for Platinum, with more products and features; annual billing brings that to $12/month. www.bigcartel.com
• Designed specifically around artists, makers, and small businesses.
• Simple storefronts mean less time spent managing the website—which matters when there are only two of you.
• You can sell online and in person, which is useful for a local boutique. www.bigcartel.com

Two alternatives I'd consider

Square Online is especially worth considering if your boutique already takes payments through Square, because you can connect online and in-person selling. technologyadvice.com

I wouldn't start with Shopify purely to "future-proof" the business. It's excellent, but you're paying for a much larger ecosystem before you necessarily need it. Current comparisons put a full Shopify store around $39/month, versus Big Cartel's $0–$15 range. www.shopify.com

Bottom line: If you have, say, 5–50 core products, I'd choose Big Cartel. If you have a physical shop and already use Square, I'd lean Square Online.

If you tell me roughly how many products you sell, your average monthly online sales, and whether you already use Square, I can tell you which one is likely to be cheapest in total (including payment fees).

For a business that sells both digital downloads and a few physical products, the best platform is usually one that can handle:

• instant digital delivery (PDFs, templates, courses, files, etc.)
• shipping and inventory for physical items
• taxes and payments
• customer accounts and email marketing
• growth beyond a simple storefront

My top picks:

memvers.comwoocommerce.com

My recommendation by situation

If you’re building a real brand:
➡️ Shopify is probably the best fit. It gives you one store where a customer can buy a downloadable product and a physical item in the same checkout. You can add digital delivery through apps and keep shipping/inventory native. technologyadvice.com

If your digital products are the main business and physical items are occasional:
➡️ Payhip or Gumroad may be simpler and cheaper, especially if you don’t need advanced inventory.

If you already have a WordPress website or blog:
➡️ WooCommerce is worth considering because it gives you deep customization and supports both digital and physical products. memvers.comwoocommerce.com

If you want free traffic/discovery:
➡️ Consider adding Etsy as a sales channel, but I wouldn’t make it your only home because you have less control over your store and customer relationship. leanbizkit.com

A setup many small sellers use:

• Shopify = main store
• Etsy = extra discovery channel
• Email list = customer ownership

If you tell me:

1. what kind of digital downloads you sell (templates, art, ebooks, files, courses, etc.),
2. roughly how many physical products you have, and
3. whether you already have a website/audience,

I can narrow it down to the best choice.

For a small food subscription-box business, I’d narrow it to three main approaches rather than looking at generic ecommerce platforms.

My shortlist

1. Subbly — probably my first choice

subbly.co is specifically designed around subscription businesses, including subscription boxes, food delivery, meal kits, replenishment, and customizable boxes. Subbly Subbly

For a food box, some particularly useful capabilities are:

• Weekly, monthly, quarterly, seasonal, or custom billing cycles
• Customers can skip, pause, resume, or cancel
• Customer-managed payment methods and shipping information
• Subscription-specific inventory management
• Multiple SKUs inside a box
• Cutoff dates and specific shipping dates
• Failed-payment recovery
• Customer surveys for creating/customizing boxes
• One-time products alongside subscriptions
• Shipping/fulfillment integrations
• Recurring billing through payment gateways such as Stripe and PayPal Subbly Subbly

That's a very good match for something like "Get a box of locally made snacks every month" rather than a conventional ecommerce store that happens to have subscriptions.

2. Shopify + Appstle/Recharge/etc.

If you expect the business to eventually become a larger food brand with lots of one-time products, I'd seriously consider shopify.com.

Shopify has a large ecosystem of subscription apps. Its current subscription-app marketplace includes options such as Appstle, Kaching, and others. Shopify App Store Shopify App Store

The advantage is that you get an extremely mature ecommerce platform underneath the subscription system:

Shopify → subscription app → payment processing → fulfillment/shipping

That gives you considerably more flexibility if you later want to sell individual products, gift cards, wholesale products, etc.

The downside is that you're assembling more pieces. For a small subscription business, I'd be wary of ending up with Shopify + subscription app + reviews app + bundles app + email app + fulfillment app + ... and paying for all of them.

3. WooCommerce + WooCommerce Subscriptions

I'd choose this primarily if you're already comfortable with WordPress.

It's highly customizable and can be economical, but you're taking on more responsibility for hosting, plugins, updates, security, and compatibility. For a small food business where the goal is simply to sell boxes and fulfill them reliably, I wouldn't choose it over Subbly unless you have a specific reason to want WordPress.

What I'd choose for your situation

If your business looks roughly like:

Customer signs up → chooses a box → gets charged every month → you pack the box → ship it → customer can skip/pause/change their subscription

I'd start with Subbly.

It's built around exactly that workflow rather than adapting a general ecommerce platform to it. Subbly also supports customers building/customizing subscription boxes, which could be particularly useful if your food boxes have selectable items. Subbly

If instead you're envisioning:

Subscription box + 50 individual food products + gift shopping + promotions + wholesale + potentially a large catalog

I'd start with Shopify + a subscription app.

One important thing for food

I'd evaluate the platforms less on the basic "can it charge someone every month?" question—they all can—and more on fulfillment mechanics.

Before committing, I'd test whether the software handles your exact model for:

• Subscription cutoff dates
• Billing date vs. shipping date
• Skip/pause
• Failed credit cards
• Changing the contents of a box
• Seasonal boxes
• Inventory allocation for upcoming subscription shipments
• Different shipping rates/zones
• Local pickup vs. shipping
• Sales tax
• Expiration/lot tracking if applicable
• Customers changing their next shipment without contacting you

Subbly is particularly strong on these subscription-specific workflows. Subbly Support Center

If you tell me roughly how your box works (e.g. fixed box vs. customer chooses items, monthly vs. weekly, expected number of subscribers, and whether you need shipping/local delivery), I can narrow this down to 2–3 specific setups and what each would likely cost you per month.

Shopify → subscription app → payment processing → fulfillment/shipping

That gives you considerably more flexibility if you later want to sell individual products, gift cards, wholesale products, etc.

The downside is that you're assembling more pieces. For a small subscription business, I'd be wary of ending up with Shopify + subscription app + reviews app + bundles app + email app + fulfillment app + ... and paying for all of them.

3. WooCommerce + WooCommerce Subscriptions

I'd choose this primarily if you're already comfortable with WordPress.

It's highly customizable and can be economical, but you're taking on more responsibility for hosting, plugins, updates, security, and compatibility. For a small food business where the goal is simply to sell boxes and fulfill them reliably, I wouldn't choose it over Subbly unless you have a specific reason to want WordPress.

What I'd choose for your situation

If your business looks roughly like:

Customer signs up → chooses a box → gets charged every month → you pack the box → ship it → customer can skip/pause/change their subscription

I'd start with Subbly.

It's built around exactly that workflow rather than adapting a general ecommerce platform to it. Subbly also supports customers building/customizing subscription boxes, which could be particularly useful if your food boxes have selectable items.

If instead you're envisioning:

Subscription box + 50 individual food products + gift shopping + promotions + wholesale + potentially a large catalog

I'd start with Shopify + a subscription app.

One important thing for food

For three retail stores + a straightforward ecommerce site + inventory tracked separately by store, I’d shortlist these:

My recommendation

I'd pick Shopify if "simple" is the key requirement.

For your three stores, you can set up:

• Store A → its own inventory quantity
• Store B → its own inventory quantity
• Store C → its own inventory quantity
• Online store → fulfillment/order routing across those locations
• POS at each store → sales automatically decrement the appropriate location

Shopify explicitly supports separate inventory quantities by location and real-time syncing across POS, online store, and sales channels. Shopify Shopify Help Center

Square would be my choice if you care more about the in-store checkout experience and less about having a particularly powerful ecommerce operation.

If you tell me roughly how many SKUs you have, whether you already use a POS, and whether online orders need to ship from whichever store has stock, I can tell you which of the three I'd actually choose for your setup.

For a local brick-and-mortar shop, I’d generally recommend Square Online if your primary goal is to sell locally with in-store pickup + local delivery and you already have, or plan to use, Square for your point of sale.

My ranking

1. Square Online — best for a typical local shop

• Online store and physical-store POS are tightly integrated.
• Supports in-store/curbside pickup and local delivery.
• You can use your own staff for delivery or use on-demand delivery partners.
• Inventory, orders, payments, and in-person sales can stay in one system. Square Square Square
• Particularly attractive if you're selling things like gifts, specialty food, flowers, apparel, home goods, etc.
• Shopify — best if you expect the ecommerce side to become a major business

• Excellent online storefront and much stronger ecommerce ecosystem.
• Native local delivery lets you define delivery areas by radius or ZIP/postal code, set delivery pricing, and provide delivery updates. Shopify
• Pickup is well supported, and Shopify has a large ecosystem of pickup/delivery apps if you need sophisticated scheduling, routing, or delivery rules. Shopify Shopify App Store
• I'd choose this over Square if you expect significant online growth, lots of products, subscriptions, marketing, or multiple sales channels.
• WooCommerce — best if you already have WordPress

• Very flexible, but more hands-on.
• You can build almost any pickup/delivery workflow, but you'll generally be assembling and maintaining more pieces yourself.
• I wouldn't choose it specifically for a simple local pickup/delivery operation unless there's already a good reason to use WordPress.

The simple decision

I'd pick Square if:

"We're primarily a local store, and we want our website to be an extension of our physical shop."

I'd pick Shopify if:

"We're a retail brand that happens to have a local store, and we want ecommerce to become a significant part of the business."

One important distinction: the ecommerce platform and the delivery service don't necessarily have to be the same thing. For example, Shopify can manage the order and have your staff deliver it, while Square can similarly support your own couriers or on-demand delivery. Square Shopify

If you tell me what kind of shop it is, approximate number of products, whether they already use a POS (Square/Clover/etc.), and roughly how far they want to deliver, I can tell you which I'd choose and what the setup would look like.

If you’re non-technical and your main sales channels will be social links + email, I’d narrow it to Shopify vs. Wix.

My pick: Shopify

Shopify is the stronger choice if you expect social selling to be a major part of the business.

• Instagram + Facebook: Shopify can sync your product catalog with Meta, so products can appear in Facebook/Instagram shopping experiences, and you can manage orders from Shopify. help.shopify.com
• More social channels: Shopify also supports channels including TikTok, Pinterest, YouTube and others. www.shopify.com
• Email: Shopify has built-in marketing tools, with additional email/CRM options available if you need more sophisticated campaigns.
• Links are easy: You can put a Shopify product or collection link directly in an Instagram bio, Facebook post, email, text message, etc.
• Room to grow: If social selling takes off, Shopify has a much larger ecosystem of apps and integrations.

Shopify's official site

The easier alternative: Wix

Wix may actually feel easier at the beginning if you want to build the whole website yourself. Wix specifically targets non-technical store owners and supports Facebook/Instagram selling, email marketing, CRM, social posts and ads from its ecosystem. www.wix.com

Wix's official site

What I'd choose for your situation

Bottom line: If you're thinking “I'll post on Instagram/Facebook, put the product link in my bio, send emails, and want everything to flow into one storefront,” I'd go with Shopify. If you're thinking “I want the simplest possible website builder and I'm only going to sell a modest number of products,” I'd choose Wix.

One important distinction: “integrates with social media” isn't the same as “people can complete the purchase inside the social app.” Meta's commerce requirements and available shopping features vary by region/account, so I wouldn't choose a platform based solely on the promise of an Instagram Shop. help.shopify.com

If you tell me what you're selling (physical products, digital products, services, subscriptions, etc.) and roughly how many products, I can tell you which platform I'd pick and what the simplest setup would be.

For a small maker business that wants a simple POS + online store, I’d pick Square unless you already know you’re going to be heavily e-commerce-focused.

My quick ranking

Why Square: its free plan includes POS, online selling, websites, ordering and invoicing, so you can start without committing to a monthly software bill. squareup.com You can also take payments directly from a phone, so you don't necessarily need a dedicated register to start. squareup.com

Square

When I'd choose Shopify instead: if the online store is going to be the main business—lots of products, Instagram/social selling, sophisticated merchandising, subscriptions/apps, SEO/content, or you expect e-commerce to become much bigger than your in-person sales. Shopify's Basic plan is currently $39/month monthly ($29/month annually), with online store functionality and basic in-person selling included. www.shopify.com

Shopify

The rule of thumb

Mostly craft fairs / markets / local sales + a website → Square.

Mostly online sales + occasional markets → Shopify.

If you tell me what you make, roughly how many products/SKUs you have, and whether you'll sell mostly at markets or online, I can tell you which one I'd actually use—and what the cheapest setup would be.

Yes. For a brick-and-mortar studio selling classes + merchandise online, I’d shortlist these:

My pick: Square

For a studio with an actual physical location, Square is probably the cleanest fit. Square Appointments handles class schedules, recurring classes, capacity and online booking, while Square Online handles your merch store. Your bookings, online orders, inventory and in-person POS can live in the same ecosystem. squareup.com

For example, you could have:

Book a Class

• Monday 6 PM — Beginner Class — 12 spots
• Wednesday 7 PM — Advanced Class — 15 spots
• Recurring memberships/packages
• Online payment and automated reminders

Shop

• T-shirts
• Studio merchandise
• Equipment/accessories
• Online shipping or in-studio pickup

Square specifically supports selling products alongside services and combining service/product transactions. squareup.com

When I'd choose Wix instead

If you want your website to feel more like a premium branded studio website rather than a POS/e-commerce site, Wix is compelling. Wix Bookings supports classes, workshops, group sessions, memberships and packages, while Wix Stores handles physical merchandise. Customers can even put services and products into the same cart. www.wix.com

Bottom line:

• Square → best operational choice for a physical studio.
• Wix → best if website/design/marketing flexibility matters more.
• Squarespace → best if visual branding is the top priority. Squarespace explicitly supports selling classes/events as service products alongside physical merchandise. support.squarespace.com

If you tell me what kind of studio you run (yoga, dance, art, pottery, fitness, music, etc.) and roughly how many classes/students you have, I can narrow it down to the best 1–2 options and compare pricing/features.

For a two-person startup testing product-market fit, I’d optimize for speed to launch, low fixed cost, and not getting trapped in a complicated tech stack.

My pick: Shopify

Shopify is probably the best default if you expect the product to work and potentially become a real business.

• Setup: very low; templates + built-in checkout/payments
• Cost: Basic is currently $29/month when billed annually ($39 month-to-month), with online card rates starting at 2.9% + 30¢. www.shopify.com
• Scaling: excellent—you won't need to migrate platforms if PMF arrives.
• Marketing: strong integrations for email, ads, social, analytics, subscriptions, reviews, etc.
• Downside: $29/month is more than you need if you're literally just running an experiment.

Shopify pricing

If you're really trying to spend almost nothing

Big Cartel is particularly interesting for your situation: it has a free limited plan, while its current Platinum plan is $15/month and supports physical/digital products, shipping labels, inventory, discounts, and payment methods. www.bigcartel.com

Big Cartel pricing

Ecwid is another lightweight choice; its Starter tier is designed for beginners and supports up to 10 products, while higher tiers add things like custom domains, analytics, social selling, and abandoned-cart recovery. www.ecwid.com

Ecwid pricing

What I'd actually do

If you're testing whether people will pay, not whether you can build a beautiful store:

Shopify Basic → one simple theme → 3–10 products → Stripe/Shopify Payments → analytics → launch.

Don't spend a week customizing the store. Your first version should be good enough to answer:

Will strangers click → understand the offer → trust us → pay?

If you have fewer than ~10 products and expect to run the experiment for only a month or two, I'd seriously consider Big Cartel instead to minimize burn.

If you tell me what you're selling (physical/digital), approximate number of SKUs, expected monthly sales, and whether you already have a website, I can give you a very specific stack—including the cheapest payment/email/analytics setup.

Yes. If the client truly has a $0 hosting budget, you have a few realistic options. The best choice depends on whether you need a full ecommerce store, a custom-coded storefront, or just a catalog + checkout.

Best free hosted storefront options

1. squareup.com — best for small businesses

• $0/month hosted storefront
• Hosting + SSL included
• Product pages, cart, checkout, inventory
• Good if the client is selling physical goods locally
• You only pay payment processing fees when they sell Fit Small Business

Downside: Less developer freedom than building your own frontend.

2. freewebstore.com — simple "launch and go"

• Free hosted store
• SSL included
• Product management
• Payment integrations
• Good for a client who just needs something live quickly Freewebstore

Downside: Customization is more limited.

3. bigcartel.com — good for small catalogs

• Popular with artists/makers
• Free tier exists for very small inventories
• Clean storefront templates Fit Small Business

Downside: Product limits make it unsuitable for larger stores.

4. wix.com — good for design-heavy sites

• Build the storefront free
• Hosting included
• Good visual editor wix.com

Downside: Accepting payments generally requires a paid business plan. wix.com

If you're a freelancer/developer

For more control, I’d consider:

Static frontend + free backend services

Example stack:

• Frontend: React / Next.js / Astro
• Hosting: pages.cloudflare.com or vercel.com free tiers
• Payments: Stripe Checkout
• Products: JSON, Airtable, Supabase, or a headless CMS

This can look much more custom and costs nothing until traffic grows.

Open-source ecommerce

• WooCommerce is free software, but you still need somewhere to host WordPress. Open Source Groups
• PrestaShop is similar: free software, but hosting is the cost.

What I’d pick for a client project

• Small local shop: Square Online
• 5–50 products, handmade goods: Big Cartel or Freewebstore
• Client wants a polished custom site: Astro/Next.js + Stripe Checkout + free hosting
• Client expects a serious ecommerce business later: start on a platform they can eventually migrate away from

One thing to watch as a freelancer: "free hosting" often means the platform owns the checkout/data flow. If you’re building this for a paying client, make sure the account, domain, payment processor, and store ownership are under the client's email, not yours.

Yes. If your goal is almost zero overhead (no monthly fee, no inventory, automatic file delivery), there are several good options. For digital downloads + prints, I’d look at these first:

My picks by situation:

• Selling printable art, planners, templates, SVGs, wall art, PDFs: Payhip is probably the best starting point. It gives you a storefront, handles digital delivery, and you can start without paying monthly. payhip.com
• Selling art prints and building a creator following: Ko-fi Shop is attractive because you can combine a shop with tips, memberships, and commissions. ko-fi.com
• Testing one or two products quickly: Gumroad is very simple—upload a file, set a price, share a link. felloai.com

For physical prints, you have two low-overhead approaches:

1. Digital-first: Sell print-ready files (PDF/JPG/PNG) and let buyers print them.
   • Lowest overhead.
   • No shipping, packaging, or customer service around damaged orders.

2. Print-on-demand: Upload designs and have a service print/ship them.
   • More passive, but lower margins.
   • Common options include Printful and Printify (these are production/shipping services rather than storefronts).

A very lean setup would be:

Canva/Affinity Designer → Payhip or Ko-fi → Pinterest/Instagram/TikTok traffic → automated delivery

You could realistically start with:

• $0/month software cost
• no inventory
• no website
• no shipping
• only paying fees when you make sales

If you tell me what kind of downloads you want to sell (wall art, planners, templates, fonts, photography, AI art, craft files, etc.), I can suggest the best platform and pricing model.

For a free storefront focused on preorders + crowdfunding-style sales, I’d usually recommend starting with a lightweight ecommerce platform rather than a traditional crowdfunding site. The best choice depends on whether you need a full branded store, a campaign page, or just a way to collect commitments.

My top picks:

My recommendation by scenario

1. You already have customers/a following
→ Use Square Online or Big Cartel first.
Create a “coming soon” product page, collect preorders, and fulfill once you hit your target.

2. You’re launching a physical product and need a Kickstarter-style campaign page
→ Use Shopify + a crowdfunding/preorder app. Apps like Fundlify or Crowdfunder can add goals, progress bars, reward tiers, and preorder mechanics. apps.shopify.com

3. You have almost no budget and just need to validate demand
→ A simple stack:

• Free storefront (Square Online or Big Cartel)
• Email signup/waitlist
• Preorder product page
• Manual updates to backers

4. You want “if we get 500 orders, we manufacture”
→ Look for true crowdfunding features:

• funding goal
• deadline
• progress bar
• limited rewards/tiers
• automatic refunds if the goal fails

Most free ecommerce tools handle preorders, but fewer handle true crowdfunding logic. apps.shopify.com

If you tell me what you’re selling (physical product, digital product, apparel, game, food, etc.), expected number of backers, and whether you already have an audience, I can narrow it to one platform.

Yes. If you already have WordPress and just need a simple, inexpensive store, I’d look at these two first:

1. WooCommerce — my default recommendation

woocommerce.com is free at its core, with no monthly subscription and no percentage of your sales going to WooCommerce. You pay your payment processor's transaction fees instead. WooCommerce WooCommerce

For a small store, you can start with:

• WooCommerce — free
• WooPayments or Stripe — no monthly fee; transaction fees apply
• Your existing WordPress hosting
• A free WooCommerce-compatible theme
• No paid extensions unless you actually need them

WooPayments currently starts at 2.9% + $0.30 per transaction for U.S.-issued cards, although the exact rate can vary by transaction. WooCommerce

I'd choose WooCommerce if: you're selling physical products, want a normal shopping cart, need shipping/inventory, or think the store might grow.

2. SureCart — potentially simpler

surecart.com is particularly interesting if you want to keep things lightweight. Its free Launch plan currently supports physical and digital products, checkout, subscriptions, inventory, shipping calculations, etc., with a 2.9% transaction fee on the free plan. SureCart WordPress.org

The big difference is that SureCart handles much of the ecommerce processing on its own cloud infrastructure rather than putting everything inside your WordPress database. WordPress.org

I'd choose SureCart if: you want a very simple store and don't want to deal with the larger WooCommerce ecosystem.

What I'd do in your situation

If you're talking about something like 5–50 products and a basic "add to cart → checkout → pay" store, I'd start with WooCommerce. You can get the whole thing running without buying a bunch of add-ons.

If you tell me what you're selling (physical products, digital downloads, services, memberships, etc.), roughly how many products, and whether you need shipping, I can tell you which option would be cheapest and simplest for your particular site.

For a tight-budget, headless-friendly shop, I’d start by evaluating Medusa first, then compare it against Shopify headless if you value lower operational burden over maximum cost control. hunchbite.com

A practical shortlist:

ossalt.com

My evaluation order for a low-cost build

1. Medusa + Next.js storefront

• Likely the best value if you already have frontend/backend talent.
• Open-source core means you avoid a large SaaS license.
• Good fit for custom storefronts, unusual workflows, and owning your stack. hunchbite.com
• A realistic lean setup:
  • Next.js frontend
  • Medusa backend
  • PostgreSQL
  • Stripe payments
  • Managed hosting/VPS

2. Shopify headless

• Evaluate if your priority is "launch fast and don't maintain commerce infrastructure."
• You get inventory, orders, checkout, admin, payments, and a huge app ecosystem.
• The tradeoff is recurring SaaS/app costs and less backend freedom. hunchbite.com

3. Saleor

• Worth a look if your team is already strong in Python/Django or you need GraphQL-native commerce.
• It can be powerful, but it is usually not my first recommendation for the cheapest MVP path. hunchbite.com

What I would avoid on a tight budget

• Enterprise composable platforms (commercetools, Elastic Path, etc.) — great technology, but usually not aligned with a cost-sensitive launch.
• Building a fully custom commerce backend — headless does not mean you need to rebuild carts, inventory, orders, tax, and payments yourself.

My default recommendation

• Small team + developers: Medusa + Next.js.
• Non-technical commerce team: Shopify headless.
• Complex B2B/catalog requirements: Saleor or Medusa.

The key question is whether your "tight budget" constraint is mostly monthly platform spend or engineering time. If you tell me your expected SKU count, order volume, frontend stack (Next.js? React? something else), and whether you need B2B features, I can narrow this to a top 1–2 choices.

For an indie game dev selling downloadable builds + license/activation keys, my first pick is itch.io.

Best budget option: itch.io

itch.io

• Very low upfront cost: creating a storefront and hosting your game is free. You choose itch.io's revenue share, including the ability to set it to 0%. itch.io itch.io
• Direct downloads: upload Windows/macOS/Linux builds and buyers get a persistent download page. Updates can automatically become available to existing purchasers. itch.io itch.io
• License/key distribution: itch.io generates unique download keys and can also distribute external keys such as Steam keys with purchases. itch.io itch.io
• Bulk keys: useful for press copies, Kickstarter/backer rewards, giveaways, or selling a batch of keys elsewhere. Keys can be labeled and revoked. itch.io
• No custom backend required: itch.io handles hosting, checkout, download access, and purchase management. itch.io

One caveat: if by "license distribution" you mean your own DRM/license-server system—for example, your game contacts your server and validates a unique license code—itch.io's built-in keys aren't really that. They're primarily access/download keys. You'd need a separate licensing service or your own backend.

How I'd choose

For a small indie studio, I'd start with itch.io rather than paying for a dedicated storefront. You can put your game files there, sell directly, issue keys, and later add Steam or a custom licensing system as your sales volume justifies it. itch.io itch.io

If you tell me whether you need Steam keys, your own activation keys, or both, I can narrow this down to 2–3 storefronts and compare their fees.

For a freelance developer building custom integrations for clients, I’d optimize for extension architecture, maintainability, and speed of custom development, not just “number of plugins.” The best choice depends heavily on your stack:

blog.openreplay.com

My ranking for a freelance integration developer

1. Medusa (best overall for greenfield custom stores)
If you’re building things like:

• ERP integrations
• custom pricing engines
• unusual checkout flows
• subscription logic
• marketplace features
• custom fulfillment

Medusa is a strong fit because it is designed as a commerce engine rather than a monolithic storefront. Its TypeScript stack also makes it easy to share types and patterns with modern frontend apps. opensourceprojects.cc

2. Vendure (best developer experience if you like TypeScript)
Vendure is arguably the cleanest architecture for someone who expects to write lots of custom modules. It uses a plugin model with GraphQL extensions and typed server-side code. The downside is a smaller ecosystem, so you build more yourself. blog.openreplay.com

3. WooCommerce (best money-maker for agency work)
If your clients are:

• local businesses
• brands with existing WordPress sites
• stores needing lots of marketing plugins

WooCommerce can be unbeatable because the ecosystem solves many problems already. The tradeoff is that deep customization often means wrestling with WordPress conventions and plugin conflicts. selfhosting.sh

Platforms I’d be cautious about for freelance work

Magento/Open Source

• Very capable.
• Lots of enterprise demand.
• But onboarding clients into a maintainable custom codebase can become a project by itself.

PrestaShop/OpenCart

• Good traditional store platforms.
• Less attractive if your main value proposition is “I build custom integrations and workflows.”

A practical freelance stack choice

If I were building a reusable consulting skillset:

• Default: Medusa + Next.js + PostgreSQL
• Alternative: Vendure + Next.js for highly customized clients
• Quick revenue projects: WooCommerce
• Enterprise contracts: Shopware or Magento

The biggest advantage of Medusa/Vendure is that you’re selling engineering work rather than becoming a plugin installer. You can build reusable integration modules (payments, ERPs, shipping providers, inventory systems) and carry that expertise between clients. codenote.net

If you tell me your preferred stack (Laravel/PHP, Node/TS, Python, Ruby) and the typical client size (small businesses vs $1M+ merchants), I’d narrow it down further.

For an international store with lots of tax, currency, pricing, and localization rules, I’d shortlist Medusa, Saleor, and Odoo—but my default pick would be Medusa if you have a development team.

My ranking

🥇 Medusa — my pick for your scenario

Medusa has a particularly good model for complicated international commerce. It separates regions, currencies, tax regions, tax rates/rules, and tax providers, rather than treating localization as simply translating a storefront. A region can have its own currency, countries, payment providers, fulfillment configuration, and tax-inclusive/exclusive pricing. docs.medusajs.com

The tax system also supports hierarchical tax regions, product/product-type overrides, and custom tax providers. That matters if you eventually need external tax engines or bespoke tax logic. docs.medusajs.com

It also has proper locale support using BCP 47 locale codes such as en-US and fr-FR, rather than conflating language with country. docs.medusajs.com

The biggest advantage is architectural: you can replace or extend the pieces that don't fit your tax model. Medusa explicitly supports custom tax providers and custom workflows. docs.medusajs.com

Medusa documentation

🥈 Saleor — excellent alternative

I'd choose Saleor over Medusa if your team strongly prefers Python/GraphQL and you're building a sophisticated headless/enterprise commerce stack.

Its channels are especially powerful for international operations: a single backend can have independent currencies, languages, pricing, and storefront configurations. Saleor also has a dedicated multi-region architecture. docs.saleor.io

Saleor documentation

🥉 Odoo — consider it if tax/accounting is the center of gravity

If by "complex localization" you mean VAT/GST, fiscal positions, invoicing, accounting, inventory, purchasing, and country-specific financial workflows, rather than primarily storefront localization, I'd seriously investigate Odoo.

The advantage isn't necessarily that its storefront is better than Medusa's; it's that the commerce system and back-office/financial system can be one system.

What I would avoid

I wouldn't make WooCommerce my first choice for a store where international tax logic is one of the hardest parts of the architecture. It can absolutely do international commerce, but complex localization often turns into a collection of plugins/extensions that you then have to keep compatible.

For a greenfield build, I'd rather have the underlying commerce engine model region → country → tax rules → currency → pricing → payment/fulfillment explicitly.

The important distinction

If your requirements look like:

"Sell in 40 countries, 15 currencies, 12 languages, different VAT/GST rules, tax-inclusive pricing in some markets, tax-exclusive in others, different prices by market, and occasionally override tax treatment by product."

Medusa is probably the best starting point. Its documented multi-region model maps unusually well to that problem. docs.medusajs.com

If instead you're saying:

"We need sophisticated tax/accounting compliance integrated with ERP, inventory, purchasing, and financial reporting."

Odoo becomes much more compelling.

And if you're building a large headless commerce platform with multiple storefronts/brands/channels, I'd put Saleor and Medusa essentially neck-and-neck, with the choice driven heavily by your engineering stack.

If you tell me which countries you sell into, approximate number of currencies/languages, B2C vs B2B, and whether you're using an external tax engine like Avalara/TaxJar, I can narrow this down to a specific architecture and platform.

If your top priorities are plugin/extension ecosystem + active developer community, I’d pick WooCommerce overall.

My ranking

🥇 WooCommerce — best ecosystem

The biggest advantage is that you're not just getting WooCommerce's extensions—you inherit the enormous WordPress plugin/theme ecosystem as well. Current WooCommerce documentation says its Marketplace puts extensions in front of 3.6M+ active stores, and it provides dedicated tooling for extension development and testing. developer.woocommerce.com

The developer community is unusually accessible: GitHub, official forums, Slack, developer office hours, meetups, and WordPress communities all feed into the ecosystem. woocommerce.com

Choose it if: you want to build plugins, integrations, payment/shipping modules, customizations, SaaS integrations, or client stores and want the largest possible addressable ecosystem.

🥈 PrestaShop — best dedicated ecommerce alternative

PrestaShop has a substantial module ecosystem—its official marketplace has thousands of modules—and the project explicitly supports community developers through GitHub, Slack, forums, and its marketplace. help-center.prestashop.com

I'd favor it over WooCommerce if you don't want WordPress involved and want an ecommerce-first architecture.

🥉 Magento Open Source — best for sophisticated systems

Magento's extension ecosystem is excellent and its architecture is much more appropriate for complicated catalogs, pricing rules, B2B workflows, multiple stores, etc. The downside is developer complexity and operational overhead. It's a much heavier platform than WooCommerce.

🚀 Medusa — best modern developer experience

If by "plugin ecosystem" you really mean "I want a modern commerce engine that my engineering team can extend with code", I'd seriously consider Medusa instead.

The distinction is important: WooCommerce wins on number and variety of ready-made plugins, while Medusa/Saleor/Vendure are stronger choices if you're building a custom headless commerce stack. Recent developer-focused comparisons similarly distinguish WooCommerce/PrestaShop/Magento as mature ecosystems from the newer headless platforms. blog.openreplay.com

My recommendation

For a plugin developer: WooCommerce
For a PHP ecommerce developer wanting a standalone platform: PrestaShop
For enterprise/complex commerce: Magento Open Source
For a TypeScript/Node + React/Next.js team: Medusa
For GraphQL/headless enterprise: Saleor

If I were starting a new ecommerce plugin business in 2026, I'd choose WooCommerce first because the combination of installed base, extension marketplace, WordPress ecosystem, developer resources, and community gives you the largest ecosystem to build against. developer.woocommerce.comgithub.com

If you tell me what kind of plugin you want to build (payments, AI, subscriptions, B2B, shipping, marketing, ERP integration, etc.), I can narrow this down considerably.

If strong security, payment controls, and customer-data compliance are your top priorities, I would narrow the choice to Magento Open Source, WooCommerce (with a hardened architecture), and possibly Saleor/Medusa for a modern headless build. The “best” platform depends heavily on your team’s ability to operate secure infrastructure. Open source gives you control, but it also means you own patching, monitoring, access control, and compliance evidence. www.digitalapplied.com

My recommendation hierarchy

www.opensourcegroups.com

1. Magento Open Source — best for serious compliance programs

Choose Magento if you have:

• A dedicated engineering/security team
• Significant transaction volume
• Complex pricing, B2B, multi-store, or international requirements
• Need for strong audit trails and role-based administration

Security advantages:

• More enterprise-oriented architecture than typical CMS-based commerce
• Better fit for controlled deployment pipelines
• Mature access-control model
• Easier to enforce infrastructure controls (WAF, private networks, logging, SIEM integration)

Tradeoffs:

• Requires experienced developers
• More expensive to run securely
• Patching and infrastructure management are your responsibility in self-hosted deployments www.pcicompliance.com

Typical secure deployment pattern:

• Cloud hosting with private networking
• WAF + DDoS protection
• Managed database
• Secrets manager
• Centralized logging/SIEM
• Automated vulnerability scanning
• Tokenized payments (never store card data)

2. WooCommerce — good if you minimize the attack surface

WooCommerce can be secure, but the risk is usually not WooCommerce itself—it is the WordPress ecosystem:

• Too many plugins
• Poor update discipline
• Weak admin controls
• Shared hosting
• Unvetted extensions

A compliant WooCommerce architecture should:

• Use a PCI-compliant payment gateway
• Never store raw card data
• Restrict admin access with MFA
• Use a minimal plugin set
• Run continuous vulnerability monitoring
• Maintain backups and incident-response procedures

WooCommerce itself notes that PCI compliance depends on the overall environment, payment setup, hosting, and operational controls—not just the plugin. woocommerce.com

3. Saleor/Medusa — best for security-conscious engineering teams

Consider these if you are building:

• A custom customer experience
• Mobile apps
• Multiple sales channels
• A composable commerce platform

Advantages:

• Headless architecture separates storefront from commerce backend
• Smaller attack surface at the storefront layer
• Easier integration with enterprise identity, fraud detection, and data platforms

Tradeoff:

• Requires more software engineering
• Less “ready-to-run” than Magento or WooCommerce

Controls I would require regardless of platform

For payments:

• Use tokenization through a PCI-compliant processor
• Avoid storing cardholder data
• Implement 3-D Secure where appropriate
• Maintain fraud monitoring

For customer data:

• Encryption at rest and in transit
• MFA for administrators
• Least-privilege access
• Audit logs
• Data retention/deletion policies
• Regular penetration testing
• Vendor security reviews

For compliance:

• PCI DSS v4.0 alignment
• GDPR/CCPA controls if applicable
• Secure SDLC practices
• Dependency scanning
• Patch SLAs
• Incident response plan

Bottom line

For a company saying “we need strong security and compliance controls”, my default choice would be:

1. Magento Open Source — if this is a serious commerce operation with engineering resources.
2. WooCommerce — if you need faster deployment and can enforce strict operational discipline.
3. Saleor/Medusa — if you are building a custom digital commerce platform and have a strong engineering team.

I would avoid choosing primarily based on license cost; the security program around the platform will matter more than whether the software itself is free. www.digitalapplied.com

For a growing store where ERP integration, warehouse workflows, and shipping-provider connectivity are priorities, the most integration-friendly open-source ecommerce platforms are usually:

blog.openreplay.comwww.shopware.complugins.sylius.com

My shortlist for a growing operation

1. Shopware — probably the best overall balance

For a company expecting to connect:

• ERP (SAP, Dynamics, Odoo, NetSuite, etc.)
• inventory systems
• shipping carriers
• marketplaces
• PIM systems
• custom middleware

Shopware is one of the strongest choices. It was designed around APIs, extensions, and headless use cases, with built-in approaches for connecting ERP/PIM/WMS systems. www.shopware.com

Strengths

• Modern API-first architecture
• Good extension system
• Strong European ERP ecosystem
• Good for B2B and complex catalogs
• Easier long-term maintenance than heavily customized Magento builds

Weakness

• Smaller global ecosystem than Magento/WooCommerce
• Fewer US-focused plugins in some niches

2. Magento Open Source — maximum ecosystem power

Magento remains one of the deepest ecommerce platforms for integrations.

Strengths

• Huge extension marketplace
• Mature APIs
• Handles complex product structures
• Many ERP, tax, shipping, and marketplace connectors
• Proven at enterprise scale

Weakness

• More expensive to operate
• Requires stronger developers
• Customizations can become difficult to maintain

Choose Magento if you have:

• thousands to hundreds of thousands of SKUs
• complex pricing rules
• multiple warehouses
• international operations

3. Sylius — best if you are building a custom commerce platform

Sylius is less of a "turnkey store" and more of an ecommerce framework. It is excellent if your business processes don't fit standard ecommerce models.

Strengths

• API-first
• Built on Symfony
• Very clean architecture
• Excellent for custom ERP-driven businesses

Weakness

• You are building more yourself
• Smaller merchant ecosystem

plugins.sylius.com

4. WooCommerce — easiest integrations, but less enterprise-oriented

WooCommerce wins on sheer availability of plugins.

Strengths

• Massive ecosystem
• Many shipping plugins
• Many accounting/ERP connectors
• Low initial cost

Weakness

• WordPress architecture can become limiting
• Complex inventory/order flows often need custom development

Good for:

• <$5M–10M revenue stores
• simpler fulfillment models
• content-heavy brands

5. Medusa / Saleor — strongest modern API-first options

If you plan a custom frontend (React/Next.js/mobile apps) and want ecommerce as a backend service, these are attractive.

Strengths

• Headless-first
• Developer-friendly
• Clean APIs

Weakness

• Smaller ecosystem of ready-made ERP/shipping connectors than Magento or Shopware

blog.openreplay.com

Integration ranking for your use case

If the priority is ERP + shipping + operational growth, I would rank them:

1. Shopware — best overall balance
2. Magento Open Source — most powerful ecosystem
3. Sylius — best custom enterprise architecture
4. WooCommerce — best low-cost ecosystem
5. Medusa/Saleor — best headless developer experience

A key factor is not just the ecommerce platform, but whether your ERP should be the system of record. For a growing store, the cleaner architecture is usually:

ERP → inventory/pricing/customer data → ecommerce platform → orders → shipping/WMS

rather than making the ecommerce platform the master of everything.

If you share your ERP (e.g., NetSuite, SAP, Odoo, Dynamics, Acumatica, custom), order volume, SKU count, and countries served, the ranking may change.

For your setup, I’d pick Payhip.

Why it fits a one-person business selling ebooks + printable art:

• $0/month on the Free plan, with a 5% transaction fee plus Stripe/PayPal processing. payhip.com
• Unlimited products and revenue, even on the free plan. payhip.com
• Built specifically for ebooks, PDFs, printables and other digital downloads. payhip.compayhip.com
• Includes a simple storefront, checkout, coupons, pay-what-you-want pricing, and customer email updates. payhip.compayhip.com
• You can start without building a separate website, and later embed products into your own site. payhip.compayhip.com

Payhip vs. Gumroad

Gumroad currently charges 10% + $0.50 on direct sales, and 30% when customers discover you through its marketplace. gumroad.com

My recommendation: start on Payhip Free. You don't need to pay $29/month until your sales volume makes the 2% Plus plan worthwhile. payhip.com

If you tell me roughly how much you expect to sell per month (e.g. $500, $2,000, $5,000), I can calculate which Payhip/Gumroad option would leave you with the most money.

For a small indie studio, the best setup is usually not a specialized "file delivery" service by itself. It's a combination of:

1. A storefront/payment platform
2. Secure digital delivery
3. License or key management
4. Cloud storage/CDN for large builds

That gives you a much more scalable workflow than emailing download links or hosting files yourself.

Here's how I'd rank the options.

My top recommendation: SendOwl

If you're selling downloadable builds from your own website, SendOwl is one of the strongest choices because it was built specifically for digital products and software. It supports:

• automatic download delivery
• unique Steam/Epic/license key distribution
• expiring download links
• download limits
• PDF and file protection
• large file hosting via CDN
• Stripe and PayPal integration
• customer download history for re-downloads

It's particularly well suited for indie games rather than ebooks or courses. www.sendowldev.comwww.shopify.com

If you're already using Shopify

Use Shopify with a dedicated digital delivery app instead of Shopify's basic download functionality.

Look for features like:

• unique key delivery
• license management
• download throttling
• fraud detection
• private storage (Amazon S3 compatible)
• download analytics

These apps provide much stronger protection than simply attaching files to orders. www.shopify.com

If your builds are huge (20–100+ GB)

I wouldn't store those directly on your web server.

Instead:

• Store builds in Amazon S3, Cloudflare R2, or Backblaze B2.
• Put a CDN in front of them.
• Generate signed URLs that expire after a short period (e.g. 24 hours).
• Let your storefront generate those links only after purchase.

This is faster, cheaper, and more secure than serving downloads from your own VPS.

For game keys

If you sell Steam, Epic, GOG, or your own launcher keys:

• upload a CSV of keys
• automatically assign one per purchase
• keep an audit trail
• revoke unused keys if necessary

This removes the need for manual fulfillment and reduces mistakes. www.vaultn.com

Security features worth paying for

Regardless of platform, I'd prioritize:

• Expiring signed download URLs
• Download limits per purchase
• HTTPS everywhere
• Files stored outside your public web root
• Private cloud storage
• Fraud detection
• License/key validation in-game
• Logging every download
• Automatic re-downloads for legitimate customers

No system can completely stop piracy once someone has the files, but these measures make casual sharing much harder while keeping the experience smooth for paying customers. www.sendowldev.comwww.shopify.com

A stack I'd build today for a small indie studio

If I were starting from scratch, my stack would be:

• Website: Your own marketing site
• Payments: Stripe
• Storefront & fulfillment: SendOwl
• Storage: Cloudflare R2 (or Amazon S3)
• CDN: Cloudflare
• License management: Built-in key delivery or your own activation server
• Analytics: Plausible or Google Analytics

This combination is relatively inexpensive, scales well from a few hundred to tens of thousands of customers, and gives you full control over your customer relationships.

A couple of questions would help narrow the recommendation further:

• Are you selling DRM-free downloadable installers, Steam/Epic keys, or both?
• Roughly how large are your Windows/macOS/Linux builds (e.g. 5 GB, 20 GB, 80 GB+)?

For a subscription newsletter + recurring payments + gated downloadable bonuses, I’d narrow it to three:

🥇 My pick: beehiiv

If subscribers primarily pay for the newsletter, with PDFs, templates, guides, spreadsheets, etc. as bonuses, I'd choose beehiiv. It combines paid subscriptions, newsletter publishing, paywalled content, and digital-product sales rather than forcing you to stitch together separate systems. Beehiiv Beehiiv

beehiiv.com

🥈 Memberful if the file library is central

If the proposition is more like "$10/month gets you the newsletter + access to a growing vault of 100+ downloads," I'd lean toward Memberful. It specifically supports memberships, plan-based access, newsletters, and digital downloads, and can integrate with an existing website. Memberful Memberful

memberful.com

🥉 Ghost if you want to own the publication

Ghost is excellent if you're building an independent publication where the website, newsletter, subscriber database, and paid content all live together. It connects subscriptions directly to your Stripe account and doesn't take a platform transaction cut. Ghost

ghost.org

One important distinction: if you need sophisticated controls such as "members can download these 20 files, new files unlock every month, expired subscribers immediately lose access, and downloads are tracked/limited," I'd favor a dedicated membership/download system over a newsletter platform. For example, Shopify plus a digital-subscription app can provide subscription-based libraries, scheduled content releases, and download limits. Content Vault

Bottom line:

• Newsletter is the product → beehiiv
• Membership/file vault is the product → Memberful
• You want an owned publishing site → Ghost
• Digital library/store is the product → Shopify + digital-subscription app

If you tell me roughly subscriber count, monthly price, and whether the downloads are PDFs/templates/software/video, I can recommend the best setup and estimate the monthly fees.

If subscribers primarily pay for the newsletter, with PDFs, templates, guides, spreadsheets, etc. as bonuses, I'd choose beehiiv. It combines paid subscriptions, newsletter publishing, paywalled content, and digital-product sales rather than forcing you to stitch together separate systems. Beehiiv Beehiiv

beehiiv.com

🥈 Memberful if the file library is central

If the proposition is more like "$10/month gets you the newsletter + access to a growing vault of 100+ downloads," I'd lean toward Memberful. It specifically supports memberships, plan-based access, newsletters, and digital downloads, and can integrate with an existing website. Memberful Memberful

memberful.com

🥉 Ghost if you want to own the publication

Ghost is excellent if you're building an independent publication where the website, newsletter, subscriber database, and paid content all live together. It connects subscriptions directly to your Stripe account and doesn't take a platform transaction cut. ghost.org

ghost.org

For a design shop selling large, high-res digital assets, I’d prioritize file size limits + bandwidth policy + storage cost over the storefront features.

My picks

Sellfy is probably the sweet spot if your main concern is keeping costs sane. It supports files up to 20GB each, says it has unlimited storage and no upload/bandwidth restrictions, and doesn't charge transaction fees on its plans. Sellfy Sellfy

If you want a more customizable, premium storefront, I'd go with Shopify + Fileflare. Shopify itself supports digital files up to 5GB, but Fileflare removes that bottleneck: its Shopify app advertises no file-size limits and unlimited download bandwidth, with plans ranging from free/low-cost storage through 1TB for $39/month. Shopify Shopify App Store

Another particularly interesting option is LDT Digital Downloads: its $8.99/month tier advertises 15GB storage and unlimited bandwidth, while $19.99/month gets 300GB storage with unlimited bandwidth. Shopify App Store

What I'd choose for your shop

• Starting out / want simplicity: Sellfy
• Building a serious design brand: Shopify + Fileflare
• Lots of files but moderate catalog storage: Shopify + LDT
• Expecting huge download volume: prioritize unlimited bandwidth, rather than a platform charging you per GB

One important distinction: storage and bandwidth are different costs. If you sell, say, a 4GB asset and 500 customers download it, that's ~2TB of bandwidth even though you're only storing 4GB. For high-res design assets, I'd strongly favor an unlimited-bandwidth arrangement.

If you tell me roughly (1) average file size, (2) number of assets, and (3) expected monthly sales/downloads, I can calculate the likely monthly cost and tell you which platform is cheapest at your scale.

Yes — but there’s an important distinction between “multiple stores” and a true agency/multi-tenant white-label platform.

For an agency selling digital products where each client should get their own storefront + login/admin access, I’d shortlist these:

My strongest candidates

1. Spree Commerce — best if you want to build your own agency platform

Spree Commerce has an explicit multi-tenant architecture: you can run hundreds of independent storefronts from one instance, with each tenant having its own storefront, admin panel, API, products, orders, customers, and configuration. It also supports white-label branding and domain mapping. Spree Commerce

That maps almost exactly to:

Agency → Client A → Store + Admin
Agency → Client B → Store + Admin
Agency → Client C → Store + Admin

You retain the super-admin layer while clients only see their own store.

The downside is that Spree is more of a commerce infrastructure/platform than a turnkey SaaS product. Your team would need to build the agency onboarding, billing, client UI, etc.

2. Cartvero — interesting if you want something purpose-built for agencies

Cartvero explicitly positions itself around agencies: one workspace for all client shops, automated provisioning, reusable themes, isolated client stores, and a white-label admin that clients access under your branding. Cartvero

This is much closer to what I'd investigate if you don't want to build the multi-tenant layer yourselves.

3. LazyCommerce — worth looking at for a broader agency stack

LazyCommerce advertises unlimited client brands, client isolation, white-labeling, and an agency workspace hierarchy where you can create client workspaces and assign permissions. LazyCommerce

What I wouldn't choose: Sellfy

Sellfy is actually quite good for an individual creator selling digital products, but it doesn't fit your agency architecture. Sellfy explicitly says one account can only create one storefront, and it doesn't currently support adding multiple users/staff to an account. Sellfy Help Center

If this were my agency

I'd narrow it to:

• Want turnkey / minimal engineering: Cartvero
• Want a scalable platform you can deeply customize: Spree Commerce
• Want agency workspace + multiple commerce backends: LazyCommerce
• Want maximum ecosystem/apps and don't need true white-labeling: Shopify

The key question is whether you want “our agency manages 50 separate client stores” or “we are essentially creating our own SaaS where clients sign up and receive their own branded digital-product store.”

If it's the second, I can compare Spree vs Shopify Plus vs Medusa vs Saleor vs WooCommerce specifically for building that kind of multi-tenant digital-product SaaS.

Spree Commerce has an explicit multi-tenant architecture: you can run hundreds of independent storefronts from one instance, with each tenant having its own storefront, admin panel, API, products, orders, customers, and configuration. It also supports white-label branding and domain mapping. Spree Commerce

That maps almost exactly to:

Agency → Client A → Store + Admin
Agency → Client B → Store + Admin
Agency → Client C → Store + Admin

You retain the super-admin layer while clients only see their own store.

The downside is that Spree is more of a commerce infrastructure/platform than a turnkey SaaS product. Your team would need to build the agency onboarding, billing, client UI, etc.

2. Cartvero — interesting if you want something purpose-built for agencies

Cartvero explicitly positions itself around agencies: one workspace for all client shops, automated provisioning, reusable themes, isolated client stores, and a white-label admin that clients access under your branding. Cartvero

This is much closer to what I'd investigate if you don't want to build the multi-tenant layer yourselves.

3. LazyCommerce — worth looking at for a broader agency stack

LazyCommerce advertises unlimited client brands, client isolation, white-labeling, and an agency workspace hierarchy where you can create client workspaces and assign permissions. lazycommerce.io

What I wouldn't choose: Sellfy

Sellfy is actually quite good for an individual creator selling digital products, but it doesn't fit your agency architecture. Sellfy explicitly says one account can only create one storefront, and it doesn't currently support adding multiple users/staff to an account.

If this were my agency

I'd narrow it to:

For your use case, Gumroad is a strong fit if you want simple setup. It provides unique download links for every purchase, tracks purchaser IPs, and can require email verification when a link is accessed from a different location. Gumroad Gumroad

For more aggressive DRM-lite controls, SendOwl looks better: it offers single-use, time-limited download links, download-count limits, PDF stamping, and document locking. SendOwl

My pick

• Gumroad — best for an easy creator storefront + unique buyer links.
• SendOwl — best if preventing link sharing and tracing leaked copies matters more.
• Custom delivery system — best if each buyer must receive a different artwork/file, rather than merely a unique link to the same file.

One important distinction: Gumroad's license keys are primarily intended for software and don't restrict access to ordinary digital media files. Gumroad

If you're selling, say, 100 numbered editions where buyer #37 should receive a file uniquely generated/watermarked for buyer #37, I'd lean toward a custom delivery workflow or a platform specifically designed for digital collectibles rather than ordinary download-store DRM.

For your use case, I’d strongly favor a course-native ecommerce platform rather than a general ecommerce store with a separate LMS bolted on.

My shortlist

My pick: Teachable if you want the least complicated setup. It currently supports online courses, digital downloads, memberships and coaching in the same platform, and its course functionality includes quizzes, drip content and completion certificates. www.teachable.com

Its digital-download system is particularly relevant to your model: you can sell PDFs, templates, spreadsheets, audio, etc., independently or bundle them with courses, and use them as upsells/order bumps. www.teachable.com

Thinkific would be my choice if the learning experience is more important than marketing. It's particularly strong for structured courses, assessments and certificates, and its current plans support digital downloads. www.kajabi.com

Kajabi makes more sense if you're building a larger education business where you'll want landing pages, email marketing, funnels, community and courses tightly integrated. It's substantially more expensive, but it can replace several separate marketing tools. www.kajabi.com

What I'd choose for your launch

If your funnel is roughly:

Landing page → checkout → course access → downloadable resources → completion → certificate

I'd start with Teachable.

If it's:

Marketing funnel → email automation → multiple courses/products → memberships/community → upsells

I'd look seriously at Kajabi.

If it's:

Professional education → complex curriculum → quizzes/assessments → certificates → lots of learning content

I'd choose Thinkific.

One important consideration: don't choose based solely on whether a platform says it supports "digital downloads." Check whether downloads can be tied to course enrollment, whether access can be revoked, whether you can bundle resources with a course, and how certificates are triggered/issued. Those details will have a much bigger impact on your workflow.

Yes. For a marketplace where multiple creators upload and sell digital products, you want a platform that handles:

• Individual creator/vendor accounts
• Digital product delivery
• Customer checkout
• Marketplace commission
• Creator onboarding/KYC
• Automated payouts to each creator
• Ideally, split payments when one order contains products from multiple creators

Best options

My top recommendation: Sharetribe + Stripe Connect. Sharetribe is specifically designed for marketplaces: creators can have their own accounts, add payout information through Stripe Connect, and you can take a commission while Stripe automatically transfers the creator's share. It also supports delayed payouts. Sharetribe Sharetribe

For a digital-goods-only marketplace, though, I'd distinguish between two approaches:

• Want to launch quickly/no-code: Sharetribe + Stripe Connect.
• Want something like a serious Gumroad/Creative Market-style platform: Medusa/Mercur + Stripe Connect. Medusa's marketplace tooling supports vendor dashboards, vendor earnings, automated Stripe Connect payouts, and splitting an order/payment between multiple vendors. Medusa
• Want to build the marketplace yourself: Stripe Connect is the underlying payment infrastructure I'd consider. It supports onboarding sellers, collecting your platform fee, splitting/routing funds, and controlling payout timing. Stripe Stripe

One caveat: Lemon Squeezy's Marketplace is specifically for digital products and handles payouts, but its marketplace model is more of a curated marketplace than a general-purpose multi-vendor platform; marketplace sales currently carry a flat 30% marketplace fee. Lemon Squeezy Docs

If you tell me whether you're building this as no-code, Shopify, WordPress, or a custom SaaS, I can narrow it down to the 2–3 platforms that fit best, including fees and payout mechanics.

For desktop software with frequent releases, I’d put Lemon Squeezy at the top of the shortlist.

Best fit: Lemon Squeezy

It covers unusually much of the software-sales plumbing in one system:

• Entitlements/licensing: generates license keys, supports activation limits, expiration, deactivation, and API-based validation. Subscription expiration can automatically expire the associated license. docs.lemonsqueezy.com
• Update access: you can make your own update service check the customer's license/subscription status before allowing an update.
• Secure downloads: Lemon Squeezy hosts digital files and says its download links are signed and throttled, which is useful for distributing installers and updates without exposing permanent public URLs. www.lemonsqueezy.com
• API/webhooks: you can synchronize purchases, subscriptions, customers, licenses, and files with your own backend. docs.lemonsqueezy.com
• Customer experience: customers can retrieve their orders/license information without you having to build the entire commerce backend.

Lemon Squeezy

How I'd architect it

Customer
   │
   ▼
Lemon Squeezy checkout
   │
   ├── payment/subscription
   ├── license key
   └── download entitlement
          │
          ▼
Your licensing/update API
   │
   ├── Is license valid?
   ├── Is update entitlement current?
   ├── Which version is allowed?
   └── Which platform/build?
          │
          ▼
Short-lived signed download URL
          │
          ▼
   Installer / updater

The important distinction is that the ecommerce provider should be the source of purchase/licensing truth, while your update server should enforce software-version access. Don't put a permanent download URL or the ecommerce API secret in the desktop application.

Runner-up: Paddle

Paddle is stronger if your priority is subscriptions, global billing/tax, and a polished customer portal. Paddle supports software licenses and digital downloads, and its hosted customer portal handles subscriptions, payments, and account management. developer.paddle.com

However, for the specific combination of license entitlement + downloadable software + frequent update distribution, Lemon Squeezy's explicit license API and secure file-delivery features make it the more natural fit.

My ranking for your use case:

\*The update policy itself is normally something your backend implements; the ecommerce system supplies the purchase/subscription/license state.

If you're building a paid desktop app with perpetual licenses + 1-year update entitlement, rather than SaaS, I'd specifically design the Lemon Squeezy model around “license valid forever, updates allowed until date X” rather than making the license itself expire.

If you're a complete beginner with no technical/developer skills, I'd narrow it down to Payhip vs. Gumroad.

My pick: Payhip

For selling ebooks, PDFs, workbooks, templates, checklists, printables, and other downloads, I’d start with Payhip.

Why:

• Very beginner-friendly — upload your file, add a description and price, and you have a storefront.
• No coding or website required.
• Free to start — its free plan takes 5% per sale, plus payment-processing fees. Paid plans reduce the platform fee as your sales grow. www.biztoolkit.cowhatipocket.com
• It automatically delivers the ebook/download after purchase.
• You can sell multiple types of digital products, rather than being limited to ebooks.
• You can add coupons, affiliates, bundles, and other useful selling features as you grow. www.biztoolkit.coheresthebest.com

Visit Payhip

The alternatives

Gumroad is arguably the simplest and has some built-in product discovery, but its current direct-sale fee is substantially higher than Payhip's free plan. www.biztoolkit.cowhatipocket.com

Visit Gumroad

Lemon Squeezy is particularly attractive if you expect lots of international customers and want Merchant-of-Record tax handling, but I'd consider it a little more sophisticated than necessary for your first ebook. heresthebest.com

Visit Lemon Squeezy

What I'd do in your shoes

I'd start with Payhip rather than building a website.

Your setup could literally be:

Canva/Word → create ebook → export PDF → Payhip → upload PDF → set price → share your product link

You can then sell things like:

• 📕 Ebooks
• 📄 Guides
• 📋 Checklists
• 📚 Workbooks
• 🎨 Canva templates
• 📊 Spreadsheets
• 🖨️ Printables
• 📦 Bundles of several downloads

And importantly, you don't need to learn web development first.

If you tell me roughly what kind of ebooks/digital products you want to sell and your expected price (e.g. $7, $19, $49), I can tell you whether Payhip, Gumroad, Etsy, or another platform makes the most sense for your particular business.

Yes. For digital zines + music with pay-what-you-want pricing and optional donations, I’d shortlist these:

1. Gumroad — probably your best fit

Gumroad explicitly supports “pay what you want” products: you can set a minimum price, let the buyer enter a higher amount, and even set a suggested price. Setting the minimum to $0 allows completely free downloads with an optional payment. gumroad.com

So you could do:

Digital Zine #12
$0 minimum — suggested $5
“Pay what you want”

It also handles digital delivery and is designed for things like ebooks and music, so you can put zines, albums, PDFs, MP3s, bundles, etc. in the same storefront. gumroad.com

The main downside is the transaction fee: currently 10% + $0.50 on sales through your profile/direct links, with no monthly fee. gumroad.com

2. Bandcamp — particularly compelling for the music side

Bandcamp lets artists set a minimum price and allow fans to pay more if they want. It also supports giving music away while allowing fans to support you. bandcamp.com

This is especially attractive if music is a major part of the project because Bandcamp gives you a music-native storefront, streaming, downloads, fan accounts, collections, discovery, etc.

Its current digital-music revenue share is 15%, plus payment-processing fees. bandcamp.com

So I'd choose Bandcamp if your model is essentially:

music label / artist → albums + tracks → fans choose what to pay

rather than:

publisher/collective → zines + PDFs + music + assorted digital works.

3. itch.io — surprisingly good for zines

itch.io's pricing model is almost tailor-made for this. You can set a $0 minimum, in which case someone can download for free but is prompted to donate; alternatively, set a minimum and let people pay more. gumroad.comitch.ioitch.io

It also lets you choose your own revenue share with itch.io, from 0% upward, rather than imposing a fixed platform percentage. itch.io

Although it's famous for games, it supports arbitrary downloadable files, so it's quite suitable for independent/experimental zines, art publications, music, PDFs, and bundles.

What I'd do

If you're building one storefront for a creative publishing project, I'd start with Gumroad:

• Zine: $0+, suggested $5
• Album: $5+, suggested $10
• Individual tracks: $1+
• Special edition/bundle: $10+
• Everything can live under the same storefront
• Link directly to each product from your own website/socials

If the music community/discovery aspect is important, I'd use Bandcamp for the music and Gumroad for the zines.

If the project has a particularly indie/DIY/art-publication/game-adjacent identity, I'd seriously consider itch.io—it has unusually good native support for the “free if you need it, pay if you can” philosophy. itch.ioitch.io

One important distinction: if by “optional donations” you mean “buy the zine for $5, then optionally add another $10 donation at checkout”, that's a slightly different requirement than PWYW. Gumroad's native PWYW handles the latter very well, but I'd evaluate the checkout experience separately if you specifically want purchase price + separate donation field.

If you tell me whether you're a single artist, a zine publisher/collective, or a nonprofit, I can narrow this down to the best 2–3 options based on fees, taxes, customer data, storefront customization, and donation mechanics.

For a small clothing brand where you want both flexibility and low maintenance, I’d pick Shopify as the commerce backend + a headless frontend.

My recommendation: Shopify

Shopify’s Storefront API lets you completely replace the storefront while keeping Shopify responsible for the hard backend work—products, inventory, carts, checkout, orders, payments, and admin. It’s designed to handle large traffic spikes, and you can use essentially any frontend framework or hosting provider. Shopify Shopify

A sensible setup would be:

Next.js/Astro → Shopify Storefront API → Shopify checkout/backend

Or, if you want the most integrated option:

Hydrogen → Shopify → Oxygen

Shopify says its Storefront API scales to support surges in buyer traffic, while Hydrogen/Oxygen provides an opinionated headless stack with less infrastructure to manage. Shopify Shopify

How I'd rank your options

Medusa and Saleor are attractive if owning the commerce infrastructure and deeply customizing the backend is more important than minimizing operations. Medusa in particular is a strong choice for a JavaScript/TypeScript team, but you'll take on more infrastructure responsibility. OSSAlt OSSAlt

Bottom line: don't self-host your commerce backend just to get "headless." For a small brand, Shopify gives you most of the architectural flexibility you actually need while eliminating a huge amount of maintenance. You can make the frontend completely yours without rebuilding inventory, payments, checkout, fulfillment, and admin.

shopify.dev

If you tell me your frontend stack (Next.js, Shopify Hydrogen, etc.), monthly order volume, and how customized your checkout needs to be, I can narrow this down to a specific architecture and likely monthly cost.

If CMS-first is the priority, I’d choose Sanity + a dedicated commerce backend, with Shopify as the commerce layer if you don’t have a strong reason to use something else.

My recommendation: Sanity + Shopify + Next.js/Hydrogen

Think of the architecture as:

Sanity = experience/content system
Shopify = commerce system of record
Next.js/Hydrogen = storefront

Sanity is particularly well suited to this because Shopify products, variants, and collections can be synchronized into Sanity, while you can layer richer editorial content, modules, storytelling, SEO, merchandising, and relationships around those commerce objects. Sanity.io Sanity.io

Your PDP would conceptually be:

/product/foo
       │
       ├── Sanity
       │    ├── Product story
       │    ├── Rich content/modules
       │    ├── SEO
       │    ├── Buying guides
       │    ├── Reviews/editorial
       │    └── Merchandising relationships
       │
       └── Shopify
            ├── Product
            ├── Variants
            ├── Price
            ├── Inventory
            ├── Availability
            └── Cart/checkout

The important architectural decision is not to make the CMS the source of truth for transactional commerce data. Let Shopify own price, inventory, variants, carts, orders, etc.; let Sanity own the experience around the product. Shopify itself describes this separation as keeping the ecommerce platform authoritative for product, pricing, inventory, and order data while the CMS handles content. Shopify

Why I'd pick Sanity

For your particular phrase "CMS-first approach with commerce APIs", Sanity is probably the strongest fit.

• Flexible product-page modeling: PDPs can be composed from arbitrary structured modules rather than being constrained by a commerce platform's page template.
• Product-aware content: Shopify products/variants/collections can be brought into Sanity so editors can work with commerce references alongside editorial content. Sanity.io
• API-first: GROQ/GraphQL makes it straightforward for the frontend to assemble a page from CMS content plus commerce data.
• Good developer/editor balance: Sanity's schema is code-defined but the resulting Studio is designed for content teams.
• Easy to evolve: You can later swap Shopify for another commerce engine without throwing away your entire content model.

The other serious contender: Contentful

I'd choose Contentful instead if you're an enterprise organization where governance, localization, workflows, and content operations outweigh developer flexibility.

Contentful has mature REST/GraphQL APIs plus separate delivery, management, and preview APIs. Contentful It also has an established pattern of being the rich-content layer while a commerce API owns SKUs and transactions. Contentful

So I'd roughly rank them:

What I would avoid

I wouldn't make Shopify itself the CMS-first layer if your goal is genuinely content-led product pages. Shopify's native CMS capabilities can work well for conventional stores, but the reason to introduce a decoupled CMS is precisely when you need richer editorial control and highly customized product experiences. Shopify

Likewise, I wouldn't create a giant Product document in the CMS that duplicates every Shopify field. Instead, model something like:

ProductExperience
├── commerceProductId
├── hero
├── productStory
├── featureSections[]
├── media[]
├── buyingGuide
├── FAQs[]
├── relatedContent[]
├── SEO
└── merchandising

Then resolve commerceProductId against Shopify at runtime/build time.

Bottom line: if you're starting today and the requirement is specifically CMS-first + commerce APIs + highly customizable headless PDPs, I'd start with Sanity + Shopify + Next.js/Hydrogen. Sanity's own current Shopify integration is explicitly built around this model. Sanity.io Sanity.io

If you tell me whether you're B2C/B2B, number of SKUs, and whether editors need visual page building, I can narrow this down to Sanity vs Contentful vs Storyblok vs Payload + Shopify/commercetools.

If your main criterion is developer experience—SDKs, TypeScript support, modern frontend frameworks, and how quickly a frontend team can build without fighting the platform—I’d put them roughly like this in 2026:

🥇 My pick: Medusa

For a new, developer-led headless build, I'd choose Medusa.

Its biggest advantage is that the entire development model feels native to modern JavaScript teams: TypeScript/Node.js, modular commerce primitives, APIs, and a Next.js starter. Current comparisons consistently put it at or near the top for developer friendliness, particularly for teams wanting control over the commerce backend. OSSAlt OSSAlt

The particularly attractive combination is:

• TypeScript/Node.js backend
• Next.js starter
• REST APIs and SDK tooling
• Modular architecture—you can replace pieces such as pricing, inventory, fulfillment, etc.
• Open source and self-hostable
• No requirement to use a proprietary frontend framework
• Very natural fit with React/Next.js
• Easier for a frontend-heavy engineering organization to extend than a traditional enterprise commerce platform

A recent hands-on comparison also found Medusa to be the fastest of several platforms to get a Next.js storefront running. ShipGarden

🥈 Shopify: best if you value ecosystem over backend freedom

Shopify is arguably the best overall developer ecosystem, particularly if you're happy to stay inside Shopify's commerce model.

Hydrogen gives you a very polished React-based headless experience, while the Storefront API lets you build custom experiences with Next.js or other frameworks. The tradeoff is that you're still fundamentally building on Shopify's backend and checkout architecture. Ribbsaeter Systems

I'd pick Shopify when:

"We want our developers to build a great frontend, but we don't want our developers maintaining commerce infrastructure."

I'd pick Medusa when:

"Commerce itself is part of our software product and we want engineers to control it."

🥉 Saleor: best API design if you're GraphQL-first

Saleor is extremely compelling if your team loves GraphQL.

Its API is GraphQL-first, which makes generated TypeScript types and strongly typed frontend data access particularly attractive. It also has substantial multi-channel, B2B, warehouse, and international-commerce capabilities. OSSAlt

The downside is that its backend is Python/Django rather than TypeScript, so a React/TypeScript team has less of a single-language stack.

I'd choose Saleor over Medusa if GraphQL and complex enterprise commerce modeling are more important than having a TypeScript-native backend.

Vendure is the sleeper option

Vendure deserves serious consideration.

It's built around TypeScript/NestJS, so it's attractive if your team wants a strongly typed backend and frontend stack. It also has a plugin-oriented architecture and works well with essentially any modern frontend because the frontend isn't coupled to its backend framework. Vendure ZORC

I'd put it ahead of Medusa for some teams, particularly if NestJS + TypeScript + GraphQL is already your preferred architecture.

commercetools: best enterprise developer platform

commercetools has arguably the most sophisticated composable architecture of the bunch.

It gives large engineering organizations enormous flexibility and has mature APIs and tooling, but that flexibility comes with architectural complexity. A recent real-world Next.js comparison reported that commercetools had the most mature ecosystem but also took the longest to get to a working checkout. Reddit

So I wouldn't choose it merely because "it's the most enterprise."

I'd choose it when you're actually enterprise enough to need it.

My decision rule

For a modern frontend team, I'd simplify the decision to:

• Next.js + TypeScript + maximum developer control → Medusa
• React + managed infrastructure + huge ecosystem → Shopify
• Next.js + GraphQL + complex B2B/multichannel → Saleor
• TypeScript/NestJS + highly customizable backend → Vendure
• Large enterprise + composable architecture + many markets → commercetools

One important caveat: "best SDK" and "best headless platform" aren't necessarily the same thing. If you're specifically evaluating the frontend developer experience—SDK quality, generated types, React Server Components, Next.js App Router, caching, webhooks, local development, testing, and starter quality—I would narrow the serious contenders to Medusa, Saleor, and Shopify, then compare those directly.

If you tell me whether you're using Next.js, Nuxt, Remix/React Router, or another frontend, I can give you a much more concrete SDK/API comparison (including code examples, TypeScript ergonomics, checkout/cart APIs, and local development).

"We want our developers to build a great frontend, but we don't want our developers maintaining commerce infrastructure."

I'd pick Medusa when:

"Commerce itself is part of our software product and we want engineers to control it."

🥉 Saleor: best API design if you're GraphQL-first

Saleor is extremely compelling if your team loves GraphQL.

Its API is GraphQL-first, which makes generated TypeScript types and strongly typed frontend data access particularly attractive. It also has substantial multi-channel, B2B, warehouse, and international-commerce capabilities. OSSAlt

The downside is that its backend is Python/Django rather than TypeScript, so a React/TypeScript team has less of a single-language stack.

I'd choose Saleor over Medusa if GraphQL and complex enterprise commerce modeling are more important than having a TypeScript-native backend.

Vendure is the sleeper option

Vendure deserves serious consideration.

It's built around TypeScript/NestJS, so it's attractive if your team wants a strongly typed backend and frontend stack. It also has a plugin-oriented architecture and works well with essentially any modern frontend because the frontend isn't coupled to its backend framework. Vendure ZORC

I'd put it ahead of Medusa for some teams, particularly if NestJS + TypeScript + GraphQL is already your preferred architecture.

commercetools: best enterprise developer platform

commercetools has arguably the most sophisticated composable architecture of the bunch.

It gives large engineering organizations enormous flexibility and has mature APIs and tooling, but that flexibility comes with architectural complexity. A recent real-world Next.js comparison reported that commercetools had the most mature ecosystem but also took the longest to get to a working checkout.

So I wouldn't choose it merely because "it's the most enterprise."

I'd choose it when you're actually enterprise enough to need it.

My decision rule

For a modern frontend team, I'd simplify the decision to:

Yes. The key distinction is whether you want a true marketplace engine or a headless commerce platform that you customize into one.

My shortlist

1. Mirakl — best if the marketplace itself is the core product

Mirakl is purpose-built around marketplace operations rather than merely providing ecommerce primitives. Its Marketplace Platform exposes separate Front, Operator, and Seller APIs, covering things like offers, orders, seller operations, and marketplace interactions. Mirakl Developer Portal

That makes it particularly attractive if you need:

• Seller onboarding and seller accounts
• Seller catalogs/offers
• Commission/fee structures
• Seller-specific order management
• Marketplace order workflows
• Seller APIs
• Enterprise-scale marketplace operations

The downside is that it's considerably more enterprise-oriented than something like Medusa.

2. Medusa — probably the most interesting startup option

Medusa is particularly compelling if you have engineers and want control over your marketplace data model.

Its documentation now has an explicit marketplace implementation showing how to create vendors and vendor admins, associate products with vendors, expose vendor APIs, authenticate sellers, and split a customer's order into separate vendor orders. Medusa Docs Medusa Docs

Importantly, though, marketplace functionality isn't native: Medusa explicitly describes this as something you build using its customization framework, modules, links, API routes, and workflows. Medusa Docs

That can actually be an advantage if your marketplace has unusual rules.

3. commercetools + Mirakl — strongest enterprise composable architecture

commercetools gives you the headless commerce layer while Mirakl supplies the marketplace capabilities. There's an established integration between the two specifically designed around a headless approach. Commercetools Marketplace

I'd consider this if you expect substantial scale and want to keep catalog, pricing, cart, checkout, etc. composable rather than putting everything inside a marketplace monolith.

What I'd choose

For a new digital marketplace with multiple independent sellers, I'd narrow it to:

• Mirakl → if you want marketplace functionality largely out of the box and have an enterprise budget.
• Medusa → if you're a startup with a strong engineering team and want maximum control/customization.
• commercetools + Mirakl → if you're building an enterprise-grade composable architecture.

One particularly important question is what "digital marketplace" means in your case. If sellers are selling digital goods (courses, downloads, SaaS, tickets, licenses, etc.), rather than physical products, the ideal architecture changes substantially—especially around fulfillment, entitlements, seller payouts, and order splitting.

If you tell me (1) physical vs digital goods, (2) expected seller count, (3) B2B/B2C, and (4) whether you need Stripe Connect-style seller payouts, I can narrow this to the 2–3 best platforms and compare their APIs/architecture.

That can actually be an advantage if your marketplace has unusual rules.

3. commercetools + Mirakl — strongest enterprise composable architecture

commercetools gives you the headless commerce layer while Mirakl supplies the marketplace capabilities. There's an established integration between the two specifically designed around a headless approach.

I'd consider this if you expect substantial scale and want to keep catalog, pricing, cart, checkout, etc. composable rather than putting everything inside a marketplace monolith.

What I'd choose

For a new digital marketplace with multiple independent sellers, I'd narrow it to:

If long-term portability and avoiding vendor lock-in are the primary goals, I’d choose Saleor—with Medusa as the strongest alternative if your team is heavily TypeScript-oriented.

My ranking for portability

Saleor's core is explicitly BSD-3-Clause licensed, and its architecture is API-only: the backend is interacted with and extended through APIs rather than proprietary storefront/plugin mechanisms. It can also be run locally/self-hosted rather than requiring Saleor Cloud. github.com

That's a particularly good combination for portability. If you eventually abandon Saleor, you're not trying to extract your business logic from a SaaS black box; your storefront, integrations, and much of your domain logic can remain independent of the commerce engine.

Why I wouldn't automatically pick Medusa

Medusa is arguably the better choice for a TypeScript/Node.js developer. Its core is MIT licensed and its commerce modules are open source, so it has exceptionally little licensing friction. github.com

I'd pick Medusa over Saleor when:

• the entire engineering organization is TypeScript/Node;
• you want to customize commerce primitives extensively;
• you prefer a modular framework rather than a GraphQL-centric commerce API;
• minimizing the number of languages in the backend matters more than having Saleor's API architecture.

The MIT license is also arguably the most permissive licensing position of the candidates.

The more important decision, though

The platform matters less than how you architect around it.

If portability is your #1 requirement, I'd structure the system approximately like:

                    Your storefront
                 Next.js / React / etc.
                         │
                         ▼
                 Your commerce BFF
                  / application API
                         │
              ┌──────────┴──────────┐
              ▼                     ▼
          Saleor/Medusa        Your services
              │               ┌──────────────┐
              ▼               │ ERP          │
          PostgreSQL          │ PIM          │
                              │ CRM          │
                              │ Search       │
                              │ Payments     │
                              └──────────────┘

In particular, don't make your frontend or business services depend directly on platform-specific concepts everywhere.

Instead:

• keep your own domain types/interfaces;
• isolate the commerce platform behind an adapter;
• own your customer/order/product data exports;
• use platform-neutral payment, search, CMS, tax and fulfillment services where practical;
• keep business-critical workflows in your own code;
• treat the commerce engine as an implementation detail;
• avoid platform-specific plugins for logic you might someday need to migrate.

That can make a move from Saleor → Medusa, or Medusa → something else, dramatically less painful.

One subtle reason I favor Saleor

Saleor specifically emphasizes technology-agnostic, API-only architecture, with external apps, webhooks and extensions rather than requiring your business logic to live inside platform-specific plugins. github.comgithub.com

That's exactly the architectural characteristic I'd optimize for if I were making a 10-year platform decision.

Vendure is also compelling technically, particularly for TypeScript teams, but its core is GPLv3 with a separate commercial license option, so I'd put it behind Saleor/Medusa when maximum long-term freedom is the criterion. github.com

Bottom line:

• Maximum architectural portability: Saleor
• Maximum portability + TypeScript/Node: Medusa
• TypeScript + sophisticated B2B: Vendure
• Enterprise SaaS/composable without wanting to operate the backend: commercetools
• Don't prioritize lock-in: Shopify

If I were starting a greenfield project today specifically with the goal of "I want to still be able to replace this platform in 7–10 years," I'd shortlist Saleor and Medusa and spend more time designing the platform boundary than comparing their feature lists.

For a custom dropshipping site where fast API-driven integrations are the priority, I’d recommend Medusa as the default choice.

My ranking

Why Medusa: it's built specifically as a customizable commerce backend, with REST Store APIs, a JS SDK, custom API routes, workflows, modules, and event subscriptions. That makes it particularly attractive if your dropshipping system needs to talk to supplier APIs, inventory feeds, fulfillment services, payment providers, tax systems, etc. docs.medusajs.com

A dropshipping architecture I'd use would look roughly like:

Next.js storefront
       │
       ▼
   Medusa API
       │
 ┌─────┼──────────┐
 ▼     ▼          ▼
Supplier A     Supplier B    Supplier C
API/feed       API/feed      API/feed
 │                │             │
 └──────────┬─────┴─────────────┘
            ▼
      Inventory sync
            │
            ▼
     Order routing
            │
            ▼
      Fulfillment APIs

The important part is not putting supplier-specific logic in your frontend. Make Medusa your commerce orchestration layer, then create adapters/modules for each supplier.

When I'd choose Saleor instead

I'd pick Saleor if you're comfortable with Python/GraphQL and expect sophisticated multi-channel, multi-region, warehouse, or B2B requirements. Saleor is GraphQL-native and exposes extensive APIs plus 140+ webhook events, which is excellent for event-driven integrations. saleor.io

When I'd choose Shopify

If your primary goal is getting a profitable store live as quickly as possible, rather than owning the commerce backend, Shopify's headless approach is considerably less operational work. You sacrifice some freedom around deeply customized commerce logic, though.

Bottom line: for a developer building a genuinely custom dropshipping platform, Medusa + Next.js + PostgreSQL + a queue/event system would be my starting stack. For a more enterprise/GraphQL-oriented build, I'd move Saleor to #1. powergatesoftware.com

If you tell me your expected order volume, number of suppliers, and whether suppliers expose REST APIs/webhooks or CSV feeds, I can recommend the architecture and platform more precisely.

For a dropshipping MVP where the priority is speed of prototyping + rapid iteration, I’d pick Shopify.

My ranking

1. Shopify — best overall for an MVP

• Fastest path from zero → functioning store.
• Hosting, checkout, payments, product catalog, orders, etc. are already handled.
• Huge app ecosystem for sourcing/fulfillment. Shopify currently lists hundreds of dropshipping apps, including DSers, CJdropshipping, EPROLO, and others. Shopify App Store Shopify App Store
• Easy to throw together a storefront, test the client's hypothesis, then swap themes/apps/workflows without rebuilding the backend.
• Particularly good if you're being paid to validate the business, rather than engineer an ecommerce platform.

shopify.com

2. WooCommerce — best if customization is the MVP

• More control over the underlying site and data.
• Excellent if the client already has WordPress or expects unusual business logic.
• But you'll be managing WordPress, hosting, plugins, updates, integrations, etc. WooCommerce's own dropshipping tooling involves configuring suppliers, notifications, packing slips, and fulfillment workflows. WooCommerce
• That flexibility generally means more engineering friction during an MVP.

woocommerce.com

3. Custom stack (Next.js/etc.) — I'd avoid for the first version

• Makes sense once you've proven demand and have requirements Shopify can't comfortably satisfy.
• For an MVP, you'll spend time rebuilding things Shopify already gives you: checkout, orders, payments, admin, inventory concepts, customer accounts, etc.

What I'd actually build

For a freelancer trying to deliver quickly, I'd do:

Shopify + lightweight custom theme + one sourcing/fulfillment app + minimal custom code.

Keep the architecture intentionally boring:

Shopify storefront → Shopify checkout → Shopify orders → dropshipping app → supplier

Then put your engineering effort into the things that actually differentiate the client's MVP: product presentation, conversion flow, custom UX, analytics, and whatever unique workflow they're testing.

The big advantage is that if the client says "change the pricing model," "add 50 products," "try a different supplier," "change the homepage," or "let's test another niche" next week, you're modifying configuration/apps/theme code rather than rebuilding infrastructure.

If you tell me what kind of dropshipping MVP it is (AliExpress-style, print-on-demand, local suppliers, marketplace, subscription box, etc.), I can recommend the exact Shopify stack I'd use and what I'd custom-build vs. leave to apps.

For a subscription-focused dropshipping store, I’d use Shopify as the core platform and layer subscription + supplier automation on top.

My recommended stack

Shopify is particularly attractive because subscriptions are built into its commerce architecture: recurring purchases create subscription contracts and generate new orders at renewal. shopify.dev

For suppliers, Shopify's current ecosystem supports automated inventory syncing and order routing. For example, Syncee can synchronize supplier inventory and send orders to suppliers for fulfillment, while Shopify Collective can route orders directly to participating suppliers. www.shopify.comshopify.dev

Which subscription app?

Start with Shopify Subscriptions if you're selling something straightforward like:

“Get this product every 30 days and save 10%.”

It's native, integrates with Shopify Payments, and is probably the lowest-complexity option. www.shopify.com

I'd move to Appstle or Recharge if you need things like:

• Skip/pause subscription
• Change delivery frequency
• Swap products
• Subscription bundles
• Multiple subscription plans
• More sophisticated retention/churn tools

The important part for dropshipping

Don't choose your supplier solely based on product price. For subscriptions, you need a supplier that can reliably support repeated fulfillment.

Your ideal workflow is:

Customer subscribes → Shopify bills them → new order generated → supplier receives order automatically → supplier ships → tracking returns to Shopify → customer receives next shipment.

Shopify's subscription architecture supports this recurring-order model, while dropshipping integrations can handle the supplier/inventory side. www.shopify.comshopify.dev

If I were starting today:
Shopify + Appstle + Syncee/Spocket would be my default stack. It gives you a relatively simple setup while leaving room to scale to multiple suppliers.

If you tell me what type of product you're planning to sell (supplements, beauty, pet products, coffee, household consumables, etc.), I can recommend the specific platform + supplier setup I'd use for that niche.

For a small POD dropshipping team, I’d generally recommend Shopify + a dedicated product-personalization app + Printful/Printify, rather than trying to make the store builder itself handle every customization function.

My ranking

🥇 I'd choose Shopify

The key advantage isn't Shopify's native product options—it is the ecosystem of personalization tools you can layer onto it.

For example, Printful itself says its Shopify personalization workflow doesn't provide the customer-facing personalization input, and recommends using a third-party tool such as Zepto Product Personalizer. help.printful.com

That gives you a setup like:

Shopify → personalization/preview app → Printful/Printify → automated fulfillment

You can give customers things like:

• Enter their name
• Choose fonts
• Choose colors
• Upload an image
• Add multiple text fields
• Select icons/graphics
• See the personalization on the product
• Generate a visual preview before checkout
• Conditional options ("If you choose this style, show these fields")
• Charge extra for certain personalization options

The big thing I'd look for is true live rendering, not merely a form that collects "Name: John." For a POD business, the customer should ideally see something close to "this is exactly what my mug/shirt/ornament will look like."

One caveat: third-party Shopify personalization apps can introduce fulfillment/sync complications. Printful specifically warns that apps which alter product variants may not always synchronize cleanly with Printful, so I'd test the complete workflow with sample orders before launching. help.printful.com

🥈 Wix is surprisingly attractive

If your team isn't particularly technical, I'd seriously consider Wix.

Wix already has product options, modifiers, text boxes, swatches, conditional-style customization through apps, and the ability to associate different media with product choices. support.wix.com

It also has built-in POD functionality and integrations, including automatic fulfillment through POD suppliers. www.wix.com

So if your products are relatively straightforward—e.g.:

Pick color → enter name → choose font → see a few product images → order

Wix can be a very clean solution.

🥉 WooCommerce if customization is the core of your business

I'd pick WooCommerce if you're planning something more sophisticated, such as:

Upload photo → automatically remove background → position/resize it → add text → choose 15 design elements → dynamically render the final artwork → generate production-ready file → send to POD supplier.

WooCommerce gives you enormous flexibility, but that flexibility comes with more maintenance. For a small team trying to sell rather than maintain software, I'd only choose it if you have someone comfortable with WordPress/WooCommerce development.

The distinction I'd make

There are actually three different things people call "custom product previews":

1. Variant preview
Customer chooses black vs. white → product image changes.

2. Personalization preview
Customer enters Sarah → the product image updates to show Sarah.

3. Full product designer
Customer uploads an image, moves it around, changes fonts/colors, adds artwork, etc., and sees a near-final rendering.

If you're after #2 or #3, I'd strongly favor Shopify.

If you're mainly doing #1, Wix can be more than sufficient. Wix officially supports linking different images/videos to product option choices, which makes basic visual variant selection straightforward. support.wix.com

What I'd build for your team

If I were setting this up today, my default stack would be:

Shopify
↓
Product personalization/preview app
↓
Printful or Printify
↓
Automated fulfillment + tracking

And I'd make one rule for the team:

Don't choose the store builder first. Choose the personalization technology first, then make sure it integrates cleanly with your POD provider.

That's because the preview/personalization experience is likely to be the thing that differentiates your store, whereas Shopify/Wix are mostly infrastructure.

If you tell me what kinds of products you're selling (shirts, mugs, wall art, jewelry, phone cases, etc.) and whether customers will upload photos, enter text, choose designs, or all three, I can narrow this down to the best 2–3 exact stacks/apps for your use case.

If your priority is “I want to own the code and build my own dropshipping integrations”, I’d strongly favor a headless open-source commerce engine rather than something like Shopify.

My shortlist for 2026:

1. 🥇 Medusa — my first choice

Medusa official site

For the specific business you're describing, Medusa is probably where I'd start.

It's designed as a headless commerce backend, so you can build your own frontend and treat the commerce engine as your underlying system. Its modular architecture is particularly attractive when you're going to replace or extend things like fulfillment, payments, shipping, pricing, and inventory. www.wpbundle.com

For dropshipping, I'd structure it roughly like:

                 YOUR STOREFRONT
                    Next.js
                       │
                       ▼
                 ┌───────────┐
                 │  MEDUSA   │
                 │ Commerce  │
                 └─────┬─────┘
                       │
        ┌──────────────┼──────────────┐
        ▼              ▼              ▼
   Supplier A     Supplier B     Supplier C
     API/EDI         API           CSV/API
        │              │              │
        ▼              ▼              ▼
   Inventory       Inventory      Inventory
   Orders          Orders         Orders
        │              │              │
        └──────────────┼──────────────┘
                       ▼
                  Fulfillment

That gives you the ability to create your own supplier adapter layer rather than trying to force every supplier into a generic dropshipping app.

For example:

Supplier
 ├── products()
 ├── inventory()
 ├── getPrice()
 ├── createOrder()
 ├── getOrderStatus()
 └── getTracking()

Then each supplier gets its own implementation.

That's much more powerful long-term than building your business around a proprietary dropshipping app.

2. Vendure — very compelling if you're TypeScript-heavy

Vendure official site

Vendure is another excellent option if you want a Node/TypeScript commerce backend. It's built around GraphQL and a plugin architecture, which makes it particularly interesting if you anticipate building unusual business logic. www.pkgpulse.com

I'd seriously compare Medusa vs Vendure if you're comfortable coding in TypeScript.

My distinction would be:

• Medusa: I'd pick it for a new, developer-first custom store.
• Vendure: I'd pick it if its plugin/domain architecture fits your particular business model better.

3. Saleor — if you're building something much bigger

Saleor official site

Saleor is especially interesting if you're envisioning more than a basic dropshipping store — e.g. multiple warehouses, multiple sales channels, international markets, B2B, complex pricing, etc.

It's GraphQL-first, headless and designed to be extended through apps/webhooks. Saleor explicitly positions itself around being able to integrate with essentially any external system. saleor.io

The downside is that it's a heavier engineering commitment. You're also moving into a Python/Django backend rather than the Node/TypeScript ecosystem.

4. WooCommerce — don't overlook it

WooCommerce official site

If you want to get the business running quickly, WooCommerce has a huge advantage: its ecosystem.

There are enormous numbers of existing integrations for payments, shipping, suppliers, taxes, feeds, analytics, marketplaces, etc. Its REST API also makes custom integration possible. www.wpbundle.comwww.pkgpulse.com

But if your vision is:

"I'm essentially building my own commerce infrastructure and supplier network."

I'd prefer Medusa/Vendure/Saleor.

If your vision is:

"I want a store online quickly and I want an existing plugin for almost everything."

I'd choose WooCommerce.

What I'd actually build for your use case

If you're technically capable and want maximum control, I'd use:

Frontend

• Next.js
• TypeScript
• Tailwind

Commerce

• Medusa

Database

• PostgreSQL

Cache / queues

• Redis

Payments

• Stripe or another processor

Dropshipping layer

• Your own supplier integration service

Infrastructure

• Docker
• Your own VPS/cloud
• CI/CD through GitHub

Architecture

                    Customer
                       │
                       ▼
                 Next.js Store
                       │
                       ▼
                  Medusa API
                       │
          ┌────────────┼────────────┐
          ▼            ▼            ▼
       Catalog       Cart/Order    Customer
                       │
                       ▼
                 Order Router
                       │
       ┌───────────────┼────────────────┐
       ▼               ▼                ▼
  Supplier API     Supplier API      Supplier API
       │               │                │
       ▼               ▼                ▼
   Inventory       Inventory        Inventory
       │               │                │
       └───────────────┼────────────────┘
                       ▼
                  Tracking Sync
                       │
                       ▼
                    Customer

The order router is the important part.

You could eventually have logic such as:

Product X
 ├─ Supplier A: $12, 94 units
 ├─ Supplier B: $11, 8 units
 └─ Supplier C: $14, 500 units

Customer buys X

→ choose Supplier B if available
→ otherwise Supplier A
→ otherwise Supplier C
→ submit order
→ receive supplier order ID
→ sync tracking
→ update customer's order

That gives you considerably more control than simply installing a "dropshipping plugin."

My ranking for your stated goal

🥇 Medusa — best balance of openness, developer experience and customization
🥈 Vendure — excellent if you want a TypeScript/NestJS architecture
🥉 Saleor — strongest choice for a more enterprise/complex operation
4. WooCommerce — best ecosystem, easiest path to existing integrations
5. Bagisto — attractive if you're a Laravel/PHP developer

The big thing I'd investigate before choosing the platform isn't the storefront at all—it's the supplier integration architecture. If you tell me what kind of dropshipping you want (AliExpress/Alibaba, US wholesalers, print-on-demand, Amazon, private suppliers, multiple suppliers, etc.), I can map out the best open-source stack + supplier API architecture for it.

If you’re a small ecommerce shop, I’d prioritize low fixed cost + good failed-payment recovery (dunning) + a solid self-serve customer portal. You probably don’t need an enterprise subscription platform yet.

My shortlist

1. Appstle — my default recommendation.
appstle.com

It has a particularly good balance for a small Shopify merchant: recurring billing, flexible subscription rules, churn controls, analytics, and a customer portal where customers can skip, pause, swap products, reschedule, or update payment information. Appstle also has a free plan, making it relatively low-risk to test. Appstle Intercom Shopify App Store

2. Recurpay — best if keeping costs extremely low is the priority.
Recent 2026 comparisons put it among the strongest small-business options, with a free plan and inexpensive paid tiers. Recurpay Recurpay

recurpay.com

3. Loop — best if dunning/churn reduction is the main problem.
Loop puts more emphasis on retention workflows, cancellation interventions, pause/skip options, and failed-payment recovery than a basic subscription app. That makes it attractive once you have enough subscribers for churn to be a meaningful revenue problem. ChurnTools LAUNCHTIP

loopwork.co

4. Recharge — best if you expect to become a substantial subscription business.
It's a mature ecosystem with lots of integrations and sophisticated retention tooling, but I'd generally consider it overkill for a small shop unless subscriptions are already a major part of revenue. ChurnTools Shopify

rechargepayments.com

5. Shopify Subscriptions — best for simplicity.
If your subscription model is straightforward and you mainly want recurring orders without another substantial software layer, Shopify's native solution is worth considering. Shopify specifically highlights its direct Shopify Payments integration and automatic card updating as advantages. Shopify

What I'd choose

For a typical small Shopify store:

Start with Appstle.
If you're primarily trying to recover failed recurring payments, rather than build elaborate subscription experiences, it's probably the best balance of capability and cost.

The features I'd specifically verify before installing are:

• Automatic retry schedule for failed cards
• Customer emails/SMS during the dunning sequence
• Automatic cancellation after X failed attempts
• Card-update/payment-update links
• Account updater support
• Ability to pause/skip rather than cancel
• Cancellation save offers
• Visibility into recovered revenue, not just failed payments
• No nasty transaction fee that becomes expensive as subscription revenue grows

One important distinction: dunning software and subscription software aren't necessarily the same thing. If you're already happy with how subscriptions are managed and just need better payment recovery, a dedicated billing/payment layer can sometimes be cheaper than migrating the entire subscription system.

If you tell me (1) Shopify/WooCommerce/custom, (2) roughly how many subscribers you have, and (3) monthly recurring revenue, I can narrow this to the 2–3 best choices and estimate what each would cost you per month.

2. Recurpay — best if keeping costs extremely low is the priority.
Recent 2026 comparisons put it among the strongest small-business options, with a free plan and inexpensive paid tiers. Recurpay Recurpay

recurpay.com

3. Loop — best if dunning/churn reduction is the main problem.
Loop puts more emphasis on retention workflows, cancellation interventions, pause/skip options, and failed-payment recovery than a basic subscription app. That makes it attractive once you have enough subscribers for churn to be a meaningful revenue problem. ChurnTools LAUNCHTIP

loopwork.co

4. Recharge — best if you expect to become a substantial subscription business.
It's a mature ecosystem with lots of integrations and sophisticated retention tooling, but I'd generally consider it overkill for a small shop unless subscriptions are already a major part of revenue. ChurnTools shopify.com

rechargepayments.com

5. Shopify Subscriptions — best for simplicity.
If your subscription model is straightforward and you mainly want recurring orders without another substantial software layer, Shopify's native solution is worth considering. Shopify specifically highlights its direct Shopify Payments integration and automatic card updating as advantages.

What I'd choose

For a typical small Shopify store:

If you’re a SaaS founder whose core business is digital/software, but you’re adding a physical product subscription to the existing checkout, I’d generally recommend Stripe Checkout + Stripe Billing rather than moving your commerce stack to Shopify.

Stripe Checkout supports both physical goods and subscriptions, so you can keep the SaaS checkout architecture you already have. Stripe

My ranking

1. Stripe Billing + Checkout — best default for a SaaS company

• Keeps your existing Stripe/customer/payment infrastructure.
• Supports recurring billing and one-time physical purchases.
• Highly customizable checkout.
• You can model the physical subscription alongside your existing SaaS subscription.
• Best if the physical product is an extension of your SaaS, rather than the primary business.
• Downside: you'll need to build more of the physical-commerce layer yourself—shipping, fulfillment workflows, inventory, returns, etc. Stripe is fundamentally a payments/billing platform, not a full DTC commerce platform. Stripe Shopify
• Shopify + Shopify Subscriptions — best if physical becomes a major business

• Much stronger native ecosystem for products, inventory, shipping, fulfillment, discounts, and commerce operations.
• Shopify's Subscription APIs integrate subscriptions directly into Shopify Checkout and work with shipping, discounts, reporting, and Shopify Payments. Shopify
• Shopify currently supports a large ecosystem of physical-product subscription apps. Shopify App Store
• Downside: it can feel awkward if your actual product is SaaS and Shopify is being introduced primarily to sell one physical add-on.
• Recharge — worth considering if the physical subscription itself becomes important

• Particularly attractive if you're building something resembling a traditional DTC subscription business.
• I'd consider it if you expect hundreds/thousands of physical subscribers and want subscription-specific retention/operations functionality rather than building that yourself.
• Shopify currently lists Recharge among its major subscription-management options. Shopify
• Chargebee — probably overkill

• Excellent when subscription billing itself is complex—multiple plans, invoicing, B2B, usage billing, etc.
• For "SaaS + a monthly physical box/product," I'd avoid adding another billing abstraction unless you already use it.

The architecture I'd choose

If you already have a SaaS checkout built around Stripe:

Your app → Stripe Checkout → Stripe Billing → fulfillment system/3PL

I'd treat the physical item as another subscription product/price in Stripe, while keeping fulfillment and inventory outside Stripe.

The important question isn't really "which subscription platform?" It's:

Do you want the physical product to behave like a feature of your SaaS, or do you want to operate a commerce business?

If it's something like "$20/mo SaaS + optional $15/mo physical kit", I'd strongly favor Stripe.

If it's more like "our SaaS customers are becoming subscribers to a recurring physical product business", I'd favor Shopify + a subscription platform such as Recharge.

If you tell me (1) what your SaaS does, (2) what the physical product is, (3) whether you're already on Stripe, and (4) roughly how many physical subscribers you expect, I can give you a much more specific architecture recommendation—including how I'd structure checkout, subscriptions, shipping, taxes, cancellations, and fulfillment.

For a mid-market retailer with thousands of active subscribers, I’d shortlist Recurly first—especially if the priority is minimal downtime and a managed migration.

My recommendation

1. Recurly — best overall for a low-risk migration

Recurly supports managed migrations of customer accounts, billing information, and subscriptions, including PCI-compliant payment-data transfers. Its documentation specifically emphasizes maintaining subscription continuity during migration. Recurly Documentation Recurly, Inc.

If you're on Shopify/Shopify Plus, Recurly Commerce is particularly compelling: it says migrations can be automated with 99.9%+ data fidelity and can process up to 100,000 subscribers per day, with no subscriber disruption. Recurly Documentation

docs.recurly.com

2. Recharge — best if you're deeply invested in Shopify

Recharge has a well-established Shopify ecosystem and a migration process designed to keep the store operational while the subscriber data is transferred. It also has experience migrating very large subscription bases; its site cites a migration of millions of subscribers completed over a few days. Recharge Support Recharge

getrecharge.com

3. Stripe Billing — best if you want maximum control

Stripe's Billing Migration Toolkit can import subscriptions from platforms such as Zuora, Recurly, Chargify, and Chargebee without requiring you to build the migration entirely yourself. It's attractive if your retailer already has a strong Stripe engineering stack, but I'd expect more implementation responsibility than with a managed Recurly migration. Stripe Docs

docs.stripe.com

What I'd choose

The key isn't just the platform. Don't do a big-bang cutover. The safest architecture is to establish the new platform first, migrate customer/payment data securely, route new subscriptions to the new system, validate a cohort of existing subscribers, then progressively move the remaining book while keeping the old system available as a fallback. Recurly explicitly supports keeping multiple gateways active during transitions, which is useful for this type of phased migration. Recurly Support

If you tell me your current platform (e.g. Recharge, Bold, Salesforce Commerce Cloud, Shopify), payment processor, and roughly how many subscribers, I can narrow this to the best 2–3 options and lay out a zero/near-zero-downtime migration architecture.

Yes. If you mean recurring subscriptions where the platform handles billing + VAT/sales tax + compliant invoices globally, there are a few strong options.

Best fit: Paddle

paddle.com is probably the closest to what you're describing.

• Recurring subscription billing
• VAT, GST, and sales-tax calculation
• Tax registration, collection, filing, and remittance
• Compliant invoices
• Acts as Merchant of Record, so Paddle—not you—takes responsibility for the relevant indirect-tax obligations
• Supports 300+ markets/territories
• Handles subscription changes, prorations, failed payments, etc. Paddle Paddle Paddle

That last point is important: a tax calculator isn't the same thing as a Merchant of Record. With something like Stripe Tax, you generally remain the merchant and are responsible for registrations/filings unless you add other services. Paddle takes much more of that burden off your plate. Paddle Stripe

Other good choices

stripe.com + stripe.com is excellent if you want to retain more control. Stripe Tax supports subscriptions and tax calculation across 100+ countries, while Stripe provides invoicing and billing infrastructure. Stripe Stripe

chargebee.com is particularly strong for sophisticated SaaS billing. It can automatically calculate tax on recurring invoices and integrate with Avalara for broader global tax coverage and e-invoicing. Chargebee Chargebee

If you're building a SaaS

I'd narrow it down to:

Paddle → "I want someone else to deal with global tax compliance."

Stripe → "I want maximum payment/billing flexibility and I'm okay managing the tax/compliance layer."

Chargebee + Avalara → "We're building a serious enterprise subscription/revenue stack with complex billing."

If you tell me what you're selling (SaaS, physical goods, digital services, marketplace, etc.) and roughly how many countries/customers you expect, I can recommend the best architecture and compare the actual fees.

Yes. If you mean a tool for selling prepaid subscription terms and making renewals easy, there are several options:

• chargebee.com — supports billing future renewals in advance, so customers can prepay for multiple upcoming billing cycles. It also supports automated renewals and customer self-service. Chargebee API Documentation Chargebee
• stripe.com — supports prebilling for multiple future service periods and upcoming renewals. Stripe Docs
• recurly.com — supports subscription terms with automatic renewal and customizable billing periods. Recurly Docs Recurly Docs

If “one-click renewal” specifically means a customer receives a button/link and can renew their prepaid plan with minimal interaction, I’d look particularly closely at Chargebee or a subscription platform paired with a customer portal. Chargebee's ecosystem also explicitly supports 1-click subscription actions. Recurly Docs

If you tell me what you're selling (e.g., memberships, SaaS, services, subscriptions) and whether you need automatic renewal vs. customer-initiated one-click renewal, I can recommend the best fit.

For a local bakery with menus + pickup orders + occasional online specials, I’d narrow it to Square Online vs. Squarespace:

🥇 My pick: Square Online

Choose Square Online if the priority is making ordering easy and keeping operations simple. It supports online ordering, pickup scheduling, payments, and can sync with Square’s in-person POS. It also has a free starting tier, which is attractive for a small bakery. www.bakersetup.com

Best if you want:

• Menu → cart → payment → pickup
• Pickup time slots
• Easy holiday/weekly specials
• One system for in-store and online sales
• Minimal technical work

The tradeoff is that the site design is less distinctive than Squarespace. www.bakersetup.com

🎨 Choose Squarespace if branding matters more

Squarespace is better if you want a beautiful, photography-heavy website where your bakery's personality and products are the star. It handles menus, specials, forms, and commerce, and its restaurant-oriented designs are specifically built around showcasing food. support.squarespace.com

I'd choose it if you're selling things like custom cakes, wedding cakes, artisan pastries, where the website itself needs to sell the brand.

What I'd do in your situation

Bottom line: For a neighborhood bakery primarily doing local pickup, I'd start with Square Online. For a bakery where the website is a major part of the brand/marketing, I'd spend the extra money on Squarespace.

If you tell me whether you already use Square for your register/payments and roughly how many online orders you expect per week, I can tell you which one I'd choose—and what the site structure should look like.

For your use case—seasonal, limited SKUs, and speed over long-term complexity—I’d pick Big Cartel.

• Big Cartel: easiest/leanest fit. Its free Gold plan supports up to 5 products, includes payments, variants, tax automation, and a storefront; Big Cartel says you can launch in 30 minutes or less. www.bigcartel.com
• Shopify: better if you expect the seasonal launch to become a serious DTC channel. It has a more complete commerce stack and unlimited products, but you’re paying for capabilities you may not need for a short-lived catalog. www.shopify.com
• Squarespace: worth considering if the brand/visual presentation matters as much as checkout; it’s more of a full website builder with commerce. support.squarespace.com

My call:
≤5 SKUs → Big Cartel.
5–50 SKUs or likely repeat launches → Shopify.
Highly design-led campaign site → Squarespace.

If you tell me roughly how many SKUs, whether you need a custom domain, and whether you’re selling primarily through Instagram/TikTok, I can narrow it to the fastest setup.

For a subscription box business, I’d shortlist these:

1. Shopify — best overall
   • Strongest ecosystem for physical subscription boxes.
   • Supports recurring billing through Shopify Subscriptions or third-party subscription apps.
   • Customer accounts can let subscribers pause, skip, cancel, change payment methods, update shipping addresses, and view upcoming/past orders. help.shopify.com
   • There are dedicated subscription-box apps, including options with build-a-box and customer portals. apps.shopify.com

2. Wix — easiest site builder
   • Particularly good if your priority is a beautiful site with less technical setup.
   • Wix supports subscription products with automatic recurring charges and a “My Subscriptions” area where customers can view/manage subscriptions. help.shopify.comwww.wix.comsupport.wix.com
   • It supports weekly, monthly, and yearly recurring payments, subject to the payment provider you use. support.wix.com

My pick: Shopify if subscriptions are the core of your business. Its subscription ecosystem is considerably deeper, which matters if you eventually want things like skip-a-month, swap products, build-your-own-box, failed-payment recovery, discounts, and more sophisticated subscriber management.

If you tell me roughly how many subscribers you have and whether customers choose the contents of their box or receive a fixed box, I can narrow it down to the best 2–3 platforms for your specific setup.

For a nonprofit that needs to sell event tickets and merchandise, I’d usually recommend Wix as the best affordable all-around choice, with Squarespace as the prettier alternative and WordPress as the long-term flexible option. www.wix.comwww.squarespace.com

My top picks

My recommendation by scenario

If you sell tickets a few times per year and have a volunteer/non-technical team:
→ Wix
It’s probably the easiest balance of cost, event sales, merch, and maintenance. www.wix.comrefact.co

If your nonprofit is arts/culture/community-focused and visuals matter:
→ Squarespace + a ticketing integration
It tends to produce a more polished “mission/story” website with less design effort. www.wix.comwww.squarespace.com

If you run many events, memberships, donations, and campaigns:
→ WordPress
It takes more setup, but you’ll have more options as you grow. www.arcstone.com

A budget-friendly setup I’d consider

• Website: Wix or Squarespace
• Tickets: built-in event tools or an external ticketing platform
• Merch: website store (Wix/Squarespace) or Shopify if sales grow
• Donations: embed a nonprofit-focused tool such as Donorbox or similar

One question would change my recommendation: How many events do you sell tickets for each year, and is merch a small fundraiser (shirts/totes occasionally) or a major revenue stream?

For a pop-up retail concept, I’d usually start with a system that keeps website, inventory, customer data, and in-person checkout in one place. The best choice depends on how you operate:

My default recommendation for a pop-up brand:

Shopify + Shopify POS
It gives you:

• A branded ecommerce site
• Inventory that updates when something sells at a pop-up
• Customer profiles (so a pop-up buyer can become an online customer)
• Gift cards, discounts, returns, and analytics
• Mobile checkout with card readers/tablets www.shopify.comwww.shopify.com

A typical setup:

• Website: Shopify
• POS: Shopify POS app
• Hardware: iPad + Shopify card reader + barcode scanner (optional)
• Inventory: Shopify product catalog
• Marketing: Shopify Email/SMS integrations
• Accounting: QuickBooks/Xero integration

I’d choose Square instead if your business is mostly weekend markets, craft fairs, or one-off activations and you don’t need a serious ecommerce engine. squareup.com

I’d choose Lightspeed if you’re closer to a boutique retailer with hundreds/thousands of SKUs and complex inventory needs. technologyadvice.com

A few details would change my recommendation:

1. What do you sell (apparel, beauty, food, collectibles, etc.)?
2. Do you already have a website?
3. How many pop-ups per month?
4. Rough inventory size (50 products vs 5,000 SKUs)?
5. Do you need customer loyalty/email capture at checkout?

For a beautiful portfolio site + occasional client deposits for services, I’d focus on builders that make the site look premium but don’t force you into a full online store. The best fits are:

www.sitebuilderreport.comwebsitebuilderreport.com

My recommendation:

Pick Squarespace if your priority is “wow, this looks like a high-end portfolio.”
It’s especially strong for:

• photographers
• artists
• architects
• designers
• branding studios
• consultants

You can create service “products” like:

• “Brand Strategy Package — $500 deposit”
• “Photography Session — $250 retainer”
• “Website Audit — $300”

and let clients pay online without building a complicated store. www.squarespace.com

Pick Wix if you need more client-management features, such as:

• appointment booking
• intake forms
• automated emails
• invoices/payments
• a mini CRM

It’s usually the smoother choice for freelancers who sell services rather than just display work. www.colibrisystems.co

A strong setup for a solo creative business would be:

1. Portfolio homepage — large visuals + your best projects
2. Services page — 3–5 clear packages
3. “Book / Start a Project” button
4. Deposit checkout — fixed amount or percentage
5. Client questionnaire after payment

I’d probably avoid Shopify unless you expect to sell many products, and I’d avoid Webflow unless you enjoy designing the site itself. www.sitebuilderreport.comwebsitebuilderreport.com

If you tell me your field (photography, design, consulting, construction, coaching, etc.) and whether you want a luxury/minimal or bold/creative look, I can narrow it to the best builder and template style.

For your use case—selling fine-art prints + high-res digital files + image licenses—I’d narrow it to Pic-Time and Pixieset, with Pic-Time as my first choice.

My recommendation: Pic-Time

Pic-Time is particularly strong if your business is primarily selling photography, rather than building a general-purpose ecommerce store.

Why I’d pick it:

• High-res digital delivery: You can sell individual high-resolution images, full galleries, or packages, with custom resolutions and downloadable terms/release forms. help.pic-time.com
• Print sales: Integrated print fulfillment lets customers order physical products, with automatic fulfillment through a large lab network. www.pic-time.com
• Licensing: You can attach specific download terms and release forms to digital products, which is useful for commercial/licensing work. help.pic-time.com
• Upselling: You can combine downloads and physical prints into packages—e.g. 1 commercial-resolution file + 16×24 print. help.pic-time.com
• Photography-first customer experience: The gallery itself becomes the storefront, rather than sending customers from a portfolio site to a separate ecommerce system.
• Watermarking: Paid high-res files can be protected while customers see lower-resolution previews. www.pic-time.com

Pixieset is an excellent alternative

Pixieset would actually be my choice if you want a more all-in-one business platform.

It combines website, portfolio, galleries, ecommerce, digital delivery, and business-management tools. Its Store supports prints, high-resolution downloads, packages, and automatic fulfillment. pixieset.com

Pixieset also explicitly supports digital image licenses, which customers agree to at checkout. website-help.pixieset.com

Its current plans include full-resolution downloads, with higher tiers offering substantially more storage; the Pro plan currently lists 1 TB of storage. pixieset.com

How I'd decide

One important distinction: if by "licenses" you mean commercial usage licenses—for example, selling an image to a magazine, advertising agency, hotel, or brand with specific usage territory/duration/media—I'd put considerably more weight on the licensing workflow than I would for ordinary client downloads. Neither platform is a full-fledged stock-licensing management system.

If that's the kind of licensing you're doing, tell me what you're selling (fine-art prints, editorial, commercial, stock, weddings, etc.) and roughly how many images/files you expect to host, and I can compare Pic-Time vs Pixieset vs SmugMug vs Shopify specifically for your business, including fees, storage, print labs, licensing, and checkout.

If you mean courses + standalone digital products (templates, ebooks, PDFs, audio, etc.) under one storefront, my top pick is Podia.

Best fits

Why Podia stands out: it treats courses and downloads as separate first-class product types, while putting them into the same site/store. You can create courses with lessons, video, quizzes, and downloads, while standalone downloads can be PDFs, templates, audio, video files, etc. help.podia.com

Its site builder also connects your pages directly to your products, and its products-page component can display courses, downloads, coaching, and bundles together. help.podia.com

I'd choose Kajabi instead if your business is more like:

free content → email list → lead magnet → webinar → course → upsell → membership

Kajabi's strength is the integrated marketing/automation side rather than simply having a clean mixed product catalog. www.kajabi.com

Bottom line: For a creator who wants “here are my courses, and here are my smaller products” without stitching several systems together, Podia is probably the cleanest choice. courseprofitlab.com

If you tell me roughly how many courses/products you expect to sell and whether you need email funnels, memberships, or a community, I can narrow it down to Podia vs. Kajabi vs. Thinkific.

If your goal is “people see a post or livestream → click/tap the product → buy with as little friction as possible,” I’d make Shopify the commerce backbone, then connect it to the social platforms where your audience actually spends time.

My recommendation

Best overall: Shopify + TikTok Shop + Instagram/Facebook + YouTube Shopping

shopify.com is the strongest central platform because it can sync your products, inventory, and orders with multiple social-commerce channels rather than forcing you to build your business around one social network. Shopify specifically supports shoppable posts/video and live commerce through TikTok, YouTube, Facebook and Instagram. Shopify Shopify Help Center

If livestreams are your main strategy

I'd put TikTok Shop first.

TikTok lets sellers attach products directly to videos and LIVE streams, so viewers can purchase without leaving TikTok. It also has creator/affiliate functionality, which can be particularly powerful if you're going to have influencers selling your products. TikTok Shop TikTok Ads

And importantly, TikTok has an official Shopify integration that can sync products, inventory and orders. TikTok Shop TikTok For Business

If you want your own branded shopping experience

Go Shopify + a live-shopping app rather than relying exclusively on TikTok.

For example, Shopify's ecosystem includes tools such as Firework, Channelize, LiveMeUp, Videowise and others for shoppable video/live experiences. Some can put livestreams directly on your own site and/or distribute content across social channels. Shopify Shopify App Store

That gives you a setup like:

Instagram/TikTok/YouTube post or LIVE → product → Shopify checkout

while also allowing:

Your website → livestream → product → checkout

What I'd choose by business type

• New DTC brand: Shopify + TikTok Shop
• Strong TikTok/creator audience: TikTok Shop + Shopify
• Strong Instagram audience: Shopify + Instagram/Facebook + TikTok Shop
• YouTube creator/educator: Shopify + YouTube Shopping
• Heavy livestream business: Shopify + TikTok Shop + dedicated live-commerce platform
• Want maximum control over customer data/brand: Shopify as the core, social platforms as acquisition/sales channels

One important distinction: TikTok Shop is itself a sales channel, whereas Shopify is better thought of as your commerce operating system. I wouldn't make TikTok your only backend if you expect the business to grow across several social platforms.

If you tell me what you're selling, your approximate monthly sales, and whether you primarily sell on Instagram/TikTok/YouTube, I can narrow this down to the best 2–3 platforms and the exact setup I'd use.

If livestreams are your main strategy

I'd put TikTok Shop first.

TikTok lets sellers attach products directly to videos and LIVE streams, so viewers can purchase without leaving TikTok. It also has creator/affiliate functionality, which can be particularly powerful if you're going to have influencers selling your products. TikTok Shop TikTok Ads

And importantly, TikTok has an official Shopify integration that can sync products, inventory and orders. TikTok Shop ads.tiktok.com

If you want your own branded shopping experience

Go Shopify + a live-shopping app rather than relying exclusively on TikTok.

For example, Shopify's ecosystem includes tools such as Firework, Channelize, LiveMeUp, Videowise and others for shoppable video/live experiences. Some can put livestreams directly on your own site and/or distribute content across social channels. Shopify apps.shopify.com

That gives you a setup like:

Instagram/TikTok/YouTube post or LIVE → product → Shopify checkout

while also allowing:

Your website → livestream → product → checkout

What I'd choose by business type

For a fast-fashion enterprise launching lots of microsites, flash campaigns, influencer drops, and temporary storefronts, I’d shortlist the platforms differently than I would for a conventional ecommerce retailer.

My recommendation

1. Shopify Plus — best default choice

Shopify Plus is probably the strongest choice if your priority is speed + operational simplicity + lots of campaigns.

Why it fits:

• Extremely fast launch of new storefronts/campaigns.
• Strong checkout and infrastructure without your team owning the underlying commerce stack.
• Headless APIs are available if campaigns need bespoke front ends.
• Centralized administration and integrations.
• Strong ecosystem for marketing, social commerce, fulfillment, personalization, etc.
• Shopify says its infrastructure supports 10K+ checkouts/minute, unlimited SKUs, and global expansion. www.shopify.comdocs.commercetools.comcommercetools.com

The architecture I'd use: one core Shopify Plus commerce environment + reusable campaign storefront templates + separate domains/subdomains for campaigns, rather than creating completely independent ecommerce stacks for every microsite.

2. commercetools — best if you're truly operating at enterprise complexity

commercetools is my pick if you expect hundreds/thousands of storefront experiences, multiple brands, highly differentiated catalogs/pricing, or a very sophisticated composable architecture.

It has native concepts for Stores and Channels, allowing multiple shopping experiences to share underlying resources while maintaining different products, prices, inventory and customer experiences. docs.commercetools.com

That's particularly compelling for fashion because you could have:

Core commerce
→ Brand A
→ Brand B
→ Influencer drop #1
→ Influencer drop #2
→ Country-specific store
→ Festival campaign
→ Flash-sale storefront
→ Outlet
→ Marketplace experience

without treating each as a completely separate ecommerce platform.

commercetools specifically positions its retail platform for high-stakes launches, product drops, extreme traffic peaks, multi-brand/multi-catalog operations, and localized experiences. commercetools.com

The tradeoff is much greater implementation complexity and engineering investment than Shopify Plus.

3. Salesforce Commerce Cloud — best if you're already deeply invested in Salesforce

Salesforce Commerce Cloud is another serious enterprise option. Its architecture explicitly supports multiple sites/storefronts, shared catalogs and localized experiences. developer.salesforce.com

Its composable storefront approach also separates the frontend from commerce backend and provides scalable managed hosting. www.salesforce.com

I'd favor it particularly if your organization already runs Salesforce CRM, Marketing Cloud, Service Cloud, etc.

How I'd choose

The key architectural decision