Answers that do not mention BigCommerce

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.

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.

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 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 small handmade-goods shop on a tight budget, I’d start with Square Online.

• Square Online — best if you want a simple store that can grow: Its Free plan has $0/month in subscription costs and lets you build an online store and take payments; you pay processing fees when you make a sale. Square Square
• Big Cartel — especially good if you only have a tiny catalog: Its free Gold plan supports up to 5 products, online selling, cards/PayPal, and basic storefront features. Big Cartel
• Etsy — useful if you want access to an existing marketplace: It's not free per sale: Etsy currently charges $0.20 per listing plus a 6.5% transaction fee, along with payment-processing and potentially other fees. Etsy Help

What I'd do in your situation

Start with Square Online if you have more than ~5 products or expect your catalog to grow. You can launch without paying a monthly subscription, then worry about a custom domain and paid features after you're actually making sales.

Choose Big Cartel instead if you're starting with just a handful of handmade products and want a storefront geared toward artists/makers.

squareup.com
bigcartel.com

If you tell me roughly how many products you'll sell and whether you also sell in person at markets/craft fairs, I can narrow it down to the cheapest setup for you.

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 solo indie maker with zero dev experience, I’d narrow it to these:

• squareup.com — easiest all-around free starting point. $0/month, no coding required, hosted store, payments, shipping/pickup, inventory, and SEO tools. The free plan charges a transaction fee when you sell. Square Square
• bigcartel.com — great for a tiny indie catalog. Its Gold plan is genuinely $0 with no credit card required, and supports 5 products, variants, payments, tax tools, and a simple template. Big Cartel says you can launch in about 30 minutes. Big Cartel
• ecwid.com — good if you want a more traditional website. It emphasizes zero technical experience, drag-and-drop editing, templates, and a free company.site domain. Ecwid | E-Commerce Shopping Cart Ecwid | E-Commerce Shopping Cart
• shopify.com — consider later rather than starting here. It's very beginner-friendly and built to scale, but its lowest-cost options aren't as attractive if your priority is $0 upfront. Shopify

My practical pick

Start with Square Online if you're selling physical products. You can get a store live without touching code or paying a monthly subscription, then upgrade only when you actually need more customization. Square

If you're selling 5 or fewer products and want the absolute simplest indie-maker setup, I'd look at Big Cartel first. Big Cartel

If you tell me what you're selling (physical, digital, or both) and roughly how many products, I can narrow it down to one and give you a 30-minute setup plan.

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.

Yes. If you already have WordPress and just need a simple, inexpensive store, I’d look at these three:

1. woocommerce.com — best if you want a traditional store

• The core plugin is free with no monthly subscription and no WooCommerce revenue share. WooCommerce
• Works directly inside WordPress.
• Handles physical products, inventory, shipping, coupons, taxes, etc.
• You can start with just the free plugin and add paid extensions only if you actually need them.
• Your main ongoing costs are your existing hosting plus payment-processing fees.

For a small store selling physical products, this is probably where I'd start.

2. surecart.com — potentially simpler

SureCart is particularly interesting if you don't need a huge, complicated catalog. Its Launch plan is currently $0/month, but charges a 2.9% transaction fee in addition to your payment processor's fees. SureCart SureCart

It supports physical products, digital products, subscriptions, payments, coupons, order management, and shipping. SureCart

The tradeoff is basically:

WooCommerce: more control, potentially lower costs as sales grow
SureCart: simpler managed setup, but the transaction fee matters if you sell a lot

3. ecwid.com — good if you want the store separate from WordPress

Ecwid can be embedded into an existing WordPress site rather than making WordPress itself the ecommerce system. Its plans support adding a store to an existing website, and Ecwid says it charges no transaction fees. Ecwid | E-Commerce Shopping Cart

It's attractive if you want something relatively hands-off, although the ongoing subscription can make it less economical than WooCommerce for a very small store.

What I'd choose

If you told me "I have a normal WordPress site, maybe 5–50 products, and I just want people to buy things without spending much", I'd probably use:

WordPress + WooCommerce + Stripe/PayPal + your existing hosting.

You can get surprisingly far without buying any WooCommerce extensions. WooCommerce

If you tell me what you're selling (physical products, digital downloads, services, memberships, etc.) and roughly how many products, I can suggest the cheapest setup and exactly which plugins you'd need, including what you can avoid paying for.

If your main business is building custom integrations for clients, I’d look first at Medusa.

Why Medusa fits a freelance integration shop

Medusa is built around a modular architecture rather than treating the store as a giant monolith. Its current architecture gives you:

• Custom modules for client-specific domains and third-party integrations.
• Workflows for multi-step business logic, including rollback/data consistency.
• API routes, subscribers, scheduled jobs, and admin extensions inside plugins.
• Access to the underlying commerce modules—products, orders, customers, inventory, payments, fulfillment, etc.—from your custom code.
• Reusable plugins/modules that you can carry from one client project to another. Medusa Docs Medusa Docs Medusa Docs

That last point is particularly attractive for a freelancer. You could, for example, build your own reusable integration package for an ERP, PIM, shipping provider, or CRM and deploy it across multiple client stores.

How I'd think about the main options

Saleor is also very extensible, but its model is more deliberately API/app oriented: its documentation emphasizes GraphQL, apps, webhooks, and extending the dashboard. Saleor Documentation

