Answers that do not mention BigCommerce

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

My quick recommendation:

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

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

If you tell me:

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

I can narrow it to one best fit.

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

How I’d compare them

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

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

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

My practical recommendation

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

WordPress + WooCommerce + a multi-vendor marketplace extension

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

That's especially true if you need things like:

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

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

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

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

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

My shortlist

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

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

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

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

What I'd do in your shoes

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

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

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

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

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

What I'd look at for a box business

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

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

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

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

My practical shortlist:

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

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

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

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

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

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

My practical shortlist:

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

My shortlist

If I were building a new custom store

I'd look at Medusa first.

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

A typical architecture would be:

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

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

When I'd choose the others

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

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

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

The important distinction

I'd divide your options like this:

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

→ WooCommerce / PrestaShop

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

→ Medusa / Vendure / Saleor

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

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

For a first serious store and someone who isn’t tech-savvy, I’d start with Shopify.

Why it fits a handmade-goods business:

• No coding required: you can start with a ready-made theme and customize it visually. www.shopify.com
• Built for selling: products, inventory, payments, shipping, orders, and customer information are all managed in one place. help.shopify.com
• Good room to grow: you can later add social selling, marketplaces, apps, and other sales channels without rebuilding your store. www.shopify.com
• You don't need to make it complicated: start with a simple theme, your best products, good photos, and basic shipping/payment settings.

Shopify vs. Wix

Wix is particularly beginner-friendly and offers AI-assisted store creation with no coding, so it’s worth considering if designing your website yourself is more important than having a commerce-first platform. www.wix.com

My practical suggestion: use Shopify if you expect your handmade shop to become a substantial business; use Wix if you mainly want a beautiful website that also sells a modest number of products.

Shopify's official online-store guide

If you tell me roughly how many products you have, your budget per month, and whether you already sell on Etsy or at markets, I can narrow it down to the simplest setup for you.

For a two-person boutique on a tight budget, I’d start with Square Online if you already use Square for in-person sales, or Big Cartel if you mainly need a simple online catalog/store.

• Square Online: $0/month on the Free plan; you pay payment-processing fees when you sell. It also syncs online and in-person inventory. Square Square
• Big Cartel: Free for up to 5 products; $15/month for up to 50 products on Platinum, with no platform transaction fees. Big Cartel Big Cartel
• Shopify: More powerful, but its standard plan starts substantially higher, so I wouldn't choose it purely for minimizing monthly costs. Shopify

My practical pick: Square if you have a physical shop/POS; Big Cartel if you're primarily selling a small curated collection online.

If you sell mostly digital downloads plus a smaller number of physical products, I’d narrow it to Shopify vs. WooCommerce.

My pick: Shopify

For your mix, Shopify is probably the easiest all-around choice.

• Digital downloads: Shopify’s free Digital Products app can automatically deliver PDFs, ZIPs, videos, templates, etc., with download limits and secure links. Shopify Shopify Help Center
• Physical products: You get inventory, shipping, variants, fulfillment, and the normal ecommerce features in the same store.
• Mixed products: You can sell a physical item with a digital download attached—for example, a physical workbook that also includes a PDF version. Shopify Help Center
• Mixed orders: Shopify separates digital and physical fulfillment, so customers can receive their download immediately while the physical portion is still being shipped. Shopify Help Center
• Growth: It's hosted and relatively low-maintenance, with a large ecosystem of apps if you later need email marketing, bundles, subscriptions, upsells, etc.

shopify.com

When I'd choose WooCommerce instead

WooCommerce is worth considering if you already have a WordPress site or want maximum control over your website.

It natively supports physical, virtual, and downloadable products, including products that combine shipping with a download. WooCommerce WooCommerce

The tradeoff is that you'll generally have more responsibility for hosting, WordPress updates, plugins, security, and maintenance.

woocommerce.com

Quick comparison

I wouldn't make Gumroad your primary store if physical products are an important part of the business; its strength is primarily the digital-product/creator side.

Bottom line: If you want one storefront that can handle both without much technical work, I'd start with Shopify. If you already have a WordPress site and enjoy having more control, WooCommerce is a strong alternative.

If you tell me roughly how many digital products you have, how many physical products, and your monthly sales/revenue, I can also compare the actual costs of Shopify, WooCommerce, Gumroad, and a couple of other options for your situation.

If you’re a solo entrepreneur selling custom T-shirts and your priority is “I don’t want to manage servers, hosting, updates, or infrastructure,” I’d lean toward Shopify.

My practical recommendation

shopify.com + a print-on-demand provider such as Printful or Printify.

Why it fits:

• Fully hosted: Shopify handles the storefront infrastructure, hosting, security, and platform maintenance.
• Built specifically for commerce: You get payments, checkout, inventory, orders, discounts, analytics, etc., without assembling a WordPress/WooCommerce stack.
• Excellent POD ecosystem: Shopify currently supports hundreds of print-on-demand integrations, and its own documentation specifically lists providers such as Printful. Shopify Shopify Help Center
• No inventory required: A POD provider can print and ship each shirt after the customer orders. Shopify
• Room to grow: You can start with a handful of designs and later add personalization, subscriptions, marketplaces, social selling, email marketing, etc.

Shopify vs. Wix

Wix is a perfectly viable alternative: it has built-in e-commerce hosting and POD integrations, including Printful and Printify. wix.com wix.com

I'd choose Wix if your business is primarily a personal/creative brand website with a relatively small shop. I'd choose Shopify if selling T-shirts is the core business.

What I'd actually build

For a one-person T-shirt business, I'd keep the stack simple:

Shopify → Printful/Printify → payment processor → customer

You design the shirts and market them. The platform handles the website/order infrastructure, while the POD supplier handles production and fulfillment. That gets you very close to a zero-server-management business. Shopify Shopify

If you tell me your approximate monthly sales target and whether customers customize the shirt themselves or you're selling pre-designed shirts, I can narrow this down to the most appropriate platform + POD setup.

For a small maker business (handmade goods, crafts, art, candles, jewelry, ceramics, apparel, etc.) that needs a simple POS + an online store, I’d usually narrow it to Shopify vs Square. The right pick depends mostly on where your sales happen. Shopify TechnologyAdvice

My short recommendation

Pick shopify.com if:

• Your goal is to build a brand and grow online
• You expect online sales to become a major part of the business
• You want a polished website, better product pages, email marketing, shipping tools, and room to expand
• You sell at craft fairs/pop-ups but want everything tied together in one inventory system

Shopify’s strength is ecommerce first, with POS added on. It’s generally the better fit for makers who want their website to become their main storefront. Shopify TechnologyAdvice

Pick squareup.com if:

• Most of your sales are in person
• You do farmers markets, craft fairs, pop-ups, studios, or a small physical shop
• You want the simplest setup and lowest upfront cost
• You mainly need a card reader, inventory, receipts, and a basic online presence

Square started as a POS/payment system, so it tends to feel simpler for occasional in-person selling. Fit Small Business TechnologyAdvice

How I’d choose for common maker scenarios

What about Etsy + Square?

That combo can work well early because Etsy provides marketplace discovery while Square handles in-person payments. The downside is that inventory, customer data, and branding are split between systems. Shopify

My default setup for a serious small maker in 2026:

• Starting out / mostly local: Square + Etsy
• Trying to build a long-term brand: Shopify + Shopify POS
• Already getting steady online traffic: Shopify from day one

A few details would change the answer:

1. What do you make (jewelry, food, clothing, art, etc.)?
2. Roughly what % of sales will be in person vs online?
3. Do you already sell on Etsy or are you starting from scratch?

For a small artisan selling both ready-made goods and custom items, these are strong fits:

• shopify.com — Best all-around/easiest setup. Use pre-order and made-to-order apps to show production windows, collect deposits, and manage custom items. Shopify supports pre-orders through apps with payment options such as full, partial, or later payment depending on setup. Shopify Help Center Shopify Help Center
• woocommerce.com — Best if you want more control. With WooCommerce Pre-Orders you can set availability dates, charge upfront or on release, and manage handmade or limited-run products. WooCommerce WooCommerce Add a lead-time plugin for “ships in 3–5 weeks” style messaging. Barn2 Plugins
• etsy.com — Good for artisan discovery, but custom lead-time workflows are less flexible than running your own store.

For your use case, I’d lean:

1. Shopify if you want simple operations and growth.
2. WooCommerce if your custom orders need detailed options, forms, or unusual workflows.
3. Etsy + Shopify/WooCommerce if you want marketplace traffic plus a dedicated shop.

Look for features like:

• per-product production times (“made in 2–4 weeks”)
• deposits or partial payments
• custom fields/options
• order notes and customer approvals
• preorder status emails
• ability to mix in-stock and made-to-order items

For a handmade business, avoid platforms that only handle “out of stock preorders” but cannot communicate custom production timelines.

Yes. If the client literally has $0 budget for hosting, you have several workable options.

Best options

• squareup.com — Probably the easiest choice for a normal physical-product store. The Free plan is $0/month, includes hosted ecommerce, SSL, checkout, inventory, and a Square-hosted URL. You pay payment-processing fees when something sells. Square Square
• bigcartel.com — Genuinely free for a tiny catalog: up to 5 products, with a hosted storefront and no monthly fee. Good for artists, merch, or a very small product line. Big Cartel Big Cartel
• ecwid.com — Useful if you're already building a static site and want to embed ecommerce into it. Its free offering is more limited, so I'd check the current product/payment limits before committing.
• pages.github.com + a payment provider — If you're comfortable coding, you can host the storefront itself for free on static hosting and use something like Stripe Checkout/payment links. This gives you much more design control, but you'll have to build more of the ecommerce functionality yourself.

What I'd do as a freelancer

If this is a real client store with products, cart, checkout, orders, etc., I'd lean toward Square Online Free. You can build the client a legitimate hosted store without asking them to pay for hosting, and the platform handles the infrastructure. Square explicitly says its free plan includes hosting and SSL. Square

The catch is that "free hosting" doesn't mean "free ecommerce." Payment processing still costs money when the client makes sales, and custom domains generally require a paid plan. Square

If you tell me what you're building it with (plain HTML/JS, React/Next.js, WordPress, etc.) and roughly how many products, I can suggest a completely $0/month architecture that you can hand off to the client.

For a small boutique with seasonal inventory and only occasional selling, I’d usually avoid paying for a full-featured ecommerce subscription year-round. The best fit depends on whether you need a “real store” all the time or just a place to sell during drops/seasons.

Here are the strongest low-cost options:

Shopify### My general picks by situation

• You sell a few seasonal collections (holiday, summer, pop-ups):

→ Big Cartel is often the sweet spot: inexpensive, simple, and not overloaded with features you won’t use.

• You sell mostly in-person and occasionally online:

→ Square Online is usually the easiest because inventory and payments can stay connected.

• You want to test whether online sales will work:

→ Etsy can be a low-commitment starting point, especially if you don’t have many SKUs.

• You plan to become a full-time boutique:

→ Shopify may justify the higher monthly cost because of its inventory, apps, and marketing tools.

A seasonal boutique should prioritize:

1. No large monthly fee during slow months
2. Easy product uploads/removals
3. Good photo presentation
4. Simple inventory tracking (sizes, colors, limited quantities)
5. Easy “collection drop” launches

For many occasional sellers, I’d start with Big Cartel or Square Online, then move to Shopify only when the store is selling consistently enough to justify the extra tools. Shopify

If you tell me roughly how many items you carry (e.g., 20 vs. 500 SKUs), whether you sell clothing, gifts, jewelry, etc., and whether you have a physical shop or only pop-ups, I can narrow it down.

If your goal is a storefront that costs $0/month and lets you sell products as preorders/crowdfunding campaigns, I’d narrow it to a few approaches:

My recommendation: Shopify + a free preorder/crowdfunding app

This is probably the best fit if you want something that can grow into a real store.

• Shopify gives you the actual storefront, checkout, product pages, order management, etc.
• Its App Store currently has 100+ preorder apps with crowdfunding functionality, including several with free plans. Shopify App Store Shopify App Store
• For example, Lift: Crowdfunding Presales is currently listed as free and is specifically designed for crowdfunding, presales, and product drops. Shopify App Store
• UpRank: Crowdfund & Preorders also has a free plan and is specifically designed around crowdfunding/preorders. Shopify App Store
• There are also free preorder apps if you don't need sophisticated crowdfunding mechanics. Shopify App Store

