Answers that do not mention BigCommerce

For your situation, I’d pick shopify.com.

• Very beginner-friendly: its visual editor is designed for no-code setup, with drag-and-drop sections and customizable themes. Shopify Shopify
• Fully hosted: Shopify handles hosting, security, and software maintenance for you. Shopify
• Good fit for handmade goods: you can manage products, inventory, payments, shipping, orders, and marketing from one dashboard. Shopify
• Room to grow: you can start simple and later add apps, social selling, in-person sales, or more sophisticated storefront features. Shopify

Runner-up: squarespace.com — I'd choose it if the visual/brand presentation of your handmade shop is more important than having the deepest ecommerce toolkit. It's also hosted and no-code, with templates and built-in tools for selling physical products. Squarespace Squarespace Help

My quick rule:
Shopify = best if you primarily want to sell products.
Squarespace = best if you want a beautiful brand website that also sells products.

For a small handmade-goods shop, Shopify is the safer all-around choice.

Yes. If your startup needs both one-time digital downloads and recurring subscriptions/memberships in the same storefront, there are several good creator-focused options.

My top picks

• fourthwall.com — best all-around creator platform. It supports digital downloads, subscription memberships, a branded storefront, member-only content, tiers, discounts, and community integrations. There are no monthly fees; its published pricing is 5% for memberships and 5% for digital products (with some plans/features changing the digital-product fee). Fourthwall Fourthwall
• gumroad.com — best for straightforward digital products. Gumroad handles downloads and recurring memberships in the same product ecosystem, including multiple tiers, recurring billing, and member-only content. It's particularly attractive if your business is primarily PDFs, templates, courses, software, assets, etc. Gumroad Gumroad
• patreon.com — best if subscriptions/community are the core business. Patreon now has a dedicated digital-product shop, so you can sell one-off downloads alongside memberships and even make products free for certain members. Patreon

What I'd choose for a startup

If your model is something like:

$29 template → $99 bundle → $15/month premium subscription

I'd lean Fourthwall or Gumroad, rather than Patreon.

Fourthwall is especially interesting if you want a more complete branded storefront and expect to grow into memberships, community, or physical products. Gumroad is simpler and very well suited to a business whose main inventory is digital files.

If you tell me what you're selling (e.g. ebooks, templates, software, courses, AI prompts, design assets) and roughly your monthly revenue/number of customers, I can compare the best 3 platforms on fees, subscription features, customer ownership, checkout, taxes/VAT, and API/integrations for your specific startup.

For a one-person print-on-demand (POD) shop, the most cost-effective choice depends on whether you mean lowest upfront cost or best return on your time.

My typical recommendation for a solo beginner:

Best overall starting point: Etsy + a POD supplier

Cost: lowest risk

Why:

• No monthly ecommerce subscription to start.
• Built-in shoppers already searching for products.
• You can test designs before paying for a full storefront.
• Good fit if you only have 10–100 products at first. www.gelato.comwww.printondemandbusiness.com

Downsides:

• Less control over branding.
• Marketplace fees reduce margins.
• You don't fully own the customer relationship. www.gelato.comwww.printondemandbusiness.com

Best for:

• Testing niches
• T-shirts, mugs, posters, stickers, gifts
• Someone who wants to spend more time designing than managing tech

Best long-term solo-business platform: Shopify

Cost: roughly $30+/month plus apps and payment fees

Why:

• Very easy to run alone.
• Excellent POD integrations (Printful, Printify, Gelato, etc.).
• Better for building a real brand instead of just selling listings.
• Less technical maintenance than self-hosted options. ecommerce-platforms.com

Downsides:

• Monthly cost even if sales are slow.
• Apps can add up.

Best for:

• You already have a niche and brand idea.
• You plan to run ads, build an email list, or grow beyond a few products.

Cheapest "own website" option: WooCommerce

Cost: potentially ~$10–30/month, but more work

Why:

• The software itself is free.
• You control the site, SEO, and customer data.
• No platform subscription fee. www.gelato.comwww.printondemandbusiness.comwoocommerce.com

Downsides:

• You handle hosting, updates, security, and troubleshooting.
• More time-consuming for a solo operator. woocommerce.com

Best for:

• You already know WordPress.
• You enjoy tinkering with websites.
• You want maximum control.

My suggested path for a one-person POD shop

Stage 1 (first 1–3 months):

• Start on Etsy
• Connect to Printify or Printful
• Launch 20–50 designs
• Find which products actually sell

Stage 2 (after consistent sales):

• Add Shopify
• Move your best sellers there
• Build email marketing and a brand

Stage 3:

• Keep Etsy as a discovery channel and Shopify as your owned store

If I were starting from zero as a solo operator with limited budget, I’d probably spend $0–50 upfront, validate designs on Etsy, and only pay for Shopify once I had evidence that people wanted the products. www.gelato.comwww.printondemandbusiness.com

A few details would change the recommendation:

1. Are you selling shirts/apparel, wall art, stickers, or something else?
2. Do you already have an audience (Instagram/TikTok/email list), or are you starting from scratch?
3. Is your priority minimum cost or building a brand you can grow for years?

For a high-traffic sales event, flash deals, or product drops, the ecommerce solutions most commonly chosen for spike reliability are:

For true flash-sale conditions (e.g., thousands of shoppers arriving within minutes for limited inventory), the platform alone is not enough. The critical features are:

• Virtual waiting room / traffic queueing to prevent checkout overload
• CDN caching and edge protection
• Bot mitigation and rate limiting
• Load testing before launch
• Inventory reservation strategy that avoids locking up stock
• Checkout integrations that can handle the same surge as the storefront

Salesforce specifically documents flash-sale practices such as waiting rooms, rate limiting, bot mitigation, cache preparation, and third-party service readiness for hype sales. Salesforce Developer

A practical shortlist:

• Biggest global brand + mission-critical launches: Salesforce Commerce Cloud
• High-volume DTC brand that wants less infrastructure work: Shopify Plus
• Complex B2B/B2C requirements and deep customization: Adobe Commerce
• Engineering-led company building a custom commerce ecosystem: commercetools

If you expect Black Friday-scale traffic, limited-edition drops, or ticket-style demand spikes, I would prioritize platforms with proven traffic-control mechanisms over just raw autoscaling. Salesforce Developer

If your priority is self-hosting + full customization + owning the code/data, I’d narrow it to Medusa, Saleor, WooCommerce, and Bagisto. The right choice depends heavily on whether you want a ready-made store or a developer-oriented commerce backend. www.opensourcegroups.com

My recommendation: Medusa

I’d pick Medusa if you’re comfortable developing the storefront yourself.

Medusa

It is a modern, TypeScript/Node.js, headless commerce platform designed to be customized rather than fought against. You can self-host the backend, build the storefront however you want (Next.js, React, etc.), and replace/customize major parts of the commerce logic. Its modular architecture is particularly attractive if you expect unusual business rules. www.wpbundle.com

Why I'd choose it:

• Full control over frontend and backend
• TypeScript/Node.js
• Headless/API-first architecture
• Good fit for Next.js
• Modular payments, fulfillment, inventory, etc.
• Self-hostable
• No platform transaction fee
• Much less legacy baggage than WooCommerce/Magento

Downside: you're taking on more development work. The extension ecosystem is nowhere near WooCommerce's. www.wpbundle.com

The alternatives

When I'd pick something else

WooCommerce — probably the best choice if you want to get a store running quickly and customize it through an enormous ecosystem of plugins. It's much more "complete store out of the box" than Medusa. www.wpbundle.com

WooCommerce

Saleor — excellent if you're building something substantial and have Python/Django + GraphQL expertise. It has strong multi-channel, multi-warehouse and multi-currency capabilities, but the infrastructure is considerably more involved. ossalt.com

Saleor

Bagisto — I'd seriously consider this if you already like Laravel. It's a surprisingly capable option, particularly if you're building a marketplace/multi-vendor system. ossalt.com

Bagisto

Sylius — great if your team is Symfony/PHP-oriented and you essentially want an ecommerce framework that you can mold into your own application rather than a traditional "store builder."

Sylius

What I would personally do

If you're starting a new project today:

Next.js storefront → Medusa → PostgreSQL → Redis → Stripe → your own hosting

That gives you a genuinely custom store rather than a heavily modified Shopify/WooCommerce-style site.

If, however, your goal is "I want to install this tonight, add products, install a payment plugin, and start selling", I'd go WooCommerce instead.

The biggest question is whether you want an ecommerce application you can program or an ecommerce store you can configure. For the former, Medusa is my first choice.

For a small handmade goods shop where you aren’t tech-savvy but want a serious online store, I’d usually recommend starting with:

Best overall: Shopify

Shopify

Why it fits:

• Built specifically for selling products (not just making a pretty website)
• Easy drag-and-drop setup
• Handles payments, inventory, shipping, discounts, and customer orders
• Can grow with you if your shop takes off
• Lots of beginner tutorials and support

The tradeoff: there is a monthly cost, and you’ll need to bring in customers through social media, email, markets, ads, or other channels. www.shopify.com

If you want the easiest first step: Etsy

Etsy

Good if:

• You have only a few products
• You want to start selling quickly
• You don’t want to build a whole website yet

Etsy already has shoppers looking for handmade items, which makes it easier to get your first sales. The downside is less control over your branding and more competition beside your products. www.forbes.com

If your products are very visual: Squarespace

Squarespace

Good for:

• Jewelry makers
• Artists
• Home décor brands
• Boutique-style shops where photos and storytelling matter

It’s easier to make a beautiful site, but it is generally less focused on scaling a large product catalog than Shopify. fitsmallbusiness.com

My recommendation for a first “serious” store:

Use Shopify as your main store + keep Etsy as a discovery channel if you already sell there. Many handmade sellers eventually use a marketplace for finding new customers and their own store for building repeat customers and a brand. ecomguider.net

A simple path:

1. Pick Shopify
2. Start with 10–20 best-selling products (don’t upload everything at once)
3. Use a clean theme
4. Take good product photos
5. Add an email signup (“get 10% off your first order”)
6. Connect it to your Instagram/TikTok/Pinterest if you use those

If you tell me what you make (jewelry, candles, clothing, art, woodworking, etc.), your approximate number of products, and whether you already sell at craft fairs or on Etsy, I can narrow it down further.

If your priority is “I want to sell custom T-shirts without managing servers, hosting, updates, or infrastructure,” I’d pick Shopify + a print-on-demand provider.

My recommendation: Shopify + Printful

• shopify.com — Your storefront, checkout, payments, hosting, SSL, product management, etc. Shopify explicitly includes hosted commerce infrastructure, so you don't manage a server. Shopify Shopify
• printful.com — Handles printing, packing, and shipping when someone orders. It integrates directly with Shopify. Printful Help Center Printful

For a solo entrepreneur, this gives you a very clean division:

You: designs → branding → marketing → customer relationships
Shopify: website → checkout → payments → hosting
Printful: printing → fulfillment → shipping

Why I'd choose it over WooCommerce

WooCommerce can be excellent, but you're more responsible for WordPress hosting, updates, plugins, security, backups, and troubleshooting. That's exactly the infrastructure work you're trying to avoid.

Shopify's Basic plan is currently $29/month when billed annually (or $39 month-to-month), and it includes unlimited hosting. Shopify

One caveat

If you already have an audience and mainly want the cheapest/easiest way to test designs, Etsy + Printful can be simpler initially because Etsy provides marketplace traffic. But if you're building your own brand, Shopify is the better long-term home. Printful

Bottom line: For a solo T-shirt business, I'd start with Shopify Basic + Printful. It minimizes technical work while still giving you a real branded store that can scale.

If your business is selling both high-resolution digital files and physical prints, I’d put Pixieset at the top of the list for most photographers.

My ranking

\*Usually requires an app/integration for photography-specific digital delivery.

🥇 Pixieset — my pick

Pixieset is particularly well suited to the workflow you're describing because digital downloads and print sales live in the same gallery/store. You can sell individual images or full-gallery downloads, specify the resolution, and have the files automatically delivered after purchase. High-resolution downloads aren't watermarked. website-help.pixieset.comwebsite-help.pixieset.com

For physical products, Pixieset can automatically send orders to professional labs for printing, packaging, and shipping. Its current lab network includes WHCC, Miller's, ProDPI, Mpix, and others, and you can select the lab when creating a price sheet. website-help.pixieset.com

That combination is compelling:

Photo gallery → customer chooses image → buys high-res file OR print → Pixieset handles delivery/fulfillment.

You can also create packages combining digital downloads and physical products. website-help.pixieset.comwebsite-help.pixieset.com

Pixieset Store

🥈 SmugMug

SmugMug is an excellent alternative if you have a large archive of photographs and want your website, galleries, hosting, downloads, and print sales under one roof. It has native digital downloads and a substantial print/product marketplace, including a quality guarantee. www.smugmug.com

I'd lean toward SmugMug if your business is more "online photography archive + ongoing print sales" than "boutique storefront for individual fine-art images."

🥉 Pic-Time

Pic-Time is worth serious consideration if your sales depend heavily on beautiful galleries, client engagement, and automated sales campaigns. It's particularly popular for wedding/event photographers, but it can work well for fine-art and portrait work too.

What I'd choose for you

If you're primarily selling fine-art prints + downloadable full-resolution files, I'd start with:

Pixieset → WHCC/Miller's/ProDPI fulfillment → your own markup

One important distinction: if by "high-resolution downloads" you mean true original/full-resolution files suitable for commercial licensing, rather than a 3600px print-ready file, I'd evaluate the download/storage/licensing controls more carefully before committing. Pixieset supports different download resolutions and original/high-resolution delivery, but your exact file-delivery setup matters. website-help.pixieset.comwww.smugmug.com

If you tell me (1) what kind of photography you sell, (2) typical print sizes/prices, and (3) whether you're selling to consumers or commercial/licensing clients, I can narrow this down to the best 2–3 options and compare fees, margins, download limits, print labs, and color/print quality.

For a neighbourhood gift shop, I’d shortlist Shopify, Square, and WooCommerce. If spreadsheet importing is a major priority, WooCommerce and Square are particularly straightforward.

My pick for your shop

1. Shopify — easiest overall

• Good choice if you want a polished online store without much technical work.
• CSV is the normal way to bulk-load products.
• Particularly attractive if you're starting fresh and want ecommerce to be relatively hands-off.

2. Square — best if you also sell in the physical shop

• Square lets you bulk add or update your item catalog from a spreadsheet. It supports both .xlsx and .csv. squareup.comsquareup.com
• That's useful for a gift shop because the same product catalog can serve your in-store POS and online operation.
• One caveat: Square's importer is more template-driven—you need to preserve certain columns and formatting. squareup.comsquareup.com

3. WooCommerce — best for spreadsheet power users