Medusa, by contrast, lets your custom code live directly in the application architecture. Its modules can define their own models/services, and workflows can combine those custom modules with Medusa's built-in commerce modules. Medusa Docs Medusa Docs

For a freelance developer, I'd choose based on stack

If you're primarily TypeScript/Node → Medusa.

If you're primarily Python/Django/GraphQL → Saleor.

If you're primarily PHP/Symfony → Sylius.

If you're primarily PHP/Laravel → Bagisto.

If your clients mostly want "WordPress + ecommerce + whatever plugin does it" → WooCommerce.

The interesting distinction is that WooCommerce may be the easiest to extend in terms of sheer ecosystem, whereas Medusa is arguably the cleaner starting point when your actual product is custom engineering. Current comparisons likewise distinguish WooCommerce's enormous extension ecosystem from Medusa's more developer-oriented modular architecture. OSSAlt OpenReplay Blog

For your particular business model, I'd seriously consider standardizing on Medusa + Next.js + PostgreSQL + Redis and building a small internal library of reusable integration modules. Medusa's own docs explicitly support reusable plugins containing modules, workflows, API routes, subscribers, scheduled jobs, and admin extensions. Medusa Docs Medusa Docs

If you tell me what kinds of integrations your clients typically need (ERP, Shopify migration, Stripe, shipping, PIM, marketplaces, subscriptions, B2B pricing, etc.), I can compare Medusa vs Saleor vs Sylius specifically for those workloads.

For complex international tax, currency, language, and regional rules, I’d shortlist Saleor and Medusa. Saleor is particularly designed around multi-channel, multi-currency, tax, warehouse, and permission complexity. Macrostack eryxinnovationslab.com

• Saleor — strongest fit for highly complex localization; Python/GraphQL, channel-based regionalization.
• Medusa — excellent if your team is TypeScript/Node; its Region module supports localized currencies, taxes, shipping, and payments. Medusa
• Shopware — worth considering if you want a more turnkey, traditional ecommerce platform rather than a headless commerce backend. EU Vetted

For your specific description, I’d investigate Saleor first, especially if tax jurisdiction logic and many distinct markets are central requirements.

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:

For a static/headless storefront, I’d shortlist these:

• Medusa — my default for a TypeScript/JavaScript stack. REST API + JS SDK, modular architecture, and MIT-licensed core. Vendure Pawel Owerczuk
• Saleor — excellent if you prefer GraphQL and have Python/Django expertise; particularly strong for multi-channel commerce. Vendure
• Vendure — TypeScript + NestJS + GraphQL, with a structured plugin system; worth considering for complex B2B/multi-channel setups. Vendure Eryx Innovations Lab

For a static site specifically, I’d start with Medusa unless GraphQL is a firm requirement. Your architecture can be:

Static site → Medusa API → PostgreSQL

If you tell me your frontend stack (Astro, Next.js, plain HTML, etc.) and whether you need subscriptions/B2B/multiple stores, I can narrow it down.

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 one-person creative business selling ebooks and printable art, I’d look at these three:

• payhip.com — probably the simplest fit. Its free plan is $0/month + 5% per sale, with unlimited products and revenue, and it specifically supports ebooks, PDFs, digital downloads, coupons, affiliates, and embedded checkout. You still pay Stripe/PayPal processing fees. Payhip Payhip Payhip
• lemonsqueezy.com — good if you want taxes handled for you. There's no monthly ecommerce fee; the standard fee is 5% + $0.50 per transaction, with Lemon Squeezy acting as merchant of record and handling sales-tax/VAT collection and remittance. LemonSqueezy Lemon Squeezy Docs
• gumroad.com — very easy to launch, but pricier. There’s no monthly fee, but direct sales cost 10% + $0.50, and sales through its Discover marketplace cost 30%. Gumroad also handles worldwide sales-tax obligations as merchant of record. Gumroad

My practical pick

Start with Payhip if your priority is simple storefront + low ongoing cost. You can put your ebooks and printable bundles in one storefront without paying a monthly subscription, then move to its $29/month plan if your sales volume eventually makes the lower 2% transaction fee worthwhile. Payhip

If tax/VAT administration is something you particularly don't want to deal with, I'd instead consider Lemon Squeezy.

If you tell me roughly how much you expect to charge per product (e.g. $5, $15, $30) and how many sales/month you expect, I can calculate the approximate fees for each and show you the break-even point.

For a small indie studio selling downloadable game builds + license/download keys, I’d shortlist SendOwl and Lemon Squeezy, with the choice depending on whether delivery security or all-in-one commerce matters more.

My shortlist

SendOwl is probably the closest match to your requirements. It supports software/ZIP files, automatically delivers purchases, lets you limit downloads and expiration, and supports license-key management. Its current business plans advertise a 50 GB maximum file size. SendOwl Help Center SendOwl

It also supports self-hosting the actual builds on Amazon S3 while letting SendOwl handle the purchase/access layer, which is attractive if your games are tens of GB and you want more control over storage/CDN costs. SendOwl Help Center

Lemon Squeezy is particularly interesting if you want the commerce side bundled together. It can issue license keys automatically, and its download URLs are signed, expire after one hour, and are rate-limited. The current product limit is 5 GB total files per product, however, so that can become restrictive for modern AAA-sized indie builds. Lemon Squeezy Docs Lemon Squeezy Docs