The catch: Shopify itself isn't permanently free, so if "$0 platform cost" is an absolute requirement, I'd look at a different setup.

If you mean literally free: I'd consider a simple storefront + payment link

For an initial crowdfunding campaign, you may not actually need a full ecommerce platform. A landing page can explain:

We're making X.
Goal: 500 units
Current commitments: 327
Estimated delivery: March 2027
Preorder — $49

Then send customers through a payment/checkout system.

That can be dramatically cheaper than building a conventional ecommerce store, particularly if you're validating whether people will actually buy.

One important distinction

There are really three different things people call "crowdfunding":

1. Preorder: Customer pays $50 now → you manufacture → ship the product later.
2. Deposit/pledge: Customer pays $10 now → pays the remaining $40 when production is confirmed.
3. True crowdfunding: Campaign has a funding target, deadline, backer tiers/rewards, progress bar, etc.

If you want #3, I'd specifically use a crowdfunding/preorder app rather than trying to fake it with a normal ecommerce product. Shopify's ecosystem now has dedicated apps for exactly this; for example, LaunchMate supports preorder, donation, hybrid, and tiered-backer campaigns, although its current plans are paid after a trial. Shopify App Store

If you tell me what you're selling and whether you need customers to pay 100% upfront or just pledge/deposit, I can give you a specific $0-cost stack and explain exactly how I'd set it up.

That can be dramatically cheaper than building a conventional ecommerce store, particularly if you're validating whether people will actually buy.

One important distinction

There are really three different things people call "crowdfunding":

1. Preorder: Customer pays $50 now → you manufacture → ship the product later.
2. Deposit/pledge: Customer pays $10 now → pays the remaining $40 when production is confirmed.
3. True crowdfunding: Campaign has a funding target, deadline, backer tiers/rewards, progress bar, etc.

If you want #3, I'd specifically use a crowdfunding/preorder app rather than trying to fake it with a normal ecommerce product. Shopify's ecosystem now has dedicated apps for exactly this; for example, LaunchMate supports preorder, donation, hybrid, and tiered-backer campaigns, although its current plans are paid after a trial.

For a tiny prospect-facing demo storefront with $0/month spend, I’d look at these:

• squareup.com — probably the simplest. Square has a $0/month Free plan with a hosted storefront, product catalog, checkout, shipping/pickup options, and hosting. You only incur payment-processing fees if you actually take payments. Square Square
• WooCommerce — free/open-source software, but you need WordPress hosting, so it isn't truly $0 unless you already have hosting.
• Ecwid — useful if you want to embed a small store into an existing agency/demo site; its free tier can be suitable for very small catalogs, though feature limits matter.
• Shopify — polished for demos, but generally better suited to a trial/prototype than a permanently free storefront.

For an agency demo, Square is particularly convenient: create 5–10 fictional products, brand the site for the prospect, and hand them a public storefront URL. You can leave checkout/payment processing unused, so the demo itself doesn't cost anything. Square

If you tell me whether you want (a) a public URL, (b) a fake checkout that never charges, or (c) a fully editable demo you can clone for each prospect, I can narrow it down to the most practical option.

For a photographer selling prints + digital downloads + licensing, I’d look first at Pixieset and Pic-Time. Both are built specifically around photography rather than being generic ecommerce platforms.

My shortlist

🥇 Pixieset — probably the easiest starting point

pixieset.com

Pixieset's free plan is genuinely usable: 3 GB storage, unlimited galleries, an integrated storefront, online payments and automatic print fulfillment. The tradeoff is a 15% commission on store sales. The Basic plan is currently $8/month when billed annually and removes the commission. Pixieset Pixieset

It supports print products, digital downloads and packages, so you could structure a gallery like:

• Digital download — web resolution
• Digital download — full resolution
• Fine-art print — various sizes
• Print + digital bundle
• Commercial image license — custom/negotiated

Pixieset Help CenterWhy I'd consider it: very little technical setup. You can have a polished photography storefront without building Shopify/WordPress yourself.

🥈 Pic-Time — particularly interesting for selling prints

pic-time.com

Pic-Time has a permanent free plan, and its Print Shop is included without a monthly fee. It can automatically fulfill prints through 30+ labs worldwide. The free plan has a 15% commission, while the Beginner plan is $7/month annually. Pic-Time Pic-Time Onboarding

It also has unusually good controls for digital-download packages, volume pricing, full-gallery pricing, and custom products. Pic-Time Help Center Pic-Time Help Center

That makes it attractive if you're selling photography more like art/stock/licensed imagery rather than simply delivering client galleries.

What about licensing?

This is the one area where I'd distinguish "selling digital files" from "selling licenses."

If by licensing you mean something like:

"Commercial use of this photograph for one print campaign, one year, North America, $500"

I'd want a platform where you can create a custom digital product/payment + license terms, rather than treating it as an ordinary photo download.

For a small photography business, you can keep the storefront on Pixieset/Pic-Time and handle unusual commercial licenses through a custom product/invoice and a separate license agreement. That avoids paying for a much more complicated stock-photo platform before you actually need one.

What I'd choose

Starting out / keeping costs near zero: Pixieset Free.

Print-heavy fine-art photography: Pic-Time Free, especially if automated lab fulfillment matters.

Regular commercial licensing: I'd use Pixieset or Pic-Time for the storefront and galleries, but build a more explicit licensing workflow around them rather than relying on a generic "download" product.

If you tell me roughly how many images you have, whether you're selling fine-art prints vs. client prints, and what kind of licensing (editorial/commercial/stock), I can narrow this down to the most economical setup and show you exactly how I'd structure the store.

For a tight-budget, headless-first shop, I’d put Medusa at the top of the evaluation list.

• Medusa — particularly compelling if your team is comfortable with TypeScript/Node. Its managed Cloud starts at $29/month, has 0% GMV fees, and includes backend + storefront hosting. You can also self-host, so you retain an escape hatch if infrastructure costs become important. docs.medusajs.com
• Saleor — very capable GraphQL/headless option, with an open-source version you can self-host. However, its managed Cloud pricing is currently much higher, starting at $1,599/month, so it makes more sense if you specifically value its architecture/features or have the engineering resources to self-host. saleor.io
• Shopify + Hydrogen — worth evaluating if minimizing engineering/operations work matters more than minimizing platform cost. It's generally a different tradeoff: managed commerce infrastructure and ecosystem versus greater platform dependence.

My evaluation shortlist

For a small team, I'd prototype the same simple store in Medusa and Shopify/Hydrogen, then compare the actual monthly cost and developer effort. Medusa's $29 Cloud entry point makes that experiment relatively inexpensive. docs.medusajs.com

If you tell me your expected monthly orders, SKU count, and frontend stack (e.g. Next.js), I can narrow this to a concrete low-cost architecture and estimated monthly bill.

If you’re testing one product for a few weeks and want $0/month recurring cost, I’d avoid full Shopify-style setups at first. You mainly need:

• a focused landing page
• checkout/payment link
• basic order handling
• no monthly subscription

Good options:

For a 2–4 week product validation test, I’d probably choose:

1. Physical product: Square Online or Corpus + Stripe
2. Digital product: Payhip
3. Ad-testing landing page first (before building a store): Zoho LandingPage + payment link

A simple test stack could be:

• Landing page: free builder
• Checkout: Stripe Payment Link
• Analytics: Google Analytics or the landing page’s built-in analytics
• Traffic: organic posts or small ad test

I would avoid starting with Shopify unless you already know the product sells, because the monthly subscription becomes a fixed cost before you have proof of demand.

I’d start with itch.io for a budget-friendly indie game storefront. It supports direct game downloads, paid sales, downloadable license/access keys, bulk keys for press/promotions, and optional Steam-key distribution. itch.io itch.io

• itch.io: Best low-cost all-in-one option; no upfront storefront cost, flexible revenue share, hosting included. itch.io
• Gumroad: Simple direct-sales alternative; currently 10% + $0.50 per direct transaction, with tax handling included. Gumroad
• Own store + specialized delivery: More control, but more setup and hosting complexity.

For a solo/indie dev selling downloads + license/Steam keys, itch.io is probably the simplest starting point. itch.io

For a small handmade-goods shop, tight budget, and maximum control, I’d start with WooCommerce on self-hosted WordPress.

Why it fits:

• No platform subscription or per-order fee — WooCommerce itself is open source; you mainly pay for hosting, your domain, payment processing, and any optional extensions. woocommerce.com
• Easy to self-host — unlike headless platforms such as Medusa or Saleor, you get a complete storefront and admin rather than having to build the frontend yourself. www.opensourcegroups.com
• Huge ecosystem for payments, shipping, taxes, product variations, coupons, email, SEO, etc.
• Excellent for handmade products where you might need variants such as size/color, inventory counts, made-to-order products, and custom shipping rules.
• You retain control of your site, database, code, and hosting, and WooCommerce exposes a REST API for further customization. woocommerce.com

The alternatives

PrestaShop is probably the main alternative I'd investigate. Its current open-source version is fully self-hostable and includes catalog, inventory, orders, shipping, payments, SEO, and customization capabilities. prestashop.com

I wouldn't start with Medusa or Saleor for a tiny shop unless you're already comfortable developing software. They're powerful API/headless systems, but you'll generally take on considerably more development and operational work than with WooCommerce. openbusinessnetwork.online

A very cheap setup

I'd aim for:

Your domain → inexpensive Linux hosting/VPS → WordPress → WooCommerce → free/lightweight theme → Stripe/PayPal → automated backups

The important caveat is that open source doesn't mean zero cost. Hosting, payment processing, backups, security updates, and occasional paid plugins can still cost money. www.velsof.com

If you tell me roughly how many products you have, whether they're made-to-order, and whether you're comfortable with Linux/Docker, I can narrow this down to a specific stack and a realistic $/month self-hosting budget.

For a 10-person engineering team building a high-traffic headless storefront, I’d shortlist Medusa, Saleor, and Vendure. I’d lean toward Medusa if your team is primarily TypeScript/React, but the architecture and API preferences matter more than a generic “best platform” label.

Medusa describes its core as a customizable commerce framework with modules for DTC, B2B, marketplaces, etc. GitHub Saleor is GraphQL-first and currently documents a stack designed for composable/headless deployments; its site also reports production deployments handling very large API volumes. Saleor Saleor Vendure is TypeScript/NestJS/GraphQL and explicitly supports self-hosting on Docker/Kubernetes/cloud infrastructure. GitHub

What I'd choose for your situation

1. Medusa — my default shortlist choice

For a 10-person startup, the big advantage is that your storefront and commerce backend can live comfortably in the same TypeScript ecosystem. That reduces context switching and makes it relatively straightforward to implement custom pricing, promotions, checkout logic, integrations, and asynchronous workflows.

It's also modular rather than forcing you into a giant monolithic commerce suite. GitHub

For high traffic, I'd architect it roughly as:

CDN → Next.js/React storefront → cache → Medusa API → PostgreSQL + Redis → async workers → external services

Don't interpret "high traffic" as requiring the commerce API itself to handle every storefront request. Cache aggressively at the storefront/CDN layer and keep the transactional path—cart, checkout, inventory, order creation—much smaller.

2. Saleor — seriously consider it if GraphQL is central

Saleor is attractive if your team likes Python/Django and wants a GraphQL-native commerce API. Its current open-source stack includes the API, dashboard, extensions/apps, and composable storefront tooling. Saleor

One particularly interesting data point for your use case is Saleor's published infrastructure scale: its site currently reports deployments handling 1B+ API requests/month and hundreds of thousands of orders/month. That doesn't mean your deployment automatically scales that way, but it is evidence that the architecture is intended for substantial traffic. Saleor

I'd favor it when GraphQL + sophisticated multi-channel/B2B commerce are more important than having an all-TypeScript stack.

3. Vendure — strong choice for a structured TypeScript team

Vendure is also a very natural fit for a React/TypeScript startup. It uses NestJS and GraphQL and has a plugin-oriented architecture. GitHub

I'd put it especially high on the list if you expect the commerce domain to become complicated—multiple channels, B2B, marketplace functionality, subscriptions, custom business rules—and you want more architectural structure imposed by the framework.