• Its built-in importer handles new products, bulk updates, SKUs, variations, categories and images via CSV.
• It automatically maps recognizable columns, which makes importing an existing spreadsheet fairly painless. woocommerce.com
• It's more flexible than the others, but you'll have WordPress hosting and maintenance to deal with.

Bottom line: If you already have a brick-and-mortar POS, I'd seriously consider Square. If you're primarily looking for the simplest online shop, I'd choose Shopify. If your inventory spreadsheet is complicated and you want lots of control, WooCommerce wins.

If you tell me roughly how many products you have (e.g. 200, 2,000, 10,000) and whether you need in-store POS + online inventory synchronization, I can narrow it down to one.

Yes. For a small artisan selling a mix of ready-to-ship products, pre-orders, and genuinely made-to-order/custom pieces, I’d put Shopify at the top of the list.

Best fits

Why Shopify stands out: its ecosystem has a large selection of pre-order apps specifically supporting made-to-order products. Shopify's own pre-order system supports things such as paying upfront, deposits, or later payment, while apps can add ship-by dates and other lead-time messaging. www.shopify.com

One particularly relevant option is Preorderly: it can display a “Ships by” date, accept deposits/partial payments, handle pre-orders by product or variant, and warn customers about carts containing both pre-order and in-stock products. apps.shopify.com

Another useful Shopify app is Downpay, which is specifically geared toward deposits and partial payments for custom and pre-order sales. apps.shopify.comapps.shopify.comsquareup.com

What I'd choose for your business

I'd structure it like this:

• In-stock item: “Ready to ship in 1–2 business days”
• Made-to-order: “Made especially for you — ships in 2–3 weeks”
• Pre-order: “Pre-order now — ships by October 15”
• Custom item: customer selects options → pays → you make it → order stays in your normal fulfillment workflow
• Limited batch: pre-orders open until a particular date or quantity

That distinction is important: you don't just want a store that says “out of stock → preorder.” You want customers to see the expected production/fulfillment window before they pay.

Square is worth considering if you want something particularly simple and already use Square for payments/POS. Its online preorder feature lets you specify availability dates and shows the fulfillment window to customers. squareup.com

My recommendation: Shopify + a pre-order/lead-time app. It gives you the easiest path from a handful of artisan products today to more sophisticated custom orders later. Shopify's current Basic plan is listed at $29/month when billed annually, with a much larger app ecosystem if you eventually need more customization. www.shopify.com

If you tell me roughly how many products you have, whether customers choose custom options (color/size/name/etc.), and your monthly budget, I can narrow this down to 2–3 specific store setups and their current costs.

For a small handmade goods shop on a tight budget, I’d prioritize low monthly cost, easy setup, and not needing technical skills. Here are the strongest options:

Best free or very cheap options

1. etsy.com — best if you want customers quickly

Cost: No monthly fee; you pay listing and transaction fees.

Good for:

• Handmade jewelry, crafts, art, candles, crochet, vintage-style goods
• Getting discovered without already having an audience

Pros

• Built-in shoppers
• Trusted marketplace
• Easy setup

Cons

• Fees add up
• Less control over branding
• You’re building on someone else’s platform

Best choice if: You have little marketing experience and want your first sales.

2. squareup.com — best free storefront

Cost: Free plan available; paid upgrades if you need more features.

Good for:

• A simple branded shop
• Selling through social media, markets, or local events

Pros

• Free website/store option
• Easy product listings
• Good payment tools
• Works well with in-person selling

Cons

• Fewer design options than some competitors
• You still need to bring customers

Best choice if: You sell at craft fairs or locally and want an online home base.

3. bigcartel.com — best for a tiny catalog

Cost: Free plan for a small number of products.

Good for:

• Artists and makers with a handful of products

Pros

• Designed for independent creators
• Simple, clean storefronts
• Low-pressure setup

Cons

• Limited features compared with larger platforms
• Not ideal if you’ll have hundreds of products

Best choice if: You’re starting with 5–20 items.

4. shopify.com — best later, not necessarily first

Cost: Usually paid monthly after trial/promotions.

Good for:

• Growing brands
• More advanced marketing and inventory

Pros

• Very powerful
• Huge app ecosystem
• Professional-looking stores

Cons

• Monthly cost
• More setup than beginners need

Best choice if: You already have sales and want to scale.

My recommendation for a tight-budget handmade shop

A practical starting path:

1. Start on Etsy to test which products sell.
2. Create a free Square Online store as your branded website.
3. Use social media (Instagram, TikTok, Pinterest) to drive repeat customers.
4. Move to Shopify only when your monthly sales justify the cost.

If you already have a following (friends, local customers, social media audience), I’d lean toward Square Online or Big Cartel instead of Etsy so you keep more control.

For a small boutique with seasonal inventory and occasional selling, the best ecommerce solution is usually one with little or no monthly cost when you’re inactive. You generally want to avoid paying a full subscription year-round for a store that is only busy during certain seasons. Find Homegrown

Here are the strongest fits:

My pick by situation

• You sell a few collections per year (holiday, summer, markets): Square Online is probably the best match. It keeps overhead low during downtime. Find Homegrown
• You have 10–50 products and want a cute branded shop: Big Cartel is worth considering. Shopify
• You want shoppers to discover you without much marketing: Etsy can work well, especially for distinctive boutique items. Reddit
• You plan to grow into a full-time online boutique: start simple, but consider Shopify once sales volume justifies the monthly cost. Shopify

For an occasional seasonal boutique, I would generally avoid paying for a premium store every month. A “pay only when selling” or free-tier approach usually matches the business pattern better. Find Homegrown

If you tell me whether you sell clothing, handmade goods, gifts, vintage, or something else and roughly how many products are active at once, I can narrow it down.

For an artisan seller who only wants to sell locally, I’d pick Square Online first.

• squareup.com — best cheap/easiest option. The Free plan is $0/month and supports online ordering, free in-person pickup, and local delivery. You pay payment-processing fees when you make a sale. Square Square
• ecwid.com — better if you want a more flexible artisan storefront or already have a website. It supports pickup, delivery zones/radii, delivery fees, and pickup scheduling. Ecwid | E-Commerce Shopping Cart Ecwid | E-Commerce Shopping Cart
• squarespace.com — good if the visual/brand presentation is especially important, and it now supports local pickup and delivery. Squarespace Help

My recommendation

If you're selling things like handmade crafts, candles, artwork, baked goods, jewelry, or other artisan products and don't need nationwide shipping:

Square Online Free → probably the best starting point.

You can set up:
Customer orders online → chooses pickup OR local delivery → you fulfill it locally.

If you tell me roughly how many products you have (e.g. 10, 50, 200) and whether you want a custom website/domain, I can narrow it down to the cheapest option for your specific setup.

For a physical subscription box on a shoestring, I’d start with Stripe Billing.

Why:

• No monthly commitment: Stripe Billing’s pay-as-you-go plan charges 0.7% of Billing volume, on top of Stripe’s normal payment-processing fees. stripe.com
• Easy to launch: You can create subscriptions and accept payments with no-code Payment Links or Stripe Checkout, so you don't need to build billing infrastructure. stripe.com
• Built for physical subscriptions: You can handle recurring monthly/annual charges, failed-payment retries, customer billing management, discounts, etc. stripe.com
• Scales well: You won't have to migrate when you go from dozens to thousands of subscribers.

One important alternative

Lemon Squeezy is attractive if you want an extremely hands-off setup: it has no monthly fee and handles subscriptions, payment processing, and tax compliance for you. But its standard fee is 5% + $0.50 per transaction, with an additional 0.5% for subscription payments in some cases. www.lemonsqueezy.com

For a physical box, that fee can become painful as your order value and volume grow.

My pick: Stripe Billing + a simple storefront (or Stripe Payment Links initially). Keep the tech stack minimal until you've proven people will subscribe.

If you tell me your box price (e.g. $25/month), expected subscribers, and whether you're selling through a website, Shopify, or social media, I can calculate the cheapest setup and your actual monthly payment-processing cost.

For a photographer selling prints + digital downloads + image licensing, I’d start with Pixieset.

Best affordable options

1. Pixieset — my recommendation

Pixieset's free Client Gallery plan includes a storefront where you can sell prints and digital downloads, with 15% commission on sales. The Basic plan is currently $8/month when billed annually ($10 monthly) and eliminates the commission, while giving you 10 GB storage, custom branding/domain, and full-resolution downloads. pixieset.com

It also supports digital-image licensing: its digital-download products can include a digital image license, which makes it much more suitable for commercial photography than a basic digital-download platform. website-help.pixieset.com

Prints can be automatically fulfilled through lab partners, or you can self-fulfill, so you don't have to handle every print order yourself. website-help.pixieset.com

For someone starting out, I'd use the free plan initially. If you're making enough sales that 15% becomes significant, move to the $8/month plan.

2. Zenfolio — good alternative

Zenfolio is particularly geared toward photographers selling individual images, galleries, prints, and downloads. Its current system supports digital downloads, with a base processing/delivery cost of $0.09 for an individual image or $0.99 for a full gallery, plus a 7% commerce fee. success.zenfolio.com

I'd consider it if you expect more serious photo-commerce functionality and don't mind paying more than Pixieset.

3. SmugMug — excellent, but less budget-friendly

SmugMug's Portfolio plan is currently about $23.50/month when billed annually and includes print and digital-download sales, customizable pricing/profit margins, watermarking, and print-lab fulfillment. www.smugmug.com

It's excellent if your priority is a polished photography portfolio/store, but I wouldn't choose it if keeping monthly costs extremely low is the goal.

What I'd do in your situation

Start with Pixieset Free → upgrade to Basic at $8/mo once sales justify it.

Set up three types of products:

• Fine-art prints — different sizes/papers/framing
• Personal-use digital downloads — high-resolution JPEG
• Commercial licensing — separate products for web, editorial, advertising, etc., with a clearly defined license

One important distinction: don't treat a commercial license as simply another "digital download." The value is in the rights you're granting—duration, territory, media, exclusivity, advertising use, resale/merchandising, etc. Pixieset can handle the transaction/delivery side, while your license terms define what the buyer is actually purchasing.

If you tell me roughly how many images you have, your expected monthly sales, typical print price, and whether your licensing is mostly editorial or commercial, I can recommend the cheapest setup and show you what the fees would look like at, say, $500, $1,000, and $5,000/month in sales.

For a few-week test of one product, I’d avoid full ecommerce platforms (Shopify, Wix ecommerce, etc.) because you’ll pay monthly before you know if the product works.

The best free/near-free setups:

For a physical product, I’d do:

1. Build a one-page landing page in Carrd:
   • Hero image
   • Problem → solution
   • Benefits
   • Reviews/social proof
   • FAQ
   • “Buy now” button

carrd.com

2. Connect the button to:
   • Stripe Payment Link (cleanest), or
   • Gumroad/Payhip if you want checkout + fulfillment handled.

3. Run traffic for 2–4 weeks and measure:
   • Landing page conversion rate
   • Cost per purchase (if using ads)
   • Refunds/questions
   • Whether people buy without heavy persuasion

My pick for a true MVP:

• Physical product: Carrd + Stripe Payment Link
• Digital product: Gumroad or Payhip
• Need email list too: Carrd + MailerLite

One caveat: the free Carrd tier is great for a landing page, but ecommerce features usually require connecting external checkout tools rather than having a built-in store. carrd.com

If you tell me whether the product is physical, digital, subscription, or preorder, I can suggest the leanest stack.

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

My ranking

Why WooCommerce

WooCommerce is open source, free to download, and can run on essentially any normal WordPress-compatible hosting. You control the hosting, store data, source code, checkout, and extensions. woocommerce.com

That's particularly good for handmade goods because you can start very simply:

• WordPress + WooCommerce
• inexpensive VPS/shared hosting
• your own domain
• free theme
• Stripe/PayPal for payments
• inexpensive or free shipping/tax plugins
• automatic backups
• Cloudflare for DNS/CDN

You don't need to build a custom frontend or hire a developer just to launch.

The big advantage is the ecosystem: if later you need things like custom product options, made-to-order items, coupons, email marketing, abandoned carts, wholesale pricing, subscriptions, or local pickup, there's a good chance an existing extension can handle it. WooCommerce itself emphasizes its large extension ecosystem and its ability to be hosted wherever you choose. woocommerce.com

When I'd choose PrestaShop instead

PrestaShop is my second choice. It's a dedicated ecommerce application rather than a WordPress plugin, so it can feel cleaner if the website exists primarily to sell products. It's also fully self-hostable and open source. prestashop.com

I'd lean toward PrestaShop if you expect a larger catalog, multiple languages/currencies, or more sophisticated ecommerce operations.

One important caveat

"Open source" doesn't mean zero cost. You'll still pay for hosting, domain registration, payment processing, backups, and possibly premium themes/plugins. You'll also be responsible for security and updates when self-hosting. prestashop.com

For your situation, I'd keep the initial stack boring: WooCommerce + a cheap Linux host + free theme + Stripe/PayPal + automated backups. Don't start with Medusa/Saleor/headless architecture unless you already have development experience.

If you tell me roughly how many products you have and your monthly hosting budget (e.g. $5, $10, $20), I can recommend a specific self-hosting setup and estimate the ongoing cost.

If multi-vendor marketplace capability + total ownership of your code and data are the two primary requirements, I’d shortlist Vendure, Medusa, and Bagisto—but my first choice would be Vendure for a serious, long-lived marketplace.

My ranking

1. 🥇 Vendure — my recommendation

Vendure

Vendure is particularly strong because multi-vendor is designed into its architecture, rather than being merely an add-on. Its Channels can represent individual sellers, with seller-specific products, pricing, inventory, shipping, roles and orders. docs.vendure.io

It also specifically supports the hard marketplace problems: splitting orders between sellers, seller-specific fulfillment/shipping, platform fees and commissions. vendure.io

For ownership, self-hosting means your company controls the infrastructure and database. Vendure describes its core as open source and emphasizes portable code and data. vendure.io

Choose Vendure if you expect:

• Hundreds/thousands of vendors
• Complex vendor permissions
• Vendor-specific catalogs and pricing
• Multi-vendor checkout
• Order splitting
• Commissions/platform fees
• Multiple storefronts/channels
• B2B + B2C
• ERP/PIM/CRM integration
• Significant customization over several years

The main thing I'd have your legal team examine is the exact license for the Vendure version/components you intend to deploy, particularly if your definition of "total ownership" includes proprietary modifications and redistribution rights.

2. 🥈 Medusa — excellent if your engineering team wants maximum flexibility

Medusa

Medusa is a very good alternative, especially for a TypeScript/Node.js engineering organization.

The important caveat is that marketplace functionality isn't as native to the core as Vendure's. Medusa's own documentation describes marketplace functionality as something you build by extending its framework with vendor models, APIs and workflows. docs.medusajs.com