itch.io is worth considering if you don't need your own checkout. Its download keys are unique URLs granting access to a game's files, and its API lets you verify whether a particular key is valid, revoked, or associated with a purchase. itch.io itch.io

What I'd build for your studio

For builds larger than a few GB, I'd use:

Your store/checkout → SendOwl → private object storage/CDN → expiring download URL

And keep the license key separate from the download URL. That way, leaking a download URL doesn't automatically constitute leaking a reusable game key.

For particularly large games, I'd also consider S3-compatible object storage + a CDN underneath the delivery service rather than treating Google Drive/Dropbox as your file host. SendOwl explicitly supports private S3 hosting and signed URL expiry. SendOwl Help Center

If you tell me roughly how large your builds are (e.g. 2 GB, 20 GB, 100 GB), how many sales/month you expect, and whether you already have a website/Stripe checkout, I can narrow this down to the most economical architecture.

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 many creators sell digital goods and receive payouts, you’ll want a platform that supports:

• Creator/vendor accounts
• Digital file delivery (downloads, licenses, courses, assets, etc.)
• Commission splits
• Automated seller payouts
• Vendor dashboards
• Tax/payment compliance support

Here are some options depending on whether you want a hosted marketplace or to build your own marketplace:

Some marketplace-focused digital solutions include Shopify-based multi-vendor setups where creators upload products, commissions are calculated, and payouts are handled through payment integrations. Garnet Marketplace PuppetVendors

If you are building a marketplace like "Etsy for digital products"

A common architecture is:

Frontend

• Shopify, Webflow, Bubble, Next.js, or custom React app

Marketplace engine

• Sharetribe
• Arcadier
• Custom backend

Payments

• Stripe Connect — commonly used for marketplace payouts, because it can route payments and split funds between the marketplace and sellers

Digital delivery

• Amazon S3 + signed URLs
• Digital downloads plugin
• Built-in asset delivery system

My shortlist by use case

Fastest launch (no/low code):

• Shopify + multi-vendor marketplace app Garnet Marketplace PuppetVendors
• Arcadier

Most customizable marketplace:

• Sharetribe + Stripe Connect

WordPress-based:

• WooCommerce + Dokan/WCFM-style vendor marketplace plugins

Creator-first SaaS marketplace:

• Consider newer digital creator marketplaces such as Knotwell, which focuses on digital assets and creator revenue sharing. Knotwell

If you’re aiming for something like Gumroad + Etsy combined (thousands of creators, automatic payouts, subscriptions, licensing, affiliate commissions), I’d lean toward Sharetribe/Stripe Connect or a custom stack rather than a normal ecommerce platform.

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 down to Payhip, Gumroad, and Podia. You don't need to build or host a website yourself with any of them.

My practical shortlist

Payhip would be my starting point for your situation. Its free plan gives you unlimited products and revenue, with a 5% transaction fee. It specifically supports ebooks, PDFs and other digital products, and includes things like coupons, affiliates and pay-what-you-want pricing. Payhip Payhip

payhip.com

Gumroad is arguably even simpler. There's no monthly subscription, and it handles sales-tax obligations as merchant of record. The tradeoff is a substantially higher transaction fee: 10% + $0.50 on sales through your profile/direct links, or 30% when a customer comes through its Discover marketplace. Gumroad

gumroad.com

Podia makes more sense if you eventually want to sell ebooks alongside courses, memberships, coaching, email marketing, and a more complete website. It supports PDFs, ebooks, audio, video, ZIP files and other downloads, with built-in sales pages and delivery. Podia Podia Help Center

podia.com

What I'd do if I were starting from zero

I'd start with Payhip, rather than Shopify or WordPress.

Your basic workflow can be:

1. Create your ebook/PDF.
2. Create a free Payhip account.
3. Upload the file.
4. Add a cover image, description and price.
5. Connect Stripe or PayPal.
6. Publish the product.
7. Share the product page wherever you find customers.

You can start without paying a monthly subscription, which is particularly useful while you're testing whether people actually want your products. Payhip

If you tell me what kinds of digital products you want to sell (e.g. ebooks, planners, Canva templates, printables, AI prompts, courses, spreadsheets), I can also compare Payhip vs Gumroad vs Etsy vs Shopify specifically for your business model and show you what I'd choose.

Gumroad is arguably even simpler. There's no monthly subscription, and it handles sales-tax obligations as merchant of record. The tradeoff is a substantially higher transaction fee: 10% + $0.50 on sales through your profile/direct links, or 30% when a customer comes through its Discover marketplace. gumroad.com

gumroad.com

Podia makes more sense if you eventually want to sell ebooks alongside courses, memberships, coaching, email marketing, and a more complete website. It supports PDFs, ebooks, audio, video, ZIP files and other downloads, with built-in sales pages and delivery.

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

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 monthly physical subscription boxes, I’d start with Shopify + Shopify Subscriptions.

Why Shopify fits your requirements

Shopify's first-party Subscriptions app supports automatic weekly, monthly, and yearly renewals. Customers can manage subscriptions, including pausing, resuming, skipping orders, canceling, updating payment methods, and changing shipping addresses, through their customer account. Shopify Help Center Shopify Help Center

help.shopify.com

The main alternative: WooCommerce

WooCommerce + WooCommerce Subscriptions is worth considering if you already use WordPress or want much more control over your store.

