Answers that do not mention BigCommerce

For a one-person print-on-demand shop, I’d optimize for low fixed costs + minimal maintenance, rather than choosing the most powerful ecommerce platform.

My recommendation

Start with Etsy + Printful if your priority is getting sales with the least upfront cost.

• Etsy gives you an existing marketplace and doesn't require you to build/market a standalone store from scratch.
• Printful has a $0/month entry plan, and you pay for fulfillment only when you get an order. It integrates directly with Etsy, including product publishing and order fulfillment. Printful Printful Help Center
• Your main costs become Etsy's listing/transaction/payment fees plus Printful's product and shipping costs, rather than another monthly ecommerce subscription.

The downside is that you're building on Etsy's marketplace, rather than owning the customer relationship and storefront as completely as you would with your own site.

If you want your own website

I'd choose Shopify + Printful once you have evidence that people want your products.

Shopify is more expensive, but it's considerably more capable as a long-term branded store. Printful integrates directly with it and automatically sends orders for fulfillment. Printful Help Center Printful

For a one-person operation, though, I wouldn't start there unless you already have an audience. You're paying a monthly platform fee before you've proven the business.

One interesting ultra-cheap option

Printful Quick Stores are worth looking at if you're in the U.S. and primarily want a simple storefront. Printful says Quick Stores let you sell directly through a shareable store without a separate ecommerce platform, and they're aimed specifically at people who want a simple starting point. Printful Help Center

That could make your initial software cost essentially $0/month, although you don't get the marketplace discovery of Etsy or the full capabilities of Shopify.

What I'd do personally

One caveat: Big Cartel looks attractive because of its free/cheap plans, but its Printful integration currently requires a paid Big Cartel plan, so it isn't necessarily the bargain it first appears to be. Big Cartel

Bottom line: If you're literally starting from zero with a handful of POD designs, I'd go Etsy + Printful Free. Don't spend $30–$50/month on ecommerce software until you've demonstrated that customers will actually buy.

If you tell me roughly what you're selling (T-shirts, mugs, posters, stickers, etc.) and whether you already have an audience, I can give you the cheapest setup and estimate the break-even sales/month for Etsy vs. Shopify.

If you’re launching a subscription box, I’d start with Shopify + a dedicated subscription app rather than trying to make a general ecommerce platform handle recurring orders by itself.

My shortlist

• shopify.com — Best if you want the simplest/lowest-complexity launch. It integrates directly with Shopify Payments and keeps subscriptions inside Shopify Admin. Shopify
• rechargepayments.com — My pick if subscriptions are the core of your business. It has strong recurring-order infrastructure, integrations, customer management, and fulfillment workflows. Shopify's current subscription-app guidance lists Recharge among its leading options. Shopify Shopify App Store
• appstle.com — Worth considering for a startup that wants subscription boxes, bundles, and recurring billing without jumping immediately to a more expensive subscription platform. Its Shopify listing specifically supports subscription boxes and bundles. Shopify App Store
• skio.com — Strong if subscriber experience and retention are especially important. Its current Shopify offering includes Build-a-Box, automated journeys, payment recovery, and a no-code customer portal. Shopify App Store

For your particular business

If you're shipping a physical box every month, I'd rank them:

The key thing I'd investigate before choosing is how the subscription app creates and passes recurring orders to your fulfillment provider/3PL. You don't want billing to work beautifully while your warehouse has to manually reconcile subscription orders.

If you tell me (1) what you're selling, (2) expected subscribers in year 1, (3) whether you're using a 3PL or shipping yourself, and (4) your approximate box price, I can narrow this down to the best 1–2 options and compare their likely costs.

If your priority is “I want to host it myself and customize absolutely everything”, I would avoid most traditional hosted-style solutions and focus on platforms with clean codebases and APIs. The best choice depends on how much you want to build yourself. Open Source Projects WPBundle

My recommendations:

1. Medusa — Best overall for a fully custom store

Best for: developers who want a Shopify-like backend but complete frontend freedom.

Stack:

• Backend: Node.js + TypeScript
• Frontend: usually Next.js/React (but can be anything)
• Database: PostgreSQL
• Deployment: Docker-friendly

Why I like it:

• Modern architecture
• Very customizable checkout, pricing, inventory, fulfillment logic
• No forced theme system
• Great if you want a unique shopping experience
• Easier for modern web developers than older PHP platforms

Downsides:

• You build more yourself
• Smaller plugin ecosystem than WooCommerce
• Requires development skills

Choose Medusa if your vision is something like:

“I want my store to work exactly how I imagine, not how a template expects.”

Open Source Projects WPBundle

2. WooCommerce — Best if you want the biggest ecosystem

Best for: getting a powerful store running quickly while still owning the code.

Advantages:

• Huge plugin ecosystem
• Tons of payment/shipping integrations
• Easy admin experience
• WordPress gives you blogging, SEO, landing pages, and content tools

Downsides:

• WordPress architecture can become messy with many plugins
• Deep customization often means working around existing conventions
• Less elegant for highly custom commerce logic

A good setup is:

• WooCommerce backend
• Custom React/Next.js frontend (“headless WooCommerce”)

That gives you WordPress’s ecosystem with a custom storefront. WPBundle

3. Saleor — Best for serious/enterprise builds

Best for: complex catalogs, multiple warehouses, international commerce.

Strengths:

• GraphQL-first
• Excellent API design
• Strong inventory and multi-channel features
• Built for large custom applications

Downsides:

• More complicated to operate
• Requires stronger engineering skills
• Probably overkill for a small store

WPBundle

4. Sylius — Best if you are a PHP/Symfony developer

Very flexible and clean, but more of a framework than a ready-made store.

Good for:

• Custom B2B commerce
• Complex workflows
• Developers who already use Symfony

OpenReplay Blog

5. PrestaShop — Best traditional self-hosted store

Good if you want:

• A complete store out of the box
• Product management
• Tax/shipping tools
• Less custom development

Less appealing if your goal is a completely unique experience.

Open Source Groups

My ranking for your stated goal

For a new project today, I would personally shortlist:

1. Medusa + Next.js + PostgreSQL → if you are building something unique
2. Headless WooCommerce + Next.js → if you need lots of existing integrations
3. Saleor + React → if you expect enterprise complexity

If you tell me your stack (Node/Python/PHP), expected product count, and whether you need subscriptions, marketplace features, or B2B pricing, I can narrow it down further.

For a new project today, I would personally shortlist:

1. Medusa + Next.js + PostgreSQL → if you are building something unique
2. Headless WooCommerce + Next.js → if you need lots of existing integrations
3. Saleor + React → if you expect enterprise complexity

If you tell me your stack (Node/Python/PHP), expected product count, and whether you need subscriptions, marketplace features, or B2B pricing, I can narrow it down further.

If your priority is developer-friendly mobile commerce integration, I’d put Shopify first for most teams.

My ranking

Why I'd choose Shopify

Shopify has unusually direct support for the exact architecture you're describing: native iOS/Android/React Native UI + Storefront API + embedded checkout. Its current mobile documentation specifically supports product browsing, search, cart management, and checkout in native apps. Shopify Shopify

The typical flow is:

Mobile app → Storefront API → cart → checkoutUrl → Checkout Kit → Shopify payment/order

Checkout Kit handles the checkout experience inside the app, while the Storefront API handles products, search, and carts. Shopify also provides official mobile libraries/examples and recommends Apollo for typed GraphQL queries and caching. Shopify Shopify

That's a big advantage over platforms where you have to assemble the commerce backend, checkout, payments, and mobile integration yourself.

One caveat: Shopify's Storefront API is GraphQL-only, so your team needs to be comfortable with GraphQL. Shopify

When I'd pick something else

• Medusa — choose this if your app is the product and you want maximum control over pricing, checkout, catalog logic, and backend architecture. It's a stronger choice when you're willing to own more infrastructure.
• Saleor — attractive if your team strongly prefers GraphQL and wants an API-first/headless backend.
• CommerceTools — I'd consider it for a large enterprise where composable commerce and complex integrations matter more than implementation simplicity.
• WooCommerce — sensible if the business already runs on WordPress/WooCommerce, but I wouldn't start a new mobile-first commerce product with it solely for its API.

Bottom line: for a new mobile storefront, I'd start with Shopify unless you have a strong reason to own the entire commerce backend. The combination of Storefront API + Checkout Kit is currently one of the cleanest mobile-commerce paths. Shopify Shopify

If you tell me whether you're using React Native, Flutter, Swift/Kotlin, or Expo, I can narrow this down further and compare the actual SDK/API experience between Shopify, Medusa, Saleor, and CommerceTools.

The typical flow is:

Mobile app → Storefront API → cart → checkoutUrl → Checkout Kit → Shopify payment/order

Checkout Kit handles the checkout experience inside the app, while the Storefront API handles products, search, and carts. Shopify also provides official mobile libraries/examples and recommends Apollo for typed GraphQL queries and caching.

That's a big advantage over platforms where you have to assemble the commerce backend, checkout, payments, and mobile integration yourself.

One caveat: Shopify's Storefront API is GraphQL-only, so your team needs to be comfortable with GraphQL.

When I'd pick something else

For a small handmade-goods shop where you’re not tech-savvy, I’d choose Shopify for your first serious store.

shopify.com is built specifically around selling: products, payments, inventory, shipping, orders, marketing, and even in-person sales can all live in one dashboard. You don't need to code, and Shopify currently offers a free trial; its Basic plan is $39/month month-to-month or $29/month when billed annually. Shopify Shopify

Why I'd pick it for you

• Easy enough for a non-technical owner: you start with a template, add your products, photos, prices, and descriptions, and customize the storefront.
• Good for handmade products: you can handle variants, inventory, shipping, discounts, gift cards, etc.
• Room to grow: you won't have to rebuild your store if your business goes from 20 products to 200.
• Works beyond your website: Shopify supports selling through social channels, marketplaces, and in person. Shopify
• Support is built in: the Basic plan includes 24/7 live-chat support. Shopify

The one alternative I'd seriously consider

Squarespace would be my second choice if the look and feel of your brand is more important than sophisticated ecommerce features. It's particularly attractive for a handmade business where beautiful photography and storytelling are central. Its current plans support selling physical products, and its drag-and-drop editor is designed for beginners. Squarespace Help Squarespace Help

My simple rule:

Shopify = "I want to build a real retail business."
Squarespace = "I want a beautiful website that also sells my products."

For a first serious store, I'd go with Shopify Basic and avoid paying for extra apps until you actually discover you need them.

shopify.com

If you tell me roughly how many products you sell and whether you currently sell on Etsy, Instagram, at markets, or somewhere else, I can tell you exactly how I'd set up your first store without getting overly technical.

For three retail stores with simple multi-location inventory, I’d shortlist these three:

My recommendation for your situation:

• If you have three stores, a modest SKU count, and want something easy for staff → Square for Retail is probably the best fit. It handles the basics: inventory by location, sales, online orders, and store reporting without much complexity. getstash.io
• If your website is the main growth channel and stores are extensions of ecommerce → Shopify + Shopify POS. technologyadvice.comtechnologyadvice.com
• If you have lots of SKUs, frequent transfers between stores, size/color variants, or need stronger purchasing workflows → Lightspeed Retail. technologyadvice.com

For a 3-location retailer, I’d usually avoid jumping to an ERP unless you have complex warehousing or wholesale needs.

A few questions would narrow it down:

1. Roughly how many products/SKUs do you carry (100, 1,000, 10,000+)?
2. Do all three stores sell the same products, or does each location have its own assortment?
3. Do you already have an ecommerce site (Shopify, WooCommerce, etc.)?

For a local brick-and-mortar shop, I’d narrow it to Shopify vs. Square Online. My default recommendation would be Shopify, but Square can be the better choice if the store already runs on Square POS.

My recommendation: Shopify

shopify.com is probably the best overall fit if you want the ecommerce operation to become an important sales channel.

It supports:

• In-store pickup and local delivery.
• Delivery zones based on radius or ZIP/postal codes.
• Different delivery prices by zone.
• Delivery instructions and customer notifications.
• A built-in local-delivery workflow, including route optimization through Shopify's Local Delivery app. Shopify
• A very large app ecosystem if you eventually need sophisticated delivery scheduling, driver tracking, route optimization, subscriptions, loyalty, etc. Shopify App Store

For example, if the shop sells $20–$200 products and wants customers to choose "Pick up at our store" or "Deliver within 10 miles" at checkout, Shopify handles that nicely.

When I'd choose Square instead

If the physical shop already uses Square for its cash register/POS, I'd seriously consider squareup.com instead.

Square has a particularly nice advantage for a local retailer: online and in-person sales can operate from the same ecosystem. Its online system supports in-store/curbside pickup and local delivery, including either your own employees doing deliveries or on-demand delivery through Square's delivery partners. Square Square

So I'd roughly rank them:

One important consideration

If local delivery is a major part of the business, I'd actually choose the platform partly based on the delivery workflow rather than just the ecommerce features.

For Shopify, there are apps such as Zapiet and EasyRoutes that add more sophisticated pickup/delivery scheduling and route management. Shopify App Store

For example, you might eventually want:

Customer enters address → system verifies they're in the delivery area → customer chooses Tuesday 4–6 PM → delivery fee is calculated → order appears on driver's route → customer gets tracking.

Shopify gives you a good foundation for that and lets you add the complexity as the business grows.

Bottom line:

• Starting from scratch: Shopify.
• Already using Square POS: Square Online.
• Delivery is a core part of the business: Shopify + a dedicated pickup/delivery app.
• Simple store, small catalog, minimal technical overhead: Square Online.

If you tell me what kind of shop it is, roughly how many products you have, whether you already use Square/another POS, and how far you deliver, I can recommend the specific setup—including the plan/apps I'd use and what it should cost.

Square has a particularly nice advantage for a local retailer: online and in-person sales can operate from the same ecosystem. Its online system supports in-store/curbside pickup and local delivery, including either your own employees doing deliveries or on-demand delivery through Square's delivery partners. api.squareup.com my.squareup.com

So I'd roughly rank them:

One important consideration

If local delivery is a major part of the business, I'd actually choose the platform partly based on the delivery workflow rather than just the ecommerce features.

For Shopify, there are apps such as Zapiet and EasyRoutes that add more sophisticated pickup/delivery scheduling and route management.

For example, you might eventually want:

Customer enters address → system verifies they're in the delivery area → customer chooses Tuesday 4–6 PM → delivery fee is calculated → order appears on driver's route → customer gets tracking.

Shopify gives you a good foundation for that and lets you add the complexity as the business grows.

Bottom line:

For a non-technical seller who wants to sell through social links and email, I’d generally rank the options like this:

1. Shopify — Best overall for social selling

shopify.com

Best if you want to grow beyond a few products.

Why it fits:

• Strong connections to business.instagram.com, facebook.com, TikTok, Pinterest, and other sales channels. Shopify Zapier
• Customers can go from a social post → product page → checkout quickly.
• Easy email capture with tools like Shopify Email or integrations with email platforms. HostAdvice
• Huge ecosystem if you later need reviews, subscriptions, bundles, SMS, or automation. Ecommerce-Platforms.com

Downside:

• It has more features, so the dashboard can feel busier than simpler website builders.

Good fit: Instagram/TikTok sellers, creators, product brands, handmade goods, dropshipping, growing businesses.

2. Wix — Easiest for beginners

wix.com

Best if you want a simple store and website together.

Why it fits:

• Very beginner-friendly drag-and-drop setup.
• Built-in marketing tools and social integrations.
• Good for sending people from Facebook, Instagram, or email newsletters to a clean storefront. HostAdvice

Downside:

• If your social selling becomes a major sales engine, Shopify usually gives you more specialized ecommerce tools. Ecommerce-Platforms.com

Good fit: Coaches, artists, local businesses, small catalogs, first-time sellers.

3. Squarespace — Best-looking storefront

squarespace.com

Best if your brand image matters most.

Why it fits:

• Beautiful templates.
• Good for email newsletters and content-driven selling.
• Simple product catalogs work well.

Downside:

• Social commerce integrations are generally less extensive than Shopify’s ecosystem. Zapier

Good fit: Photographers, designers, artists, premium small brands.

My recommendation for your situation

If your main plan is:

• “I’ll post on Instagram/Facebook/TikTok and send email offers” → choose Shopify.
• “I only have a few products and want the easiest setup” → choose Wix.
• “My brand is very visual and I sell occasionally” → choose Squarespace.

For a non-technical seller starting today, I’d lean toward Shopify + a simple email tool + social integrations because it gives you the easiest path from a social follower to a paying customer while leaving room to grow. Shopify Ecommerce-Platforms.com

A couple of details would change the recommendation:

1. Are you selling physical products, digital products, or services?
2. Which social channel matters most: Instagram, Facebook, TikTok, Pinterest, or email list?

For a small maker business selling both at markets/in person and through an online shop, I’d pick Square unless your online store is likely to become the main part of the business.

My recommendation: Square

squareup.com is probably the simplest starting point:

• $0/month for the basic POS, so you can start without another monthly software bill. Square Square
• Your in-person and online inventory stays synced, which is particularly useful when you make limited quantities of products. Square
• You can build a basic online store, accept payments, offer shipping/pickup, and sell in person from the same system. Square
• Hardware is relatively inexpensive: the basic Square Reader is currently $59, and Square Stand is $149. Square
• You can even take contactless payments directly on an iPhone/Android without buying hardware. Square

For a maker doing craft fairs, pop-ups, Instagram sales, and a modest web shop, that's a very attractive combination.

When I'd choose Shopify instead

shopify.com becomes my pick if you expect the online store to be the heart of the business.

Shopify's ecommerce tools are deeper, and its POS ties directly into the online Shopify store. But the entry-level Shopify plan is currently $39/month, with POS Pro costing another $89/month/location if you need its advanced retail features. Shopify

So I'd roughly think of it this way:

Bottom line: If you told me, "I make candles/jewelry/ceramics/art/etc., I do weekend markets, and I just need a nice little website where people can buy my stuff," I'd start with Square. You can always move to Shopify later if ecommerce becomes substantial.

If you tell me what you make, roughly how many products/SKUs you have, and whether most sales are currently at markets or online, I can narrow it down to the exact setup I'd use.

Yes. For your mix of ready-to-ship products + made-to-order/custom work + preorders, I’d shortlist these:

• Shopify — best overall. Its core store handles ordinary inventory well, while preorder apps can add preorders, deposits, “ships by” dates, and made-to-order products. For example, Preorderly supports both pre-orders and made-to-order products and can display shipping dates. Shopify App Store Shopify Help Center
• Big Cartel — best for a very small artisan operation. It's specifically aimed at artists and makers and is simpler than Shopify. The catch is that you'll generally communicate custom/preorder lead times through product descriptions and policies rather than having sophisticated production scheduling built in. There are plenty of artisan Big Cartel stores successfully using this model. Shopify migration goods More Than Plenty Creations
• WooCommerce — best if you want maximum control. You can combine WooCommerce with preorder, product-options, and delivery-date extensions, but it's more hands-on technically.

What I'd choose for you

If you're one person or a tiny team, I'd lean:

Big Cartel if your custom work is relatively simple — e.g. “choose color/size/personalization, then I make it in 7–14 days.”

Shopify if you expect the made-to-order side to become a substantial part of the business, or you want customers to see things like “Preorder — ships approximately October 15”, collect deposits, handle different lead times by product, and automate more of the workflow. Shopify's preorder system explicitly supports taking payment before an item is ready, with preorder apps handling the customer-facing information. Shopify Help Center Shopify App Store

One important distinction: “custom lead time” can mean two different things. If you simply need Product A = ships in 3–5 days and Product B = made to order, ships in 2–3 weeks, that's easy. If you need customer chooses a custom option → that option changes production time → system calculates the resulting ship date, I'd favor Shopify/WooCommerce over Big Cartel.

If you tell me what you're making, roughly how many products you expect, and whether customers need to enter custom specifications, I can narrow this down to the best 2–3 options and compare their actual costs/features.

For a small handmade-goods shop on a tight budget, I’d start with squareup.com.

My picks

• 🥇 Square Online — best overall for $0/month

• Free plan has no monthly fee or startup cost.
• You can build a real storefront, add products, take payments, manage inventory, and offer shipping/pickup.
• You pay payment-processing fees when you actually make a sale. Square
• Best if you expect to have more than a handful of products.
• 🥈 Big Cartel — best if you only have a few products

• Its free Gold plan allows up to 5 products, with online selling and card/PayPal payments. Big Cartel Big Cartel
• It's particularly geared toward artists, makers, and independent creators. Big Cartel
• Great if you're launching with, say, 3–5 signature handmade items.
• 🥉 Etsy — best for getting discovered by existing shoppers

• You don't need to build much of a website yourself, and Etsy already has a marketplace audience.
• But it isn't really the cheapest store: listings cost $0.20 each, and Etsy charges a 6.5% transaction fee, plus payment-processing fees. Etsy Help
• I'd consider Etsy an additional sales channel, rather than your primary store, once you're ready.

What I'd do in your situation

Start with Square Online if you have more than 5 products. You can launch for $0/month and avoid paying for hosting or a fancy website while you figure out what actually sells.

If you're starting with just a handful of handmade products, I'd choose Big Cartel for its maker-focused simplicity.

I would not pay for Shopify yet. A monthly subscription makes more sense once your sales justify the added features.

If you tell me roughly how many products you expect to sell and whether you'll also sell at craft fairs/in person, I can tell you which one I'd pick specifically for your shop.

For a two-person startup testing product-market fit, I’d optimize for speed, low fixed cost, and not having to rebuild later.

My pick: Shopify

Shopify is probably the best default.

• $5/month Starter if you mainly need simple product links/checkout and are selling through social, email, or an existing site.
• $29/month Basic (annual billing) when you want a proper standalone storefront.
• Hosting, checkout, payments, inventory, orders, shipping integrations, etc. are all in one place.
• The big advantage for a startup is that you can start extremely lean but don't have to migrate platforms if you find PMF. Shopify Shopify

shopify.com

If minimizing cost is the #1 priority

Ecwid's $5 Starter plan supports up to 10 products, while Square has a free plan but charges higher payment fees. Big Cartel's free tier is limited to five products. Shopify Zapier

ecwid.com
squareup.com
bigcartel.com

What I'd do in your shoes

Start with Shopify Starter if you're still validating the product itself. Don't spend a week designing a beautiful store. Put up:

1. One strong landing/product page
2. 1–3 products
3. Stripe/Shopify Payments checkout
4. Basic analytics
5. A custom domain
6. A simple email capture

Then, once you're getting consistent sales, move to Shopify Basic and invest in the storefront, email flows, reviews, upsells, etc.

The important PMF principle is: don't optimize the ecommerce stack before you've proven people want the product.

If you tell me what you're selling (physical vs. digital), roughly how many SKUs, and whether you're already using a website, I can tell you which option I'd choose and the cheapest setup I'd use.

Yes. payhip.com is probably the best fit for what you're describing.

Best low-overhead options

• Payhip — my top pick

• $0/month on the Free Forever plan
• 5% transaction fee per sale, plus normal PayPal/Stripe processing fees
• Unlimited products and unlimited revenue
• Built-in storefront, checkout, and automatic digital delivery
• Supports JPG, PNG, SVG, PDFs, etc.
• You can sell digital prints/downloads and also physical products if you later want to offer printed versions. Payhip Payhip
• You can also offer some downloads for free as lead magnets. Payhip Help Center
• Gumroad — easiest alternative

• $0/month
• But the transaction fee is substantially higher: 10% + $0.50 on direct/profile sales, plus applicable payment-processing fees; sales through Gumroad Discover are 30%. Gumroad Gumroad
• It does have a marketplace/discovery component, which can be useful if you don't already have an audience. Gumroad

What I'd do in your situation

I'd start with Payhip's free plan and avoid paying for a website, Shopify subscription, Etsy listing fees, or anything else until you're actually making sales.

A simple setup could be:

Create artwork → upload to Payhip → customer pays → Payhip automatically delivers the download → you pay fees only when you make a sale.

For example, if you sell a $10 printable, Payhip's 5% platform fee is $0.50, before the separate payment processor fee. That's pretty close to "no overhead" while you're testing whether your products sell.

payhip.com

One important distinction: if by "prints" you mean physical prints shipped to customers, that's different from digital printables. Payhip can accommodate physical products too, but you'll have printing, packaging, shipping, and potentially fulfillment costs. If you want almost zero overhead, I'd start with downloadable art/printables and only add physical prints once you know which designs sell.

If you tell me what kind of digital downloads/prints you want to sell (wall art, planners, templates, coloring pages, photography, AI art, etc.), I can suggest the lowest-cost stack for creating + selling + delivering them, including which tools can be completely free.

Yes. If your goal is $0/month + taking paid preorders + presenting the campaign like a small crowdfunding launch, I’d narrow it to Square Online, Big Cartel, and Gumroad.

My recommendation: Square Online

squareup.com is probably the best fit if you’re selling physical products.

• $0/month on the Free plan.
• Customers can pay online and you can manage orders/shipping.
• Square explicitly supports retail preorders.
• Online card processing is currently 3.3% + $0.30 on the Free plan.
• You can build an actual storefront rather than just a checkout page. Square Square
• The downside: it feels more like a conventional ecommerce store than a Kickstarter-style campaign.

If the campaign itself is the important part: Big Cartel

bigcartel.com is attractive for a small, curated launch. Its free tier is intended for very small catalogs, while the paid tiers add things like product scheduling and more advanced selling tools. Big Cartel

I'd choose this if you're launching something like:

“We're making 500 units. Preorder yours for $49. Production begins when the campaign closes.”

You can make the storefront feel much more like a product launch than a general-purpose shop.

Gumroad: easiest, but expensive

gumroad.com has no monthly fee, but takes 10% + $0.50 per direct transaction. Gumroad

It's incredibly easy to get something live, but I wouldn't choose it for a physical-product crowdfunding campaign unless simplicity is much more important than fees.

What I'd actually do

For a physical product with preorders, I'd rank them:

One important distinction: none of these is really a Kickstarter replacement. They let you sell preorders, but they generally don't give you the same campaign mechanics—funding goal, campaign progress bar, stretch goals, backer tiers, “all-or-nothing” funding, etc.

If you tell me what you're selling, roughly how many orders you expect, your target price, and whether you need the money upfront to fund production, I can recommend the best setup—and potentially a $0/month stack that feels much more like Kickstarter.

Yes. For an agency prospect demo, I’d pick Shopify development stores.

• shopify.dev — Best overall for a polished prospect demo. Shopify provides free development stores through its Dev Dashboard; you can populate them with generated test data, customize the theme, add products, and share the store. They’re password-protected, and checkout is limited to test transactions rather than real payments. Shopify Shopify
• woocommerce.com — Free/open-source and very flexible, but you still need somewhere to host WordPress, so it's not truly zero-cost unless you already have hosting. WooCommerce
• saleor.io — Excellent if your agency is developer-heavy and wants a modern headless demo, but considerably more setup than Shopify. It's open source and offers projects/sandboxes. Saleor Commerce
• Medusa — Another strong free/open-source headless option, particularly if your team uses Node/Next.js, but again you'll have hosting/deployment overhead. Open Source Lab OSSAlt

My recommendation

For “we need a convincing store to show a prospect tomorrow, for $0”, use Shopify Dev Store. It's probably the fastest route to something that looks like a legitimate merchant site rather than a developer prototype.

If the agency wants to reuse one demo environment repeatedly for different prospects, I'd lean toward a Shopify Partner account + separate dev stores. Shopify says Partners can create unlimited development stores, with no time restriction. Shopify

shopify.dev

For a simple, low-cost store on an existing WordPress site, I’d usually start with a plugin rather than moving to Shopify or another platform. The best choice depends mostly on what you’re selling.

Best low-cost options

1. WooCommerce — best general choice

woocommerce.com

Cost: Free plugin; you mainly pay payment processing fees (Stripe/PayPal, etc.). GigaPress

Good for:

• Physical products
• A small catalog
• Shipping and inventory
• Coupons and basic promotions

Pros:

• Huge ecosystem
• Works directly inside WordPress
• Easy to expand later

Cons:

• Can become complicated if you add many extensions
• Some useful features (subscriptions, advanced shipping, memberships) cost extra SureCart

For a small store selling a handful of products, WooCommerce is usually the safest long-term choice.

2. SureCart — best if you want simple setup

surecart.com

Cost: Has a free option; paid plans add features. WordPress.org

Good for:

• Digital products
• Services
• Simple physical products
• Memberships/subscriptions

Pros:

• Cleaner setup than WooCommerce
• Less plugin maintenance
• Modern checkout experience

Cons:

• Less customizable than WooCommerce for complex stores

This is attractive if you want “add a store and sell” without managing lots of WordPress store components. SureCart

3. Easy Digital Downloads — best for downloads

easydigitaldownloads.com

Good for:

• PDFs
• Ebooks
• Templates
• Software
• Digital files

I would not pick it for physical products because it is designed primarily around digital sales. Odd Jar

My recommendation by scenario

• Selling a few physical items: WooCommerce
• Selling 1–20 simple products and want minimal hassle: SureCart
• Selling only downloads: Easy Digital Downloads
• Selling only one item (like a service, booking deposit, or payment): a simple Stripe payment plugin may be enough

For most small business WordPress sites, I’d install WooCommerce first, use a free theme-compatible setup, connect Stripe or PayPal, and avoid paid extensions until there is a real need.

If you tell me:

1. what you’re selling (physical, digital, services, memberships),
2. roughly how many products, and
3. whether you need shipping, taxes, or subscriptions,

I can narrow it down to the cheapest setup.

If you’re starting a clothing brand on a tight budget, I’d pick Big Cartel first.

My ranking

1. bigcartel.com — best budget launch

• Starts at $0, with the paid Platinum plan at $15/month.
• Supports clothing products with size/color variants, multiple product photos, inventory tracking, and discount codes/promotions. Big Cartel Big Cartel
• Big Cartel says it charges 0% transaction fees on its platform. Big Cartel
• Particularly good if you're launching with a relatively small catalog rather than hundreds of SKUs.
• shopify.com — best if you expect to grow quickly

• Basic is currently $29/month when paid annually ($39 monthly).
• Unlimited products, strong inventory/variant handling, social selling, excellent checkout, and a huge app ecosystem. Shopify
• You can add apps for things like variant-specific photos, size charts, swatches, and more. Shopify App Store
• More expensive, but I'd choose it if you already know you'll be running ads, doing frequent drops, or building a sizable catalog.
• wix.com — best if visual website design matters most

• Its entry-level paid ecommerce option currently lists around $7/month, with discounts/coupons and gift cards; higher tiers increase product limits and marketing functionality. wix.com
• Wix supports pricing at the variant level and coupon codes that can target particular products/categories. Wix Support Wix Support
• Good for a fashion brand where the website itself needs to feel highly designed.

What I'd do with limited funds

Big Cartel + Canva/your phone for photos + Instagram/TikTok for promotion.

You don't need to spend heavily on professional photography initially. Get 3–6 strong photos per item: front, back, close-up/material, model shot, and a detail/fit shot. Big Cartel's paid plan supports multiple product images and variants, plus discounts and promotions. Big Cartel

If your budget is under $50/month, I'd start Big Cartel. If you can comfortably spend ~$30/month and want a platform you probably won't outgrow, I'd go Shopify.

For an indie game where you want to sell downloadable builds + license keys, I’d shortlist these:

• lemonsqueezy.com — best overall for software-style licensing. It’s free to start, with 5% + $0.50 per transaction and no monthly ecommerce fee. It can host digital downloads, automatically issue license keys, set activation limits/license durations, and provides a License API if your game needs to validate keys. LemonSqueezy LemonSqueezy Lemon Squeezy Docs
• itch.io — cheapest/easiest for indie games. There’s no upfront cost, you upload and host your game directly, and you can choose itch.io's revenue-share percentage—even 0%. It also supports downloadable games and generating download keys. itch.io itch.io itch.io
• Lemon Squeezy + itch.io together is actually a strong setup: use itch.io as your community/discovery storefront, while Lemon Squeezy handles direct sales, licensing, and your own branded checkout.

My pick

If your game is a normal downloadable PC/Mac/Linux title and you specifically mean actual software license keys, I'd choose Lemon Squeezy. The automatic key generation, activation limits, downloadable-file hosting, API, and $0/month pricing make it unusually good for a small developer. LemonSqueezy Lemon Squeezy Docs

If you mainly want “put my indie game up and start selling it with almost zero overhead,” choose itch.io.

One caveat: if by “game keys” you mean Steam keys, rather than license keys for your own launcher/game, that's a different requirement and I'd recommend a different setup.

If your main business is building custom stores for clients, I’d put Medusa at the top of the list right now—especially if you’re comfortable with TypeScript/Node.

My ranking for a freelance developer

1. Medusa — best overall for custom integrations
2. Vendure — excellent if you prefer NestJS/GraphQL
3. Sylius — excellent if you’re a PHP/Symfony developer
4. Saleor — powerful, particularly for Python/GraphQL and larger B2B builds
5. WooCommerce — easiest to get a conventional store running, but less pleasant for deeply custom commerce logic

Why I’d choose Medusa