On the other hand, that gives you tremendous architectural freedom. Medusa's marketplace example supports vendor admins, vendor-specific products/orders and splitting customer orders by vendor. vendure.iovendure.iodocs.medusajs.com

Medusa is particularly attractive if you want to build a custom marketplace product, rather than configure an existing marketplace application.

3. 🥉 Bagisto — consider this if you prefer Laravel

Bagisto

Bagisto is worth serious consideration if your team is strong in PHP/Laravel. Its marketplace extension provides vendor registration, vendor dashboards, products and commissions, while the underlying platform is open source and self-hostable. bagisto.com

I'd favor it when time-to-market and conventional ecommerce functionality matter more than having a highly composable headless architecture.

What I'd choose

For a company starting a marketplace today:

Vendure → best overall architecture for a sophisticated multi-vendor marketplace

Medusa → best if your developers want a very flexible TypeScript framework and are comfortable building marketplace logic

Bagisto → best if you have a Laravel/PHP team and want a more traditional ecommerce platform

And I would not make Shopify, Mirakl, VTEX, etc. the first choice if "total data ownership" literally means we must control the production database, infrastructure, source code and ability to migrate without platform dependency. Self-hosted open source is much better aligned with that requirement.

One important distinction: "open source" does not automatically mean "total ownership." Before selecting, I'd evaluate the software license, dependencies, hosted/cloud terms, database portability, proprietary extensions, payment-provider data, vendor/customer data export, and whether you can continue running the exact version independently of the vendor.

If you tell me your expected number of vendors, B2B vs B2C, tech stack (PHP/Node/Python/etc.), expected GMV/order volume, and whether vendors need their own storefronts, I can narrow this to a specific architecture and recommend Vendure vs Medusa vs Bagisto for your company.

For a solo founder with limited dev skills, I would not start with the most “modern” headless platform. I’d optimize for:

1. A good admin you can actually use daily
2. Easy theme customization
3. Lots of plugins/integrations
4. Low maintenance

My shortlist:

blog.openreplay.comwww.opensourcegroups.com

My recommendation: WooCommerce

For your situation, I would pick WooCommerce + a modern theme builder.

Why:

• You get a mature product/order/customer admin.
• Themes are abundant and easy to modify.
• You can add payments, shipping, subscriptions, marketplaces, email marketing, etc. without coding.
• If the store grows, you can hire almost any WordPress freelancer.

The downside: WordPress plugins can become messy, so keep your stack lean.

Good starting setup:

• WooCommerce
• A lightweight theme like Astra, Kadence, or Blocksy
• Stripe/PayPal
• A page builder only if you truly need one

If you want something more “Shopify-like”

Look at PrestaShop. It is a dedicated ecommerce application rather than a WordPress plugin, with a stronger store-management focus. blog.openreplay.comwww.opensourcegroups.com

What I would avoid initially

I would not choose Medusa, Saleor, or Vendure as a non-technical solo founder unless you already enjoy building software. They are modern API-first commerce engines, but you usually end up creating more of the storefront experience yourself. blog.openreplay.com

My ranking for your exact profile:

1. 🥇 WooCommerce — launch fastest, easiest hiring, easiest themes
2. 🥈 PrestaShop — better if you want a pure ecommerce system
3. 🥉 Medusa — consider after you have traction and need customization

If your goal is “I want to launch a branded store in 2–4 weeks without becoming a developer”, WooCommerce is probably the closest open-source answer.

For a static site that needs a commerce backend via APIs, I’d focus on platforms that were built headless-first, not traditional stores that merely added APIs later. The strongest open-source options right now are usually:

OpenReplay Blog Vendure## My recommendation by scenario

Pick Medusa if:

• Your frontend is Astro, Next.js, Nuxt, SvelteKit, React, etc.
• You want a clean API backend and your own UI.
• Your developers prefer JavaScript/TypeScript.
• You expect custom checkout flows, subscriptions, bundles, or unusual product logic.

Medusa is probably the closest match to “Shopify backend, but self-hosted and API-native.” Vendure

Pick Saleor if:

• You have a large catalog.
• You need multi-channel, multi-region, inventory complexity, B2B pricing, or enterprise workflows.
• Your team likes GraphQL.

Saleor’s GraphQL-first approach is one of its biggest strengths. WPBundle

Pick Vendure if:

• Your team is already TypeScript-heavy.
• You want a very extensible backend with plugin-based customization.
• You’re building something more like a commerce platform than a simple store.

Vendure## What I would avoid for a new headless build

• Magento/Open Source unless you already have Magento expertise. It is powerful but heavy.
• WooCommerce unless you specifically need WordPress plugins/content workflows. It can work headlessly, but the architecture is less clean than platforms designed API-first. WPBundle

A common modern stack

A setup I’d consider for a static site:

• Frontend: Astro / Next.js / SvelteKit
• Commerce API: Medusa
• CMS: Payload CMS, Strapi, or similar
• Database: PostgreSQL
• Payments: Stripe
• Hosting: your preferred cloud/VPS

If you tell me your frontend framework (Astro, Next.js, plain HTML, etc.), catalog size, and whether you need subscriptions/B2B, I can narrow it to one choice.

If subscription boxes + recurring billing are core to the business, I’d narrow it to WooCommerce vs. Medusa, rather than choosing purely on “best open-source ecommerce platform.”

My recommendation: WooCommerce

For a subscription-box business, I’d pick WooCommerce if your priority is getting a reliable subscription business running with the least custom engineering.

Why:

• Subscriptions are a mature use case. WooCommerce has a large ecosystem of extensions for recurring products, renewals, failed-payment handling, coupons, shipping, taxes, etc.
• Huge ecosystem. Compared with newer headless platforms, there are substantially more existing integrations and developers available. WPBundle ossium
• Self-hosting is straightforward: WordPress + WooCommerce + your payment provider.
• You can still build a custom React/Next.js storefront later if you don't want the traditional WordPress frontend.
• For a subscription box, the boring stuff—renewals, order generation, customer account management, payment failures—is more important than having an elegant commerce API.

The downside is that WordPress/WooCommerce can become plugin-heavy and require more maintenance as you scale.

When I'd choose Medusa instead

Choose Medusa if you're a developer-heavy team and want to build the subscription system as part of your application.

Medusa is a particularly attractive choice if you're already using TypeScript/Node.js + Next.js. Its architecture is much more natural for a custom subscription-box experience than modifying WordPress. However, subscriptions aren't native: Medusa's own documentation describes implementing subscriptions as a customization, including recurring renewals and Stripe integration. Medusa Docs

So your architecture would look roughly like:

Next.js storefront
       │
       ▼
    Medusa
       │
   ┌───┴────┐
   │        │
Stripe   Your subscription service
   │        │
   └───┬────┘
       ▼
 recurring payments
       │
       ▼
 subscription → order → fulfillment

That's more work initially, but gives you much more control over things like:

• "skip this month's box"
• swap products
• different box sizes
• pause/resume
• prepaid 3/6/12-month plans
• renewal-date changes
• add-ons
• build-your-own-box
• subscription-specific shipping logic

What about Saleor?

Saleor is excellent technically—GraphQL-first, headless, composable, and explicitly designed for self-hosting. Saleor Commerce GitHub

But I wouldn't make it my first choice for a subscription-first business. Recurring billing isn't a first-class native feature, so you'd still be building the subscription/payment layer yourself. Devioand

My ranking for your specific use case

The broader 2026 landscape similarly puts WooCommerce toward the ecosystem/merchant end and Medusa/Saleor toward developer-oriented headless commerce. OpenReplay Blog Open Source Projects

If you tell me your expected scale (e.g. 500 vs. 50,000 subscribers), tech stack, and whether you need customers to customize/skip/swap boxes, I can recommend the architecture—not just the platform—and specifically compare WooCommerce + Subscriptions vs. Medusa + Stripe.

For an enterprise team prioritizing scalability, containerized deployment, and long-term control, I would generally shortlist Spree Commerce, Saleor, Vendure, and Medusa, with the final choice depending on your engineering stack and commerce complexity. Open Source Groups Designodin

Recommended choices

1. Spree Commerce — Best overall enterprise fit

Recommended when: you need B2B, marketplaces, multi-region commerce, large catalogs, and a mature commerce domain model.

Why it stands out:

• Headless architecture with API-driven storefronts.
• Strong fit for Kubernetes/Docker-style deployments.
• Built for complex enterprise workflows such as multi-store, multi-currency, inventory, and integrations.
• Ruby/Rails ecosystem, which can be attractive for teams already using Rails. Spree Commerce Spree Commerce

Potential downside:

• Smaller enterprise talent pool than Java/.NET ecosystems.
• Requires experienced Rails engineers for deep customization.

My default enterprise recommendation: Spree if you want a proven commerce engine that your team owns and operates.

2. Saleor — Best API-first cloud-native option

Recommended when: your organization wants a modern composable stack.

Strengths:

• Python/Django backend.
• GraphQL-first API model.
• Designed for headless storefronts and custom customer experiences.
• Docker-based deployment approach fits container platforms well. Open Source Groups Netguru

Good match for:

• Kubernetes environments.
• Teams building React/Next.js/mobile experiences.
• Organizations treating commerce as a backend service.

Tradeoff:

• More engineering work up front because you typically build more of the frontend experience yourself.

3. Vendure — Best for TypeScript enterprises

Recommended when: your team is already standardized on Node.js/TypeScript.

Strengths:

• NestJS-based architecture.
• Plugin-driven extensibility.
• GraphQL API.
• Runs well in Docker/Kubernetes environments and supports horizontal scaling patterns. GitHub Vendure

Good match for:

• Frontend-heavy organizations.
• Teams wanting a strongly typed commerce backend.
• Companies avoiding PHP/Ruby stacks.

4. Medusa — Best developer-centric modular platform

Recommended when: you want a highly customizable commerce foundation.

Strengths:

• Node.js/TypeScript ecosystem.
• Modular architecture.
• Strong fit for custom commerce experiences and integrations.
• Enterprise deployments emphasize ownership of infrastructure and avoiding platform fees. Medusa

Tradeoff:

• More of a commerce framework than a fully opinionated enterprise suite, so your team owns more architecture decisions.

What I would choose by scenario

Suggested enterprise architecture

A typical scalable deployment would look like:

• Kubernetes cluster
• Commerce API pods (horizontal autoscaling)
• PostgreSQL primary database + replicas
• Redis for caching/jobs
• Object storage for media
• Search engine (OpenSearch/Elasticsearch)
• CDN for storefront assets
• Separate frontend (Next.js/React/mobile apps)
• CI/CD pipeline with container image promotion

For a new enterprise build in 2026, my ranking would be:

1. Spree Commerce — safest enterprise commerce foundation
2. Saleor — strongest cloud-native/headless architecture
3. Vendure — best if your company is TypeScript-first
4. Medusa — best for teams wanting maximum customization

The deciding factor is usually not raw scalability; all can scale with good architecture. The bigger question is whether your team wants a commerce platform to configure (Spree) or a commerce engine to build on (Saleor/Vendure/Medusa).

For a low-traffic boutique store run by a non-technical owner, I would usually choose WooCommerce as the easiest self-hosted option. It has the gentlest learning curve because it sits inside WordPress, which many small-business owners already find familiar, and it has a very large ecosystem of themes, plugins, and hosting providers. www.opensourcegroups.com

A practical ranking for your situation:

shopappy.comwww.velsof.comopensourceprojects.cc

My recommendation: WooCommerce + managed WordPress hosting

For a boutique owner who does not want to be a server administrator:

• Use a managed WordPress host that handles:
  • backups
  • WordPress updates
  • SSL certificates
  • basic security
• Keep plugins to a minimum.
• Use a mainstream payment gateway such as Stripe or PayPal.
• Pick a well-supported theme and avoid heavy customization.

The biggest advantage is that the owner can manage:

• adding products
• changing photos
• updating prices
• creating coupons
• writing blog/news posts

without touching code. www.opensourcegroups.comstablecommerce.ai

When I would pick OpenCart instead

OpenCart is a reasonable alternative if the store is very simple:

• 20–500 products
• no blog/content strategy
• no unusual integrations
• mostly “browse → buy”

It is lightweight and has a simpler standalone shopping-cart focus, but finding help and extensions can be less convenient than with WooCommerce. shopappy.comwww.afcommerce.com

Platforms I would avoid here

• Magento Open Source: far too much maintenance for a boutique store; it is aimed at teams with technical resources. shopappy.comwww.velsof.comopensourceprojects.cc
• Headless platforms (Medusa, Saleor, etc.): powerful but require developer involvement. opensourceprojects.cc
• Over-customized PrestaShop: capable, but the owner may end up needing a developer for routine changes. shopappy.comwww.afcommerce.com

One caveat: if the owner truly wants zero technical maintenance, a hosted platform like Shopify is usually easier than any self-hosted system. Self-hosting always means someone is responsible for updates, backups, and security. blog.unlimitedwebhosting.co.uk

For your exact scenario, my shortlist would be:

1. WooCommerce — best overall choice
2. OpenCart — if the store is extremely simple
3. PrestaShop — if the catalog or international needs are expected to grow

I would not choose based on “most powerful”; I would choose based on “least likely to require a developer six months from now.”

If strong inventory + warehouse management is the priority, I’d narrow the field considerably. My top recommendation would be Odoo, with ERPNext as the strongest alternative.

My ranking

1. Odoo — my first choice

odoo.com

If you're saying "I need real warehouse management, not just a product stock counter," Odoo is probably the best starting point.

Its inventory system supports multiple warehouses and locations, replenishment rules, advanced routing, barcode operations, lots/serial numbers, inventory valuation, reservations, cycle counting, and batch/wave/cluster picking. Odoo Odoo

The particularly important distinction is that Odoo treats inventory as an operational system: purchasing → receiving → put-away → inventory → picking → packing → shipping can all live in the same system.

That makes it attractive if you have things like:

• Multiple physical warehouses
• Bin/location-level inventory
• Purchase orders and receiving
• Barcode scanning
• Lot/serial tracking
• Returns
• Replenishment/reordering
• Pick/pack/ship workflows
• Inventory valuation
• Manufacturing or kitting
• Dropshipping
• Transfers between warehouses

Odoo also has sophisticated picking strategies and routing, rather than simply decrementing stock_quantity when an order is placed. Odoo Odoo

The catch: Odoo is really an ERP with ecommerce capabilities, rather than a pure ecommerce platform. If your storefront is extremely custom/headless and ecommerce UX is the center of the business, something like Saleor may be a better architectural fit.

2. ERPNext — excellent if you want a true open-source ERP

erpnext.com

ERPNext is the other one I'd seriously evaluate.

Its warehouse model can go surprisingly deep: Warehouse → Room → Row → Shelf → Bin, and inventory balances are maintained for each item/warehouse combination. Frappe Docs