It supports recurring billing, multiple payment gateways, failed-payment rebilling, and a customer My Account → Subscriptions area where subscribers can manage their subscriptions. WooCommerce WooCommerce

The tradeoff is that WooCommerce generally requires more technical setup and ongoing maintenance. The Subscriptions extension itself is currently listed at $279/year, before considering hosting and other extensions. WooCommerce

My practical recommendation

• Starting from scratch: Shopify + Shopify Subscriptions
• Already on WordPress: WooCommerce + WooCommerce Subscriptions
• Want the simplest customer experience: Shopify
• Want maximum technical/customization control: WooCommerce

One important caveat: if your box needs complex subscription logic—for example, letting subscribers choose several products each month, build their own box, swap individual items, add one-time extras to the next shipment, or use sophisticated churn/retention flows—I would look beyond the basic Shopify Subscriptions app and evaluate a dedicated subscription platform/app.

If you tell me what kind of box you're selling, expected monthly subscribers, price per box, and whether customers choose/customize what's inside, I can narrow it down to the best 2–3 setups and compare their actual costs.

The main alternative: WooCommerce

WooCommerce + WooCommerce Subscriptions is worth considering if you already use WordPress or want much more control over your store.

It supports recurring billing, multiple payment gateways, failed-payment rebilling, and a customer My Account → Subscriptions area where subscribers can manage their subscriptions.

The tradeoff is that WooCommerce generally requires more technical setup and ongoing maintenance. The Subscriptions extension itself is currently listed at $279/year, before considering hosting and other extensions.

My practical recommendation

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:

Yes. If you're looking for a subscription-management platform that lets customers gift, pause, and swap items, Skio is a strong match.

• Pause: Customers can pause indefinitely or temporarily, with configurable pause options. Skio Skio
• Swap items: Customers can swap products/variants, adjust quantities, or add products through the customer portal. Skio
• Gift: Skio supports “gift on skip,” allowing a subscriber to gift an upcoming order rather than skip it. It also supports prepaid gift subscriptions where someone buys a subscription for another person. Skio Skio
• Self-service: These actions can be exposed directly to customers in the subscription portal, rather than requiring support intervention. Skio Skio
• Automations: Skio's Journeys can trigger product swaps, gifts, discounts, and other subscription changes based on customer behavior. Skio

skio.com

One important distinction: if by “gifting” you mean “I have an active subscription and want to send this month's item to someone else”, Skio's Gift on Skip feature is particularly relevant. If you mean “buy a 3/6/12-month subscription as a gift for another person”, its prepaid gift subscription feature covers that, although there are some restrictions on what the recipient can change. Skio

If you tell me whether you're on Shopify, WooCommerce, or another commerce platform, I can also give you a short comparison of the best tools for gift + pause + swap specifically.

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.

Yes. What you’re looking for is usually called payment recovery, dunning, or smart retries. These tools automatically detect failed subscription payments, decide when/how often to retry, and help recover customers before their subscriptions churn.

Some common options:

• Stripe — If you already use Stripe Billing, it has built-in revenue recovery features including Smart Retries, failed payment automation, and subscription recovery workflows. Stripe Docs

• Good fit if your shop already runs on Stripe.
• Handles retry timing, customer emails, payment method updates, and subscription status changes.
• Chargebee — Offers Revive (ML-powered retry optimization) plus dunning workflows. It evaluates failed payments using billing/payment context and can automate retry decisions and customer recovery messaging. Chargebee

• Good fit for SaaS, memberships, and subscription-heavy businesses.
• Recurly — Provides Intelligent Retries and revenue recovery tools. Its retry engine can adjust retry timing based on transaction data instead of using one fixed schedule. Recurly Documentation

• Good fit for subscription businesses that want dedicated billing recovery features.
• Churnkey — Focuses more broadly on subscription retention and churn prevention, including cancellation flows and win-back experiences.

Typical setup looks like:

1. Customer’s recurring payment fails.
2. Tool classifies the failure:

• Temporary issue (insufficient funds, bank outage) → retry later.
• Permanent issue (expired card, blocked card) → ask customer to update payment method.
• Sends automated emails/SMS:

• “Your payment failed”
• “Update your card”
• “Your subscription is at risk”
• Retries automatically.
• Restores the subscription when payment succeeds.

For a shop, the best choice depends mostly on your stack:

• Shopify subscriptions: look at Shopify-compatible subscription apps or Stripe/Recharge-style integrations.
• Stripe Billing already in use: start with Stripe’s built-in recovery.
• Large subscription catalog / SaaS: consider Chargebee or Recurly.
• Custom checkout: use your payment processor’s recovery APIs plus a dunning layer.

If you tell me what your shop runs on (Shopify, WooCommerce, Stripe, Magento, custom, etc.) and whether you sell subscriptions or one-time products, I can narrow it down.

For your requirements, I’d look at B2B-first commerce platforms rather than a standard consumer store builder. You need three workflows to work together:

• Wholesale registration + approval — businesses apply, you review them, then activate their account.
• Net 30 invoicing — approved accounts get credit terms and invoices rather than paying by card.
• Sales-rep commissions — orders are attributed to reps and commissions are calculated/tracked.

My shortlist

Willow Commerce is the one I'd investigate first. Its B2B offering explicitly supports company accounts, customer-specific pricing, purchase orders, Net 30/60/90 terms, invoicing/AR, and—importantly for your requirement—assigning sales reps to B2B accounts and automatically tracking commissions based on order value, product category, or custom rules. Willowcommerce Willowcommerce