The decision I'd make

If you told me only:

10 engineers + high-traffic + headless + open source + startup

I'd start with Medusa and Vendure, then add Saleor if your team is comfortable with Python/GraphQL.

The more important question is actually what kind of "high traffic" you mean. A storefront getting 100k requests/minute is a very different engineering problem from a catalog with 10 million SKUs or a checkout system processing 1,000 orders/minute.

If you give me your approximate peak requests/minute, SKU count, orders/minute, B2C vs B2B, and whether your team is TypeScript or Python, I can give you a much more concrete architecture comparison—including where I'd put Redis, Postgres replicas, search, CDN caching, queues, and inventory so you don't accidentally make the commerce backend your bottleneck.

If your priorities are solo-founder friendly + modern admin + easy theming, I’d narrow it to Medusa, Vendure, and Saleor rather than the older all-in-one platforms.

My practical shortlist

Medusa

For your particular situation, Medusa is probably the first one I'd investigate.

Its admin is genuinely modern: it has light/dark themes, search, configurable layouts, and can be extended with custom admin pages/widgets. Medusa Docs Medusa Docs Medusa Docs

The storefront is deliberately separate from the commerce backend, so you can use a React/Next.js frontend and essentially make the customer-facing site look however you want. Medusa also provides a Next.js starter with a fairly polished starting design. Medusa Docs Medusa Docs

The catch for a low-code founder is that headless means you're still responsible for the storefront. You don't get the same "pick a theme, change colors, publish" experience that you get from Shopify or WooCommerce.

Vendure

I'd put Vendure very close to Medusa if you're comfortable with TypeScript.

Its current dashboard has a modern theming system based around CSS variables/Tailwind, and you can customize the dashboard's appearance. Vendure Developer Hub

It's particularly interesting if you expect to eventually need sophisticated commerce logic. The tradeoff is that you're still dealing with a developer-oriented headless system rather than a turnkey merchant platform.

Saleor

Saleor has an excellent modern architecture and very capable dashboard/API, with built-in concepts for things like channels, promotions, multi-region selling, and dashboard extensions. Saleor Documentation

But for a solo founder with limited development experience, I'd be cautious about choosing it solely because it looks polished. Its Python/Django + GraphQL architecture introduces a different technical stack, whereas Medusa keeps you in the JavaScript/TypeScript ecosystem. Eryx Innovations Lab

The important distinction

If by "easy theming" you mean:

"I want to install a theme, change fonts/colors/layout, add products, and mostly stay out of code."

Then I would actually look at WooCommerce or Shopware before these headless platforms.

If you mean:

"I want a modern-looking storefront that I can heavily customize without fighting the platform."

Then Medusa is the one I'd prototype first.

The architecture is essentially:

Medusa → products/orders/payments/commerce logic
Next.js → your actual website/design

That separation is what makes the theming flexible, but it's also what makes Medusa more technical than Shopify/WooCommerce. Medusa Docs

For a solo founder, I'd test one thing before committing: take your desired homepage/product page design and try rebuilding it with Medusa's starter. If you can get ~80% of your desired look without needing custom backend code, you've probably found a good fit.

If you tell me what you're selling (physical products, digital products, subscriptions, marketplace, etc.) and whether you want to use a visual builder, I can narrow this down to 2–3 platforms and explain the actual setup effort.

For a self-hosted subscription-box business, I’d narrow it to WooCommerce or Medusa, depending on how much custom engineering you want.

My practical recommendation: WooCommerce

woocommerce.com

If your priority is getting a subscription box operational without building the billing system yourself, WooCommerce is the safer choice.

• WooCommerce itself is open source and self-hostable.
• WooCommerce Subscriptions adds recurring billing, automatic renewals, trials, signup fees, expiration, billing-date alignment, and subscription management. WooCommerce WooCommerce
• It supports automatic recurring payments through compatible payment gateways and has a documented failed-payment retry system. WooCommerce WooCommerce
• It's particularly well suited to physical subscription boxes because recurring orders can drive your normal inventory and fulfillment workflow. WooCommerce
• The downside: the subscription functionality itself is a paid extension, so it isn't a completely free/open-source subscription stack. WooCommerce

If you're building a custom product: Medusa

docs.medusajs.com

Medusa is more attractive if you're a developer and want a headless, API-first commerce backend with your own frontend and business logic.

The important caveat is that subscriptions aren't native. Medusa's own documentation provides a recipe for implementing subscriptions, including automatic renewal, expiration, customer cancellation, and Stripe-based recurring payments. Medusa Docs

So you'd be building/maintaining more of the subscription infrastructure yourself.

For a subscription box specifically, I'd start with WooCommerce unless you have a strong reason to build a headless/custom stack.

One architectural point I'd strongly recommend: let Stripe/payment infrastructure handle the actual recurring payment authorization rather than trying to store cards and implement recurring charging yourself. WooCommerce's ecosystem supports both site-initiated renewals and, in some configurations, Stripe Billing's off-site billing engine. WooCommerce

If you tell me your stack (PHP/Node/etc.), expected subscribers, Stripe vs. another processor, and whether customers can customize their box, I can give you a more specific architecture recommendation.

For an enterprise team prioritizing scalability, containerized deployment, and long-term control, I’d shortlist Medusa, Saleor, and Vendure rather than traditional monolithic platforms. Current comparisons consistently identify these as the major open-source headless options. Vendure Pawel Owerczuk

My recommendation: Medusa

For a greenfield enterprise deployment, I'd generally start with Medusa if your engineering organization is already strong in TypeScript/Node.js. Its modular architecture makes it well suited to separating services and scaling workloads horizontally, while its API-first/headless model works naturally with Kubernetes, containers, independent storefronts, and surrounding microservices. Recent production comparisons also report an active ecosystem and substantial contributor base. Pawel Owerczuk

A typical deployment could look like:

                    ┌───────────────┐
                    │ CDN / WAF     │
                    └───────┬───────┘
                            │
                    ┌───────▼───────┐
                    │ Next.js / Web │
                    └───────┬───────┘
                            │
              ┌─────────────▼─────────────┐
              │       Kubernetes          │
              │                           │
              │  Medusa API pods          │
              │  Worker pods              │
              │  Custom commerce modules  │
              └──────┬─────────┬──────────┘
                     │         │
              ┌──────▼───┐ ┌──▼──────┐
              │PostgreSQL│ │ Redis   │
              └──────────┘ └─────────┘

Choose Saleor instead if your organization is predominantly Python/Django and wants a GraphQL-first commerce platform with substantial built-in enterprise/B2B functionality. Pawel Owerczuk Eryx Innovations Lab

Choose Vendure instead if you're a TypeScript/NestJS organization that particularly values its plugin architecture and structured backend. One important consideration is its GPLv3 licensing model, versus the more permissive licensing associated with Medusa's core, so enterprise legal review matters. Pawel Owerczuk

So, assuming TypeScript + Kubernetes + high customization + enterprise scale, my shortlist would start with Medusa, with Saleor as the main alternative for a Python/GraphQL organization. This is a fit-based recommendation rather than a universal ranking—the architecture and team stack should drive the final choice. Vendure

If your priority is specifically the largest plugin/extension ecosystem plus an active developer community, I’d put WooCommerce at the top.

Why WooCommerce

WooCommerce benefits from the enormous WordPress ecosystem: there are thousands of extensions, themes, payment integrations, shipping integrations, and developer resources. Current 2026 comparisons continue to identify it as having the broadest open-source ecommerce ecosystem. Toolradar OSSAlt

Its development is also quite transparent: the WooCommerce GitHub monorepo contains the core plugins, packages, and tools, with public issues and contributions. GitHub

The main downside is that the ecosystem's size can also mean plugin conflicts, inconsistent quality, security/maintenance burdens, and upgrade headaches. A recent 2026 security incident involving a WooCommerce extension illustrates why extension vetting and timely updates matter. TechRadar

The important alternative: Magento Open Source

If by "plugin ecosystem" you mean deep, sophisticated extension architecture for developers, rather than simply the largest number of plugins, Magento Open Source deserves serious consideration.

Adobe says its marketplace has thousands of extensions, and its extension ecosystem includes formal quality checks. Experience League Adobe Commerce Developer Portal Magento also has a substantial developer community, documentation, GitHub activity, forums, and Stack Exchange resources. Adobe Business Adobe Developer

The tradeoff is substantially greater complexity. Magento makes more sense when you're building a large catalog, complex pricing/catalog rules, multiple stores, B2B functionality, or highly customized commerce workflows.

If you're a modern JS/TS developer

I'd look at Medusa or Vendure instead. They're much more developer-oriented and API/headless by design, but their extension ecosystems are nowhere near WooCommerce's maturity and breadth. Current 2026 comparisons describe Medusa and Vendure as particularly strong options for TypeScript/Node teams. Toolradar OpenReplay Blog

Bottom line:

• Maximum ecosystem + community: WooCommerce
• Deep enterprise extension architecture: Magento Open Source
• Modern TypeScript/headless development: Medusa or Vendure
• Python/GraphQL: Saleor
• Traditional PHP ecommerce: PrestaShop

If you tell me your stack (PHP/Node/Python), store size, and whether you're building a monolith or headless, I can narrow this down to the platform that fits your development workflow.

WooCommerce benefits from the enormous WordPress ecosystem: there are thousands of extensions, themes, payment integrations, shipping integrations, and developer resources. Current 2026 comparisons continue to identify it as having the broadest open-source ecommerce ecosystem. Toolradar OSSAlt

Its development is also quite transparent: the WooCommerce GitHub monorepo contains the core plugins, packages, and tools, with public issues and contributions. GitHub

The main downside is that the ecosystem's size can also mean plugin conflicts, inconsistent quality, security/maintenance burdens, and upgrade headaches. A recent 2026 security incident involving a WooCommerce extension illustrates why extension vetting and timely updates matter. TechRadar

The important alternative: Magento Open Source

If by "plugin ecosystem" you mean deep, sophisticated extension architecture for developers, rather than simply the largest number of plugins, Magento Open Source deserves serious consideration.

Adobe says its marketplace has thousands of extensions, and its extension ecosystem includes formal quality checks. experienceleague.adobe.com commercedeveloper.adobe.com Magento also has a substantial developer community, documentation, GitHub activity, forums, and Stack Exchange resources. business.adobe.com developer.adobe.com

The tradeoff is substantially greater complexity. Magento makes more sense when you're building a large catalog, complex pricing/catalog rules, multiple stores, B2B functionality, or highly customized commerce workflows.

If you're a modern JS/TS developer

I'd look at Medusa or Vendure instead. They're much more developer-oriented and API/headless by design, but their extension ecosystems are nowhere near WooCommerce's maturity and breadth. Current 2026 comparisons describe Medusa and Vendure as particularly strong options for TypeScript/Node teams.

For a low-traffic boutique store with a non-technical owner, I’d generally look at WooCommerce first among self-hosted options—but the hosting setup matters almost as much as the software.

Practical comparison

Why WooCommerce: the day-to-day interface is familiar to many small-business owners, and there is a large ecosystem of themes, payment integrations, and hosting providers. Its downside is that you're maintaining WordPress + WooCommerce + themes + plugins, so updates and compatibility can become the main maintenance issue. WooCommerce itself recommends regular updates, backups, and ideally testing updates on staging. WooCommerce WooCommerce

PrestaShop is more purpose-built for ecommerce, but its current requirements are somewhat more involved—for example, PrestaShop 9 recommends PHP 8.4 and at least 512 MB of PHP memory. PrestaShop Help Center PrestaShop

The important distinction

If by self-hosted you mean "I want control over the server and software, but I don't want to be a Linux administrator," I'd use:

WooCommerce + managed WordPress hosting + automatic backups + a very small plugin set.

That gives the owner a relatively simple admin experience while the host handles much of the server-level work. WooCommerce's own documentation explicitly recommends contacting the hosting provider for things such as PHP upgrades. WooCommerce

If you mean "I will personally administer the VPS/server," then I would not call any of these particularly easy for a non-technical owner. The server, PHP, database, HTTPS, backups, security updates, and application updates all become your responsibility.