The Stock module covers inventory movements, receipts, deliveries, transfers, reconciliation, valuation and reporting. Frappe Docs

I'd lean toward ERPNext over Odoo if your business is more:

ERP / purchasing / manufacturing / wholesale / operations

than:

highly polished ecommerce / omnichannel storefront.

3. Saleor — best if you're building a sophisticated headless ecommerce platform

saleor.io

Saleor is worth serious consideration if you're a development team building a headless ecommerce stack.

Its architecture is much more ecommerce-centric than Odoo/ERPNext, with a GraphQL API and strong support for multi-warehouse and multi-channel commerce. Current comparisons also put it ahead of Medusa when advanced warehouse requirements are important. WPBundle WPBundle

I'd choose Saleor when the desired architecture looks something like:

Next.js storefront → Saleor → WMS/ERP → carriers/3PLs

rather than:

Odoo → everything

4. Medusa — great commerce engine, but I'd be cautious for your requirement

medusajs.com

Medusa is excellent if you're a TypeScript/Node team wanting a modular, headless commerce backend.

But there's an important distinction: Medusa is a commerce engine, not a full-blown WMS/ERP. Its modular architecture makes it possible to integrate or replace inventory functionality, but if warehouse operations are one of your core requirements, you'll likely end up building/integrating more yourself. Born Digital

So I wouldn't pick it simply because it's modern and open source.

What I'd pick

If you gave me no other requirements, I'd go:

Odoo → ERPNext → Saleor → Medusa → WooCommerce

But there's a potentially important architectural question:

If inventory/warehouse is the heart of the business

Odoo or ERPNext.

If ecommerce is the heart of the business and WMS is important

Saleor + dedicated WMS/ERP is probably the more scalable architecture.

If you want a modern developer-centric stack

Saleor or Medusa + dedicated inventory/WMS.

I would not start with WooCommerce if sophisticated warehouse operations are a primary requirement. Its enormous plugin ecosystem is an advantage, but you're more likely to assemble a collection of inventory/WMS plugins than get a coherent warehouse system.

If you tell me (1) number of SKUs, (2) number of warehouses, (3) B2C vs B2B, (4) whether you need manufacturing/kitting, and (5) whether you want headless, I can recommend the architecture—not just the platform—and compare Odoo vs ERPNext vs Saleor specifically for your operation.

Yes. For a SaaS company that already has—or plans to have—a dedicated subscription/billing system, I would not make the ecommerce platform responsible for billing. Instead, use it as the catalog + checkout + order layer, with your billing system as the source of truth for subscriptions.

My shortlist

1. WooCommerce — probably the pragmatic choice

If your store is genuinely small, I'd seriously consider WooCommerce.

Its enormous plugin/API ecosystem makes it comparatively easy to connect:

Your SaaS
→ billing/subscription system
→ WooCommerce checkout
→ payment provider
→ license provisioning

WooCommerce is particularly attractive if you're selling things like:

• SaaS licenses
• annual plans
• add-ons
• support packages
• one-time software licenses
• physical merchandise alongside software

It also has an unusually broad ecosystem for subscriptions and payment gateways. WooCommerce itself even provides a Billing API specifically for SaaS products, although that's aimed at products listed in the WooCommerce Marketplace rather than being a general-purpose SaaS billing layer. The WooCommerce Developer Blog

woocommerce.com

Downside: WordPress/WooCommerce can be more machinery than you want if your existing SaaS is already a modern React/Node/etc. application.

2. Medusa — my favorite for a modern SaaS

If your company has developers and doesn't want WordPress, I'd lean toward Medusa.

It's a self-hosted, headless commerce engine built around Node.js/TypeScript, with a modular architecture. That makes it particularly nice when your existing application is already JavaScript/TypeScript. WPBundle WPBundle

The important caveat is that Medusa doesn't natively provide subscriptions. Its own documentation explicitly treats subscriptions as something you implement/customize, with Stripe used as an example. Medusa Docs

But that's actually potentially a good architecture for your situation:

                    ┌──────────────────┐
                    │   SaaS App       │
                    │                  │
                    │ Users / Accounts │
                    │ Entitlements     │
                    └────────┬─────────┘
                             │
                             ▼
                    ┌──────────────────┐
                    │ Billing System   │
                    │                  │
                    │ Subscriptions    │
                    │ Invoices         │
                    │ Renewals         │
                    │ Usage            │
                    └────────┬─────────┘
                             │
                        webhooks/API
                             │
                             ▼
                    ┌──────────────────┐
                    │    Medusa       │
                    │                  │
                    │ Products         │
                    │ Cart             │
                    │ Checkout         │
                    │ Orders           │
                    └──────────────────┘

You can therefore keep billing semantics out of ecommerce.

For example, someone buys:

"Acme Pro — 10 seats — Annual"

Medusa records the commercial transaction, while your billing system creates/maintains the actual subscription. A webhook then tells your SaaS:

subscription sub_123 → active → 10 seats → expires/renews on X

That separation is much cleaner than trying to make an ecommerce plugin your SaaS's subscription database.

medusajs.com

3. Saleor — excellent, but probably more than you need

Saleor is another strong option.

It's GraphQL-first, API-only/headless, and designed to be highly composable. It also has webhooks and extension mechanisms that make external billing integrations quite natural. Saleor Commerce GitHub

I'd choose Saleor over Medusa if you have requirements like:

• multiple storefronts
• multiple currencies/regions
• B2B pricing
• sophisticated catalogs
• multiple sales channels
• substantial customization
• a GraphQL-centric architecture

For a small SaaS license store, however, I think you're likely paying complexity you don't need.

saleor.io

The more important architectural decision

I'd distinguish ecommerce from subscription billing.

A good SaaS architecture is roughly:

Ecommerce system

• product catalog
• product descriptions
• shopping cart
• checkout
• discount codes
• orders
• customer-facing store

Billing system

• subscriptions
• billing cycles
• invoices
• prorations
• failed payments
• dunning
• upgrades/downgrades
• tax/billing records

Your SaaS

• accounts
• users
• seats
• entitlements
• license generation
• license validation
• feature access

That gives you the flexibility to change your storefront without rewriting your billing infrastructure.

If you're considering an open-source billing system too

There are some interesting combinations now. For example, Lago is an open-source/self-hosted billing engine designed around subscription and usage-based billing, while Medusa/Saleor/WooCommerce handle commerce. OSSAlt

So you could have:

Medusa + Lago + Stripe + your SaaS

or:

WooCommerce + Stripe Billing + your SaaS

depending on how much you want to build yourself.

What I'd choose

For your description—"SaaS company adding a small store to sell licenses"—I'd rank them:

1. Medusa — if you want a clean, modern, self-hosted architecture and have developers.
2. WooCommerce — if the store is small and you want the least engineering effort/ecosystem risk.
3. Saleor — if you expect the store to become a serious commerce operation.
4. Vendure — worth considering if your team is strongly TypeScript/Node-oriented.

If you tell me what billing system you're already using (Stripe Billing, Chargebee, Recurly, Orb, Lago, etc.) and what your SaaS stack is, I can narrow this down substantially and suggest the cleanest integration architecture.

So you could have:

"Acme Pro — 10 seats — Annual"

Medusa records the commercial transaction, while your billing system creates/maintains the actual subscription. A webhook then tells your SaaS:

subscription sub_123 → active → 10 seats → expires/renews on X

That separation is much cleaner than trying to make an ecommerce plugin your SaaS's subscription database.

medusajs.com

3. Saleor — excellent, but probably more than you need

Saleor is another strong option.

For a solo developer selling desktop software licenses + paid updates, I’d pick Lemon Squeezy first.

My ranking

Why I'd choose Lemon Squeezy

Lemon Squeezy has native license-key generation, including license duration and activation limits. Each purchase can automatically generate a unique key, which the customer receives in their receipt and order history. Lemon Squeezy Docs Lemon Squeezy Docs

More importantly for a software developer, it gives you an API for:

• activating a license
• validating a license
• deactivating a license
• tracking individual activations
• setting activation limits
• setting/changing expiration dates
• disabling licenses

Lemon Squeezy Docs Lemon Squeezy DocsThat maps very naturally to a desktop application:

Customer buys "MyApp Pro"
        ↓
Lemon Squeezy generates license
        ↓
Customer downloads MyApp 4.2
        ↓
MyApp asks for license key
        ↓
Your API/Lemon Squeezy validates key
        ↓
App activated

The one thing I'd build yourself

I wouldn't use the ecommerce platform as your actual version-management system.

Instead, have a tiny update/download service of your own:

                    Lemon Squeezy
                         │
                    Purchase/license
                         │
                         ▼
Your app ───────► Your licensing API
                         │
                         ├── Is license valid?
                         ├── What products does it own?
                         ├── What update entitlement?
                         └── What's the latest version?
                                  │
                                  ▼
                           Download server
                         ┌───────────────┐
                         │ 4.2.1         │
                         │ 4.1.8         │
                         │ 4.0.12        │
                         └───────────────┘

For example, your backend could expose:

GET /api/update?product=myapp&version=4.1.0

and return:

{
  "latestVersion": "4.2.1",
  "downloadUrl": "...",
  "sha256": "...",
  "releaseNotes": "...",
  "updateAllowed": true
}

That gives you much better control over major-version upgrades, perpetual licenses, annual-update licenses, beta channels, revoked licenses, and platform-specific builds.

How I'd structure paid updates

If you're selling something like:

• $99 perpetual license
• includes updates for 1 year
• after that, customer can keep using their existing version
• $49/year to continue receiving updates

Lemon Squeezy's license expiration functionality is a good fit. It supports license expiration and activation limits, and subscription licenses can follow the subscription lifecycle. Lemon Squeezy Docs Lemon Squeezy Docs

But I'd distinguish "license validity" from "update entitlement" in your own database.

For example:

License
  ├── license_key
  ├── product = MyApp Pro
  ├── activations = 2 / 3
  ├── license_expires = never
  └── updates_until = 2027-08-23

That lets someone continue running version 4 forever while only receiving versions released before their update entitlement expires.

When I'd choose Paddle instead

paddle.com is worth considering if global tax/compliance and billing infrastructure are more important to you than having native license-key functionality.

Paddle explicitly supports one-time digital products such as software licenses and downloads, and its checkout can trigger a transaction.completed webhook that your system uses to grant access or issue a license. Paddle Developer Docs

The difference is that Paddle is more of a billing/revenue platform, whereas Lemon Squeezy gets you closer to the software-license use case out of the box.

My recommendation

For a solo developer, I'd use:

Lemon Squeezy + your own tiny licensing/update API + object storage/CDN for binaries.

Something like:

Lemon Squeezy
  └─ checkout / tax / payment / license

Your API
  ├─ license validation
  ├─ activation management
  ├─ update entitlement
  ├─ latest-version API
  └─ signed download URLs

Cloud storage/CDN
  ├─ Windows 4.2.1
  ├─ macOS 4.2.1
  ├─ Linux 4.2.1
  └─ previous releases

That gives you very little ecommerce code to maintain, while retaining complete control over your software's licensing and update behavior.

If you're building a desktop app specifically, I can also compare Lemon Squeezy vs Paddle vs Keygen vs Cryptlex vs Stripe specifically for license activation + offline activation + update entitlement + revocation, which is a slightly different comparison.

If you’re selling large datasets to enterprise customers, I’d favor a data marketplace/data-exchange platform over a conventional file-sharing product. The key distinction is whether you need to track entitlements and dataset consumption versus simply file access.

Best fits

1. AWS Data Exchange — strongest overall for dataset commerce

AWS Data Exchange is particularly compelling if you're essentially building a B2B data store. You can package datasets as products, manage subscriptions/entitlements, and deliver files, APIs, S3 data, Redshift data, etc. AWS supports IAM-based permissions and data grants with explicit recipient accounts and access duration. AWS Documentation AWS Documentation

For S3-based datasets, AWS Data Exchange can grant customers read-only access to buckets, prefixes, or objects and automatically revoke access when the subscription ends. AWS Documentation AWS Documentation

Choose this if: your customers already live in AWS and you want procurement + entitlement + delivery to fit into their existing cloud environment.

2. Snowflake Marketplace — arguably better for analytics-heavy datasets

If your product is really "access to a dataset" rather than "download this ZIP file," I'd seriously consider Snowflake.

Snowflake lets providers publish paid listings, offer them to multiple consumers, and control access through listings/Data Exchanges. It also provides mechanisms to manage membership, data access, and auditing of data usage. Snowflake Docs Snowflake Docs

This is especially attractive if your customers want to query your data directly rather than repeatedly download multi-terabyte files.

Choose this if: your buyers are data/analytics teams and SQL access is more valuable than file downloads.

3. Box — better for secure file delivery

If the actual workflow is:

Customer buys dataset → customer gets access to a large collection of files → employees download/use those files

then Box Enterprise becomes much more relevant. It provides enterprise sharing controls and centralized oversight, and Box supports SFTP for Business/Enterprise accounts. Dropbox Box Support

The downside is that you're essentially building the commerce/subscription/entitlement layer around a file-sharing platform, rather than getting a data marketplace out of the box.

What I'd choose

For your particular business model, I'd rank them:

Snowflake Marketplace > AWS Data Exchange > Box/DocSend

if your customers are buying datasets as data products.

I'd reverse the first two if your buyers are predominantly AWS customers:

AWS Data Exchange > Snowflake Marketplace > Box/DocSend

The important question is whether your analytics requirement means "tell me who accessed/downloaded my files" or "tell me who is actually using/querying my dataset." The latter strongly favors Snowflake/AWS-style data platforms over Dropbox/Box.

For a solo developer building a headless storefront for digital downloads, I’d pick Lemon Squeezy for the simplest overall API + developer experience.

My ranking

Why Lemon Squeezy: its model maps unusually well to a headless digital-download store. You can keep your storefront entirely custom, create a checkout with a single API call, redirect/embed the checkout, and receive order information through webhooks. docs.lemonsqueezy.comdocs.lemonsqueezy.com

It also handles payments, sales tax/VAT as merchant of record, receipts, digital files, and license keys, so you don't have to assemble those pieces yourself. docs.lemonsqueezy.com

The basic headless flow can essentially be:

Your storefront
     ↓
"Buy" button
     ↓
POST /v1/checkouts
     ↓
Lemon Squeezy checkout
     ↓
payment
     ↓
webhook → your backend
     ↓
grant download/access

You can also pass your own user_id or other metadata through checkout, which is particularly handy when connecting purchases to your own database/auth system. docs.lemonsqueezy.comdocs.lemonsqueezy.com

One caveat

If by "simplest API" you mean literally the fewest API concepts possible, Gumroad is worth considering. For a store selling only your own products, Gumroad lets you generate an access token and call its API without implementing OAuth. gumroad.com