willowcommerce.com

Shopify B2B is worth considering if you want the broader Shopify ecosystem. Shopify natively supports company accounts and payment terms including Net 30, while an app such as TermFlo can handle wholesale applications, approval, credit limits, and receivables. You'd likely add a sales-rep/commission app or connect your CRM/ERP for commissions. Shopify Help Center TermFlo

help.shopify.com

OrderDock is particularly interesting if you're primarily a wholesaler/distributor: it advertises native Net 30/60, buyer accounts, custom pricing, order approvals, and a sales-rep portal. Orderdock

orderdock.app

What I'd choose based on your workflow

If your process is roughly:

Prospect → business applies → staff approves account → assign sales rep → buyer gets customer-specific pricing → buyer orders → Net 30 invoice → rep gets commission

then Willow Commerce is the closest apparent all-in-one match based on the features its current documentation lists. Willowcommerce

If you tell me what you're selling, approximate number of customers/reps, and whether you already use QuickBooks, NetSuite, Salesforce, etc., I can narrow this down to 2–3 platforms and compare actual pricing, commission functionality, accounting integrations, and implementation complexity.

Yes. If by salesperson-assisted ordering you mean a rep can select a business account, see its customer-specific pricing/history, build or share a cart, create a quote, and ultimately place an order on the customer's behalf, several B2B commerce platforms support this.

Particularly relevant options

• **** — Very close to your description

For a secure B2B storefront with IP-restricted access, per-account content, and contract pricing, the best choice depends heavily on whether you need a packaged SaaS platform or a highly customized portal. The key capabilities to look for are:

• Identity and access control

• SSO/SAML/OIDC support
• MFA
• customer approval workflows
• IP allowlists or VPN/private-network restrictions (often handled via an identity provider or edge layer)
• role-based access (buyer, approver, admin)
• Account-level commerce rules

• customer-specific catalogs
• negotiated/contract price lists
• account-specific promotions
• restricted SKUs/content
• buyer permissions
• Enterprise integration

• ERP synchronization
• CRM integration
• contract/CPQ systems
• audit logs

Shortlist

1. Virto Commerce — Best fit for complex enterprise B2B

Good when you need deep control over customer-specific experiences.

Strengths:

• Account-specific catalogs and pricing
• Contract price lists
• Role-based workflows
• Customer-specific content and product visibility
• API-first architecture for custom security layers Virto Commerce Virto Commerce

Typical architecture:

• Virto Commerce for storefront + commerce rules
• Identity provider (for example, enterprise SSO/MFA)
• Cloud WAF/reverse proxy for IP restrictions

Best for:

• Manufacturers
• Distributors
• Regulated industries
• Large partner portals

Tradeoff:

• More implementation effort than pure SaaS.

2. Shopify Plus B2B — Best if you want faster deployment

Shopify Plus B2B supports company accounts, catalogs, customer-specific pricing, and restricted B2B purchasing experiences. Catalogs can control products and pricing by company/location. Shopify Help Center Shopify Help Center

Best for:

• Mid-market B2B brands
• Companies already using Shopify
• Teams wanting lower operational overhead

Tradeoff:

• IP-restricted access usually requires an additional layer (identity provider, app, VPN, or edge security service).
• Extremely complex contract pricing can require customization.

3. Adobe Commerce (Magento) — Best for custom B2B workflows

A strong option when you need:

• custom authorization logic
• complex pricing engines
• multiple business units
• bespoke integrations

Best for:

• Enterprises with development teams

Tradeoff:

• Higher build and maintenance cost.

4. Headless commerce + custom portal — Best for maximum security/control

A common enterprise pattern:

Frontend

• Next.js / React portal

Commerce

• Virto, Adobe Commerce, commercetools, or similar

Identity

• Okta / Azure AD / Auth0

Security

• Cloudflare Access, AWS PrivateLink, VPN, or zero-trust gateway

Data

• ERP as source of truth for pricing/contracts

This is usually the cleanest design if "only users from approved corporate networks can access" is a hard requirement.

My practical recommendation by scenario

A common production architecture would be:

Corporate User
      |
      v
Zero Trust Gateway (IP rules + MFA)
      |
      v
B2B Storefront
      |
      +--> Customer Account Service
      |
      +--> Pricing Engine
      |
      +--> ERP (contracts, inventory, orders)

One important question: is the IP restriction meant to protect the entire storefront (only accessible from customer corporate networks), or only to add an extra check after login? That changes the recommended architecture quite a bit.

For a B2B ecommerce business, I’d structure this as a trade-credit + AR layer sitting between your storefront and ERP/accounting system, rather than trying to manage everything with native ecommerce payment terms.

Recommended setup

1. Customer/trade accounts

• Create a B2B company account for each customer.
• Store approved payment terms: Net 15/30/60/90.
• Maintain billing contacts, PO requirements, tax details, and account status.
• Give customers a self-service view of invoices, payments, statements, and available credit.

2. Credit-limit engine
Treat credit as an exposure calculation, not simply a field on the customer record:

Available credit = approved limit − unpaid invoices − open/committed orders + eligible credits/payments

The checkout should check that amount before accepting an order. Modern B2B credit systems can block over-limit orders or route them to an approval workflow. gmi.softwaretermflo.com