Medusa is deliberately structured around modules, workflows, API routes, events, and plugins, rather than expecting you to hack the core. Its current architecture lets you create custom modules, connect their data to built-in commerce models, hook custom behavior into existing workflows, and package reusable integrations as plugins. Medusa Docs Medusa Docs Medusa Docs

That maps extremely well to freelance work. For example, you could build a reusable:

• ERP integration
• custom pricing engine
• B2B customer/account system
• shipping provider integration
• marketplace functionality
• subscription system
• PIM connector
• client-specific fulfillment workflow

…and turn the common pieces into your own reusable modules/plugins.

Medusa even explicitly supports linking your custom data models to core models such as Products and Customers without modifying those core models directly. Medusa Docs Medusa Docs Medusa Docs

Where the others fit

Vendure is probably my second choice. It's also TypeScript/NestJS-based and has a strong plugin architecture. I'd choose it over Medusa if you're already heavily invested in NestJS and want a more conventional enterprise backend architecture.

Sylius is arguably the best choice if you're a Symfony/PHP developer. Its plugin system is mature and specifically designed for extending commerce without modifying core code. Sylius Academy

Saleor is attractive when the client needs sophisticated multi-channel/B2B commerce and your team likes Python/Django + GraphQL. It's less compelling for a solo JS/TS freelancer simply because the ecosystem and architecture are optimized somewhat differently.

WooCommerce wins if the client wants a traditional WordPress site with a huge plugin ecosystem. But for the sort of "client has an unusual business process and I need to make the commerce engine behave differently" work you're describing, I'd rather start with Medusa/Vendure/Sylius.

The important distinction

I'd separate "easiest to extend" from "easiest to build a store with."

For your business, the former matters much more.

So if you're starting a new freelance commerce stack today, my default would be:

Next.js storefront + Medusa backend + PostgreSQL + your own reusable Medusa modules/plugins.

That gives you a pretty compelling agency/freelancer model: instead of rebuilding integrations for every client, you gradually accumulate your own commerce framework on top of Medusa. Medusa's documentation explicitly supports packaging reusable customizations as plugins that can be installed across projects. Medusa Docs

If you tell me your preferred language (PHP/TS/Python), typical client size, and the kinds of integrations you build, I can narrow this down to Medusa vs Vendure vs Sylius and explain which one will make you the most money/least maintenance as a freelancer.

If your priorities are solo-founder friendliness + modern admin + easy storefront theming, I’d narrow it to Medusa and WooCommerce, with Medusa as my pick if you’re comfortable doing some initial setup.

My ranking

🥇 Medusa — best modern choice

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

Its current Admin is a polished dashboard for products, orders, customers, etc., and it even has light/dark themes. Medusa Docs Medusa Docs

The big advantage is the storefront: Medusa deliberately separates the storefront from the commerce backend, and its official Next.js starter gives you a modern store that you can customize rather than forcing you into a rigid theme system. Medusa Docs

Why I'd choose it:

• Modern React/Next.js stack
• Excellent-looking starting point
• Very flexible theming
• Good admin
• Open source
• You aren't locked into a proprietary storefront
• Lots of room to grow

The catch: you're still dealing with Node.js, Next.js, deployment, environment variables, etc. For a genuinely nontechnical founder, that initial setup can be painful.

🥈 WooCommerce — easiest for a nontechnical solo founder

woocommerce.com is the one I'd pick if "I don't want to become a developer" is your overriding constraint.

WordPress gives you an enormous ecosystem of themes and plugins, so getting from zero to a customized store is substantially easier than building a headless Medusa storefront. WooCommerce also has by far the broader ecosystem among these options. Open Source Groups WPBundle

The downside is that it doesn't feel as architecturally clean or modern as Medusa. You'll eventually encounter plugin conflicts, WordPress maintenance, theme quirks, and a sprawling settings interface.

In other words:

WooCommerce = easiest to launch.
Medusa = nicest foundation to build on.

🥉 Vendure — very interesting alternative

vendure.io has become particularly interesting in 2026 because its new React Admin Dashboard replaces its older Angular admin. The new dashboard uses Tailwind/shadcn-style theming, while the platform provides strong customization of both the dashboard and storefront. Vendure Vendure

I actually like Vendure's admin approach a lot. But for a solo founder with limited development skills, I'd still put Medusa ahead because its Next.js storefront path is particularly approachable.

What I'd avoid for your situation

Saleor is excellent software, but I'd consider it overkill for a solo founder unless you specifically need its more sophisticated multi-channel/B2B capabilities. It's much more of a developer-oriented platform.

Magento/OpenMage: powerful, but absolutely not what I'd choose with limited dev skills.

Bagisto: worthwhile if you're already comfortable with Laravel/PHP, but I wouldn't learn Laravel just to get an ecommerce store running.

My actual recommendation

If I were in your shoes:

Choose Medusa + Next.js if you want a modern, highly customizable brand.

Start from the official Next.js starter, modify the colors/fonts/layout, and leave the commerce logic to Medusa. That's a much better solo-founder architecture than building an ecommerce backend yourself. Medusa explicitly provides the starter storefront for this workflow. Medusa Docs

Choose WooCommerce if your priority is getting the store live with the least technical involvement possible.

One important caveat: open source doesn't automatically mean low maintenance. With Medusa, you'll own hosting, updates, backups, deployment, and some technical troubleshooting. That's the main reason I'd steer a very nontechnical founder toward WooCommerce.

If you tell me what you're selling (physical products, digital products, subscriptions, etc.) and roughly how many SKUs, I can give you a much more specific pick.

For your specific scenario—low traffic, small catalog, and a non-technical owner—I'd pick WooCommerce as the easiest self-hosted option.

My ranking

1. WooCommerce — easiest overall

• Huge ecosystem and lots of hosting providers that can handle the technical side.
• Familiar WordPress admin interface.
• Excellent for a small boutique with relatively standard products.
• You can keep the installation simple and avoid most plugins.
• The downside is that you're maintaining WordPress + WooCommerce + themes/plugins + PHP, so updates and backups still matter. WooCommerce itself recommends backups and, ideally, staging before updates. WooCommerce WooCommerce
• PrestaShop — best dedicated ecommerce alternative

• More purpose-built than WooCommerce, so the store functionality is more centralized.
• But I'd rank it second for a non-technical owner because server requirements and updates are somewhat more involved. PrestaShop's current guidance calls for Apache, PHP 8.4 recommended, and at least 512 MB PHP memory for PrestaShop 9. PrestaShop Help Center
• Its own update guidance emphasizes checking modules/themes, maintaining documentation, and keeping tested backups. PrestaShop Help Center
• Shopware / Adobe Commerce — overkill

• Powerful, but I'd avoid them for a small boutique. You're taking on substantially more infrastructure and complexity than the business requires.

The important distinction

If "self-hosted" means you want to run the server yourself, WooCommerce is probably the easiest.

If it means "I want to own/control the store but don't want to do server administration," I'd actually recommend managed WordPress hosting + WooCommerce. That's still a self-hosted/open-source ecommerce setup in the sense that you control the WordPress/WooCommerce installation and data, while the hosting company handles much of the infrastructure.

For a non-technical owner, I'd optimize for:

managed WordPress hosting → WordPress → WooCommerce → lightweight theme → only essential plugins → automatic backups → minimal customization.

That's considerably easier to live with than running a VPS and administering Linux, PHP, MySQL, web-server configuration, backups, and security yourself. WooCommerce's current server requirements alone include PHP 8.3+, MySQL 8/MariaDB 10.6+, HTTPS, and adequate memory. WooCommerce

Bottom line: For a low-traffic boutique, WooCommerce on good managed WordPress hosting is my first choice. If you want a dedicated ecommerce application rather than WordPress, I'd choose PrestaShop.

If security and compliance for payments and customer data are the top priorities, I would generally shortlist enterprise-grade open-source platforms with strong security practices, mature ecosystems, and the ability to run in a controlled environment rather than choosing based only on features.

My ranking would be:

1. Adobe Commerce (Magento Open Source) — best for high-security enterprise deployments

Best fit: Large catalogs, regulated industries, B2B, complex workflows, dedicated security teams.

Strengths:

• Mature enterprise architecture with granular roles, permissions, and admin controls.
• Strong ecosystem for security tooling, monitoring, and hardened hosting.
• Supports self-hosting, allowing you to control infrastructure, encryption, logging, backups, and network controls.
• Good fit when you need formal compliance programs (PCI DSS, SOC 2 environments, audit trails).

Tradeoffs:

• Requires experienced developers and operations teams.
• Security depends heavily on patching, infrastructure hardening, extension quality, and deployment practices.

Choose Magento if you have a security team or a capable managed hosting partner.

2. Shopware — best modern open-source enterprise option

Best fit: Mid-market and enterprise companies wanting modern architecture with strong privacy/security posture.

Strengths:

• API-first architecture and flexible deployment models.
• Good separation of commerce logic from storefronts.
• Supports self-hosted deployments where you control infrastructure.
• Vendor emphasizes security, privacy, encryption, ISO 27001, SOC 2-related controls, and GDPR support. Shopware

Tradeoffs:

• Smaller ecosystem than Magento.
• You may need specialized Shopware expertise for complex implementations.

For many organizations, Shopware is a strong balance between enterprise capability and operational simplicity. Shopware

3. WooCommerce — good for smaller organizations with disciplined security

Best fit: Small-to-medium businesses already invested in WordPress.

Strengths:

• Huge ecosystem.
• Flexible payment integrations.
• Can reduce PCI scope by using hosted payment providers rather than handling raw card data. WooCommerce

Risks:

• Security depends heavily on WordPress hosting, plugins, themes, update discipline, and configuration.
• A large plugin ecosystem increases supply-chain risk.
• Requires strong governance to maintain compliance.

WooCommerce can be secure, but it usually requires more ongoing operational discipline than Magento or Shopware. WooCommerce

Platforms I would be cautious about for your requirement

• PrestaShop — capable, but enterprise security governance and complex compliance programs may require more customization.
• Headless platforms (Saleor, Medusa, Vendure, etc.) — excellent developer platforms, but you own more of the security architecture.

My recommendation by scenario

Regardless of platform, the biggest compliance wins usually come from:

• Avoiding storage of cardholder data (use tokenized/hosted payment flows).
• Enforcing MFA and least-privilege access.
• Centralized logging and monitoring.
• Automated vulnerability scanning.
• Secure SDLC and dependency management.
• Regular penetration testing.
• Strong vendor/plugin review processes.

If you are handling large payment volumes, healthcare/financial data, government contracts, or customer identity data, I would lean toward Magento Open Source or Shopware with a hardened cloud deployment rather than WooCommerce.

For a one-person creative business selling ebooks and printable art, I’d start with a tool that handles digital delivery, checkout, taxes, and simple storefront pages without a monthly bill.

My top picks:

1. Payhip — best overall fit for low fees

payhip.com

Why it fits your business:

• Free to start
• Lower transaction fee on the free plan than many creator platforms (5% platform fee, plus payment processing)
• Built for ebooks, PDFs, printables, templates, courses, and memberships
• Automatically delivers files after purchase
• Lets you create a simple branded storefront
• Includes features like discount codes and affiliate tools Shopify Payhip

Best if: you already have (or can build) an audience through Instagram, Pinterest, email, a blog, or your website.

2. Gumroad — easiest launch

gumroad.com

Why people like it:

• Very fast setup
• No monthly fee
• Clean checkout experience
• Good for a first ebook or printable collection Shopify

Downside: the transaction fee is higher than Payhip’s free plan, so it can cost more as sales grow. LaunchAdvisor

Best if: you want to put up a product today and don’t want to think about store design.

3. Etsy — best for built-in discovery

etsy.com

Why it can work for printable art:

• Shoppers already search there for wall art, planners, templates, and printables
• You may get traffic without having a large audience Shopify

Tradeoff: more competition and less control over your customer relationship.

I’d probably choose this setup for you:

• Primary storefront: Payhip
• Traffic sources: Pinterest + Instagram + an email list
• Optional extra marketplace: Etsy for your best-selling printable art
• Skip Shopify for now unless you plan to add physical products, a large catalog, or a more complex branded store. LaunchAdvisor

A simple rule:

• Selling under ~$500/month: Payhip or Gumroad
• Growing catalog + want search traffic: add Etsy
• Selling lots of products + physical goods later: consider Shopify

For your specific mix (ebooks + printable art), Payhip is probably the sweet spot.

For a small indie studio selling large downloadable builds + license/activation keys, I’d generally avoid generic “file-sharing” products. The better architecture is private object storage + your own order/entitlement layer + short-lived signed download URLs.

My top pick: Cloudflare R2

cloudflare.com is probably the best fit if you're comfortable doing a little integration work.

• Private storage: keep every game build in a non-public bucket.
• Secure delivery: after a successful purchase, your server generates a temporary presigned URL for the customer's specific build. R2 supports expiring URLs from 1 second to 7 days. Cloudflare Docs Cloudflare Docs
• Large files: customers download directly from R2 rather than through your web server, which is important when builds are tens of GB.
• Simple infrastructure: R2 is S3-compatible, so you can use standard S3 SDKs/tools. Cloudflare Docs
• Good security model: the customer never gets your storage credentials. Treat the signed URL itself as a temporary bearer token. Cloudflare Docs

The basic flow I'd use is:

Purchase → create entitlement → generate license key → customer logs in/enters key → server verifies entitlement → generate short-lived signed URL → direct download

That gives you much more control than emailing a permanent download link.

Runner-up: Amazon S3

aws.amazon.com is the more established alternative and is excellent technically. S3 supports private objects and presigned URLs, including downloads of very large objects; AWS documents presigned URLs as a way to give time-limited access without changing bucket permissions. AWS Documentation AWS Documentation

I'd choose S3 if:

• you're already using AWS;
• you expect substantial scale;
• you want the enormous AWS ecosystem around it;
• your developer is comfortable with AWS.

For a small studio starting from scratch, though, R2 is usually the simpler recommendation I'd investigate first.

What I would not do

I wouldn't make your build files permanently public and rely on obscure URLs. Once a URL gets posted, anyone can potentially download the game.

I also wouldn't put your storage credentials into your website/game launcher. Keep them server-side and issue narrowly scoped, expiring download URLs instead. Both R2 and S3 explicitly describe presigned URLs as bearer credentials, so their lifetime and exposure matter. Cloudflare Docs AWS Documentation

One important distinction

File delivery and key management are separate problems.

For example:

• R2/S3 → stores and delivers your 20–100 GB game builds.
• Your database → records who bought which game/version.
• Payment processor → handles the transaction.
• Your key/entitlement system → determines whether someone is entitled to download/activate.
• Your website/launcher → authenticates the customer and requests the temporary download URL.

If you tell me what you're using for your storefront/payment (Stripe, Shopify, WooCommerce, custom site, itch.io, etc.), your typical build size, and whether you have a launcher, I can recommend a specific stack and architecture rather than just the storage layer.

I also wouldn't put your storage credentials into your website/game launcher. Keep them server-side and issue narrowly scoped, expiring download URLs instead. Both R2 and S3 explicitly describe presigned URLs as bearer credentials, so their lifetime and exposure matter.

One important distinction

File delivery and key management are separate problems.

For example:

Yes. For an agency model where you build/manage multiple independent client stores, the key distinction is between a normal ecommerce platform with multi-store features and a genuinely multi-tenant/white-label platform.

Best fits

My first choice for your use case would be Spree Commerce. It is explicitly designed for multi-tenant/white-label commerce: each client can have an independent storefront, admin panel and API, while your agency retains a super-admin/operator layer. Spree Commerce

If you want something less development-heavy and more agency SaaS-like, UShopTec is worth investigating. It specifically targets agencies/software providers running many brands from one deployment, with separate catalogs, branding and pricing per tenant. UShopTec

Cartvero is another interesting agency-oriented option: it advertises automated client-store provisioning, reusable theme presets, white-labeled client admin, and roles where your team manages everything while clients see only their own shop. Cartvero

What I would not choose

Sellfy is great if each client simply needs an easy digital-download store, but it doesn't fit your agency architecture particularly well. Its current documentation says one storefront per account and that multiple users can't be added to an account. Sellfy Sellfy

Shopify Plus can handle multiple stores and centralized organization management, but its expansion-store model is primarily designed around stores belonging to the same organization/brand. Shopify says the stores are independently configured and data isn't shared by default. Shopify Help Center For an agency wanting dozens of unrelated client businesses, it's not as clean as a true tenant model.

The architecture I'd look for

For your agency, ideally you want:

Agency account
→ Client A
→ Storefront + products + orders + customers + client users
→ Client B
→ Storefront + products + orders + customers + client users
→ Client C
→ Storefront + products + orders + customers + client users