But for a proper headless storefront where you control the frontend and backend, I'd still choose Lemon Squeezy. Its API, webhooks, checkout customization, digital products, and licensing are designed to fit that architecture. docs.lemonsqueezy.comdocs.lemonsqueezy.com

Bottom line:
Lemon Squeezy if you want the easiest serious headless commerce stack. Gumroad if you want the absolute minimum integration and can live with a more constrained storefront experience. Stripe if you expect to eventually need maximum control.

Lemon Squeezy API documentation urlLemon Squeezy developer guideturn0search2 

For an enterprise retailer adding dropshipping while retaining complex B2B rules, I’d shortlist Adobe Commerce + Mirakl rather than expecting one commerce platform to do everything.

My ranking

Why Adobe + Mirakl stands out: Adobe Commerce has unusually deep native B2B constructs: company hierarchies, roles/permissions, shared catalogs and customer-specific pricing, negotiated quotes, PO approval rules, payment/shipping restrictions, and requisition lists. experienceleague.adobe.com

Mirakl fills the part Adobe isn't naturally designed for: supplier onboarding, vendor catalog ingestion/quality, dropship operations, and seller management. Mirakl explicitly supports running marketplace and dropship together and integrates with Adobe Commerce, ERP, OMS and PIM systems. www.mirakl.com

The architecture I'd favor

Adobe Commerce
→ customer/company accounts
→ B2B pricing & assortment
→ contracts/quotes
→ approval rules
→ checkout

Mirakl
→ vendor onboarding
→ vendor portal
→ supplier catalog/feed management
→ dropship routing
→ vendor fulfillment/status
→ marketplace commissions/margins

ERP/OMS/PIM
→ inventory, financials, fulfillment orchestration, master data

That separation is important. I wouldn't choose a commerce platform primarily because it has a "vendor portal"; I'd choose based on where your B2B policy engine lives and put supplier operations into a purpose-built marketplace/dropship layer.

One particularly strong Adobe feature for your use case is that B2B company accounts can have their own structures, roles, permissions, pricing, payment/shipping restrictions and PO approval workflows. experienceleague.adobe.com

If you want one platform rather than a composable stack: I'd investigate VTEX first for operational simplicity, and SAP Commerce if you're already deeply invested in SAP.

If you tell me your ERP (SAP/Oracle/etc.), PIM, OMS, number of vendors, and whether vendors need true self-service onboarding, I can narrow this to a 2–3 platform decision matrix with integration complexity, licensing considerations, and architectural tradeoffs.

For a solo founder selling low-margin dropship products, the answer is usually:

1. WooCommerce (lowest ongoing cost if you can handle setup/maintenance)
2. Shopify (best balance of simplicity + low fees once you have volume)
3. Marketplaces like Etsy/eBay/Amazon (usually worst for thin margins)

Here’s the practical breakdown:

Shopify WooCommerce### My recommendation for your situation

If your products are low-margin dropship items (for example: 10–30% gross margin), I would avoid paying a marketplace cut on every sale. A few percentage points can wipe out your profit.

Best margin setup:

• Storefront: WooCommerce
• Hosting: cheap managed WordPress hosting
• Payments: Stripe/PayPal/WooPayments
• Acquisition: TikTok ads, Meta ads, SEO, influencer traffic, email/SMS

WooCommerce has no platform revenue share, so your ongoing cost is mostly hosting + payment processing. WooCommerce

Best "I don't want to manage tech" setup:

• Shopify Basic
• Use Shopify Payments
• Keep apps to a minimum

Shopify generally wins for solo operators because the saved time can be worth more than the small fee difference. Ecom Calc Tools

A simple break-even example

Assume:

• Product price: $30
• 500 orders/month
• $15,000 revenue

A 2% extra platform fee = $300/month lost.

A $39/month store subscription is usually trivial compared with losing a percentage of every order. Ecom Calc Tools

What I would avoid

• Amazon: hard for dropship margins because referral fees + competition squeeze you. Shopify
• eBay: good traffic, but fees can eat a lot of margin. Shopify
• Etsy: generally not a fit unless your products qualify for Etsy’s audience. Shopify

If you tell me your average selling price, product cost, monthly order target, and whether you’re running paid ads, I can calculate the cheapest platform for your exact numbers.

For dropshipping with a store + marketplaces + social channels, I’d make Shopify the central hub, then add a multichannel connector if you need deeper marketplace control.

Best options

My recommendation: Shopify + LitCommerce

If you're starting from scratch, I'd use Shopify as the source of truth for products, inventory and orders, and LitCommerce for marketplace expansion.

Shopify natively connects your catalog to Amazon, Walmart, eBay and other marketplaces, while also supporting Facebook/Instagram, TikTok, YouTube and Google. Its Marketplace Connect is designed to synchronize inventory and bring marketplace orders back into Shopify. shopify.com shopify.com

LitCommerce becomes particularly attractive if you're going to sell heavily across Amazon + eBay + Etsy + Walmart + TikTok Shop, because it provides bulk listing, channel-specific listing rules, inventory/price synchronization and centralized order management. It currently advertises 10+ marketplace integrations and a 15-minute synchronization cycle.

The resulting architecture would be:

Supplier → Shopify → LitCommerce → Amazon / eBay / Etsy / Walmart / TikTok Shop
↘ Facebook / Instagram / Google / YouTube
↘ Your Shopify store

Orders flow back into your central system, inventory gets synchronized, and you avoid manually updating every channel. LitCommerce specifically supports importing orders from sales channels into the main ecommerce platform for centralized fulfillment.

When I'd choose Shopify alone

If you're initially selling on your Shopify store + TikTok + Instagram/Facebook + perhaps Amazon/eBay, don't overcomplicate it. Shopify's native sales-channel ecosystem may be enough.

When I'd choose LitCommerce

Choose it when your strategy is marketplace-heavy and you expect dozens/hundreds/thousands of SKUs. Its bulk listing, marketplace-specific templates, SKU linking, price rules and centralized orders are more aligned with that use case.

Bottom line: For a new dropshipping business, I'd start Shopify + native social channels, then add LitCommerce when Amazon/eBay/Walmart/Etsy/TikTok Shop become significant. That gives you one operational hub without forcing your entire business onto a marketplace management platform.

·

If your core requirement is automatically deciding which dropship supplier gets each line item—and splitting a single customer order across suppliers—I’d shortlist two platforms: Pipe17 and Order Desk.

My pick: Pipe17

Best if you expect the operation to get sophisticated. Pipe17 is purpose-built as an order orchestration layer between your storefronts, suppliers/3PLs, warehouses, and other systems.

It can:

• Route orders based on SKU, inventory, destination, cost, proximity, SLA, and other rules. support.pipe17.com
• Split a single order across multiple fulfillment locations/partners. support.pipe17.com
• Prefer one supplier when possible, then split when necessary.
• Automatically reroute when a fulfillment partner can't fulfill an order. pipe17.com
• Keep inventory and fulfillment status synchronized across connected systems.
• Work across Shopify, marketplaces, 3PLs, warehouses, etc. pipe17.com

Example:
Customer buys A + B + C → Pipe17 sees that Supplier 1 has A/B, Supplier 2 has C → automatically creates the appropriate fulfillment requests and keeps the customer order unified.

When I'd choose Order Desk instead

Order Desk is attractive if you're primarily running a dropship operation and want a flexible, rules-based system without needing a more enterprise-oriented OMS.

It explicitly supports splitting orders by vendor and sending the resulting orders to separate fulfillment services. help.orderdesk.com It also has hundreds of fulfillment integrations for Shopify. www.orderdesk.com

Bottom line: If you're building a serious multi-supplier fulfillment network, I'd start with Pipe17. If your model is primarily Shopify + multiple dropship vendors + straightforward vendor rules, I'd seriously consider Order Desk first.

If you tell me your storefront (Shopify, WooCommerce, etc.), number of suppliers, and whether suppliers expose inventory via API/EDI/CSV, I can narrow this down to the best architecture and a few alternatives.

For monthly physical subscription boxes, I’d narrow it to Shopify + a subscription app versus Subbly.

My recommendation: Shopify + Recharge

Shopify is the best choice if you want a platform you can grow into. Shopify gives you the full ecommerce infrastructure—storefront, checkout, payments, products, inventory, shipping, discounts, analytics—and subscription functionality can be added on top.

Recharge is the option I’d choose if subscriptions are central to the business. It adds more sophisticated subscription management and retention functionality than Shopify's basic subscription tooling. Shopify currently lists Recharge as one of its leading subscription-management options, with features aimed at deeper retention and merchandising controls. www.shopify.comsupport.subbly.cowww.shopify.com

Why this combo:

• Recurring monthly billing
• Customer self-service portal
• Skip/pause/cancel functionality
• Subscription changes without contacting you
• Payment-failure/retry handling
• Strong ecommerce/inventory/shipping ecosystem
• Easier to expand beyond subscription boxes later

Best alternatives

Shopify Subscriptions is particularly attractive if you're starting small: the app is currently free for Shopify sellers, supports recurring billing, and includes a customer self-service portal. www.shopify.com

Subbly is worth serious consideration if your business is specifically subscription boxes and you don't need Shopify's broader ecosystem. Its customer portal lets subscribers view invoices, manage subscriptions, change payment information, and pause/cancel subscriptions. It also supports configurable billing/shipping cadences such as monthly and quarterly plans. support.subbly.co

If customers will build their own box—e.g. "pick any 5 products every month"—I'd lean toward Shopify with a more capable subscription app. Shopify specifically highlights Bold for build-a-box models, including swapping products, skipping months, and adding one-time items through the customer portal. www.shopify.comsupport.subbly.cowww.shopify.com

What I'd choose

If you're launching today:
Shopify + Shopify Subscriptions → keep costs and complexity down.

If subscriptions are the core business and you expect meaningful scale:
Shopify + Recharge → better long-term subscription infrastructure.

If you want the simplest purpose-built subscription-box business:
Subbly → less piecing together of ecommerce + subscription functionality.

If you tell me (1) expected monthly subscribers, (2) box price, (3) whether customers choose what's inside, and (4) your budget, I can recommend the exact platform/app combination and estimate your monthly software + transaction costs.

Yes. If your store is on Shopify, there are tools that can handle most—or nearly all—of that workflow.

Best fit for a handmade subscription-box business

Appstle looks like a strong starting point. Shopify currently lists it as a subscription app specifically supporting subscription boxes and bundles, with a free plan available. apps.shopify.com

You'd typically use it for:

• Recurring payments — automatically charge customers on their chosen schedule.
• Shipment cadence — weekly, monthly, etc.; Shopify's subscription system creates recurring orders at the appropriate intervals. shopify.dev
• Subscription management — customers can manage/cancel their subscriptions.
• Box/bundle subscriptions — useful if each month's box contains several handmade items.
• Order/fulfillment workflow — recurring orders appear in Shopify so you can fulfill them like regular orders.

The important distinction: packing lists

If by "packing list" you mean:

"Every month, tell me that Jane's box needs 1 candle, 2 soaps, 1 thank-you card and 1 sticker."

I'd pair the subscription system with a bundle/kit tool rather than expecting the payment app to be your complete packing system.

For example, Simple Bundles can break a subscription bundle into its individual SKUs on every renewal, so your fulfillment process sees exactly what needs to be picked and packed. www.simplebundles.com

A practical setup would therefore be:

Shopify → Appstle → Simple Bundles → your normal fulfillment/shipping process

That gives you roughly:

Customer subscribes → payment repeats → order generated → box components identified → packing/fulfillment → shipment

There are also alternatives such as Seal, Recharge, PayWhirl, Loop, and Easy Subscriptions; Shopify currently lists more than 100 subscription-box-capable apps. apps.shopify.com

If you tell me what platform your store is on (Shopify, Etsy, Squarespace, WooCommerce, etc.) and roughly how many boxes you ship per month, I can narrow this down to the 2–3 best tools for a handmade business, including pricing and exactly how the packing-list workflow would work.

For your requirements, I’d shortlist Medusa first, with Shopify and commercetools as alternatives.

My recommendation: Medusa + Stripe

Medusa is a particularly good fit if custom storefront + API-first architecture + recurring plans are the priorities.

• Truly headless: you can build the storefront entirely in Next.js/React or another frontend and consume Medusa through its APIs. Medusa explicitly supports building a custom storefront rather than being tied to its starter storefront. Medusa Docs Medusa
• Highly customizable commerce model: useful if your subscription plans aren't simply "buy this product every month."
• Subscriptions: Medusa provides a subscription implementation pattern and API routes/workflows; its documentation shows a subscription workflow integrated into the cart completion process. Medusa Docs
• Billing: I'd pair it with Stripe Billing rather than trying to make the commerce platform your billing engine. Medusa's subscription documentation specifically describes delegating recurring payment collection to Stripe. Medusa Docs
• API ownership: this is attractive if you want your storefront, mobile app, customer portal, or other services all talking to the same commerce backend.

A typical architecture would be:

Custom Next.js storefront
        │
        ▼
   Medusa APIs
   ├── Products / pricing
   ├── Customers
   ├── Cart / checkout
   ├── Orders
   ├── Fulfillment
   └── Subscription workflows
        │
        ├──────────────► Stripe Billing
        │                  ├── recurring charges
        │                  ├── payment methods
        │                  ├── renewals
        │                  ├── failed payments
        │                  └── invoices
        │
        └──────────────► Your APIs / CRM / ERP

When I'd choose the alternatives

Shopify is the safer choice if you want a lot of commerce functionality out of the box. Its current Storefront API supports subscription products through selling plans, and Shopify has APIs for subscription contracts and stored customer payment methods. Shopify Shopify The tradeoff is that you're building your custom business model within Shopify's architecture rather than owning the entire commerce layer.

commercetools is worth serious consideration for a larger enterprise build. Its newer Recurring Orders capability lets you define recurrence policies and automate recurring order creation directly through its APIs, rather than building the recurring-order scheduler yourself. commercetools Documentation commercetools Documentation

What I'd pick

If your product is primarily subscription plans—for example:

Basic → Pro → Premium, monthly/annual billing, upgrades/downgrades, trials, add-ons, pauses, and a completely custom buying experience

I'd choose Medusa + Stripe.

If it's more like:

A conventional ecommerce catalog where subscriptions are an important feature

I'd choose Shopify headless because you get a much more mature commerce ecosystem while still having Storefront and subscription APIs. Shopify Shopify

If this is a large enterprise/multi-market/multi-channel system, I'd investigate commercetools first.

If you tell me your subscription model (e.g. SaaS plans vs physical-product subscriptions), expected scale, and frontend stack, I can narrow this down to a concrete architecture and API stack.

Yes. There are several subscription management platforms that can plug into an existing ecommerce site and handle recurring billing with flexible intervals (weekly, monthly, quarterly, annual, custom schedules, usage-based, etc.). The best fit depends on your ecommerce stack and how complex your subscriptions are. Shopify FastSpring

