All answers

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 main priority is having the broadest and easiest-to-manage supplier ecosystem, I’d choose shopify.com.

My ranking for a multi-supplier dropshipping business

Why Shopify wins

Shopify has an unusually deep ecosystem of supplier and sourcing apps. Its own recommendations include Shopify Collective, Syncee, DropCommerce, Spocket, and others, while the App Store has integrations for AliExpress, Alibaba, CJ Dropshipping, print-on-demand suppliers, wholesale suppliers, and more. Shopify Help Center Shopify App Store

For example, DSers provides AliExpress/Alibaba/1688 connectivity, multi-supplier/agent management, supplier mapping, automatic inventory/price/order updates, and multi-channel management. Shopify App Store

That matters if your model is something like:

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations. BigCommerce BigCommerce

It also supports dropshipping tools such as Avasam and Spocket. BigCommerce

So I'd frame it this way:

• Shopify: best if you want to connect lots of existing suppliers quickly.
• BigCommerce: best if you eventually want to build sophisticated/custom supplier infrastructure.
• WooCommerce: best if you want maximum technical control and don't mind managing more infrastructure.

One important distinction

If by "supplier ecosystem" you mean you want to build a platform where hundreds/thousands of suppliers themselves connect to your store/network, rather than simply operating a dropshipping store using suppliers, my answer changes somewhat.

In that case, I'd look closely at BigCommerce vs Shopify, particularly their APIs, webhooks, catalog/variant handling, inventory synchronization, order routing, and multi-store capabilities. Those become more important than simply counting the number of dropshipping apps.

If you tell me whether you're planning (1) one dropshipping store with many suppliers, (2) multiple stores, or (3) a marketplace/platform connecting suppliers to retailers, I can give you a much more specific recommendation.

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations.

If the priority is tight monthly spend + solid core ecommerce features, I’d narrow it to WooCommerce, Shopify, and Square Online.

My pick: WooCommerce

WooCommerce itself has no monthly platform subscription or revenue share. You pay for hosting and whatever extensions you actually need; WooCommerce currently estimates hosting at roughly $25–$350/month for most stores, although a small, lean store can potentially operate below that range with inexpensive hosting. WooCommerce WooCommerce

It gives you the important basics—product/catalog management, orders, checkout, payments, shipping, coupons, inventory, and essentially unlimited products—without forcing you into a higher-tier plan as you grow. WooCommerce

When I'd choose Shopify instead

If your team doesn't want to manage WordPress, hosting, updates, security, and plugins, Shopify is probably worth the extra money. Its Basic plan is currently $39/month month-to-month or $29/month when billed annually, with a full-featured online store and unlimited products. Shopify Shopify

The tradeoff is that Shopify's app ecosystem can gradually increase your monthly bill, and third-party payment providers can incur additional transaction fees depending on the plan. Shopify Help Center

Bottom line

• Under ~$50/month and comfortable with some technical setup: WooCommerce
• Want predictable simplicity and minimal maintenance: Shopify Basic
• Already use Square for payments/POS: Square Online
• I'd avoid enterprise-oriented platforms at this stage; you're likely paying for capabilities you don't need.

If you tell me your approximate monthly budget (e.g. $25, $50, $100), number of products, and expected monthly orders, I can narrow this down to the cheapest option that still covers your required features.

WooCommerce itself has no monthly platform subscription or revenue share. You pay for hosting and whatever extensions you actually need; WooCommerce currently estimates hosting at roughly $25–$350/month for most stores, although a small, lean store can potentially operate below that range with inexpensive hosting. WooCommerce WooCommerce

It gives you the important basics—product/catalog management, orders, checkout, payments, shipping, coupons, inventory, and essentially unlimited products—without forcing you into a higher-tier plan as you grow. WooCommerce

When I'd choose Shopify instead

If your team doesn't want to manage WordPress, hosting, updates, security, and plugins, Shopify is probably worth the extra money. Its Basic plan is currently $39/month month-to-month or $29/month when billed annually, with a full-featured online store and unlimited products.

The tradeoff is that Shopify's app ecosystem can gradually increase your monthly bill, and third-party payment providers can incur additional transaction fees depending on the plan.

Bottom line

For a solo entrepreneur selling custom t-shirts who wants zero server management, I’d usually pick a hosted ecommerce platform + print-on-demand integration rather than building a site yourself.

My top picks:

My recommendation for most solo t-shirt entrepreneurs:

Start with Shopify + a print-on-demand provider.

A simple stack:

• Storefront: Shopify
• Printing/fulfillment: Printful or Printify
• Design: Canva, Illustrator, or similar
• Marketing: Instagram/TikTok/Pinterest + email list

This avoids:

• managing servers
• installing updates
• handling inventory
• packing orders
• maintaining payment security

Shopify’s POD integrations can automatically send orders to fulfillment partners, who print and ship the shirts after purchase. www.shopify.com

When I would choose something else:

• You already have a following → Etsy can be a fast way to test demand.
• You plan to sell hundreds of SKUs or wholesale later → BigCommerce may make sense.
• You only want a simple branded landing page with a few products → Wix or Squarespace could be enough.

For a first-time solo seller, I’d avoid:

• WooCommerce (unless you enjoy managing WordPress hosting/plugins)
• self-hosted ecommerce
• custom-built stores

The extra control usually isn’t worth the maintenance burden early on.

For a small B2B parts supplier with a handful of wholesale customers, customer-specific pricing should be one of the deciding factors. You don't necessarily need a heavyweight enterprise platform.

My shortlist

1. BigCommerce — probably my first choice

BigCommerce is particularly well suited to your situation. Its B2B functionality lets you create price lists that can be assigned to individual wholesale accounts or customer groups, including prices down to the individual SKU. BigCommerce BigCommerce

For example:

• Customer A → Part #123 = $18.50
• Customer B → Part #123 = $21.00
• Customer C → Part #123 = $16.75
• Everyone else → $29.95

You can also have customer-specific catalogs, payment methods, credit limits, reordering, etc. BigCommerce BigCommerce

Why I'd lean this way: it handles the awkward B2B stuff without requiring you to bolt together a bunch of plugins.

bigcommerce.com

2. WooCommerce — excellent if keeping costs down matters

WooCommerce can do extremely flexible customer-specific pricing, but you'll generally use a B2B extension/plugin rather than getting everything from the core platform.

Its B2B pricing functionality supports custom prices for customer groups, quantity pricing, tax exemptions, product/category rules, and hiding prices from non-approved customers. WooCommerce

There are also extensions that support pricing for individual customers, rather than just broad customer groups. WooCommerce

I'd choose WooCommerce if you already use WordPress or have someone comfortable maintaining it.

woocommerce.com

3. Shopify — easiest to operate, but I'd scrutinize the pricing model

Shopify now has native B2B catalogs and pricing. You can assign catalogs to companies/company locations and specify products and prices for those customers. Shopify Plus removes the catalog limits and allows direct assignment to companies and locations. Shopify Help Center

The catch is that your use case sounds more like negotiated account-level pricing than conventional wholesale tiers. I'd therefore make Shopify prove that its current catalog setup handles your exact pricing matrix before choosing it.

4. Adobe Commerce — great, but likely too much

Adobe Commerce has very sophisticated customer-group and shared-catalog pricing. Its B2B functionality specifically supports custom pricing for different companies. Experience League

But for "we have a few wholesale customers and need their negotiated prices online," I'd consider it excessive unless you have unusually complex ERP, catalog, workflow, or account requirements.

What I'd choose for your business

BigCommerce if you're starting from scratch.

WooCommerce if you already have WordPress or want maximum flexibility at relatively low cost.

Shopify if ease of administration is more important than having the most natural B2B pricing architecture.

The key question I'd use to narrow it down is how you currently maintain prices. If you have something like a spreadsheet with 5–20 wholesale customers and each customer has hundreds/thousands of negotiated part prices, I can compare BigCommerce vs WooCommerce vs Shopify specifically for importing/managing those customer-specific price lists. That's where the differences become much more important.

For a tiny team selling internationally, I’d pick Shopify—specifically Shopify with Markets + Managed Markets.

My ranking

1. Shopify — simplest overall

• Markets lets you set up different countries/regions with local currencies and pricing. Shopify Help Center Shopify Help Center
• Managed Markets is the big advantage for a small team: it can handle international tax registration/remittance, duties, local payment methods, customs, and localization through its merchant-of-record arrangement. Shopify Help Center
• It can also give customers duties/taxes-inclusive pricing, reducing surprise charges at delivery. Shopify Changelog
• The tradeoff is cost: Managed Markets charges a 3.5% transaction fee on Basic/Grow/Advanced, plus 1.5% currency conversion, on top of Shopify Payments fees. Shopify Help Center
• Wix — simplest if you're mostly a website business

• Wix supports local-currency display and international payments, and integrates with Avalara for automated tax calculations. wix.com
• I'd choose it if ecommerce is relatively secondary to the website/brand experience.
• BigCommerce — powerful, but I'd avoid it for a tiny team unless you need its flexibility

• It can pair with Stripe Tax to automate VAT/GST/sales-tax calculations internationally. BigCommerce
• But you're likely to end up making more decisions about integrations and configuration than you would with Shopify.

The important distinction

There's a difference between "calculate the right tax at checkout" and "take international tax compliance off our plate."

If you want the latter, Shopify Managed Markets is the compelling option. Shopify describes it as handling the international merchant-of-record responsibilities, including tax registration/remittance and duties. Shopify Help Center

So for a 2–5 person team, my default would be:

Shopify → Shopify Payments → Markets → Managed Markets for countries where you don't want to manage local tax compliance yourself.

If you tell me what you're selling, where your company is based, and your top 3–5 countries, I can tell you whether Managed Markets is actually worth the fees for your situation.

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 bigcartel.com.

My pick: Big Cartel

• $0/month on its Gold plan.
• The free plan lets you list up to 5 products, accept card/PayPal payments, and use a customizable storefront. Big Cartel Big Cartel
• It’s specifically designed around artists, makers, and independent sellers, so it fits handmade goods particularly well. Big Cartel
• Big Cartel says it charges 0% platform transaction fees; you'll still have payment-processing fees when someone buys. Big Cartel
• You can upgrade to $15/month if you outgrow the five-product limit. Big Cartel

Another excellent $0 option: Square

If you expect to sell in person at craft fairs, markets, or pop-ups, I'd seriously consider squareup.com instead. Its Free plan has no monthly subscription or startup cost, and you can use Square for both your online store and in-person payments. You pay processing fees when you make sales. Square Square

Simple rule:

• 🧵 Mostly handmade products + small catalog → Big Cartel
• 🛍️ Online + craft fairs/pop-ups → Square
• 📈 Lots of products and more advanced ecommerce later → consider Shopify once sales justify it

If you're starting with only 3–5 products, I'd spend $0 on the store initially and put your limited budget into good product photos, packaging, and getting your first customers.

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 farmers’ co-op, I’d prioritize software that can handle multiple vendors, shared storefronts, vendor payouts, inventory by producer, pickup/delivery workflows, and low operating costs. The best choice depends on whether you are mainly selling CSA boxes, farmers-market style retail, or wholesale/food hub orders. NC State Extension Young Farmers Coalition

Here are some low-budget options worth considering:

My shortlist for a low-budget farmers’ co-op

1. Start with Open Food Network if your mission is cooperative/local food infrastructure and you want vendors to share one marketplace. Local Food
2. Choose Local Line if you want something easier for farmers to adopt without much technical work. Young Farmers Coalition
3. Use Shopify + a marketplace app if you already have someone comfortable managing ecommerce and you want maximum customization. Shopify App Store

A few questions would change the recommendation:

• How many vendors do you expect (5, 20, 100+)?
• Are customers buying individual items (tomatoes, eggs, bread) or weekly CSA boxes?
• Do vendors need to get paid automatically after each order?
• Do you need delivery routing, or just pickup at one location?

For a 10-person startup building a high-traffic headless storefront, I would narrow the field pretty aggressively. You probably do not want a traditional monolith like Magento/WooCommerce unless you have a very specific reason. For a greenfield headless build, the strongest open-source candidates today are Medusa, Saleor, and Vendure. Vendure

My default recommendation for your team:

1. Pick Medusa if you are a TypeScript/React shop

Best fit: 10–30 person product teams building a custom DTC/B2B storefront that need speed and flexibility.

Why I’d lean here:

• TypeScript/Node stack pairs naturally with a Next.js storefront.
• Modular architecture: you can replace pieces rather than fork the whole platform.
• Good developer experience for a small team.
• MIT license is startup-friendly.
• Easier hiring: many frontend/full-stack engineers can contribute. Vendure Build With Matija

Tradeoffs:

• You are still building a lot: merchandising UX, CMS workflows, search, analytics, personalization, etc.
• Some enterprise commerce features may require custom modules.

A common architecture would be:

Next.js storefront
        |
        v
Medusa API
        |
  ----------------
  |      |       |
Postgres Redis  Workers
        |
Stripe / Adyen / Tax / Shipping APIs

For a startup, I like this because your team owns the customer experience instead of fighting a legacy admin system.

2. Pick Saleor if you have complex commerce requirements

Best fit: marketplaces, international commerce, B2B, multi-channel.

Strengths:

• GraphQL-first API.
• Strong catalog/channel concepts.
• Mature handling of things like warehouses, pricing, and complex commerce models. Designodin

Tradeoffs:

• Python/Django backend means less overlap if your team is all TypeScript.
• More opinionated architecture.
• Operationally heavier for a small team.

I would choose Saleor over Medusa if your roadmap includes things like:

• multiple regions/currencies from day one
• complicated pricing rules
• wholesale accounts
• multiple inventory locations
• marketplace-style workflows

3. Pick Vendure if your team loves NestJS

Best fit: TypeScript teams wanting a strongly structured backend.

Strengths:

• TypeScript end-to-end.
• NestJS architecture feels familiar to backend engineers.
• Good plugin model.
• Strong fit for custom commerce applications. OpenReplay Blog

Tradeoffs:

• Smaller ecosystem/community than Medusa.
• You may build more integrations yourself.

What I would avoid for your situation

Magento / Adobe Commerce

Powerful, but a 10-person startup usually spends too much time operating and customizing it.

WooCommerce headless

Great ecosystem, but the underlying model is still WordPress-centric. It is usually not what I would start with for a high-traffic, API-first storefront.

Building from scratch

Tempting, but commerce has thousands of edge cases:

• tax
• refunds
• inventory race conditions
• promotions
• carts
• payment retries
• fulfillment states

You want to own your differentiation, not reinvent checkout state machines.

My shortlist for your startup

For a typical 10-person startup targeting high traffic, I would start with Medusa + Next.js + PostgreSQL + Redis + a managed search layer (Algolia/OpenSearch/Elastic) and keep the commerce core replaceable.

The bigger scaling risks usually won't be the commerce engine itself; they will be:

• product search
• inventory consistency
• checkout/payment reliability
• caching strategy
• content delivery
• observability

Those deserve architectural attention early. OSSAlt

A few details would change my recommendation:

1. Is this DTC, B2B, or a marketplace?
2. What stack is your team strongest in (TypeScript, Python, PHP)?
3. Expected scale: 10k, 100k, or millions of SKUs/orders?

• tax
• refunds
• inventory race conditions
• promotions
• carts
• payment retries
• fulfillment states

You want to own your differentiation, not reinvent checkout state machines.

My shortlist for your startup

