All answers

If flexibility + API control are your top criteria, I’d shortlist Medusa, Saleor, Vendure, and commercetools. For a developer building a genuinely custom frontend, the choice mostly comes down to how much of the commerce backend you want to own.

Medusa

For a TypeScript/Next.js developer, I'd look particularly closely at Medusa.

Its current architecture is modular: products, carts, pricing, inventory, orders, payments, fulfillment, promotions, etc. are separate commerce modules, and you can extend their data models and build your own workflows. Medusa Docs Medusa Docs

The API is also straightforward for a custom frontend: Medusa exposes separate Store and Admin REST APIs, provides a JS SDK, and publishes an OpenAPI specification. Medusa Docs Medusa Docs

Most importantly for your use case, the storefront is completely separate from the backend. You can build it from scratch with Next.js, React, mobile, or another frontend rather than adapting your UI to a platform's storefront model. Medusa Docs

I'd choose Medusa when you want:

• TypeScript end-to-end
• Full control over checkout/business logic
• Custom product/catalog models
• Custom pricing/promotions
• Custom APIs and integrations
• Self-hosting
• A backend you can actually modify rather than merely configure

Saleor

Saleor is particularly interesting if you prefer GraphQL.

Its API is GraphQL-first, and its architecture is deliberately headless: storefront and admin experiences are API-driven, with extensions through APIs and webhooks rather than requiring platform-specific frontend plugins. Saleor Documentation Saleor Commerce

I'd investigate Saleor if your frontend/BFF architecture is heavily GraphQL-oriented or you need sophisticated multi-channel, international, B2B, or marketplace capabilities.

Vendure

Vendure is another strong option if you want TypeScript on the backend but prefer a GraphQL/plugin-oriented architecture.

It's worth comparing directly with Medusa if your team wants to own the commerce backend rather than use a SaaS commerce service.

commercetools

commercetools is the one I'd examine for a larger enterprise project.

Its APIs include both HTTP and GraphQL, and its documentation specifically recommends using general APIs behind a middleware/BFF layer for custom frontends to maximize control. commercetools Documentation commercetools Documentation

The tradeoff is that you're buying into a much more enterprise-oriented platform rather than getting a lightweight codebase you can freely modify.

My practical decision tree

If you're a JS/TS developer building a custom Next.js frontend:
→ Medusa

If you want GraphQL everywhere:
→ Saleor

If you want TypeScript + GraphQL + a plugin architecture:
→ Vendure

If this is a large enterprise/composable-commerce project:
→ commercetools

If you mainly want a managed backend and don't want to operate commerce infrastructure:
→ Shopify headless

For your particular wording — "I'm a developer building a custom frontend" + "flexibility and APIs" — I'd start by prototyping Medusa vs Saleor, rather than starting with Shopify. The architectural difference is significant: Medusa gives you a TypeScript/REST-oriented backend you can modify deeply, while Saleor gives you a GraphQL-first API boundary with a more API/application-extension-oriented model. Eryx Innovations Lab Saleor Commerce

If you tell me Next.js/React vs another frontend, expected catalog size, B2C vs B2B, and whether you want to self-host, I can narrow this down to the architecture I'd use and show the API flow for product → cart → checkout → payment → order.

For a brick-and-mortar + online business, I’d narrow it to Shopify POS vs. Cin7. The better choice depends mostly on how complex your inventory operation is.

My practical recommendation

If you're already on Shopify or are happy to move your ecommerce onto Shopify, start by evaluating Shopify POS. It gives you a genuinely unified inventory model rather than having a separate ecommerce inventory and POS inventory that need reconciliation. Shopify

If inventory itself is the complicated part of your business, I'd look seriously at Cin7. For example, if you have Amazon/eBay/Walmart + your website + physical stores + multiple warehouses/3PLs, Cin7 is designed to act as the inventory/order hub underneath those channels. Cin7 Cin7

One important distinction: don't choose based purely on "does it sync inventory?" Almost all of these platforms claim that. Look at where the source of truth lives, how reservations/committed stock work, multi-location transfers, returns, bundles/kits, purchase orders, and what happens when two channels sell the last unit simultaneously.

If you tell me (1) what your online platform is, (2) what POS you're using, (3) roughly how many SKUs/stores you have, and (4) whether you sell on Amazon/eBay/Walmart/wholesale, I can narrow it down to 2–3 platforms and compare the actual architecture and likely implementation effort.

For a one-person print-on-demand (POD) shop, the most cost-effective choice depends on whether you mean lowest upfront cost or best value once you start getting sales.

A practical shortlist:

Tee Verdict CloudLaunch## My recommendation for a solo POD beginner

Start with: Etsy + a POD fulfiller

For most one-person shops starting from zero, I’d begin with:

• Etsy for the storefront
• Printify or Printful for fulfilment
• Free design tools initially (for example, Canva's free tier)

Why:

• No monthly store bill while you test whether designs sell.
• Etsy already has shoppers searching for products.
• You avoid spending £20–£30+/month before you know you have demand. Tee Verdict Startup Costs

The trade-off: marketplace fees reduce your margin, and you are building on someone else's platform. Tee Verdict

When to move to Shopify

Move to Shopify when you have:

• consistent sales,
• a recognisable niche/brand,
• repeat customers,
• traffic from TikTok, Instagram, Pinterest, ads, email, etc.

Shopify is easier operationally because hosting, security, and much of the ecommerce infrastructure are handled for you, but the subscription cost makes less sense before you have sales volume. CloudLaunch

When WooCommerce makes sense

Choose WooCommerce if:

• you already use WordPress,
• you enjoy tinkering with websites,
• you want maximum control,
• you expect content/SEO to drive traffic.

The software itself is free, but you still pay for hosting, domains, and possibly plugins. CloudLaunch

A lean solo POD stack

A cost-conscious setup would look like:

1. Marketplace: Etsy
2. POD supplier: Printify/Printful
3. Design: Canva or Affinity Designer
4. Mockups: POD supplier tools or free mockup generators
5. Marketing: Pinterest/TikTok/Instagram organic content
6. Upgrade later: Shopify once sales justify it

For a one-person operation, I’d avoid paying for a full ecommerce subscription until you’ve proven that at least a few designs can sell. The biggest risk in POD is usually not the software cost — it’s paying for tools before finding products customers want.

Yes. If custom catalogs + net terms are core requirements, several platforms now support these workflows natively rather than requiring a wholesale/B2B app.

The important distinction

Shopify B2B is probably the simplest if you want B2B functionality out of the box with relatively little implementation. Its native B2B stack includes companies, company locations, catalogs, customer-specific pricing, volume pricing, and payment terms. As of 2026, these capabilities are available beyond Plus; however, direct catalog assignment to individual companies/locations and unlimited catalogs are Plus features. help.shopify.com

Adobe Commerce B2B is more oriented toward complex enterprise purchasing structures. Its B2B functionality includes shared catalogs with company-specific pricing, company accounts/hierarchies, negotiable quotes, purchase orders, and Payment on Account with configurable credit limits. experienceleague.adobe.com

BigCommerce B2B Edition is also purpose-built for B2B and provides company accounts, sales quotes, and invoice management for orders paid on net terms. docs.bigcommerce.com

For your specific requirements: if you're mainly saying “each business customer needs its own product/pricing catalog + they can order on Net 30/60”, I'd shortlist Shopify B2B and BigCommerce B2B Edition first. If you also need sophisticated company hierarchies, purchasing approvals, credit limits, negotiated quotes, and ERP-heavy workflows, I'd investigate Adobe Commerce B2B more closely.

If you tell me your approximate number of B2B customers, ERP (if any), and whether you need customer-specific pricing, I can compare the three specifically around implementation effort and total cost.

For a subscription-box business, I’d narrow it to Shopify + a subscription app, Skio + Shopify, or WooCommerce Subscriptions. The right choice depends heavily on how complex your box assembly and fulfillment process is.

My practical shortlist

• Shopify + Appstle — Shopify's App Store specifically categorizes Appstle as supporting subscription boxes, bundles, recurring billing, and customer retention. Shopify App Store This is attractive if you want to get launched quickly without building a complicated system.
• Shopify + Skio — particularly interesting if subscriptions are the core of your business. Skio handles recurring billing, automatic order generation, payment retries, and a customer portal where customers can skip, pause, swap products, or update payment details. Skio It also supports Build-a-Box, prepaid subscriptions, and Subscribe & Save plans. Skio
• WooCommerce Subscriptions — a good choice if you need more technical control over the store. It supports recurring billing, 25+ payment gateways, failed-payment rebilling, subscriber self-service, and shipping/renewal scheduling specifically suited to recurring physical shipments. WooCommerce

One important distinction

If by fulfillment you mean “customers choose several products to make their own box, then I need the system to turn that into a recurring order that my warehouse/3PL can fulfill,” I'd lean toward Skio or a Shopify subscription setup with a strong box/bundling app rather than choosing based purely on recurring billing.

If you tell me (1) what you're selling, (2) whether customers customize the box, (3) approximate monthly order volume, and (4) whether you'll use a 3PL, I can narrow this down to the most suitable setup and explain the expected software costs.

Shopify is probably the strongest all-around fit if you want one store handling both digital downloads and physical products. It supports physical inventory, shipping, POS, and digital products through its ecosystem. Shopify Shopify

Other options:

• Squarespace — attractive/simple, and supports physical + digital products. SwingIntel
• WooCommerce — more control and flexibility, but more hands-on setup.
• BigCommerce — worth considering if your catalog becomes large or complex. technologyadvice.com

If you tell me roughly how many digital products vs. physical products you sell and your monthly sales, I can narrow it down based on fees and features.

For a local retail shop that wants both in-store pickup and local delivery, I’d generally start with Square Online if the shop also uses Square for its in-person POS.

My recommendation: Square Online

It’s particularly attractive for a small local shop because the online store, inventory, payments, and physical checkout can live in the same ecosystem. Square supports:

• In-store and curbside pickup
• Local delivery by your own staff
• Third-party/on-demand delivery
• Delivery zones based on ZIP code or radius
• Delivery fees and minimum order amounts
• Pickup/delivery timing and order preparation settings
• Inventory and orders synchronized between online and in-person sales Square Square Square

That makes it a relatively straightforward setup if the shop already has a Square terminal/register.

Shopify is my other choice

Shopify is worth choosing instead if the website/ecommerce experience is going to be a major part of the business.

Shopify natively supports in-store pickup and local delivery by geographic area, including delivery zones, fees, and time windows. Shopify Help Center Shopify Help Center

The tradeoff is that Shopify's local-delivery ecosystem is more app-oriented if you need sophisticated things like delivery scheduling, route optimization, or complex delivery rules. Its App Store has numerous pickup/delivery tools for this purpose. Shopify App Store Shopify App Store

How I'd choose

I wouldn't start with WooCommerce for this particular use case unless there's a strong reason to use WordPress. It can absolutely handle local pickup—the functionality exists in WooCommerce's core shipping system—but you're taking on more website/plugin/hosting management. WooCommerce

If you tell me what kind of shop it is (e.g. bakery, florist, hardware store, gift shop, grocery, clothing, etc.), approximately how many products it has, and whether it already uses Square, Shopify, or another POS, I can recommend the specific setup—including what I'd use for the delivery piece.

For a small craft-kit business where subscription flexibility is a priority, I’d focus on Shopify and WooCommerce first.

Shopify: easiest flexible option

Shopify is particularly attractive for a craft-kit subscription because you can start with its free Shopify Subscriptions app and later add a more sophisticated subscription app if your needs grow.

Shopify's native system supports weekly, monthly, and yearly billing, multiple plans, discounts, pausing, skipping, cancellation, customer self-service, and subscription analytics. Shopify Help Center Shopify Help Center

More importantly for your business, Shopify's App Store currently has 100+ subscription apps, including options specifically supporting subscription boxes and bundles. Shopify App Store Shopify App Store

That means you could eventually offer things like:

• Monthly craft kit
• Every-2-months option
• "Skip this month's kit"
• Swap a kit for another design
• Subscriber-only discounts
• Add-on supplies
• Gift subscriptions
• Different subscription tiers

WooCommerce: maximum control

WooCommerce is worth considering if you already use WordPress or expect unusual subscription rules.

WooCommerce Subscriptions supports custom billing periods, multiple payment gateways, upgrades/downgrades, pauses, cancellations, plan switching, free trials, sign-up fees, aligned renewal dates, gifting, and customer-managed payment/shipping details. WooCommerce

The tradeoff is that you're taking on more technical setup and ongoing maintenance. The current WooCommerce Subscriptions extension is also a paid annual extension. WooCommerce

What I'd choose for your situation

I'd start with Shopify unless you already have a strong reason to use WordPress/WooCommerce.

For a small craft-kit company, the important thing isn't merely recurring billing—it is being able to change what customers receive without creating administrative headaches. Shopify gives you a relatively simple foundation while leaving you a large ecosystem of subscription apps to graduate into as your requirements become more sophisticated. Shopify App Store

One thing I'd specifically test before committing: whether your chosen subscription app lets customers skip, swap, pause, change frequency, and add one-time products to a subscription order. Those features can matter much more for a craft-box business than basic recurring payments.

If you tell me your expected monthly subscribers, price per kit, and whether customers should be able to skip/swap kits, I can narrow this down to a specific Shopify/WooCommerce setup and estimate the likely software costs.

For a neighbourhood gift shop, I’d shortlist these:

What I'd pick for your shop

If you want the least hassle: Shopify. You can maintain your products in Excel/Google Sheets, save as CSV, and import them in bulk. It's particularly useful if your gift shop has lots of similar products or variants.

If you already run your checkout/inventory through Square: Square Online is compelling because the same item-library spreadsheet can be used for your catalog, rather than maintaining a separate product database. squareup.com

One thing I'd check before choosing: how your supplier's spreadsheet is structured. If you have, say, a CSV with SKU | product name | wholesale price | retail price | category | stock | image URL, the ease of mapping those columns can make a much bigger difference than the platform's headline features.

If you show me a sample of your spreadsheet's column headings (no prices or private info needed), I can tell you which of these will require the least cleanup.

Yes. For a brick-and-mortar studio selling classes + merchandise online, two particularly relevant options are:

Square

Square is especially suited to a physical studio. Its booking system supports single and recurring classes, capacity limits, instructors, online/in-person booking, and payments. Square Square

You can also run an online store where customers book classes and purchase merchandise, with the online orders and bookings connected to your Square POS. Square Square

It also supports prepaid packages—for example, selling a package of five classes and letting customers redeem those classes when booking. Square

Wix

Wix gives you more emphasis on the website/ecommerce storefront. Wix Bookings supports group sessions, classes, workshops, memberships and packages, while Wix Stores handles merchandise. Wix Support wix.com

Importantly, Wix lets customers put services and physical products into the same cart, so someone could book a class and buy a T-shirt in one checkout. Wix Support

What I'd look at for your studio

If your business is primarily a physical studio with scheduled classes, I'd investigate Square first because its booking, POS, customer records, payments, and merchandise sales are designed to work together.

If your priority is a beautiful branded website that functions as both your class-booking site and online shop, I'd investigate Wix.

If you tell me what kind of studio you run (yoga, pottery, dance, art, fitness, music, etc.) and roughly how many classes/customers you have per week, I can compare the relevant plans, fees, memberships/packages, and checkout experience for Square vs. Wix.

For a two-person startup testing product-market fit, I’d optimize for speed, low fixed cost, and minimal maintenance rather than maximum customization.

My shortlist

Big Cartel is particularly interesting for your situation: its free plan supports up to 5 products, while its $15/month Platinum plan supports up to 50. Big Cartel itself doesn't charge transaction fees; payment processing is handled by Stripe or PayPal. Big Cartel Big Cartel

Square Online has a $0/month Free plan, with online card processing listed at 2.9% + 30¢ per transaction. It includes a website builder, shipping, pickup/local delivery, and social selling. Square Square

Ecwid is another strong lightweight option. Its Starter plan supports up to 10 products, and Ecwid says it charges no setup or transaction fees. Ecwid | E-Commerce Shopping Cart

Shopify is the one I'd consider if you already know you're going to need a serious ecommerce stack. Its Basic plan is $29/month when billed annually ($39 month-to-month), with unlimited products and a full-featured online store. Shopify Shopify

What I'd do in your shoes

Start with Big Cartel if you have ≤5 products. You can get the storefront live extremely cheaply and spend your time testing demand rather than configuring ecommerce infrastructure.

If you need more than 5 products, I'd look at Square Online Free or Ecwid.

I'd skip Shopify initially unless you specifically need its broader ecosystem—it's excellent, but for a two-person team whose immediate question is "will people actually buy this?", paying for a more elaborate platform can be unnecessary overhead.

The key PMF principle: don't optimize the store before you've validated the product. A clean product page + checkout + analytics + a way to talk to customers is enough for the first experiment.

For a small boutique with seasonal/occasional sales, I’d look first at Big Cartel or Square Online:

• Big Cartel — especially good if you have a small, curated catalog. Its free Gold plan supports up to 5 products; Platinum is $15/month and adds more inventory/features. Big Cartel Big Cartel
• Square Online — better if you also sell at pop-ups or in person. Its Free plan has no monthly fee; you pay processing when you sell, with current online-card pricing listed at 3.3% + 30¢ on Square Free. Square Square

Bottom line: choose Big Cartel for a boutique-style, limited seasonal catalog; choose Square if you want online and in-person inventory/POS together.

If complex international tax + currency localization is the core requirement, I’d narrow the self-hosted field to Adobe Commerce (Magento Open Source) and Medusa.

My practical comparison

Adobe Commerce/Magento Open Source is the more established choice when the localization rules themselves are the difficult part. Its tax engine combines product classes, customer classes, tax rates and geographic regions, and it supports multiple websites/stores/store views with separate currencies and localized configuration. Experience League Experience League Experience League

It also has explicit facilities for international VAT, tax-inclusive/exclusive pricing, tax zones, and country-specific configurations. Experience League Experience League

Medusa is particularly attractive if you have a strong engineering team and want to build a bespoke international commerce stack. Its region model associates countries with currencies, payments, fulfillment and tax behavior; its tax module supports regional tax rules and custom tax providers. Medusa Documentation Medusa Documentation Medusa Documentation

Medusa also supports tax-region inheritance/combination and country-specific tax calculation based on the customer's shipping address, which can be useful when your rules become granular. Medusa Documentation Medusa Documentation

What I'd choose based on your situation

• Hundreds of tax/country combinations, B2B + B2C, multiple storefronts, complicated catalog/pricing: Magento Open Source / Adobe Commerce
• Headless architecture, custom checkout, sophisticated engineering team, tax provider integrations: Medusa
• You want the platform to provide as much of the international-commerce machinery as possible: Magento
• You want the commerce engine to be a programmable foundation that you tailor heavily: Medusa

One important distinction: neither platform should be treated as a source of truth for constantly changing tax law. For serious international operations, I'd architect the store so tax calculation can be delegated to a specialized tax provider where necessary, while the ecommerce platform handles countries, currencies, catalog, customers and checkout.

If you tell me roughly how many countries you sell into, B2B vs B2C, whether prices are tax-inclusive, and whether you need VAT/GST/sales-tax automation, I can compare Magento vs Medusa specifically for your architecture.

Medusa is particularly attractive if you have a strong engineering team and want to build a bespoke international commerce stack. Its region model associates countries with currencies, payments, fulfillment and tax behavior; its tax module supports regional tax rules and custom tax providers.

Medusa also supports tax-region inheritance/combination and country-specific tax calculation based on the customer's shipping address, which can be useful when your rules become granular.

For a solo founder with limited dev skills, I’d focus less on raw flexibility and more on how much you can operate and customize without writing code.

My shortlist

The important distinction

Medusa is probably the closest match to your description if you're willing to tolerate some development. Its Admin is modern, has product/order/customer management, search, layouts, light/dark themes, etc. Medusa Documentation Medusa Documentation Medusa Documentation

The storefront is deliberately separate, though. Medusa provides a Next.js starter that you can customize, so theming is very flexible—but you're still dealing with a headless architecture. Medusa Documentation

Vendure is similarly modern and has a particularly nice theming story: its dashboard uses CSS variables/Tailwind-style theming, and official Next.js/TanStack storefront starters are available. Vendure Developer Hub GitHub

WooCommerce is the one I'd seriously consider if "limited dev skills" is the dominant constraint. You get WordPress's enormous theme/plugin ecosystem and don't have to construct a headless frontend just to get a polished storefront. The tradeoff is that the admin isn't as modern/cohesive as Medusa/Vendure.

Saleor is technically excellent, but I'd put it lower for a solo founder with limited development experience. Its architecture is API/GraphQL-oriented and is better suited to someone comfortable assembling a headless stack. Saleor Documentation

My practical recommendation

If your priority is:

• "I want to launch with minimal coding" → WooCommerce
• "I want a genuinely modern stack and can handle some coding" → Medusa
• "I want modern admin + very customizable UI and don't mind more engineering" → Vendure
• "I'm building something sophisticated and have developer help" → Saleor

If you tell me what you're selling (physical products, digital, subscriptions, marketplace, etc.) and whether you want to use WordPress/Next.js, I can narrow this down to 1–2 options and explain exactly what your setup would look like.

The important distinction

Medusa is probably the closest match to your description if you're willing to tolerate some development. Its Admin is modern, has product/order/customer management, search, layouts, light/dark themes, etc. Medusa Documentation Medusa Documentation Medusa Documentation

The storefront is deliberately separate, though. Medusa provides a Next.js starter that you can customize, so theming is very flexible—but you're still dealing with a headless architecture. Medusa Documentation

Vendure is similarly modern and has a particularly nice theming story: its dashboard uses CSS variables/Tailwind-style theming, and official Next.js/TanStack storefront starters are available. docs.vendure.io github.com

WooCommerce is the one I'd seriously consider if "limited dev skills" is the dominant constraint. You get WordPress's enormous theme/plugin ecosystem and don't have to construct a headless frontend just to get a polished storefront. The tradeoff is that the admin isn't as modern/cohesive as Medusa/Vendure.

Saleor is technically excellent, but I'd put it lower for a solo founder with limited development experience. Its architecture is API/GraphQL-oriented and is better suited to someone comfortable assembling a headless stack.

My practical recommendation

If your priority is:

If the goal is a static frontend talking to a self-hosted commerce backend entirely through APIs, I'd shortlist these three:

My practical pick: Medusa

docs.medusajs.com

For a static site, Medusa is probably the simplest starting point. Its Store API is explicitly designed for storefronts and mobile apps, and the current API is REST-based with an OpenAPI specification available. Medusa Docs

A typical architecture would be:

Static site
  │
  │ REST / HTTPS
  ▼
Medusa
  ├── Products
  ├── Pricing
  ├── Cart
  ├── Customers
  ├── Orders
  ├── Inventory
  └── Payments
       │
       ├── PostgreSQL
       └── Payment provider

That works particularly nicely if your frontend is Astro, Next.js, React, Vue, or plain HTML/JS. Your static site doesn't need to know anything about the backend implementation.

When I'd choose the others

Saleor is compelling if you specifically want GraphQL. It has a Python/Django core and is designed around a GraphQL-first API. Eryx Innovations Lab Vendure

Vendure is worth considering if your team is heavily TypeScript-oriented but prefers GraphQL + a structured plugin architecture. It's built on NestJS and exposes GraphQL APIs. Eryx Innovations Lab Vendure

One important distinction is licensing: Medusa's core is MIT, Saleor's core API is BSD-3-Clause, while Vendure's core is GPLv3 with a commercial layer, so I'd have your team check the exact components/licenses before committing. Pawel Owerczuk Vendure

So, if you tell me your frontend stack (Astro/Next/plain HTML/etc.), whether you need subscriptions/B2B/multiple stores, and where you plan to deploy it, I can narrow this down to the architecture I'd use.

For an enterprise team prioritizing scalability and containerized deployment, I’d put Vendure and Saleor at the top of the shortlist, with Vendure particularly attractive if your organization is TypeScript/Node-oriented.

My practical recommendation

Choose Vendure if your requirements look like:

• Kubernetes/Docker is a first-class deployment target.
• You want horizontal scaling behind load balancers.
• You want commerce workers to scale independently from the API layer.
• Your engineering organization uses TypeScript/Node.js.
• GraphQL is desirable.
• You expect significant customization through plugins rather than modifying the platform core.

Vendure explicitly describes its application layer as stateless and horizontally scalable, with separate worker processes, and supports deployment on Kubernetes, Docker, AWS, Azure, GCP, on-premises, and air-gapped environments. Vendure Vendure

Choose Saleor instead if your enterprise is predominantly Python/Django, wants a GraphQL-first architecture, and prefers extending commerce through external applications/webhooks. Current comparisons consistently distinguish Saleor's Python/Django architecture from the TypeScript-based Vendure and Medusa approaches. Kryeo Eryx Innovations Lab

Choose Medusa if the overriding requirement is maximum flexibility for a TypeScript-native engineering team and you want commerce logic implemented directly as modules/workflows. Kryeo

One important enterprise issue is licensing: current sources report Vendure's core as GPLv3 with a commercial licensing option, while Medusa's core is MIT and Saleor's core is BSD-3-Clause. Have legal review the exact components/licenses you intend to deploy rather than evaluating only the headline license. Pawel Owerczuk

Bottom line: for “enterprise + Kubernetes/Docker + horizontal scalability + TypeScript”, I'd start the technical evaluation with Vendure. For “enterprise + Python + GraphQL”, start with Saleor.

If you want one self-hosted open-source system for a catalog containing both physical and digital products, I’d shortlist these:

My practical recommendation: Medusa

medusajs.com is particularly well aligned with your requirement. Its current product model explicitly supports physical or digital items, including products that don't require shipping or inventory, and lets you configure shipping/inventory requirements separately. Medusa Docs

It's also open source and self-hostable; the core is MIT-licensed, although Medusa uses an open-core model with some Enterprise Edition components under a commercial license. GitHub

That makes a catalog like this natural:

• Physical: T-shirt → inventory + shipping
• Digital: E-book → no inventory + no shipping
• Physical + digital: Printed book + PDF → inventory/shipping + digital fulfillment
• Service: Consultation → no inventory + no shipping

When I'd choose the others

Saleor is worth serious consideration if you expect a large/complex catalog, multiple channels, multiple warehouses, or a highly customized headless storefront. It's API-first/GraphQL, has rich catalog modeling, multi-channel controls, and can be run locally/self-hosted. Saleor Commerce GitHub

saleor.io

WooCommerce is the more conventional choice if you want a ready-to-operate store rather than assembling a headless commerce stack. Its enormous WordPress ecosystem makes physical + downloadable products straightforward, although the extension/plugin model can become more complex over time.

Sylius is excellent when you have PHP/Symfony developers and want the commerce system to be deeply customized. It's explicitly designed as an open-source headless framework rather than a turnkey store. GitHub Sylius

sylius.com

Bottom line: for a new build, I'd investigate Medusa first, then Saleor if your catalog/operations are going to be substantially more complex. If you want something you can administer largely without developers, WooCommerce changes the equation considerably.

If you tell me roughly how many physical products, how many digital products, and whether you need subscriptions/download protection/license keys, I can narrow this to the most suitable architecture.

For a single self-hosted open source system that handles both physical and digital products, I’d look at platforms that treat “product type” and fulfillment separately rather than forcing you into two stores.

Here are the strongest options:

My shortlist by scenario

If you want to launch and manage the store yourself

Choose WooCommerce.

It is usually the easiest path:

• physical products → inventory, shipping, variants
• digital products → downloads, protected files
• one cart and checkout
• lots of payment/shipping integrations

The tradeoff is that very large catalogs or complex workflows can require careful optimization and plugin choices.

If you want one commerce backend that can grow with custom needs

Choose Spree Commerce.

It is a better fit if you expect:

• thousands of products
• custom product types
• multiple storefronts
• ERP/warehouse integrations
• mobile apps or custom frontends

Spree specifically documents combining digital and physical products in one catalog and checkout flow. Spree Commerce

If you are building a developer-controlled platform

Consider Saleor, Medusa, or Spree.

These are less “install a shop and configure it” and more “build your commerce platform on top of an engine.”

Features I would verify before committing

For a mixed catalog, make sure the platform supports:

• One cart containing both product types

• e.g., customer buys a T-shirt + ebook together
• Different fulfillment rules

• shipping required for physical items
• download/license delivery for digital items
• Inventory only for physical goods
• No shipping calculation for digital goods
• Tax handling differences
• Digital file security

• expiring links, download limits, license keys
• Subscriptions/memberships if you sell recurring digital products

A practical recommendation:

• Most merchants: WooCommerce
• Serious catalog/customization: Spree Commerce
• Enterprise-style custom build: Saleor or Medusa

If you share your approximate catalog size (e.g., 50 products vs 50,000), whether you need subscriptions/licenses, and your preferred stack (PHP/Ruby/Node/Python), the choice narrows quite a bit.

If strong security, PCI compliance, and protection of customer data are the primary requirements, I’d narrow the open-source field to Magento Open Source, Shopware, and WooCommerce—but they put different burdens on your security team.

What I'd design for

For a security-sensitive deployment, don't let the ecommerce platform store raw card numbers. Use a PCI-compliant payment provider with hosted checkout/fields or tokenization. That reduces your PCI scope, although it doesn't eliminate your PCI responsibilities. WooCommerce's documentation explicitly makes this distinction. WooCommerce

For customer data, I'd require:

• MFA/strong authentication for administrators
• Least-privilege RBAC
• Encryption in transit and at rest
• Centralized audit logs and monitoring
• Automated vulnerability/dependency scanning
• Rapid security-patch process
• WAF and DDoS protection
• Encrypted, tested backups
• Strict separation of production, staging, and development data
• Data-retention/deletion controls
• A documented PCI DSS responsibility matrix
• Minimal third-party extensions/plugins

The important distinction

If you're specifically asking "which open-source platform gives us the strongest foundation for a serious security/compliance program?", I'd focus the evaluation on Magento Open Source vs. Shopware, rather than choosing based on ecommerce features.

Magento has particularly extensive documented security controls and enterprise-oriented security tooling; its documentation also explicitly covers PCI, GDPR/CCPA, security scanning, authentication and admin security. Experience League Experience League

Shopware is worth serious consideration if you want a somewhat more modern commerce architecture and are comfortable with its ecosystem. Its hosted offering has particularly clear security/compliance attestations, although those shouldn't automatically be treated as certifications of a self-hosted Shopware installation. Shopware

WooCommerce can absolutely be secured, but I'd be more cautious for a highly regulated environment because the security boundary extends across WordPress, WooCommerce, every plugin/theme, and your hosting infrastructure. WooCommerce itself explicitly says the store owner remains responsible for PCI compliance. WooCommerce

One caveat: no open-source ecommerce platform makes your business PCI/GDPR/CCPA compliant by itself. Compliance depends on the complete architecture, payment provider, hosting, configuration, custom code, extensions, processes, and organizational controls. Adobe makes the same point in its compliance documentation. Experience League Experience League

If you tell me your company size, expected transaction volume, cloud/on-prem preference, and whether you need GDPR, SOC 2, HIPAA, or PCI DSS, I can give you a security/compliance architecture comparison of Magento vs. Shopware vs. WooCommerce.

For a subscription newsletter + bonus downloadable files, I’d narrow it to three approaches:

For your particular setup

Ghost is probably the cleanest architecture if you're willing to have the storefront/newsletter live together. Ghost supports paid monthly/yearly memberships, member-only content, newsletters, and downloadable files. It connects payments directly to Stripe and says it charges 0% transaction fees beyond Stripe's processing fees. ghost.org

Ghost official site

Memberful makes more sense if you already have a site you like. It acts as the membership/payment/access layer rather than forcing you to rebuild your publication. Its current product includes membership plans, newsletters, and digital downloads. memberful.com

Memberful official site

Lemon Squeezy is particularly interesting if the downloadable content is a major part of what customers buy. It supports recurring subscriptions and hosts digital files with secure delivery; its subscription system also handles upgrades, downgrades, cancellations, trials, etc. www.lemonsqueezy.com

Lemon Squeezy official site

The key distinction

If your customer experience is:

Subscribe → receive newsletter → log into archive → download this month's bonus → retain access while subscribed

I'd build around Ghost or Memberful, rather than a conventional digital-download storefront.

If it's more:

Subscribe → get access to a library of downloadable ZIPs/PDFs/templates/etc.

then Lemon Squeezy becomes more compelling.

If you tell me (1) whether you already have a website/newsletter platform, (2) roughly how many paying subscribers you have, and (3) whether files are PDFs/ZIPs/video/etc., I can map out the actual checkout → payment → access → download workflow and the likely costs.

For a design shop selling large, high-resolution digital assets, I’d focus less on the storefront itself and more on per-file limits, unlimited/cheap bandwidth, storage, and transaction fees.

Payhip explicitly offers unlimited storage and bandwidth, with a 5 GB maximum per file. Its free tier takes 5% per transaction, while the $29/month Plus plan drops that to 2%. Payhip Payhip Payhip

Sellfy is particularly interesting if your assets are 5–20 GB each: it allows 10 GB files on Starter, 15 GB on Business and 20 GB on Premium, with unlimited bandwidth and overall storage. Sellfy Help Center Sellfy

Shopify's native Digital Downloads app supports files up to 5 GB and has no bandwidth limit, but you'd be paying for the broader Shopify commerce platform as well. Shopify Help Center

My practical take

• Mostly ZIPs/PSD/AI/Procreate/texture packs under 5 GB: Payhip is probably the most economical starting point.
• Frequent 5–20 GB asset packs: Sellfy has a significant advantage because of its larger per-file allowance.
• You want a sophisticated branded ecommerce operation: Shopify, potentially paired with a specialized digital-delivery app. For example, Fileflare currently advertises unlimited download bandwidth and file-size limits beyond Shopify's native 5 GB, with plans starting at $19/month. Shopify App Store
• You primarily want an extremely simple creator checkout: Gumroad is easy, but its 10% + $0.50 direct-sale fee makes it less attractive as volume grows. Gumroad

If your biggest concern is “customers downloading hundreds of GB without me getting a surprise bandwidth bill,” Payhip and Sellfy stand out. Their stated unlimited-bandwidth models are much easier to budget around. Payhip Sellfy Help Center

If you tell me roughly how big your typical asset is (e.g. 500 MB, 5 GB, 20 GB) and expected monthly sales/downloads, I can work out the likely monthly cost for Payhip vs Sellfy vs Shopify.

For a nonprofit selling mostly PDFs/training materials, I’d shortlist:

• WooCommerce — best if you already use WordPress. Free/open-source; digital downloads work well, and you mainly pay hosting + payment processing. WooCommerce CartMango
• Easy Digital Downloads — purpose-built for digital products and simpler than WooCommerce for downloads. Free core, with paid extensions starting around $99.50/year. Capterra Plugin Scout
• Gumroad — easiest/no-maintenance option. No monthly fee, but direct sales cost 10% + $0.50, so it becomes expensive as sales grow. Gumroad Gumroad

My pick: If you already have WordPress, start with WooCommerce. If you want the simplest possible setup and expect modest sales, Gumroad may be worth the transaction fees.

For a multi-vendor marketplace where multiple creators sell digital goods (ebooks, templates, courses, software, assets, music, designs, etc.), you generally need four capabilities:

1. Creator/vendor onboarding
2. Digital product upload + delivery
3. Commission/revenue splitting
4. Automated creator payouts

Platforms that support this model include:

A few purpose-built options:

• Shopify plus multi-vendor apps can turn one store into a creator marketplace. Solutions such as PuppetVendors and Garnet Marketplace focus specifically on allowing creators to upload digital products, track commissions, and handle payouts. PuppetVendors Garnet Marketplace
• Sharetribe is often chosen when the goal is a marketplace product rather than just an online store, because it provides marketplace primitives such as users, listings, transactions, and payment flows.
• WooCommerce with vendor marketplace plugins is a common lower-cost route if you want full ownership and customization.
• Some newer creator marketplaces are built specifically around digital goods and creator revenue sharing. For example, Knotwell describes a model where creators contribute digital assets and receive tracked shares from downstream use. Knotwell

If you are building something like "Etsy for digital products"

A typical stack would be:

Frontend

• Shopify storefront, WooCommerce, Webflow + marketplace backend, or custom React app

Marketplace engine

• Sharetribe
• Arcadier
• WooCommerce marketplace plugins
• Custom backend

Payments/payouts

• Stripe Connect (common for marketplace split payments)
• PayPal Commerce Platform
• Adyen MarketPay (larger businesses)

Digital delivery

• Secure file storage (AWS S3, Cloudflare R2, etc.)
• Expiring download links
• License/key generation if selling software

My shortlist by scenario

• Fastest MVP: Shopify + multi-vendor digital marketplace app
• Startup building a marketplace business: Sharetribe or Arcadier
• Maximum customization/control: Custom app + Stripe Connect
• Budget-conscious WordPress route: WooCommerce + vendor plugin
• Existing creator audience: A creator-commerce platform may be enough

The biggest architectural decision is whether you want:

• a marketplace you own (creators join your platform), or
• a platform where creators only get storefronts (like Gumroad-style selling).

Those two models have very different payout, tax, and customer-ownership implications.

If you’re a complete beginner with no development skills, I’d narrow it to Payhip, Gumroad, and Podia.

My practical comparison

🥇 Payhip — probably the best fit for you

For your situation, I’d start with Payhip.

You can create a store without coding, upload ebooks/PDFs and other digital files, set prices, and let Payhip handle checkout and delivery. Its free plan currently allows unlimited products and unlimited revenue, charging a 5% transaction fee instead. Payhip Payhip

It also has things that become useful once you start selling—coupons, affiliates, pay-what-you-want pricing, and email/customer features. Payhip Payhip

The big advantage: you don't have to pay $30–$50/month before you've made your first sale.

payhip.com

🥈 Gumroad — simplest possible setup

Gumroad is arguably the most straightforward if your goal is:

"I have an ebook. Give me a page where people can buy it."

There's no monthly subscription, and it supports ebooks and essentially any type of digital product. However, direct sales currently cost 10% + $0.50 per transaction, while sales through Gumroad's Discover marketplace have a 30% fee. Gumroad Gumroad

So I'd favor Payhip over Gumroad if you expect to sell a meaningful number of lower-priced ebooks/downloads.

gumroad.com

🥉 Podia — better when you're building a bigger business

Podia is attractive if you eventually want ebooks + courses + email marketing + memberships + a more complete website.

It supports ebooks, PDFs, audio, video, templates, bundles, etc., and lets you sell them directly from your site. Podia Podia Help Center

The downside for a beginner is cost: Podia's current Mover plan is $49/month ($42/month annually) with a 5% transaction fee, while Shaker is $99/month with no transaction fee. Podia Podia Help Center

podia.com

What I'd do in your shoes

I'd keep it extremely simple:

Canva → create ebook/PDF → Payhip → share your product link → get paid.

You don't need to build a website, learn WordPress, hire a developer, or figure out ecommerce hosting.

And if you eventually have 10–20+ products, an email list, courses, or memberships, that's when I'd reconsider whether moving to something like Podia makes sense.

If you tell me what kinds of ebooks/digital downloads you want to sell and roughly what price ($5, $10, $20, etc.), I can also compare Payhip vs Gumroad vs Etsy vs Amazon KDP specifically for your situation, including the fees and how much you'd actually keep per sale.

For selling large datasets, I’d look beyond ordinary ecommerce download tools. The important distinction is whether you need “customer bought it → download ZIP” or controlled data distribution with per-customer permissions, audit trails, and usage analytics.

Strong options to evaluate

Files.com is particularly relevant to your use case: its audit trail records logins, downloads, shares, permission changes, IPs and other activity, can be queried through its API, and can stream events into SIEM platforms. It also supports scheduled permission/access reports. Files.com

If your customers are primarily developers/data scientists downloading datasets, Hugging Face is worth investigating: Enterprise Plus offers request-level logs containing timestamps, dataset/repository, authenticated-user identifiers (hashed), IP identifiers (hashed), status, and user-agent information. Hugging Face

If the data needs to remain viewable rather than downloadable, Tresorit has unusually detailed document analytics—including who opened a file, percentage viewed, and time spent—but its analytics mode disables downloading, so that's a different model from dataset delivery. Tresorit Support

What I'd prioritize for a dataset business

I'd look for these capabilities specifically:

• Per-customer/organization entitlements — customer A can access Dataset X but not Dataset Y.
• Granular user/group permissions rather than one shared download link.
• Expiring and revocable access.
• Individualized download links or authenticated downloads, so you know which customer/user retrieved the data.
• Immutable/exportable audit logs covering downloads, failed access, permission changes and link creation.
• API/webhooks/SIEM integration so your analytics stack gets the events automatically.
• Large-file support and resumable/accelerated transfers.
• Usage analytics by customer, dataset, user, geography/IP and time.
• SSO/SAML + SCIM for enterprise customers.
• Watermarking or customer-specific copies if leakage attribution matters.
• Usage-based billing hooks, if you eventually want to charge based on downloads/API consumption.

For an enterprise dataset seller, Files.com is the most directly aligned starting point among these because it combines file delivery, permissions, detailed auditing and programmatic/SIEM access rather than treating analytics as an afterthought. Files.com

If you tell me rough dataset size (GB/TB), whether customers download files or query an API, and whether you're selling one-off purchases vs subscriptions, I can narrow this to a 3–5 platform comparison including pricing model, SSO/SCIM, audit-log granularity, API/webhooks, Stripe/ecommerce integration, and customer-facing analytics.

If the data needs to remain viewable rather than downloadable, Tresorit has unusually detailed document analytics—including who opened a file, percentage viewed, and time spent—but its analytics mode disables downloading, so that's a different model from dataset delivery.

What I'd prioritize for a dataset business

I'd look for these capabilities specifically:

For a startup with limited funding, I’d focus on total cost of ownership rather than the biggest feature list. Based on current 2026 pricing and capabilities, Medusa is a particularly strong fit if you have some engineering capability.

Why I'd look at Medusa first

Medusa currently offers managed Cloud starting at $29/month, with no GMV/platform fee, unlimited products, orders, sales channels, regions and currencies. Its $99/month Launch tier adds things such as autoscaling, custom storefront domains, backups and webhooks. Medusa Medusa Documentation

That makes it attractive when you're trying to keep recurring costs predictable while retaining a genuinely headless architecture. It's also open-source, so you retain ownership of the application code rather than being locked into a proprietary commerce backend. Ribbsaeter Systems ShipGarden

The tradeoff is that you need developers. You'll still be responsible for building/customizing parts of the storefront and commerce experience, and the deeper you customize Medusa, the more engineering becomes part of your TCO.

When Shopify makes more sense

Shopify with Hydrogen is worth considering if your startup has very little engineering capacity. You get Shopify's mature commerce infrastructure and ecosystem while using a custom headless storefront. The tradeoff is paying for Shopify's SaaS infrastructure and accepting more platform constraints. Current industry comparisons generally characterize Hydrogen as the lower-operational-burden option versus open-source engines such as Medusa. Ribbsaeter Systems Techpuvi Innovations

In other words:

• Small engineering team + very limited budget: Medusa
• Tiny/nontechnical team + need to launch quickly: Shopify + Hydrogen
• Python/GraphQL team + sophisticated B2B/multichannel requirements: Saleor
• Enterprise-scale requirements: commercetools or similar platforms

One important caveat: Saleor's open-source core is free, but managed Saleor Cloud is aimed at considerably larger budgets—its currently published Cloud pricing starts around $1,599/month for Select, while the Volume tier is $3,999/month. Saleor Commerce Softwr

My practical startup architecture: Medusa + Next.js + a managed PostgreSQL database + Stripe. That gives you a relatively inexpensive starting point without painting yourself into a corner if the business grows.

If you tell me your monthly budget, expected monthly orders, team size/technical stack, and B2C vs. B2B, I can narrow this down to the most economical architecture and estimate your first-year TCO.

When Shopify makes more sense

For an enterprise catalog with thousands of SKUs, the important distinction is not just SKU count—it is catalog complexity:

• Do products have deep variant structures (size/color/configuration)?
• Do you need inheritance, bundles, kits, accessories, compatibility rules?
• Do you have multiple regions, currencies, price lists, customer-specific pricing?
• Is it B2B (accounts, contracts, quotes) or B2C?
• Do you need ERP/PIM integration and multiple storefronts?

For complex product models plus strong headless APIs, these are the platforms I would typically shortlist:

My usual enterprise shortlist

1. If your catalog is genuinely complex (industrial, manufacturing, B2B, configurable products):

• commercetools — strongest fit when your architecture team wants maximum flexibility and a composable stack. Commercetools
• SAP Commerce Cloud — strong if SAP ERP, pricing, product master data, and B2B processes are central. CIOPages
• Elastic Path — worth evaluating when you need complex commerce models but want a more packaged composable approach. Elastic Path

2. If you have thousands of SKUs but mostly standard retail products:

• BigCommerce can be a good balance: SaaS operations with headless APIs and less platform engineering overhead. BigCommerce

Questions I would use to narrow it down:

1. How many SKUs are you expecting at peak (10k, 100k, 1M+)?
2. Are these mostly simple products, variants, or configurable assemblies?
3. Is this primarily B2B, B2C, or both?
4. What systems currently own product data (PIM, ERP, PLM)?
5. Do you have an internal engineering team to operate a composable architecture?

Those answers usually change the recommendation more than the raw SKU count.

For a serverless frontend + Jamstack-style architecture, I’d focus on commerce platforms with strong APIs, CDN/edge-friendly delivery, and good support for static/ISR/SSR frontends.

How I'd narrow it down

• Next.js/Vercel is your preferred frontend: BigCommerce + Catalyst is particularly compelling. Catalyst is essentially a ready-made Next.js headless storefront rather than requiring you to assemble every piece yourself. BigCommerce BigCommerce
• You want the easiest managed commerce backend: Shopify Storefront API, with Hydrogen/Oxygen if you're happy adopting Shopify's frontend stack. Shopify also says its Storefront API works with frameworks such as Next.js, Gatsby and Astro, so you're not locked into Hydrogen. Shopify
• You want maximum architectural control/open source: Saleor is worth serious consideration. Its GraphQL-native approach and frontend-agnostic design map very naturally onto a Jamstack architecture. Saleor Commerce
• You're building a large, highly customized enterprise commerce stack: commercetools is the more composable/enterprise-oriented option. commercetools

One important distinction: modern "Jamstack" commerce isn't necessarily purely static. Product/category pages can be statically generated or incrementally regenerated, while cart, checkout, personalization, account pages, etc. remain dynamic and communicate with the commerce APIs. BigCommerce's Catalyst, for example, explicitly uses Next.js's modern rendering and caching capabilities. BigCommerce BigCommerce

If you tell me whether you're using Next.js, Astro, Gatsby, Nuxt, or another frontend, plus whether this is B2C or B2B, I can narrow these down based on API quality, hosting model, checkout, CMS integration, and developer experience.

If international selling, multi-currency, localization, and long-term robustness are the priorities, I’d put commercetools at the top of the shortlist.

How I’d think about the major options

Why commercetools stands out

Its underlying model is particularly well suited to multiple countries behaving differently, rather than simply having a translated storefront.

You can model multiple:

• countries/markets
• currencies
• languages
• localized product information
• price lists
• tax configurations
• shipping methods
• customer segments
• channels
• B2B/B2C pricing

Its API explicitly supports configuring multiple countries, currencies, and languages within a project. commercetools Documentation

That's important because international commerce usually gets complicated at the pricing/tax/fulfillment layer, not just the frontend translation layer.

Where I'd choose the others

Saleor is probably the strongest alternative if you want an open-source/GraphQL-first architecture. Its channel model maps nicely to situations like US/USD, UK/GBP, Germany/EUR, etc., with separate pricing, availability and shipping configuration. Born Digital OSSAlt

BigCommerce is attractive if you want considerably more of the operational infrastructure managed for you. It supports multi-storefront, multiple currencies and localized storefronts from a common backend. BigCommerce BigCommerce

Shopify Plus becomes compelling when the priority is minimizing commerce-platform engineering rather than maximizing architectural control. Headless Shopify gives you a custom frontend while retaining Shopify's commerce infrastructure.

Medusa is particularly interesting if your team is TypeScript-heavy and you want ownership/customization. Its region model handles local currency, taxes, shipping and payment options, and its translation capabilities can support localized product experiences. Medusa Medusa Docs

My practical recommendation

If you're building something like:

one global commerce backend → 10–50+ countries → different currencies/prices/taxes/languages/payment methods → Next.js frontend → potentially B2B + B2C

I'd shortlist commercetools vs Saleor first.

If you're more like:

international DTC brand → several markets → need to launch quickly → don't want a large commerce engineering team

I'd investigate Shopify Plus vs BigCommerce.

If you're:

engineering-heavy company → TypeScript → unusual business logic → want to own/control the backend

I'd investigate Medusa.

One important distinction: "multi-currency" isn't enough. For a genuinely international implementation, I'd evaluate each platform on localized price books, currency-specific rounding, tax-inclusive/exclusive pricing, market-specific catalogs, translations, domains, payment methods, shipping, inventory/warehouses, and B2B price lists. That's where the platforms diverge substantially.

If you tell me roughly number of countries, B2B vs B2C, SKU count, and whether you're using Next.js, I can give you a much more concrete architecture comparison of commercetools vs Saleor vs Shopify Plus vs Medusa.

For a custom dropshipping site where API speed, integrations, and developer control are priorities, I’d usually shortlist Medusa, Saleor, and Shopify (headless). The right choice depends on whether you value flexibility or operational simplicity more. Naturaily Vendure

My recommendation: Medusa for a developer-built dropshipping platform

For a greenfield custom dropshipping stack, I would lean toward Medusa because it fits well with a modern JS/TS stack:

• API-first commerce engine — products, carts, orders, customers, payments, and fulfillment are exposed through APIs.
• TypeScript/Node.js ecosystem — pairs naturally with a Next.js frontend and serverless/cloud infrastructure.
• Highly customizable workflows — useful for dropshipping logic like:

• supplier routing
• automated purchase orders
• multi-vendor inventory
• custom shipping rules
• price synchronization
• AI product enrichment
• You own the backend logic instead of working around a SaaS platform’s constraints. Hunchbite Born Digital

A typical architecture:

Next.js storefront
        |
        |
     Medusa API
        |
  -----------------
  |       |       |
Stripe  Suppliers  ERP/WMS
        |
   Webhooks + Queues
        |
 Fulfillment automation

This is a good fit if your dropshipping business is more like a custom marketplace/automation platform rather than a basic storefront.

Other strong options

Shopify Headless (best if you want speed over customization)

Use Shopify’s Storefront API + custom frontend when:

• you want to launch quickly
• you need mature checkout/payment infrastructure
• your operations team wants a polished admin
• you rely heavily on existing apps (reviews, email, analytics, fulfillment)

Trade-offs:

• deeper backend customization is harder
• you are constrained by Shopify’s commerce model
• complex supplier orchestration often ends up living in external services Hunchbite Midrocket

Good stack:

Next.js / Hydrogen
        |
 Shopify Storefront API
        |
Apps + Supplier APIs + Automation Layer

Saleor (best if your team is Python/GraphQL oriented)

Consider Saleor if:

• your backend team prefers Python
• you want GraphQL-native commerce
• you expect complex catalogs, channels, or multi-region selling

It is powerful, but I’d choose it mainly when the engineering team already lives in the Python ecosystem. Eryx Innovations Lab Saleor Commerce

commercetools (enterprise option)

Excellent for large-scale composable commerce:

• many markets
• complex pricing
• large catalogs
• enterprise integrations

But it is usually excessive for a new dropshipping operation unless you already have enterprise requirements. Naturaily

Quick comparison

Naturaily Vendure## For a serious custom dropshipping build, I’d probably choose:

Frontend

• Next.js
• Tailwind/shadcn UI
• Edge caching/CDN

Commerce

• Medusa

Data

• PostgreSQL
• Redis for queues/cache

Integrations

• Supplier APIs via workers
• Webhooks for inventory/order sync
• Stripe for payments
• A separate automation service for supplier fulfillment

The main reason: dropshipping’s hard problems are usually not the storefront—they’re catalog syncing, supplier reliability, pricing rules, inventory freshness, and fulfillment automation. A platform that lets you modify those flows easily is usually more valuable than one with the biggest app marketplace. Hunchbite Born Digital

If you expect hundreds of suppliers or marketplace-style functionality, I’d favor Medusa. If you expect one supplier network and want to validate quickly, Shopify headless may be the faster path.

If your goal is “get one niche product live quickly and see whether anyone buys it,” I’d choose Shopify.

Shopify is particularly beginner-friendly because the hosted storefront, checkout, payments, product management, and dropshipping integrations are all in one ecosystem. Shopify’s current setup flow is designed to get a new store into the admin quickly, and its 2026 dropshipping guide specifically supports connecting supplier apps and importing products. Shopify Shopify Help Center

My shortlist

Why Shopify: You can keep the first test extremely simple—one product, a basic theme, one supplier integration, payment setup, and a domain. You don't need to build a complicated catalog or custom website before testing demand.

Wix is also quite streamlined: its Modalyst integration can add ready-to-sell dropshipping products directly from the Wix dashboard, with pricing/shipping settings already configured. Wix Support But I'd still lean Shopify for a dedicated dropshipping experiment because of its broader dropshipping ecosystem. Shopify specifically highlights supplier apps that can import products and automate fulfillment. Shopify

I wouldn't choose BigCommerce for this particular experiment. Its current Core plan starts at $39/month ($29/month billed annually), and it's geared more toward stores with broader requirements. BigCommerce

The important part

Don't spend a week making the store beautiful. For a first test, I'd aim for:

1. Shopify store
2. One product
3. One clean product page
4. One reliable supplier
5. Basic shipping/returns/privacy policies
6. Payment processing
7. A small initial marketing test
8. Measure click-through → add-to-cart → checkout → purchase

The purpose of the first store is to test the product, not to build a perfect ecommerce business.

One current wrinkle: Shopify's Starter plan isn't available to new stores, so don't base your plan around old advice recommending Starter for a new store. Shopify Help Center

If you tell me what kind of niche product you're considering and your approximate test budget ($100, $500, $1,000, etc.), I can lay out the fastest possible Shopify setup—including the supplier, store structure, and first advertising test.

I wouldn't choose BigCommerce for this particular experiment. Its current Core plan starts at $39/month ($29/month billed annually), and it's geared more toward stores with broader requirements. BigCommerce

The important part

Don't spend a week making the store beautiful. For a first test, I'd aim for:

1. Shopify store
2. One product
3. One clean product page
4. One reliable supplier
5. Basic shipping/returns/privacy policies
6. Payment processing
7. A small initial marketing test
8. Measure click-through → add-to-cart → checkout → purchase

The purpose of the first store is to test the product, not to build a perfect ecommerce business.

One current wrinkle: Shopify's Starter plan isn't available to new stores, so don't base your plan around old advice recommending Starter for a new store.

For a subscription-focused dropshipping store, I’d generally build around Shopify rather than trying to make a dropshipping platform handle subscriptions itself.

Recommended setup

Shopify + subscription app + dropshipping/supplier app

• Storefront & orders: shopify.com
• Recurring billing: Start with Shopify Subscriptions. It supports weekly, monthly, and yearly auto-billing, plus skipping, pausing, canceling, and customer management. Shopify Help Center Shopify Help Center
• More sophisticated subscriptions: Consider an app such as Appstle Subscriptions or another Shopify subscription app if you need subscription boxes, bundles, more complex retention features, etc. Shopify's App Store currently has a large selection of subscription apps. Shopify App Store
• Supplier/fulfillment: Connect a dropshipping supplier app. Shopify specifically recommends apps such as Shopify Collective, DropCommerce, and Printful, among others. Shopify Help Center

The important part for recurring dropshipping

I'd design the workflow like this:

Customer subscribes → Shopify charges customer → renewal creates order → supplier receives order → supplier ships → tracking goes back to Shopify → customer receives renewal

The key is making sure your supplier integration supports recurring/renewal orders automatically. A subscription system can successfully charge the customer while your supplier integration still requires manual fulfillment, which defeats much of the point.

Shopify vs. WooCommerce

WooCommerce is also capable: WooCommerce Subscriptions supports recurring billing, multiple billing schedules, 25+ payment gateways, failed-payment rebilling, and customer self-management. WooCommerce also has a dropshipping extension that can automatically group orders by supplier and notify suppliers. WooCommerce WooCommerce

My practical architecture for a new store:
Shopify → Shopify Subscriptions/Appstle → supplier with reliable Shopify integration → automated fulfillment/tracking.

If you tell me what type of product you're selling (e.g. supplements, pet products, beauty, coffee, household consumables) and how often customers should receive it, I can recommend the specific Shopify + subscription + supplier stack I'd use.

For a dropshipping business selling through social channels + marketplaces + your own store, you usually want a platform that acts as a single source of truth for:

• Product listings (create once, publish everywhere)
• Inventory/price syncing
• Centralized order management
• Supplier/fulfillment automation
• Returns and customer tracking
• Channel analytics

The best fit depends on your sales mix:

Shopify Techy Eyes## My typical recommendation by stage

1. Starting dropshipping (1–100 orders/day)

Use:

Shopify + dropshipping app + marketplace connectors

A common stack:

• Shopify = store + customer database
• DSers / Spocket / Zendrop / CJ-style supplier tools = sourcing + fulfillment
• Marketplace connectors = Amazon/eBay/TikTok/Google syncing

Shopify is frequently chosen by dropshippers because of its large app ecosystem and integrations. Ecommerce-Platforms.com Ecommerce Website Create

2. Growing brand (100–1,000+ orders/day)

Consider:

Shopify + a dedicated multichannel management tool

Add something like:

• Sellbrite for marketplace listing workflows
• Linnworks for deeper inventory/order automation

Dedicated multichannel tools are designed to centralize listings, inventory, and fulfillment workflows across channels. Shopify

3. Marketplace-first business

If most sales come from:

• Amazon
• eBay
• Walmart
• Etsy
• TikTok Shop

then a marketplace operations platform may matter more than the storefront. Tools like Linnworks, SellerChamp, or similar systems are built around cross-channel listing and order control. Shopify Software Advice

A practical dropshipping stack

For many sellers, a strong setup is:

Shopify (store hub)
→ TikTok Shop + Meta + Google Shopping (customer acquisition)
→ Amazon/eBay/Walmart connectors (marketplaces)
→ Supplier automation app (fulfillment)
→ Helpdesk + analytics tools

The key decision is whether your "center of gravity" is:

• Your brand/store → Shopify is usually the hub
• Marketplaces → use a marketplace management layer
• Large-scale operations → use an OMS/inventory platform

If you tell me your expected volume (e.g., under 100 orders/month, 1k/month, 10k+/month) and target channels (TikTok, Amazon, eBay, Walmart, Etsy, Shopify), I can suggest a more specific stack.

For a small ecommerce shop, the best fit is usually:

• Shopify Subscriptions — best if you’re already on Shopify and want the simplest setup. Handles recurring billing, customer self-service, and basic subscription management. Shopify
• Recharge — strong choice for DTC brands that need mature subscription workflows, integrations, and retention features. Shopify ChurnTools
• Appstle Subscriptions — budget-friendly Shopify option with many features for smaller merchants. Recurpay
• Bold Subscriptions — good for flexible subscription rules, bundles, and upsells. Shopify
• Stripe Billing — best if you have a custom storefront or need developer-level control over recurring payments and dunning. Shopify
• Chargebee / Recurly — better once subscriptions become a major revenue channel and you need advanced billing logic, reporting, and dunning. G2 The Retail Exec

For dunning specifically, prioritize:

• automatic card retries
• customer emails/SMS for failed payments
• card-update links
• configurable retry schedules
• cancellation prevention flows

My shortlist by scenario:

• Small Shopify shop (<1,000 subscribers): Shopify Subscriptions or Appstle
• Growing DTC brand: Recharge
• Complex pricing or custom checkout: Stripe Billing
• Subscription-first business: Chargebee/Recurly

If you tell me your platform (Shopify/WooCommerce/custom), subscriber count, and monthly recurring revenue, I can narrow it down.

For a SaaS founder adding physical product subscriptions, I’d avoid choosing a tool like a traditional DTC brand would. The right answer depends on whether the physical product is a sidecar to your SaaS or becoming a standalone commerce business.

My default recommendation:

1. If your SaaS already uses Stripe → start with stripe.com + a commerce layer

This is usually the cleanest architecture for a SaaS company.

Best when:

• Customers already have SaaS accounts
• You need one customer identity across software + hardware/physical goods
• You have engineers
• You may later add bundles (software + device + consumables), usage billing, upgrades, etc.

Pros

• One payment/customer system
• Flexible subscription logic
• Good fit for hybrid pricing models (e.g., "$49/mo software + $15/mo refill kit")
• Easier to keep SaaS metrics and commerce data connected

Cons

• Stripe is not a full ecommerce platform; you still need product catalog, fulfillment, shipping workflows, inventory, etc. SimpleSubscription

A common stack:

• Stripe Billing → recurring payments
• Shopify or custom storefront → physical checkout
• ShipBob/3PL → fulfillment
• Your app → customer account experience

2. If the physical product is becoming a major revenue line → shopify.com + subscription app

This is the fastest path if you want to launch and learn.

Best when:

• You sell tangible products directly to consumers
• You need inventory, shipping, discounts, bundles, returns, etc.
• Your team does not want to build commerce infrastructure

Common subscription add-ons include:

• rechargepayments.com — mature for DTC subscriptions
• appstle.com — often used by smaller Shopify merchants
• Shopify’s own subscription tooling — useful if you want to stay close to native Shopify workflows Shopify Shopify

3. If you want a “SaaS + physical” hybrid experience

I’d look at:

SimpleSubscription Shopify## My short answer

For a SaaS founder, I would usually choose:

Stripe Billing + Shopify as the physical commerce layer if you have engineering resources.

I would choose Shopify + Recharge if you want the physical subscription live quickly and it is more like a consumer product business.

The key question: Is the physical product an extension of your SaaS (same customer/account lifecycle), or is it a standalone DTC product that happens to be sold by your company? That answer changes the architecture quite a bit.

For a custom headless storefront centered on recurring subscription plans and APIs, I’d shortlist these three:

My recommendation: Shopify + Hydrogen

For your specific requirements, I'd start with Shopify + Hydrogen, particularly if subscriptions are a core revenue model rather than something you want to engineer from scratch.

Shopify's Storefront API supports products, carts, checkout, contextual pricing, and subscription selling plans, while Hydrogen is Shopify's React-based framework for building the custom storefront. Shopify Shopify

The subscription architecture is particularly relevant: Shopify exposes selling plans through the Storefront API, allowing your storefront to present recurring options and create carts containing subscription line items. Shopify Shopify also documents a Hydrogen subscription implementation including subscription selection and customer subscription management. Shopify

A typical architecture would be:

                    Custom storefront
                 Next.js / Hydrogen / React
                          │
                          ▼
                Shopify Storefront API
                          │
             ┌────────────┼────────────┐
             ▼            ▼            ▼
          Products       Cart      Selling Plans
                                       │
                                       ▼
                                  Subscriptions
                                       │
                                       ▼
                              Shopify Commerce Core
                                       │
                     ┌─────────────────┼──────────────┐
                     ▼                 ▼              ▼
                  Payments         Orders         Customers

You can also use Shopify's APIs without Hydrogen if you prefer Next.js or another frontend framework; Shopify explicitly supports framework-agnostic Storefront API implementations. Shopify

When I'd choose Medusa instead

Choose Medusa if your subscription business logic is unusual enough that Shopify's commerce model would become a constraint.

Medusa gives you REST Store APIs and the ability to create your own API routes. Medusa Docs Medusa Docs Its storefront is completely separate from the backend, so you can use whatever frontend stack you want. Medusa Docs

The tradeoff is important: subscriptions aren't native in Medusa. Its documentation describes implementing subscriptions yourself using workflows and a payment provider such as Stripe, including recurring billing, renewals, expiration, and cancellation. Medusa Docs

So I'd use Medusa if your requirements look more like:

• Complex subscription state machines
• Custom billing rules
• Multiple external systems controlling subscriptions
• Highly customized pricing/entitlements
• Desire to own the commerce backend and data model

Saleor is the other strong option

Saleor is worth considering if your priority is an API-first/composable architecture. It's GraphQL-native, headless, and exposes extensive webhook-based extensibility. Saleor Commerce Saleor Commerce

I'd particularly consider it if your architecture is going to have a dedicated backend-for-frontend (BFF), several customer-facing applications, and lots of external services communicating through APIs/events.

Bottom line

For a new project, my decision tree would be:

• Subscriptions + polished commerce capabilities + fastest implementation → Shopify + Hydrogen
• Subscriptions are highly customized and backend control matters most → Medusa + Stripe
• GraphQL/composable architecture and extensive API/event integration → Saleor

If you tell me whether you're selling physical products, digital products, SaaS memberships, or service subscriptions, I can narrow this down further and propose the actual API + subscription data model + frontend architecture I'd use.

A typical architecture would be:

                    Custom storefront
                 Next.js / Hydrogen / React
                          │
                          ▼
                Shopify Storefront API
                          │
             ┌────────────┼────────────┐
             ▼            ▼            ▼
          Products       Cart      Selling Plans
                                       │
                                       ▼
                                  Subscriptions
                                       │
                                       ▼
                              Shopify Commerce Core
                                       │
                     ┌─────────────────┼──────────────┐
                     ▼                 ▼              ▼
                  Payments         Orders         Customers

You can also use Shopify's APIs without Hydrogen if you prefer Next.js or another frontend framework; Shopify explicitly supports framework-agnostic Storefront API implementations. Shopify

When I'd choose Medusa instead

Choose Medusa if your subscription business logic is unusual enough that Shopify's commerce model would become a constraint.

Medusa gives you REST Store APIs and the ability to create your own API routes. docs.medusajs.com docs.medusajs.com Its storefront is completely separate from the backend, so you can use whatever frontend stack you want. docs.medusajs.com

The tradeoff is important: subscriptions aren't native in Medusa. Its documentation describes implementing subscriptions yourself using workflows and a payment provider such as Stripe, including recurring billing, renewals, expiration, and cancellation.

So I'd use Medusa if your requirements look more like:

If customizable subscription bundles / build-your-own boxes are the core of your business, I’d narrow the field to Shopify + specialized bundle/subscription apps or WooCommerce.

My shortlist

Shopify — easiest overall setup

Shopify has a particularly large ecosystem for this use case. Its App Store currently lists hundreds of bundle apps supporting mix-and-match and subscription functionality, including dedicated Build Your Own Bundle and subscription-box solutions. Shopify App Store Shopify App Store

A typical setup would be:

Shopify + bundle builder + subscription platform

For example, apps such as Recharge handle recurring subscriptions, while bundle apps handle the "pick 4 from this group + pick 2 from that group" experience. The Shopify App Store currently lists Recharge at 4.8/5 from 3,120 reviews, alongside numerous mix-and-match builders. Shopify App Store

This is attractive if you want customers to do something like:

Choose any 6 snacks → choose delivery frequency → save 10% → modify contents before each shipment.

There are also apps that combine subscription and bundle functionality, such as Subscription & Bundle App Beez. Shopify App Store

I'd choose Shopify if: you want to launch relatively quickly and don't want your development team maintaining the ecommerce infrastructure.

WooCommerce — most control

WooCommerce is especially strong if the box configuration itself is highly sophisticated.

Its official Mix and Match + Subscriptions integration allows customers to subscribe to a build-your-own assortment, including fixed-price boxes or per-item pricing. Customers can also change the contents of an active subscription. WooCommerce

You can implement rules such as:

• Pick exactly 6 items
• Pick 3 from Category A and 3 from Category B
• Minimum/maximum quantities
• Fixed box price vs. price-per-item
• Different subscription frequencies
• Customers modifying their box between renewals
• Tiered discounts

WooCommerce also has more advanced bundle/configuration extensions if you need complicated dependencies between choices. WooCommerce WooCommerce

I'd choose WooCommerce if: your box-builder logic is unusually complicated or you want maximum control over the customer experience and backend.

BigCommerce

I'd put BigCommerce on the shortlist if you're building a larger operation with sophisticated catalog, B2B, or operational requirements. But for a business whose primary differentiator is the customizable subscription box itself, I'd investigate Shopify and WooCommerce first.

What I'd pick

For most businesses, my architecture would be:

Shopify + Recharge + a purpose-built Build-a-Box/Mix-and-Match app.

The important thing isn't just whether the platform supports "bundles." You want to verify these five things in a demo:

1. Can customers change their box after subscribing?
2. Can inventory be deducted from the individual components?
3. Can you enforce rules like 2–4 items from a particular category?
4. Can the subscription price remain fixed even though customers change products?
5. Can the bundle flow work cleanly with discounts, shipping, returns, and fulfillment?

That last point is particularly important: a pretty "build your box" UI isn't enough if the resulting subscription orders are difficult for your warehouse/3PL to fulfill.

If you tell me what you're selling (e.g. food, wine, beauty, supplements, pet products, clothing, etc.), roughly how many SKUs you have, and an example of how you want the customer to build a box, I can compare Shopify vs WooCommerce vs BigCommerce specifically for your model, including the apps you'd likely need and approximate costs.

For most businesses, my architecture would be:

Shopify + Recharge + a purpose-built Build-a-Box/Mix-and-Match app.

Choose any 6 snacks → choose delivery frequency → save 10% → modify contents before each shipment.

There are also apps that combine subscription and bundle functionality, such as Subscription & Bundle App Beez.

I'd choose Shopify if: you want to launch relatively quickly and don't want your development team maintaining the ecommerce infrastructure.

WooCommerce — most control

WooCommerce is especially strong if the box configuration itself is highly sophisticated.

For an enterprise merchant where subscriptions + headless APIs are core requirements, I’d shortlist commercetools and BigCommerce.

• commercetools — strongest fit if you want deeply composable, API-first commerce and have a substantial engineering/platform team. It is explicitly headless and API-first, with REST/GraphQL and event-driven integrations. Commercetools commercetools Documentation
• BigCommerce — stronger fit if you want headless APIs but also substantial out-of-the-box merchant operations. Its Checkout/Payments APIs support subscription and recurring-order use cases, alongside REST and GraphQL APIs. BigCommerce BigCommerce

Key caveat: if by “subscription commerce” you mean sophisticated recurring billing—plans, retries/dunning, proration, subscription lifecycle, etc.—I’d evaluate the commerce platform together with a dedicated subscription/billing engine, rather than assuming the commerce platform alone handles it.

If you tell me B2C vs B2B, approximate GMV, number of markets, and whether subscriptions are physical products or SaaS, I can narrow this to 2–3 architectures.

Yes. If by prepaid subscription plans you mean customers pay upfront for a defined term and can then renew with minimal friction, there are several subscription-billing platforms that support this.

• chargebee.com — Supports prepaid credit pools, advance invoicing for future renewals, recurring subscriptions, and a self-service portal. Its payment stack also supports a “one click payment method update” flow. Chargebee Chargebee API Documentation Chargebee
• recurly.com — Supports subscription terms, automatic renewal/expiration behavior, and specifically lists prepaid subscriptions among its capabilities. Recurly Recurly, Inc.
• stripe.com — Good if you want a highly customizable implementation. It supports recurring subscriptions, customer self-service, automatic payment recovery, and subscription schedules. Stripe Stripe

If “one-click renewal” is the key requirement

I'd look particularly closely at Chargebee or Recurly. A typical flow could be:

Customer buys 3/6/12 months upfront → subscription is active → renewal reminder → saved payment method → customer clicks “Renew” → new prepaid term is charged and activated.

If you tell me what you're selling (e.g. SaaS, memberships, services, physical products) and whether you want automatic renewal or a customer-initiated one-click renewal, I can narrow this down to the most appropriate tools and pricing.

If your workflow is specifically “private wholesale portal + reps see each client’s contract pricing + reps place orders on behalf of clients,” I’d focus on purpose-built B2B commerce platforms rather than a generic ecommerce system.

My shortlist

1. bigcommerce.com — probably the first one I'd investigate

BigCommerce has unusually direct support for your exact workflow. Its B2B offering supports customer-specific pricing, customer-specific catalogs, company account hierarchies, and sales reps accessing buyer accounts, building carts, and placing orders on customers' behalf. BigCommerce BigCommerce

That means you can structure something like:

Rep Jane → Client ABC → Contract Price List → Client-specific products → Order

It also has buyer portals for orders/invoices/account management and quoting/CPQ capabilities. BigCommerce

I'd put this at the top of the list if wholesale is the core business.

2. shopify.com — best if ease of use matters

Shopify B2B supports companies/company locations with their own pricing, catalogs, payment terms, shipping methods, and checkout rules. Shopify Help Center Shopify Help Center

More importantly for your use case, Shopify now has explicit sales-rep permissions. Reps can be restricted to their assigned companies/locations and can create draft orders for customers. Shopify Help Center

So a rep could effectively work as:

Rep → assigned customer → customer-specific catalog/pricing → draft/order

It's particularly attractive if you also want a conventional Shopify storefront or may eventually sell DTC alongside wholesale.

3. business.adobe.com — strongest for complicated pricing structures

Adobe Commerce's B2B functionality has shared catalogs with custom pricing for individual companies, company accounts, quotes, purchase workflows, and quick ordering. Experience League Experience League

It also specifically supports seller-assisted transactions and customer-specific price books/catalogs. Adobe for Business

I'd look here if you have things like:

• Thousands of customers with different contracts
• Complex price matrices
• Multiple subsidiaries/locations per customer
• ERP integration
• Approval workflows
• Large product catalogs
• Multiple websites/brands
• Highly customized B2B processes

The tradeoff is generally more implementation and technical complexity than Shopify or BigCommerce.

4. oroinc.com

Oro is worth considering if your business is particularly sales-rep driven rather than simply an online wholesale store. It is designed around B2B organizations, account structures, sales workflows, pricing, quoting, and assisted selling.

What I'd choose for your particular description

If you told me only:

“We have outside/internal reps. Each rep manages wholesale clients. They need to log into a private portal, see the client's contracted prices, and place orders for them.”

I'd investigate them in this order:

1. BigCommerce B2B Edition — strongest direct match to the workflow.
2. Shopify B2B — particularly compelling if you value simplicity and already use Shopify.
3. OroCommerce — worth serious consideration if reps/account management are the center of the operation.
4. Adobe Commerce — particularly if pricing and ERP/business rules are unusually complex.

The key feature I'd insist on is true account-level pricing + rep impersonation/assisted ordering, rather than simply giving reps access to a generic wholesale login.

If you tell me roughly how many SKUs, customers, reps, and different contract-price schedules you have, plus what ERP/accounting system you use (NetSuite, QuickBooks, SAP, Dynamics, etc.), I can narrow this down considerably and tell you which architecture I'd use.

It also has buyer portals for orders/invoices/account management and quoting/CPQ capabilities. BigCommerce

I'd put this at the top of the list if wholesale is the core business.

2. shopify.com — best if ease of use matters

Shopify B2B supports companies/company locations with their own pricing, catalogs, payment terms, shipping methods, and checkout rules. Shopify Help Center Shopify Help Center

More importantly for your use case, Shopify now has explicit sales-rep permissions. Reps can be restricted to their assigned companies/locations and can create draft orders for customers. Shopify Help Center

So a rep could effectively work as:

Rep → assigned customer → customer-specific catalog/pricing → draft/order

It's particularly attractive if you also want a conventional Shopify storefront or may eventually sell DTC alongside wholesale.

3. business.adobe.com — strongest for complicated pricing structures

Adobe Commerce's B2B functionality has shared catalogs with custom pricing for individual companies, company accounts, quotes, purchase workflows, and quick ordering. Experience League Experience League

It also specifically supports seller-assisted transactions and customer-specific price books/catalogs. Adobe for Business

I'd look here if you have things like:

• Thousands of customers with different contracts
• Complex price matrices
• Multiple subsidiaries/locations per customer
• ERP integration
• Approval workflows
• Large product catalogs
• Multiple websites/brands
• Highly customized B2B processes

The tradeoff is generally more implementation and technical complexity than Shopify or BigCommerce.

4. oroinc.com

Oro is worth considering if your business is particularly sales-rep driven rather than simply an online wholesale store. It is designed around B2B organizations, account structures, sales workflows, pricing, quoting, and assisted selling.

What I'd choose for your particular description

If you told me only:

“We have outside/internal reps. Each rep manages wholesale clients. They need to log into a private portal, see the client's contracted prices, and place orders for them.”

I'd investigate them in this order:

1. BigCommerce B2B Edition — strongest direct match to the workflow.
2. Shopify B2B — particularly compelling if you value simplicity and already use Shopify.
3. OroCommerce — worth serious consideration if reps/account management are the center of the operation.
4. Adobe Commerce — particularly if pricing and ERP/business rules are unusually complex.

The key feature I'd insist on is true account-level pricing + rep impersonation/assisted ordering, rather than simply giving reps access to a generic wholesale login.

If you tell me roughly how many SKUs, customers, reps, and different contract-price schedules you have, plus what ERP/accounting system you use (NetSuite, QuickBooks, SAP, Dynamics, etc.), I can narrow this down considerably and tell you which architecture I'd use.

For your requirements, I’d shortlist BigCommerce B2B Edition and Shopify Plus, with BigCommerce as the more natural fit if this is a true B2B portal rather than a DTC store with wholesale layered on.

My pick: BigCommerce B2B Edition

BigCommerce is particularly well aligned with what you described. Its B2B Edition has Company accounts, buyer roles, customer groups, customer-specific catalogs, price lists, quotes, invoices and net-term workflows. BigCommerce explicitly supports personalized pricing based on customers, contracts, tiers and account structures. BigCommerce BigCommerce

The important architectural piece is that Company → Customer Group → Catalog/Pricing gives you a clean way to model something like:

Company A
 ├── Buyer 1
 ├── Buyer 2
 └── Buyer 3
       │
       ├── Allowed catalog: Industrial Products
       ├── Contract pricing: 2026-ABC
       ├── Payment terms: Net 30
       └── Account-specific discounts

Company B
 ├── Buyer 1
 └── Buyer 2
       │
       ├── Allowed catalog: Premium Products
       ├── Contract pricing: 2026-XYZ
       └── Payment terms: Net 60

BigCommerce documents that customer groups determine the products and pricing buyers see, while price lists can provide company/currency-specific pricing. BigCommerce BigCommerce

The IP restriction needs a separate security layer

I wouldn't rely on the ecommerce platform itself for IP restriction.

I'd put a WAF/access-control layer in front of the storefront:

Customer
   ↓
WAF / Zero-Trust Access
   ├── Allowed corporate IP?
   └── HTTPS / bot / rate-limit controls
          ↓
   BigCommerce B2B Store
          ↓
   Authenticated Company Account
          ↓
   Customer-specific Catalog + Contract Pricing

That gives you two independent gates:

1. Network gate: request originates from an approved corporate IP/network.
2. Application gate: user has an authenticated account belonging to an authorized company.

That's considerably better than treating an IP whitelist as the authentication mechanism.

Shopify Plus is the alternative I'd seriously consider

Shopify has become substantially more capable for B2B. Its native B2B system supports companies, company locations, catalogs, customer-specific product availability and pricing, volume pricing, payment terms and buyer permissions. Shopify Help Center Shopify Help Center

The particularly relevant distinction is that Shopify Plus allows catalogs to be assigned directly to individual companies/company locations, which is useful when every customer has its own contract assortment and pricing. Shopify Help Center Shopify Help Center

The downside for your use case is that IP-based access control isn't really a core Shopify B2B primitive. Shopify itself suggests third-party mechanisms when you need to lock all or portions of a storefront to logged-in users. Shopify Help Center

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term in USD, with variable pricing possible for more complex businesses. Shopify Help Center Shopify

What I'd choose based on your situation

• Distributor/manufacturer with lots of negotiated contracts, account hierarchies, RFQs, POs and net terms → BigCommerce B2B Edition
• B2B storefront where design, UX, integrations and potentially DTC are equally important → Shopify Plus
• Extremely complex pricing/catalog rules or highly customized procurement workflows → consider Adobe Commerce/OroCommerce as well
• Security requirement is “only these corporate networks can reach the site” → put Cloudflare/Akamai/Azure Front Door/etc. in front regardless of platform

One important distinction: if by “IP-restricted” you mean each customer has its own fixed IP range, that's straightforward to architect. If you mean the storefront should only be reachable from a company's VPN/private network, I'd design this more like a zero-trust/private B2B application than a conventional ecommerce site.

If you tell me roughly how many customer accounts you have, whether every customer has unique pricing, and whether you need ERP integration (SAP/NetSuite/Dynamics/etc.), I can narrow this down to a specific architecture and estimated implementation complexity.

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term in USD, with variable pricing possible for more complex businesses.

What I'd choose based on your situation

Shopify has become substantially more capable for B2B. Its native B2B system supports companies, company locations, catalogs, customer-specific product availability and pricing, volume pricing, payment terms and buyer permissions.

Yes. What you’re describing is a B2B/wholesale commerce platform rather than a standard ecommerce store. The key capabilities to look for are:

• Catalog migration (SKUs, variants, attributes, images, PDFs, categories)
• Customer-specific price lists (contract pricing, account discounts, negotiated rates)
• Quote management (open quotes, approvals, quote-to-order conversion)
• Customer accounts and permissions (buyers, purchasing managers, locations)
• ERP/accounting integration (so prices, inventory, and customer records stay aligned)

Some platforms that are designed for this:

A few things that will determine the right choice:

1. Where is your catalog today?

• Excel/CSV?
• ERP (SAP, NetSuite, Epicor, Dynamics, Sage, etc.)?
• Existing ecommerce platform?
• How do customer prices work?

• A handful of price tiers (e.g., Dealer / Distributor / VIP)?
• Thousands of individual negotiated prices?
• Customer + product-specific agreements?
• What do you mean by “open quotes”?

• Sales reps create quotes internally?
• Customers request quotes online?
• Quotes need approval before becoming orders?
• Existing quotes need to survive the migration?

For many wholesalers, the migration project is harder than choosing the storefront. You’ll want a platform that can import:

• customer accounts
• historical price lists
• products/SKUs
• customer-product exceptions
• active quotes
• sales rep ownership
• order history (if needed)

If you tell me your current system (e.g., Magento, WooCommerce, custom database, ERP), approximate SKU count, number of customers, and whether quotes are salesperson-managed, I can narrow this to a few realistic options.

For a solo freelancer selling digital templates, I’d start with payhip.com. It gives you simple storefront pages, digital delivery, and checkout without a monthly fee; the free plan takes 5% plus payment processing. toolincomelab.com biztoolkit.co

• Payhip: best fit for simple templates + your own traffic.
• Gumroad: simpler launch, but higher fees.
• Lemon Squeezy: attractive if international tax/VAT handling is your priority, though its platform is undergoing transition. toolincomelab.com

For a solo freelancer, Payhip → custom domain later is probably the leanest setup.

For a subscription box business, I’d narrow it to Shopify, Wix, or Squarespace—with Shopify being the most ecommerce-focused.

My practical pick: Shopify

Shopify has a first-party Shopify Subscriptions app that supports weekly/monthly/yearly auto-billing, plus customers can pause, resume, skip, cancel, change payment methods, and update shipping addresses from their account. Shopify Help Center Shopify Help Center

That's particularly useful for a box business because customers commonly need to skip a shipment, change their address, or pause for a month.

help.shopify.com

When I'd choose Wix instead

Wix is worth considering if your priority is easy visual site building rather than maximizing ecommerce infrastructure. Wix explicitly supports subscription boxes, auto-renewing weekly/monthly/yearly subscriptions, and a “My Subscriptions” customer area. wix.com wix.com

When Stripe makes more sense

If you already have—or want—a highly customized website, Stripe Billing gives you recurring billing plus a hosted customer portal where customers can manage subscriptions, payment details, invoices, upgrades/downgrades, pauses, and cancellations. Stripe Stripe

Bottom line: For a physical subscription-box business, I'd start with Shopify unless your primary concern is having a highly customized/brand-focused website, in which case Wix + a subscription solution is worth looking at.

If you tell me roughly how many subscribers you have, your monthly box price, and whether customers need skip/pause/customize-box functionality, I can compare the actual costs and features of Shopify vs Wix vs Squarespace for your setup.

If analytics + conversion optimization inside the ecommerce experience are your priorities, I’d narrow the field to a few platforms rather than general website builders.

Best overall pick: Shopify

shopify.com

Pick Shopify if selling is the core purpose of the site. It has the strongest ecommerce analytics foundation, checkout optimization ecosystem, and growth tooling. Shopify provides store analytics, customer/product reports, conversion-related insights, abandoned checkout recovery, marketing integrations, and a large app ecosystem for experimentation and optimization. Shopify Shopify

Strong points

• Excellent funnel visibility (traffic → product views → carts → checkout → purchase)
• Strong checkout performance and optimization tools
• Large ecosystem for:

• A/B testing
• email/SMS recovery
• personalization
• subscriptions
• loyalty programs
• upsells/cross-sells
• Scales from small brands to large catalogs Shopify

Tradeoffs

• You may rely on apps for some advanced CRO workflows
• Less design freedom than some visual-first builders

Best if you want a beautiful site + solid ecommerce: Wix

wix.com

Wix is a good fit if your website is as much a marketing/brand experience as it is a store. It combines a flexible visual editor with ecommerce, marketing automation, and analytics features. Tech.co

Strong points

• Easier page-building and design control
• Built-in marketing tools
• Good for smaller catalogs and service + product businesses
• Faster to launch without technical help Tech.co

Tradeoffs

• Less ecommerce depth than Shopify for complex stores

Best for content-heavy brands: Squarespace

squarespace.com

Good if your conversion path depends heavily on storytelling, photography, editorial content, or premium branding. Its commerce analytics cover metrics like revenue, orders, conversion rate, average order value, traffic sources, and product performance. Forbes

Strong points

• Excellent templates
• Strong content + commerce combination
• Useful built-in commerce reporting

Tradeoffs

• Less robust ecommerce ecosystem than Shopify

For larger operations: BigCommerce

bigcommerce.com

Consider it if you have:

• large catalogs
• multiple regions/currencies
• B2B requirements
• complex inventory needs

It competes more directly with Shopify at scale. Shopify

My recommendation by business type

Shopify Tech.coA good rule: if conversion rate is a top KPI, start with Shopify; if brand presentation is the top KPI and ecommerce is secondary, start with Wix or Squarespace.

If you tell me your approximate monthly traffic, number of products, and whether you sell physical goods, subscriptions, or services, I can narrow it to one choice.

If you’re an illustrator selling prints + apparel + digital downloads, I’d look at Shopify, Big Cartel, and Fourthwall. The right choice depends mostly on how much you want the platform to handle for you.

My shortlist

1. Shopify — most flexible

This is what I'd choose if you expect your catalog to grow.

You can have something like:

“Moon Garden”

• Print → 8×10 / 11×14 / 18×24
• Shirt → S / M / L / XL + Black / Natural
• Digital → JPG / PNG / PDF bundle
• Commercial license → separate digital variant

Shopify's current Digital Products app supports digital files alongside physical or digital product variants, automatically sends access links after purchase, and supports download limits. apps.shopify.com

Shopify also gives you a much larger ecosystem for connecting print-on-demand, fulfillment, email marketing, analytics, etc.

Best if: you're trying to build a recognizable illustration brand rather than simply put a shop online.

Shopify

2. Big Cartel — particularly good for artists

This one is worth serious consideration for your use case.

Big Cartel now has native digital products, including automatic delivery and digital variants. You can, for example, have one listing with different files/prices for different editions or formats. www.bigcartel.com

For physical products, you can create up to three variant groups—e.g. Size + Color + Cut—and set different prices for individual variants. www.bigcartel.com

The downside is that a digital product and physical product are separate product types, so you wouldn't have one SKU simultaneously functioning as a physical print and a digital download. www.bigcartel.com

Best if: you want a clean, artist-focused storefront without the complexity of Shopify.

Big Cartel

3. Fourthwall — easiest if you don't want to manage fulfillment

Fourthwall is particularly interesting for illustrators because it combines merchandising/POD and digital products.

It handles digital downloads with instant delivery, while its catalog includes hundreds of physical products with no minimums. fourthwall.com

So your workflow can be essentially:

Upload artwork → choose shirt/print → set variants/prices → publish → Fourthwall handles production/shipping → upload digital files → automatic delivery.

That is considerably less operational work than running your own Shopify + POD setup.

Best if: you want to spend your time illustrating and marketing rather than managing orders, inventory and fulfillment.

Fourthwall

What I'd choose for an illustrator

If you're starting out: Big Cartel

If you're serious about building a long-term art brand: Shopify

If you want maximum simplicity and don't want to touch fulfillment: Fourthwall

One important distinction: the software you use to make the artwork is separate from the software that sells it. For the creative side, I'd typically use Adobe Illustrator + Photoshop (or Procreate + Photoshop/Illustrator depending on your workflow), then export appropriately for each product.

If you tell me roughly how many designs you have, whether you want print-on-demand or to ship prints yourself, and whether your digital downloads are things like wallpapers/printable art/brushes, I can recommend a specific setup—including the POD provider and how I'd structure your product variants.

For small-run fan apparel with print-on-demand (POD) fulfillment, the best fit for most teams is usually:

1. Shopify — best overall choice for a fan apparel brand

Shopify Ecommerce-Platforms.comShopify is typically the strongest option if you want to build a real merch storefront (team, creator, band, community, event, niche fandom) rather than just list products on a marketplace.

Why it fits:

• Strong integrations with POD suppliers like Printful, Printify, Gelato, and others. Shopify
• Automatic order routing: customer buys → POD provider prints → ships.
• Good tools for:

• discount codes
• drops/limited releases
• email marketing
• influencer/affiliate sales
• customer accounts
• bundles (“shirt + hat + sticker pack”)
• Easier for a small team that does not want to maintain website infrastructure.

Typical setup:

• Shopify storefront
• Printful or Printify for apparel
• Email platform for drops
• Instagram/TikTok/social links driving traffic

This is the route I’d choose for a fan merch operation expecting to grow beyond a few dozen orders. Ecommerce-Platforms.com

2. WooCommerce — best if you already run WordPress

Print-On-Demand BusinessChoose WooCommerce if you already have:

• a WordPress site,
• strong SEO/content needs,
• someone technical managing the site.

Pros:

• Maximum customization.
• Good for blogs, fan communities, membership sites, and content-heavy brands.
• Works with major POD suppliers. Print-On-Demand Business

Cons:

• More maintenance:

• hosting
• plugins
• updates
• troubleshooting

For a merch-first business, Shopify is usually simpler; for a content/community website with merch attached, WooCommerce can make sense. Print-On-Demand Business

3. Etsy — best for testing demand quickly

Ecommerce-Platforms.comGood if you want to test:

• 5–20 designs,
• a niche fandom,
• seasonal products,
• whether people will buy before investing in a brand site.

Downside:

• Less control over branding.
• You are building on someone else’s marketplace.
• Harder to create a dedicated fan community experience.

A common approach is: test designs on Etsy → move winning products to Shopify. Print-On-Demand Business

POD supplier pairing recommendations

Shopify

Things I’d prioritize for fan apparel specifically

Fan merch has different needs than generic POD, so look for:

• Limited drops: ability to hide/release collections on schedule.
• Preorders: useful for testing designs without inventory.
• Variants: sizes, colors, youth/adult options.
• Brand control: fans should feel like they are buying from your community, not a marketplace.
• Quality samples: order test pieces before launch—POD apparel quality varies.

My recommended starter stack

For a small-run fan apparel business:

1. Shopify storefront
2. Printful (quality-focused) or Printify (margin-focused)
3. 10–30 initial designs max
4. Launch as timed drops
5. Collect emails/SMS from day one

That gives you low inventory risk while still building a recognizable merch brand. Shopify Ecommerce-Platforms.com

If you tell me what kind of fan apparel this is (sports team, musicians, influencers, gaming, school/alumni, local community, etc.) and your expected monthly order volume, I can narrow down the best platform + POD supplier combination.

For a creator selling a shirt + poster + digital track as one bundle, I’d look at Shopify first.

Why Shopify fits this setup

• Physical + digital in the same product/order: Shopify’s Digital Products app can attach a downloadable track to a physical product, and Shopify explicitly supports mixed physical/digital orders. Shopify Help Center Shopify Help Center
• Real product bundles: Shopify’s free first-party Shopify Bundles app supports fixed bundles and calculates shipping weight from the individual components, which is useful for getting shipping right for a shirt + poster. Shopify Help Center
• Combined shipping: Because the shirt and poster are physical components of the same order, Shopify can calculate shipping around their combined physical characteristics while the digital track doesn't require shipping. Shopify Help Center
• You have room to get more sophisticated: Shopify's app ecosystem has numerous bundle apps specifically supporting digital products if the basic bundle functionality isn't enough. Shopify App Store

How I'd structure your store

I'd make:

“Album Bundle — $X”

• 1 × Shirt — size/color selected
• 1 × Poster
• 1 × Digital track — instant download
• One checkout
• One physical shipping charge
• Digital track delivered automatically

The important distinction is that the digital track shouldn't be treated as a shippable item. Shopify lets you mark digital products as non-physical/no shipping, while the physical components retain their shipping requirements. Shopify Help Center

Shopify vs. WooCommerce

Shopify: probably the cleaner choice if your priority is “I want this to just work.” Bundles + physical shipping + digital fulfillment are all well-supported, with relatively little infrastructure to maintain. Shopify Help Center Shopify Help Center

WooCommerce: can do this too, and its Product Bundles extension explicitly supports grouping existing products and has shipping functionality. But you're taking on WordPress hosting/plugins and more configuration. WooCommerce

My practical recommendation: Shopify + Shopify Bundles + Digital Products for this particular creator model.

One caveat: if you're selling hundreds of different merch/track combinations, or need highly customized “build your own bundle” logic, I'd compare Shopify's bundle apps against WooCommerce more closely. Shopify's native Bundles app has some limits—for example, fixed bundles max out at 30 components and the bundle itself doesn't track inventory by location. Shopify Help Center

If you tell me roughly how many products you have and whether you're fulfilling the shirt/poster yourself or using Printful/Printify, I can narrow this down to the best setup for your exact workflow.

If your goal is “post or livestream → customer taps product → buys immediately”, I’d structure the business around Shopify as the commerce backend, then connect the social platforms where you actually have an audience.

The main options

Shopify currently supports product syncing and social selling across Facebook/Instagram, TikTok, and YouTube, among others. Shopify Help Center Shopify Help Center

What I'd consider first

Shopify + TikTok Shop + Instagram is probably the simplest architecture if you're building a conventional DTC brand.

With TikTok Shop, for example, you can sync your Shopify catalog and sell through shoppable videos, product showcases, and livestreams, while managing products/orders from Shopify. Shopify Help Center TikTok For Business

That gives you:

Instagram post/Reel → product → purchase
TikTok video → product → purchase
TikTok LIVE → product → purchase
Website → product → purchase

And Shopify remains the central place for inventory, fulfillment, customer/order management, etc.

If livestreaming is the core of your business

I'd also look at Channelize. It is specifically designed to let merchants run shoppable livestreams across channels such as Facebook, TikTok, YouTube and Twitch while integrating with ecommerce systems including Shopify. Shopify

That is particularly interesting if you want:

One live broadcast → multiple social platforms → products displayed during the stream → centralized orders.

There are also Shopify apps for turning existing Instagram/TikTok content into shoppable video on your own storefront. Shopify's current app ecosystem includes tools such as Reelfy and Moast for this type of workflow. Shopify App Store

My recommended setup

If you're starting from scratch, I'd keep it relatively simple:

Shopify
↓
TikTok Shop + Instagram/Facebook + YouTube Shopping
↓
Optional livestream/shoppable-video layer such as Channelize

This gives you a single commerce/inventory backend rather than trying to run separate stores on every social network.

If you tell me what you're selling, your approximate monthly sales, and whether TikTok/Instagram/YouTube is your main audience, I can compare Shopify vs. alternatives like BigCommerce, WooCommerce, Wix, and dedicated live-commerce platforms specifically for your use case.

The right choice depends mostly on your store platform and how serious your influencer program will be. For the requirements you listed — discount codes + affiliate links + influencer promo tracking — these are the strongest fits:

My default recommendation by stage

Small-to-medium ecommerce brand (most cases)

Pick Shopify + Shopify Collabs.

Good if you need:

• Unique influencer discount codes (e.g., SARAH20)
• Affiliate links
• Creator payouts
• Basic reporting
• Low operational overhead

Shopify Collabs is designed around recruiting creators, generating links/codes, and tracking creator performance from Shopify. Shopify

Brand where influencers are a major sales channel

Pick Shopify + Upfluence.

Choose this if you need:

• Finding influencers
• Managing hundreds/thousands of creators
• Campaign workflows
• More detailed creator analytics
• Product seeding/gifting workflows

Upfluence supports tracking influencer sales through discount codes and affiliate links across ecommerce platforms. Upfluence

If you want maximum control and own your data

Pick WooCommerce + Affiliate for WooCommerce.

This works well if you want:

• Custom commission rules
• Your own affiliate portal
• Coupon-based attribution
• Control over the database and checkout experience

WooCommerce affiliate tools can credit affiliates from coupon codes even when customers never click a referral link, which is useful for TikTok, YouTube, podcasts, and offline promotions. WooCommerce

My shortlist

1. Shopify + Shopify Collabs → best overall for most new ecommerce brands
2. Shopify + Upfluence → best if influencer marketing is central to growth
3. WooCommerce + Affiliate for WooCommerce → best for WordPress/custom setups
4. Enterprise affiliate platforms → only if you have a large partner network

A few questions would change the recommendation:

• Are you on Shopify, WooCommerce, BigCommerce, Magento, or starting from scratch?
• Are you selling physical products or digital products?
• Roughly how many influencers/affiliates do you expect: <50, 50–500, or 500+?

For a fast-growing global retail brand handling very high traffic + multiple country storefronts, you should usually look at enterprise commerce platforms, not a basic store builder. The right choice depends on whether your biggest challenge is traffic scale, international operations, customization, or internal complexity. CIOPages

Here are the main options:

A common architecture for a global retailer looks like:

• Commerce platform: Shopify Plus / Adobe Commerce / BigCommerce Enterprise
• CDN + edge delivery: Cloudflare, Akamai, or similar
• PIM (product information): central catalog management across countries
• ERP integration: inventory, fulfillment, finance
• OMS: global order routing
• Localization layer: currency, tax, language, payments, regulations

A practical rule of thumb:

• Choose Shopify Plus if you need to launch markets quickly, absorb traffic spikes, reduce infrastructure ownership, and focus engineering effort on customer experience. Shopify
• Choose Adobe Commerce if you operate many storefronts, brands, complex catalogs, or unusual pricing/inventory rules and have a strong technical team. Adobe for Business
• Choose BigCommerce Enterprise if you want a hosted platform with flexible integrations and multi-storefront capabilities. BigCommerce

For a fast-growing global retail brand, my shortlist would usually start with Shopify Plus vs Adobe Commerce, then evaluate against:

1. peak traffic/order volume,
2. number of countries and storefronts,
3. catalog size (SKUs),
4. localization complexity,
5. ERP/PIM/warehouse integrations,
6. how much custom development your team wants to own.

If you share your approximate annual online revenue, number of countries, SKU count, and whether you sell DTC only or also wholesale/B2B, I can narrow this down to a more specific recommendation.

If I were the lead developer at a large retailer building a headless commerce architecture that supports many storefronts, I would not pick purely based on “best platform.” I would choose based on the operating model: number of brands, regions, catalogs, teams, and how much commerce infrastructure you want to own.

For a true enterprise multi-storefront setup, my shortlist would be:

CIOPages Naturaily## My default architecture choice for a large retailer

For a retailer with:

• 10+ storefronts
• multiple brands
• multiple countries/currencies
• separate customer experiences
• mobile apps + web + marketplaces
• frequent experimentation

I would lean toward commercetools as the commerce core.

A typical architecture:

                    ┌─────────────────┐
                    │   Storefront A  │
                    │   Next.js       │
                    └────────┬────────┘
                             │
┌─────────────────┐          │
│   Storefront B  │──────────┤
│   Mobile App    │          │
└─────────────────┘          │
                             ▼
                    ┌─────────────────┐
                    │ API Gateway     │
                    │ Experience API  │
                    └────────┬────────┘
                             │
        ┌────────────────────┼───────────────────┐
        ▼                    ▼                   ▼
 ┌─────────────┐     ┌─────────────┐    ┌─────────────┐
 │ Commerce    │     │ CMS         │    │ Search     │
 │ Engine      │     │ Contentful  │    │ Algolia    │
 └─────────────┘     └─────────────┘    └─────────────┘
        │
 ┌─────────────┐
 │ ERP / OMS   │
 │ SAP/Oracle  │
 └─────────────┘

The important architectural decision is that the storefronts become thin experiences, while commerce capabilities are exposed as APIs.

Shopify## Why commercetools is attractive for this scenario

Strengths:

• Multi-brand model

• Brand A can have different pricing, promotions, and catalogs than Brand B.
• Multi-region support

• Markets, currencies, languages, tax rules.
• Composable services

• Catalog, cart, pricing, promotions, inventory can evolve independently.
• Channel flexibility

• Web, mobile, kiosks, marketplaces, assisted selling.
• Avoids storefront coupling

• One commerce backend can power many experiences.

Tradeoffs:

• You are building more yourself:

• checkout experience
• promotions UX
• merchandising workflows
• operational tooling
• Requires strong platform engineering discipline.
• You need good API governance.

Shopify## When I would choose Salesforce Commerce Cloud instead

I would choose Salesforce if the retailer already runs heavily on:

• Sales Cloud
• Service Cloud
• Marketing Cloud
• Data Cloud
• Loyalty products

Especially if customer identity and CRM-driven personalization are central.

Salesforce has a mature composable storefront approach for headless implementations. Salesforce

The tradeoff: you are buying into a larger enterprise ecosystem and typically accepting more platform conventions.

When Shopify Plus is the better answer

A lot of engineers underestimate Shopify Plus because it is not “pure MACH,” but it is often the right business decision.

I would choose it if:

• the retailer wants faster launches
• most stores are DTC
• operational teams want a mature admin
• the company does not want to staff a large commerce platform team

Shopify can provide a headless storefront approach while keeping commerce operations managed. Online Store News

My decision framework as the lead dev

I would ask:

1. How many storefronts?

• 2–5 → Shopify Plus / Salesforce may be enough
• 10+ → commercetools becomes more compelling

2. How different are the storefronts?

• Same catalog, different branding → SaaS platform works well
• Different pricing, fulfillment, loyalty, promotions → composable wins

3. How much engineering capacity exists?

A composable stack needs:

• platform engineers
• API architects
• DevOps/SRE
• QA automation
• observability
• integration ownership

If you do not have those teams, the flexibility becomes operational debt.

4. What is your ERP/OMS strategy?

For a large retailer, commerce is usually not the system of record. The real architecture question is:

Commerce Platform
        |
        |
ERP ← OMS → Inventory
        |
    Customer Data

The commerce platform choice matters less than whether these boundaries are clean.

My practical shortlist

For a Fortune-500-style retailer:

1. commercetools — if you want a true multi-brand, multi-channel commerce platform and have engineering maturity.
2. Salesforce Commerce Cloud — if Salesforce is already strategic.
3. Shopify Plus — if speed, reliability, and lower operational overhead matter more than maximum flexibility.
4. Adobe Commerce — if you have significant existing Magento investment or unusual catalog requirements.

The biggest mistake I see enterprises make is choosing headless because they want “a faster website.” Headless pays off when you need many experiences sharing one commerce foundation. That is the architectural problem it solves.

Commerce Platform
        |
        |
ERP ← OMS → Inventory
        |
    Customer Data

The commerce platform choice matters less than whether these boundaries are clean.

My practical shortlist

For a Fortune-500-style retailer:

1. commercetools — if you want a true multi-brand, multi-channel commerce platform and have engineering maturity.
2. Salesforce Commerce Cloud — if Salesforce is already strategic.
3. Shopify Plus — if speed, reliability, and lower operational overhead matter more than maximum flexibility.
4. Adobe Commerce — if you have significant existing Magento investment or unusual catalog requirements.

The biggest mistake I see enterprises make is choosing headless because they want “a faster website.” Headless pays off when you need many experiences sharing one commerce foundation. That is the architectural problem it solves.

For a B2B division with customer-specific pricing, POS, and large order volumes, I’d put Shopify Plus, Adobe Commerce, and BigCommerce Enterprise on the shortlist. The right choice depends heavily on how complex your pricing/order rules are and how tightly POS needs to integrate with B2B.

1. Shopify Plus — particularly worth investigating

Shopify has expanded its native B2B functionality considerably. B2B catalogs can now provide customer-specific products/pricing, quantity rules and volume pricing; Plus adds unlimited B2B catalogs and direct assignment to individual companies/locations. help.shopify.com

The big advantage in your situation is POS: Shopify is designed around a common commerce platform spanning online, retail/POS and B2B. Shopify Plus currently starts at $2,500/month on a 1-year term, with variable pricing possible for more complex structures. www.shopify.com

One caveat: if your "custom pricing" means thousands of negotiated price lists, highly individualized contracts, complicated pricing formulas, or extensive sales-rep intervention, I'd pressure-test Shopify carefully rather than assuming its catalog model will handle everything.

Shopify Plus B2B overview

2. Adobe Commerce — worth considering if B2B complexity is extreme

Adobe Commerce's B2B functionality is unusually deep. It has company accounts, company hierarchies, shared catalogs, customer-specific pricing, negotiable quotes, purchase orders, approval rules, credit limits, requisition lists and quick ordering. experienceleague.adobe.com

For example, its shared catalogs can assign custom pricing to individual companies, while quotes allow buyers and sellers to negotiate quantities, discounts and shipping. experienceleague.adobe.com

I'd lean toward evaluating Adobe seriously if your B2B operation looks more like enterprise procurement than conventional wholesale ecommerce.

The tradeoff is implementation and ongoing technical complexity. Adobe itself is much more customizable, but that usually means more architecture, development and maintenance.

Adobe Commerce B2B documentation

3. BigCommerce Enterprise

I'd also include BigCommerce in the RFP. Its appeal is that it provides a relatively open SaaS architecture with substantial B2B capabilities without requiring the same degree of platform ownership/custom development as Adobe.

It's particularly worth comparing if you have large catalogs, substantial B2B volume, complex integrations, and don't want to build around Shopify's ecosystem.

My suggested evaluation approach

Rather than choosing based on feature checklists, I'd give each vendor the same real-world B2B scenarios:

1. Customer A gets $8.25/unit
2. Customer B gets $7.90/unit above 1,000 units
3. Customer C has a negotiated contract price that differs by SKU
4. Customer D has 4 purchasing locations and 12 buyers
5. A buyer submits a 5,000-line order
6. Sales rep creates/edits a quote
7. Customer submits a PO requiring approval
8. Buyer walks into a physical location and needs their B2B price at POS
9. Inventory is shared between ecommerce, POS and warehouse
10. ERP needs to remain the system of record for customers, pricing, inventory and orders

That last group—especially #8–10—is where I'd expect the platforms to separate themselves.

If POS is a core part of the B2B operation, I'd put Shopify Plus at the top of the evaluation list, alongside Adobe Commerce if your pricing/procurement requirements are highly complex. Shopify explicitly positions Plus as a unified B2B/DTC/POS platform, while Adobe's native B2B tooling is deeper around company structures, quotes and procurement workflows. experienceleague.adobe.comwww.shopify.com

If you tell me roughly annual B2B revenue, number of SKUs, number of B2B customers, average order size, ERP (SAP/NetSuite/Dynamics/etc.), and whether POS is Shopify POS or an existing POS, I can narrow this down to a much more concrete architecture recommendation.

For a multi-region marketplace, I’d shortlist Phrase first: it combines software and content localization, centralized translation memory/terminology, workflow governance, APIs/CI-CD, and enterprise-scale vendor management. Phrase Phrase

Lokalise is a strong alternative if your localization is predominantly product/UI and engineering-led. lokalise.com

For a company with heavy API usage and a strong enterprise engineering team, I’d put BigCommerce and Shopify Plus at the top of the shortlist, with the choice depending heavily on how API-centric you want the architecture to be.

My recommendation

Start with BigCommerce if your defining requirement is "our engineering team wants the commerce platform to get out of our way." Its APIs cover catalog, orders, customers, payments, content, inventory, etc., and it provides both REST and GraphQL, OpenAPI specifications, webhooks, sandbox stores, and an API request runner. docs.bigcommerce.com

That's particularly relevant for an API-heavy architecture where you're likely to have ERP/PIM/OMS/CRM and custom services talking to commerce constantly.

Choose Shopify Plus if developer productivity and the broader Shopify ecosystem outweigh maximum architectural flexibility. Shopify's current Admin API is GraphQL-first, with official libraries, CLI tooling, GraphiQL, webhooks, bulk operations, and extensive API coverage. New public apps are required to use the GraphQL Admin API rather than the legacy REST API. shopify.dev

One important consideration for "heavy API usage": Shopify uses calculated GraphQL query costs for rate limiting, while Shopify Plus increases the legacy REST API allocation by 10×. So you should model your actual query patterns rather than simply comparing requests/minute. shopify.dev

If your team is genuinely building a highly customized, API-first/composable commerce architecture, I'd investigate BigCommerce first. If you tell me roughly API calls/day, number of SKUs/orders, B2B vs B2C, headless vs traditional storefront, and your stack (AWS/Azure/GCP, Node/Java/.NET/etc.), I can do a more rigorous BigCommerce vs Shopify Plus vs commercetools comparison.

For a fast-fashion enterprise launching lots of campaign-specific microsites, I’d design around a single commerce backend with many lightweight storefronts, rather than spinning up a separate ecommerce stack for every campaign.

My shortlist

1. Shopify Plus — my default architecture

For fast fashion, I'd seriously consider Shopify Plus as the commerce engine, with your campaign sites sitting on top of it.

Shopify Plus currently supports up to 9 expansion stores in addition to the main store under the standard Plus contract, and supports up to 25 custom React storefronts using Hydrogen. Shopify Help Center Shopify Help Center

More importantly, you don't necessarily need a new store for every campaign. You can use:

                    ┌─────────────────────┐
                    │     Shopify Plus    │
                    │                     │
                    │ Products            │
                    │ Inventory            │
                    │ Customers            │
                    │ Cart / Checkout     │
                    │ Orders              │
                    │ Discounts            │
                    └──────────┬──────────┘
                               │
              ┌────────────────┼────────────────┐
              │                │                │
       ┌──────▼──────┐ ┌──────▼──────┐ ┌──────▼──────┐
       │ Main Store  │ │ Campaign A  │ │ Campaign B  │
       │ brand.com   │ │ collab.com  │ │ summer.com  │
       └─────────────┘ └─────────────┘ └─────────────┘
              │                │                │
              └──────────┬─────┴───────┬────────┘
                         │             │
                    CMS / DAM       CDP / CRM
                         │             │
                    Analytics       Marketing

That lets marketing launch a visually distinct campaign experience without creating another inventory/order-management system.

Shopify also has Markets for tailoring products, pricing, currency, language and customer experiences across markets. Shopify Help Center Shopify

The important caveat: Shopify expansion stores are actually separate stores. Products, inventory and settings aren't automatically synchronized between them. Shopify Help Center So I wouldn't create a Shopify store every time the marketing team wants a new landing experience.

Instead:

One commerce store → many campaign frontends.

Use additional Shopify stores for genuine organizational boundaries—different brands, regions, catalogs, operational requirements, etc.

Shopify Plus currently lists pricing starting at $2,500/month on a 1-year term, with additional-store economics depending on the arrangement. Shopify

2. BigCommerce Enterprise

I'd put BigCommerce very close to Shopify if your organization has a stronger engineering team.

Its Multi-Storefront capability is particularly relevant: you can run multiple storefronts/domains from a single backend while giving each storefront its own look, pricing, products and configuration. BigCommerce BigCommerce

It also explicitly supports headless storefronts and lets you choose your frontend technology. BigCommerce BigCommerce

That makes an architecture like this attractive:

                    BigCommerce
                         │
        ┌────────────────┼────────────────┐
        │                │                │
   storefront 1     storefront 2     storefront 3
        │                │                │
    Next.js          Next.js          Next.js
        │                │                │
    Campaign A       Campaign B       Campaign C

BigCommerce becomes particularly interesting if:

• you want many genuinely separate storefronts;
• you want more control over your frontend stack;
• you have a substantial internal engineering organization;
• you want to minimize dependence on a proprietary frontend;
• you're integrating a sophisticated PIM/CMS/CDP stack.

3. commercetools

I'd consider commercetools if you're operating at the level where ecommerce is essentially an internal technology platform.

Its model explicitly supports multiple "Stores" within a project, allowing different commerce experiences while sharing resources and maintaining data isolation. commercetools Documentation

This is attractive if you want:

                    Commerce Platform
                          │
       ┌──────────────────┼──────────────────┐
       │                  │                  │
     Brand A            Brand B          Campaigns
       │                  │                  │
       └──────────────┬───┴──────────────┬───┘
                      │                  │
                    PIM                CMS
                      │                  │
                    ERP                CDP
                      │                  │
                  Inventory          Personalization

But there's a tradeoff: you are buying flexibility rather than simplicity. You'll need to own much more of the architecture—frontend, CMS, search, promotions, integrations, deployment, etc.

For a fast-fashion company whose competitive advantage is how quickly marketing can launch campaigns, that engineering overhead may or may not be worthwhile.

What I'd actually build

If I were designing this for your organization, I'd start with:

Shopify Plus + headless campaign layer + CMS + PIM/DAM + CDP

Something along these lines:

                         ┌───────────────┐
                         │    Shopify    │
                         │     Plus      │
                         └───────┬───────┘
                                 │
                    Commerce / Checkout / Orders
                                 │
                ┌────────────────┴────────────────┐
                │                                 │
        ┌───────▼────────┐                ┌───────▼───────┐
        │  PIM / Product │                │  OMS / ERP    │
        │     Data       │                │  Inventory    │
        └────────────────┘                └───────────────┘
                │
        ┌───────▼────────┐
        │      CMS       │
        │ Campaign pages │
        │ Landing pages  │
        └───────┬────────┘
                │
       ┌────────┴─────────┐
       │                  │
 ┌─────▼──────┐     ┌─────▼──────┐
 │ Campaign A │     │ Campaign B │
 │ microsite  │     │ microsite  │
 └────────────┘     └────────────┘

The crucial design principle is:

Don't make "microsite" synonymous with "store."

A campaign should ideally be something your marketing team can instantiate from a template:

Create Campaign
      ↓
Choose products
      ↓
Choose campaign template
      ↓
Upload creative
      ↓
Configure merchandising
      ↓
Configure discount
      ↓
Assign domain
      ↓
Publish

rather than:

Request engineering
      ↓
Create ecommerce store
      ↓
Configure payments
      ↓
Configure products
      ↓
Configure inventory
      ↓
Configure checkout
      ↓
Deploy

That distinction becomes very important at fast-fashion scale.

One other architecture decision I'd make

Keep product, inventory, pricing, customer and order data centralized wherever possible, while allowing campaign content, merchandising and frontend presentation to be decentralized.

That gives you:

• rapid campaign launches;
• consistent inventory;
• one order/fulfillment system;
• reusable checkout;
• centralized customer data;
• independent campaign branding;
• easier A/B testing;
• fewer engineering dependencies;
• much less operational duplication.

If you tell me roughly (1) number of microsites/campaigns per month, (2) annual GMV, (3) number of brands, (4) whether each microsite needs its own checkout/domain, and (5) your current stack (Shopify/Magento/SFCC/custom), I can map this into a concrete Shopify Plus vs BigCommerce vs commercetools architecture and estimated TCO.

This is attractive if you want:

                    Commerce Platform
                          │
       ┌──────────────────┼──────────────────┐
       │                  │                  │
     Brand A            Brand B          Campaigns
       │                  │                  │
       └──────────────┬───┴──────────────┬───┘
                      │                  │
                    PIM                CMS
                      │                  │
                    ERP                CDP
                      │                  │
                  Inventory          Personalization

But there's a tradeoff: you are buying flexibility rather than simplicity. You'll need to own much more of the architecture—frontend, CMS, search, promotions, integrations, deployment, etc.

For a fast-fashion company whose competitive advantage is how quickly marketing can launch campaigns, that engineering overhead may or may not be worthwhile.

What I'd actually build

If I were designing this for your organization, I'd start with:

Shopify Plus + headless campaign layer + CMS + PIM/DAM + CDP

Something along these lines:

                         ┌───────────────┐
                         │    Shopify    │
                         │     Plus      │
                         └───────┬───────┘
                                 │
                    Commerce / Checkout / Orders
                                 │
                ┌────────────────┴────────────────┐
                │                                 │
        ┌───────▼────────┐                ┌───────▼───────┐
        │  PIM / Product │                │  OMS / ERP    │
        │     Data       │                │  Inventory    │
        └────────────────┘                └───────────────┘
                │
        ┌───────▼────────┐
        │      CMS       │
        │ Campaign pages │
        │ Landing pages  │
        └───────┬────────┘
                │
       ┌────────┴─────────┐
       │                  │
 ┌─────▼──────┐     ┌─────▼──────┐
 │ Campaign A │     │ Campaign B │
 │ microsite  │     │ microsite  │
 └────────────┘     └────────────┘

The crucial design principle is:

Don't make "microsite" synonymous with "store."

A campaign should ideally be something your marketing team can instantiate from a template:

Create Campaign
      ↓
Choose products
      ↓
Choose campaign template
      ↓
Upload creative
      ↓
Configure merchandising
      ↓
Configure discount
      ↓
Assign domain
      ↓
Publish

rather than:

Request engineering
      ↓
Create ecommerce store
      ↓
Configure payments
      ↓
Configure products
      ↓
Configure inventory
      ↓
Configure checkout
      ↓
Deploy

That distinction becomes very important at fast-fashion scale.

One other architecture decision I'd make

Keep product, inventory, pricing, customer and order data centralized wherever possible, while allowing campaign content, merchandising and frontend presentation to be decentralized.

That gives you:

• rapid campaign launches;
• consistent inventory;
• one order/fulfillment system;
• reusable checkout;
• centralized customer data;
• independent campaign branding;
• easier A/B testing;
• fewer engineering dependencies;
• much less operational duplication.

If you tell me roughly (1) number of microsites/campaigns per month, (2) annual GMV, (3) number of brands, (4) whether each microsite needs its own checkout/domain, and (5) your current stack (Shopify/Magento/SFCC/custom), I can map this into a concrete Shopify Plus vs BigCommerce vs commercetools architecture and estimated TCO.

For a digital-first enterprise that wants to decouple frontend and backend, the “best” headless commerce platform depends less on storefront technology and more on your commerce complexity, engineering maturity, and operating model. For large-scale deployments, the shortlist usually narrows to a few platforms. CIOPages Shopify

Enterprise headless commerce shortlist

Shopify## My typical recommendation by enterprise profile

1. You are building a true composable commerce architecture

Choose commercetools.

This is usually the strongest fit when the goal is:

• React/Next.js/mobile/native apps as independent channels
• Multiple brands, regions, or business units
• Replacing individual services independently (search, CMS, promotions, checkout)
• A dedicated architecture/platform engineering team

It is designed around API-first commerce rather than a traditional storefront platform. Shopify

2. You are a large retailer/manufacturer with complex operations

Choose Salesforce Commerce Cloud if you already rely heavily on:

• Salesforce CRM
• Service Cloud
• Marketing Cloud
• Complex customer segmentation
• B2B account structures
• Multi-country commerce operations

Salesforce positions its headless approach around using commerce APIs with independently built experiences across channels. Salesforce

3. You want enterprise scale without building a commerce platform team

Choose Shopify Plus with a headless frontend.

This can work well when:

• Your business is primarily DTC
• You want faster time-to-market
• Your commerce logic is relatively standard
• You want SaaS operations rather than owning infrastructure

Shopify’s headless approach allows custom storefronts while keeping Shopify’s commerce backend. Pointerflow

Architecture considerations before choosing

For a large-scale headless deployment, evaluate:

Commerce domain complexity

• Simple catalog + checkout → Shopify Plus may be sufficient
• Complex pricing, contracts, inventory rules, marketplaces → composable platforms become more attractive

Engineering capability

A headless architecture shifts responsibility from vendor themes to your engineering organization:

• Frontend platform team
• API governance
• CI/CD pipelines
• Observability
• Performance engineering
• Integration ownership

Integration landscape

Check how the platform connects with:

• ERP (SAP, Oracle, Dynamics)
• OMS
• PIM
• CMS
• Search
• Tax engines
• Payments
• Loyalty systems

Global scale

For multinational deployments, look closely at:

• Multi-currency
• Multi-language
• Regional catalogs
• Tax rules
• Data residency
• Peak traffic handling

A practical enterprise decision matrix

• Need maximum architectural freedom: commercetools
• Already a Salesforce enterprise: Salesforce Commerce Cloud
• Need fastest enterprise launch: Shopify Plus
• SAP-driven organization: SAP Commerce Cloud
• Need maximum customization/control: Adobe Commerce

For a digital-first enterprise explicitly choosing headless because frontend and backend must evolve independently, I would generally start the evaluation with commercetools vs Salesforce Commerce Cloud, then include Shopify Plus if operational simplicity and speed are major priorities. CIOPages Shopify

If you share your approximate GMV/revenue band, B2C vs B2B mix, number of regions, ERP (SAP/Oracle/etc.), and whether you have an internal engineering platform team, I can narrow this to a more specific recommendation.

For a digital-first enterprise whose primary goal is to decouple frontend and backend, I’d put commercetools at the top of the shortlist—not because it is universally “best,” but because its architecture most directly matches that requirement.

How I’d shortlist them

1. commercetools — strongest architectural fit

commercetools is explicitly built around modular, API-first commerce. Its model allows commerce capabilities to be assembled as independent components and scaled/replaced independently. It currently says more than 500 enterprises run on the platform. commercetools

That makes it particularly compelling if you're thinking:

Next.js/React frontend → API layer → commerce services → PIM/CMS/search/payments/ERP

rather than:

Commerce platform → customized presentation layer

The trade-off is that you're taking on more architectural responsibility. Your engineering organization needs to be comfortable owning integrations, orchestration, observability, caching, deployment architecture, and potentially multiple vendors.

2. Salesforce Commerce Cloud — strong enterprise alternative

Salesforce has made its Composable Storefront specifically around decoupling the experience layer from commerce logic. Its PWA Kit is React-based, while Managed Runtime provides a scalable managed hosting environment; the Commerce APIs can also be combined with third-party CMS, search, and other components. Developer Developer

I'd investigate this particularly seriously if your enterprise already has substantial Salesforce investment—because the surrounding ecosystem can matter as much as the commerce engine itself.

3. Shopify Plus / Enterprise — less architectural overhead

Shopify is worth considering if your priority is rapid execution at enormous scale rather than maximum architectural decomposition.

Shopify supports headless storefronts through its APIs, Hydrogen/Oxygen and other frontend approaches, while its Enterprise offering provides higher platform limits, contractual service levels and dedicated account management. Shopify Shopify

The important distinction is that Shopify gives you a decoupled frontend, but it isn't trying to make every commerce capability independently replaceable in the way a deeply composable platform does.

4. BigCommerce — pragmatic middle ground

BigCommerce provides REST and GraphQL APIs, multiple storefronts, and integrations with CMS/PIM/DXP/etc. Its Catalyst architecture is built around Next.js, React Server Components and its GraphQL Storefront API. BigCommerce

It can therefore be attractive if your team wants headless without taking on quite as much platform engineering as a fully composable architecture.

BigCommerce also currently advertises enterprise infrastructure with 99.98% uptime. BigCommerce

My architectural decision rule

I'd frame the decision this way:

• Maximum frontend/backend independence + composability: commercetools
• Enterprise Salesforce ecosystem + composable storefront: Salesforce Commerce Cloud
• Maximum operational simplicity + enormous scale + headless: Shopify Enterprise/Plus
• API-first headless with a relatively pragmatic implementation: BigCommerce

For your stated requirement, I'd start the RFP with commercetools, Salesforce Commerce Cloud, and Shopify Enterprise, then make the decision based on your actual commerce complexity rather than frontend technology.

The key question isn't really “which has the best headless APIs?” All three can decouple the frontend. It's how much of the commerce stack you want to own versus outsource to the platform.

If you give me your annual GMV, monthly peak traffic/orders, B2C vs B2B, number of countries/stores, ERP/PIM/CMS, and whether you're targeting Next.js, I can build a more detailed enterprise architecture comparison—including TCO, scalability, API model, multi-region, checkout, B2B, extensibility, and migration risk.

Next.js/React frontend → API layer → commerce services → PIM/CMS/search/payments/ERP

rather than:

Commerce platform → customized presentation layer

The trade-off is that you're taking on more architectural responsibility. Your engineering organization needs to be comfortable owning integrations, orchestration, observability, caching, deployment architecture, and potentially multiple vendors.

2. Salesforce Commerce Cloud — strong enterprise alternative

Salesforce has made its Composable Storefront specifically around decoupling the experience layer from commerce logic. Its PWA Kit is React-based, while Managed Runtime provides a scalable managed hosting environment; the Commerce APIs can also be combined with third-party CMS, search, and other components. Developer Developer

I'd investigate this particularly seriously if your enterprise already has substantial Salesforce investment—because the surrounding ecosystem can matter as much as the commerce engine itself.

3. Shopify Plus / Enterprise — less architectural overhead

Shopify is worth considering if your priority is rapid execution at enormous scale rather than maximum architectural decomposition.

Shopify supports headless storefronts through its APIs, Hydrogen/Oxygen and other frontend approaches, while its Enterprise offering provides higher platform limits, contractual service levels and dedicated account management. shopify.com shopify.com

The important distinction is that Shopify gives you a decoupled frontend, but it isn't trying to make every commerce capability independently replaceable in the way a deeply composable platform does.

4. BigCommerce — pragmatic middle ground

BigCommerce provides REST and GraphQL APIs, multiple storefronts, and integrations with CMS/PIM/DXP/etc. Its Catalyst architecture is built around Next.js, React Server Components and its GraphQL Storefront API.

For a CTO of a marketplace operator, the right platform depends on whether you are building a true marketplace operating system (seller onboarding, governance, commissions, catalog quality, payouts, workflows) or adding marketplace capability to an existing commerce stack.

At enterprise scale, the main platforms I would evaluate are:

My shortlist for a CTO evaluating a marketplace at scale

1. Mirakl — if marketplace is the core business capability

• Best when you expect:

• thousands of sellers
• complex seller onboarding
• catalog ingestion from many sources
• marketplace governance teams
• seller quality scoring and approval workflows

Mirakl2. Spryker — if you need a composable commerce platform

• Better fit when marketplace functionality must coexist with:

• B2B commerce
• complex pricing
• customer-specific catalogs
• headless storefronts
• custom workflows

Spryker3. Build on a commerce engine (Adobe/Broadleaf/custom) — if differentiation matters

• Consider this when your marketplace model is unusual:

• managed services marketplace
• procurement exchange
• vertical marketplace
• highly customized fulfillment model

Broadleaf CLEARgo### CTO architecture checklist

At scale, I would not evaluate only the storefront. The critical capabilities are:

• Seller lifecycle

• self-service registration
• KYC/compliance workflows
• contracts and commissions
• seller performance dashboards
• Catalog operations

• supplier feeds/API ingestion
• SKU matching and deduplication
• taxonomy governance
• attribute normalization
• approval workflows
• Marketplace transactions

• split carts
• split fulfillment
• commissions
• refunds/returns
• payouts
• Platform operations

• seller support tooling
• audit trails
• analytics
• fraud/risk controls
• API/event architecture

• avoid tightly coupling seller systems to your storefront
• use event-driven integrations for catalog, inventory, and order changes

If you are operating something like Amazon-style third-party retail, B2B procurement, or a vertical marketplace with 10k+ sellers, I would start the evaluation with Mirakl vs Spryker vs a composable build (Broadleaf/custom) rather than a traditional ecommerce platform. Mirakl Spryker Broadleaf

A useful next step would be to map the choice against your scale: number of sellers, SKU count, GMV, geography, B2C vs B2B, and whether you own inventory or run seller-fulfilled dropship.

If global shopper latency and edge performance are your primary criteria, the enterprise platforms separate into two fairly different models:

The two I'd investigate first

Shopify Plus is compelling if you want the platform to take care of the edge layer. Shopify explicitly says its CDN is backed by Cloudflare and provides global edge caching, HTTP/3, Brotli/gzip compression and TLS 1.3. Shopify Shopify

For headless, Shopify's Oxygen is particularly interesting: Hydrogen storefronts execute on a worker-based runtime at the edge, with Cloudflare's workerd underneath. Shopify Shopify

The important tradeoff is control. Shopify deliberately tells merchants not to put another CDN/proxy in front of the storefront because it adds another network hop. Shopify So you get a very optimized managed edge, but you're not getting the same degree of CDN customization you'd have with Fastly/Akamai directly.

Adobe Commerce Cloud is the more interesting choice if your team considers the edge itself part of the application architecture. Adobe Commerce Cloud uses Fastly as its edge/full-page caching layer, and Fastly is integrated into the platform rather than being something you have to bolt on. Experience League Experience League

You can customize Fastly with VCL/edge modules, configure origin shielding, tune backends and timeouts, and use Fastly to cache GraphQL responses in headless deployments. Experience League Experience League

That makes Adobe particularly interesting for a sophisticated global architecture where you care about things like:

• geographic cache strategy
• aggressive cache/purge control
• origin shielding
• edge personalization/routing
• GraphQL caching
• custom VCL
• integrating multiple origins
• minimizing origin trips during traffic spikes

So, architecturally

If your question is "which platform gives us the strongest built-in edge/CDN foundation?", I'd narrow the evaluation to:

Adobe Commerce Cloud ↔ Shopify Plus

with the distinction being:

• Shopify Plus: "Give us an extremely optimized global edge and don't make us manage it."
• Adobe Commerce: "Give our engineering team substantial control over how commerce interacts with the edge."

If you're running a headless global storefront, I'd give especially serious consideration to Shopify Hydrogen/Oxygen vs. Adobe Commerce + Fastly, because that's where the architectural differences become much more consequential than simply comparing CDN POP counts.

One caveat: I wouldn't choose based on advertised "number of CDN locations." For ecommerce, TTFB to the actual commerce application, cacheability of product/category HTML, cart/API latency, origin distance, cache invalidation, and third-party JavaScript generally matter more than raw POP count.

If you tell me your approximate architecture (e.g. Shopify Plus vs Adobe vs Salesforce, headless vs traditional, regions such as US/EU/APAC, and whether product/catalog APIs are a major bottleneck), I can break down the edge request path and likely latency tradeoffs for each.