while your agency has a master dashboard that can:

• provision a new store
• clone your standard store/theme
• manage domains
• access any client's admin
• control client permissions
• manage billing/subscriptions
• white-label the admin experience
• keep each client's data isolated
• optionally share your own digital-product infrastructure/templates across stores

If you're expecting 10–100+ client stores, I'd strongly favor a true multi-tenant platform such as Spree/UShopTec/Cartvero over trying to bend Shopify or Sellfy into an agency platform.

If you tell me roughly how many stores you expect (10, 50, 500+) and whether clients need to log into their own admin, I can narrow this to the 2–3 strongest choices and compare pricing, APIs, white-label depth, digital downloads, Stripe, subscriptions, and client permissions.

Cartvero is another interesting agency-oriented option: it advertises automated client-store provisioning, reusable theme presets, white-labeled client admin, and roles where your team manages everything while clients see only their own shop. Cartvero

What I would not choose

Sellfy is great if each client simply needs an easy digital-download store, but it doesn't fit your agency architecture particularly well. Its current documentation says one storefront per account and that multiple users can't be added to an account. Sellfy Sellfy

Shopify Plus can handle multiple stores and centralized organization management, but its expansion-store model is primarily designed around stores belonging to the same organization/brand. Shopify says the stores are independently configured and data isn't shared by default. help.shopify.com For an agency wanting dozens of unrelated client businesses, it's not as clean as a true tenant model.

The architecture I'd look for

For your agency, ideally you want:

Agency account
→ Client A
→ Storefront + products + orders + customers + client users
→ Client B
→ Storefront + products + orders + customers + client users
→ Client C
→ Storefront + products + orders + customers + client users

For a small shop that mostly sells physical goods but occasionally sells digital products, I’d narrow it to Shopify vs. Squarespace.

My pick: Shopify

shopify.com is probably the smoothest overall choice if shipping and inventory are important. It lets you sell physical and digital products in the same store, and its digital-products tooling can automatically deliver downloads while physical products continue through normal shipping/fulfillment. You can even combine both—for example, a physical product that includes a digital download. Shopify

Best if you:

• Sell physical products regularly
• Want solid shipping/inventory tools
• Expect the shop to grow
• Might eventually sell in person as well as online
• Want flexibility to add apps later

Best for simplicity/design: Squarespace

squarespace.com is especially appealing if your shop is small and brand/website presentation matters as much as ecommerce. It natively supports physical products and downloadable products, and physical orders can use flat-rate, weight-based, or carrier-calculated shipping. Squarespace Help Squarespace Help

Its digital downloads are automatically fulfilled, while physical orders can be fulfilled and tracked from the same system. Squarespace Help Squarespace Help

Quick comparison

Bottom line: If you mean “I want one system that handles both without me constantly fiddling with it,” I'd choose Shopify. If you mean “I have a small branded website and physical products are secondary, with some PDFs/downloads on the side,” I'd choose Squarespace.

If you tell me roughly what you're selling digitally and physically (e.g. printables + handmade goods, courses + merchandise, art + prints), I can tell you which one I'd pick for your specific shop.

Yes. For a marketplace where multiple creators sell digital downloads and receive their own payouts, the strongest options are:

1. Sharetribe + Stripe Connect — probably the best fit

Sharetribe is specifically designed for multi-vendor marketplaces, and its Stripe integration handles seller onboarding, KYC, payments, commissions, and payouts. Sharetribe explicitly supports digital downloads, with payouts triggered after the digital purchase process. Sharetribe Sharetribe

For example:

Creator sells a $20 template → customer pays $20 → your marketplace takes 20% ($4) → creator receives $16.

You can also configure delayed payouts, which can be useful for refunds/disputes. Sharetribe

sharetribe.com

2. Stripe Connect — best if you're building your own platform

Stripe Connect is the underlying payment infrastructure I'd consider if you're developing the marketplace yourself.

It supports:

• Multiple sellers/creators
• Seller onboarding and identity verification
• Splitting payments between your platform and creators
• Marketplace commissions
• Automatic or scheduled payouts
• Refunds and disputes
• International payouts
• Tax reporting such as 1099s in the US Stripe Stripe Docs

Stripe's marketplace documentation explicitly describes marketplaces selling physical or digital items and paying sellers from each transaction. Stripe Docs

stripe.com

3. Gumroad — not ideal for your use case

Gumroad is excellent if each creator has their own Gumroad storefront, but it isn't really designed for you to operate a unified marketplace where hundreds of creators list products and your platform controls commissions and seller payouts.

My recommendation

If you're trying to build something like "Etsy for digital products":

Sharetribe + Stripe Connect → best if you want to launch quickly without building the marketplace infrastructure yourself.

Custom marketplace + Stripe Connect → best if you need a highly customized experience, sophisticated creator dashboards, subscriptions, bundles, licensing, affiliate revenue, etc.

If you tell me your expected number of creators, average product price, and whether you're building no-code or custom, I can also compare the actual fees and payout flow for the best 3–5 options.

For software that is continuously updated, you usually want more than a normal ecommerce cart. The important pieces are:

• Entitlement management — who owns what, what plan they have, expiration/support window, seats/devices
• License activation/validation — your app checks whether the customer is allowed to run it
• Update authorization — only entitled customers can receive new builds
• Secure download endpoints — signed URLs, tokenized downloads, revocation, audit logs
• Upgrade/renewal flows — annual maintenance, subscriptions, paid upgrades

The best fit depends on your scale and whether you want a hosted platform or to own the stack.

Best dedicated software licensing + entitlement platforms

Revenera

Best for: enterprise software vendors

Strengths:

• Full entitlement management
• License enforcement
• Software delivery and updates
• Complex models (feature tiers, floating licenses, usage-based, device-based)
• Enterprise reporting and compliance

Revenera’s platform specifically combines entitlement management, licensing, and software delivery workflows. Revenera Revenera

Good choice if you sell:

• Developer tools
• Enterprise applications
• On-prem software
• High-value commercial software

Tradeoff:

• Expensive and heavier operationally than a startup needs.

Ecommerce-first options

WooCommerce + licensing extensions

Best for: small to mid-sized software companies that want control

A common stack:

• WooCommerce → checkout, payments, customer accounts
• License plugin → keys, activations, update API
• S3/CDN → binaries
• Your app → checks license server

Examples:

• Kestrel API Manager can issue license keys, handle activations, validate licenses, and provide secure expiring download links from your site, S3, or remote storage. WooCommerce
• Software licensing extensions for WooCommerce can add activation, expiration, and update delivery workflows. WooCommerce

Good choice if you want:

• Your own storefront
• Lower fees
• Custom customer experience

Tradeoff:

• You assemble more pieces yourself.

ChargePanda

Best for: independent software vendors wanting built-in entitlement logic

Features aimed at software sales:

• Versioned files
• Plan-based access
• Support/update windows
• Signed expiring download links
• Entitlement checks before downloads

ChargePandaGood fit for:

• Desktop apps
• Plugins
• Developer tools
• Paid updates model (“buy version 5, get updates for 12 months”)

Hosted software selling platforms

SellApp

Best for: quick launches

Supports:

• License delivery
• Recurring plans
• Upgrades
• Protected downloads

SellAppTradeoff:

• Less control than building around your own licensing API.

If you are building a SaaS instead of downloadable software

You may not need download licensing. A typical architecture is:

• Stripe → billing
• Your database → entitlements
• Your API gateway → authorization
• Your app → feature flags

The "license key" becomes an account entitlement record.

Practical recommendation by company stage

For many modern software businesses, the cleanest architecture is:

Checkout system → entitlement database → license/update API → signed download service → customer app updater

That keeps ecommerce separate from the software security layer and makes frequent releases much easier to manage.

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

My pick: Payhip

For ebooks, PDFs, templates, printables, guides, and other downloadable products, Payhip is probably the best overall starting point.

• Very easy setup: upload your file, add a title/description/price, and you get a storefront and checkout.
• No website required: you can simply share your product/store link.
• Built for digital downloads: automatic delivery after purchase.
• Free to start: the free plan takes 5% of each sale, plus payment-processing fees. Paid plans reduce the Payhip transaction fee. Biztoolkit Heresthebest
• It supports things beyond ebooks, so you can later sell workbooks, templates, planners, bundles, audio files, etc.
• It's particularly attractive if you're selling lower-priced products because Payhip's free plan doesn't add a fixed fee per transaction. EarnifyHub

payhip.com

The easiest alternative: Gumroad

If your priority is "I want the absolute least intimidating setup and don't care about paying somewhat higher fees," I'd choose Gumroad.

It's extremely beginner-friendly and has no monthly subscription. The tradeoff is that its direct-sale fee is currently 10% + $0.50 per transaction, making it considerably more expensive as sales grow. We Are Founders Heresthebest

gumroad.com

How I'd rank them for you

Lemon Squeezy is particularly good when international tax handling and software/subscriptions matter, but it has a somewhat steeper learning curve and isn't as focused on ordinary ebook sellers. What I Pocket EarnifyHub

What I'd do in your situation

Start with Payhip. Don't build a website yet.

You could literally start with:

PDF ebook → Payhip product page → customer pays → Payhip automatically delivers PDF → you promote the link on social media/email.

Once you're consistently making sales, then worry about branding, your own website, email marketing, bundles, upsells, etc.

If you tell me what kind of ebooks/digital downloads you want to sell and roughly what price ($5, $15, $30, etc.), I can tell you whether Payhip, Gumroad, or Etsy would give you the best setup and economics for your particular products.

For an enterprise selling large datasets, I’d separate the decision into two use cases: secure file/data delivery versus customer-facing dataset commerce.

Strongest options

My first choice would be Files.com if the core product is downloadable datasets. It specifically records logins, uploads/downloads, permission changes, shares and protocol activity, and can stream events to Splunk, Microsoft Sentinel, Datadog, etc. Files.com Files.com

FileCloud is particularly interesting if you want a more traditional enterprise customer portal. It offers granular folder/subfolder permissions, external accounts, audit trails containing user/time/IP/device information, and analytics around usage trends and geographic access. FileCloud FileCloud

If your datasets are multi-GB/TB and you're already AWS-native, I'd seriously consider building the delivery layer on S3 + a customer-facing authorization layer, rather than putting the data inside an ecommerce platform. AWS provides detailed file-access auditing and can route events into CloudWatch, Firehose, S3, OpenSearch, Splunk, or Datadog for analysis. AWS Documentation

One important distinction

If by "analytics" you mean commercial engagement analytics—e.g.:

• Customer A downloaded Dataset X
• Customer B viewed only the metadata
• Customer C downloaded 80% of the available files
• Which datasets are most valuable?
• Which accounts are inactive?
• Alert sales when a prospect downloads a particular dataset

—then I'd favor a custom portal/data marketplace architecture over a generic file-sharing product. You can combine the delivery system's immutable access logs with your CRM/product analytics.

If you tell me rough dataset size (GB/TB), whether customers download files or query data via API, and whether you need Stripe/ecommerce checkout, I can narrow this to 3–4 concrete architectures and compare pricing, SSO/SCIM, auditability, APIs, and customer-facing analytics.

If your datasets are multi-GB/TB and you're already AWS-native, I'd seriously consider building the delivery layer on S3 + a customer-facing authorization layer, rather than putting the data inside an ecommerce platform. AWS provides detailed file-access auditing and can route events into CloudWatch, Firehose, S3, OpenSearch, Splunk, or Datadog for analysis.

One important distinction

If by "analytics" you mean commercial engagement analytics—e.g.:

For a small clothing brand, I’d pick Shopify as the commerce backend + a headless frontend (Hydrogen/Next.js).

My recommendation: Shopify Headless

It gives you the best balance of flexibility, scale, and low maintenance:

• Low ops burden: Shopify handles products, inventory, orders, checkout, payments, security, and scaling.
• Actually headless: The Storefront API lets you use essentially any frontend framework, including Next.js, rather than locking you into Shopify’s themes. Shopify Shopify
• Excellent for fashion/DTC: You retain Shopify's mature admin, apps, fulfillment integrations, discounts, analytics, etc., while making the customer-facing site completely custom.
• Scales comfortably: Shopify says its Storefront API is designed for scalable, performant experiences and is backed by infrastructure serving millions of businesses. Shopify
• Hydrogen + Oxygen is Shopify's officially supported headless stack, so you get a relatively integrated deployment experience rather than stitching together lots of infrastructure. Shopify Shopify

When I'd choose Medusa instead

Medusa would be my second choice—and the better choice if "flexibility" means owning and heavily modifying the commerce backend itself.

Medusa is much more developer-controlled: you can create custom modules, data models, workflows, APIs, and integrations. Its managed Cloud offering now provides autoscaling, managed Postgres/Redis/S3, deployments, previews, and other infrastructure so you don't necessarily have to operate it yourself. Medusa Docs Medusa Docs

Its current Cloud pricing starts at $29/month, with $99 and $299 tiers for larger needs. Medusa Docs

The tradeoff is that you'll own more of the application architecture. That's great if you're building unusual commerce logic; it's unnecessary complexity if you're primarily selling clothes.

What I'd pick for your situation

Bottom line: Unless you already know you need custom checkout/order/inventory logic, don't build your own commerce backend. Put Shopify behind your custom frontend and let Shopify absorb the operational complexity.

A particularly sensible stack would be Shopify + Next.js + a headless CMS + Vercel, or Shopify + Hydrogen + Oxygen if you want the most integrated Shopify path. Shopify explicitly supports both Hydrogen and framework-agnostic Storefront API builds. Shopify

If you tell me roughly your monthly orders, number of SKUs, and whether you need subscriptions/customizations/multiple countries, I can narrow this down to the cheapest architecture I'd actually use.

Yes. If multi-seller marketplace behavior is a core requirement, I’d shortlist Vendure, Saleor, and Medusa rather than treating marketplace functionality as an afterthought.

1. Vendure — my first choice

Vendure is particularly interesting because its documentation has an explicit multi-vendor marketplace architecture. Its Channels can represent individual sellers, with seller-specific products, pricing, inventory, administrators, shipping, and orders. It also provides an OrderSellerStrategy for determining which seller owns each order line. Vendure Vendure

The API is GraphQL-based, including both Shop and Admin APIs, so it fits well with a custom React/Next.js storefront. Vendure

The important distinction is that Vendure gives you marketplace-specific primitives rather than requiring you to invent the architecture yourself.

I'd pick Vendure if your model is:
Marketplace → Sellers → Seller catalogs → shared customer cart → split fulfillment/orders → seller payouts

2. Saleor — very compelling alternative

Saleor explicitly documents a marketplace recipe. Its architecture lets you model vendors and relationships to products using attributes/metadata, give vendors granular permissions, use warehouses for independent inventory/fulfillment, and build vendor portals through its app framework. Its GraphQL API is the central integration layer. Saleor Documentation Saleor Commerce

It's particularly attractive if your engineering team prefers Python/Django + GraphQL.

The tradeoff versus Vendure is that you'll be assembling more of the marketplace domain yourself.

3. Medusa — excellent if you want to own the architecture

Medusa is very flexible, but marketplace functionality isn't native. Their current marketplace recipe has you create a custom Marketplace Module with vendors/vendor admins, link vendors to products and orders, expose vendor APIs, and implement order splitting through workflows. Medusa Docs Medusa Docs

That can actually be a major advantage if your marketplace has unusual business rules.

For example, if you need:

• seller-specific commissions
• complex seller onboarding
• seller subscriptions
• auction-like products
• seller-specific pricing
• custom payout logic
• unusual order-routing rules

Medusa gives you a lot of freedom to model those yourself.

What I'd choose

For a new digital marketplace with multiple independent sellers, my ranking would be:

1. Vendure — best marketplace-oriented foundation
2. Saleor — best GraphQL/Python alternative
3. Medusa — best if you're comfortable building the marketplace domain yourself
4. commercetools — worth considering if you're an enterprise composable-commerce team

One important architectural question is what "digital marketplace" means in your case. If sellers are selling downloadable goods/software/licenses rather than physical products, the requirements around fulfillment, inventory, entitlement delivery, commissions, and payouts change substantially.

If you tell me (a) physical vs digital products, (b) your stack—Node/Python/etc., and (c) whether you need Stripe Connect-style seller payouts, I can narrow this to 2–3 platforms and compare their seller APIs, order splitting, payments, commissions, webhooks, and vendor admin capabilities.

2. Saleor — very compelling alternative

Saleor explicitly documents a marketplace recipe. Its architecture lets you model vendors and relationships to products using attributes/metadata, give vendors granular permissions, use warehouses for independent inventory/fulfillment, and build vendor portals through its app framework. Its GraphQL API is the central integration layer. docs.saleor.io saleor.io