For a boutique with, say, 20–500 products and tens to a few hundred orders per month, I would keep the stack deliberately boring: WooCommerce, one lightweight theme, one payment gateway, shipping integration, automated backups, and as few plugins as possible. That minimizes the most common WooCommerce troubleshooting source: conflicts between outdated software, themes, and plugins. WooCommerce

If you tell me your budget and whether you're comfortable managing a VPS, I can narrow this down to a specific self-hosted stack.

For a small SaaS store selling software licenses, I’d look at headless/self-hosted commerce platforms rather than traditional ecommerce packages. The key architectural question is whether the ecommerce system should own billing/subscriptions, or whether something like Stripe Billing/Chargebee/Paddle should remain the source of truth.

The main options

Medusa is probably the first one I'd investigate for your particular use case. It has a modular architecture and a native Stripe payment provider, while its documentation explicitly provides a recipe for implementing recurring subscriptions with Stripe, including renewals, expiration, cancellation, and subscription management. docs.medusajs.comdocs.medusajs.com

The important caveat is that Medusa does not natively provide subscription billing as a first-class commerce primitive. Its own documentation describes subscriptions as something you implement on top of the platform. docs.medusajs.comdocs.vendure.ioapps.saleor.io

The architecture I'd consider

For SaaS licenses, I'd separate commerce from billing:

                 ┌──────────────────┐
                 │   Your SaaS      │
                 │   application    │
                 └────────┬─────────┘
                          │
                    license / entitlements
                          │
                 ┌────────▼─────────┐
                 │ License Service  │
                 └────────┬─────────┘
                          │
        ┌─────────────────┴─────────────────┐
        │                                   │
┌───────▼────────┐                  ┌───────▼────────┐
│    Medusa      │                  │ Stripe Billing │
│  product/cart  │                  │ subscriptions  │
│  checkout/order│                  │ invoices       │
└───────┬────────┘                  └───────┬────────┘
        │                                   │
        └───────────────┬───────────────────┘
                        │ webhooks
                 ┌──────▼───────┐
                 │ Your SaaS DB │
                 └──────────────┘

That gives you a useful separation:

• Medusa: products, license SKUs, checkout, orders, coupons, customer/storefront experience.
• Stripe Billing: recurring charges, invoices, payment methods, failed-payment handling, renewals.
• Your application: license issuance, activation, seats, entitlements, expiration, upgrades/downgrades.
• Webhooks: synchronize Stripe → your SaaS and Medusa → your SaaS.

Medusa already has a payment-module abstraction and Stripe provider, so this isn't fighting its architecture. docs.medusajs.com

Why I'd lean away from making ecommerce own subscriptions

For a SaaS company, the actual commercial object isn't really an "order." It's something like:

Customer → subscription → entitlement → license/seats

For example:

Acme Corp
   │
   └── Pro Annual
         │
         ├── Stripe subscription
         ├── 25 seats
         ├── License: ABCD-...
         └── expires: 2027-09-18

That model maps much more naturally onto Stripe Billing + your own entitlement system than trying to turn an ecommerce database into your SaaS billing database.

Where Vendure fits

I'd seriously consider Vendure if your engineering team is TypeScript/NestJS and you want a highly customizable commerce backend. Its plugin architecture is particularly interesting for license provisioning and SaaS-specific workflows. There are already subscription-oriented plugins/integrations in its ecosystem. docs.vendure.io

Where Saleor fits

Saleor is attractive if you're comfortable with Python/GraphQL and want a more platform-oriented commerce system. Its Stripe integration is mature and available for self-hosted deployments. apps.saleor.io

For a small store attached to an existing SaaS, though, I'd be cautious about adopting a larger commerce platform than you actually need.

My shortlist would therefore be:

1. Medusa + Stripe Billing + your license/entitlement service
2. Vendure + Stripe Billing + your license/entitlement service
3. Saleor + Stripe Billing + your license/entitlement service

The deciding factor between the first two is largely Medusa's workflow/module model vs. Vendure's plugin/GraphQL model, rather than basic ecommerce capability. kryeo.com

If you tell me what billing system you already use (Stripe, Chargebee, Paddle, Recurly, etc.) and your stack (Node/Python/PHP/etc.), I can narrow this down considerably and sketch the integration architecture.

For a solo developer selling downloadable software with paid licenses and ongoing updates, I’d structure the decision around two separate jobs:

1. E-commerce: checkout, taxes, invoices, subscriptions/refunds.
2. Software distribution: license generation/activation, customer entitlements, and delivering the correct software version.

My shortlist

I'd pick Lemon Squeezy for your use case

Lemon Squeezy has native license-key generation, activation limits, license expiration, and an API for validating/revoking licenses. Keys can also follow a subscription's lifecycle. Lemon Squeezy Docs Lemon Squeezy Docs Lemon Squeezy Docs

docs.lemonsqueezy.com

The architecture I'd use is:

                    ┌──────────────────┐
                    │   Your website   │
                    └────────┬─────────┘
                             │
                         Checkout
                             │
                    ┌────────▼─────────┐
                    │  Lemon Squeezy   │
                    │                  │
                    │ • Payment       │
                    │ • Tax           │
                    │ • License key   │
                    │ • Customer      │
                    └────────┬─────────┘
                             │ webhook
                             ▼
                    ┌──────────────────┐
                    │ Your API/backend │
                    │                  │
                    │ • entitlement    │
                    │ • releases      │
                    │ • download auth │
                    └────────┬─────────┘
                             │
                             ▼
                    ┌──────────────────┐
                    │ Versioned files │
                    │                  │
                    │ v1.0.0          │
                    │ v1.1.0          │
                    │ v1.2.0          │
                    └──────────────────┘

The important distinction is that I wouldn't make the ecommerce platform your software-update system.

Instead, let Lemon Squeezy answer:

"Did this person buy a license, and is it valid?"

And let your own small update service answer:

"What version is this customer entitled to download?"

That gives you considerably more flexibility.

For example

Your customer buys:

MyApp Pro — $79, includes 12 months of updates

Lemon Squeezy generates:

XXXX-XXXX-XXXX-XXXX

Your application sends the key to your API:

POST /license/activate

Your API verifies the license and returns something like:

{
  "valid": true,
  "product": "pro",
  "updates_until": "2027-09-18",
  "latest_version": "3.4.1"
}

Then the application checks:

GET /updates/latest

and your server determines whether that customer can download 3.4.1.

This makes "license valid" and "entitled to updates through version X" separate concepts.

What about Gumroad?

Gumroad is also viable. Its documentation explicitly supports software license keys, API verification, multi-seat licenses, and product versions. Gumroad

So if your requirements are essentially:

Buy → receive key → download software

Gumroad can work very well.

I'd lean toward it if your product is more like a simple downloadable digital product and you don't need much custom licensing infrastructure.

For a software product with a serious update/entitlement system, however, I'd rather have the more software-oriented architecture above.

When I'd use Paddle instead

Paddle becomes more interesting if you're building toward a larger SaaS/business operation with sophisticated recurring billing, invoicing, and subscription management.

The tradeoff is that you'd generally be adding another component for the actual license-management layer rather than getting the license-key functionality directly from the commerce platform.

So for a solo developer, Paddle + separate licensing service can be more infrastructure than you actually need initially.

One important caveat: "versioned downloads"

If by versioned downloads you mean:

Customer bought v2.0, gets v2.0 forever, but customers who bought the "1 year of updates" plan can download v2.1, v2.2, etc.

then don't model this purely as product versions in the storefront.

I'd create an entitlement model such as:

Customer
  └── License
       ├── product = MyApp Pro
       ├── seats = 2
       ├── purchased = 2026-09-18
       ├── updates_until = 2027-09-18
       └── channel = stable

and releases:

Release
  ├── version = 2.0.0
  ├── released = 2026-09-18
  └── minimum_entitlement = none

Release
  ├── version = 2.1.0
  ├── released = 2026-11-02
  └── requires_updates_through = 2026-11-02

That gives you a very clean model for perpetual licenses + paid update periods, which is a common desktop-software business model.

Bottom line

For one person selling desktop software directly from their website, I'd start with:

Lemon Squeezy → license generation/validation → tiny custom entitlement API → object storage/CDN for versioned binaries.

You get the difficult commerce/tax/license pieces without having to build a complete ecommerce backend, while retaining control over the part that matters most for software: who can download which version. Lemon Squeezy Docs Lemon Squeezy Docs

If you tell me what kind of software you're selling (Windows/macOS/Linux, plugin, CLI, etc.) and whether updates are free forever or paid annually, I can sketch the exact architecture and database/API I'd use.

For your use case, I’d look at course-first platforms that also handle ecommerce and digital downloads, rather than trying to bolt an LMS onto Shopify/WooCommerce.

Best fits

Teachable is particularly well aligned with what you described. It supports online courses and digital downloads in the same platform, and downloads can be sold separately, bundled with courses, or used as upsells. Teachable Teachable Help Center

It also has native course-completion certificates, which can be automatically or manually issued. Teachable Help Center Its integrations include Stripe, PayPal, Zapier, Mailchimp, Google Analytics and others. Teachable Teachable

Thinkific is another strong choice if the learning experience is the center of the business. It supports downloadable products such as PDFs, templates, audio and other files, and its certificates can be automatically issued upon course completion. Thinkific Thinkific Support It can also integrate with Accredible if you need more sophisticated/verifiable credentials. Thinkific App Store

Kajabi is attractive if you're planning a larger marketing funnel around the course—landing pages, email automation, upsells, memberships, etc.—while also selling downloadable products. Kajabi

My practical recommendation

For a launch consisting of:

Course → downloadable workbook/templates/resources → completion certificate → payment/checkout

I'd shortlist Teachable and Thinkific first. They let you keep the student, course, payment, download, and certificate experience in one ecosystem rather than stitching together an ecommerce store + LMS + file-delivery service + certificate provider.

If you tell me your expected number of students, course price, whether you need subscriptions/memberships, and whether certificates need verification/accreditation, I can narrow this down to the most appropriate setup and compare the current pricing/transaction fees.

Lemon Squeezy fits this use case particularly well. It provides license keys/entitlements, subscription-linked access, customer downloads, and securely signed/throttled download links. You can replace uploaded files with each release so existing customers receive the latest version. LemonSqueezy Lemon Squeezy Docs

Gumroad also supports license verification, but more of the entitlement enforcement is left to your application. gumroad.com

For an enterprise selling large datasets, I’d look at this as a secure data-delivery / managed file transfer (MFT) problem rather than conventional ecommerce. You want customer-level permissions, expiring access, download tracking, audit trails, and ideally SIEM/API integration.

Strong candidates

Files.com is particularly aligned with your requirements: its enterprise offering supports SSO/SCIM/RBAC, granular permissions, and audit logs covering logins, file activity, permissions and protocol sessions. It can stream events to SIEM systems and provides reports for permissions, login history, shares and usage. Files.com Files.com Files.com

files.com

SFTPGo Enterprise is compelling if your customers are technically sophisticated and expect SFTP/SCP/WebDAV/API access. Its audit trail records downloads/uploads, paths, usernames, timestamps, IPs and statuses, while its permission model can restrict users at the directory level. SFTPGo Documentation SFTPGo Documentation

docs.sftpgo.com

For a dataset marketplace with a custom customer portal, I'd instead consider object storage underneath your application. Cloudflare R2, for example, supports presigned URLs with object-specific operations and expiration, while its Data Access Logs provide per-request records. One caveat is significant for compliance: Cloudflare explicitly says those access logs are asynchronous/best-effort and can be delayed or omitted, so I wouldn't make them your sole authoritative audit trail. Cloudflare Docs Cloudflare Docs

developers.cloudflare.com

What I'd architect

For your use case, I'd generally separate commerce, authorization, delivery, and audit:

Customer → Your portal → Entitlement/permissions → Files.com or object storage → Dataset

with every access generating something like:

customer_id | user_id | dataset_id | file/object | action | timestamp | IP | bytes | success/failure | access_method

That gives you analytics such as:

• Which customers have access to each dataset?
• Which users downloaded it?
• How many times?
• How many GB did they consume?
• Which datasets are actually being used?
• When does a customer's entitlement expire?
• Who generated or revoked a share?
• Which downloads failed or were denied?
• Can security/auditors reconstruct a customer's entire access history?