For a typical 10-person startup targeting high traffic, I would start with Medusa + Next.js + PostgreSQL + Redis + a managed search layer (Algolia/OpenSearch/Elastic) and keep the commerce core replaceable.

The bigger scaling risks usually won't be the commerce engine itself; they will be:

• product search
• inventory consistency
• checkout/payment reliability
• caching strategy
• content delivery
• observability

Those deserve architectural attention early.

A few details would change my recommendation:

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 multi-vendor marketplace capability + total data ownership are your top requirements, I would prioritize self-hosted open-source platforms over SaaS marketplaces. The best fit depends on your business model, engineering capacity, and scale. Mercur Twosided

Shortlist

My recommendation by scenario

1. You want maximum control and long-term ownership

Choose Spree Commerce or Bagisto.

• Your database stays on your infrastructure.
• You control customer, vendor, order, and transaction data.
• You avoid marketplace SaaS lock-in.
• You can modify the code and workflows.

Spree specifically positions its marketplace capabilities around vendor dashboards, multi-vendor checkout, commissions, APIs, and self-hosted ownership. Spree Commerce

2. You need to launch quickly but still own the platform

Choose CS-Cart Multi-Vendor.

Good if you need:

• vendor registration
• seller dashboards
• commissions
• product approvals
• shipping workflows
• marketplace operations without building everything

The tradeoff is that it is less developer-centric than a pure open-source framework. Twosided Jujubesy

3. You are building a unique marketplace business model

Choose a composable/headless approach:

• Backend: Spree, Medusa, Bagisto, or Magento
• Frontend: React/Next.js/Vue
• Payments: your own processor integrations
• Infrastructure: your cloud account
• Data warehouse: your own stack

This gives you the strongest ownership and flexibility.

Platforms I would be cautious about for “total data ownership”

• Shopify marketplace apps — convenient, but you remain dependent on Shopify’s ecosystem.
• Sharetribe — excellent for validation and service marketplaces, but hosted SaaS means less infrastructure ownership.
• Mirakl-type enterprise marketplace layers — powerful, but usually introduce vendor dependency and licensing costs. Mercur

My default recommendation

For a company serious about owning its marketplace:

Tier 1 choice: Spree Commerce
Tier 2 choice: Bagisto
Fastest operational launch: CS-Cart

A few questions would change the recommendation:

1. Are you building a B2C marketplace (Amazon-style), B2B marketplace, or services marketplace?
2. How many vendors do you expect (100, 10,000, 100,000+)?
3. Do you have an internal engineering team (PHP/Laravel, Node.js, Java, etc.)?
4. Do you need built-in vendor payouts/split payments?

For that profile, WooCommerce is probably the easiest self-hosted option to maintain.

My ranking

1. WooCommerce — easiest overall

• Familiar WordPress admin interface.
• Huge ecosystem, so finding themes, payment integrations, shipping tools, and people who can help is relatively easy.
• For a small, low-traffic catalog, it doesn't require much server horsepower; WooCommerce's own guidance gives a simple baseline of 1 vCPU and 2 GB RAM. The WooCommerce Developer Blog
• The downside is that you're maintaining WordPress + WooCommerce + themes + plugins + PHP, so updates and backups still matter. WooCommerce specifically recommends backups and staging before updates. WooCommerce WooCommerce
• PrestaShop — good dedicated-store alternative

• More purpose-built than WooCommerce.
• A reasonable choice if you don't want WordPress at all.
• I'd still put it behind WooCommerce for a non-technical owner because the WordPress/WooCommerce ecosystem tends to make finding help and extensions easier.
• OpenCart — lightweight, but less attractive today

• Relatively straightforward and lightweight.
• Smaller ecosystem and less mainstream than WooCommerce, which matters when the owner eventually needs someone to troubleshoot something.
• Shopware — avoid for this use case

• Powerful, but it's aimed at substantially more sophisticated deployments.
• Shopware itself says its self-hosted version is appropriate when you have an expert developer team; its cloud version is what it recommends when you want infrastructure and updates handled for you. Shopware
• Its current self-hosted requirements also involve things such as PHP 8.2–8.4, Node.js 20+, and MySQL/MariaDB configuration. Shopware Documentation

The important caveat

If by self-hosted you mean "I want the store software on my own VPS and the owner shouldn't need to understand Linux, databases, SSL, backups, etc.", then I'd actually choose:

WordPress + WooCommerce + a managed WordPress host, rather than installing WooCommerce manually on a VPS.

That's still self-hosted in the sense that you control the application/site and can migrate it, but the hosting company handles much of the unpleasant server maintenance. WooCommerce itself emphasizes that the host affects security, stability, and performance. WooCommerce

For a low-traffic boutique store with a non-technical owner, my sweet spot would therefore be:

WooCommerce + a reputable managed WordPress host + a small number of well-maintained plugins.

The last part is important: plugin sprawl is probably a bigger maintenance risk than WooCommerce itself. Keep the installation boring and conventional, and it can be quite easy to operate.

For a SaaS company selling licenses (rather than physical goods), I would prioritize license management, subscription lifecycle handling, entitlements, webhooks, and API integration over a traditional shopping cart. The best fit depends on whether you want the ecommerce system to own billing or simply be a storefront around an existing billing system like Stripe Billing.

Here are the strongest self-hosted options:

My shortlist for a small SaaS license store

1. ChargePanda — closest out-of-the-box fit

ChargePanda is specifically aimed at selling digital products, software licenses, and SaaS plans. It includes subscription plans, trials, customer portals, license generation, activation controls, and entitlement APIs. ChargePanda ChargePanda

A typical flow would be:

Customer checkout
        ↓
Payment processor (Stripe/PayPal)
        ↓
ChargePanda subscription created
        ↓
License generated
        ↓
Your SaaS checks entitlement API
        ↓
Features enabled/disabled

This avoids building:

• license key generation
• renewal handling
• subscription status syncing
• customer self-service billing

ChargePanda#### 2. WooCommerce if you already use WordPress

WooCommerce works well if your store is mostly a website selling plans. WooCommerce has subscription capabilities and APIs, but you will likely need additional plugins or custom code for SaaS entitlements and provisioning. The WooCommerce Developer Blog

Good when:

• your marketing site is WordPress
• you want coupons, content marketing, SEO
• your SaaS provisioning is already custom

Less ideal when:

• the license itself is the product
• you need complex plan gating

3. Spree Commerce for a custom engineering approach

Spree Commerce is a strong option if you want a fully custom commerce layer. It supports digital products and subscriptions, but you should expect to build more of the SaaS-specific pieces yourself. Spree Commerce

Architecture I would choose for a small SaaS

For most SaaS companies, I would avoid making the ecommerce platform the source of truth. A cleaner architecture is:

Storefront
   |
Checkout
   |
Stripe Billing / payment provider
   |
Subscription events (webhooks)
   |
Your SaaS entitlement service
   |
Application feature access

The store handles:

• pricing pages
• checkout
• invoices
• coupons

Your SaaS handles:

• who has access
• feature limits
• seats/users
• usage quotas

Recommendation

For a small SaaS selling licenses today:

1. Fastest launch: ChargePanda
2. Already on WordPress: WooCommerce + subscription/license extensions
3. Building a serious SaaS platform: custom frontend + Stripe Billing + your own entitlement service
4. Need a highly customizable commerce backend: Spree Commerce

I would not start with a general ecommerce platform like Magento/OpenCart unless you also plan to sell a large catalog of non-SaaS products. For software licenses, the hard part is not the cart — it is entitlement management.

If strong security/compliance for payments and customer data is the priority, I’d choose Magento Open Source (Adobe Commerce’s open-source edition) over WooCommerce or PrestaShop—provided you have a capable engineering/security team.

My ranking

*These can be excellent security architectures, but they put substantially more responsibility on your engineering team.

Why I'd pick Magento

Magento has a relatively mature security model for a self-hosted open-source platform: 2FA, CAPTCHA/reCAPTCHA, security scanning, security advisories and a formal security-patch process are documented by Adobe. Experience League Experience League

It's also designed for more complex enterprise commerce requirements than WooCommerce. The important caveat is that Magento Open Source itself does not make you PCI compliant. Adobe explicitly notes that merchants remain responsible for their PCI obligations and the security of their implementation. Experience League

And you need to take patching seriously: Adobe has continued issuing security updates for Magento Open Source in 2026, including fixes for issues capable of arbitrary code execution and privilege escalation. Adobe Help Center

The architecture matters more than the platform

For a security-sensitive payment system, I would design it so that:

• The ecommerce application never stores raw card numbers.
• Payments go through a PCI-compliant processor using hosted fields/tokenization or an appropriately scoped hosted checkout.
• Customer PII is encrypted in transit and protected at rest.
• Admin access requires MFA, least privilege and preferably SSO.
• Production access is tightly restricted and audited.
• WAF + CDN + DDoS protection sit in front of the storefront.
• Dependencies, extensions and OS packages are continuously vulnerability-scanned.
• Security patches are tested and deployed rapidly.
• Centralized immutable logging/SIEM captures authentication, privilege changes, payment events and sensitive-data access.
• Backups are encrypted, isolated and regularly restore-tested.
• You maintain documented retention/deletion procedures for customer data.
• PCI DSS, GDPR/CCPA and your organization's security policies are treated as separate compliance requirements, not something the ecommerce platform magically provides.

One important alternative

If your organization doesn't specifically require self-hosted open source, I'd seriously consider Adobe Commerce Cloud rather than operating Magento Open Source yourself. Adobe currently documents SOC 2 Type II, ISO 27001 and PCI DSS coverage for its Commerce cloud infrastructure, while maintaining a shared-responsibility model for your application, code, extensions and data. Experience League Experience League

That can remove a substantial amount of infrastructure/security operational burden.

Bottom line: For a genuinely security- and compliance-sensitive organization that requires open source, I'd shortlist Magento Open Source first. If minimizing operational compliance burden matters more than having the platform itself be open source, Adobe Commerce Cloud deserves serious consideration. WooCommerce is perfectly capable of a secure deployment, but its security responsibility extends across WordPress, WooCommerce, themes, plugins and hosting, which creates a larger dependency surface; WooCommerce itself explicitly says the store owner remains responsible for PCI compliance. WooCommerce WooCommerce

If you tell me your company size, expected transaction volume, cloud (AWS/Azure/GCP), and compliance requirements (PCI DSS, SOC 2, HIPAA, GDPR, etc.), I can narrow this down to a specific architecture and platform choice.

The architecture matters more than the platform

If ERP + shipping integration flexibility is the priority for a growing store, I’d shortlist Shopware and Medusa, with Shopware as the safer overall choice and Medusa as the better developer-first choice.

My pick: Shopware 6

Shopware 6 is probably the best balance of open-source flexibility and pre-existing business integrations.

Its API-first architecture exposes the platform to ERP, PIM, WMS, CRM, and external services, while its extension ecosystem has ready-made connectors. Shopware specifically documents integrations with systems such as SAP, Microsoft Dynamics, Xentral, weclapp, and Pickware. Shopware Shopware

Its ecosystem is particularly attractive for shipping/fulfillment because there are extensions rather than requiring you to build every integration yourself. The Shopware extension store currently lists numerous ERP connectors, including Odoo, SAP Business One, and PlentyONE. Shopware Store Shopware Store

shopware.com

When I'd choose Medusa instead

Medusa is extremely compelling if you have a strong development team and expect your ERP/fulfillment architecture to be highly customized.

Medusa treats integrations as modular components and explicitly supports building ERP integrations. Its documentation includes an ERP integration recipe and an Odoo-specific example. Medusa Documentation Medusa Documentation Medusa Documentation

It also has a fulfillment-provider abstraction, with integrations such as ShipStation, plus community integrations for services including Sendcloud and DHL. Medusa Documentation Medusa

The important distinction is:

• Shopware: "There is probably already a connector for what I need."
• Medusa: "I can build exactly the integration architecture I want."

For a growing retailer that wants to minimize engineering effort, I'd favor Shopware.

For a company where the commerce platform itself is a custom software product, I'd favor Medusa.

One caveat: WooCommerce

WooCommerce deserves consideration because its ecosystem is enormous. If your ERP and shipping providers already have mature WooCommerce connectors, it can actually be the lowest-effort option.

But I wouldn't choose it because you want a sophisticated ERP-centric architecture. As the operation grows, the plugin-heavy WordPress architecture can become harder to govern than a purpose-built commerce platform.

My ranking for your use case

1. Shopware 6 — best overall integration ecosystem + scalability
2. Medusa — best if you have developers and want maximum architectural control
3. WooCommerce — best if your specific ERP/shipping vendors already have excellent plugins
4. Saleor — excellent API/headless architecture, but generally more custom integration work
5. Sylius — superb for bespoke builds, but more of a framework than an out-of-the-box merchant platform

If you tell me which ERP you're using (e.g. NetSuite, SAP, Odoo, Dynamics, Acumatica) and which shipping providers (UPS/FedEx/USPS, ShipStation, ShipBob, EasyPost, etc.), I can narrow this down considerably.

WooCommerce deserves consideration because its ecosystem is enormous. If your ERP and shipping providers already have mature WooCommerce connectors, it can actually be the lowest-effort option.

But I wouldn't choose it because you want a sophisticated ERP-centric architecture. As the operation grows, the plugin-heavy WordPress architecture can become harder to govern than a purpose-built commerce platform.

My ranking for your use case

When I'd choose Medusa instead

Medusa is extremely compelling if you have a strong development team and expect your ERP/fulfillment architecture to be highly customized.

Medusa treats integrations as modular components and explicitly supports building ERP integrations. Its documentation includes an ERP integration recipe and an Odoo-specific example.

It also has a fulfillment-provider abstraction, with integrations such as ShipStation, plus community integrations for services including Sendcloud and DHL.

The important distinction is:

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.

Yes. For an agency model—multiple client-owned digital-product stores, separate client logins, and your agency operating everything behind the scenes—I’d narrow it to a few options.

Best fits

Lemon Squeezy is particularly interesting for your use case because one account can manage multiple independent stores, each with its own products, domains, customers, billing and payouts. It's also purpose-built for digital products and acts as the merchant of record, handling sales tax/VAT. Lemon Squeezy Docs Lemon Squeezy Lemon Squeezy Docs

However, if by white-label you mean:

"Our agency has one master dashboard → Client A sees only Client A's store → Client B sees only Client B's store → clients log into a branded portal → we control the infrastructure"

then Lemon Squeezy isn't quite a full agency/white-label SaaS platform. Its multi-store functionality is primarily an account/store management feature.

Shopify is the more flexible architecture

Shopify gives you much stronger client/staff permissions and an enormous app/API ecosystem. You can create one Shopify store per client and have your agency retain partner/admin access while giving clients restricted staff access.

There's also now an interesting third-party option, Plectix Multi-Store Hub, which specifically markets agency workspaces, isolated white-labeled client views, multi-store management, and a unified dashboard across Shopify stores. Shopify App Store Shopify App Store

apps.shopify.com

If you're building your own agency platform

I'd seriously consider this architecture:

Your Agency SaaS
→ Client A workspace
→ Client B workspace
→ Client C workspace
→ each connected to its own Lemon Squeezy or Shopify store
→ your agency owns/administers the infrastructure
→ client gets a restricted branded dashboard

That gives you much more control over client isolation, recurring agency fees, branding, domains, permissions, analytics and onboarding than trying to force a creator platform into an agency model.

One notable advantage of Lemon Squeezy is that you can have many stores under the same account, which maps nicely to the "one client = one store" model. Lemon Squeezy Docs