I'd also support:

• Per-customer credit limits
• Temporary credit-limit overrides
• Manual finance approval
• Automatic blocks for seriously overdue accounts
• Credit utilization alerts
• Full audit trail of limit changes

3. Automated invoicing + collections
When an order ships or reaches your configured billing event:

Order → Invoice → Due date → Reminder sequence → Payment → Reconciliation

For example:

Automated invoice reminders and AR aging are already standard capabilities in platforms such as Stripe. stripe.com

What I'd actually use

If you're on Shopify, I'd look first at a dedicated B2B credit/AR application rather than building this yourself. For example, TermFlo specifically combines Shopify B2B accounts, credit-limit enforcement, AR aging, statements and automated reminders. gmi.softwaretermflo.com

Another option is TradeLiq, which combines credit limits, invoices, automated dunning, payments and a B2B customer portal in one Shopify-oriented stack. tradeliq.com

If you need credit underwriting/financing as well as account management, Resolve is worth evaluating: it combines net terms at ecommerce checkout, credit decisions and AR management. resolvepay.com

If you're already heavily ERP-centric, I'd instead make the ERP the system of record for customers, invoices, balances and credit, with ecommerce querying that information in real time. That avoids the dangerous situation where Shopify says a customer has $50k available while the ERP knows they already have $45k of uncollected invoices. ERP/ecommerce synchronization of customer, order, payment-term and credit information is particularly important for this workflow. www.shopify.com

Architecture I'd recommend

                 ┌──────────────────┐
                 │   B2B Storefront  │
                 └────────┬─────────┘
                          │
                    checkout request
                          │
                          ▼
                 ┌──────────────────┐
                 │ Credit / AR Layer│
                 │                  │
                 │ • Account        │
                 │ • Credit limit   │
                 │ • Utilization    │
                 │ • Terms          │
                 │ • Aging          │
                 │ • Dunning        │
                 └────────┬─────────┘
                          │
             ┌────────────┴────────────┐
             ▼                         ▼
      ┌──────────────┐          ┌──────────────┐
      │     ERP      │          │   Payments   │
      │ customers    │          │ ACH / card   │
      │ invoices     │          │ bank transfer│
      │ AR ledger    │          └──────────────┘
      └──────────────┘

The key design decision: don't let the ecommerce platform become a second accounting system. Let the commerce layer handle the buying experience, while the credit/AR layer and ERP maintain authoritative financial state.

If you tell me your ecommerce platform (Shopify, WooCommerce, Magento, custom, etc.), ERP/accounting system (NetSuite, Dynamics, QuickBooks, SAP, etc.), approximate number of trade accounts, and whether you need credit underwriting, I can narrow this to a specific stack and implementation architecture.

For a small handmade-goods shop on a tight budget, I’d narrow it to these:

• Square Online — probably the cheapest way to get a real store running. Its Free plan has no monthly subscription, and you pay processing fees when you make a sale. You get a website builder, product catalog, checkout, shipping, discounts, and inventory features. Square Square
• Wix — a good choice if the look and feel of your handmade brand matters as much as the shop. It has a drag-and-drop builder and built-in ecommerce, with U.S. ecommerce plans starting around $29/month on annual billing according to Wix's current pricing information. wix.com wix.com
• Shopify — strongest if you expect the shop to become a substantial part of your business, but it's more expensive: Basic is currently $29/month when paid yearly (or $39 month-to-month). It has particularly extensive ecommerce functionality. Shopify Shopify Help Center

My practical pick

Start with Square Online if keeping costs as close to $0/month as possible is your priority. You can build a proper storefront without committing to a monthly subscription. Square

Choose Wix instead if you're willing to spend ~$30/month and want a prettier, more customizable brand website alongside your store.

For handmade goods specifically, I'd also pay attention to product variants, good photo galleries, inventory tracking, shipping, discount codes, and abandoned-cart recovery—those can matter more than having dozens of advanced ecommerce features.

squareup.com · wix.com · shopify.com

If you tell me roughly how many products you sell (e.g. 10, 50, 200) and whether you also sell in person at markets, I can narrow it down between Square, Wix, and Shopify based on your likely monthly cost.

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.

For a pop-up retail concept where your website and in-person checkout need to share the same inventory, products, orders, and customer data, I’d start with Shopify + Shopify POS.

My shortlist

Why I'd lean Shopify

shopify.com is built specifically around connecting ecommerce and physical retail. Its POS works at pop-ups and markets, and sales made through POS automatically sync orders and inventory with the online store. Shopify Shopify Help Center

For a pop-up concept, that's particularly useful because you can:

• Have one product catalog for the website and physical events.
• Sell using an iPhone/iPad and mobile card reader, including Tap to Pay on iPhone. Shopify
• Automatically reduce website inventory when something sells at a pop-up.
• Let customers buy online and pick up at an event/store, or potentially ship items to them.
• Maintain customer purchase history across online and offline purchases.
• Move from a temporary pop-up to a permanent store without changing platforms.
• Add more sophisticated POS functionality later through POS Pro if the concept grows. Shopify Help Center Shopify Help Center

Shopify currently lists its entry-level plan at $29/month when billed annually, with POS functionality included; POS Pro adds additional retail capabilities. Shopify

When I'd choose something else