My practical shortlist would be Files.com vs. SFTPGo Enterprise vs. custom portal + R2/S3. If you tell me whether your datasets are typically GBs, hundreds of GBs, or TBs+, and whether customers need browser downloads, API access, SFTP, or all three, I can narrow this down to an appropriate architecture and compare the permission/audit models in detail.

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

1. Payhip — probably the simplest fit

payhip.com supports PWYW directly: you can set a product to 0+ for completely optional payment, or 5+ for a $5 minimum with customers free to pay more. It supports digital products and automatically delivers downloads. Payhip Help Center Payhip Help Center Payhip

For example, a zine could be:

Digital Zine — $5 or more
Pay what you can. If you'd like to support the project, you can choose a higher amount.

Payhip's current pricing starts at $0/month + 5% transaction fee, with paid plans reducing or eliminating the platform transaction fee. Payhip

2. Gumroad — particularly good for creator/music sales

gumroad.com also has native PWYW. You can set a minimum amount and a suggested amount, and customers can enter whatever they'd like to pay above the minimum. It also supports a $0 minimum, allowing genuinely free downloads with optional payment. Gumroad

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. Gumroad

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products. WooCommerce WooCommerce

That's attractive if you eventually want something like:

• Zine: $3 minimum / $7 suggested / unlimited maximum
• Album: $5 minimum / $10 suggested
• Free sampler: $0+
• Separate "Support the artist" contribution
• Your own domain and storefront
• More control over branding and checkout

The tradeoff is that you're managing WordPress/WooCommerce and paying for extensions rather than getting the whole system in one hosted package.

My practical take

For a small independent publishing/music project, I'd start with Payhip if the priority is "get this working with minimal technical overhead." Its 0+ / 5+ pricing model maps almost exactly to what you're describing.

I'd choose Gumroad if you particularly value the creator-oriented marketplace/discovery ecosystem.

I'd choose WooCommerce if you want the store to become a substantial part of your own website and want maximum control over the pricing and donation experience.

One important distinction: if by "optional donations" you mean someone can buy a $5 zine and then add an entirely separate $10 donation at checkout, rather than simply letting them pay $15 for the zine, I'd verify that specific checkout flow before choosing. PWYW handles the latter very well; a separate donation field is a slightly different requirement.

Its current direct-sale fee is 10% + $0.50 per transaction, with a higher fee for sales through its Discover marketplace. gumroad.com

3. WooCommerce — best if you want your own storefront

If you already have WordPress, WooCommerce + Name Your Price gives you substantially more control. The official extension supports customer-entered prices, suggested prices, minimums, and donations, and it works with both simple and variable products.

That's attractive if you eventually want something like:

I’d shortlist commercetools, Saleor, and Medusa—with commercetools the strongest fit for an enterprise-grade, highly decoupled checkout.

• commercetools — API-first/composable, with a dedicated Checkout API supporting both fully custom checkout and payment-only flows. Strong choice if checkout needs to evolve independently of the frontend and integrate multiple channels. commercetools Documentation commercetools Documentation
• Saleor — GraphQL-native and fully headless, with checkout, payments, shipping, and extensibility exposed through APIs. Particularly attractive if you want maximum frontend/BFF control and open-source flexibility. Saleor Documentation Saleor Commerce
• Medusa — Very developer/customization-oriented; storefronts are separate applications and commerce operations are exposed through APIs. Good if you want to own more of the checkout implementation. Medusa Docs Medusa Docs

Architecture-wise: I’d put a Checkout BFF/service between your frontend(s) and commerce platform, rather than letting the frontend directly orchestrate carts, payments, shipping, promotions, and order creation. That gives you freedom to swap frontend frameworks/channels—and potentially commerce components—without rewriting checkout.

If you tell me your scale, B2C/B2B, payment provider(s), and whether you want SaaS vs self-hosted, I can narrow this to an architecture recommendation.

Yes. If multi-seller marketplace behavior is a core requirement, I’d narrow the field to a few API-first platforms rather than generic headless commerce engines.

1. Mirakl — most marketplace-native

Mirakl is somewhat different from the others: marketplaces are its primary use case, rather than something you construct on top of a commerce engine.

Its Marketplace Platform exposes separate Front, Operator, and Seller APIs, covering things such as offers, orders, seller operations, and marketplace interactions. Mirakl Developer Portal Mirakl Developer Portal

It also supports seller onboarding/management and seller portals, and its current platform supports integrations through API, CSV, XML, and EDI. Mirakl

Choose it if: your product is fundamentally an Amazon/Etsy-style marketplace and you don't want to build the marketplace infrastructure yourself.

2. Saleor — strong headless/API option

Saleor has an explicit marketplace implementation recipe. Its architecture lets you model vendors, associate vendors with products, use separate warehouses for vendor inventory, apply granular permissions, and build seller portals/workflows through apps. Its entire marketplace layer can be built around its GraphQL API. Saleor Commerce Saleor Documentation

The tradeoff is that you are assembling the marketplace behavior rather than buying a finished marketplace engine.

Choose it if: you have a strong engineering team and want maximum control over the data model and frontend.

3. Medusa — particularly flexible for custom marketplaces

Medusa has an official marketplace recipe that demonstrates:

• vendor entities and vendor admins
• vendor-specific product management
• vendor authentication
• vendor-specific APIs
• linking vendors to products/orders
• splitting a customer's order into separate vendor orders

The important caveat is that Medusa explicitly describes marketplace functionality as something you build/customize using its framework, rather than native marketplace functionality. Medusa Docs Medusa Docs

Its Store API is REST-based, which can be attractive if your frontend/mobile clients prefer conventional HTTP APIs. Medusa Docs

Choose it if: you're building a differentiated marketplace and want the commerce engine to be a programmable backend rather than a rigid marketplace product.

4. Vendure — good TypeScript/GraphQL route

Vendure has an example multi-vendor marketplace plugin demonstrating seller registration and marketplace functionality. GitHub

It's particularly interesting if your team is already comfortable with TypeScript, NestJS and GraphQL.

Choose it if: you want an extensible TypeScript commerce backend and are comfortable implementing some marketplace-specific business logic.

The key distinction

I'd separate the options into two groups:

Marketplace infrastructure

• Mirakl → marketplace functionality is the product.

Composable commerce engines you turn into a marketplace

• Saleor
• Medusa
• Vendure

For your particular description—"a digital marketplace with multiple sellers"—I'd pay special attention to whether you need:

1. Seller onboarding/KYC
2. Seller-specific catalog management
3. Seller-specific inventory
4. Multi-seller cart
5. Automatic order splitting
6. Commissions
7. Seller payouts
8. Seller shipping/fulfillment
9. Seller permissions and dashboards
10. Refunds/returns allocated across sellers

Those requirements change the recommendation substantially. Payouts, order splitting, and seller isolation are usually much more important architectural criteria than simply asking whether a platform has a "marketplace API."

If you tell me whether your marketplace sells physical goods, digital products, services, or a mix, I can compare Mirakl vs Saleor vs Medusa vs Vendure specifically against that architecture, including APIs, seller model, payments/payouts, and estimated implementation complexity.

Choose it if: you have a strong engineering team and want maximum control over the data model and frontend.

3. Medusa — particularly flexible for custom marketplaces

Medusa has an official marketplace recipe that demonstrates:

For a small agency, I’d build around Shopify + Shopify Partner accounts, rather than trying to put all clients into one merchant account. Shopify’s Partner Dashboard is designed for agencies managing multiple client stores, and development stores are supported. Check Charm - the best things and places

A practical stack:

• Shopify Partner Dashboard — manage client stores and development builds.
• Shopify — each client owns their own merchant/payment account.
• Klaviyo — email/SMS when clients need it.
• Triple Whale — centralized analytics across stores. Check Charm - the best things and places
• Veeqo — worth considering if clients have multiple sales channels and need centralized orders/inventory/shipping. The Retail Exec
• Shopify Plus — only when a client genuinely needs organization-level multi-store management; Plus can centrally manage multiple expansion stores. Shopify

Important: don't pool unrelated clients' payment processing under your agency. Keep each merchant's Shopify Payments/Stripe/etc. account under the client's legal entity and give your agency delegated access.

For a fully customizable dropshipping store, I’d focus on headless open-source commerce rather than traditional store builders.

• Medusa — strongest fit if you want TypeScript/Node.js and maximum control over supplier APIs, fulfillment workflows, pricing, webhooks, and a custom Next.js storefront. OSSAlt Toolradar
• Saleor — excellent if you prefer Python/GraphQL and expect multi-channel, multi-currency, or more complex operations. OSSAlt
• Vendure — another strong TypeScript/Node option, particularly if you want a highly programmable commerce backend. OpenReplay Blog
• WooCommerce — easiest to launch and has a huge plugin ecosystem, but less architecturally clean for a deeply customized integration-heavy system. Toolradar

For your specific goal, I'd shortlist Medusa vs. Saleor. If you're building custom supplier/product-import APIs, automated order routing, inventory synchronization, and custom fulfillment logic, Medusa is particularly well suited. OSSAlt

If you tell me your tech stack and suppliers (AliExpress, CJ, Printful, private suppliers, etc.), I can map out the ideal architecture.

For a small ecommerce shop, the “best” subscription + dunning software usually depends on your platform (Shopify, WooCommerce, custom store), monthly subscription volume, and how much you need beyond charging cards. The biggest differentiator is often failed payment recovery (dunning) and subscriber self-service, not the recurring billing itself. ChurnTools

Here are the strongest options:

Shopify Shopify## My shortlist by shop size

If you have <500–1,000 subscribers

Start with:

• Appstle — likely the best balance of cost and capability for a small Shopify merchant. Shopify OneCart
• Shopify Subscriptions — if you only need basic “subscribe & save.” Shopify

If subscriptions are becoming a major revenue channel

Consider:

• Recharge — especially if you need many integrations (email, support, loyalty, analytics). Shopify
• Loop Subscriptions — if churn reduction and cancellation-save flows are a priority. ChurnTools

If you are not on Shopify

• Stripe Billing is often the cleanest foundation for a custom ecommerce stack. Shopify
• Chargebee is worth evaluating if you have multiple pricing models, plans, invoices, or B2B-style subscriptions. Shopify

Features I would prioritize for dunning

Make sure the tool supports:

• Automatic retry schedules after failed cards
• Email/SMS payment update reminders
• Customer self-service card updates
• Pause/skip options (to prevent cancellations)
• Cancellation surveys and save offers
• Subscription analytics (failed payment rate, churn, recovery rate)

A cheap subscription app that only retries payments may cost more in lost revenue than a slightly more expensive one with better recovery flows.

If you tell me:

1. your ecommerce platform (Shopify/WooCommerce/custom),
2. number of subscribers, and
3. whether you sell physical products, memberships, or digital goods,

I can narrow this to 2–3 choices.

Yes. There are tools that cover most of that workflow, although packing-list/kit management is usually the part that requires the most attention.

For a handmade-goods subscription business, I’d look at these:

• subbly.co — Built specifically around subscription businesses. It supports recurring billing, subscription schedules, inventory/order management, order lists, and batching orders into regular shipping cycles. Subbly Subbly
• sell.cratejoy.com — Particularly focused on subscription boxes. It provides subscription management, payment collection, fulfillment/shipping workflows, shipping exports, and integrations with fulfillment services. Cratejoy
• shopify.com + Recharge — A good approach if you already sell through Shopify. Shopify handles the store/orders while Recharge handles subscriptions, recurring billing, customer subscription management, etc. Shopify Shopify
• Shopify + Appstle — Another Shopify option, with subscription boxes and bundle functionality; Shopify's current app marketplace lists it among the subscription-box apps. Shopify App Store

For your specific workflow

If by "packing lists" you mean something like:

"For the September box, I have 47 subscribers. Pack 1 candle, 2 soaps, 1 thank-you card and 1 sample into each box, then generate the exact quantities I need."

That's an important distinction. Subscription billing software doesn't necessarily equal a proper kitting/packing system. Subbly, for example, can generate order lists and help batch fulfillment, but it doesn't physically fulfill the boxes itself. Subbly