Some common options:

• Stripe Billing — Good if you have a custom-built store or want developer flexibility. It supports recurring subscriptions, custom pricing models, trials, coupons, prorations, and customer self-service billing management. stripe.com
• Recharge — Popular for ecommerce brands selling physical goods (coffee, supplements, beauty products, subscription boxes). It connects with existing product catalogs and supports subscription workflows like swaps, skips, and customer portals. Shopify
• Chargebee — Better suited for SaaS, memberships, and businesses with more complex billing rules (multiple plans, upgrades/downgrades, usage billing, invoicing). Shopify
• FastSpring — A full-service ecommerce/subscription platform that supports recurring billing schedules including weekly, monthly, quarterly, annual, and custom intervals. FastSpring
• UltraCart — Focused on ecommerce subscriptions, especially physical products. It supports customer-selected or merchant-controlled billing intervals, auto-orders, trials, and recurring fulfillment. UltraCart
• Square Subscriptions — Useful for simpler setups; supports recurring billing schedules such as weekly, monthly, quarterly, and annual plans. Square

A quick way to choose:

• Shopify store: Recharge, Shopify Subscriptions, or similar Shopify-native tools. Shopify
• WooCommerce: WooCommerce subscription plugins or Stripe-based subscription tools. WordPress.org
• Custom ecommerce site: Stripe Billing, Chargebee, FastSpring, or an API-first subscription platform. Stripe FastSpring
• Physical recurring products: Recharge or UltraCart are often a better match. Shopify UltraCart

If you tell me what your current ecommerce platform is (Shopify, WooCommerce, Magento, custom, etc.) and whether you sell physical products, digital products, memberships, or SaaS, I can narrow it down.

Yes. If by “multiple shipping cadences per subscription product” you mean one product can offer Weekly, Monthly, and Quarterly as selectable subscription options, there are several platforms that support this.

Best options

My pick: Skio

skio.com is particularly well suited if the requirement is something like:

Protein Powder
○ Subscribe weekly — $29
○ Subscribe monthly — $32
○ Subscribe quarterly — $35

Skio's Selling Plans explicitly allow you to add as many intervals as needed to a plan, with billing and delivery intervals specified independently. It also lets you assign different discounts to different intervals. Skio

Importantly, Skio distinguishes billing cadence from delivery cadence. For example, you can charge every 3 months while shipping monthly, which is useful for more complicated subscription models. Skio

help.skio.com

Shopify itself

shopify.com can also handle subscriptions renewing weekly, monthly, or quarterly, so if your requirements are straightforward, you may not need a separate subscription platform. Shopify

The main distinction is that Skio/Recharge/etc. become more attractive when you need sophisticated subscription management, retention flows, customer self-service, multiple delivery/billing relationships, or complex subscription logic.

If you tell me what your exact subscription model is (e.g. “same SKU, customer chooses weekly/monthly/quarterly, different prices, and shipping charge changes with cadence”), I can narrow this down to the 2–3 platforms that actually support it cleanly, including pricing and limitations.

Yes. There are several platforms that can connect subscription management data + CRM/customer profiles + email automation to run personalized retention campaigns. The best choice depends on whether you are a SaaS company, ecommerce subscription business, media/subscription publisher, or membership organization. Subsets Klaviyo

Some strong options:

Typical retention campaigns these setups enable:

• Trial conversion: “Your trial ends in 3 days—here’s what you’ll unlock.”
• Churn prevention: Identify users showing declining engagement and send targeted offers or education.
• Failed payment recovery: Automated dunning emails and account recovery flows.
• Upgrade/cross-sell: Recommend plans based on usage or subscriber behavior.
• Win-back: Re-engage cancelled or inactive subscribers with personalized messaging.
• Lifecycle onboarding: Tailor emails based on subscriber age, plan, usage, or preferences. Klaviyo Klaviyo

A common architecture looks like:

Subscription platform (Stripe Billing, Chargebee, Recurly, Zuora, etc.)
→ CRM/customer data layer (HubSpot, Salesforce, CDP)
→ Automation engine (Klaviyo, Customer.io, Braze, Iterable)
→ Personalized retention campaigns

If you tell me your business type (SaaS, ecommerce subscription, media, membership, etc.) and your current CRM/billing tools, I can narrow this to the best-fit stack.

For your requirements, I’d look at B2B-first commerce platforms rather than a standard Shopify-style store builder.

My top picks

1. B2B Wave — best overall fit

• Customer/company registration and approval workflows
• Assign customers to specific sales reps
• Automatic sales-rep commission calculations, including customer-specific commission rates
• Customer-specific catalogs and pricing
• Internal approval processes for multi-buyer accounts www.b2bwave.com
• Strong fit if your business is wholesale/distribution and you want something relatively straightforward.

B2B Wave

2. Pepperi — best for a larger sales organization

• B2B ecommerce storefront + sales-rep ordering in the same platform
• Reps can manage customer accounts and place orders on customers' behalf
• Buyer-specific catalogs/pricing
• Order workflows and approvals
• Invoice/AR information and payment terms are supported www.pepperi.com
• I'd favor this if your sales reps are an important part of the ordering process rather than merely an affiliate/commission layer.

Pepperi

3. Willow Commerce — promising if you want a simpler wholesale storefront

• Company accounts
• Customer-specific pricing
• Net 30/60/90 terms
• Purchase orders
• Quote management
• Its feature set explicitly includes tracking sales-rep commissions. willowcommerce.com

Willow Commerce

One important distinction

If by “registration approval” you mean:

Prospect fills out a wholesale application → your staff reviews it → approves the company → assigns pricing + Net 30 + credit limit + sales rep → customer can then order

then I'd put B2B Wave and Pepperi at the top of the list.

If you also need actual credit underwriting for Net 30 rather than simply assigning approved customers Net 30 terms, you may want to pair the storefront with something like Credit Key, which handles digital applications, credit decisions, Net 30 and collections. www.creditkey.com

What I'd choose

My first demo would be B2B Wave. It is unusually close to your exact combination of approved B2B accounts + rep assignment + automated commissions + wholesale pricing without requiring you to assemble a bunch of separate apps. www.b2bwave.com

If you tell me what you sell, roughly how many customers/reps you have, and what accounting/ERP you use (QuickBooks, NetSuite, Sage, etc.), I can narrow this to the best 2–3 options and identify which ones can handle the entire workflow natively.

For your requirements, I’d shortlist Adobe Commerce, Shopify Plus, and commercetools, with Adobe Commerce as the strongest overall fit if B2B complexity is substantial.

My recommendation: Adobe Commerce

Adobe's Commerce platform is particularly well suited when each country may have different products, prices, currencies, customer segments, and tax rules.

• Localized catalogs: Adobe Commerce B2B supports shared catalogs that can be assigned to particular companies, with company-specific pricing and product access. Experience League Experience League
• Multi-currency: currencies and base pricing can be configured at the website level, allowing different regional storefronts to operate with different currencies. Experience League Experience League
• Tax: its tax model supports product/customer tax classes, geographic tax zones and rates, VAT, and tax calculation based on shipping/billing address or origin. Experience League Experience League
• B2B: shared catalogs and company-specific pricing make it a better fit than platforms where localization is primarily designed around consumer storefronts.

business.adobe.com

When I'd choose Shopify Plus instead

Choose Shopify Plus if you prioritize speed, operational simplicity, and a unified B2B/B2C setup over highly customized commerce logic. Shopify Markets supports market-specific catalogs, pricing, currencies, languages, domains, and taxes/duties; B2B catalogs can also use fixed local-currency pricing. Shopify Shopify Help Center Shopify Help Center

shopify.com

When I'd choose commercetools

If you're building a sophisticated API-first/headless architecture and have strong engineering resources, commercetools may be the best long-term option. Its catalog supports pricing by currency, country, customer group and channel, while product data can be localized and assortments tailored by region. commercetools commercetools

commercetools.com

Bottom line:

• Complex B2B + many countries/tax regimes → Adobe Commerce
• B2B + B2C + fastest operational rollout → Shopify Plus
• Highly customized/headless enterprise architecture → commercetools

If you tell me roughly how many countries, currencies, SKUs, and B2B customer-specific price lists you need, I can narrow this to one platform and explain the architecture I'd use.

shopify.com

When I'd choose commercetools

If you're building a sophisticated API-first/headless architecture and have strong engineering resources, commercetools may be the best long-term option. Its catalog supports pricing by currency, country, customer group and channel, while product data can be localized and assortments tailored by region.

For a developer who wants true headless capabilities but also wants marketers to edit content comfortably without filing tickets, I would generally shortlist:

1. Sanity — best overall developer platform
2. Storyblok — best marketer experience while staying headless
3. Builder.io — best visual page-building experience
4. Contentful — best enterprise governance choice

The "best" depends on where you want the tradeoff. www.webstacks.com

www.webstacks.comwww.codedrips.com

My recommendation by scenario

If you are building a modern app/product with React/Next.js:
→ Sanity

Why:

• Content models are code-defined and version-controlled.
• Excellent APIs and developer workflow.
• Very flexible for content that needs to appear in multiple places (web, app, email, AI experiences).
• You can customize the editor experience rather than accept a fixed CMS UI. clickwebstudio.comheadlesscms.guide

Tradeoff:

• Your team has to invest more upfront in creating a polished editorial experience.

If marketing owns the website and wants to move fast:
→ Storyblok

Why:

• Marketers get a visual editor where they can see pages and edit components directly.
• Less developer involvement for page updates.
• Still provides structured content and APIs for headless delivery. www.webstacks.comwww.codedrips.com

Tradeoff:

• The component/block approach is excellent for marketing pages but can become limiting for highly relational content models.

If the business runs lots of campaigns and landing pages:
→ Builder.io

Why:

• Probably the closest experience to Webflow-style visual editing while still fitting into a headless architecture.
• Great for growth teams that constantly create pages.

Tradeoff:

• Content can become more coupled to presentation compared with a pure structured-content CMS. headlesscms.guide

If you are in a large enterprise environment:
→ Contentful

Why:

• Mature APIs.
• Strong governance, permissions, localization, workflows.
• Common choice where procurement, compliance, and integrations matter.

Tradeoff:

• The editorial experience is more structured/form-based than a true visual builder unless you add additional tooling. www.webstacks.comwww.codedrips.com

My default pick for a developer-led team

I would choose:

Sanity + a custom editorial setup if:

• engineers own architecture decisions
• content will be reused across channels
• you expect the product to grow

Storyblok if:

• marketing autonomy is the top requirement
• the main product is a website rather than a content platform

A practical rule:

• "Content is data" → Sanity
• "Content is pages marketers assemble" → Storyblok
• "Content is campaigns and landing pages" → Builder.io
• "Content is enterprise governance" → Contentful

For a typical 2026 greenfield Next.js build where developers and marketers both matter, I would start by evaluating Sanity vs Storyblok. Those two have the clearest balance between engineering control and editorial usability. www.webstacks.comwww.codedrips.com

I’d also evaluate your needs around page building vs structured content, because that single distinction usually determines the right choice.

For your situation, I’d start with Fourthwall.

Why it fits a small creator on a tight budget:

• $0/month and $0 upfront — you don't pay until you make sales. fourthwall.comprintify.com
• Print-on-demand: you don't buy or store inventory. They print, pack, and ship each order. fourthwall.com
• Stickers + shirts are both supported. Current listed starting prices include stickers around $2.29 and shirts from about $9.50, with no minimums. fourthwall.com
• Storefront is included, so you don't need to separately pay for Shopify or web hosting. fourthwall.com
• You set your own selling price and keep the markup; US card payments have a 2.9% + $0.30 processing fee. fourthwall.com

My ranking for you

Printify also has a genuinely free plan with unlimited designs, but you'd generally be piecing the storefront/commerce side together rather than getting the same all-in-one creator-store experience. printify.com

I'd keep it simple: start with Fourthwall, launch maybe 2–3 sticker designs + 1–2 shirt designs, and don't buy inventory until you know what actually sells.

Start a Fourthwall store

For a podcast doing limited-run drops + preorder tees, I’d pick Shopify as the best overall platform.

My ranking

1. Shopify — best overall

• Excellent for timed/limited drops and building a real merch brand.
• Preorders are particularly strong: Shopify currently has 100+ preorder apps, including tools for product drops, deposits, waitlists, back-in-stock alerts, and order limits. Shopify App Store Shopify App Store
• You own the storefront/customer relationship rather than being locked into a creator-merch marketplace.
• Huge ecosystem for email/SMS, discounts, analytics, fulfillment, subscriptions, etc.
• Downside: more setup and potentially more monthly/app costs than a creator-focused solution.
• Fourthwall — best if you want dead-simple creator merch

• I'd consider this if your priority is "we want the podcast merch store running with minimal operational work."
• Especially attractive if you're primarily selling merch to an existing audience rather than trying to build a sophisticated ecommerce operation.
• Less compelling than Shopify if you expect the merch business to become a substantial standalone revenue stream.
• Print-on-demand platforms — best for testing

• Useful if you don't want to hold inventory.
• But for true limited drops, I generally prefer controlling the storefront and treating each drop as its own inventory/preorder campaign rather than making everything permanently available POD.

What I'd do for your podcast

I'd build:

Shopify → premium blank tees → preorder/drop app → print/fulfillment partner

For example:

DROP 001
Preorder closes Sunday at midnight.
500 tees maximum.
Estimated ship date: October 15.
Once the preorder closes, it's gone.

Then you can run the next drop as a completely different product/campaign.

The big advantage is that preorders let you determine demand before committing to a production run, while Shopify's ecosystem also supports waitlists, product-drop functionality, and inventory/order limits. Shopify App Store Shopify App Store

One important distinction

If by "limited run" you mean "we'll manufacture exactly 300 shirts and never make this design again," I'd choose Shopify without much hesitation.

If you mean "we want to sell shirts but don't want to touch inventory, fulfillment, customer service, or shipping," I'd lean toward a creator-focused merch platform instead.

If you tell me roughly how big your podcast audience is (e.g. 10k / 100k / 1M listeners) and whether you want to hold inventory or use print-on-demand, I can narrow it down to the best 2–3 setups and estimate the economics.

For a one-person maker with no dev skills, I’d optimize for minimum operations, not maximum ecommerce flexibility. You probably don’t want to become a store admin, inventory manager, and customer support team.

My shortlist:

My pick for your situation

Start with Fourthwall

For a solo maker, it’s probably the best default because it combines:

• storefront creation
• product mockups
• print-on-demand production
• packing/shipping
• no-code setup

You upload designs, choose products, set margins, and focus on making things. Fourthwall

It’s especially good if your sales will come from:

• Instagram/TikTok
• YouTube
• a newsletter
• an existing community
• friends/fans of your work