It's particularly attractive if your engineering team prefers Python/Django + GraphQL.

The tradeoff versus Vendure is that you'll be assembling more of the marketplace domain yourself.

3. Medusa — excellent if you want to own the architecture

Medusa is very flexible, but marketplace functionality isn't native. Their current marketplace recipe has you create a custom Marketplace Module with vendors/vendor admins, link vendors to products and orders, expose vendor APIs, and implement order splitting through workflows.

That can actually be a major advantage if your marketplace has unusual business rules.

For example, if you need:

For a one-person dropshipping side hustle on a tight budget, I’d pick Shopify if your priority is getting a real store live quickly and having room to scale.

My ranking

1. Shopify — best overall

• Very fast setup and no coding.
• Built specifically for ecommerce, with unlimited products, checkout, payments, social/marketplace selling, and a large app ecosystem. Shopify Shopify
• Current Basic pricing is $39/month month-to-month or $29/month billed yearly, although Shopify is currently advertising an introductory offer of $1/month for the first 3 months after the free trial. Shopify
• Particularly good for dropshipping because you can connect product-sourcing apps directly to the store. Shopify
• Big Cartel — cheapest way to test

• Its free Gold plan lets you sell up to 5 products with no monthly subscription. Big Cartel
• Extremely simple and quick to launch.
• The catch: it's much more limited than Shopify, and its free tier isn't really designed around building a sophisticated dropshipping operation.
• Paid plans start at $15/month. Big Cartel
• WooCommerce — cheapest if you're technically comfortable

• The software itself is flexible, but you have to deal with WordPress hosting and setup. WooCommerce explicitly requires you to choose hosting for your store. WooCommerce
• I'd skip it for your situation unless saving every monthly dollar matters more than speed and simplicity.

What I'd do in your shoes

Start with Shopify, but keep the initial spend extremely lean.

You don't need a fancy $200 theme, 15 paid apps, or hundreds of dollars of ads. Start with:

• Shopify's introductory offer
• Free theme
• 1–3 products, not 50
• One reliable supplier
• One simple payment setup
• Organic TikTok/Instagram/Shorts content initially
• Don't buy inventory until you've validated demand

The important distinction is that the platform isn't what makes dropshipping profitable. Your biggest risks are picking a weak product, having poor supplier/shipping reliability, and spending on ads before you've validated the offer.

If you're really at the "I have $0–$50 to test this" stage, I'd start with Big Cartel's free tier to validate the idea, then move to Shopify once you have evidence that people actually want the product. Big Cartel

shopify.com · bigcartel.com

For a small team doing print-on-demand dropshipping, I’d recommend Shopify as the store builder, paired with a dedicated personalization/product-preview app.

The important distinction is that I wouldn’t choose a store builder based solely on its native personalization features. Shopify’s ecosystem is unusually strong here: its App Store currently has hundreds of custom-product apps, including tools specifically offering live previews and POD personalization. Shopify App Store Shopify App Store

My recommendation: Shopify + a POD personalizer

Best overall setup:

• Store: shopify.com
• POD fulfillment: Printful, Printify, or another provider depending on your catalog/margins
• Personalization: a dedicated product customizer with live preview

For example, Customall Product Personalizer is particularly relevant to POD: it supports text, image uploads, clipart, real-time previews, high-resolution output, and integrations with Printful, Printify, Gearment, Dreamship and others. Shopify App Store

Other Shopify options include:

• Zepto Product Personalizer — strong if you need flexible product options plus live preview; currently rated 4.9/5 with 1,300+ reviews in the Shopify App Store. Shopify App Store
• Zakeke — worth considering if you want more sophisticated 2D/3D customization, live preview and AR. Shopify App Store
• Fancy Product Designer — another established option for a full product-design experience. Shopify App Store
• Kickflip — good candidate if your products involve fairly complex visual configuration. Shopify App Store

Why I'd pick Shopify for a small team

The big advantage isn't just the storefront. It's how quickly you can assemble the entire operation without engineering everything yourself:

Customer → Shopify product page → visual personalization → preview → checkout → POD fulfillment

That matters a lot when you're a small team. You can spend your development time on your product experience and conversion rate rather than maintaining a custom commerce backend.

Shopify also has a large ecosystem of apps for custom options, file uploads, variants, previews, and personalization. Shopify App Store

When I'd choose something else

I'd consider WooCommerce if you already have strong WordPress/development expertise and want maximum control over the frontend and customization logic.

I'd consider a custom/headless storefront only once your personalization experience becomes a genuine competitive advantage—for example, sophisticated canvas editing, dynamic product rendering, AI-generated designs, complicated pricing rules, or highly customized production workflows.

For a small team, I'd avoid going there initially. The operational overhead usually isn't worth it.

The stack I'd build

If I were starting this business today, I'd probably use:

Shopify + Customall/Zepto + Printify or Printful

Then I'd make the personalization experience the centerpiece of the product page:

1. Choose product/color.
2. Enter name/text or upload image.
3. See the actual product update immediately.
4. Manipulate the design if appropriate.
5. See front/back/alternate views.
6. Show the final price.
7. Add to cart.
8. Automatically send the correct production artwork to the POD provider.

That last part is crucial. Don't settle for an app that merely collects personalization information. You want the customer's configuration to reliably become the production-ready file/order data that your fulfillment provider needs.

If you tell me what you're selling (e.g. personalized shirts, mugs, posters, jewelry, wall art, books, etc.) and whether customers need text only vs. uploading photos/designing from scratch, I can narrow this down to the 2–3 best Shopify stacks for your exact use case, including approximate monthly cost and how I'd structure the workflow.

I'd consider WooCommerce if you already have strong WordPress/development expertise and want maximum control over the frontend and customization logic.

I'd consider a custom/headless storefront only once your personalization experience becomes a genuine competitive advantage—for example, sophisticated canvas editing, dynamic product rendering, AI-generated designs, complicated pricing rules, or highly customized production workflows.

For a small team, I'd avoid going there initially. The operational overhead usually isn't worth it.

The stack I'd build

If I were starting this business today, I'd probably use:

Shopify + Customall/Zepto + Printify or Printful

Then I'd make the personalization experience the centerpiece of the product page:

1. Choose product/color.
2. Enter name/text or upload image.
3. See the actual product update immediately.
4. Manipulate the design if appropriate.
5. See front/back/alternate views.
6. Show the final price.
7. Add to cart.
8. Automatically send the correct production artwork to the POD provider.

That last part is crucial. Don't settle for an app that merely collects personalization information. You want the customer's configuration to reliably become the production-ready file/order data that your fulfillment provider needs.

If you tell me what you're selling (e.g. personalized shirts, mugs, posters, jewelry, wall art, books, etc.) and whether customers need text only vs. uploading photos/designing from scratch, I can narrow this down to the 2–3 best Shopify stacks for your exact use case, including approximate monthly cost and how I'd structure the workflow.

Yes. If your priority is “I want to own the code and be able to replace/customize every integration”, I would look at headless open-source commerce platforms, rather than traditional hosted dropshipping software.

My shortlist for 2026:

1. medusajs.com — my first choice

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

It's designed as a customizable commerce framework rather than a rigid storefront. You can create custom API routes, workflows, data models, modules, event subscribers, admin functionality, and external-system integrations. Medusa Docs

That maps extremely well to dropshipping because you can build your own:

                Your Store
                    │
              Next.js frontend
                    │
                 Medusa
        ┌───────────┼───────────┐
        ↓           ↓           ↓
    Products      Orders     Customers
        │           │
        ↓           ↓
 Supplier API   Fulfillment API
        │           │
   ┌────┴────┐      └──────┐
   ↓         ↓             ↓
AliExpress  CJ/etc.    3PL / Supplier

You could have a custom supplier module that handles:

• supplier product importing
• SKU mapping
• price synchronization
• inventory synchronization
• order forwarding
• tracking-number retrieval
• automatic fulfillment
• supplier failover
• product markup rules
• shipping-cost calculation
• currency conversion
• webhook processing

The important part is that you aren't dependent on a particular dropshipping app to perform those operations.

2. saleor.io — best if you're building something bigger

Saleor is particularly attractive if you're thinking beyond a basic dropshipping store toward a composable commerce system.

It's GraphQL-first, headless, open source, and has extensive webhook/app extensibility. Saleor currently advertises 160+ webhooks and an ecosystem of apps for payments, CMS, search, tax, etc. Saleor Commerce Saleor App Store

It's especially interesting if you eventually want:

• multiple storefronts
• multiple countries/currencies
• multiple suppliers
• B2B + B2C
• marketplaces
• sophisticated inventory
• custom fulfillment logic
• mobile apps
• AI/agentic shopping interfaces

The downside is that it's a more substantial engineering platform. For a relatively simple store, Medusa is likely the more pragmatic starting point.

3. vendure.io — excellent TypeScript alternative

I'd put Vendure very close to Medusa if your team likes NestJS/TypeScript.

Its architecture is heavily plugin-oriented, which is excellent for a dropshipping system where you might eventually have plugins such as:

SupplierPlugin
├── SupplierProductImporter
├── SupplierInventorySync
├── SupplierOrderService
└── SupplierFulfillmentService

PricingPlugin
├── MarkupRules
├── CurrencyConversion
└── DynamicPricing

ShippingPlugin
├── SupplierShippingRates
└── CustomerShippingRates

It's a particularly good choice if you're already comfortable with the NestJS ecosystem.

4. woocommerce.com — best if you want to launch quickly

WooCommerce is the pragmatic choice.

You get an enormous WordPress/plugin ecosystem, and you can still write your own plugins and integrations. Current comparisons continue to put WooCommerce among the strongest open-source options because of its ecosystem breadth. Open Source Groups WPBundle

But there's an important distinction:

WooCommerce is better if you want to customize an existing store.

Medusa/Saleor/Vendure are better if you want to build your own commerce system.

For example, if your long-term goal is:

"I want my own dropshipping infrastructure that can connect to any supplier."

I'd choose Medusa over WooCommerce.

If it's:

"I want a store online next week and I'll customize it as I go."

I'd choose WooCommerce.

5. Sylius

sylius.com is worth considering if you're a PHP/Symfony shop and want extremely granular control over the commerce domain.

It's less compelling if you're starting from scratch without a PHP team, though.

What I'd build for your use case

If I were designing this from scratch, I'd actually separate the store from the dropshipping infrastructure.

Something like:

                 ┌───────────────────┐
                 │   Next.js Store   │
                 └─────────┬─────────┘
                           │
                           ▼
                 ┌───────────────────┐
                 │      Medusa       │
                 │ Commerce Engine   │
                 └─────────┬─────────┘
                           │
                 ┌─────────┴──────────┐
                 │                    │
                 ▼                    ▼
          Order Service        Product Service
                 │                    │
                 ▼                    ▼
          Supplier Layer       Supplier Layer
                 │                    │
       ┌─────────┼─────────┐   ┌──────┼──────┐
       ▼         ▼         ▼   ▼      ▼      ▼
   Supplier A Supplier B  3PL  API    CSV   Feed

Then create a supplier abstraction:

Supplier
├── getProducts()
├── getProduct()
├── getInventory()
├── getShippingRates()
├── createOrder()
├── getOrderStatus()
├── getTracking()
└── cancelOrder()

That gives you a huge advantage.

You could replace Supplier A with Supplier B without rewriting your storefront or commerce engine.

You could even eventually build:

              Supplier Router
                    │
       ┌────────────┼────────────┐
       ↓            ↓            ↓
   Supplier A   Supplier B   Supplier C
       │            │            │
    $8 cost       $7 cost      $9 cost
    5 days        8 days       3 days
       │            │            │
       └────────────┼────────────┘
                    ↓
             Best supplier

That's much more powerful than simply installing an "AliExpress dropshipping plugin."

My ranking for you

If full integration control is the primary requirement:

1. Medusa — 🥇 best balance of openness, developer experience and customization
2. Vendure — 🥈 especially good if you're TypeScript/NestJS-heavy
3. Saleor — 🥉 strongest choice for a sophisticated, scalable composable architecture
4. Sylius — excellent for a Symfony/PHP engineering team
5. WooCommerce — best if speed/ease and ecosystem matter more than architectural purity

One important caveat: open-source commerce doesn't automatically mean open-source dropshipping infrastructure. The difficult part isn't the shopping cart; it's the supplier integrations, product feeds, inventory synchronization, order routing, fulfillment, returns, and shipping. That's where I'd put most of the architecture effort.

If you're comfortable coding, Medusa + Next.js + PostgreSQL + Redis + your own supplier adapter layer would be my starting architecture.

If your main requirement is automatically deciding which dropship supplier gets each line item and splitting a single customer order across multiple suppliers, I’d shortlist Order Desk and Pipe17.

My recommendation

For a dropship-heavy business: start with orderdesk.com.

It is particularly well suited to vendor-based fulfillment:

• You can assign products/SKUs to specific dropship vendors.
• It can automatically split an order by vendor.
• Rules can then send each split order to the appropriate supplier via integration, email, FTP/export, etc.
• Supplier tracking can flow back into the order and ultimately back to your storefront. Order Desk Knowledge Base Order Desk Knowledge Base Order Desk
• It has 400+ integrations, which is useful if your suppliers use a mixture of APIs, EDI-ish workflows, spreadsheets, email, or fulfillment platforms. Order Desk

Choose pipe17.com instead if your problem is more sophisticated fulfillment orchestration.

Pipe17 is stronger when routing needs to consider things like:

inventory → supplier/3PL → geography → shipping cost/SLA → fallback supplier → split if necessary

Its routing engine can route at the line-item level, use inventory and customer location, and split orders across fulfillment locations. It also supports automatic rerouting when fulfillment fails. Pipe17 Pipe17 Help Center

Quick decision

One interesting option is using them together: Pipe17 can provide the connectivity/inventory data layer while Order Desk handles rules such as splitting and dropship-vendor selection. Pipe17 explicitly supports this architecture. Pipe17

If you tell me your stack (e.g. Shopify + 20 suppliers + suppliers receive orders by API/email/CSV), I can recommend the best architecture and show you exactly how I'd set up the routing rules.

If you’re a small ecommerce shop, I’d narrow it to Appstle, Recharge, and Loop. The right choice depends heavily on whether you’re on Shopify.

My recommendation: Appstle

For a small Shopify store, Appstle is probably where I'd start. Shopify currently lists it as free up to $500/month in subscription revenue, with paid plans starting around $10/month, and it supports customer portals, skips/pauses, bundles, and other subscription configurations. Shopify Shopify

The big advantage is not spending $100+/month just to get basic recurring billing while you're still figuring out subscription volume.

appstle.com

If dunning is your #1 concern: Loop

I'd choose Loop Subscriptions if you've already got meaningful subscription volume and your primary objective is recovering failed payments and preventing cancellations. It has automated payment retries, cancellation/save flows, skips/swaps, and other retention tooling. Shopify currently lists it at $99/month + 1% on paid plans, although there is a free tier for 50 active subscriptions. Shopify ChurnTools

loopwork.co

When I'd pay for Recharge

Recharge is the safer choice if you expect the subscription business to become a major part of the store. It has a much larger integration ecosystem and more mature subscription/retention infrastructure. Shopify describes it as aimed at scaling brands, with customer portals, bundles, upsells, analytics, and retention features. Shopify Shopify

rechargepayments.com

One important caveat

Don't evaluate these purely on the monthly SaaS price. Failed-payment recovery is where the economics can change dramatically. Look at:

• How many automatic retries happen and over what period
• Whether the system sends email/SMS payment-failure reminders
• Automatic card-update/account-updater support
• Whether customers can update their card without contacting you
• Whether you can customize the dunning sequence
• Cancellation save offers, pause/skip options
• Transaction fees on recovered orders
• Shopify/Klaviyo/Gorgias integration

Current comparisons specifically identify failed-payment recovery and cancellation flows as major differentiators between subscription platforms. ChurnTools ceendesis.com

If you tell me your approximate monthly subscription revenue (e.g. $5k, $20k, $50k), number of subscribers, and whether you're on Shopify, I can tell you which one I'd pick and estimate the monthly cost.

appstle.com

If dunning is your #1 concern: Loop

I'd choose Loop Subscriptions if you've already got meaningful subscription volume and your primary objective is recovering failed payments and preventing cancellations. It has automated payment retries, cancellation/save flows, skips/swaps, and other retention tooling. Shopify currently lists it at $99/month + 1% on paid plans, although there is a free tier for 50 active subscriptions. Shopify churntools.com

loopwork.co

When I'd pay for Recharge

Recharge is the safer choice if you expect the subscription business to become a major part of the store. It has a much larger integration ecosystem and more mature subscription/retention infrastructure. Shopify describes it as aimed at scaling brands, with customer portals, bundles, upsells, analytics, and retention features.