My ranking for your specific business:

1. Shopify + custom/agency management layer — best if you want maximum control and scalability.
2. Lemon Squeezy — best if the priority is digital products + simple deployment + merchant-of-record.
3. Whop/white-label infrastructure — worth investigating if you want the platform itself to be white-labeled.
4. Sellfy/Podia — great for individual creators, but I'd avoid them for a multi-client agency architecture. Sellfy, for example, explicitly says one storefront per account and doesn't support multiple users on an account. Sellfy Help Center

If you tell me (1) whether clients need their own login, (2) whether they need to see sales/orders/customers, and (3) whether your agency wants to own the Stripe/payment accounts, I can narrow this down to the 2–3 platforms that actually fit your SaaS/agency model.

Lemon Squeezy is particularly interesting for your use case because one account can manage multiple independent stores, each with its own products, domains, customers, billing and payouts. It's also purpose-built for digital products and acts as the merchant of record, handling sales tax/VAT. Lemon Squeezy Docs Lemon Squeezy Lemon Squeezy Docs

However, if by white-label you mean:

"Our agency has one master dashboard → Client A sees only Client A's store → Client B sees only Client B's store → clients log into a branded portal → we control the infrastructure"

then Lemon Squeezy isn't quite a full agency/white-label SaaS platform. Its multi-store functionality is primarily an account/store management feature.

Shopify is the more flexible architecture

Shopify gives you much stronger client/staff permissions and an enormous app/API ecosystem. You can create one Shopify store per client and have your agency retain partner/admin access while giving clients restricted staff access.

There's also now an interesting third-party option, Plectix Multi-Store Hub, which specifically markets agency workspaces, isolated white-labeled client views, multi-store management, and a unified dashboard across Shopify stores. Shopify App Store Shopify App Store

apps.shopify.com

If you're building your own agency platform

I'd seriously consider this architecture:

Your Agency SaaS
→ Client A workspace
→ Client B workspace
→ Client C workspace
→ each connected to its own Lemon Squeezy or Shopify store
→ your agency owns/administers the infrastructure
→ client gets a restricted branded dashboard

That gives you much more control over client isolation, recurring agency fees, branding, domains, permissions, analytics and onboarding than trying to force a creator platform into an agency model.

One notable advantage of Lemon Squeezy is that you can have many stores under the same account, which maps nicely to the "one client = one store" model.

My ranking for your specific business:

Yes. For a photographer selling high-res digital downloads, the two strongest fits I’d look at are Pic-Time and Pixieset.

Pic-Time — my first choice

pic-time.com

Pic-Time is particularly well matched to what you're describing. You can sell individual high-resolution images, full galleries, or packages. It also lets you define custom resolutions, so you could offer something like:

• Web/social — 2048px
• High-res — 6000px / original
• Custom commercial resolution
• Full-gallery download

It supports volume/tiered pricing and packages as well. Pic-Time Help Center Pic-Time Help Center Pic-Time Help Center

For previews, Pic-Time's watermark system can apply watermarks to gallery and shop/product-preview images while keeping the purchased high-resolution files clean. Its burned watermark option permanently embeds the watermark into the low-resolution preview. Pic-Time Help Center Pic-Time Help Center

That's a very good match if your priority is: beautiful preview → protected preview → customer purchases → clean full-resolution file.

Pixieset — excellent alternative

pixieset.com

Pixieset also checks essentially all of your boxes. Its Store integrates directly with galleries, and its Personalized Product Preview can use the customer's selected image in product previews. Pixieset Website Help Center

You can sell individual downloads or full-gallery downloads and control the resolution. Pixieset Website Help Center

Its watermarking is also nicely designed for this workflow: watermarks appear on displayed/gallery images, while original/high-resolution downloads are delivered without the watermark. You can optionally retain watermarks on web-sized downloads. Pixieset Website Help Center Pixieset Website Help Center

Which I'd pick

I'd choose Pic-Time if you're primarily building a photography storefront. Its custom-resolution and package capabilities are especially strong for selling the same photograph at different licensing/use levels.

I'd choose Pixieset if you want an all-in-one photographer business platform encompassing galleries, website, store, and studio-management tools. Pixieset

One important distinction: neither platform is really designed around watermarking the actual purchased high-res file—the watermark is primarily protection for the preview. That's generally what you want for a digital-download store anyway. Pic-Time explicitly says high-res downloads aren't watermarked, and Pixieset does the same. Pic-Time Help Center Pixieset Website Help Center

If you're selling fine-art/stock-style individual images rather than client galleries, I can also compare these against Shopify + a digital-download app, WooCommerce, SmugMug, and Zenfolio specifically for watermarked previews + multiple downloadable resolutions + automated delivery.

For your use case, I’d strongly consider an all-in-one course platform rather than a generic ecommerce store. You need three things tightly connected: course access, downloadable resources, and automated certificates.

My top picks

🥇 Best fit: Podia

For the exact combination you described, Podia is probably the cleanest choice.

A Podia course can contain video, text, quizzes, and downloadable files directly inside lessons. Separately, you can sell digital-download products, so you can distribute standalone workbooks, templates, PDFs, ZIPs, etc. Podia Help Center Podia

Most importantly, certificates are native to the course: they're automatically issued when the learner completes the course, can be branded/customized, and students can download them as PDFs. Podia Help Center Podia Help Center

It also lets you bundle courses and downloads together, which is particularly useful if your offer looks something like:

Course + Resource Library + Completion Certificate

You can sell that as one purchase while keeping the learning experience and resources under the same customer account. Podia

podia.com

🥈 Thinkific if the course experience is the priority

I'd choose Thinkific instead if you're building a more substantial education business and expect to need more sophisticated learning-management features.

Thinkific supports digital downloads alongside courses, and its certificate system automatically issues certificates when students reach 100% completion. Students can download their personalized certificates as PDFs. Thinkific Thinkific Support

thinkific.com

What I'd choose

• Small/medium launch, want simplicity: Podia
• Growing education business, deeper LMS needs: Thinkific
• Marketing funnels, email automation, memberships are central: Kajabi
• Want a straightforward course-selling setup: Teachable

For your specific description—online course + downloadable resources + certificates—I'd start with Podia, unless you already know you'll need advanced LMS functionality.

If you tell me your expected number of students, price of the course, whether it's one-time or subscription, and whether you need quizzes/assessments, I can narrow this down to the best platform and plan.

A Podia course can contain video, text, quizzes, and downloadable files directly inside lessons. Separately, you can sell digital-download products, so you can distribute standalone workbooks, templates, PDFs, ZIPs, etc. Podia Help Center Podia

Most importantly, certificates are native to the course: they're automatically issued when the learner completes the course, can be branded/customized, and students can download them as PDFs. Podia Help Center Podia Help Center

It also lets you bundle courses and downloads together, which is particularly useful if your offer looks something like:

Course + Resource Library + Completion Certificate

You can sell that as one purchase while keeping the learning experience and resources under the same customer account. Podia

podia.com

🥈 Thinkific if the course experience is the priority

I'd choose Thinkific instead if you're building a more substantial education business and expect to need more sophisticated learning-management features.

Thinkific supports digital downloads alongside courses, and its certificate system automatically issues certificates when students reach 100% completion. Students can download their personalized certificates as PDFs.

For a small shop owner who sells both digital products and occasional physical goods, the best fit is usually a platform that treats digital downloads as a normal product type while still handling inventory, shipping, taxes, and order management. Fit Small Business Hostinger

My shortlist:

1. shopify.com — Best overall for a mixed store

Best if: you want one system that can grow with you.

Why it works well:

• Sell physical items with inventory, variants, shipping rates, and fulfillment.
• Sell digital files (ebooks, templates, downloads, courses) using apps or integrations.
• Strong checkout, payment processing, marketing tools, and customer management.
• Good if you may eventually sell through social media, marketplaces, or in person. Fit Small Business

Downside: monthly cost plus possible app costs can add up, especially for advanced digital-product features.

My pick for: a handmade goods shop, creator brand, boutique, or small business that expects to grow.

2. squareup.com — Best if you also sell in person

Best if: you run a market stall, pop-up, retail counter, or physical shop.

Why it works well:

• Syncs online sales with Square’s point-of-sale ecosystem.
• Good inventory management for physical products.
• Simple setup for occasional online selling. Fit Small Business TechRadar

Downside: digital products are not its strongest area compared with Shopify or creator-focused platforms.

My pick for: a local shop that mostly sells physical goods but occasionally adds digital items.

3. woocommerce.com — Best if you already use WordPress

Best if: you want maximum control.

Why it works well:

• Handles both physical and downloadable products.
• Huge ecosystem of plugins for shipping, memberships, subscriptions, and digital delivery.
• You own the website rather than renting a hosted store. Hostinger

Downside: more setup and maintenance than Shopify.

My pick for: someone comfortable managing a website or already invested in WordPress.

4. wix.com — Best for a simple, attractive storefront

Best if: your store is small and brand/design-focused.

Why it works well:

• Easy drag-and-drop website building.
• Supports physical and digital products.
• Good for artists, makers, portfolios, and small catalogs. TechRadar

Downside: may feel limiting as your catalog and operations become more complex.

My recommendation by situation

• Mostly digital + some physical shipping: Shopify
• Mostly physical + occasional digital downloads: Square Online or Shopify
• Already have WordPress: WooCommerce
• Small creative brand with a beautiful website focus: Wix or Shopify

For a typical small shop owner who wants the least hassle, I’d start with Shopify because it handles the “mixed inventory” problem cleanly and gives you room to grow. Fit Small Business

If you tell me what your digital products are (downloads, courses, memberships, templates, etc.) and roughly how many physical items you sell, I can narrow it down further.

For digital downloads specifically, I’d put Medusa at the top of your shortlist.

My ranking

1. Medusa — best fit for your use case

• TypeScript/Node.js and very API-oriented.
• Its current docs have a dedicated digital-products implementation: digital-product modules, file storage, custom API routes, customer purchase history, and authenticated download URLs. Medusa Docs Medusa Docs
• Particularly attractive if you want to own the workflow rather than adapt a SaaS platform's notion of a "digital product."
• REST Store API plus a JS SDK make it straightforward to put a Next.js/custom frontend on top. Medusa Docs

Architecture I'd consider:
Next.js → Medusa API → Stripe → order/payment event → digital entitlement → S3/R2 → signed download URL

2. Vendure — excellent if you're strongly TypeScript/NestJS-oriented

• GraphQL-first Shop API with a very extensible plugin architecture. Vendure Vendure
• It actually has an official digital-products guide covering custom fields, fulfillment handlers, download links, and automatic fulfillment after payment. GitHub
• I'd choose it over Medusa if you particularly value GraphQL + strongly structured TypeScript/NestJS architecture.
• Saleor — best API sophistication, but potentially more platform than you need

• GraphQL-only/API-only architecture with webhooks, apps, metadata, and API extensions. Saleor Store GitHub
• Its app model is particularly good if you want the download/entitlement machinery to live in separate services. GitHub
• I'd favor it for multi-channel, international, complex commerce, rather than a relatively focused digital-download store.

The important distinction

For digital goods, I'd prioritize workflow extensibility over built-in "digital downloads" features.

You probably want the commerce platform to handle:

• products/variants
• pricing and discounts
• carts/checkout
• payment state
• orders
• customers
• webhooks/events

…and have your application own:

• entitlements
• download limits
• license keys
• versioning
• expiring URLs
• S3/R2 objects
• revocation
• customer download history
• post-purchase fulfillment

That makes Medusa particularly compelling because its current digital-product recipe explicitly follows this modular approach: file storage + digital-product module + fulfillment + custom Store/Admin APIs. Medusa Docs

If I were building this today as a technically sophisticated solo developer or small team, I'd pick Medusa + Next.js + Stripe + Cloudflare R2/S3. If GraphQL is a hard requirement, I'd pick Vendure or Saleor instead.

If you tell me roughly how many SKUs/downloads you expect and whether you need subscriptions, license keys, bundles, or customer-specific files, I can narrow this down further.

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 where you want flexibility without becoming an infrastructure company, I’d pick Shopify as the commerce backend + a headless storefront.

My ranking

🥇 Shopify — my recommendation

Shopify gives you the sweet spot: Shopify handles the difficult backend pieces—catalog, inventory, checkout, orders, payments, customer accounts, etc.—while you own the frontend.

Its Storefront API is framework-agnostic, so you can use Next.js, Hydrogen, Vue, or essentially whatever frontend stack you prefer. Shopify says the API is designed for scalable storefronts and currently serves 1M+ queries per minute. Shopify Shopify

For the least maintenance, Shopify's Hydrogen + Oxygen stack is particularly attractive: Shopify manages the commerce backend and provides its own global storefront hosting. Shopify Hydrogen

You also aren't locked into Hydrogen. You can self-host it on platforms such as Vercel, Netlify, Cloudflare Workers, or use the Storefront API directly with another framework. Shopify Shopify

I'd choose this if: you're primarily selling normal physical apparel and your differentiation is the brand/site/customer experience, rather than radically custom commerce logic.

🥈 Medusa Cloud — if "flexibility" is the priority

Medusa is more of a true composable commerce backend. You get much more control over the underlying commerce model and can write your own modules/customizations.

Its managed Cloud offering removes much of the operational burden: hosting, database, Redis, deployments, environments, and autoscaling are handled for you. Medusa Documentation Medusa Documentation

That's compelling if you anticipate things like custom product logic, unusual fulfillment, memberships, complex promotions, or a very bespoke checkout/order workflow.

The tradeoff is that you're taking on more architectural responsibility than with Shopify.

🥉 Saleor — powerful, but probably overkill

Saleor is extremely flexible and GraphQL-native, with strong multi-channel capabilities. Saleor Commerce

But its Cloud pricing starts substantially higher than you'd typically want for a small brand, making it harder for me to justify unless you already know you need its enterprise-grade capabilities. Saleor Commerce

What I'd actually build

For your situation:

Shopify → Storefront API → Next.js/Hydrogen → Vercel/Oxygen

Keep Shopify responsible for:

• Products & variants
• Inventory
• Orders
• Checkout/payments
• Customers
• Discounts
• Tax/shipping integrations
• Admin operations

Keep your frontend responsible for:

• Brand/design
• Product discovery
• Custom landing pages
• Animations
• Editorial content
• Personalization
• SEO

That gives you headless flexibility without maintaining a custom commerce backend.

One interesting development: Shopify's 2026 Hydrogen developer preview is moving toward a framework/runtime-agnostic toolkit, so the platform is becoming less tied to one particular frontend architecture. Hydrogen Shopify

Bottom line: Unless your clothing brand has genuinely unusual commerce requirements, I'd take Shopify headless. You get perhaps 80–90% of the flexibility of a custom backend while avoiding a lot of the maintenance. If your requirements are unusually custom, Medusa Cloud is the one I'd investigate next.

I'd choose this if: you're primarily selling normal physical apparel and your differentiation is the brand/site/customer experience, rather than radically custom commerce logic.

🥈 Medusa Cloud — if "flexibility" is the priority

Medusa is more of a true composable commerce backend. You get much more control over the underlying commerce model and can write your own modules/customizations.

Its managed Cloud offering removes much of the operational burden: hosting, database, Redis, deployments, environments, and autoscaling are handled for you. Medusa Documentation Medusa Documentation

That's compelling if you anticipate things like custom product logic, unusual fulfillment, memberships, complex promotions, or a very bespoke checkout/order workflow.