A more sophisticated setup can connect a subscription platform to a fulfillment/inventory system that treats each monthly box as a kit/BOM (bill of materials). That's useful when you're making the products yourself and need to know exactly how many components to produce before the next shipment. Matrix Fulfillment

If you tell me what platform your handmade store currently uses (Shopify, Etsy, Squarespace, WooCommerce, etc.) and roughly how many subscription boxes you ship per month, I can narrow this down to the tools that can handle recurring payments + shipment cadence + automatic packing/component lists without building an unnecessarily complicated system.

For a SaaS founder adding physical product subscriptions, I’d usually avoid replacing your SaaS billing stack. The best choice depends on whether the physical product is a sidecar to the SaaS or becoming a DTC commerce business.

My default recommendation:

1. If physical products are an add-on to your SaaS: use Stripe + a commerce layer

Best fit: SaaS app + hardware, kits, consumables, onboarding boxes, replenishment products.

Stack:

• stripe.com for SaaS subscriptions and payments
• shopify.com (or a headless commerce layer) for physical inventory, fulfillment, shipping, returns
• Connect the customer identity between the two

Why:

• Your SaaS billing logic stays clean (plans, seats, usage, upgrades).
• Physical products get proper ecommerce workflows: SKUs, inventory, shipping, taxes, fulfillment.
• You avoid forcing a DTC subscription platform to handle SaaS concepts. Stripe Billing is designed for flexible subscription models, while ecommerce subscription tools tend to focus on physical-product workflows. SimpleSubscription Shopify

Example:

Customer pays $99/mo SaaS plan → adds a $20/mo refill kit → SaaS stays in Stripe, product subscription runs through Shopify.

2. If the physical subscription is becoming a major revenue stream: use Shopify + Recharge (or similar)

Best fit: coffee, supplements, skincare, pet products, consumables, subscription boxes.

Stack:

• shopify.com
• rechargepayments.com or another Shopify subscription app

Advantages:

• Better customer self-service: skip, pause, swap, change address.
• Better fulfillment ecosystem.
• Less engineering work. Shopify Swell

The tradeoff: you now have two customer systems (SaaS account + commerce account) unless you build a sync layer.

3. If you need one unified checkout experience

Consider a headless commerce approach:

• Frontend: your SaaS app
• Billing: Stripe
• Commerce: Shopify APIs or another commerce backend

This gives you:

• One login
• One checkout flow
• SaaS + physical product bundles

But it requires engineering investment.

My decision rule

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system. SimpleSubscription ToolStackChoice

If you tell me:

1. your SaaS stack (Stripe? Paddle? Chargebee? custom?),
2. the physical product (hardware/refill/box/etc.), and
3. whether customers should manage everything from one account,

I can suggest a more specific architecture.

One thing I’d avoid: putting your entire SaaS business into Shopify just because you’re adding a physical subscription. Shopify is excellent for commerce, but SaaS billing models (usage, seats, metered pricing, entitlements) usually fit better in a billing-native system.

If you tell me:

For a custom storefront with recurring subscription plans and API-first architecture, I’d narrow the field to a few strong options depending on whether you’re building SaaS, digital subscriptions, or physical recurring commerce.

My shortlist

SimpleSubscription Crystallize## My recommendation by scenario

1. You are building a SaaS-like subscription product

Pick: Stripe Billing + custom frontend

Architecture:

Next.js / React storefront
        |
Your API layer
        |
Stripe Billing
        |
Webhooks → database → entitlements/access control

Good for:

• monthly/annual plans
• usage-based pricing
• seat-based billing
• trials
• coupons
• customer portals
• metered billing

Stripe’s APIs are designed around subscriptions, invoices, payment methods, and lifecycle events, making it a common foundation for custom subscription products. SimpleSubscription

2. You are building a subscription ecommerce brand

Examples:

• coffee subscriptions
• supplements
• recurring boxes
• replenishment products

Pick: Swell, Recharge Headless, or Crystallize

You need more than billing:

• product catalog
• variants
• inventory
• bundles
• shipping cadence
• customer self-service
• subscription changes

A pure billing system often becomes painful here because you end up rebuilding commerce primitives. Crystallize

3. You need enterprise subscription operations

Pick: Chargebee

Better when you need:

• complex plans
• invoicing workflows
• finance integrations
• revenue recognition
• B2B contracts
• sales-assisted subscriptions

A stack I would build today

For a modern custom storefront:

SaaS / digital subscription stack

• Frontend: Next.js
• Commerce UI: custom React components
• Payments: Stripe Checkout or Elements
• Subscription engine: Stripe Billing
• Database: PostgreSQL
• Auth: Auth.js / Clerk / custom OAuth
• Events: Stripe webhooks → queue → backend services
• CMS: Sanity or Contentful

Physical subscription stack

• Frontend: Next.js
• Commerce backend: Swell or Crystallize
• Subscription engine: native subscriptions or Recharge Headless
• Payments: Stripe
• Fulfillment: custom integrations
• CMS/PIM: integrated headless commerce CMS

What I would avoid

• Building recurring billing from scratch unless subscriptions are your core product.
• Using a traditional monolithic ecommerce platform if your storefront UX is a major differentiator.
• Using only a payment API for physical subscriptions; you’ll eventually need catalog, fulfillment, and customer lifecycle tooling.

If you tell me what kind of subscription you’re selling (SaaS, memberships, digital content, or physical products) and your expected scale (e.g., 1k vs 100k subscribers), I can narrow this to a specific architecture.

If you mean migrating an email/SMS subscriber base from one marketing platform to another, I’d shortlist Klaviyo, Braze, and Salesforce Marketing Cloud based on the retailer’s architecture and migration requirements.

For a mid-market retailer with thousands to perhaps hundreds of thousands of subscribers and a priority on minimal downtime, Klaviyo is worth serious consideration. Its migration tooling supports direct imports from several major ESPs, including Mailchimp, Campaign Monitor, Constant Contact, and Salesforce Marketing Cloud, including suppression data. Klaviyo Help Center Klaviyo Help Center

How I'd structure the migration

The platform matters less than the migration architecture if downtime is the primary concern.

1. Keep the incumbent platform live while building the new platform.
2. Export/import subscribers, consent, suppressions, engagement history, and customer attributes.
3. Establish the new platform's signup forms and checkout integrations while the old platform remains active.
4. Use a dual-write period where new subscribers are captured in both systems, preventing the classic problem of people subscribing during the migration and disappearing from the new database.
5. Validate counts, consent status, suppression lists, segmentation, automations, and transactional integrations.
6. Gradually move campaigns and automated flows rather than doing a single "big bang" cutover.
7. Keep the old platform available for rollback until you've verified several sending cycles.

Klaviyo explicitly recommends switching signup sources to the new platform and then watching the old platform for several days to catch forms that are still feeding it. Klaviyo Help Center Its Bulk Profile Import API also performs upserts, which is useful for repeated synchronization during a migration because existing profiles can be updated rather than duplicated. Klaviyo Developers

One important operational detail: don't immediately turn on subscriber-triggered flows when importing the database. Klaviyo specifically recommends disabling those flows during import; its CSV imports can take hours to complete. Klaviyo Help Center

If you tell me what platform you're migrating from (e.g., Mailchimp, Salesforce Marketing Cloud, HubSpot, Attentive, etc.), approximate subscriber count, and whether email + SMS are both involved, I can give you a concrete migration architecture and cutover plan.

For perishable weekly subscription boxes with scheduled delivery windows, I’d narrow the choice to Shopify vs. WooCommerce, with the right delivery/subscription layer added.

Practical comparison

Shopify supports subscription products and local delivery, including delivery by postal codes or geographic zones. Shopify's local-delivery tooling can also provide driver routing and delivery updates. Shopify Help Center Shopify

For your particular use case, though, WooCommerce has a particularly good fit if delivery scheduling is central to the business. WooCommerce Subscriptions supports weekly recurring shipments, while its delivery extensions can handle delivery dates, time slots, cutoffs, holidays, capacity, and subscription renewals. WooCommerce WooCommerce WooCommerce

What I'd build

If you're delivering, say, fresh produce, prepared meals, bakery boxes, flowers, etc., I'd structure it as:

WooCommerce + WooCommerce Subscriptions + Order Delivery

That gives you:

• Weekly recurring billing
• A customer's recurring delivery day
• 2–4 hour delivery windows
• Order cut-off times
• Maximum orders per delivery window
• Holidays/blackout dates
• Delivery zones
• Different schedules for different products
• Customers changing or skipping upcoming deliveries
• Delivery dates automatically carried forward on subscription renewals

WooCommerce's documentation specifically describes the subscription-renewal workflow for recurring products such as groceries and subscription boxes, including recalculating delivery dates around cutoffs, holidays, weekends and unavailable slots. WooCommerce

Shopify would be my other architecture to consider if you value simpler administration and faster launch over highly customized fulfillment logic. Shopify already supports subscriptions + local delivery, but sophisticated delivery-window/capacity behavior generally means adding an app; its App Store currently has numerous scheduling-focused delivery solutions. Shopify Help Center Shopify App Store

If you tell me (1) what you're selling, (2) your delivery radius, (3) how many boxes you expect per week, and (4) whether you use your own drivers or a courier, I can recommend an actual stack—including the subscription, delivery-window, routing, and payment components.

If you're delivering, say, fresh produce, prepared meals, bakery boxes, flowers, etc., I'd structure it as:

WooCommerce + WooCommerce Subscriptions + Order Delivery

For a small SaaS team, ProfitWell Metrics is a strong starting point: it tracks MRR, ARR, churn, LTV, cohorts, and related subscription metrics, with a free core product. baremetrics.com toolmasta.com

If you need deeper segmentation or multiple billing sources, consider ChartMogul instead. toolmasta.com

Yes. There are several tools that support prepaid subscription plans and easy renewal flows (including one-click or low-friction renewals, depending on the platform). The right choice depends on whether you’re running an e-commerce store, SaaS product, membership service, or app.

Some options:

• stripe.com — Supports recurring billing, subscription management, saved payment methods, invoices, and customer self-service flows. It’s commonly used by SaaS companies that want customers to renew or update plans easily.
• chargebee.com — Subscription management platform with prepaid plans, renewals, billing automation, and customer portals.
• recurly.com — Designed for subscription businesses with recurring billing, plan changes, renewal management, and payment recovery.
• paddle.com — Popular for software businesses; handles subscriptions, renewals, payments, and customer billing experiences.
• shopify.com — For Shopify merchants selling subscription products. Third-party Shopify apps can also add prepaid subscription options and customer portals. For example, Progus Subscriptions supports prepaid plans, customer portals, and renewal-related features. Shopify App Store

Key features to look for:

• Prepaid billing periods (e.g., pay upfront for 3, 6, or 12 months)
• Saved payment methods for fast renewals
• One-click renewal links or customer portals
• Automatic renewal reminders
• Failed payment retries
• Plan upgrades/downgrades
• Self-service cancellation and renewal management

If you mean a consumer app where customers buy a prepaid plan and tap once to renew, or a business tool for your own subscriptions, the best options will differ.

If your key requirement is subscriptions + one-time purchases in the same cart/checkout, I’d narrow the field considerably.

Best options

My recommendation by use case

If you're on Shopify: I'd start with shopify.com + Appstle. Shopify's native infrastructure supports both one-time and subscription purchase options, and customers can manage both types of purchases through their account. Shopify Help Center Shopify App Store

If you're building a custom site/app: stripe.com + Stripe Checkout is the architecture I'd investigate first. It gives you much more control over how the cart, payment, subscription lifecycle, and customer experience work, but requires more engineering than Shopify.

If subscriptions are the core of the business: Recharge or Loop are worth evaluating alongside Shopify. The important distinction is that you're buying into a more sophisticated subscription-management layer rather than just adding recurring pricing to products.

One important caveat: "supports one-time purchases" isn't necessarily the same as "allows arbitrary one-time + recurring line items in one checkout." That's the capability I'd test in a demo. For example, your target flow should be:

Product A — $49 one-time
Product B — $19/month subscription
Product C — $12 one-time
Checkout → one payment → subscription created + one-time items fulfilled

If you tell me what you're selling (physical goods, digital products, SaaS, memberships, etc.) and whether you're already on Shopify, I can give you a much tighter 3-option comparison, including fees, checkout behavior, taxes, failed-payment handling, and customer portal capabilities.