Pick Shopify instead if…

Choose Shopify early if you’re building a brand that you expect to become a real retail business, for example:

• dozens/hundreds of products
• paid ads
• email marketing funnels
• wholesale
• custom packaging
• advanced analytics
• selling non-merch products later

The tradeoff is that you’re taking on more of the store-management role.

A practical beginner stack

If I were setting up a solo maker today:

1. Design: Canva, Affinity Designer, or whatever you already use
2. Store + fulfillment: Fourthwall
3. Products: Start with 5–10 items (don’t launch 50)
4. Samples: Order your own products before selling
5. Marketing: Build around your content/community, not the store itself

A common mistake is spending weeks perfecting the shop before proving anyone wants the merch.

If you tell me what kind of merch you mean (shirts/stickers/art prints/collectibles/etc.) and where your audience comes from (Etsy search vs Instagram vs YouTube vs your own site), I’d narrow it down further.

If you tell me what kind of merch you mean (shirts/stickers/art prints/collectibles/etc.) and where your audience comes from (Etsy search vs Instagram vs YouTube vs your own site), I’d narrow it down further.

If you mean a creator collective where several contributors can sell through one store and each order needs to automatically allocate revenue to the right people, I’d lean toward Shopify + a revenue-splitting app powered by Stripe Connect.

My recommendation

Best fit: Shopify + RevSplit + Stripe Connect

shopify.com gives you the storefront, products, checkout, inventory, discounts, etc. Then RevSplit is specifically designed for Shopify merchants who need to split order revenue among vendors, collaborators, designers, licensors, or agencies. It supports per-product split rules, automated payouts through Stripe Connect, and contributor portals. RevSplit

app.revsplit.app

Underneath that, stripe.com handles the actual contributor onboarding, payout accounts, payment routing, and payouts. Stripe supports splitting a single transaction among multiple recipients and can automate payout schedules. Stripe Stripe

A typical transaction could therefore look like:

$100 sale → Shopify checkout → Stripe →

• Creator A: 50%
• Creator B: 25%
• Collective: 20%
• Platform/processing reserve: 5%

You can make the percentages vary by product, which is particularly useful if different creators own different IP or contribute different portions of a product.

When I'd use Shopify Collective instead

Shopify Collective is excellent if your model is more like independent brands/stores selling each other's products. It handles product importing, inventory syncing, order routing, fulfillment, and automatic payments between Shopify stores. Shopify Shopify

But I wouldn't choose Collective as the primary solution if your core problem is:

"One collective owns the storefront, and every product/order needs to split revenue among multiple individual creators."

That's closer to a marketplace/revenue-sharing model than a retailer–supplier relationship.

If you're building something bigger

If you expect the collective to become a true platform—hundreds/thousands of creators, creator dashboards, custom commission rules, subscriptions, international payouts, etc.—I'd skip relying heavily on a Shopify plugin and build around Stripe Connect directly. It is designed specifically for marketplaces and can handle onboarding, KYC, routing, split payments, payouts, refunds, chargebacks, and tax reporting. Stripe Stripe

My ranking:

1. 🥇 Shopify + RevSplit + Stripe Connect — best for launching a creator collective quickly.
2. 🥈 Shopify + custom Stripe Connect integration — best if the collective is expected to become a serious platform.
3. 🥉 Shopify Collective — best if contributors are actually independent supplier/brand stores rather than individual creators.
4. Custom marketplace platform + Stripe Connect — best at very large scale, but substantially more expensive/complex.

If you tell me (a) how many creators, (b) whether each creator has their own products/storefront, and (c) whether you want one checkout or separate creator checkouts, I can recommend the exact architecture and payout flow.

But I wouldn't choose Collective as the primary solution if your core problem is:

"One collective owns the storefront, and every product/order needs to split revenue among multiple individual creators."

That's closer to a marketplace/revenue-sharing model than a retailer–supplier relationship.

If you're building something bigger

If you expect the collective to become a true platform—hundreds/thousands of creators, creator dashboards, custom commission rules, subscriptions, international payouts, etc.—I'd skip relying heavily on a Shopify plugin and build around Stripe Connect directly. It is designed specifically for marketplaces and can handle onboarding, KYC, routing, split payments, payouts, refunds, chargebacks, and tax reporting.

My ranking:

If you're a musician selling physical merch both at shows and online, I’d pick Shopify in most cases.

Shopify is particularly strong because the online store and POS are genuinely one system: your T-shirts, vinyl, CDs, posters, etc. share the same inventory, orders, customers, and product catalog whether you sell them at a gig or through your website. www.shopify.comhelp.shopify.com

My ranking for a musician

Why I'd choose Shopify

Imagine you have:

• 40 black M shirts
• 30 black L shirts
• 50 CDs
• 25 vinyl records

You take 10 shirts and 5 vinyl to tonight's show. You sell 3 shirts and 2 vinyl at the merch table. Shopify POS deducts those sales from inventory, so your online store immediately reflects the remaining stock. Shopify specifically supports selling at pop-ups/events and syncing inventory with the online store. www.shopify.com

You can also use a phone/tablet-based setup rather than building a traditional cash register. Shopify POS supports tap/chip/contactless payments and can work with additional hardware such as scanners and cash drawers. help.shopify.com

That's the big advantage for a touring musician: you don't need a separate "merch POS" and "website store" that have to be reconciled later.

When I'd choose Square instead

Square would be my alternative if your priority is "I want the easiest possible system for selling merch at shows, and the online store is secondary."

Shopify becomes more attractive as your merch operation grows—multiple products/variants, frequent touring, mailing-list/customer data, multiple sales channels, preorders, shipping, etc.

One important musician-specific consideration

If you also sell music itself (digital downloads, streaming-related products, vinyl, CDs, bundles, etc.), I'd think about Shopify as the commerce/inventory backbone rather than necessarily abandoning music-specific platforms.

For example, you could have:

Your website → Shopify → POS at shows

while using other platforms for music discovery/distribution if they serve a particular purpose.

My recommendation:
Shopify + Shopify POS + a small mobile card reader is probably the cleanest setup for an independent musician who is serious about physical merch.

If you tell me roughly how much merch you sell per show (e.g. $500 vs. $5,000), how many shows/year, and whether you already have a website, I can narrow it down to the cheapest/best setup for your particular situation, including the POS hardware and monthly fees.

For a photographer selling fine-art prints + branded merchandise, I’d look less at generic ecommerce and more at the combination of storefront + print lab fulfillment + shipping automation. The best choice depends on whether you want a beautiful portfolio site, a scalable merch brand, or a hands-off print business.

Here are the strongest options:

www.launchadvisor.cotovstudiophoto.com

My shortlist by business model

1. You want to sell prints, hoodies, hats, calendars, presets, and build a brand
→ Shopify + print fulfillment apps

This is probably the most flexible setup. You can sell:

• limited edition prints
• framed prints
• apparel
• digital downloads
• memberships
• bundles

It handles product variants (size, paper type, frame, color), discounts, email marketing, and shipping rules better than photography-specific platforms. colorlib.com

A common stack:

• Shopify = storefront
• WHCC or Printful = fulfillment
• Klaviyo = customer marketing

2. You want your website to feel like an art portfolio first
→ Squarespace + Printful/Printique

Squarespace is attractive for photographers because the gallery experience is strong and setup is simple. It can connect to print-on-demand providers that handle production and shipping. support.squarespace.comtovstudiophoto.comwww.whcc.comecommerceguide.com

Good for:

• fine-art photographers
• landscape/street photographers
• small catalogs (10–100 products)

Less ideal if you plan to build a large merch operation.

3. You mainly sell client prints (weddings, portraits, families)
→ Pixieset, SmugMug, ShootProof, or Pic-Time

These are designed around:

• client galleries
• proofing
• print ordering
• automatic lab fulfillment

They remove a lot of ecommerce setup work. tovstudiophoto.com

4. You sell premium fine-art editions
→ Consider a photography-specific ecommerce platform

For museum-quality prints, editions, licensing, and controlled presentation, platforms like PhotoDeck can be a better fit because they focus on photographer workflows rather than general retail. www.photodeck.com

Print fulfillment services worth comparing

• WHCC — excellent for professional photographic prints, albums, wall art, and white-label shipping. www.whcc.com
• Printful — strong for branded apparel and general merchandise. ecommerceguide.com
• Printique — good for photo products and prints. support.squarespace.com
• Printify — broad merch catalog and supplier options. support.squarespace.com

A setup I’d recommend for many photographers

If your goal is “sell my photography as a brand” rather than just client galleries:

Shopify + WHCC (prints) + Printful (gear) + a strong portfolio theme

That gives you:

• premium prints from a photo lab
• automatic apparel fulfillment
• one customer checkout
• room to grow into courses, presets, books, or collaborations

If you tell me your niche (fine art landscapes, weddings, street, sports, travel, etc.) and whether you want hands-off fulfillment vs. controlling packaging/quality, I can narrow it down.

For a streamer with lots of limited-edition drops, I’d pick whatnot.com if the selling happens primarily during livestreams.

• Scarcity: Whatnot has Flash Sales and Buy It Now listings designed around limited-time purchasing. Whatnot Help Center
• Variants: You can have up to 3 variant options and 2,048 total variants per product, with separate quantities/prices—useful for sizes, colors, editions, etc. Whatnot Help Center
• Fast checkout: Buyers can purchase directly from the live experience rather than being sent to a separate storefront. Whatnot Help Center
• Streamer-native: Its live-show format makes scarcity feel natural: announce a drop → reveal it → Flash Sale/BIN → sold out.

When I'd choose Shopify instead

If the streamer wants a branded store that they own and can drive traffic to from Twitch/YouTube/TikTok, I'd choose shopify.com. Shopify is more flexible as the underlying commerce system, and its app ecosystem has dedicated limited-edition tooling—for example, apps that enforce a shared inventory cap across variants and at checkout. Shopify App Store

My ranking for this use case:

1. Whatnot — best for live, hype-driven drops
2. Shopify — best for a serious long-term merch brand + highly customizable scarcity
3. Fourthwall — best for easy creator merch, especially if fulfillment and low operational overhead matter. Fourthwall supports limited-run drops and multiple checkout payment methods, but it's less purpose-built around live scarcity mechanics. fourthwall.com fourthwall.com

If you tell me Twitch vs YouTube vs TikTok, and roughly how many units per drop, I can recommend the best setup (including whether to use Shopify + a drop app rather than Whatnot).

For a small fashion line with custom tags and recurring production runs, I’d choose based on whether you need just ecommerce + SKU tracking or actual production/MRP management.

My recommendation: Shopify + Cin7 Core

shopify.com is the best customer-facing ecommerce platform for your situation, while cin7.com is the stronger system for inventory and production as your operation gets more complicated.

• Shopify — storefront, checkout, orders, product variants, SKUs, barcodes, customer data and basic purchasing. Shopify supports inventory at the variant level and purchase orders, so it's perfectly capable of getting a small line off the ground. Shopify Shopify App Store
• Cin7 Core — production runs, bills of materials, raw materials, finished goods, purchasing, batch tracking and production planning. It specifically supports apparel size grids, per-size barcodes and ecommerce variant syncing. Cin7 Cin7

That combination becomes particularly useful if, for example, you have:

Style: T-shirt 001
→ Black / S
→ Black / M
→ Black / L
→ Cream / S
→ Cream / M
→ Cream / L

…and each finished garment requires:

1 garment + 1 custom woven label + 1 hangtag + 1 polybag + 1 care label

Cin7 can model those materials through a bill of materials, track the components consumed during production, and keep raw-material, work-in-progress and finished-goods inventory connected. Cin7 Cin7

When I'd not add Cin7 yet

If you're launching with, say, 5–20 styles and a handful of production runs, and your manufacturer is handling most of the manufacturing logistics, I'd start with Shopify alone. Keep your production BOMs and run quantities in a simple spreadsheet initially.

Then add Cin7 when you start having problems such as:

• "How many labels do I actually have left?"
• "Which production run did these units come from?"
• "How much fabric/trim do I need to reorder?"
• "What's currently in production versus finished?"
• "Why does Shopify say I have 80 units when only 35 are actually available?"
• Multiple manufacturers or warehouses
• Wholesale + DTC inventory needing to stay synchronized

Cin7 is explicitly designed around raw materials → production → finished goods and supports production scheduling, component tracking and batch/lot traceability. Cin7 Cin7

What I'd choose at different stages

One important point: don't design your SKU system around the custom tag. The garment/style/size/color should generally determine the sellable SKU; your custom label, hangtag, care label, packaging, etc. should be components/materials in your production system. That keeps your ecommerce catalog clean while still letting you know exactly what goes into each production run.

If you tell me roughly how many styles, colors/sizes, units per production run, and whether you're manufacturing yourself or using a factory, I can tell you whether Cin7 is worth paying for at launch or whether Shopify alone will be enough.

• "How many labels do I actually have left?"
• "Which production run did these units come from?"
• "How much fabric/trim do I need to reorder?"
• "What's currently in production versus finished?"
• "Why does Shopify say I have 80 units when only 35 are actually available?"
• Multiple manufacturers or warehouses
• Wholesale + DTC inventory needing to stay synchronized

Cin7 is explicitly designed around raw materials → production → finished goods and supports production scheduling, component tracking and batch/lot traceability.

What I'd choose at different stages

For a creator selling a shirt + poster + digital track as one bundle, I’d rank them:

1. shopify.com — best overall

• Native Shopify Bundles lets you create a bundle from separate products while keeping inventory tied to the underlying items. Shopify Help Center Shopify Help Center
• Shipping is calculated from the individual products' shipping profiles, so the shirt + poster can be treated as one physical shipment while the digital track doesn't need shipping. Shopify Help Center
• The big advantage is flexibility: you can have the shirt and poster sold individually and offer a discounted "Complete Bundle."
• If you eventually want mix-and-match bundles, there are third-party Shopify bundle apps with more advanced functionality. Shopify Help Center Shopify
• bigcartel.com — best for a simpler creator shop

• It now supports both physical and digital products, so your digital track can be delivered automatically. Big Cartel Big Cartel
• Its shipping profiles are particularly good for your use case: rates can combine across products, with a "first item" price plus lower "additional item" prices. Big Cartel
• The downside is that its actual bundle-product functionality is less sophisticated than Shopify's. You'd generally be configuring the products/shipping behavior rather than getting Shopify's full bundle ecosystem.
• woocommerce.com — most powerful, but more work

• WooCommerce Product Bundles can combine existing products, including variable products, and has substantial control over pricing and shipping. WooCommerce
• Excellent if you already run WordPress, but I'd consider it overkill for a creator primarily selling merch.

For your exact bundle

I'd do this on Shopify:

"Artist Bundle — $XX"