Square makes sense if your business is primarily in-person and the website is secondary. It's particularly attractive if you want to get a simple pop-up checkout running quickly.

Lightspeed is worth considering if you're building a more operationally complex retail business—multiple locations, sophisticated inventory, purchasing, reporting, etc. Shopify's current comparison describes Lightspeed as starting at $89/month and targeting more sophisticated cloud-based retail operations. Shopify

WooCommerce can be attractive if your website is already on WordPress or you need extensive custom development, but I wouldn't choose it from scratch solely for a pop-up concept. You'll generally be assembling the ecommerce and POS pieces rather than getting the unified system Shopify provides natively. Shopify

What I'd build for your concept

I'd probably set it up as:

Shopify website → Shopify inventory/catalog → Shopify POS → mobile card reader → pop-up

That gives you a single source of truth rather than having a website inventory system and a separate POS that need to be reconciled.

If you tell me (1) what you're selling, (2) roughly how many SKUs, (3) how many pop-ups per month, (4) whether you already have a website, and (5) your approximate monthly sales, I can narrow this down to the specific software + hardware stack I'd use and the likely monthly cost.

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.

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 multinational with localized catalogs + regional inventory + distributed fulfillment, the “best” platform depends heavily on where your complexity sits:

• ERP/supply chain complexity → SAP Commerce Cloud
• Deep customization and multi-store flexibility → Adobe Commerce
• CRM-led commerce and omnichannel customer experience → Salesforce Commerce Cloud
• API-first global commerce architecture → commercetools / composable stack

A practical enterprise shortlist:

CIOPages Elastic PathFor your specific scenario, I would evaluate platforms against these capabilities:

1. Inventory segmentation

You likely need:

• Warehouse-level ATP (available-to-promise)
• Regional inventory pools (Americas / EMEA / APAC)
• Localized availability rules
• Inventory reservations during checkout
• Backorder and substitution logic

Adobe Commerce explicitly supports multiple inventory sources, stocks, and mapping websites to regional inventory pools. Experience League

2. Order orchestration

Look for:

• Split shipments
• Ship-from-nearest-node
• Ship-from-store
• Cost-aware routing
• Carrier/service-level optimization
• Returns routing

Many global enterprises use a dedicated OMS (order management system) alongside commerce rather than expecting the commerce platform alone to solve fulfillment optimization.

3. Catalog localization

Important features:

• Country-specific assortments
• Regional pricing
• Currency/tax rules
• Language variants
• Regulatory differences
• Market-specific product visibility

Adobe Commerce supports multi-store and regional catalog models, while SAP Commerce Cloud is designed for complex catalogs and global B2B/B2C deployments. Adobe for Business SAP

My typical enterprise decision path

• You run SAP ERP and have complex supply chains: start with SAP Commerce Cloud.
• You have many brands/countries and need catalog agility: evaluate Adobe Commerce.
• You want a future-proof composable architecture and have strong engineering: evaluate commercetools.
• You are Salesforce-centric: Salesforce Commerce Cloud may fit, especially with Salesforce OMS/Service tooling.

A few details would change the recommendation substantially:

1. Are you primarily B2B, B2C, or B2B2C?
2. What ERP/WMS do you run (SAP, Oracle, Dynamics, custom)?
3. Roughly how many warehouses and countries?
4. Do you already have an OMS, or does the commerce platform need to own routing decisions?

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 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 you mean an enterprise marketplace operator with many third-party sellers, complex onboarding, and very large/messy catalogs, the shortlist I’d put in front of a CTO is:

My CTO-level read

Mirakl is the most directly aligned if the problem you're solving is "we operate a marketplace and need to onboard hundreds/thousands of sellers and normalize their catalogs without building the machinery ourselves." Its Marketplace Platform explicitly combines seller onboarding, catalog management and marketplace operations; its Catalog Platform accepts API, FTP, Excel, XML and CSV feeds and performs validation/enrichment. Mirakl Mirakl

That's particularly relevant if your catalog problem looks like:

• Sellers provide different schemas and data quality.
• You need automated category/attribute mapping.
• You need seller-specific onboarding workflows and governance.
• You have millions of SKUs rather than a relatively controlled first-party catalog.
• You want marketplace functionality without making your engineering team the permanent marketplace-operations team.

Mirakl reports $14.6B GMV in 2025 and 118 orders/second at peak, although those are vendor-reported figures rather than an independent benchmark. Mirakl

VTEX is compelling if you also want the broader commerce stack. Its marketplace offering includes seller registration/KYC, catalog upload, SKU matching, category mapping, enrichment, order orchestration, split payments and commissions. VTEX says its marketplace architecture supports thousands of concurrent sellers and millions of SKUs. VTEX

The important architectural distinction is that VTEX gives you more of the commerce platform out of the box, whereas Mirakl is more specifically optimized around marketplace/dropship operations.

commercetools is a different decision. It's attractive when your organization deliberately wants a composable/headless architecture and is comfortable assembling marketplace capabilities. Mirakl itself integrates with commercetools specifically to provide the marketplace layer. Commercetools

What I'd evaluate in a technical RFP

Don't make "number of sellers" the primary scalability test. I'd benchmark:

1. Seller onboarding: API/CSV/EDI feeds, KYC, approval workflows, seller self-service.
2. Catalog ingestion: 10M+ SKU loads, incremental updates, malformed feeds, duplicate detection.
3. Normalization: taxonomy mapping, attribute mapping, variant handling and product deduplication.
4. Operational isolation: whether one bad seller/feed can degrade the marketplace.
5. Inventory/price latency: real-time versus batch synchronization.
6. Order orchestration: split orders, seller routing, partial fulfillment and returns.
7. Payments: commissions, seller payouts, reconciliation and multi-currency.
8. API/event model: webhooks, idempotency, replayability and rate limits.
9. Governance: seller-level SLAs, catalog quality rules and automated suspension.
10. Exit strategy: how portable your seller, product, offer and order data is.

One useful real-world data point: Macy's says it used Mirakl to onboard 450+ sellers, while its Catalog Manager ingests seller catalogs through EDI, CSV and API and performs automated category/attribute mapping. Mirakl

Bottom line: if your defining requirement is vendor onboarding + heterogeneous multi-seller catalogs at enterprise scale, I'd investigate Mirakl first, then VTEX if you want a broader all-in-one commerce platform. If you're already committed to a composable architecture, commercetools + Mirakl deserves serious consideration.

If seasonal spikes are your biggest concern, I’d focus less on the marketing claims of “scalability” and more on whether the platform handles automatic capacity changes, traffic bursts, caching, checkout/order processing, and third-party integrations without your team having to manually intervene.

Shortlist

Shopify Salesforce Experience League Experience League commercetools### For your particular requirement

Shopify Plus is worth serious consideration if your priority is “we don't want our infrastructure team worrying about the holiday spike.” Shopify reports that during BFCM 2025 its infrastructure reached 489 million requests/minute, with 90 PB of data processed, and says it performs extensive load and chaos testing ahead of BFCM. Shopify

Salesforce B2C Commerce is another strong architectural fit for seasonal retailers. Salesforce specifically documents flash-sale traffic management and peak-season preparation. Its current guidance emphasizes CDN caching, load balancing, app-server capacity, third-party dependencies, bot traffic, and load testing—not simply adding more servers. Developer Salesforce

Adobe Commerce as a Cloud Service has particularly explicit autoscaling: Adobe says its managed cloud infrastructure automatically adjusts resources for peaks in traffic, orders, and catalog operations. Experience League

If you're considering Adobe Commerce on Cloud rather than the SaaS offering, there is an important distinction: its current scaled architecture can horizontally add web nodes and vertically resize capacity, but Adobe recommends load testing and advance planning for expected major events. Experience League Experience League

commercetools is attractive when you have a sophisticated engineering organization and want composable/headless architecture. Its API-first design is well suited to independently scaling different commerce capabilities, but you generally take on more architectural responsibility than with a fully managed SaaS platform. commercetools commercetools

The important caveat

No ecommerce platform can honestly guarantee “zero failures” merely because its infrastructure scales. At extreme seasonal peaks, failures often come from things around the commerce engine:

• payment gateways
• inventory/ERP systems
• search
• tax services
• shipping APIs
• poorly behaved apps/plugins
• custom checkout code
• database-heavy promotions
• bots during flash sales
• CDN/cache configuration

Salesforce's current peak-season guidance, for example, explicitly treats third-party systems and load testing as part of the customer's responsibility. Salesforce

So for a business with huge but highly seasonal loads, I'd evaluate vendors using a test like:

Can we run at 5–10× normal traffic, sustain that load for several hours, execute real checkouts/orders, and then return to normal capacity without manual infrastructure intervention?

Ask each vendor for production peak metrics from the last holiday season, not just theoretical requests/second, and run a load test involving your actual payment, inventory, search, tax, and fulfillment integrations. Salesforce itself recommends asking vendors for recent uptime results and API capacity and testing third-party systems as part of peak preparation. Salesforce Salesforce

If you tell me your normal traffic, peak traffic/orders per minute, catalog size, B2C vs B2B, and whether you need headless/custom checkout, I can narrow this to the most appropriate 2–3 architectures for your workload.

The important caveat

No ecommerce platform can honestly guarantee “zero failures” merely because its infrastructure scales. At extreme seasonal peaks, failures often come from things around the commerce engine:

For a retail chain where store pickup and complex omnichannel fulfillment are core requirements, I’d shortlist Salesforce Commerce Cloud + Salesforce Order Management and Shopify Plus.

Why Salesforce stands out for complexity: its current Commerce/POS stack supports line-level fulfillment methods including BOPIS, buy-online-fulfill-in-store, reserve-online-fulfill-in-store, and omnichannel exchanges. Its Order Management also provides location-level inventory and can treat stores as distribution/fulfillment centers. Salesforce Salesforce

Shopify Plus is a credible alternative if you want a more unified, comparatively simpler platform. It supports BOPIS, curbside pickup, ship-from-store, inventory transfers between locations, and—currently for Plus/Enterprise—mixing shipped and pickup items in the same checkout. Shopify Shopify Help Center Shopify Changelog

So, for a chain with hundreds of stores, sophisticated fulfillment rules, multiple inventory pools, and lots of exceptions, I'd evaluate Salesforce Commerce + OMS particularly closely. For a retailer prioritizing speed to market and a simpler commerce/POS stack, Shopify Plus is worth serious consideration.

If you tell me roughly number of stores, warehouses, annual online revenue, and whether you already use Salesforce/Shopify/SAP, I can give you a neutral architecture comparison including Adobe Commerce, commercetools, and VTEX.