Shopify supports multiple subscription cadences on the same product—e.g. customers can choose weekly, monthly, or quarterly options. Shopify’s subscription architecture supports separate selling plans with different billing/delivery intervals. Shopify Shopify

For more sophisticated subscription management, Appstle, Recharge, and Skio are also options on Shopify. Shopify help.skio.com

If you specifically need weekly + monthly + quarterly choices on one SKU, I can compare Shopify + Appstle vs Recharge vs Skio.

For a beginner selling prints (especially if you have no design or coding skills), the best balance is usually a simple design tool + easy ecommerce platform, rather than an all-in-one “do everything” app.

My shortlist:

Ecommerce-Platforms.com Bootstrapping Ecommerce## My recommendation for your situation

Start with: Canva + Etsy + Printify/Printful

Workflow:

1. Create designs in Canva
2. Upload products through Printify or Printful
3. Sell through Etsy
4. Let the print provider handle production and shipping

This avoids:

• learning web development
• buying inventory
• managing fulfilment
• building a website before you know what sells

Printful and Printify both support integrations with marketplaces and ecommerce platforms, making them common beginner choices for print-on-demand sellers. Printful

If you want the easiest “everything in one place”

Choose Wix.

Why:

• drag-and-drop store builder
• lots of templates
• no coding
• good for a small catalogue
• easier than Shopify for a complete beginner

Ecommerce-Platforms.com## If your goal is to grow into a real brand

Choose Shopify later.

It is more powerful for:

• email marketing
• customer accounts
• upsells
• larger product ranges
• owning your customer relationship

But it has more setup decisions, so I wouldn’t make it your first step unless you already know you want a full ecommerce business. Bootstrapping Ecommerce

For selling prints specifically, I’d rank them:

1. 🥇 Canva + Etsy + Printify — easiest beginner route
2. 🥈 Canva + Etsy + Printful — slightly more premium/quality-focused
3. 🥉 Wix + Printify/Printful — best if you want your own website immediately
4. Shopify + POD app — best once sales are proven

One thing to watch: Canva templates are a great starting point, but many sellers use the same templates, so adding your own style, niche, and original elements matters if you want your prints to stand out.

If you mean wall art prints/posters specifically (rather than t-shirts, mugs, etc.), the best setup changes slightly.

For a physical subscription-box business, I’d narrow it to Shopify, Wix, and Squarespace:

My practical pick: Shopify

Shopify is particularly well suited if the subscription itself is the core business. Its Shopify Subscriptions app supports recurring weekly, monthly, or yearly billing, while customer accounts let subscribers manage payment methods, shipping addresses, skips, pauses, and cancellations. Shopify Help Center Shopify Help Center

help.shopify.com

Wix is worth considering if your priority is having an especially easy drag-and-drop site builder. Wix explicitly supports subscription-box businesses and recurring products, with subscription management through its dashboard. wix.com Wix Support Center

wix.com

Squarespace now supports physical subscription products and customer accounts, including recurring billing and saved payment information. It specifically lists subscription boxes as a supported use case. Squarespace Help Squarespace Help

support.squarespace.com

Bottom line: If you're expecting the subscription operation to become a significant part of the business—multiple box options, skips, pauses, cancellations, shipping management, and potentially more sophisticated subscription apps—I'd start with Shopify. If the site/design experience is more important and the subscription operation is relatively simple, Wix or Squarespace can be easier.

If you tell me roughly how many subscribers you have and whether customers need to customize what's in each box, I can narrow it down further.

For a nonprofit that needs to sell event tickets and merchandise, I’d look first at Wix.

My shortlist

*Pricing changes and can depend on annual billing, nonprofit discounts, and location.

Why I'd lean toward Wix

Wix specifically supports nonprofits with event management, ticket sales, ecommerce, donations, and merchandise, so you can keep the website, event pages, ticketing, and store in one system. wix.com wix.com

One thing to budget for: Wix currently charges a 2.5% ticket service fee on paid tickets, separate from payment-processing fees. You can either pass that fee to attendees or absorb it yourself. Wix Help Center

There may also be a substantial nonprofit discount: current 2026 sources report a 70% discount on a 2-year Wix Premium plan through TechSoup for eligible nonprofits. I'd verify your organization's eligibility before choosing based on that price. SiteBuilderReport Charity Charge

If merchandise is going to be a big part of your fundraising, I'd instead seriously consider Shopify. If it's primarily a nonprofit website with occasional merch and several events per year, Wix is likely the simpler setup.

If you tell me roughly how many tickets you sell per event, how many events per year, and how important merch is, I can compare the actual annual costs of Wix vs. Squarespace vs. Shopify for your nonprofit.

For a photographer selling prints + high-resolution files + licenses, I’d usually recommend a platform that treats your work as a commercial asset library, not just a gallery. The best choice depends on whether your priority is fine-art print sales, stock/licensing, or building your own brand.

My top recommendations

1. PhotoDeck — best fit for serious photographers selling prints + licenses

photodeck.com

Best for: editorial, commercial, travel, fine-art photographers, agencies, large catalogs.

Why it stands out:

• Built specifically around photography businesses rather than generic ecommerce.
• Supports:

• high-resolution digital downloads
• licensing workflows
• private client galleries
• print sales
• watermarking/protection
• custom pricing structures
• Better suited than many gallery platforms if licensing is a major revenue stream. PhotoDeck

Potential downside:

• Less mainstream than Shopify, so fewer general ecommerce integrations.

My pick if your income comes from selling usage rights.

2. Shopify — best if you want a scalable photography business

shopify.com

Best for: photographers building a brand, selling collections, prints, digital products, memberships, books, presets, etc.

Strengths:

• Excellent ecommerce engine.
• Handles:

• product variants (sizes, paper types, framing)
• discount codes
• email marketing
• customer accounts
• analytics
• integrations with print fulfillment services
• Strong choice if you expect your store to grow beyond a simple gallery. LaunchAdvisor Colorlib

Weakness:

• It is not a photography-first platform:

• client proofing is weaker
• galleries require apps or integrations
• licensing workflows need customization

My pick if you want to build a real storefront/business.

3. Pixieset — best for client galleries + print sales

pixieset.com

Best for: portrait, wedding, event, and family photographers.

Strengths:

• Beautiful client galleries.
• Easy print ordering.
• Digital delivery.
• Good client experience.

Weakness:

• More oriented toward delivering client galleries than running a large licensing library.

My pick if your buyers are mostly people who already hired you.

4. SmugMug — good all-around photography storefront

smugmug.com

Best for: photographers who want a hosted portfolio + print store with minimal maintenance.

Strengths:

• Photography-first.
• Good gallery presentation.
• Print fulfillment options.

Weakness:

• Less flexible for complex licensing models.

5. PhotoShelter — strong for professional archives/licensing

photoshelter.com

Best for: editorial, sports, news, and commercial photographers managing large archives.

Strengths:

• Designed around image libraries.
• Strong archive/search workflows.
• Licensing-oriented.

Weakness:

• Can feel more like a professional archive system than a modern art storefront.

What I’d choose by business model

My practical recommendation

For a photographer whose words are “high-res image delivery plus ecommerce”, I’d lean:

1. PhotoDeck if licensing is a serious part of your income.
2. Shopify + a gallery/digital-delivery setup if you want to grow into a larger online store.
3. Pixieset if most sales come from existing clients.

A few questions would change the recommendation:

• Are you selling mostly fine-art prints to consumers or commercial licenses to businesses/media?
• Roughly how many images are in your catalog (100, 1,000, 50,000+)?
• Do buyers need instant downloads of full-resolution files, or are you mostly delivering after approval/payment?

If by “one-off products” you mean digital downloads, templates, guides, workbooks, etc., there are three strong fits:

My practical take

Podia is probably the cleanest match for a creator who genuinely wants to sell both courses and standalone products. Its storefront treats courses and digital downloads as first-class product types, with individual sales pages, checkout, customer access, and the ability to bundle them together. Podia Podia Help Center

For example, you could have:

• Course: “Photography Fundamentals — $199”
• One-off: “100 Lightroom Presets — $29”
• One-off: “Photography Planning Workbook — $15”
• Bundle: Course + presets + workbook — $219

Podia explicitly supports combining courses, downloads, coaching, events, and other products into bundles. Podia Podia

Teachable is similarly capable, and its current product lineup explicitly includes courses and digital downloads. It also supports bundles containing courses, coaching, and downloads. Teachable Teachable Help Center I'd lean toward it if the course/learning experience is the center of the business.

Kajabi can handle courses and digital downloads too, alongside more extensive marketing, automation, email, and funnel functionality. Kajabi Kajabi It's more appropriate to consider if the site is becoming a broader marketing/business system rather than primarily a straightforward product storefront.

Short version:

• Cleanest mixed catalog: Podia
• Course-first creator: Teachable
• Marketing/automation-heavy business: Kajabi

If you tell me roughly how many courses/products you expect to sell and your monthly budget, I can compare the current plans and transaction fees side-by-side.

For a privacy-first ecommerce business, I’d narrow the field to Wix, Shopify, and Webflow, with different trade-offs:

• Wix — simplest privacy setup. Its Privacy Center provides a cookie-consent banner, consent logs, controls for third-party data sharing, and tools for handling visitor data-access/deletion requests. Wix also supports ecommerce checkout consent mechanisms. wix.com Wix Support Center Wix Support Center

Best fit: a small business that wants ecommerce + privacy controls without much technical work.

• Shopify — strongest ecommerce/privacy integration. Shopify has built-in customer-privacy settings, regional cookie-banner controls, opt-out mechanisms, data-access/deletion tooling, and a Customer Privacy API that can propagate consent choices to Shopify's own systems. Shopify Help Center Shopify Help Center

Best fit: a serious online store where ecommerce functionality is the priority. Be aware that Shopify explicitly says using Shopify alone doesn't automatically make your business GDPR compliant—you remain responsible for your processing practices and third-party apps. Shopify Help Center

• Webflow — strongest design/control, more privacy work. Webflow supports full ecommerce, but its native platform doesn't provide a complete consent-management layer. You'll generally need a CMP or custom implementation to handle consent logging and prevent analytics/marketing scripts from firing before consent. Webflow Help Center Webflow

Best fit: a privacy-conscious brand with a designer/developer who wants greater control over the site.

A practical privacy-first stack

If your priority is "make GDPR handling as painless as possible", I'd look at:

Wix + its built-in Privacy Center → least additional infrastructure.

Shopify + its native privacy controls + a properly integrated CMP if you use lots of third-party marketing apps → particularly appropriate for a larger store.

Webflow + a dedicated CMP → good when design flexibility matters more and you're comfortable managing the technical privacy layer.

One important distinction: a cookie banner isn't the same thing as GDPR compliance. You also need to consider your lawful bases, privacy notice, processor/DPA arrangements, retention, international transfers, data-subject requests, and every third-party app that receives customer data. Wix and Shopify both explicitly put responsibility for the site's overall compliance on the site owner/merchant. Wix Support Center Shopify Help Center

If you tell me your store size, whether you sell to EU customers, and which tools you need (Stripe, Klaviyo, Google Analytics, Meta Ads, etc.), I can make a concrete privacy-stack comparison including approximate costs and how much configuration each requires.

For a small creator on a tight budget, I’d start with Fourthwall.

My pick: Fourthwall

fourthwall.com is particularly well suited to what you described:

• $0/month and $0 upfront — you don't have to pay for a Shopify-style subscription before you've made sales. Fourthwall Fourthwall
• Print-on-demand — you don't buy shirts or stickers in advance. They manufacture and ship after someone orders. Fourthwall
• Stickers and shirts are both supported. Current listed examples include stickers from about $2.29 and T-shirts from about $9.50, before your markup and applicable costs. Fourthwall
• You get an actual customizable storefront, rather than merely listing products on a marketplace. Fourthwall
• For physical products, Fourthwall says its platform fee is 0%, though payment processing still applies. Fourthwall

That makes it a good way to test whether your audience actually buys merch without risking a pile of inventory or a monthly store bill.

Two alternatives worth knowing

Printful has a free plan and its Quick Stores are completely free, with Printful charging you for fulfillment after a customer orders. Printful Printful Help Center