• 👕 Shirt — physical
• 🖼️ Poster — physical
• 🎵 Digital track — instant download
• One checkout
• One physical shipping charge
• Digital track delivered automatically
• Shirt inventory and poster inventory tracked independently

That gives you a much cleaner setup than creating a single "bundle SKU" and manually figuring out inventory.

My pick: Shopify if the bundle is central to the business; Big Cartel if you're a smaller creator who wants the simplest/cheapest storefront.

If you tell me roughly how many products you sell, whether the shirt/poster are self-fulfilled or print-on-demand, and your typical bundle price, I can tell you which one I'd choose specifically—and how I'd structure the bundle/shipping setup.

If you mean a digital creator—courses, ebooks, templates, memberships, software, downloads—the easiest route is a Merchant of Record (MoR). The platform becomes the seller on the transaction and handles VAT/sales tax collection, remittance, and much of the compliance for you.

My shortlist

Gumroad is probably the lowest-effort choice for a traditional creator. It says it acts as Merchant of Record for all sales and automatically handles worldwide sales-tax collection/remittance. For digital products, it handles EU/UK VAT as well. gumroad.comwww.lemonsqueezy.comdeveloper.paddle.com

Lemon Squeezy is my pick if you want a more polished commerce backend while still avoiding tax administration. It handles VAT/sales tax as MoR and supports up to 95 currencies. www.lemonsqueezy.com

Paddle is particularly strong if what you're selling is software, subscriptions, or SaaS. It handles tax registration, calculation, collection, filing and remittance, and supports sales in 200+ markets. developer.paddle.com

What about customs?

There's an important distinction:

• Digital products: no physical customs/import process. An MoR can handle the relevant VAT/GST/sales-tax side.
• Physical products: VAT and customs/import duties are a different problem. An MoR doesn't magically eliminate border customs. For example, Gumroad explicitly says that physical goods shipped from outside the EU can have import VAT assessed by customs when they arrive. gumroad.com

So if you're selling physical creator merchandise, I'd choose a fulfillment/e-commerce stack differently than if you're selling digital products.

Bottom line: for a solo creator who wants “I upload my product, set a price, and don't want to become a part-time international tax accountant,” I'd start with Gumroad for maximum simplicity or Lemon Squeezy for a more flexible/professional setup.

For a small team selling custom merch both at live events and online, I’d put Shopify at the top of the shortlist, with Square as the main alternative.

The key is to choose a system where the online store, event POS, inventory, customer data, and orders all share one catalog. That avoids the nightmare of selling 20 shirts at an event and then discovering your website still thinks you have those 20 shirts in stock.

My shortlist

1. Shopify — my first choice

Shopify is particularly compelling for merch because ecommerce is its core strength, while Shopify POS is designed to work at pop-ups, markets, trade shows and other mobile selling situations. Inventory, customer profiles and orders can stay synchronized between online and physical sales. www.shopify.com

For your model, I'd specifically like:

• One product catalog for the website and events
• Real-time inventory across event locations and online
• Mobile POS for events
• Customer capture at checkout
• Online ordering after someone sees your merch at an event
• Buy-online/pickup and shipping capabilities
• Good integrations for email marketing, fulfillment, accounting, etc.
• Room to grow if the merch operation gets substantially bigger

Shopify also supports centralized inventory across warehouses, retail locations and temporary pop-ups. www.shopify.com

Shopify POS

2. Square — worth serious consideration

Square is probably the one I'd demo alongside Shopify. Square is very good if your priority is getting a small team selling at events quickly without a lot of operational complexity.

Square for Retail can synchronize inventory across physical and online channels, and Square Online provides the ecommerce side. squareup.com

I'd lean Square if:

• Most of your revenue currently happens at events
• Your online store is relatively straightforward
• You want very simple POS hardware
• You don't need Shopify's enormous ecommerce/app ecosystem
• Keeping software costs down is important

Square for Retail

Where I'd land

If you told me "We're a 2–10 person team, we make/sell custom shirts, hats, hoodies, etc., do concerts/festivals/pop-ups, and also have an online store", I'd start with:

🥇 Shopify + Shopify POS
🥈 Square for Retail + Square Online
🥉 Lightspeed

The deciding factor is where you expect the business to go. If ecommerce, social selling, email marketing, drops, preorders and a growing online customer base are important, I'd choose Shopify. If you're primarily an event seller that happens to have an online shop, I'd look harder at Square.

One important wrinkle for custom merch: I'd also evaluate how each handles variants (size/color), bundles, custom products, preorder inventory, event-specific stock allocations, barcode scanning, returns, and potentially print-on-demand/fulfillment integrations. Those details can matter more than the headline POS features.

If you tell me roughly (1) number of events/month, (2) online sales vs event sales, (3) number of SKUs/variants, (4) whether you manufacture yourselves or use a printer/fulfiller, and (5) your approximate monthly revenue, I can narrow this down to the best 2–3 setups and what I'd actually buy for the team.

If your firm runs marketplaces across several regions, I’d pick Phrase as the default enterprise platform.

The reason is that marketplace localization is broader than translating UI strings: you typically need product/catalog content, seller/buyer experiences, transactional flows, marketing, help content, terminology, and regional variants—all while keeping translations synchronized with frequent releases. Phrase is specifically positioned around unifying software, marketing, support, and multimedia localization, with shared translation memory, terminology, AI, orchestration, APIs/CI/CD, and enterprise governance. Phrase Phrase

My shortlist

Smartling is the strongest alternative I'd put through procurement. It has 50+ integrations, an open API, automated website localization, enterprise workflow management, and human/AI translation options. Smartling Smartling

For your particular model, I'd evaluate Phrase vs. Smartling first. Phrase gets my nod if the goal is to build a long-lived localization platform underneath multiple marketplaces, rather than primarily outsourcing translation operations. Recent comparisons likewise put Phrase ahead for cross-functional enterprise localization, while Smartling is particularly strong for enterprise marketing/content localization. Phrase Phrase

One important caveat: don't select based on raw machine-translation quality alone. For a marketplace, I'd make the proof-of-concept test terminology consistency, locale-specific formatting/currency, pluralization, SEO, catalog attributes, seller-generated content, translation-memory reuse, API/webhook behavior, fallback handling, and the ability to deploy translations continuously without blocking product releases.

If you tell me your regions/languages, tech stack (e.g. React/mobile/headless CMS), and whether sellers supply localized content, I can narrow this to a concrete Phrase vs Smartling vs Lokalise architecture and procurement recommendation.

For a large omnichannel retailer with complex promotion and pricing rules across multiple markets, my strongest recommendation would be SAP Omnichannel Promotion Pricing (OPP), particularly if you already have or are considering SAP Commerce/S/4HANA.

Why SAP OPP stands out

sap.com is purpose-built around the problem you're describing:

• One pricing/promotion engine across channels — web, POS, sales orders, mobile, etc., rather than duplicating promotion logic in each application. SAP Help Portal SAP Help Portal
• Complex promotion mechanics — mix-and-match, buy-X-get-Y, transaction-level thresholds, percentage/fixed discounts, bonus goods, coupons, and customer-context rules. SAP Help Portal
• Centralized price and promotion repository, giving merchandising teams a single source of truth and reducing discrepancies between stores and digital. SAP Help Portal
• Extensibility — SAP explicitly supports custom attributes and business-specific logic, which matters when different countries have different promotion structures. SAP Help Portal
• High-volume retail architecture — the calculation service is designed to handle large numbers of real-time pricing requests from POS and e-commerce. SAP Help Portal
• Multi-market support — SAP positions the platform for B2C/B2B and multiple sales/engagement channels, with support for multiple languages and integration with different source systems. SAP

How I'd evaluate the major options

The important distinction is that Shopify, Salesforce, and commerce platforms generally make the storefront the center of gravity, whereas SAP OPP is much closer to a central enterprise pricing/promotion decision engine. For a retailer where the same basket can be purchased online, in a store, through assisted selling, or through another channel and must resolve to the same promotional outcome, that's a significant architectural advantage. SAP Help Portal SAP Help Portal

From a product-manager perspective

I'd choose SAP OPP if your requirements look like:

“A promotion can vary by country, banner, store cluster, customer segment, currency, product hierarchy, channel, date/time, loyalty status and basket composition—and we need the exact same calculation at POS and online checkout.”

I'd be more cautious if your primary requirement is highly dynamic/personalized pricing rather than traditional retail promotions. In that case, I'd evaluate a dedicated pricing/promotion decisioning architecture alongside OPP rather than assuming the commerce platform should own everything.

Also, because pricing rules increasingly intersect with local regulation, I'd make market-specific compliance and price-transparency rules a first-class requirement rather than simply treating markets as currency/localization variants. For example, U.S. regulators are currently scrutinizing personalized pricing practices. AP News Federal Trade Commission

Bottom line: For a large omnichannel retailer, SAP Omnichannel Promotion Pricing is one of the strongest enterprise choices for complex, centrally governed promotions across markets and channels. If you tell me your existing stack (e.g. SAP vs Salesforce vs Oracle vs custom) and the types of promotions you need, I can give you a shortlist of 3–5 platforms with an architecture-level comparison.

For a digital-first enterprise where frontend/backend decoupling is a strategic requirement, my default recommendation would be commercetools.

It is purpose-built around API-first, headless architecture rather than treating headless as an add-on. commercetools says its platform supports millions of SKUs, peak traffic, multiple brands/stores, and global expansion; it currently reports 550+ enterprise customers. commercetools.com

My enterprise shortlist

Why I'd put commercetools first

1. The architecture matches your objective.
Its commerce capabilities are exposed through independent, versioned APIs, so your frontend can evolve independently of the commerce backend. That's a much cleaner fit for a multi-frontend strategy than bolting a headless layer onto a traditional monolith. commercetools.com

2. It is designed for composability, not just headlessness.
You can combine commerce with your preferred CMS, search, personalization, PIM, OMS, CDP, payments, etc. This matters if "decouple frontend/backend" is really the first step toward a broader composable architecture. commercetools.comcommercetools.com

3. It handles enterprise complexity well.
Multiple brands, markets, channels, B2B/B2C models and large catalogs are core considerations rather than edge cases. commercetools.com

4. You aren't tied to a particular frontend.
You can use Next.js, React, Vue, native apps, kiosks, marketplaces, or other channels against the same commerce APIs.

When I'd choose Salesforce instead

If you're already heavily invested in Salesforce, I'd seriously consider Commerce Cloud. Its headless APIs support B2C and B2B use cases, while its Composable Storefront provides a managed, scalable hosting layer for the frontend. Salesforce also reports 99.99% historical uptime and more than 10 billion API calls handled during Cyber Week. developer.salesforce.com

The trade-off is that you're buying into a much broader vendor ecosystem. commercetools is generally more attractive if commerce itself needs to be an independent platform capability.

The key distinction

I'd frame the decision this way:

• Want maximum architectural freedom + enterprise scale → commercetools
• Want enterprise commerce tightly integrated with CRM/customer data → Salesforce
• Want Adobe Experience Cloud/content/personalization ecosystem → Adobe Commerce
• Want the least infrastructure/commerce-ops burden → Shopify Plus
• Want source-code ownership and maximum customization → Saleor/Medusa

One important point: don't select purely on "headless." At enterprise scale, I'd evaluate API latency/throughput, catalog size, pricing/promotion complexity, multi-region architecture, B2B requirements, checkout extensibility, inventory model, eventing, deployment model, SLAs, observability, and total cost at peak traffic.

If you give me your annual GMV, SKU count, B2B vs. B2C mix, number of markets/brands, expected peak traffic, and preferred frontend (e.g. Next.js), I can narrow this to a 2–3 platform architecture recommendation rather than a generic vendor ranking.

For an enterprise with diverse product types and a strong need for flexible catalog modeling, I’d recommend commercetools.

Why commercetools fits

• Flexible product types: You define product types as reusable collections of attributes, rather than forcing everything into a fixed product schema. Product types can be broad or granular. docs.commercetools.com
• Strong variant model: Products act as parent structures while product variants represent the actual sellable SKUs, which works well for complex combinations of size, configuration, region, packaging, etc. docs.commercetools.com
• Handles heterogeneous catalogs: The platform explicitly supports complex assortments including variants, bundles, and digital and physical products. commercetools.com
• Good for multinational enterprises: You can localize product information and manage assortments, pricing, and availability across brands, regions, and channels from a centralized catalog. commercetools.com
• Composable architecture: Its APIs and extensibility model make it particularly attractive if your catalog needs to integrate with a PIM, ERP, OMS, custom storefronts, marketplaces, or multiple customer experiences. docs.commercetools.com

How I'd rank the main choices

Adobe Commerce is the strongest alternative I'd consider. It supports arbitrarily many attributes and attribute sets, plus configurable, bundled, grouped, virtual, and downloadable products. experienceleague.adobe.com The distinction is that Adobe's catalog model is more centered around predefined attribute sets and its built-in product types, whereas commercetools is more naturally suited to an enterprise that wants the catalog itself to be a highly customizable domain model.

Bottom line: If catalog flexibility is your primary architectural requirement, I'd start with commercetools. If you want flexibility but also prefer a more opinionated, all-in-one commerce platform, I'd evaluate Adobe Commerce.

commercetools product catalog
Adobe Commerce catalog documentation

For a retail chain with complex store pickup and omnichannel fulfillment, I’d put Salesforce Commerce Cloud + Salesforce Order Management + Omnichannel Inventory at the top of the shortlist.

Best fit: Salesforce

It is particularly strong when stores need to act as both retail locations and fulfillment nodes. Salesforce supports:

• BOPIS / buy online, pickup in store
• Ship-from-store / fulfill-from-store
• Buy online, return in store
• Mixed carts where different items can have different fulfillment methods
• Real-time, location-level inventory visibility
• Distributed order routing based on fulfillment rules
• Store-associate workflows for picking and preparing pickup orders www.salesforce.com

Salesforce's Order Management can use Omnichannel Inventory to identify availability and route reservations to fulfillment locations, while continuously updating inventory as orders are fulfilled. help.salesforce.com

Strong alternative: Adobe Commerce

Adobe Commerce is also very capable, particularly if you want more control over the commerce platform and inventory architecture. Its Inventory Management supports multiple warehouses, stores, pickup locations and drop shippers, with source-selection algorithms and reservations. Customers can select a pickup store during checkout, including location-based store selection. experienceleague.adobe.com

The distinction I'd make is:

Bottom line: If your priority is “we have hundreds of stores, customers can buy online and pick up anywhere, stores can ship orders, inventory must be accurate, and fulfillment needs sophisticated routing,” I'd favor Salesforce. If your priority is a highly customizable commerce platform and you already have strong OMS/POS/ERP systems to integrate, Adobe Commerce deserves serious consideration.

Salesforce Commerce for Retail

Adobe Commerce Inventory Management documentation