The tradeoff is that you're taking on more architectural responsibility than with Shopify.

🥉 Saleor — powerful, but probably overkill

Saleor is extremely flexible and GraphQL-native, with strong multi-channel capabilities. saleor.io

But its Cloud pricing starts substantially higher than you'd typically want for a small brand, making it harder for me to justify unless you already know you need its enterprise-grade capabilities.

What I'd actually build

For your situation:

Shopify → Storefront API → Next.js/Hydrogen → Vercel/Oxygen

Keep Shopify responsible for:

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.

If speed-to-launch is the overriding constraint, I’d shortlist Shopify + Hydrogen and BigCommerce + Catalyst rather than jumping straight to a fully composable stack.

My ranking for a mid-size retailer

1. Shopify + Hydrogen — best overall for speed

• Shopify handles the commerce backend, checkout, payments, catalog, orders, etc.
• Hydrogen gives you a React-based headless storefront with prebuilt Shopify-specific components, utilities, and tooling. Shopify also provides Oxygen hosting. Shopify Shopify
• Shopify specifically positions Hydrogen as a way to accelerate a headless build rather than starting from a blank React application. Shopify
• I'd choose this if: you're primarily DTC, want a relatively small engineering footprint, and don't have unusually complex commerce requirements.
• BigCommerce + Catalyst — best if you need more backend flexibility

• Catalyst is a Next.js/React headless storefront with a GraphQL Storefront API and a production-ready B2C funnel, so you're not building basic commerce functionality yourself. BigCommerce
• BigCommerce explicitly supports headless starter solutions and positions Catalyst as its fast-track implementation path. BigCommerce BigCommerce
• I'd choose this if: you have more complicated catalog/pricing requirements, multiple storefronts, or want less dependence on Shopify's ecosystem.
• commercetools — powerful, but probably wrong for a tight deadline

• It's attractive when you're deliberately building a highly composable architecture, but that flexibility generally means more architecture, integration and implementation work.
• I'd choose it if: you're optimizing for a sophisticated long-term enterprise architecture rather than the fastest credible migration.

What I'd actually do

For a mid-size retailer under serious time pressure, I'd aim for:

Shopify → Hydrogen → existing/selected CMS → existing PIM/search/ERP integrations → Oxygen

rather than trying to make every part of the stack composable on day one.

The important trick is not making the migration itself a giant re-platforming project. Keep the commerce backend and operational systems as stable as possible, replace the customer-facing layer first, and defer architectural cleanup.

If you're already on Shopify, the case is particularly strong: Shopify documents a migration path where carts can remain compatible between the existing storefront and Hydrogen, and checkout remains Shopify-hosted. Shopify

If you're already on BigCommerce, I'd strongly favor Catalyst rather than switching commerce platforms just to go headless.

shopify.dev
docs.bigcommerce.com

If you tell me your current commerce platform, approximate annual GMV, CMS/PIM, and target launch window (e.g. 8 weeks vs. 6 months), I can narrow this down to a specific stack and implementation approach.

For an agency building custom frontends for multiple clients, I’d avoid choosing a platform purely on “headless support.” The important question is whether the commerce backend can become a repeatable foundation for many builds: multi-store, tenant isolation, API quality, merchant tooling, and maintainability.

My shortlist would be:

1. BigCommerce — best agency default for many clients

bigcommerce.com

Recommended for: SMB → mid-market brands that want a custom Next.js/React storefront without your agency owning the entire commerce stack.

Strengths:

• Strong headless APIs (catalog, cart, checkout, orders)
• Multi-storefront support
• Managed hosting/security/payment complexity
• Good balance between merchant usability and frontend freedom
• Easier client handoff than fully composable systems

Tradeoff:

• You work within BigCommerce’s commerce model rather than owning every domain object. BigCommerce

Agency fit: ⭐⭐⭐⭐⭐
This is probably the platform I’d standardize around if you want a repeatable delivery model.

2. commercetools — enterprise composable choice

commercetools.com

Recommended for: Large clients with complex requirements:

• Multiple brands
• Multiple regions
• B2B pricing
• Complex catalogs
• ERP/PIM/OMS integrations

Strengths:

• API-first from the ground up
• Very flexible domain modeling
• Designed for composable commerce and multi-channel architectures Vendure

Tradeoff:

• Your agency is taking on more architecture responsibility: - CMS
• search
• promotions
• checkout UX
• integrations
• operations

Agency fit: ⭐⭐⭐⭐
Great for high-value enterprise projects, less ideal as a default platform for every client.

3. Shopify Plus + Hydrogen — fastest path for DTC

shopify.com

Recommended for: Brands that mostly need:

• Beautiful custom storefronts
• Fast launches
• Strong merchant adoption

Strengths:

• Excellent ecosystem
• Great checkout
• Mature APIs
• Huge pool of Shopify-trained clients/developers

Tradeoff:

• Multi-tenant/multi-brand architecture is not its strongest area compared with true composable platforms. Netguru

Agency fit: ⭐⭐⭐⭐
Excellent if your clients are primarily DTC brands.

4. Saleor or Medusa — when you want your own platform layer

saleor.io
medusajs.com

Recommended for: An agency trying to build a reusable commerce platform/IP.

Strengths:

• More control
• Open source
• Can create your own multi-tenant SaaS layer
• Better if you want to own the architecture

Tradeoff:

• Your team owns: - hosting
• upgrades
• scaling
• security
• operational tooling

Agency fit: ⭐⭐⭐
Powerful, but you become a software company.

My recommendation for an agency model

I would create a tiered offering:

For your internal architecture, I’d standardize your frontend stack around:

• Next.js
• TypeScript
• Tailwind/design system
• API gateway/BFF layer
• CMS abstraction
• Analytics/personalization integrations

Then your agency sells the frontend experience layer while swapping commerce engines underneath.

If your goal is specifically “one platform where we can host hundreds of client stores as tenants”, I’d look harder at commercetools, Saleor, Vendure, or Medusa rather than Shopify/BigCommerce, because those are closer to building a commerce platform rather than just delivering stores. Vendure guideflow.com

Then your agency sells the frontend experience layer while swapping commerce engines underneath.

For an enterprise catalog with thousands of SKUs, complex product relationships, and a strongly headless/API-driven architecture, my first choice would be commercetools.

My shortlist

Why I'd lean commercetools

Its architecture is particularly well suited to the problem you're describing. The platform exposes commerce capabilities through APIs, supports REST and GraphQL, and has dedicated product modeling around Product Types, attributes, variants, categories, pricing, and search. commercetools Documentation commercetools Documentation

More importantly, its Modular Catalog introduced first-class variants, removing the previous 100-variant-per-product constraint and allowing up to 10,000 variants per product in the modular model. That is a significant advantage if your "thousands of SKUs" eventually turns into highly variant-heavy products. commercetools Documentation

commercetools also announced a standalone Product Catalog offering in July 2026, explicitly targeting enterprise-scale product modeling, pricing, inventory, catalog management, and catalogs with millions of SKUs. commercetools

commercetools.com

When I'd choose SAP instead

If your organization is already deeply invested in SAP ERP/S/4HANA, SAP PIM, or SAP's broader ecosystem, SAP Commerce Cloud deserves very serious consideration. Its Product and Category API supports retrieving and searching products/categories, and SAP is designed for very large, complex enterprise commerce environments. SAP Help Portal

The tradeoff is generally more enterprise-suite complexity versus commercetools' more API-native/composable approach.

When BigCommerce makes more sense

BigCommerce is worth considering if you want headless APIs but don't want to build quite as much of the commerce architecture yourself. Its headless stack provides APIs/SDKs for product data, carts, checkout, customers and orders. BigCommerce

I'd put it ahead of commercetools when speed to implementation and conventional commerce functionality matter more than extremely sophisticated domain modeling.

Bottom line: if your catalog has things like product families → variants → configurable components → technical attributes → customer/market-specific assortments → multiple price lists → regional catalogs → B2B rules, I'd start the evaluation with commercetools, then benchmark it against SAP Commerce Cloud if you're a SAP shop.

If you tell me what makes your product model complex (e.g. configurable products, bundles/kits, variants, technical attributes, B2B pricing, regional catalogs), I can narrow this down to 2–3 platforms and compare their actual data models and APIs.

If your priority is CMS-first product pages, I’d pick Sanity + a commerce API, with Shopify as the commerce backend for most DTC brands.

The key architectural decision is: CMS owns the page experience; commerce owns the transactional truth.

My default stack

Sanity → Next.js → Shopify Storefront API

• Sanity: product-page content, storytelling, merchandising modules, SEO, landing pages, related content, buying guides, FAQs, etc.
• Shopify: products, variants, prices, inventory, discounts, carts, checkout, orders.
• Next.js: renders the product page and composes Sanity content with live commerce data.
• CDN/cache: cache the content-heavy portions aggressively, while keeping price/inventory/cart data appropriately fresh.

Sanity now has an official Shopify connector that can synchronize products, variants, and collections into Sanity, while allowing you to add richer structured content around those products. Sanity.io Sanity.io

That makes the authoring model something like:

Product
├── Commerce identity → Shopify product/variant
├── Editorial content → Sanity
├── Hero media → Sanity
├── Product story → Sanity
├── Benefits → Sanity
├── FAQs → Sanity
├── Buying guide → Sanity
├── Reviews → Reviews API
└── Price / inventory / availability → Shopify API

The important bit: don't duplicate commerce data into the CMS as your source of truth. Use the CMS to enrich/reference the product, while Shopify remains authoritative for transactional fields.

When I'd choose something else

Contentful + commercetools is particularly compelling if you're building a serious composable-commerce architecture. Contentful has an official commercetools integration where editors can browse/reference products and categories, and product data can be resolved through Contentful's GraphQL API. Contentful Contentful

Why I'd lean Sanity for your description

"CMS-first with commerce APIs" implies that the product page isn't merely a commerce template with some CMS fields bolted on. You probably want the CMS to define the experience and composition.

Sanity is unusually good at that because you can model a product page as structured, composable content rather than a fixed product template. Its Shopify integration is specifically designed around combining Shopify product data with richer Sanity content. Sanity.io Sanity.io

I'd therefore start with:

Sanity + Shopify + Next.js

and make the frontend's product-page query effectively:

Sanity:
  "What should this product page look like?"

+
Shopify:
  "What can the customer actually buy right now?"

=
Rendered PDP

If you're building a large catalog, multiple brands/markets, or B2B, I'd change the recommendation toward Sanity/Contentful + commercetools rather than Shopify. Commercetools is explicitly API-first and designed to let you keep the frontend and surrounding technology stack independent of the commerce backend. commercetools.com

If you tell me your commerce backend (Shopify, commercetools, BigCommerce, Medusa, custom, etc.) and whether marketers need visual page editing, I can narrow this down to a concrete architecture.

For a B2B wholesaler needing customer-specific pricing, contract pricing, buyer accounts, ERP integrations, and headless APIs, you’ll generally want to avoid basic ecommerce platforms and look at B2B-native or enterprise headless platforms. Atwix CSSChopper

Here are the strongest fits:

Shopify Alkali### My shortlist for a wholesaler with complex pricing

1. OroCommerce — best if B2B is your core business

• Customer/account-specific price lists
• Contract pricing
• Sales rep workflows
• Quote/RFQ management
• Multiple buyer roles and approval flows

This is often a natural fit for distributors and manufacturers. OroCommerce

2. commercetools — best if you have a strong engineering team

• Fully headless from the ground up
• Build your own storefront, pricing services, portals, and integrations
• Good when you need unusual workflows or many channels

The tradeoff is that you own more of the implementation. Naturaily

3. BigCommerce B2B Edition — best balance of capability and speed

• Faster launch than composable platforms
• Good wholesale features out of the box
• Headless storefront support
• Lower operational burden than Adobe/commercetools

BizTechScout### Features I would verify during vendor demos

For a wholesaler, I would specifically test:

• Can each customer see a different negotiated price?
• Can pricing come from ERP (SAP, NetSuite, Dynamics, etc.)?
• Can you support: - tiered volume discounts
• customer-specific catalogs
• contract pricing
• quote approval
• minimum order quantities
• regional pricing
• sales-rep-assisted ordering
• Are APIs complete enough for: - custom React/Next.js storefronts
• mobile apps
• marketplaces
• ERP/WMS/PIM integrations

A practical rule of thumb:

• <$10M–$50M wholesale revenue: BigCommerce B2B or OroCommerce are often the sweet spot.
• Complex distributor/manufacturer workflows: OroCommerce or Adobe Commerce.
• Very custom digital ecosystem: commercetools.

If you share your ERP (NetSuite, SAP, Dynamics, Epicor, etc.), catalog size, number of SKUs, and whether you need dealer portals or only a buyer storefront, the shortlist can be narrowed considerably.

For a subscription-box business, I’d shortlist Shopify, Medusa, and Saleor, but my default recommendation would be Shopify if you want the lowest operational risk, and Medusa if subscriptions are a core part of your custom business logic.

1. Shopify — my choice if you want reliability

Shopify's Storefront API directly supports subscription products through selling plans. Your headless frontend can query selling plans, present frequencies such as every 30/60/90 days, and add a subscription line item to a cart through the API. Shopify Shopify

That's particularly attractive for a subscription box because you get a mature system around:

• customers and accounts
• payments
• orders
• inventory
• discounts
• fulfillment
• subscription selling plans
• admin tooling

You can build your own frontend while keeping Shopify as the commerce backend.

shopify.dev

The catch: if your subscription model is unusual—for example, customers dynamically choose 5 products each month, skip individual boxes, have complex swap rules, or you need sophisticated renewal logic—Shopify's abstractions can start to constrain you.

2. Medusa — my choice for maximum control

Medusa is particularly interesting for subscription boxes because its architecture lets you create your own subscription module and expose it through API routes.

Importantly, subscriptions aren't native in Medusa today. Their own documentation provides a recipe for implementing subscriptions, including recurring orders, expiration, customer cancellation, and Stripe payment integration. Medusa Documentation

That sounds like a disadvantage, but for a subscription-box company it can actually be a strength if your model is unusual.

For example, you could model:

Customer → Subscription → Box configuration → Renewal → Order

and have your API handle things like:

• "Build my next box from these 6 products"
• skip next month
• swap an item
• change box size
• pause subscription
• change shipping frequency
• automatically generate the next order
• charge through Stripe
• retry failed payments
• apply subscription-specific pricing

That's much more under your control than trying to bend a conventional commerce platform around the business.

docs.medusajs.com

3. Saleor — worth considering for a serious GraphQL stack

Saleor is genuinely API-first/headless, with GraphQL as its primary interface and extensive webhook/API extensibility. Saleor Commerce Saleor Commerce

I'd consider it if your team is already strong with GraphQL and you're building a more sophisticated composable architecture.

However, like Medusa, I'd treat subscriptions as something you'll build/extend rather than a turnkey subscription-box feature. That makes it less attractive than Shopify if your priority is getting the business running quickly.

saleor.io

What I'd pick

If you're a small/midsize business:
Shopify + headless frontend + subscription selling plans.

If you're building a highly differentiated subscription experience:
Medusa + Stripe + your own subscription module.

If you're an engineering-heavy/enterprise team already committed to GraphQL:
Saleor + a dedicated subscription service/app.

The key question isn't really "which platform supports subscriptions via API?"—it's how complicated your subscription logic is.