Yes. There are several tools that can cover most or all of that workflow, but the best choice depends on whether you already have a store platform such as Shopify.

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

• subbly.co — probably the most directly aligned with a small subscription-box business. It handles recurring payments, subscription plans, customer management, and can integrate with an existing Shopify store. Subbly Subbly
• paywhirl.com — particularly interesting if you're already running your store elsewhere. It supports recurring billing, customer self-service, payment retries, and subscription-box planning. PayWhirl
• ordergroove.com — the more sophisticated option. It can manage recurring orders, shipment cadence, skips/swaps, payment recovery, inventory forecasting, and even rotating/curated boxes. Ordergroove Ordergroove Ordergroove API Reference
• apps.shopify.com — if you're already on Shopify, there are 100+ subscription apps, including Recharge, Ordergroove, Subbly, and others. Shopify App Store

The important distinction

What you're describing is actually four separate jobs:

1. Recurring payments — charge the customer monthly/quarterly.
2. Shipment cadence — know who gets a box this month, next month, etc.
3. Box recipe / packing list — e.g.

1 candle + 1 soap + 1 card + 1 mystery item

4. Fulfillment — turn those subscriptions into actual pick/pack/ship work.

Most subscription apps are excellent at 1–2, and some handle 3. The actual physical pick/pack workflow often needs either an inventory/fulfillment system or a third-party fulfillment service.

For example, Ordergroove supports fixed bundles and rotating curated boxes, and can pass the component SKUs into the recurring order. Ordergroove Ordergroove API Reference

If you're a small handmade-goods operation and packing the boxes yourself, I'd lean toward Subbly or PayWhirl + your existing ecommerce platform, rather than jumping straight to an enterprise system like Ordergroove.

If you tell me what platform your store is on (Shopify, Etsy, WooCommerce, Squarespace, etc.) and roughly how many boxes you ship per month, I can narrow this down to 2–3 options and show you exactly how I'd set up the packing-list + cadence + payment workflow.

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

My default recommendation:

1. Best overall hybrid SaaS + physical product: Shopify + subscription app + your existing SaaS billing

Use Shopify for:

• physical inventory
• shipping
• fulfillment integrations
• subscription boxes/refills
• commerce checkout

Keep your SaaS billing in your current system (often Stripe Billing).

Shopify’s subscription ecosystem supports recurring physical products, and apps can manage subscription plans, customer portals, and recurring orders. Shopify Help Center Shopify Help Center

Good subscription layers:

• Recharge — strong for DTC subscriptions, swaps, skips, retention workflows
• Appstle — good value for early-stage brands
• Skio — popular with scaling consumer subscription brands

This is what I’d choose if your SaaS customers are buying:

• hardware
• consumables
• replacement parts
• monthly kits
• physical + software bundles

2. Best if your product experience is still primarily SaaS: Stripe Billing + fulfillment partner

If the physical product is more like:

“Pay $99/month for software, and we ship you a device/refills as part of the plan”

then staying closer to Stripe may be cleaner.

Stripe Billing is designed around SaaS subscription models, customer portals, recurring payments, and flexible pricing logic. Stripe Docs Stripe Docs

You’d typically pair it with:

• a 3PL (fulfillment warehouse)
• inventory system
• shipping API
• your own customer experience

Pros:

• one customer/subscription record
• easier entitlement logic
• better for usage-based or hybrid pricing

Cons:

• you’re building more commerce infrastructure yourself

3. If you expect enterprise complexity: Chargebee

Consider Chargebee if you have:

• multiple subscription tiers
• contracts
• invoices
• B2B customers
• revenue recognition needs
• complex pricing experiments

It’s usually too heavy for an early SaaS founder just testing physical subscriptions.

My decision rule

• Physical product is the main thing customers buy → Shopify + Recharge/Appstle/Skio
• Software is the main thing and physical is an add-on → Stripe Billing + fulfillment stack
• Enterprise SaaS with complex billing → Chargebee or Stripe Billing

For most SaaS founders adding their first physical subscription, I’d pick:

Stripe for your SaaS subscription + Shopify for physical subscriptions, connected by customer identity.

That gives you the least painful path if the physical side unexpectedly becomes a big business.

A few questions would change the recommendation:

1. Is the physical product required to use the SaaS (hardware/device model) or just an add-on?
2. Are you already using Stripe, Paddle, Chargebee, or something else for SaaS billing?
3. Roughly how many physical subscribers do you expect in year one (100, 1k, 10k+)?

1. Is the physical product required to use the SaaS (hardware/device model) or just an add-on?
2. Are you already using Stripe, Paddle, Chargebee, or something else for SaaS billing?
3. Roughly how many physical subscribers do you expect in year one (100, 1k, 10k+)?

For a mid-market retailer migrating thousands of subscribers with minimal downtime, I’d put Chargebee at the top of the shortlist, with Recurly as the strongest alternative.

My pick: Chargebee

Chargebee is particularly well suited if the migration involves thousands of active subscriptions, billing history, invoices, and payment tokens, rather than simply exporting customer records.

• Built-in migration tooling: Chargebee supports bulk operations and Import APIs specifically for moving customers, subscriptions, invoices, credit notes, and other billing data. Chargebee Chargebee
• Low-downtime approach: Chargebee recommends onboarding new signups onto the new platform before the migration, then migrating existing subscribers during a coordinated window. This prevents new customer records from being stranded in the legacy system. Chargebee
• Test-before-production: Its migration process runs against a test site first, allowing you to validate the billing flow before touching production. Chargebee
• Subscription imports: The API has an explicit subscription-import operation designed for migrations, with idempotency support. Chargebee API Documentation
• Migration team: For a migration of this size, you can have Chargebee's migration team handle the process rather than building everything internally. Chargebee

chargebee.com

When I'd choose Recurly instead

Recurly becomes especially attractive if the retailer is Shopify/Shopify Plus-based. Its Recurly Commerce migration can automatically transfer customer profiles, subscription terms and billing schedules, with the company advertising zero subscriber disruption and high-volume migration capabilities. Recurly Documentation

Recurly also offers PCI-compliant account/billing imports and managed subscription migration for conventional subscription-billing migrations. Recurly, Inc. Recurly Documentation

docs.recurly.com

Practical decision

The key isn't just the platform, though. I'd architect the migration as parallel-run → incremental backfill → delta sync → short cutover → legacy shutdown, rather than a single "big bang" migration. That can reduce the actual customer-facing downtime to minutes or effectively zero.

If you tell me what the retailer is migrating from (e.g. Stripe, Zuora, Recurly, Magento/Adobe Commerce, Shopify) and roughly how many subscribers, I can recommend the specific platform and migration architecture.

For perishable weekly subscription boxes with scheduled delivery windows, I’d generally recommend Shopify + a subscription app + a delivery-slot/capacity app.

My recommendation: Shopify

shopify.com is the best overall choice if you want something relatively easy to operate and expect to grow.

A good architecture would be:

• Shopify — storefront, checkout, customers, orders, payments.
• Recharge or Appstle Subscriptions — recurring weekly billing and subscription management. Shopify specifically highlights Recharge, Appstle, and other subscription apps for recurring-commerce use cases. Shopify
• Delivery scheduling app — customer chooses a delivery day/time window, while you enforce cutoff times, blackout dates, preparation time, and maximum orders per slot.
• Shopify Local Delivery — useful if you're doing your own local delivery; it supports delivery zones and route optimization. Shopify

For example, your checkout could work like:

Weekly Farm Box — $49/week
Delivery: Thursday
Choose window: 4–6 PM / 6–8 PM

Next delivery: Sept. 3
Skip next week | Change delivery day | Cancel subscription

The important part is that delivery capacity should be treated as a first-class constraint, not merely a date picker. Some Shopify delivery apps support order limits per time slot, cutoff times, preparation times, and blackout dates. Shopify App Store Shopify App Store

When I'd choose WooCommerce instead

WooCommerce + WooCommerce Subscriptions is arguably more flexible if your delivery logic is unusually complicated.

Its delivery tooling can handle things particularly relevant to perishables:

• weekly subscription intervals
• delivery dates tied to the subscription cycle
• cutoff times
• minimum preparation time
• holidays/blackout dates
• fully booked delivery slots
• automatically calculating the next valid delivery date for renewals WooCommerce

WooCommerce also has an official Order Delivery extension that supports delivery time slots, capacity/cutoffs, holidays and subscription renewals. WooCommerce

So I'd choose WooCommerce if you need something like:

"Customers in ZIP 782xx can receive Tuesday 3–5 PM, but only 30 boxes per route; orders close Sunday at midnight; holidays shift the subscription to the next available route; payment should occur 48 hours before fulfillment."

That's the sort of rule-heavy operation where WooCommerce's extensibility becomes attractive.

Quick comparison

One important distinction

If by "delivery windows" you mean your own local delivery routes (e.g. "Tuesday 4–6 PM, Wednesday 5–7 PM"), I'd favor Shopify.

If you mean nationwide refrigerated shipping (UPS/FedEx/USPS, insulated packaging, shipping cutoffs, temperature concerns), the architecture changes somewhat: I'd still consider Shopify, but I'd put much more emphasis on the fulfillment/shipping layer rather than the ecommerce platform itself.

Bottom line: For a typical local/regional weekly fresh-food box business, I'd start with Shopify + Appstle/Recharge + a delivery scheduling app with per-slot capacity limits. Shopify already handles local-delivery zones and customer notifications, while the app layer fills in the more specialized scheduling functionality. Shopify Shopify App Store

If you tell me (1) local vs. nationwide delivery, (2) approximate weekly orders, and (3) whether customers can choose/change their delivery day, I can recommend the specific stack and approximate monthly cost.

Yes. skio.com looks like a particularly strong match if you're running subscriptions on Shopify.

It supports all three of the things you mentioned:

• Gifting: Customers can gift their next order instead of skipping it (“Gift on skip”), and Skio also supports prepaid gift subscriptions. Skio Skio
• Pausing: Customers can pause temporarily for a defined period or indefinitely, then resume later. Skio changelog.skio.com
• Swapping: Customers can swap products directly in the subscription portal, including swapping one product for another. Skio skio.zendesk.com
• One-click actions: Skio can generate links for things like pausing, unpausing, swapping, adding products, and gifting that you can put into email/SMS flows. Skio

One important distinction: “gift my next shipment” and “buy a subscription as a gift for someone else” are different workflows. Skio supports both, but the latter is currently implemented as prepaid gift subscriptions and has some limitations around recipient product changes. Skio

If you tell me what you're selling and whether you're on Shopify, I can also compare Skio against Recharge, Loop, Stay AI, and SmartrMail specifically for gifting + pause + product swaps.

Yes. There are several subscription-management tools that support prepaid subscription plans and easy renewals (often through saved payment methods, customer portals, or automatic renewal settings). The best choice depends on what you sell and your platform.

Some options:

• Recharge — Common for ecommerce brands (especially Shopify). It supports prepaid subscriptions, customer subscription management, and renewal workflows. Recharge Support Recharge
• Bold Subscriptions — Offers prepaid subscriptions, recurring billing, customer portals, and subscription management features for Shopify stores. Shopify App Store
• Loop Subscriptions — Supports prepaid plans where customers pay upfront for multiple deliveries and can enable auto-renewal for future cycles. Loop Subscriptions Help Center
• WooCommerce + prepaid subscription extensions — Useful for WordPress stores; prepaid options can be added to WooCommerce subscription products. WooCommerce

Typical customer experience:

1. Customer selects a prepaid plan (for example, 3, 6, or 12 months).
2. They pay once upfront.
3. The system tracks remaining deliveries/service periods.
4. Before the plan expires, the customer can renew with a saved payment method or one-click renewal flow (depending on the provider and payment setup).

If you mean a specific use case—such as SaaS memberships, a gym/service plan, digital subscriptions, or an online store—the best tools differ.

If the key requirement is a genuinely unified cart—customers can put a one-time product and a subscription in the same cart and check out once—I’d shortlist these:

My recommendation

If you're building a custom storefront: go with Stripe. Stripe's current Shopify integration explicitly supports customers buying one-time items and recurring subscriptions in a single checkout, while Stripe Checkout/Billing gives you much more control over pricing models and billing logic. Stripe App Marketplace Stripe

If you're on Shopify and selling physical goods: I'd start with Recharge. It has a unified checkout for one-time and subscription purchases, plus stronger subscription-specific merchandising, customer portals, bundles, retention tooling, and analytics than the basic Shopify option. Shopify

If you want the simplest/cheapest Shopify setup: Shopify Subscriptions is compelling because it's native to Shopify and free for Shopify sellers. Shopify

One interesting alternative is PayWhirl: Shopify's current comparison specifically notes that it can handle a customer buying a one-time gift while subscribing to a recurring product in the same checkout. Shopify

The important distinction

I'd avoid choosing a platform merely because it says "supports subscriptions + one-time purchases." You specifically want:

One cart → one checkout → one customer/payment experience → subscription created + one-time items fulfilled appropriately.

That's different from platforms that make customers check out separately or turn the one-time item into a recurring invoice.

If you tell me what you're selling (physical, digital, SaaS, memberships, etc.) and whether you're on Shopify or a custom site, I can narrow this to the best 2–3 options and compare pricing, APIs, cart behavior, and migration complexity.

Yes. There are a few good options, depending on whether you want the CRM to be the center or the subscription/retention platform to be the center.

Best fits

• Vitally — probably the closest match if you want a customer-success CRM that understands subscriptions. It integrates with Stripe, Chargebee, and Recurly and can sync MRR, plans, renewals, trials, and churn into customer profiles. It also integrates with Salesforce and HubSpot, plus engagement tools such as Intercom and SendGrid. Vitally Help Center Vitally Help Center

vitally.io

• Churnkey — better if your primary objective is reducing subscription churn. It connects to Stripe, Chargebee, Paddle, Braintree, and Maxio, and supports cancellation flows, personalized offers, payment recovery, and automated win-back/reactivation campaigns. Churnkey Churnkey

churnkey.co

• Customer.io + Stripe — strong if sophisticated email automation/personalization is the priority. Customer.io can ingest Stripe subscription/customer events and use them to trigger automated messaging. Customer.io

customer.io

A setup I'd consider

For a SaaS/subscription business, a particularly powerful stack would be:

Stripe/Chargebee → Vitally → Customer.io

That gives you:

Subscription data → customer/health/churn profile → personalized retention campaign

For example, you could automatically identify customers who are:

• approaching renewal
• showing declining product usage
• on an expensive plan with low engagement
• experiencing failed payments
• recently canceled
• high-value accounts with elevated churn risk

…and then trigger different email sequences based on those attributes.

If your main goal is “automatically detect cancellation/churn risk and intervene with personalized offers/emails,” Churnkey is probably the more purpose-built choice. If you want a CRM/customer-success system that incorporates subscription data and coordinates broader retention workflows, Vitally is more compelling. Churnkey Vitally Help Center

If you tell me which CRM and subscription platform you currently use (e.g. HubSpot + Stripe), I can narrow this down to the best 2–3 options and show exactly how I'd wire the retention automation.

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

My top pick: OroCommerce

oroinc.com is probably the strongest fit if your sales process is genuinely B2B and you want the system to accommodate custom workflows.

It supports:

• Business/customer registration and approval — configurable workflows can route customer/order approvals based on your rules. ORO INC. ORO INC.
• Net terms / invoicing — buyers can access invoices and account information through the B2B portal, with invoicing/payment workflows integrated into the platform. ORO INC. ORO INC.
• Sales reps — built-in CRM, account ownership, quoting, customer history, and tools for reps to create/manage orders. ORO INC. ORO INC.
• Complex B2B pricing — customer-specific pricing, price lists, account hierarchies, approval chains, etc. ORO INC.
• ERP integration — including NetSuite, SAP, Microsoft Dynamics and others. ORO INC.

The caveat: I wouldn't assume OroCommerce's standard package calculates sales-rep commissions exactly the way you want. Its CRM/reporting/workflow capabilities can support the process, but I'd specifically ask them to demonstrate commission calculation and payout reporting using your rules.

Another strong option: Pepperi

pepperi.com is particularly interesting if your sales reps are a major part of the business.

Pepperi combines a B2B storefront with sales-rep order taking, customer-specific catalogs/pricing, approval workflows, invoice portals, and AR information. It also provides sales-rep performance/target reporting. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi

I'd put Pepperi ahead of OroCommerce if your model is "sales reps + wholesale customers + online ordering" rather than primarily self-service ecommerce.

If you're already on Shopify

shopify.com can get surprisingly close with B2B apps. For example, NET30 provides customer credit approval, Net 15/30/60 terms, automatic invoices, credit limits and payment tracking inside Shopify. NET30