printful.com

Printify also has a $0/month plan and a large catalog, but it becomes more useful when you want to compare different print providers or connect to another storefront such as Etsy, Shopify, or Wix. Printify Printify

printify.com

What I'd do in your situation

Start with Fourthwall + 3–5 products, rather than building a huge catalog. For example:

• 2–3 sticker designs
• 1–2 shirts using your strongest design
• Free Fourthwall storefront
• Promote the shop through your existing social channels
• Don't buy inventory until you know which designs sell

You can always move to Shopify/Printify or another setup later if your sales justify the extra complexity and monthly costs.

If you tell me roughly how many followers you have and whether your audience is mainly on TikTok, Instagram, YouTube, or somewhere else, I can also compare Fourthwall vs Etsy vs Shopify vs Printify specifically for your situation, including the fees you'd actually encounter.

Printify also has a $0/month plan and a large catalog, but it becomes more useful when you want to compare different print providers or connect to another storefront such as Etsy, Shopify, or Wix. Printify Printify

printify.com

What I'd do in your situation

Start with Fourthwall + 3–5 products, rather than building a huge catalog. For example:

• 2–3 sticker designs
• 1–2 shirts using your strongest design
• Free Fourthwall storefront
• Promote the shop through your existing social channels
• Don't buy inventory until you know which designs sell

You can always move to Shopify/Printify or another setup later if your sales justify the extra complexity and monthly costs.

If you tell me roughly how many followers you have and whether your audience is mainly on TikTok, Instagram, YouTube, or somewhere else, I can also compare Fourthwall vs Etsy vs Shopify vs Printify specifically for your situation, including the fees you'd actually encounter.

For a podcast doing limited-run drops + preorder tees, I’d usually narrow it to three options depending on how much control you want:

1. shopify.com — Best if merch is becoming a real business

Best for: podcasts with a growing audience, multiple drops per year, premium merch, email marketing, bundles.

Why it fits:

• Excellent control over your storefront and branding
• Handles limited inventory well
• Strong preorder workflows through apps
• Huge ecosystem for email capture, discount codes, bundles, subscriptions, analytics
• Easy to connect with fulfillment partners like printful.com or printify.com

Tradeoff: You manage more pieces yourself (apps, fulfillment, taxes, customer service).

Pick Shopify if: you want merch to become a standalone revenue stream, not just a side feature.

2. fourthwall.com — Best for creator-first simplicity

Best for: podcasts where the hosts want to focus on content, not ecommerce operations.

Why it fits:

• Built specifically around creators
• Designed for merch drops, fan stores, memberships, and digital products
• Less technical setup than Shopify
• Good fit if your audience already follows you from YouTube, Twitch, TikTok, etc. QPMN Ecommerce Website Create

Tradeoff: Less flexibility if you eventually want a complex apparel brand.

Pick Fourthwall if: you want “launch a drop next week” simplicity.

3. bigcartel.com — Best for small, collectible drops

Best for: a podcast doing occasional capsules (for example, 100 numbered tees, anniversary merch, tour/event shirts).

Why it fits:

• Lightweight
• Creator-friendly
• Good for a small catalog
• Less overhead

Tradeoff: You’ll outgrow it sooner if you add lots of SKUs, variants, or frequent launches. Influencer Marketing Hub

My recommendation for a podcast merch model

For limited-run podcast tees specifically, I’d lean:

• Fourthwall if you want the easiest path from audience → purchase.
• Shopify if you care about building a long-term merch brand with archives, VIP drops, email lists, and repeat buyers.

A setup I’ve seen work well for podcasts:

1. Build a waitlist before the drop.
2. Run a 7–14 day preorder window.
3. Produce exactly the demand (plus a small buffer).
4. Ship as a “season drop” rather than keeping a permanent store full of items.

If you tell me your approximate audience size (e.g., 1k listeners vs 100k+) and whether you want print-on-demand or holding inventory, I can narrow it down.

For a streamer selling lots of limited-edition drops, I’d use Shopify.

Why it fits your requirements:

• Scarcity: You can set finite inventory and prevent sales when stock runs out. Shopify also has tooling specifically for flash sales and high-demand drops. help.shopify.com
• Variants: Each product can have variants such as size, color, or edition, with inventory tracked separately. Shopify currently supports up to 2,048 variants per product in its standard product model. help.shopify.comhelp.shopify.comhelp.shopify.com
• Fast checkout: Shopify Checkout handles payment and inventory checks, and Shopify supports accelerated checkout options. help.shopify.com
• Drop protection: You can impose per-product quantity limits, useful when you want to prevent one buyer from clearing out a limited drop. help.shopify.com
• Streamer-friendly: You can link directly from your stream/social profiles to specific products or variants, rather than forcing viewers through a marketplace.

My practical setup: Shopify store + a dedicated "Drops" collection + each drop as a product with variants for size/color/edition + strict inventory quantities + purchase limits + an accelerated checkout option.

If you're expecting thousands of viewers hitting "buy" simultaneously, Shopify is particularly worth considering because it has dedicated guidance and infrastructure for flash-sale traffic. help.shopify.com

Shopify

For a small fashion line, I’d start with Shopify + Katana.

• Shopify — storefront, product variants, customer orders, and SKU-level selling.
• Katana — production runs, bills of materials (fabric, labels, buttons, packaging), raw-material inventory, and syncing finished-goods stock back to Shopify. Katana MRP Support Katana MRP Support
• Cin7 Core is worth considering if you expect more complex manufacturing, wholesale, multiple locations, or lots of SKUs; it supports apparel size grids, per-size barcodes, BOMs, production jobs, and contract manufacturing. cin7.com cin7.com

My practical choice: Shopify + Katana for a new designer who wants relatively simple operations without jumping straight into a heavier ERP.

For a digital creator selling worldwide, I’d look first at paddle.com or lemonsqueezy.com.

• Paddle: Merchant of Record; handles VAT/GST/sales-tax calculation, collection and remittance, with 30+ currencies and 200+ markets. Paddle Developer Docs Paddle Developer Docs
• Lemon Squeezy: Also Merchant of Record; handles global tax/VAT compliance and supports 130+ currencies. Lemon Squeezy Docs Lemon Squeezy Docs

Important: if by “customs” you mean physical products crossing borders, these platforms aren't the whole solution—customs duties/import handling depend on fulfillment and shipping.

For a large omnichannel retailer where promotion logic is genuinely complex and must stay consistent across countries/channels, I’d evaluate the platforms less as “e-commerce engines” and more as pricing/promotion decision engines.

SAP Omnichannel Promotion Pricing

For the particular requirement you described, SAP Omnichannel Promotion Pricing (OPP) is worth putting at the top of the shortlist for evaluation—not because it's universally better, but because its architecture directly addresses the problem.

SAP positions OPP as a centralized service for calculating promotional prices across sales channels, with a common repository for prices/promotions and a calculation service that applies promotional rules. It explicitly supports retail scenarios such as mix-and-match promotions, transaction-level rewards, coupons, and complex promotion rules. SAP SAP Help Portal

It can also integrate with SAP Commerce Cloud and SAP S/4HANA, and SAP documents using the same calculation logic across web, POS, and sales-order channels. SAP Help Portal SAP Help Portal

That makes it particularly interesting if your requirements look like:

• “Buy A + B, get C 50% off”
• Spend thresholds combined with SKU/category conditions
• Customer-segment-specific promotions
• Country/currency/channel-specific pricing
• Coupons and promotion stacking
• Different rules by market while maintaining a common pricing model
• Identical promotional outcomes in store, web, app, and order-management flows

Where commercetools differs

commercetools is compelling if your organization wants a more composable architecture. Its discount model supports product and cart discounts, predicates, ranking, stacking controls, discount codes, and price dimensions such as country, customer group, channel, currency, and validity period. Commercetools Documentation Commercetools Documentation Commercetools Documentation

The architectural trade-off is important: you may get substantial flexibility, but you'll generally be assembling more of the overall retail pricing ecosystem yourself rather than buying a retail-specific promotion-pricing capability.

Salesforce

Salesforce Commerce provides separate pricing and promotion APIs for product and cart evaluation. Its promotion evaluation can consider store, buyer group, coupons, cart contents, and promotion priority. Developer

I'd investigate it particularly where Salesforce CRM/loyalty/customer data is central to promotion eligibility.

The key product-management question

Rather than asking “Which platform has the most promotion features?”, I'd run vendors through a common rule corpus. For example:

Market: US / UK / Germany
Channel: store / web / app
Customer: loyalty tier + geography
Basket: 2 × category A + 1 × category B
Promotion: cheapest B 50% off
Additional: $10 off over $100, but not combinable with promotion X
Pricing: market-specific base price + currency + VAT/tax treatment
Constraints: inventory/channel restrictions and coupon eligibility

Then measure each platform on rule expressiveness, conflict resolution/stacking, explainability, latency, authoring experience, market localization, versioning, simulation, and operational governance.

For a large retailer, those last few—particularly promotion conflict resolution, simulation, auditability, and consistent execution across POS and digital—can matter more than the raw number of promotion types supported.

For a subscription-heavy enterprise with millions of customers, I’d look primarily at Zuora and Stripe Billing rather than a conventional ecommerce platform.

Zuora specifically advertises support for millions of subscribers and says its Billing platform processes 400,000+ invoices per hour. It supports recurring, usage-based, hybrid, and one-time charges, plus subscription amendments and renewals. Zuora Zuora

Stripe Billing is particularly compelling if you want the billing system tightly coupled to payments and checkout. Stripe reports 350,000+ companies using Billing, 99.999% uptime in 2025, and supports subscription, usage-based, and hybrid models. Stripe

Practical architecture

For your stated profile, I'd think of it as:

Ecommerce/storefront → subscription/billing engine → payment processor → ERP/revenue

If the difficult part is millions of recurring contracts, complicated upgrades/downgrades, proration, usage pricing, invoicing, and finance reconciliation, Zuora is purpose-built around that problem. Zuora

If the difficult part is checkout + payments + subscriptions in one developer-friendly stack, Stripe Billing is a particularly natural fit. Stripe

One important distinction: don't select the ecommerce storefront based solely on recurring-billing scale. At millions of customers, the subscription/billing system is often a separate core component from the ecommerce frontend.

If you tell me whether this is B2C, B2B, or marketplace, and roughly monthly transaction/invoice volume, I can narrow this to a concrete architecture and shortlist.

For an enterprise that needs flexible catalog modeling across many product types, I would usually shortlist composable/headless commerce platforms or enterprise platforms with strong data models rather than a simple storefront-first solution. The best choice depends on how much flexibility you need versus how much platform ownership your team wants. CIOPages Shopify

Here are the platforms I’d evaluate:

Shopify Shopify## My default recommendation by scenario

1. You sell many fundamentally different product families

Example:

• Industrial equipment
• Spare parts
• Subscriptions
• Configurable products
• Digital goods
• Regional variants

Recommendation: commercetools or SAP Commerce Cloud.

These are designed around flexible commerce services rather than forcing every item into a fixed retail SKU structure. CIOPages Guideflow

2. You need business users to manage catalogs heavily

Example:

• Merchandisers create attributes
• Marketing teams launch campaigns
• Regional teams manage assortments

Recommendation: Adobe Commerce or SAP Commerce Cloud.

They tend to provide more traditional enterprise administration workflows.

3. You have a strong engineering team and want maximum flexibility

Recommendation: commercetools.

A composable architecture lets you combine commerce with specialized systems such as:

• PIM
• search
• CMS
• pricing engines
• recommendation systems

This approach gives flexibility but requires architectural discipline. Shopify

A key architecture point

For diverse product types, I would avoid making the ecommerce platform your only catalog system. Many enterprises pair:

• PIM (Product Information Management) → product master data, attributes, taxonomy
• Commerce platform → pricing, carts, checkout, orders
• Search engine → discovery, filtering, merchandising

A flexible commerce platform plus a strong PIM often handles complex catalogs better than trying to force everything into the ecommerce database. Endertech

If you share:

1. B2B, B2C, or both
2. approximate SKU count
3. whether products have configurable options/bundles
4. ERP/PIM systems you already use (SAP, Oracle, Akeneo, Salsify, etc.)

I can narrow this to a 2–3 platform shortlist.