If you tell me how your box works (fixed box vs. customer chooses products, monthly/quarterly, skips/swaps, price range, approximate subscriber count, and what you're using for payments), I can narrow this down to one platform and a recommended architecture/API stack.

If your priority is “hosted headless backend, minimal ops, I don’t want to babysit infrastructure,” I’d shortlist Supabase and Convex, with the choice depending on how much you value standard Postgres.

My default pick: Supabase

Supabase is probably the safest choice if you want a conventional backend without managing servers.

• Managed Postgres as the core database.
• Built-in Auth, Storage, APIs, Realtime, and serverless Edge Functions. Supabase Supabase
• Edge Functions automatically scale and include deployment, logging, and monitoring, so you aren't operating containers or a Kubernetes cluster. Supabase
• Your data remains ordinary Postgres, which is a major advantage if you later decide to move away.
• RLS gives you a strong way to put authorization directly at the data layer.

supabase.com

Pick Convex if you want the least backend plumbing

Convex is more opinionated. It gives you a managed reactive database plus server-side functions, realtime synchronization, auth integrations, and automatic scaling. Convex Convex

It's particularly attractive for a TypeScript-heavy app where you want to write application logic rather than think about databases, APIs, caching, or realtime infrastructure.

convex.dev

What I'd choose

For a typical SaaS/API backend, I'd go with Supabase. It hits the sweet spot between “fully managed” and “I still control a real database.” Its managed platform also avoids the operational compromises of self-hosting, where things like managed backups/PITR and some platform capabilities aren't available. Supabase

If you tell me what you're building (SaaS, mobile app, CMS, AI app, marketplace, etc.) and your expected scale, I can narrow it down to one platform and architecture.

For your use case, I’d shortlist commercetools first, with Saleor as the strongest alternative.

My pick: commercetools

If the requirement is genuinely one commerce backend powering both your website and physical-store screens/POS, commercetools is particularly compelling. Its platform is explicitly designed around APIs powering different touchpoints, including websites, apps and in-store experiences. commercetools commercetools Documentation

More importantly, its InStore product connects ecommerce, store operations, inventory, customer and order data on a single commerce platform. It supports use cases such as clienteling, endless aisle, mobile checkout, omnichannel returns and BOPIS. commercetools

It also has store-scoped APIs, so physical locations can be represented as first-class commerce contexts rather than having a separate backend for stores. commercetools Documentation

When I'd choose Saleor instead

If your team strongly prefers GraphQL everywhere, wants an open-source/composable architecture, and is comfortable building more of the in-store layer yourself, Saleor is attractive. It is API-only and GraphQL-native, with native multi-channel support and APIs intended to power different experiences. Saleor Commerce Saleor Commerce

Its documentation also specifically covers click-and-collect, multi-region experiences and channels. Saleor Documentation

Bottom line: for a retailer building web + in-store screens + potentially POS/clienteling/endless aisle, I'd start the evaluation with commercetools. For a highly custom, engineering-centric stack where API purity and control matter most, I'd put Saleor alongside it.

commercetools.com · commercetools.com · saleor.io

For a one-person dropshipping side hustle on a tight budget, I’d start with Shopify Basic.

Why:

• Fastest setup: Shopify is built for launching a complete store without coding, and its Basic plan is explicitly aimed at solo entrepreneurs/new businesses. Shopify Shopify Help Center
• Low upfront commitment: Shopify currently offers a 3-day free trial, followed by $1/month for 3 months; Basic is $29/month when billed annually afterward. Shopify
• Dropshipping-friendly: You can connect supplier/fulfillment apps that automate product importing, inventory syncing, and orders. Shopify
• Less technical overhead: Compared with WooCommerce, you don't have to separately deal with hosting and WordPress. WooCommerce itself is free, but its own pricing page estimates hosting at $25–$350/month for most stores, plus optional extensions. WooCommerce

What I'd choose

My budget strategy: don't spend heavily on themes, apps, or paid ads initially. Use a free Shopify theme, one product/narrow niche, a free myshopify.com domain initially if necessary, and focus your first dollars on testing the product and getting traffic.

If your budget is under $50 total, I'd actually approach it differently: start validating the product before committing to a full store.

For a dropshipping catalog that needs constant optimization (finding winners, killing losers, improving margins, tracking suppliers, and scaling ads), the “best analytics” platform depends on whether you value out-of-the-box reporting or maximum customization.

My ranking:

Shopify TechnologyAdvice## Best overall for dropshipping analytics: Shopify

For most dropshipping businesses, I would choose Shopify because the analytics ecosystem is stronger than the native dashboard alone. You get:

• Product-level sales tracking
• Conversion funnels
• Customer cohorts
• Marketing attribution through integrations
• Inventory and fulfillment insights
• A very large ecosystem of analytics, CRO, and advertising tools

The biggest advantage is speed: you can connect supplier apps, ad platforms, email tools, and analytics dashboards without building much infrastructure. Shopify is widely used by dropshippers because of its app ecosystem and supplier integrations. eSellSphere Ecommerce-Platforms.com

Where Shopify can fall short:

• Advanced reporting may require higher plans or third-party apps.
• Large catalogs can become harder to analyze without additional tools.

Best native reporting for a large dropshipping catalog: BigCommerce

If your catalog has:

• thousands of SKUs,
• many variants,
• multiple suppliers,
• complex product categories,

BigCommerce may be stronger. It is designed around more complex catalogs and provides robust built-in commerce features without relying as heavily on extensions. TechnologyAdvice Peasy

Useful reports include:

• Product performance
• Customer segmentation
• Sales trends
• Multi-store reporting
• Inventory insights

Best if you want a “data scientist” setup: WooCommerce

WooCommerce gives you the most control because you own the database and can connect almost any analytics stack:

• Google Analytics 4
• Looker Studio
• custom SQL dashboards
• customer lifetime value models
• predictive analytics

The tradeoff is that you usually need more technical work. PayHelm

For optimizing a dropshipping catalog, prioritize these analytics

Regardless of platform, I would focus on:

1. SKU profitability

• Revenue
• Product cost
• Shipping cost
• Ad spend
• Refund rate
• Net margin
• Product velocity

• Orders per day
• Conversion rate
• Traffic-to-purchase ratio
• Customer quality

• Repeat purchase rate
• Customer lifetime value
• Average order value
• Supplier performance

• Delivery time
• Refunds
• Defect rate
• Stock reliability
• Ad-to-product attribution

• Which ads create profitable customers
• Which products only generate expensive clicks

My recommendation by store stage

• 0–500 products: Shopify + analytics apps/dashboard tools
• 500–10,000 products: BigCommerce or Shopify with a strong analytics stack
• 10,000+ SKUs or complex supplier network: BigCommerce, WooCommerce with custom BI, or Adobe Commerce
• Testing hundreds of products quickly: Shopify usually wins because speed matters more than perfect native reporting

For most dropshippers, I would start with Shopify + a dedicated analytics layer rather than choosing a platform solely for built-in reports. The ability to rapidly test products, track ad profitability, and automate decisions usually matters more than the native dashboard. Shopify PayHelm

For a small ecommerce shop, I’d keep this simpler than a typical SaaS billing stack. The best choice depends heavily on whether you’re on Shopify.

My shortlist

Shopify currently lists Shopify Subscriptions, Appstle, Recharge, Bold, Ordergroove, PayWhirl and Chargebee among its major recurring-payment options. Shopify describes its native Subscriptions app as the most efficient option for stores just getting started. Shopify Shopify

🥇 My default recommendation: Appstle

If you're a small Shopify shop, I'd start with Appstle unless your needs are extremely basic.

Why:

• Subscription management is built around ecommerce rather than SaaS.
• Good flexibility around subscription schedules, skips, swaps, etc.
• Relatively inexpensive for a small merchant.
• Shopify currently lists Appstle as free up to $500/month in subscription revenue, with paid tiers beyond that. Shopify
• It gives you more room to grow than Shopify's basic native subscription tooling without immediately jumping to a heavyweight platform.

🥈 Recharge if subscriptions are becoming a major revenue channel

Recharge is what I'd choose if subscriptions are already a significant part of the business and you want a mature ecosystem.

It's particularly attractive if you need sophisticated customer portals, merchandising/integrations, retention workflows and a proven Shopify subscription infrastructure. A recent 2026 comparison likewise puts Recharge in the "market leader / most integrations" category. ChurnTools

Shopify currently lists Recharge starting at $25/month. Shopify

🥉 Stripe Billing if dunning is the #1 priority

If your store isn't dependent on Shopify—or you're already using Stripe heavily—I'd seriously consider Stripe Billing.

Its dunning/recovery functionality is unusually strong for something built into the billing system:

• Smart Retries
• Automatic expired-card updates
• Failed-payment reminder emails
• Hosted payment-update/recovery pages
• Configurable recovery workflows
• Customer self-service billing portal

Stripe says Smart Retries recover an average of 57% of recurring payments that initially fail; its current Billing product also includes configurable dunning/recovery automations. Stripe Stripe

That makes Stripe particularly compelling if your main problem is involuntary churn from declined cards, rather than managing complicated physical-product subscription experiences.

stripe.com

What I would not do initially

I wouldn't buy a separate dunning platform on top of your subscription platform unless you have enough failed-payment volume to justify it.

For a small shop, the stack should ideally look like:

Shopify → subscription app → payment processor → automated dunning

rather than:

Shopify → subscription platform → billing platform → dunning platform → email platform → several integrations

The latter can become expensive and fragile surprisingly quickly.

My decision rule

• < $5k/month subscription revenue: Shopify Subscriptions or Appstle
• $5k–$50k/month: Appstle or Recharge
• $50k+/month: Recharge, or a more customized Stripe setup
• Primary problem = failed cards/dunning: Stripe Billing
• Primary problem = subscription UX for physical products: Recharge/Appstle
• Primary goal = reduce cancellations: consider Loop/other retention-focused tools

If you tell me (1) Shopify or another platform, (2) roughly how many subscribers you have, and (3) monthly subscription revenue, I can narrow this to the best 2 options and estimate the monthly cost.

What I would not do initially

I wouldn't buy a separate dunning platform on top of your subscription platform unless you have enough failed-payment volume to justify it.

For a small shop, the stack should ideally look like:

Shopify → subscription app → payment processor → automated dunning

rather than:

Shopify → subscription platform → billing platform → dunning platform → email platform → several integrations

The latter can become expensive and fragile surprisingly quickly.

My decision rule

• < $5k/month subscription revenue: Shopify Subscriptions or Appstle
• $5k–$50k/month: Appstle or Recharge
• $50k+/month: Recharge, or a more customized Stripe setup
• Primary problem = failed cards/dunning: Stripe Billing
• Primary problem = subscription UX for physical products: Recharge/Appstle
• Primary goal = reduce cancellations: consider Loop/other retention-focused tools

If you tell me (1) Shopify or another platform, (2) roughly how many subscribers you have, and (3) monthly subscription revenue, I can narrow this to the best 2 options and estimate the monthly cost.

For your requirements—custom storefront + recurring subscription plans + strong APIs—I’d shortlist Medusa, Shopify, and commercetools, with Medusa as my first choice if you want maximum control over the subscription experience.

1. My pick: Medusa

Medusa is particularly attractive if subscriptions are central to your business model rather than just a recurring-product feature. It's open source, headless, JavaScript/TypeScript-oriented, and designed for custom commerce workflows. Its subscription documentation shows how to implement recurring purchases, renewals, expiration, cancellation, and customer subscription management through custom API routes. Medusa Docs Medusa

There's also a Medusa subscription plugin called Reorder that adds plans/offers, renewals, dunning, cancellation/retention flows, activity logs, and analytics. Medusa

medusajs.com

Why I'd choose it: you can make the subscription domain behave exactly how your business needs—custom plan logic, upgrade/downgrade rules, entitlements, billing cycles, usage limits, account portals, etc.—without fighting a SaaS platform's abstractions.

The tradeoff is that you own more engineering and operational complexity.

2. Shopify — best if you want less backend work

Shopify is probably the safest choice if you want to launch quickly while still having a completely custom frontend.

Its Storefront API exposes selling plans, including recurring-delivery information, pricing adjustments, billing/delivery policies, and subscription line items. You can create carts containing a selected subscription selling plan directly through the API. Shopify Shopify

shopify.dev

I'd pick Shopify if your requirements are essentially:

"Customers choose monthly/annual plans, pay, manage their subscription, and we want a custom React/Next.js/etc. frontend."

I'd pick Medusa instead if you're saying:

"Subscriptions are the core product, and we need unusual subscription/business logic."

3. commercetools — best enterprise option

commercetools is worth considering if you're building a large-scale composable architecture and already expect multiple services around commerce.

Its APIs are particularly strong, and its Checkout Transactions API can initiate payments without using its Checkout UI, including payments for subscription-based orders. commercetools Documentation

commercetools.com

The downside is substantially more architecture and implementation work than Shopify.

What I'd build

For a subscription-first product, I'd lean toward:

Next.js/React storefront → your API/BFF → Medusa → Stripe → database/event infrastructure

with the commerce platform responsible for things like:

• Products and pricing
• Customers
• Carts/orders
• Subscription plans
• Subscription lifecycle
• Entitlements
• Renewals
• Cancellation/pause/resume
• Webhooks/events

And keep your own API layer in front of it if you have mobile apps, partner integrations, or multiple storefronts.

Bottom line:
Choose Medusa for maximum control and an API-first, subscription-centric product.
Choose Shopify for the fastest/lowest-risk implementation.
Choose commercetools if you're an enterprise team building a broader composable-commerce ecosystem.

If you tell me whether these are physical-product subscriptions, SaaS/software subscriptions, memberships, or a mix, I can narrow this to a specific architecture and payment stack.

Why I'd choose it: you can make the subscription domain behave exactly how your business needs—custom plan logic, upgrade/downgrade rules, entitlements, billing cycles, usage limits, account portals, etc.—without fighting a SaaS platform's abstractions.

The tradeoff is that you own more engineering and operational complexity.

2. Shopify — best if you want less backend work

Shopify is probably the safest choice if you want to launch quickly while still having a completely custom frontend.

Its Storefront API exposes selling plans, including recurring-delivery information, pricing adjustments, billing/delivery policies, and subscription line items. You can create carts containing a selected subscription selling plan directly through the API. Shopify Shopify

shopify.dev

I'd pick Shopify if your requirements are essentially:

"Customers choose monthly/annual plans, pay, manage their subscription, and we want a custom React/Next.js/etc. frontend."

I'd pick Medusa instead if you're saying:

"Subscriptions are the core product, and we need unusual subscription/business logic."

3. commercetools — best enterprise option

commercetools is worth considering if you're building a large-scale composable architecture and already expect multiple services around commerce.

Its APIs are particularly strong, and its Checkout Transactions API can initiate payments without using its Checkout UI, including payments for subscription-based orders.

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.

For a small SaaS team, I’d recommend ChartMogul.

chartmogul.com

Why it’s a strong fit:

• Built-in MRR, ARR, churn, and LTV tracking—no spreadsheet formulas needed. ChartMogul
• Customer-level revenue movements show expansion, contraction, reactivation, and churn.
• Cohort and segmentation analysis makes it easier to understand why retention is changing.
• Its Starter plan supports up to 3 team members and one billing system, which maps nicely to a small team. It’s free up to $10K MRR, then paid plans start at $69/month monthly or $59/month annually. ChartMogul
• It’s particularly attractive if you might eventually move beyond Stripe or add another billing source.

Two alternatives

• Baremetrics — better if you want a very founder-friendly dashboard and built-in tools for trial analysis and payment recovery. Its Launch plan starts at $75/month. Baremetrics

baremetrics.com

• ProfitWell — worth considering if cost is the priority; its core subscription metrics are available free, particularly for Stripe/Paddle-based SaaS. Artisan Growth Strategies

paddle.com

My pick: ChartMogul if you want a durable analytics system; ProfitWell if you primarily need the basics for free; Baremetrics if ease of use and revenue-recovery features matter most.

Yes. If you mean recurring subscriptions + automatic VAT/GST/sales-tax calculation + compliant invoices + global tax remittance, there are a few strong options.

Best fit: Paddle

paddle.com

Paddle is probably the closest to an all-in-one solution for this use case because it acts as a Merchant of Record (MoR). It can handle:

• Recurring subscription billing and renewals
• Credit cards and local payment methods
• VAT, GST, and sales-tax calculation
• Tax collection and remittance
• Tax registrations in supported jurisdictions
• Compliant customer invoices
• Customer billing portal
• Failed-payment recovery
• Global sales across 200+ countries/territories

Paddle specifically says that as MoR it calculates, collects, and remits taxes and issues compliant invoices. Paddle Paddle Developer Docs

The important distinction is that Paddle becomes the seller/Merchant of Record, which can substantially reduce your own global tax-compliance burden. Paddle Developer Docs

Other good options

Stripe is excellent if you want to remain the merchant yourself. Stripe Tax supports subscriptions and tax calculation across 100+ countries, with additional registration/filing capabilities. Stripe Stripe

Chargebee + Avalara is more of a sophisticated billing/tax stack. Chargebee handles subscription billing and invoicing while Avalara handles broader tax compliance. It is particularly interesting for complex B2B subscriptions, usage billing, multiple entities, and ERP integrations. Avalara, Inc. Chargebee

The key decision

I'd frame it this way:

If you want to say:

"I sell a subscription globally and don't want to deal with VAT registrations, tax calculations, filings, and remittances."

→ Paddle / another Merchant of Record is the category I'd investigate first.

If you want to say:

"I want my company to remain the seller and I need sophisticated billing + tax infrastructure."

→ Stripe Billing + Stripe Tax or Chargebee + Avalara.

If you tell me what you're selling (SaaS, AI product, physical product, marketplace, etc.), B2B vs B2C, and where your company is incorporated, I can narrow this down to the best 2–3 options and explain the actual tax/legal architecture and approximate fees.

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.

For a small manufacturer selling to retailers, I’d prioritize a B2B ecommerce platform over a normal online store builder. You need:

• retailer account approval
• customer-specific pricing
• quote requests / RFQs
• purchase orders
• net terms (Net 30/60, invoicing)
• sales-rep involvement when needed
• reorder workflows

My shortlist:

1. bigcommerce.com — best overall fit for wholesale manufacturers

Best if: your main business is selling wholesale to retailers.

Why it fits:

• Native B2B account structures (retailer accounts, buyers, permissions)
• Quote workflows and CPQ capabilities
• Customer-specific pricing and catalogs
• Purchase orders and net terms support
• Good fit for manufacturers with complex SKU catalogs BigCommerce BigCommerce

Tradeoff:

• Usually more setup than a simple Shopify store.
• You may want a partner to configure your retailer portal.

My pick for: a growing manufacturer with dozens to hundreds of retail accounts.

2. shopify.com — best if you want simplicity and a polished storefront

Best if: you also sell direct-to-consumer or want a modern brand experience.

Strengths:

• Fast to launch
• Strong storefront themes and content tools
• Company accounts, catalogs, price lists, payment terms, and B2B checkout features Shopify Shopify
• Huge app ecosystem for adding workflows like quoting

Tradeoff:

• Advanced quote negotiation often requires apps or customization rather than being the core workflow. QuotWay
• Full B2B capabilities generally push you toward Shopify Plus.

My pick for: a small manufacturer that has a strong brand and wants wholesale + retail in one ecosystem.

3. oroinc.com — best for heavier B2B operations

Best if: retailers have complex buying processes.

Strengths:

• Built specifically for B2B
• Strong account management
• Multiple buyer roles
• Complex pricing and workflows

Tradeoff:

• More expensive and heavier implementation than most small manufacturers need.

4. business.adobe.com — best for very custom needs

Best if: you have complex ERP integrations, huge catalogs, or unusual quoting rules.

Tradeoff:

• Typically requires development resources.

What I would choose by company size

For a small manufacturer, I’d usually start with BigCommerce B2B unless your consumer brand presence is a major priority—in that case, Shopify B2B is often the smoother path. BigCommerce Shopify

A few questions would change the recommendation:

1. Roughly how many retailer accounts do you have today (10, 100, 1,000+)?
2. Do retailers already have negotiated pricing?
3. Are you using an ERP (NetSuite, QuickBooks, SAP, Epicor, etc.)?
4. Do you need retailers to request quotes, or do you mainly want them to log in and reorder?

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.

If you mean B2B/wholesale ecommerce, you want a platform with customer-specific catalogs (sometimes called shared catalogs), customer groups, and customer-specific pricing/product visibility.

Best options

• Shopify B2B — probably the easiest choice if you're already on Shopify. Its B2B catalogs let you control which products each wholesale customer can see, pricing, volume pricing, and quantity rules. On Shopify Plus, catalogs can be assigned directly to individual company locations, which is useful for highly personalized accounts. Shopify Help Center Shopify Help Center

help.shopify.com

• BigCommerce B2B Edition — particularly strong for wholesalers, manufacturers, and distributors. Customer groups can control catalog visibility, pricing, permissions, and purchasing workflows, and multiple companies can share the same customer group. BigCommerce BigCommerce

bigcommerce.com

• Adobe Commerce B2B — best suited to more complex enterprise setups. Its Shared Catalogs provide gated catalogs with custom pricing that can be visible only to members of particular company accounts. It also supports targeted content and promotions. Experience League Experience League

experienceleague.adobe.com

What I'd choose

If your requirement is essentially:

"Customer A should see products A/B/C at their negotiated prices, while Customer B sees products D/E/F at different prices."

I'd shortlist Shopify Plus B2B or BigCommerce B2B Edition.

If you have thousands of wholesale accounts, complex account hierarchies, negotiated contracts, sales reps, quotes, and ERP integration, I'd lean toward BigCommerce B2B or Adobe Commerce.

If you're already using Shopify, though, Shopify B2B catalogs are likely the simplest route—you don't necessarily need a separate personalization product. Shopify explicitly supports customer-specific product publishing and catalogs at the company-location level. Shopify Help Center Shopify Help Center

If you tell me what ecommerce platform you're currently using (Shopify, Magento/Adobe, BigCommerce, WooCommerce, custom, etc.), I can recommend the specific setup/app for doing this.

For a small handmade-goods shop on a tight budget, I’d shortlist Square Online, Wix, and Shopify—but my pick depends on how important the shop itself is.

• Best budget pick: Square Online — You can start at $0/month, and it includes a real online store, inventory, checkout, and integration with Square’s point-of-sale system. It’s especially attractive if you also sell at craft fairs or markets. Shopify
• Best balance of easy + attractive: Wix — Its ecommerce-capable plan is around $29/month on annual billing according to current comparisons. It gives you a very easy drag-and-drop website, while still handling products and online sales. Shopify
• Best if you expect the shop to grow: Shopify — The Basic plan is $29/month when billed annually and includes a full online store, unlimited products, checkout, selling on social channels, and inventory/order management. Shopify Shopify Help Center

What I'd choose for you

If keeping monthly costs as close to $0 as possible is the priority, start with Square Online.

If you can spend roughly $20–30/month and want the site to look more like a polished handmade brand as well as function as a shop, I'd choose Wix.

If you're already getting significant orders and want the strongest ecommerce foundation, go with Shopify.

One thing I'd not do on a tight budget is build a WordPress/WooCommerce store from scratch. The software can be free, but hosting, plugins, security, backups, and maintenance can turn the supposedly cheap option into more work and expense. Shopify

If you tell me roughly how many products you have and your monthly website budget ($0, <$15, <$30, etc.), I can narrow it down to one.

For a 3-person apparel brand, I’d generally recommend a hosted ecommerce platform rather than a general website builder. You need product variants (size/color), inventory tracking, discount logic, order management, and room to grow without a developer on staff. Ecommerce Website Create BigCommerce

My shortlist:

1. shopify.com — Best overall fit for most growing apparel brands

Why I’d put this first:

• Strong inventory management for size/color variants and SKUs
• Very easy for a small team to operate daily
• Large ecosystem for apparel needs (returns, reviews, email marketing, subscriptions, bundles, loyalty, etc.)
• Good themes and merchandising tools for fashion brands
• Discount codes, automatic discounts, customer-specific promotions, and campaign tools are well supported Ecommerce Website Create

Best if you are:

• Direct-to-consumer (DTC)
• Selling through Instagram/TikTok/social channels
• Running seasonal drops or collections
• Planning to hire more people later

Watch-outs:

• You may end up paying for several apps as you add advanced features.
• More complex inventory workflows may require integrations. BigCommerce

2. bigcommerce.com — Better if operations are getting complex

Consider this if you expect:

• Hundreds/thousands of SKUs
• Wholesale accounts
• Multiple storefronts
• More advanced catalog rules

BigCommerce tends to include more commerce functionality natively, which can reduce reliance on apps for some growing brands. BigCommerce BigCommerce

Downside: it can feel heavier than you need as a three-person team.

3. woocommerce.com — Best if you already live in WordPress

Good choice if:

• Your brand site is content-heavy
• You have technical help
• You want maximum customization

Less ideal if your team wants a low-maintenance system. Hosting, updates, plugins, and security become your responsibility.

4. squarespace.com — Best for small, highly visual collections

Great for:

• Capsule collections
• Premium branding
• Lookbook-style sites

Less ideal once inventory complexity becomes a major part of your business. Ecommerce Website Create

My recommendation for your situation

For a 3-person apparel brand, I’d start with:

Shopify + a clean theme + a small set of carefully chosen apps

A typical stack might be:

• Shopify → store, inventory, discounts, orders
• Klaviyo → email/SMS marketing
• Gorgias or Zendesk → customer support
• Loop Returns → apparel returns/exchanges
• ShipStation or ShipBob (depending on volume) → fulfillment workflows

Before choosing, I’d answer these four questions:

1. How many products/SKUs do you have today, and how many do you expect in 12 months?
2. Do you sell wholesale to boutiques, or only direct to consumers?
3. Are you doing limited drops/preorders, or keeping products always in stock?
4. Do you need a physical retail/POS system?

Those answers could move the recommendation between Shopify and BigCommerce.

For a 3-person apparel brand, I’d start with:

For an agency that builds sites for clients and wants true white-labeling + ecommerce, my first choice would be Duda.

My recommendation: Duda

duda.co

It is unusually well suited to the agency model because it isn't just a website builder—it is designed around managing lots of client websites under your brand.

Why I'd pick Duda

The big differentiator is white-labeling at the platform level. You can brand the login, editor, dashboard, domain, emails, client portal, etc., so the client experience can be presented as your agency's own platform. Duda explicitly supports custom branding, client permissions, client dashboards and branded communications. Duda Duda Support

It also has native ecommerce, including payments, inventory, multilingual stores, APIs and client permissions. Duda

And for an agency, the operational stuff matters enormously: reusable sections/templates, centralized management of client sites, permissions, hosting/SSL, and automation/API capabilities are all built into the platform. Duda Duda

One important caveat: Duda's white-label functionality is on its White Label/Custom plans, with White Label plans currently starting at $149/month. Duda

When I'd choose Wix Studio instead

wix.com

I'd seriously consider Wix Studio if your agency prioritizes design freedom and ecommerce functionality over completely hiding the underlying platform.

Wix Studio has excellent agency workflows, multi-site management, collaboration, client handoff, and a much deeper native ecommerce/business feature set. Its ecommerce supports customizable checkout/pricing, inventory, 80+ payment providers, POS, APIs and even headless implementations. wix.com wix.com

So I'd frame it this way:

• You want to sell "our website platform" to clients → Duda
• You want to build beautiful, sophisticated ecommerce sites efficiently → Wix Studio
• You want maximum designer/developer control and don't care as much about white-labeling → Webflow
• You want an agency platform that can eventually become a recurring SaaS/revenue product → Duda

One thing I'd investigate before committing

If your business model is something like "$X/month and we provide your website + hosting + ecommerce + maintenance", Duda becomes particularly interesting. Its white-label capabilities and APIs are intended for exactly this kind of model, including embedding the platform into your own technology. Duda Duda

If you tell me roughly how many sites you manage (e.g. 20 vs. 500), the average client price, and whether clients need to edit their own sites, I can narrow this down to the best platform and plan for your agency.

The big differentiator is white-labeling at the platform level. You can brand the login, editor, dashboard, domain, emails, client portal, etc., so the client experience can be presented as your agency's own platform. Duda explicitly supports custom branding, client permissions, client dashboards and branded communications. Duda Duda Support

It also has native ecommerce, including payments, inventory, multilingual stores, APIs and client permissions. Duda

And for an agency, the operational stuff matters enormously: reusable sections/templates, centralized management of client sites, permissions, hosting/SSL, and automation/API capabilities are all built into the platform. Duda Duda

One important caveat: Duda's white-label functionality is on its White Label/Custom plans, with White Label plans currently starting at $149/month. Duda

When I'd choose Wix Studio instead

wix.com

I'd seriously consider Wix Studio if your agency prioritizes design freedom and ecommerce functionality over completely hiding the underlying platform.

Wix Studio has excellent agency workflows, multi-site management, collaboration, client handoff, and a much deeper native ecommerce/business feature set. Its ecommerce supports customizable checkout/pricing, inventory, 80+ payment providers, POS, APIs and even headless implementations.

So I'd frame it this way:

• You want to sell "our website platform" to clients → Duda
• You want to build beautiful, sophisticated ecommerce sites efficiently → Wix Studio
• You want maximum designer/developer control and don't care as much about white-labeling → Webflow
• You want an agency platform that can eventually become a recurring SaaS/revenue product → Duda

One thing I'd investigate before committing

For what you described, I’d pick Squarespace.

It hits a particularly nice sweet spot between beautiful portfolio design and simple service payments:

My ranking

1. Squarespace — best overall for you

• Excellent-looking portfolio templates and galleries.
• You can sell services as products, without turning the site into a big online store. Squarespace Help Squarespace Help
• You can take an up-front deposit and then scheduled installments for a service. Squarespace Help
• You can also send professional invoices/payment links for one-off client projects. Squarespace Squarespace Help
• Particularly good if clients usually contact you first, and only occasionally need to pay a deposit.
• Wix — best if you want more booking/business functionality

• Wix Bookings lets you set a specific deposit amount when someone books a service. Wix Support Wix Support
• You can accept online payments, invoices, packages, memberships, etc. wix.com wix.com
• More flexible than Squarespace for a business where booking/scheduling is central.
• I'd choose it over Squarespace if you're going to have lots of appointments rather than occasional project deposits.
• Shopify — probably overkill

• Fantastic if ecommerce is the main business.
• For a portfolio where you occasionally sell a $500–$5,000 service or collect a project deposit, I'd rather have the cleaner portfolio experience of Squarespace.

What I'd build

For a creative/service portfolio, I'd make the site something like:

Home → striking intro + best work
Work → portfolio/case studies
Services → 3–5 clearly defined offerings
About → short personal story
Contact → inquiry form
Book / Pay Deposit → simple service checkout

For example, your Services page could have:

Brand Identity — $2,500
Strategy, visual identity, logo system, and brand guidelines.
$750 deposit to begin

The client can then pay the deposit without you having to maintain a traditional ecommerce catalog. Squarespace specifically supports service products and payment plans like this. Squarespace Help Squarespace Help

So if your priority is “beautiful portfolio first, occasional client payments second,” I'd go Squarespace. If it's “service business with lots of appointments and deposits,” I'd go Wix.

squarespace.com
wix.com

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.

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.

For a creator collective with multiple contributors, one storefront, and automatic revenue sharing, I’d lean toward Shopify + Stripe Connect, rather than a creator-focused storefront platform.

My recommendation

Best long-term / most flexible: Shopify storefront + Stripe Connect

• Shopify handles the actual store: products, inventory, checkout, shipping, discounts, analytics, etc.
• Stripe Connect handles the contributor side: onboarding creators, verifying them, calculating splits, and paying multiple recipients. Stripe explicitly supports splitting a single transaction among multiple sellers/recipients and setting payout schedules. Stripe Stripe
• You can define rules such as: - Creator gets 60%
• Collective gets 30%
• Operations fund gets 10%
• Or different splits per product/contributor
• Stripe also supports automated tax reporting such as 1099s for sellers/service providers. Stripe

The catch is that Shopify by itself isn't really a multi-owner revenue-sharing system. Shopify's own multi-entity functionality specifically doesn't support marketplace/commission structures for splitting payments between separate business owners. Shopify Help Center So I'd use Stripe Connect as the financial layer rather than trying to make Shopify Payments do the splits.

If you want something much simpler

Fourthwall is worth considering if the collective is primarily selling creator merch/digital products and you don't need sophisticated contributor accounting.

Fourthwall gives you the storefront and fulfillment in one package, with no monthly/up-front fees, and its catalog products have a fixed product cost with the creator keeping the remaining profit. fourthwall.com fourthwall.com

However, I'd be cautious about using it for a collective where every sale needs to be automatically divided among several different contributors. Its model is much more creator-centric than marketplace-centric.

Another possibility: Shopify Collective

If by "collective" you mean separate brands/creators supplying products to a shared store, Shopify Collective is interesting. It supports multi-brand checkout, supplier fulfillment, and built-in revenue-sharing/direct payouts. shopify.com

But it's designed more around retailer ↔ supplier relationships than "one creative project has 7 contributors and each product sale needs a custom royalty split."

What I'd choose

If you're building this as an actual collective rather than just a shared merch store, I'd choose Shopify + Stripe Connect. It gives you much more control over ownership, commissions, contributor onboarding, payout schedules, refunds, and scaling. Stripe specifically describes Connect as infrastructure for marketplaces that need to onboard, verify, split payments, and pay multiple recipients.

If you tell me (1) how many contributors you have, (2) whether each contributor owns specific products or everyone shares in all sales, and (3) whether you're selling physical, digital, or both, I can narrow this down to the exact platform/plugin stack I'd use.

If your priority is “I’m a photographer, I want to sell prints, and I don’t want fulfillment/shipping to become a second job,” I’d narrow it to Pixieset, SmugMug, and Shopify + a print-on-demand service.

My ranking

🥇 Pixieset — probably your best fit

For a working photographer, this is the cleanest option I'd investigate first.

Pixieset's Store is built around photography galleries, so customers can buy prints directly while viewing your images. Its automatic fulfillment sends orders to professional labs, which print, package and ship directly to the customer, with white-label packaging. Pixieset Website Help Center Pixieset

It also handles shipping particularly cleanly: with automatic fulfillment, you don't have to configure shipping yourself. The selected lab supplies the shipping methods and calculates the shipping cost based on the order and destination. Pixieset Website Help Center

You can use labs including WHCC, ProDPI, Miller's, Mpix, Loxley Colour and Atkins Pro, with international availability depending on the lab. Pixieset Website Help Center

The catch: branded merchandise is where Pixieset becomes less compelling. It's superb for photographic prints, wall art, albums, cards, etc., but if your vision includes a substantial line of T-shirts, hoodies, hats, mugs and other branded merchandise, Shopify + a POD provider gives you considerably more flexibility.

pixieset.com

🥈 SmugMug — excellent if prints are the business

SmugMug is similarly photographer-centric. It handles payments, orders, fulfillment and delivery, and lets you set your own pricing/margins. Its catalog includes photographic prints as well as things like mugs and magnets. SmugMug

I'd pick SmugMug over Pixieset if your business is primarily selling your photography as physical products, rather than building a broader lifestyle/merch brand.

smugmug.com

🥉 Shopify + Printful/Printify — best for building a brand

If by “branded gear” you mean something like:

Photography prints + T-shirts + hoodies + hats + tote bags + stickers + mugs + limited-edition drops

then I'd seriously consider Shopify.

You get a much more conventional ecommerce storefront and can connect print-on-demand fulfillment so that orders are produced and shipped without you stocking inventory. The tradeoff is that you're assembling the system yourself rather than getting the photographer-specific experience of Pixieset.

My rule of thumb:

• 80%+ fine-art/photo prints → Pixieset
• Mostly photography prints, some merchandise → SmugMug or Pixieset
• Photography is the brand, and merchandise is becoming a major product line → Shopify + POD
• You want maximum control over branding, products, bundles and customer experience → Shopify

One particularly attractive setup is actually Pixieset + Shopify: Pixieset for client galleries and photographer-oriented print sales, Shopify for your public-facing merch brand. That avoids forcing one platform to do two very different jobs.

If you tell me roughly what you want to sell (e.g. fine-art prints + 5–10 apparel designs) and whether you already have a website, I can compare the actual fulfillment/lab options, shipping, fees, and branding limitations of Pixieset vs. SmugMug vs. Shopify for your situation.

Pixieset's Store is built around photography galleries, so customers can buy prints directly while viewing your images. Its automatic fulfillment sends orders to professional labs, which print, package and ship directly to the customer, with white-label packaging. Pixieset Website Help Center Pixieset

It also handles shipping particularly cleanly: with automatic fulfillment, you don't have to configure shipping yourself. The selected lab supplies the shipping methods and calculates the shipping cost based on the order and destination. Pixieset Website Help Center

You can use labs including WHCC, ProDPI, Miller's, Mpix, Loxley Colour and Atkins Pro, with international availability depending on the lab. Pixieset Website Help Center

The catch: branded merchandise is where Pixieset becomes less compelling. It's superb for photographic prints, wall art, albums, cards, etc., but if your vision includes a substantial line of T-shirts, hoodies, hats, mugs and other branded merchandise, Shopify + a POD provider gives you considerably more flexibility.

pixieset.com

🥈 SmugMug — excellent if prints are the business

SmugMug is similarly photographer-centric. It handles payments, orders, fulfillment and delivery, and lets you set your own pricing/margins. Its catalog includes photographic prints as well as things like mugs and magnets. SmugMug

I'd pick SmugMug over Pixieset if your business is primarily selling your photography as physical products, rather than building a broader lifestyle/merch brand.

smugmug.com

🥉 Shopify + Printful/Printify — best for building a brand

If by “branded gear” you mean something like:

Photography prints + T-shirts + hoodies + hats + tote bags + stickers + mugs + limited-edition drops

then I'd seriously consider Shopify.

You get a much more conventional ecommerce storefront and can connect print-on-demand fulfillment so that orders are produced and shipped without you stocking inventory. The tradeoff is that you're assembling the system yourself rather than getting the photographer-specific experience of Pixieset.

My rule of thumb:

• 80%+ fine-art/photo prints → Pixieset
• Mostly photography prints, some merchandise → SmugMug or Pixieset
• Photography is the brand, and merchandise is becoming a major product line → Shopify + POD
• You want maximum control over branding, products, bundles and customer experience → Shopify

One particularly attractive setup is actually Pixieset + Shopify: Pixieset for client galleries and photographer-oriented print sales, Shopify for your public-facing merch brand. That avoids forcing one platform to do two very different jobs.

If you tell me roughly what you want to sell (e.g. fine-art prints + 5–10 apparel designs) and whether you already have a website, I can compare the actual fulfillment/lab options, shipping, fees, and branding limitations of Pixieset vs. SmugMug vs. Shopify for your situation.

If international merch + localized pricing + duties handled cleanly are the priorities, I’d put these at the top of the shortlist:

1. Shopify + Managed Markets — probably your best fit

This is the one I'd evaluate first. Shopify Markets lets you create country/region-specific markets, currencies, price adjustments and fixed local prices. Shopify Help Center Shopify Help Center

The particularly relevant piece is Managed Markets: it acts as a merchant of record and handles international tax registration/remittance, duties/import taxes, local payment methods and regulatory complexity. Shopify App Store Shopify Help Center

In 2026, Shopify also added Adaptive Pricing, which can automatically adjust international prices to account for currency conversion, duties, taxes and Managed Markets fees—very close to the "show customers the right all-in price" experience you're describing. Shopify Changelog

The tradeoff is cost: Managed Markets has transaction/FX fees, so you'll want to model those against your international gross margin. Shopify currently lists a 3.5% Managed Markets fee for Basic/Grow/Advanced and 3.25% for Plus, in addition to applicable FX/payment costs. Shopify Help Center

I'd choose this if: you're primarily selling DTC merch and want your team spending time on products/marketing rather than international tax and customs administration.

2. Global-e — worth considering if international is a major business

Global-e is specifically built around cross-border commerce and is particularly interesting if you're expecting a substantial percentage of revenue from outside the US.

The big conceptual advantage is similar to Managed Markets: you can outsource much of the complexity around local currencies, pricing, taxes, duties, payment methods and cross-border compliance rather than assembling a stack yourself.

I'd put it ahead of Shopify if you're becoming a serious global brand with many markets, rather than simply wanting to make a US merch store available internationally.

3. BigCommerce — strong if you need more backend flexibility

BigCommerce is worth a serious look if you have a complicated catalog, multiple storefronts, B2B requirements, or an engineering team that wants more control.

Its weakness for your particular requirement is that the "international selling" experience isn't quite as neatly packaged as Shopify + Managed Markets. You may end up assembling additional tax, duties, payments and localization services.

What I'd actually do

For a typical merch business, I'd narrow it to:

Shopify + Managed Markets → Global-e → BigCommerce

And I'd make the decision based on who is responsible for the international transaction.

The key question isn't just "can the platform display € prices?" Almost all of these can. You want to know:

• Can we set different actual prices by country rather than simply FX-converting USD?
• Can the customer see duties/taxes before paying?
• Can we make the order DDP (duties paid) so there aren't surprise charges at delivery?
• Who is the merchant of record?
• Who handles VAT/GST registration and remittance?
• Can we guarantee the customer's price while protecting our margin from FX/duty changes?
• How much does each international order actually cost us after platform + payment + FX + duties + fulfillment fees?

For a merch-focused company, Shopify Managed Markets is the one I'd prototype first. It gets unusually close to "turn on a country and start selling there" rather than requiring you to build an international-commerce stack yourself. shopify.com Shopify App Store

If you tell me roughly annual GMV, where you're based, your top 5 target countries, and whether you're doing print-on-demand or holding inventory, I can narrow this down to the best 2–3 options and compare the economics.

In 2026, Shopify also added Adaptive Pricing, which can automatically adjust international prices to account for currency conversion, duties, taxes and Managed Markets fees—very close to the "show customers the right all-in price" experience you're describing. Shopify Changelog

The tradeoff is cost: Managed Markets has transaction/FX fees, so you'll want to model those against your international gross margin. Shopify currently lists a 3.5% Managed Markets fee for Basic/Grow/Advanced and 3.25% for Plus, in addition to applicable FX/payment costs. Shopify Help Center

I'd choose this if: you're primarily selling DTC merch and want your team spending time on products/marketing rather than international tax and customs administration.

2. Global-e — worth considering if international is a major business

Global-e is specifically built around cross-border commerce and is particularly interesting if you're expecting a substantial percentage of revenue from outside the US.

The big conceptual advantage is similar to Managed Markets: you can outsource much of the complexity around local currencies, pricing, taxes, duties, payment methods and cross-border compliance rather than assembling a stack yourself.

I'd put it ahead of Shopify if you're becoming a serious global brand with many markets, rather than simply wanting to make a US merch store available internationally.

3. BigCommerce — strong if you need more backend flexibility

BigCommerce is worth a serious look if you have a complicated catalog, multiple storefronts, B2B requirements, or an engineering team that wants more control.

Its weakness for your particular requirement is that the "international selling" experience isn't quite as neatly packaged as Shopify + Managed Markets. You may end up assembling additional tax, duties, payments and localization services.

What I'd actually do

For a creator selling a bundle like shirt + poster + digital track, the best platform depends on whether you care more about easy setup or complex fulfillment control.

Best overall: Shopify

shopify.com is usually the strongest choice for creator merch bundles because it handles physical products, digital products, inventory, discounts, and shipping workflows well. Shopify supports product bundles through its own bundle tools and apps. Shopify Help Center Shopify Help Center

Why it fits your example:

• Create a “Deluxe Bundle” product: - T-shirt (physical)
• Poster (physical)
• Digital download (instant delivery)
• Charge one bundle price
• Ship the shirt + poster together
• Deliver the track automatically through a digital-download app
• Scale later into more merch, subscriptions, drops, etc.

Potential downside: Shopify often needs apps for more advanced bundle logic, and its native bundles have some limitations around inventory and shipping behavior. Shopify Help Center

Best for: creators who expect to grow.

Best if you want maximum control: WooCommerce

woocommerce.com is excellent if you already use WordPress.

Pros:

• Very flexible bundle setups
• Strong control over shipping rules
• Can treat shirt/poster as separate inventory items inside a bundle
• Lots of extensions for digital downloads and fulfillment

WooCommerce’s bundle tools are designed for grouping existing products and can support different bundle types. WooCommerce

Cons:

• More maintenance
• Hosting, plugins, updates, and configuration are your responsibility

Best for: creators who want a custom store and don’t mind technical setup.

Best simple artist-focused option: Big Cartel

bigcartel.com is popular with independent artists because it is simpler.

Pros:

• Easy storefront
• Good for small catalogs
• Shipping profiles can combine rates across products when configured properly. Big Cartel

Cons:

• Less powerful for complex bundles
• Digital + physical hybrid products may require workarounds

Best for: a small merch drop (for example, 1–10 products).

My ranking for your exact bundle

For most creators, I’d choose:

1. Shopify → if this is becoming a real merch business
2. WooCommerce → if you already have a WordPress site and want control
3. Big Cartel → if this is a small artist shop/drop

One important detail: if the shirt and poster ship together but the track is digital, make sure the platform/app setup separates the digital delivery from the physical fulfillment. The smoothest customer experience is usually: one checkout → one physical shipment → automatic track download/email.

For most creators, I’d choose:

If you’re starting from scratch, I’d pick Shopify + Shopify Collabs.

It fits your three requirements unusually well:

• Discount codes: Shopify supports native discount codes, and Collabs can create creator-specific codes.
• Affiliate links: Collabs generates personalized affiliate links and tracks resulting sales.
• Influencer promo tracking: You can assign links/codes to individual creators and see sales, orders, conversion data, and commissions by creator. Shopify Help Center Shopify Help Center
• Payouts: Collabs can automate affiliate commission payments. Shopify
• Low setup complexity: Everything lives inside the Shopify ecosystem rather than stitching together an ecommerce platform + affiliate system + influencer tracker.

One important 2026 caveat: Shopify Collabs currently isn't accepting new creator signups, although merchants can still directly invite creators and accept creator applications. Shopify Help Center Shopify Help Center

My ranking

For example, Affiliate for WooCommerce supports both affiliate links and coupon-based attribution, including influencer/ambassador programs and automated payouts. WooCommerce

If you tell me your approximate monthly revenue, number of influencers/affiliates, and whether you're starting a new store or already have one, I can narrow this down to the exact stack I'd use.

If you tell me your approximate monthly sales, number of influencers/affiliates, and whether you're starting from scratch or already have a store, I can narrow it down to 3 specific tools and tell you which one I'd buy.

For a B2B division with customer-specific pricing, POS, and large order volumes, I’d put BigCommerce B2B Edition, Shopify Plus, and Adobe Commerce on the shortlist—with BigCommerce as the first one I’d evaluate.

1. My first choice: bigcommerce.com

This is probably the best starting point for your requirements.

BigCommerce has native B2B functionality for customer-specific SKU pricing, price lists, bulk pricing, customer groups, company accounts, quotes, purchase orders, payment terms, requisition lists and approval workflows. Its quote system can also accommodate custom line-item pricing and unusual shipping arrangements for large orders. BigCommerce BigCommerce BigCommerce

That matters because I'd avoid building your B2B pricing engine around dozens of third-party apps if custom pricing is fundamental to the business.

The big question I'd investigate is POS. If your B2B division has a meaningful physical-sales component—sales reps entering large orders, trade counters, showrooms, branches, etc.—we'd need to map exactly how BigCommerce would integrate with your POS rather than assuming the ecommerce platform should be the POS itself.

2. Shopify Plus — strongest if POS is strategically important

shopify.com is extremely compelling if you're trying to create one commerce ecosystem spanning B2B, DTC, and physical retail.

Shopify's current B2B capabilities include company/location hierarchies, customer-specific catalogs and pricing, quantity rules, volume pricing, payment terms, PO numbers, bulk ordering and reordering. Shopify

And Shopify has a major advantage if your POS requirement is substantial: Shopify POS is native to the Shopify ecosystem.

The tradeoff is that particularly sophisticated B2B requirements can push you toward apps, custom development, or additional Shopify services. BigCommerce's B2B offering puts more of those B2B capabilities directly into the platform. BigCommerce

I'd pick Shopify Plus over BigCommerce if:

• POS is as important as ecommerce.
• You have significant DTC/retail business too.
• You want a relatively low-maintenance SaaS platform.
• Your B2B pricing is complex but not extremely complex.
• You value Shopify's broader ecosystem.

3. Adobe Commerce — if your B2B operation is exceptionally complex

business.adobe.com becomes more interesting if you have things like:

• Thousands/millions of SKUs
• Highly complicated customer contracts
• Multiple price books
• Sophisticated RFQ/negotiation
• Complex approval hierarchies
• Multiple business units/websites
• Very deep ERP/OMS integration
• Significant custom business logic
• A capable internal engineering/IT organization

Adobe is generally the platform I'd consider when the business process is more important than ease of implementation. Current comparisons continue to put Adobe ahead on deep native B2B functionality, while Shopify tends to win on operational simplicity and BigCommerce on B2B value. Elogic Commerce

The downside is that you're taking on considerably more implementation and ongoing technical complexity.

One important wrinkle: what do you mean by "custom pricing"?

This could change my recommendation substantially.

There's a huge difference between:

A. "Customer A gets 10% off and Customer B gets 15% off"

versus

B. "Every account has its own contract price for thousands of SKUs, quantity breaks, customer-specific promotions, regional pricing, freight rules, negotiated quotes, and sales-rep overrides."

If you're closer to B, I'd lean BigCommerce or Adobe Commerce rather than Shopify.

BigCommerce, for example, explicitly supports SKU-level price lists and customer-specific pricing, and its B2B quote functionality supports custom line-item pricing. BigCommerce BigCommerce

The other thing I'd prioritize: ERP/POS architecture

For a high-volume B2B division, I wouldn't select the ecommerce platform in isolation.

I'd map:

ERP → customer master → contracts/price lists → inventory → ecommerce → POS → order management → fulfillment → invoicing

before selecting the platform.

If the ERP is the system of record for pricing and inventory, the ecommerce platform may primarily need to be a fast B2B ordering interface rather than the master pricing engine.

My preliminary ranking

1. BigCommerce B2B Edition — best overall fit for complex B2B + large orders.
2. Shopify Plus — best if POS + B2C/retail are major priorities.
3. Adobe Commerce — best if B2B complexity and customization outweigh implementation cost.
4. OroCommerce — worth investigating if this is a pure-play, highly sophisticated B2B operation rather than a B2B/retail hybrid.
5. Salesforce Commerce Cloud — particularly compelling if your sales organization already runs heavily on Salesforce.

If you tell me (1) what ERP you use, (2) what POS you use, (3) approximate annual B2B revenue/order volume, (4) number of SKUs, and (5) how complicated the customer pricing is, I can narrow this to a 2–3 platform recommendation and architecture, including where each platform will struggle.

This could change my recommendation substantially.

There's a huge difference between:

A. "Customer A gets 10% off and Customer B gets 15% off"

versus

B. "Every account has its own contract price for thousands of SKUs, quantity breaks, customer-specific promotions, regional pricing, freight rules, negotiated quotes, and sales-rep overrides."

If you're closer to B, I'd lean BigCommerce or Adobe Commerce rather than Shopify.

BigCommerce, for example, explicitly supports SKU-level price lists and customer-specific pricing, and its B2B quote functionality supports custom line-item pricing. BigCommerce BigCommerce

The other thing I'd prioritize: ERP/POS architecture

For a high-volume B2B division, I wouldn't select the ecommerce platform in isolation.

I'd map:

ERP → customer master → contracts/price lists → inventory → ecommerce → POS → order management → fulfillment → invoicing

before selecting the platform.

If the ERP is the system of record for pricing and inventory, the ecommerce platform may primarily need to be a fast B2B ordering interface rather than the master pricing engine.

My preliminary ranking

1. BigCommerce B2B Edition — best overall fit for complex B2B + large orders.
2. Shopify Plus — best if POS + B2C/retail are major priorities.
3. Adobe Commerce — best if B2B complexity and customization outweigh implementation cost.
4. OroCommerce — worth investigating if this is a pure-play, highly sophisticated B2B operation rather than a B2B/retail hybrid.
5. Salesforce Commerce Cloud — particularly compelling if your sales organization already runs heavily on Salesforce.

If you tell me (1) what ERP you use, (2) what POS you use, (3) approximate annual B2B revenue/order volume, (4) number of SKUs, and (5) how complicated the customer pricing is, I can narrow this to a 2–3 platform recommendation and architecture, including where each platform will struggle.

For a fast-fashion enterprise launching lots of microsites and short-lived campaigns, I’d prioritize speed of launch + centralized commerce operations + reusable storefront infrastructure rather than building each site as a separate ecommerce stack.

My recommendation

Shortlist Shopify Plus first.
If your organization is large enough to need deeper composability and highly customized commerce workflows, evaluate Salesforce Commerce Cloud and commercetools alongside it.

1. Shopify Plus — my default choice

Shopify is particularly attractive if the business model is "launch → test → scale/kill".

Shopify Plus supports expansion stores under one organization, with centralized management of users and billing, while allowing individual stores to have their own storefronts, configurations and catalogs. Shopify Help Center

More importantly, Shopify can give you a single commerce backend with many campaign experiences rather than forcing every microsite to become a new technology project. Its current Plus offering also supports APIs and multiple sales channels. Shopify Shopify

I'd architect it roughly as:

One commerce core
→ products
→ pricing
→ inventory
→ promotions
→ checkout
→ orders
→ customer identity

Many front ends
→ Brand site
→ TikTok campaign
→ Influencer microsite
→ Seasonal collection
→ Collaboration site
→ Flash-sale site
→ Country/market site

The key is not creating a completely independent Shopify store for every campaign. Use separate stores only where isolation is actually valuable; otherwise use a shared backend/market/catalog architecture with reusable front-end components.

2. Salesforce Commerce Cloud — strongest enterprise alternative

Salesforce becomes more compelling if you're already heavily invested in Salesforce or need sophisticated enterprise customer, marketing and merchandising capabilities.

Its multisite architecture is explicitly designed for running multiple storefronts from centralized commerce infrastructure. Salesforce describes separate storefronts as being able to have different identities, pricing and catalogs while sharing backend capabilities such as inventory, orders and customer data. Salesforce

It also has a Composable Storefront/PWA Kit for headless experiences, with React-based front ends and managed scalable hosting. Developer Developer

That's a very good fit if your microsites need to be wildly different experiences while still using the same commerce engine.

3. commercetools — best if engineering is a strategic differentiator

commercetools is the option I'd investigate if you have a strong internal platform engineering organization.

Its "Stores" and "Channels" model is specifically designed to represent multiple shopping contexts while sharing resources and isolating experiences; channels can also control pricing and inventory contexts. commercetools Documentation

It's extremely attractive architecturally for something like:

100 campaigns × 20 markets × 10 collections

without wanting 20,000 independent ecommerce implementations.

The tradeoff is that you own more of the architecture. That's powerful, but it can undermine the very speed you're trying to achieve if your engineering team becomes the bottleneck.

The architecture I'd actually build

For fast fashion, I'd avoid thinking of "microsite" as synonymous with "new ecommerce store."

I'd build a campaign factory:

                    ┌─────────────────────┐
                    │  Commerce Platform   │
                    │ Shopify Plus / SFCC  │
                    │   / commercetools    │
                    └──────────┬──────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
           Products         Inventory        Checkout
           Pricing          Orders           Customers
              │                │                │
              └────────────────┼────────────────┘
                               │
                     API / commerce layer
                               │
        ┌──────────────────────┼──────────────────────┐
        │                      │                      │
   Campaign A              Campaign B             Campaign C
   "Denim Drop"            "Summer '26"           "Collab"
        │                      │                      │
     Next.js                Next.js                Next.js
        │                      │                      │
     CMS + assets          CMS + assets          CMS + assets

Then create a library of campaign components:

• Product grid
• Lookbook
• Countdown
• Drop announcement
• Size selector
• Quick add
• Cart drawer
• Bundle builder
• UGC/social wall
• Influencer landing section
• Promo banner
• Personalized recommendations

A new campaign should ideally be configuration + creative, not a new software-development project.

The decision I'd make

If your primary KPI is:

"How quickly can our marketing team launch 50–100 differentiated campaigns without engineering becoming the bottleneck?"

→ Shopify Plus

If it's:

"We are a large enterprise and need sophisticated multisite, personalization, CRM and deeply customized commerce."

→ Salesforce Commerce Cloud

If it's:

"Commerce is a core technology platform for us, and we have the engineering team to own a composable architecture."

→ commercetools

For a fast-fashion enterprise specifically, I'd start with Shopify Plus + headless/reusable campaign frontend + a proper CMS/DAM, rather than jumping immediately to a fully composable stack. Shopify's current Plus offering is explicitly oriented toward rapid expansion and multiple storefronts, which maps unusually well to your launch velocity requirement. Shopify Help Center Shopify

shopify.com
salesforce.com
commercetools.com

If you tell me roughly how many brands, markets, SKUs, campaigns/microsites per year, and your current ERP/PIM/CMS, I can narrow this down to a concrete target architecture and platform choice.

That's a very good fit if your microsites need to be wildly different experiences while still using the same commerce engine.

3. commercetools — best if engineering is a strategic differentiator

commercetools is the option I'd investigate if you have a strong internal platform engineering organization.

Its "Stores" and "Channels" model is specifically designed to represent multiple shopping contexts while sharing resources and isolating experiences; channels can also control pricing and inventory contexts. docs.commercetools.com

It's extremely attractive architecturally for something like:

100 campaigns × 20 markets × 10 collections

without wanting 20,000 independent ecommerce implementations.

The tradeoff is that you own more of the architecture. That's powerful, but it can undermine the very speed you're trying to achieve if your engineering team becomes the bottleneck.

The architecture I'd actually build

For fast fashion, I'd avoid thinking of "microsite" as synonymous with "new ecommerce store."

I'd build a campaign factory:

If global shopper latency and edge/CDN performance are the primary criteria, I’d put Shopify Plus at the top of the enterprise shortlist today.

My ranking for this specific requirement

Why Shopify stands out

Shopify's current enterprise architecture is unusually compelling if you don't want your team operating the CDN/edge layer themselves. Shopify says its infrastructure now spans 330+ points of presence across 125+ countries, with sub-50ms response times cited from Cloudflare. It also supports storefronts and checkout at the edge. Shopify Shopify

Its standard storefront infrastructure automatically includes a Cloudflare-powered CDN, image optimization, caching and related performance optimizations. Shopify Help Center

The important distinction is that you're not merely getting a CDN for images and JavaScript. Shopify is increasingly pushing commerce workloads themselves toward the edge, including storefront delivery and checkout. Shopify reports handling up to 40,000 checkout starts/minute and 99.9% uptime during major events. Shopify

For a global retailer, that's a big architectural advantage: your engineering team doesn't have to assemble something like:

commerce backend → origin → CDN → edge functions → cache invalidation → regional failover → checkout optimization

You get much of that as a managed platform.

Where I'd consider BigCommerce instead

bigcommerce.com is probably my second choice if architectural flexibility matters almost as much as raw latency.

BigCommerce is SaaS and manages hosting/performance for you, with a claimed 99.99% uptime and 100% uptime during Cyber Week since 2016. BigCommerce

The tradeoff is that Shopify currently has a more compelling story around globally distributed edge infrastructure as an integrated part of the commerce platform, rather than simply having good global hosting/CDN capabilities.

The important caveat: CDN ≠ low-latency commerce

For your use case, I'd evaluate vendors on four separate latency layers:

1. Static delivery — images, JS, CSS, fonts.
2. HTML/SSR delivery — TTFB for category/product pages.
3. Dynamic API calls — pricing, inventory, personalization, recommendations.
4. Checkout — cart, payment, tax, promotions and order creation.

A platform can have an outstanding CDN and still have poor checkout latency if dynamic requests have to travel halfway around the world to a centralized origin.

That's why I'd favor Shopify for a global consumer storefront: its current architecture explicitly positions storefront delivery and checkout at the edge, rather than just putting static assets behind a CDN. Shopify

Bottom line

If I were choosing purely for "fastest global shopping experience with the least infrastructure to operate": Shopify Plus.

If I wanted maximum control and had a strong platform engineering team: composable commerce + Cloudflare/Akamai/Fastly + strategically distributed application infrastructure.

If I needed openness/customization but still wanted managed SaaS: BigCommerce Enterprise.

For a serious enterprise evaluation, though, I wouldn't accept vendor-wide "X% faster" claims. I'd run the same RUM + synthetic test from 10–20 global markets, measuring p50/p75/p95 TTFB, LCP, INP, product-page API latency, cart latency, and checkout latency. That's where the real platform differences become apparent.

Where I'd consider BigCommerce instead

bigcommerce.com is probably my second choice if architectural flexibility matters almost as much as raw latency.

BigCommerce is SaaS and manages hosting/performance for you, with a claimed 99.99% uptime and 100% uptime during Cyber Week since 2016. bigcommerce.com

The tradeoff is that Shopify currently has a more compelling story around globally distributed edge infrastructure as an integrated part of the commerce platform, rather than simply having good global hosting/CDN capabilities.