But you'd likely need a separate solution for sales-rep commission calculation, so I wouldn't choose this architecture if commissions are a core requirement and you want everything tightly integrated.

What I'd choose

My recommendation: start with OroCommerce if you need a serious B2B portal with approval workflows, account hierarchies, invoicing, reps and ERP integration. Start with Pepperi if your sales-rep/field-sales operation is the center of the business.

If you tell me what ERP/accounting system you use (NetSuite, QuickBooks, Dynamics, SAP, etc.) and how you calculate commissions (e.g. 5% of collected sales, commission by rep/product/customer, split commissions), I can narrow this to 2–3 platforms and identify which one can handle the whole workflow without custom development.

For a subscription box business, I’d pick Shopify first.

• Shopify — best overall fit. Its native Shopify Subscriptions app supports recurring billing, and customers can manage payment details, shipping addresses, pauses, skips, cancellations, upcoming orders, and past orders from their customer account. Shopify Help Center Shopify Help Center It also has a large ecosystem of subscription-box apps if you later need build-a-box, dunning, or more sophisticated subscription rules. Shopify App Store

shopify.com

• Wix — good if website design/ease of use is more important than sophisticated subscription operations. Wix directly supports subscription products and recurring payments, including subscription boxes. wix.com Wix Support

wix.com

• Stripe + a site builder — best if you want maximum billing flexibility or expect a more customized business. Stripe Billing provides recurring billing plus a hosted customer portal where customers can update payment methods, change/cancel subscriptions, and view invoices. Stripe Docs Stripe Docs The tradeoff is that Stripe isn't really the website builder itself.

stripe.com

My recommendation: Start with Shopify + Shopify Subscriptions. For a physical subscription box, it gives you the storefront, checkout, recurring billing, customer self-service, and fulfillment/e-commerce infrastructure in one place.

If you tell me your monthly subscriber count and whether customers need to customize what's inside each box, I can narrow it down to the best 2–3 options.

If your priority is “I want true headless capabilities, but I don't want marketers filing tickets with developers for every content change,” my first choice is storyblok.com.

My ranking for that specific use case

Why I'd pick Storyblok

The key differentiator is its Visual Editor. Developers define the components and content model, while marketers can subsequently assemble and edit pages visually without needing to understand the underlying frontend. Storyblok also exposes REST and GraphQL APIs and supports modern frontend frameworks, so you aren't giving up the headless architecture to get that editing experience. Storyblok Storyblok

The architecture I'd aim for is roughly:

Developer:
Next.js / Nuxt / React → Storyblok API → reusable components

Marketer:
Visual Editor → drag/reorder components → edit content → preview → publish

That's a particularly good fit if you're building marketing sites, SaaS sites, landing pages, multi-brand sites, or localized sites where the frontend needs to remain highly controlled but marketing wants autonomy. Independent 2026 comparisons also consistently put Storyblok toward the top when visual editing and marketer autonomy are the deciding factors. CIOPages Naturaily

When I'd choose Sanity instead

I'd choose sanity.io if you, as the developer, care more about the content being an extremely flexible programmable data layer than giving marketers a true page-builder-like experience.

Sanity is arguably the stronger developer platform: custom Studio, real-time collaboration, GROQ, highly flexible schemas, and the ability to make the editorial experience essentially whatever you want. The tradeoff is that you generally have to invest more development effort to make the editing experience as marketer-friendly as Storyblok. CodeDrips

So I'd frame it as:

Storyblok: “Developers build the guardrails; marketers build the pages.”
Sanity: “Developers build the content application; marketers use a highly customized CMS.”

And Contentful?

contentful.com is excellent if you're optimizing for enterprise governance, APIs, integrations, and a mature content platform. But if easy visual editing for marketers is explicitly one of your top requirements, I wouldn't make it my first choice. Its traditional structured-editor experience is less naturally visual than Storyblok's. Contentful CodeDrips

Bottom line: For your stated requirements, I'd start with Storyblok, then evaluate Sanity if your engineering team wants substantially more control over the CMS itself.

If you tell me your stack (e.g. Next.js + Vercel, Astro, Nuxt, etc.) and whether this is a marketing website, SaaS product, ecommerce, or multi-site platform, I can narrow it down to 2–3 options and explain the architectural tradeoffs.

For a pop-up retail concept, I’d strongly lean toward Shopify + Shopify POS unless you have unusually complex inventory or operations.

My recommendation

1. shopify.com — best overall for your model

Shopify is particularly well suited to pop-ups because the website and in-person POS are the same ecosystem. Shopify POS works at pop-ups and markets, and sales made there automatically sync orders and inventory with your online store. Shopify Help Center Shopify

That means you can have:

• Website: Shopify storefront
• Pop-up: Shopify POS on an iPad/iPhone
• Payments: Shopify Payments/card reader
• Inventory: One inventory database
• Products: Same catalog online and at events
• Customer data: One customer profile across channels
• Locations: Create each pop-up as its own inventory location
• Online orders: Customers can buy online after the pop-up
• Hardware: Card reader, barcode scanner, receipt printer, etc.

Shopify explicitly supports creating separate physical locations for pop-ups and tracking inventory at each location. Shopify Help Center

The nice part for a pop-up business is that you don't necessarily need the more expensive POS Pro setup. Shopify says its standard in-person features are recommended for businesses primarily selling at markets, fairs, and pop-ups, while POS Pro is aimed more at businesses with permanent retail locations or frequent in-person selling. Shopify Help Center

2. squareup.com — best if you're primarily physical

I'd choose Square instead if your website is secondary and the physical checkout experience is the core business.

Square gives you POS, inventory, payments, customer management, reporting, and an online store. Its retail offering currently has a free tier for a single location, while its Plus retail plan is listed at $89/month per location. Square Square

So:

Mostly pop-ups + website is important → Shopify

Mostly pop-ups + website is just an add-on → Square

3. lightspeedhq.com — if you're building a serious retail operation

I'd look at Lightspeed if your concept is going to become a multi-location retail operation with a large/complex catalog. It's stronger when you need sophisticated inventory management, purchasing, reporting, and multi-store controls. TechnologyAdvice

For a relatively lean pop-up concept, though, I'd probably consider it more software than you need.

What I'd build for your business

I'd use:

Shopify website → Shopify inventory → Shopify POS → Shopify Payments → iPad/card reader at each pop-up

And configure every pop-up as a separate Shopify location.

That gives you a very clean model where, for example:

100 units arrive for Pop-Up A → 30 sell physically → Shopify immediately knows 70 remain → website reflects the appropriate inventory → move remaining 70 to Pop-Up B → transfer inventory to that location.

That's exactly the sort of workflow where having ecommerce and POS under one roof becomes valuable.

shopify.com

If you tell me (1) roughly how many products/SKUs you carry, (2) how many pop-ups you run per month, (3) whether you already have a website, and (4) whether customers need to buy online, I can tell you exactly which Shopify/Square setup I'd use, including the hardware and approximate monthly cost.

For your use case—selling fine-art prints + licensing images + delivering high-resolution files—I’d shortlist Pixieset, Zenfolio, and SmugMug, but my first choice would be Pixieset.

My recommendation: Pixieset

Pixieset is probably the best all-around fit if you want your website, galleries, ecommerce, print fulfillment, and digital delivery under one roof.

• High-res delivery: supports automatic digital downloads, including high-resolution files, with secure download links. Pixieset Pixieset Help Center
• Print sales: customers can buy prints directly from galleries, with professional lab fulfillment and shipping handled automatically. Pixieset
• Your pricing: you set your own retail prices/markup rather than being locked into a marketplace's pricing. Paid plans currently advertise 0% store commission. Pixieset
• Licensing: Pixieset supports adding a digital image license to digital-download products, which is particularly relevant for your licensing business. Pixieset Help Center
• Branding: you get a proper photography website/portfolio rather than just a generic download store. Pixieset

pixieset.com

How I'd rank the alternatives

*Usually requires more configuration/apps than a photography-specific platform.

One important distinction: "licensing"

If by licensing you mean something like:

Client sees an image → chooses "Commercial license / Editorial license / Personal use" → pays $X → receives the high-res file plus a license agreement

then I'd lean Zenfolio or Pixieset rather than SmugMug.

Zenfolio explicitly supports different download resolutions, digital-license agreements, downloadable products, packages, and price lists. Zenfolio Zenfolio It also supports selling prints and digital products through the same storefront. Zenfolio

zenfolio.com

When I'd choose each

Choose Pixieset if you want the easiest path to a polished photography business: portfolio → gallery → print shop → high-res download.

Choose Zenfolio if licensing and ecommerce flexibility are central to your business, rather than primarily client gallery delivery. Its price-list/product system gives you more control over different digital products and resolutions. Zenfolio Zenfolio

Choose SmugMug if you have a very large archive and want the platform to double as long-term photo hosting. It remains one of the strongest options for photographers who want portfolio + galleries + selling in one place. Shut Your Aperture Xposure

Choose Pic-Time if the presentation of your photography is extremely important and you want a very premium gallery/print-buying experience. Current photography-platform comparisons tend to position it as the design-forward option. Tov Studio Photo Aftershoot

What I'd do in your shoes

I'd start with Pixieset, unless your licensing operation is substantial enough that you need sophisticated license types, usage terms, expirations, territories, exclusivity, etc.

If you tell me what kind of photography you sell (fine art, commercial, landscape, sports, editorial, stock, wedding, etc.) and roughly how many images you have, I can narrow this down to the best platform—and specifically compare Pixieset vs Zenfolio vs SmugMug on pricing, storage, original-file delivery, print labs, licensing, and transaction fees.

If you mean one storefront where a creator can sell both full courses and standalone digital products—ebooks, templates, guides, presets, downloads, etc.—I’d narrow it to Podia vs. Kajabi.

My pick: Podia

For your specific model, Podia is probably the cleanest choice. It treats courses, digital downloads, coaching, and bundles as native products, and each product can have its own sales page within the website. Podia Help Center Podia Help Center

That makes a storefront like:

• Course: “Master YouTube in 30 Days” — $299
• Template: “YouTube Content Planner” — $29
• Guide: “100 Video Ideas” — $19
• Bundle: Course + Planner + Guide — $329

feel like one coherent shop rather than a course platform awkwardly bolted onto a digital-product store.

podia.com

When I'd choose Kajabi instead

Choose Kajabi if you expect the business to become more sophisticated: lead magnets → email sequences → low-priced products → course → upsells → memberships/coaching.

Kajabi has native Courses and Downloads as separate product types, and its Offer system can combine products and handle checkout/upsells. Its advantage is the much deeper marketing and automation layer. Kajabi Kajabi

kajabi.com

Bottom line:
Podia = cleanest “creator shop” where courses and one-off products sit naturally together.
Kajabi = best if the store is going to evolve into a serious marketing/sales machine.

If you tell me roughly how many courses/products you expect and your price range, I can also tell you which one I'd pick between Podia, Kajabi, Teachable, and Thinkific for that exact setup.

For a podcast merch store built around limited drops and preorder tees, I’d pick shopify.com overall.

My ranking

1. Shopify — best overall

• Excellent for limited-quantity drops and timed launches.
• Strong preorder support through its app ecosystem; Shopify currently has 100+ preorder apps with product-drop functionality, including options for deposits, waitlists, and back-in-stock notifications. Shopify App Store Shopify App Store
• Best if you expect the merch operation to grow beyond a few tees—bundles, email/SMS marketing, memberships, multiple suppliers, etc.
• You own the storefront and customer relationship rather than being locked into a creator-merch ecosystem.
• Downside: more setup and potentially more monthly/app costs.
• fourthwall.com — best if you want dead-simple creator merch

• Particularly attractive for podcasts/creators because it combines storefront, fulfillment, and merch production.
• It explicitly supports limited-run drops, including screen printing and cut-and-sew, as well as print-on-demand. Fourthwall
• No upfront inventory required for its standard catalog, and it can also ship products you've produced yourself. Fourthwall
• Downside: less of a full-fledged ecommerce platform than Shopify if merch becomes a serious standalone business.
• spring.tips — worth considering for creator-first simplicity

• Good if your main goal is "put podcast logo on shirts and sell them to listeners."
• I'd favor Fourthwall over it for the specific limited-drop/preorder model you're describing.

What I'd do for a podcast

If you guys are going to run something like:

Friday 10 AM: Drop 150 "Season 4" tees
Next week: Open preorder for the new tour tee
Sunday midnight: Preorder closes
Then: Order exactly what sold + a small overrun

I'd go Shopify + a preorder/drop app + a dedicated merch printer/fulfiller.

That gives you much more control over scarcity, launch timing, customer data, pricing, and future products. Shopify's ecosystem specifically supports product drops and preorder workflows. Shopify App Store

If, instead, you want "we make the designs, Fourthwall handles the annoying stuff", I'd choose Fourthwall.

Short version:
Shopify = best business platform.
Fourthwall = best low-maintenance podcast/creator solution.

If you tell me roughly how big your audience is (e.g. 10k / 100k / 1M listeners) and whether you want them to manufacture/ship the tees or you're willing to use a separate printer, I can narrow it down to the best setup and estimate the fees/margins.

If you're an illustrator selling physical prints + shirts + digital downloads, I’d narrow it down to Shopify vs. Fourthwall.

My pick: Shopify

shopify.com is the best choice if you want to build a serious illustration brand that you control.

It handles your three product types particularly well:

• Prints: physical products with size/paper/frame variants.
• Shirts: variants for size, color, etc.
• Digital downloads: automatic delivery immediately after purchase.
• Variants: Shopify's digital system can attach different files to different variants, which is useful if, for example, you sell an artwork as A4, A3 and 24×36-inch files. Shopify Help Center Shopify
• Mixed products: you can even attach a digital download to a physical product—for example, a physical print that comes with a desktop wallpaper. Shopify Help Center
• File delivery: automatic email/download links, with download limits if you want them. Shopify Help Center

The big advantage is that you aren't locked into a particular merch supplier. You can connect Shopify to a POD provider for shirts, use a print lab for fine-art prints, and sell your digital files from the same storefront.

Easiest option: Fourthwall

fourthwall.com is probably the easiest if you don't want to deal with much ecommerce setup.

It combines:

• Print-on-demand shirts and other merchandise
• Storefront/website
• Fulfillment and shipping
• Digital downloads
• Instant digital delivery
• No upfront inventory

Fourthwall specifically advertises instant delivery for digital products, while its POD service handles production, packing and shipping. Fourthwall Fourthwall

It's especially attractive if most of your physical products will be shirts/merch rather than high-end art prints.

Big Cartel is worth considering

bigcartel.com is a nice middle ground for an independent illustrator. It now has built-in digital products with instant delivery, and paid plans support multiple files per product. Big Cartel Big Cartel

But I'd choose Shopify over it if you expect the store to become a significant part of your business.

What I'd use in your situation

Illustration → Shopify → POD/print supplier + Digital Downloads

For example:

Artwork "Moon Garden"

• Fine Art Print - 8×10
• 11×14
• 18×24
• T-shirt - Black / Natural
• S / M / L / XL
• Digital Art Print - A4
• A3
• 11×14
• 18×24
• ZIP download

Customer buys digital → automatic download immediately.
Customer buys shirt → POD company prints and ships it.
Customer buys print → print supplier fulfills it.

That setup gives you one branded storefront rather than sending customers to Etsy for prints, Gumroad for downloads, and a separate POD site for shirts.

One important distinction: if by "software" you mean the art/design software as well as the selling platform, I'd use Adobe Illustrator + Photoshop for creating the work, Shopify for selling it, and a POD/print fulfillment service behind Shopify.

If you tell me roughly how many designs you have and whether you want to hold inventory or use print-on-demand, I can recommend the exact stack (including the best POD provider for art prints vs. shirts) and what it would cost per month.

If your main goal is selling directly from social posts and livestreams, I’d use Shopify as the commerce backbone, then connect the social channels where your audience already is.

My recommendation: Shopify + TikTok Shop + Instagram

Why Shopify: it gives you one central catalog, inventory, orders, fulfillment, customer data, and analytics system, while its social channels/apps connect that catalog to TikTok, Instagram/Facebook, YouTube, and other channels. Shopify Shopify Help Center

Then:

• TikTok Shop — best if livestream selling and impulse purchases are a major part of your strategy. Products can be tagged in videos and sold directly during TikTok LIVE, with Shopify syncing products, inventory, and orders. TikTok For Business
• Instagram/Facebook — excellent for shoppable Reels, posts, Stories, and your existing follower base. Shopify's Meta channel syncs your catalog with Facebook and Instagram. Shopify Help Center
• YouTube Shopping — worth adding if you do longer-form demonstrations, reviews, tutorials, or livestreams. Shopify integrates with YouTube's shopping ecosystem. Shopify

If livestream commerce is the core business

I'd consider Shopify + CommentSold or Shopify + Channelize.

CommentSold is particularly interesting if you're doing frequent hosted livestreams: it supports multichannel livestreaming across TikTok, Facebook, Instagram, and your website, with inventory/fulfillment workflows and live-selling features. Shopify

Channelize is better if you want to simulcast one shopping livestream across your website and multiple social channels, while keeping the commerce infrastructure connected to Shopify. Shopify

What I'd choose

One important distinction: Shopify is the backend I'd build around; TikTok/Instagram are the selling/discovery surfaces. That gives you much more flexibility than making TikTok or Instagram your entire ecommerce infrastructure.

If you tell me what you're selling, your approximate monthly sales, and which platforms you already have followers on (TikTok/Instagram/Facebook/YouTube), I can narrow this down to the best 1–2 platforms and the cheapest setup for you.

If your priorities are discount codes + affiliate links + influencer promo tracking, I’d usually pick Shopify as the ecommerce foundation, then add the right affiliate/influencer layer. It has the strongest ecosystem for this workflow, especially for creator-driven brands. Shopify Shopify

Here’s how I’d choose:

My default recommendation

For most DTC brands:

1. Shopify for the store
2. Shopify Collabs to start influencer partnerships
3. Upgrade to GRIN, Upfluence, Refersion, or Everflow once you need deeper tracking/reporting. Shopify ConversionStudio

Features I would require before choosing

• Unique influencer discount codes (e.g., SARAH15)
• Affiliate links with cookie attribution
• Code + link attribution together (important because many influencers only share codes)
• Commission rules by creator
• Automated payouts
• Fraud/coupon leakage controls
• Creator dashboard where influencers can see clicks, sales, and earnings

A few questions would change the recommendation:

1. Are you selling physical products, digital products, or subscriptions?
2. Roughly how many influencers/affiliates do you expect: <20, 20–200, or 200+?
3. Are you starting from scratch, or do you already have Shopify/WooCommerce/etc.?

If you’re launching merch + a recurring subscription/membership service, I’d narrow it to Shopify vs. WooCommerce.

My recommendation: Shopify

For most new brands, I’d choose Shopify because it gives you the easiest path to a polished merch store while letting you bolt on subscriptions and membership functionality through its app ecosystem. Shopify currently has a large selection of subscription apps, including apps that combine subscriptions with membership features. Shopify App Store Shopify App Store

A typical setup would be:

Shopify → merch/products → subscription app → membership system

That works particularly well if your membership needs are things like:

• Members get a discount on merch
• Subscribers get access to exclusive products
• Recurring subscription billing
• Different membership tiers
• Member-only content or perks
• Automatic member status based on whether their subscription is active

shopify.com

When I'd choose WooCommerce instead

If the membership itself is the core of the business, and the merch store is secondary, I'd seriously consider WooCommerce + WooCommerce Memberships + WooCommerce Subscriptions.

WooCommerce has a particularly tight native relationship between memberships and subscriptions: an active subscription can grant membership access, while pausing/cancelling the subscription can automatically pause/cancel the associated membership. WooCommerce WooCommerce

That gives you something like:

WordPress → WooCommerce → Memberships → Subscriptions → Merch

It's more flexible than Shopify, especially for a content-heavy membership site, but it generally requires more setup and ongoing technical maintenance.

woocommerce.com

Quick comparison

One important distinction: if by "membership system" you already mean something like Memberful, Patreon, MemberPress, Circle, Kajabi, etc., rather than wanting the ecommerce platform itself to run memberships, the answer can change substantially.

If you tell me which membership system you're planning to use (or describe what the subscription includes), I can recommend the exact stack and explain how I'd connect checkout → subscription → member status → merch discounts/access.

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/OMS/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you want a managed commerce suite or a composable commerce architecture. CIOPages

My shortlist would be:

Virto Commerce Guideflow## My recommendation by scenario

1. You have a strong engineering team and unique commerce requirements

Choose commercetools.

Typical signals:

• Multiple storefronts/apps/kiosks
• Need to swap CMS, search, promotions, checkout, or pricing independently
• Multiple brands sharing a commerce core
• Complex integrations where your architecture is a competitive advantage

This is the “build your commerce platform as a capability” approach. CIOPages

2. You are a manufacturer, distributor, or enterprise B2B company

Shortlist SAP Commerce Cloud and Adobe Commerce.

Especially if you have:

• Contract pricing
• Customer-specific catalogs
• Account hierarchies
• Quote workflows
• Regional product differences
• ERP-driven inventory and fulfillment

SAP Commerce is often considered when SAP ERP is central; Adobe is often favored when customization and flexibility are priorities. Shopify Itechguides

3. You want to reduce platform ownership burden

Look at Shopify Plus or Salesforce Commerce Cloud.

Choose Shopify Plus if:

• D2C is dominant
• You need speed
• Your workflows fit SaaS constraints

Choose Salesforce if:

• Salesforce CRM, Service Cloud, Marketing Cloud, or Data Cloud are already strategic systems. Space Dinosaurs

Architecture I would expect for your scale

For thousands of SKUs and many markets, I would usually separate responsibilities:

• Commerce engine: commercetools / SAP Commerce / Adobe Commerce / Salesforce Commerce
• PIM: product master data (e.g., Akeneo, Salsify, Syndigo)
• ERP: SAP, Oracle, Dynamics, NetSuite, etc.
• OMS: order orchestration and fulfillment
• Search: Algolia, Elasticsearch/OpenSearch, Coveo, etc.
• CMS: Contentful, Adobe Experience Manager, Sanity, etc.
• Integration layer: MuleSoft, Boomi, Workato, SAP Integration Suite, custom APIs

The commerce platform should not become the system of record for everything. That is where many enterprise implementations become difficult.

My default enterprise shortlist

If I were running a vendor evaluation for your description, I would start with:

1. commercetools — if your engineering organization is mature
2. SAP Commerce Cloud — if ERP and operational complexity dominate
3. Adobe Commerce — if customization depth is critical
4. Salesforce Commerce Cloud — if Salesforce is your enterprise backbone
5. Shopify Plus — if speed and operational simplicity outweigh deep customization

I would evaluate them against your actual complexity drivers:

• number of markets
• number of storefronts/brands
• SKU count and variants
• pricing models
• ERP/PIM/OMS landscape
• B2B vs B2C mix
• localization requirements
• internal engineering capacity

If you share your industry (B2B/B2C), ERP/PIM stack, number of markets, and whether you need headless, I can narrow this to a 2–3 platform recommendation.

For your specific profile—a multinational with localized catalogs plus distributed inventory and warehouse-aware fulfillment—I’d shortlist Adobe Commerce, commercetools, and Shopify Plus, with Adobe Commerce the strongest fit if sophisticated multi-warehouse logic is a first-class requirement.

My ranking

1. Adobe Commerce — best overall for your scenario

Adobe's Sources + Stocks model is unusually well aligned with a multinational operating model. A source can represent a warehouse, DC, store, or dropshipper, while stocks aggregate sources and can be associated with particular websites/regions. You can prioritize sources within a stock for fulfillment. Experience League Experience League

For example, you could model:

• US website → US stock → California DC → Texas DC → 3PL
• EU website → EU stock → Germany DC → Netherlands DC
• APAC website → APAC stock → Singapore DC → Australia DC

Meanwhile, Adobe's website/store/store-view hierarchy supports different catalogs, domains, languages, currencies, categories, and regional configurations within a common platform. Experience League Experience League

Why I'd pick it: the platform's inventory model is designed around exactly the distinction you're making between where something is sold and where it can be fulfilled.

2. commercetools — best if you're building a sophisticated composable stack

I'd seriously consider commercetools if you have a strong engineering organization and want the commerce platform to be the orchestration layer rather than the entire application.

Its Stores and Channels model lets you represent different commerce experiences while channels provide context for pricing and inventory. commercetools Documentation

The upside is enormous flexibility for rules such as:

Customer market + SKU + warehouse availability + shipping zone + promised delivery date → optimal fulfillment location.

The downside is that you'll generally be assembling more of the surrounding architecture yourself—OMS, PIM, localization, fulfillment orchestration, etc.

3. Shopify Plus — best if operational simplicity matters more

Shopify has become considerably stronger here. Its Markets model supports country/region-specific product availability, pricing, currencies, languages, and catalogs, while its location model tracks inventory independently at warehouses, stores, and fulfillment services. Shopify Help Center Shopify Help Center Shopify Help Center

It's particularly attractive if your warehouse logic is relatively conventional:

fulfill from the closest eligible location → otherwise another regional location → optionally split the order.

Shopify supports multiple locations and can split orders across locations. Shopify Help Center

I'd be more cautious if your requirements include complex allocation rules, ATP/available-to-promise calculations, regional inventory pools, cross-border sourcing, or sophisticated optimization.

The important architectural distinction

I'd evaluate these platforms against three separate models, rather than simply asking which has "multi-warehouse support":

1. Catalog availability

Market → Catalog → SKU eligibility

2. Inventory availability

Market → Inventory pool → Warehouse/DC → ATP

3. Fulfillment decision

Order → eligible warehouses → allocation rules → shipment(s)

Adobe Commerce is particularly compelling because its Stocks/Sources abstraction explicitly separates the inventory pool from the physical fulfillment locations. Experience League Experience League

My recommendation

If you're a large multinational and fulfillment complexity is strategically important, I'd go:

Adobe Commerce → commercetools → Shopify Plus

But there's an important caveat: if you already have a sophisticated OMS/WMS/ERP that owns allocation and fulfillment, the ranking can change dramatically. In that architecture, commercetools or Shopify Plus may be preferable because you don't necessarily want the commerce platform trying to become your fulfillment brain.

If you tell me roughly number of countries, number of warehouses, B2C vs B2B, ERP/OMS (SAP/Oracle/etc.), and whether you need headless, I can give you a much more concrete platform recommendation and reference architecture.

For a digital-first enterprise with a deliberate frontend/backend separation, my default recommendation would be commercetools.

It is particularly strong when “headless” is not just about replacing the storefront, but about building a long-lived, API-first commerce platform that can support multiple frontends, markets, channels, catalogs, pricing models, and downstream systems. commercetools positions itself as API-first, cloud-native and modular, with 550+ enterprises using the platform. Commercetools Commercetools

My enterprise shortlist

Why I'd pick commercetools for your description

The important distinction is headless vs. composable.

A conventional headless platform gives you:

Custom frontend → API → commerce backend

A composable platform gives you something closer to:

Multiple frontends → API layer → modular commerce capabilities → external services

That distinction becomes important at enterprise scale. commercetools explicitly supports separating capabilities into independently evolvable components rather than treating the commerce backend as one large application. Commercetools Commercetools

That makes it attractive if you're planning something like:

• Next.js/React web storefront
• Native mobile apps
• B2B portal
• Marketplaces or partner channels
• Multiple countries/currencies
• Multiple catalogs and price books
• External PIM
• External CMS
• Dedicated search/personalization
• ERP/OMS integration
• Event-driven integrations
• Future AI/agentic commerce channels

In other words, the commerce engine becomes a capability in your digital architecture rather than the application that owns the entire digital experience.

The big alternative: Shopify Plus

I'd seriously consider Shopify Plus + Hydrogen if your primary objective is scale with minimal platform operations, rather than maximum architectural independence.

Shopify's current headless stack provides the Storefront API plus Hydrogen/Oxygen. Shopify says the Storefront API is framework-agnostic, while Hydrogen/Oxygen provides its more opinionated React-based path. Shopify Shopify

That's a compelling proposition:

Custom frontend → Shopify APIs → managed commerce infrastructure

You get a tremendous amount of infrastructure and commerce functionality without your team having to operate the underlying commerce platform.

I'd choose Shopify over commercetools if:

• You're primarily DTC.
• Shopify's checkout/payment ecosystem is a major advantage.
• You want the smallest possible commerce operations team.
• Your differentiation is primarily in the experience layer, not custom commerce logic.
• Speed-to-market matters more than architectural purity.

Shopify's own current guidance also acknowledges that headless introduces additional development and operational complexity, so there is a real trade-off here. Shopify

Where Saleor fits

Saleor is the one I'd put on the shortlist if your engineering organization strongly prefers open source and GraphQL.

It is particularly interesting for enterprises with sophisticated B2B requirements and a willingness to own more of the platform. Recent industry comparisons highlight its GraphQL-first architecture, multi-channel capabilities and B2B-oriented modeling. Ribbsaeter Systems

The trade-off is that you're taking on more responsibility for the platform than you would with Shopify, and you don't get quite the same enterprise ecosystem as commercetools.

My recommendation

If I were designing the architecture for a large digital-first enterprise today, I'd rank them:

1. commercetools — if architectural flexibility and long-term composability are strategic requirements.

2. Shopify Plus + Hydrogen — if operational simplicity, ecosystem and speed are more important than deep backend composability.

3. Saleor — if you're an engineering-heavy organization that wants open source/API-first commerce and is prepared to own more infrastructure.

4. Salesforce Commerce Cloud — particularly compelling if Salesforce is already your enterprise customer/data ecosystem.

5. Adobe Commerce — strongest when Adobe and complex B2B requirements drive the decision, but I'd be reluctant to choose it solely because you want headless.

One architectural point I'd emphasize: don't choose the platform based primarily on frontend performance. With a genuinely decoupled architecture, your frontend can be Next.js, React, Astro, etc. independently of the commerce engine. The more consequential decision is whether the commerce backend's data model, APIs, extensibility, integration model, deployment model and operational boundaries will still fit your organization five years from now.

If you tell me your approximate GMV/order volume, B2B vs. B2C mix, number of countries, SKU count, existing ERP/PIM/CMS, and preferred frontend stack, I can narrow this to a commercetools vs. Shopify Plus vs. Saleor architecture recommendation and show what the target stack would look like.

If you mean an enterprise marketplace operator—where your platform owns the customer experience and you need to onboard hundreds/thousands of third-party vendors while normalizing millions of SKUs—my first choice would be Mirakl.

My CTO shortlist

Why Mirakl: its marketplace platform is purpose-built around seller onboarding, catalog normalization, seller portals, commissions and marketplace operations rather than treating marketplace capability as an add-on. Its current platform supports API/CSV/XML/EDI onboarding, automated catalog mapping/categorization, seller self-service and multi-region operation. Mirakl reports $14.6B GMV in 2025 and 118 orders/sec at peak. Mirakl

mirakl.com

VTEX is the stronger alternative if you also want the underlying commerce platform/storefront, rather than primarily a marketplace operating layer. Its marketplace stack includes seller registration/KYC, catalog integration, SKU matching, category mapping, order routing, split payments and commissions. VTEX

vtex.com

Spryker is worth serious consideration when your differentiation requires substantial customization. Its Merchant Portal lets third-party merchants manage profiles, products, offers, orders, returns and performance, but I'd put it behind Mirakl/VTEX for a marketplace operator whose primary requirement is rapid, large-scale seller onboarding. Spryker

The architecture question I'd use to decide

If your requirements are:

• 10k+ vendors
• millions of SKUs
• vendors arriving with wildly inconsistent catalogs
• automated taxonomy/attribute normalization
• self-service onboarding
• KYC/compliance
• seller-specific pricing/availability
• commissions and payouts
• APIs/EDI/SFTP rather than CSV-only integrations
• marketplace + dropship potentially sharing the same seller ecosystem

→ I'd shortlist Mirakl first. Its current offering explicitly combines marketplace and dropship on one platform, with a common catalog and vendor operational layer. Mirakl

If your requirement is instead "replace our commerce platform and get marketplace capabilities at the same time," I'd evaluate VTEX first.

One important CTO distinction: don't confuse vendor onboarding with catalog onboarding. The hard problem at scale is usually the latter—mapping arbitrary supplier schemas into your canonical product model, deduplicating products, validating attributes/media, and maintaining offer-level inventory/price separately from the product itself. Mirakl has a dedicated catalog platform for precisely that supplier-data problem. Mirakl

If you tell me your approximate vendor count, SKU count, B2B vs B2C, and whether you already have a commerce platform, I can give you a more opinionated Mirakl vs VTEX vs Spryker architecture recommendation, including where I'd keep PIM, OMS, payments, search, and the marketplace layer.

Spryker is worth serious consideration when your differentiation requires substantial customization. Its Merchant Portal lets third-party merchants manage profiles, products, offers, orders, returns and performance, but I'd put it behind Mirakl/VTEX for a marketplace operator whose primary requirement is rapid, large-scale seller onboarding.

The architecture question I'd use to decide

If your requirements are: