All answers

For an enterprise catalog with thousands of SKUs and genuinely complex pricing, I’d shortlist platforms based less on SKU count and more on how complicated your customer-specific pricing, catalogs, contracts, ERP integration, and buying workflows are.

One I'd investigate first: Adobe Commerce

Based solely on what you've described, Adobe Commerce is worth putting near the top of your evaluation list. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, customer groups, negotiated quotes, and multiple websites/price scopes. Experience League Experience League Experience League

For example, Adobe's shared catalogs let you expose different product selections and pricing to different companies, while its pricing system supports fixed or percentage custom prices and quantity-based tiers. Experience League

That said, if your pricing is more like "every customer has a contract, price depends on customer + SKU + quantity + region + currency + effective dates + negotiated agreement, with ERP as the ultimate source of truth," I'd put SAP Commerce, commercetools, and Elastic Path into the evaluation alongside Adobe rather than assuming a traditional commerce platform is sufficient. Current enterprise-platform comparisons similarly distinguish integrated suites from composable platforms and emphasize the integration/operating-model tradeoff. CIOPages Elastic Path

The questions I'd use to narrow it down

The most important thing is your pricing model. For example:

• How many SKUs? 10k, 100k, 1M+?
• How many customers/accounts?
• Is pricing customer-specific, contract-specific, or mostly volume-based?
• Do you have customer-specific catalogs where customers can only see certain SKUs?
• Does pricing depend on quantity, geography, currency, channel, contract, dates, or promotions?
• Do prices originate in SAP, Oracle, Dynamics, Salesforce, or another ERP/CPQ?
• Do buyers need quotes, approval workflows, requisitions, purchase orders, or punchout?
• Do you need multiple storefronts/brands/countries?
• Do you want a headless/composable architecture, or would you rather have more functionality built into the platform?

If you give me those details—especially SKU count, number of customers, pricing rules, ERP/CRM, and whether this is B2B or B2C—I can make a much more useful side-by-side architecture comparison of Adobe Commerce vs. SAP Commerce vs. commercetools vs. Salesforce vs. Elastic Path.

Based solely on what you've described, Adobe Commerce is worth putting near the top of your evaluation list. Its B2B functionality supports company-specific shared catalogs, custom prices, tier pricing, customer groups, negotiated quotes, and multiple websites/price scopes. Experience League Experience League Experience League

For example, Adobe's shared catalogs let you expose different product selections and pricing to different companies, while its pricing system supports fixed or percentage custom prices and quantity-based tiers. Experience League

That said, if your pricing is more like "every customer has a contract, price depends on customer + SKU + quantity + region + currency + effective dates + negotiated agreement, with ERP as the ultimate source of truth," I'd put SAP Commerce, commercetools, and Elastic Path into the evaluation alongside Adobe rather than assuming a traditional commerce platform is sufficient. Current enterprise-platform comparisons similarly distinguish integrated suites from composable platforms and emphasize the integration/operating-model tradeoff.

The questions I'd use to narrow it down

The most important thing is your pricing model. For example:

If mobile developer experience is your main criterion, Shopify is a strong fit for a mobile storefront.

• Native iOS/Android: Shopify provides official mobile tooling, including typed Kotlin support for Android and iOS tooling. Shopify Shopify
• React Native: Shopify explicitly supports React Native, with the Storefront API plus Checkout Kit. Shopify
• Commerce primitives: The Storefront API covers products, collections, search, carts, pricing, and checkout flows. Shopify
• Checkout: Checkout Kit lets you hand off the cart's checkoutUrl to a native checkout experience rather than building payment yourself. Shopify
• Developer tooling: GraphiQL, official clients, SDKs, tutorials, and sample apps make the initial integration relatively straightforward. Shopify

How I'd shortlist them

For a new mobile app where you want to get from product catalog → cart → payment quickly, I'd start with Shopify. Its documented mobile flow is unusually direct: Storefront API → cart → Checkout Kit. Shopify Shopify

If your priority is instead maximum backend/control and minimal dependence on a commerce platform's built-in UX, I'd investigate Saleor or commercetools. Saleor, for example, exposes a GraphQL-first architecture with extensive customization and extension points. Saleor Documentation

shopify.dev

If you tell me iOS/Android/React Native + whether you're selling physical goods, subscriptions, or digital products, I can compare the APIs specifically for your architecture.

For a dropshipping business where supplier integrations are the priority, Shopify generally offers the strongest ecosystem. Its App Store has a large selection of supplier/sourcing integrations, including DSers, Syncee, Spocket, AutoDS, CJdropshipping, and Shopify Collective. Shopify Help Center Shopify App Store

• Shopify: broadest managed ecosystem; easiest multi-supplier setup.
• WooCommerce: highly flexible, but integrations are more plugin-dependent. WooCommerce
• BigCommerce: worth considering for more complex B2B/catalog requirements.

If you're specifically planning dozens or hundreds of different suppliers, I'd lean toward Shopify + a supplier-sync/automation layer such as Syncee, AutoDS, or custom API/feed integrations, rather than relying on one dropshipping app. eaglelytics.com

For three retail stores + one ecommerce site + simple location-level inventory, I’d shortlist these:

My pick: Shopify

For your relatively simple requirement, Shopify is probably the cleanest fit. It lets you create the three stores as separate locations, maintain quantities independently at each location, and connect those locations to Shopify POS. Online and in-store sales can update the same inventory system. Shopify Help Center Shopify Shopify Help Center

For example:

• Store A: 12 units
• Store B: 7 units
• Store C: 4 units
• Online availability: determined according to your inventory/fulfillment configuration
• A sale in Store B reduces Store B's inventory.
• You can transfer stock between locations and configure online order routing. Shopify Help Center Shopify

Square is worth considering if your three physical stores are the center of the business. Its multi-store functionality specifically supports location-level stock, transfers, centralized catalog management, and location reporting. Square

BigCommerce makes more sense if the ecommerce side is more sophisticated or you anticipate custom integrations. It supports multi-location inventory, but some location-aware storefront/fulfillment capabilities are more API/integration-oriented. BigCommerce BigCommerce

Bottom line: if you want “three stores, one website, one inventory system, minimal complexity,” I'd start by evaluating Shopify + Shopify POS.

If you tell me roughly how many SKUs you have, whether you already use Square/Shopify/POS hardware, and whether customers need in-store pickup, I can narrow it down further.

For a small craft-kit subscription business, Shopify is probably the best starting point for flexible subscription management. Its free Shopify Subscriptions app supports weekly/monthly/yearly billing, skipping, pausing, canceling, discounts, and customer self-service. Shopify Help Center Shopify Help Center

• Shopify: easiest all-around; add more advanced subscription apps later. Shopify
• WooCommerce: more customizable if you're comfortable with WordPress; supports custom schedules, plan switching, gifting, and 25+ payment gateways. WooCommerce
• BigCommerce: worth considering if you anticipate a more complex catalog or larger operation. BigCommerce

My practical pick: Shopify if you want to launch quickly without much technical overhead; WooCommerce if maximum customization matters more than simplicity.

For a photographer selling both high-resolution digital files and physical prints, I’d look first at Pixieset and Pic-Time.

• Pixieset — best all-around/simple setup. Supports original-resolution downloads, automatic digital delivery, and automatic lab fulfillment for prints. Pixieset Help Center Pixieset Help Center
• Pic-Time — strongest if print sales are a major revenue stream. It supports high-res downloads plus print fulfillment and built-in automated campaigns designed to drive print sales. Pic-Time Help Center Pic-Time
• SmugMug — good for a broader storefront/portfolio. Offers original-resolution downloads and a large print/product catalog. SmugMug Support SmugMug

My practical pick: Pixieset for simplicity; Pic-Time if you specifically want to maximize automated print sales.

For a neighbourhood gift shop, these handle spreadsheet-to-store imports well:

• Shopify — easiest overall for small retailers. Its built-in CSV importer lets you upload products, prices, SKUs, variants, inventory, and images from spreadsheets. Shopify Help Center Shopify Help Center
• WooCommerce — best if you already use WordPress. It has a built-in CSV importer with column mapping and bulk updates; useful for larger or more customized catalogs. WooCommerce
• BigCommerce — strong catalog tools and CSV-based migration/import workflows, better suited if you expect a bigger inventory. BigCommerce

For a gift shop with lots of one-off items, seasonal products, and simple spreadsheet updates, I’d usually start with Shopify. If you want maximum control and don’t mind more setup, choose WooCommerce. Shopify Help Center WooCommerce

Look for these import features:

• SKU matching for updates
• image URL imports
• category/tag mapping
• variant support (size, color, bundles)
• “dry run” or preview before changing products

A sample spreadsheet with columns like SKU, Name, Description, Price, Stock, Category, Image URL is usually enough to test any platform.

For a small local bakery with just a handful of products, Square Online is probably the simplest low-cost choice.

My shortlist

• 🥇 Square Online — best fit for a small bakery

• $0/month on the Free plan.
• You can create an ordering page, accept online payments, and offer pickup.
• Square's current Free plan charges 3.3% + $0.30 for online payments. Square Square
• Particularly convenient if you also take payments in person with Square.
• You can start without buying a website/domain or expensive software. Square
• squareup.com
• Toast — worth considering if you're becoming more of a restaurant operation

• Toast Online Ordering provides a branded ordering page and says it doesn't charge third-party commission on orders. Toast Support Center Toast POS
• However, for only a few bakery items, its broader restaurant/POS ecosystem may be more than you need.
• Shopify — good if you're planning to grow into a larger online store

• Much more powerful for a traditional ecommerce business, but Shopify's current Basic plan is $29/month when billed annually (or $39 month-to-month), so I'd generally avoid it for a tiny bakery menu. Shopify

What I'd do in your situation

I'd start with Square Free and make the ordering page extremely simple:

Cookies | Bread | Cakes | Pickup date/time → Pay

You don't need a complicated website. Put the Square ordering link in your Instagram/Facebook bio, Google Business Profile, and on a QR code at the bakery.

If you tell me roughly how many items you sell, whether you do pickup/delivery, and whether you already use Square for in-person payments, I can tell you exactly how I'd set it up and what it would cost per $100 of orders.

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

1. woocommerce.com — best if you want flexibility

WooCommerce's core plugin is free, with no monthly platform fee or revenue share. You mainly pay your payment processor and only add paid extensions if you need them. WooCommerce

Good for: physical products, shipping, inventory, coupons, lots of products.

Downside: it can become complicated/expensive if you start adding lots of extensions.

2. surecart.com — probably my pick for a simple store

SureCart is particularly attractive if you don't need a giant traditional shopping-cart system. Its Launch plan is $0/month, but charges a 2.9% transaction fee in addition to your payment processor's fees. SureCart SureCart

It handles things like products, checkout, orders, coupons, shipping, taxes, subscriptions, and payments without requiring you to assemble lots of separate WordPress plugins. SureCart

Good for: a small catalog, digital products, services, subscriptions, or a straightforward checkout.

3. ecwid.com — good if you want the store managed separately

Ecwid can be embedded into an existing WordPress site. Its plans support adding a store to an existing website, and it doesn't charge its own transaction fee. Ecwid | E-Commerce Shopping Cart

The tradeoff is that you're paying for an external ecommerce service rather than keeping everything inside WordPress.

What I'd choose

For a small WordPress site with perhaps 5–50 products, I'd start with SureCart if you want the least hassle, or WooCommerce if you want maximum control and expect the store to grow.

If you tell me what you're selling (physical products, digital downloads, services, memberships, etc.), roughly how many products, and whether you need shipping, I can narrow it down to the cheapest practical setup—including the payment fees.

For a shoestring subscription box launch, I’d usually avoid building a custom system and pick a platform that already handles:

• recurring card charges
• failed payment retries (“dunning”)
• customer self-service (skip, pause, cancel)
• subscription changes
• basic inventory/order workflows

Here are the strongest low-cost options:

Subbly Shopify## My recommendation for a lean launch

1. Best “just launch the box” choice: Subbly

For a true subscription box (monthly coffee, snacks, beauty items, pet products, etc.), Subbly is purpose-built. Its lower-tier plans are aimed at getting subscription checkout running without custom development, and it supports payment integrations such as Stripe. Subbly

A typical lean stack:

• Subbly for subscriptions + customer management
• Stripe for payments
• Simple landing page (or Subbly site)
• ShipStation/Shippo later when volume grows

2. Best if you expect a bigger ecommerce brand: Shopify

If the box is only one part of the business (you’ll also sell one-off products, bundles, gifts, etc.), Shopify is often the better foundation. Shopify offers subscription tools, including its own Shopify Subscriptions app, plus third-party subscription apps. Shopify

3. Cheapest if you have technical help: Stripe Billing

If you already have a website and someone can build checkout/customer flows, Stripe can be very cost-efficient. It gives you the billing engine, but you’ll need to create more of the subscription experience yourself. Shopify

What I would avoid at the beginning

• Enterprise subscription tools like Chargebee/Recurly unless you already have significant revenue.
• Building your own recurring billing logic.
• Paying for advanced analytics/CRM features before you have subscribers.

For a first 100–500 subscribers, I’d lean Subbly if the product is a pure subscription box, or Shopify + subscriptions if you want a full ecommerce brand. Subbly Shopify

If you tell me your box type (physical goods vs digital, expected monthly price, and whether you already have a website), I can narrow it down to the cheapest stack.

For a tight-budget, headless-first shop, I’d put Medusa at the top of the evaluation list.

Shortlist

Medusa's current cloud plans start at $29/month and explicitly have 0% GMV platform fees, with a $99/month Launch tier adding things like autoscaling, backups, custom storefront domains and Redis-backed infrastructure. Medusa Medusa Docs

Vendure Core is free/open source and can be self-hosted, although its current commercial Platform offering is sold on an annual subscription with pricing quoted per project. Vendure Vendure

Saleor is also open source, but its managed Cloud pricing is dramatically higher: the current Select tier starts at $1,599/month, making it harder to justify for a genuinely budget-constrained launch. Saleor Commerce

Shopify supports custom/headless storefronts and currently lists headless storefront support across its plans, but you're still buying into its SaaS ecosystem rather than running the commerce engine yourself. Shopify

What I'd evaluate first

Medusa + Next.js is probably the stack I'd prototype first if your priorities are:

• low monthly infrastructure cost
• genuinely headless architecture
• TypeScript throughout
• ability to self-host later
• no platform GMV tax
• freedom to customize the storefront and commerce logic

The important caveat is that "free/self-hosted" doesn't mean zero cost: you'll still pay for hosting, database, email, storage, monitoring, and your engineering time. For a small shop, though, that can be quite inexpensive.

I'd run a small proof-of-concept with Medusa and Vendure before committing, using the same requirements: catalog, variants, cart, checkout/payment, discounts, shipping, tax, order management, and your intended CMS/front end. That will tell you much more about total cost than feature checklists. Vendure Medusa

If you tell me your expected monthly orders, catalog size, tech stack (e.g. Next.js), and whether you need B2B/multi-vendor, I can narrow this to a concrete low-cost architecture and estimated monthly bill.

Shopify supports custom/headless storefronts and currently lists headless storefront support across its plans, but you're still buying into its SaaS ecosystem rather than running the commerce engine yourself.

What I'd evaluate first

Medusa + Next.js is probably the stack I'd prototype first if your priorities are:

For an indie game, itch.io is probably the most budget-friendly fit if you want both direct downloads and license/key distribution.

Why itch.io fits

• No upfront cost: creating and hosting a game page is free. You choose the percentage of revenue you want to share with itch.io, from 0–100%. itch.io itch.io
• Direct game downloads: you upload your Windows/macOS/Linux builds, and buyers get access through their purchase/download page. itch.io itch.io
• Unique download keys: you can generate individual or bulk keys for press, testers, backers, giveaways, etc., and keys can be labeled, tracked, and revoked. itch.io
• External keys: if you also sell on Steam, you can stock Steam keys and make them available to qualifying itch.io purchasers. itch.io itch.io
• No forced DRM: itch.io distributes the files as you uploaded them. itch.io
• Payments/tax handling: itch.io supports Stripe and PayPal, and its "Collected by itch.io" payout model can handle VAT collection for you. itch.io

How I'd structure it

Your website → itch.io checkout → itch.io ownership/download page → game download

Then use itch.io's keys for:

• Steam keys
• review/press copies
• Kickstarter/backer rewards
• beta testers
• giveaways
• influencer copies

One important distinction: itch.io's "license" is primarily ownership/access to your downloadable files, rather than a sophisticated DRM/license-server system. If by license distribution you mean unique activation codes that your own game validates against an API, you'd want a different service or a custom licensing backend.

For a small indie studio trying to keep fixed costs near zero, though, itch.io is a particularly good starting point. itch.io itch.io

If you tell me whether you need Steam keys, DRM-style activation, or simply unique purchase/download licenses, I can narrow it down to 2–3 storefronts and compare their fees.

For a small handmade goods shop on a tight budget, I’d pick WooCommerce self-hosted on WordPress. It gives you the most control per dollar: your data, code, hosting, themes, and checkout flow are yours, with a huge ecosystem of extensions. Toolradar

Good options:

• Best overall: WooCommerce — easiest to self-host cheaply, great for handmade catalogs, blogs, SEO, coupons, shipping plugins, and custom themes. Open Source Groups
• Simpler dedicated store: OpenCart — lighter and less tied to a CMS, but a smaller ecosystem. Velocity
• More “pure ecommerce” feel: PrestaShop — stronger built-in store features, but usually more setup and hosting overhead. Open Source Groups
• Developer-focused: Medusa — maximum customization, but you’ll build more yourself; not ideal if you want to spend time making products rather than coding. Open Business Network

For your situation, a practical stack:

• $5–15/month VPS or shared hosting
• WordPress + WooCommerce
• Free theme initially
• Stripe/PayPal for payments
• Regular backups + updates

Avoid Magento unless you expect a large catalog and have technical help; it’s powerful but expensive to maintain. Velocity

For a static/headless storefront where the backend is primarily an API, I’d narrow it to Medusa, Saleor, and Vendure. All three are designed for decoupled storefronts. Vendure

My take

1. Medusa — probably my first choice for your setup

Medusa is particularly well suited if your static site is built with JavaScript/TypeScript.

Its V2 Store API is REST, has an OpenAPI specification, and is explicitly intended for storefronts and mobile apps. It also supports publishable API keys designed for client-side storefronts. Medusa Documentation Medusa Documentation

The architecture is modular—you get products, carts, customers, inventory, orders, payments, promotions, fulfillment, etc., while being able to extend the modules and API. Medusa Documentation

Good architecture:

Static site → Medusa Store API → PostgreSQL

That makes it quite natural for something like Astro, Next.js static export, Gatsby, or a plain JS site.

docs.medusajs.com

2. Saleor — excellent if you want GraphQL

Saleor is very API-centric and GraphQL-native. Its API covers catalog, checkout, channels, promotions, payments, shipping, etc., and it has extensive webhook/app mechanisms for integrations. Saleor Documentation Saleor Commerce

I'd lean toward Saleor if you expect your storefront to make sophisticated, highly tailored GraphQL queries or you expect multi-region/multi-currency, multiple sales channels, marketplaces, or complex commerce integrations.

saleor.io

3. Vendure — great TypeScript alternative

Vendure is built with TypeScript/NestJS and exposes GraphQL Shop and Admin APIs. Its core is explicitly positioned as a framework for developers building custom ecommerce applications. Vendure Vendure

It's attractive if your backend team is already heavily invested in Node.js + TypeScript + GraphQL, especially when you'll be extending the commerce model substantially.

vendure.io

What I'd choose

For the specific phrase "plug into our static site", I'd start with Medusa unless you have a strong reason to prefer GraphQL.

The deciding factors I'd use are:

• Static/Jamstack + REST + TypeScript: Medusa
• GraphQL-first + sophisticated/headless architecture: Saleor
• TypeScript + GraphQL + substantial backend customization: Vendure

One particularly important distinction: don't choose based solely on whether the product has an API. Look closely at checkout, authentication, payments, webhooks, inventory, search, tax/shipping, and how easily you can customize those without modifying/forking the core.

If you tell me your stack (Astro / Next.js / plain HTML+JS / Hugo / etc.) and whether you need Stripe, subscriptions, digital products, or physical shipping, I can narrow this down to an architecture and API choice.

Its V2 Store API is REST, has an OpenAPI specification, and is explicitly intended for storefronts and mobile apps. It also supports publishable API keys designed for client-side storefronts. Medusa Documentation Medusa Documentation

The architecture is modular—you get products, carts, customers, inventory, orders, payments, promotions, fulfillment, etc., while being able to extend the modules and API. Medusa Documentation

Good architecture:

Static site → Medusa Store API → PostgreSQL

That makes it quite natural for something like Astro, Next.js static export, Gatsby, or a plain JS site.

docs.medusajs.com

2. Saleor — excellent if you want GraphQL

Saleor is very API-centric and GraphQL-native. Its API covers catalog, checkout, channels, promotions, payments, shipping, etc., and it has extensive webhook/app mechanisms for integrations. Saleor Documentation Saleor Commerce

I'd lean toward Saleor if you expect your storefront to make sophisticated, highly tailored GraphQL queries or you expect multi-region/multi-currency, multiple sales channels, marketplaces, or complex commerce integrations.

saleor.io

3. Vendure — great TypeScript alternative

Vendure is built with TypeScript/NestJS and exposes GraphQL Shop and Admin APIs. Its core is explicitly positioned as a framework for developers building custom ecommerce applications. Vendure docs.vendure.io

It's attractive if your backend team is already heavily invested in Node.js + TypeScript + GraphQL, especially when you'll be extending the commerce model substantially.

For a subscription box business with recurring physical-product billing, I’d narrow it to WooCommerce, Medusa, or Saleor—but they fit very different architectures.

My practical recommendation: WooCommerce

If your primary goal is running a subscription-box business rather than building ecommerce infrastructure, I'd use WordPress + WooCommerce + WooCommerce Subscriptions.

WooCommerce Subscriptions supports weekly/monthly/annual recurring payments, automatic renewals, failed-payment rebilling, customer self-service, trials, sign-up fees, and subscription changes. It also explicitly supports subscription-box use cases. WooCommerce WooCommerce

The important caveat: WooCommerce itself is open source, but WooCommerce Subscriptions is a paid extension. The current listed price is $279/year. WooCommerce

When I'd choose Medusa instead

Choose Medusa if you're comfortable writing code and want something like:

Next.js storefront → Medusa → PostgreSQL → Stripe → fulfillment/shipping system

Medusa is open source and designed as a customizable commerce framework. Its official subscription recipe covers recurring orders, renewal, expiration, cancellation, and Stripe integration—but subscriptions are not a native turnkey feature; you'd implement the subscription layer yourself. GitHub Medusa Docs

That makes Medusa particularly interesting if your box has unusual rules, such as:

• Customers choose items every month.
• Box contents change based on inventory.
• Skip/pause/upgrade logic is complex.
• Different subscription tiers have different fulfillment schedules.
• You need custom customer/account experiences.
• You eventually want mobile apps or multiple storefronts.

Saleor

Saleor is another strong self-hosted option. It's API-first and GraphQL-native, with an extensible architecture and integrations for payments, shipping, taxes, etc. Saleor Documentation Saleor Commerce

But for a subscription-box startup, I'd expect more custom subscription work than with WooCommerce.

What I'd build

If you're a small team and want to validate the business:

WordPress + WooCommerce + WooCommerce Subscriptions + Stripe

If you're a developer-led company and the subscription/fulfillment logic itself is a major differentiator:

Next.js + Medusa + Stripe + PostgreSQL

I'd avoid choosing a platform solely because it is "more modern." For subscription boxes, the difficult parts tend to be renewal handling, failed payments, skips/pauses, inventory allocation, shipping synchronization, taxes, and fulfillment, rather than the basic storefront.

If you tell me your expected number of subscribers, whether customers choose box contents, and whether you want Stripe, I can sketch the self-hosted architecture and database/subscription model I'd use.

For an enterprise team prioritizing scalability and containerized deployment, I’d shortlist Saleor, Medusa, and Vendure, with the choice driven mainly by your engineering stack and enterprise requirements. Vendure Pawel Owerczuk

• Saleor — Python/Django, GraphQL-first, PostgreSQL; strong fit for multi-channel and enterprise commerce. Vendure
• Medusa — TypeScript/Node.js, modular architecture, MIT core; attractive for teams wanting highly customizable containerized services. Pawel Owerczuk
• Vendure — TypeScript/NestJS, GraphQL, plugin architecture; particularly relevant for complex B2B/omnichannel systems. Vendure

If your team is TypeScript-heavy, Medusa or Vendure are natural candidates; if Python/GraphQL is already strategic, Saleor is worth prioritizing.

If inventory and warehouse management are the primary requirements, I’d narrow the open-source ecommerce stack to Odoo, ERPNext, and Medusa. My recommendation depends heavily on whether you want the commerce platform itself to be the operational backbone or whether you want a modern headless storefront.

My shortlist

1. Odoo — my pick for serious warehouse operations

Odoo is the one I'd investigate first if you have multiple warehouses, bins/locations, barcode workflows, replenishment, returns, purchasing, or complex fulfillment rules.

Its Inventory application is explicitly designed as both inventory management and a WMS. It supports warehouses and hierarchical locations, routes, replenishment, serial/lot tracking, cycle counting, reservations, and advanced picking strategies. Odoo Odoo Odoo

The particularly useful part is its route/push/pull-rule system. You can model flows such as:

Receiving → QC → Putaway → Picking → Packing → Shipping

and create different rules for different products or warehouses. Odoo Odoo

It also supports multiple warehouses and transfers between them. Odoo

Caveat: Odoo is open source, but its overall product is dual-licensed; some capabilities are in the commercial edition. So I'd distinguish "open-source Odoo" from "the complete Odoo feature set" when evaluating it. ERP Research

2. ERPNext — best if "fully open source" is important

ERPNext is compelling if you want the ERP and inventory system to be completely open-source rather than primarily an ecommerce framework.

Its warehouse model can go quite deep:

Warehouse → Room → Row → Shelf → Bin

and it maintains stock balances by item and warehouse. Frappe Documentation

It also integrates nicely with a separate storefront because products, orders, invoices, shipments, returns, warehouses, and stock movements are exposed through its REST API. Frappe Documentation

So a stack like:

Next.js storefront → ERPNext → warehouse/inventory/accounting

is quite reasonable.

I'd lean toward ERPNext when inventory + purchasing + accounting + manufacturing/business operations matter more than having the ecommerce engine itself be extremely sophisticated.

3. Medusa — best modern ecommerce architecture

Medusa is interesting if you want a modern headless ecommerce platform rather than an ERP.

Its inventory module supports inventory items, multiple locations/warehouses, reservations, and inventory across locations. Medusa Docs

It also supports more sophisticated ecommerce scenarios such as:

• multi-warehouse inventory
• reservations
• splitting orders across locations
• returns/exchanges
• omnichannel inventory
• custom inventory logic
• connecting to an external WMS

MedusaThat last point is important: Medusa can act as the commerce layer while a dedicated WMS/ERP handles the really complicated warehouse operations.

What I'd choose

If you told me simply:

"I want an open-source ecommerce system, and warehouse/inventory is one of the most important parts."

I'd investigate Odoo first.

If you told me:

"I want everything genuinely open source, including ERP, accounting, purchasing and inventory."

I'd investigate ERPNext.

If you told me:

"I want a modern React/Next.js headless storefront and excellent ecommerce developer experience, but inventory needs to be considerably better than Shopify's basic inventory."

I'd investigate Medusa.

The biggest architectural question is actually how sophisticated your warehouse is. If you need things like barcode scanning, bin-level inventory, receiving/putaway, wave or batch picking, lot/serial tracking, multiple fulfillment centers, cycle counts, replenishment, 3PL integration, and warehouse transfers, I'd favor an ERP/WMS-centric architecture rather than choosing a pure ecommerce platform and trying to bolt WMS functionality onto it. Odoo in particular has dedicated support for wave, cluster, and batch picking. Odoo

If you tell me your number of SKUs, number of warehouses, order volume/day, B2B vs B2C, and whether you need barcode scanners/manufacturing/3PL, I can narrow this down to a specific stack and architecture.

So a stack like:

Next.js storefront → ERPNext → warehouse/inventory/accounting

is quite reasonable.

I'd lean toward ERPNext when inventory + purchasing + accounting + manufacturing/business operations matter more than having the ecommerce engine itself be extremely sophisticated.

3. Medusa — best modern ecommerce architecture

Medusa is interesting if you want a modern headless ecommerce platform rather than an ERP.

Its inventory module supports inventory items, multiple locations/warehouses, reservations, and inventory across locations.

It also supports more sophisticated ecommerce scenarios such as:

For a subscription newsletter with bonus downloadable files, I’d narrow it to Memberful, Ghost, and Podia. The right choice depends mainly on whether the newsletter or the downloadable library is the center of the business.

My practical recommendation: Memberful

Memberful is particularly well suited if you already have a website or want your own branded membership area. It supports recurring plans, gated content, newsletters, and digital downloads, with payments through your own Stripe account. Memberful Memberful

The important advantage for your use case is that you can make the newsletter subscription itself the entitlement: someone pays monthly/yearly → they're a member → they can access the appropriate newsletter content and bonus files. Memberful specifically supports including downloads with subscription plans. Memberful

memberful.com

When I'd choose Podia instead

Podia is compelling if your downloadable content is becoming a substantial product library. It combines memberships, email marketing, digital downloads, website/landing pages, and other digital products. Its download system supports customer accounts, re-downloads, bundles, and granting bonus products alongside purchases. Podia Podia

podia.com

When Ghost makes more sense

Ghost is attractive if the newsletter/publication is the product and downloadable bonuses are secondary. It's built around publishing and paid memberships, whereas Memberful and Podia are more oriented toward membership/product commerce.

For your specific requirement of securely gating downloadable files, I'd lean away from making Ghost the sole storefront: its native membership gating is excellent for content, but file-download protection can require additional implementation. Ghost Forum

ghost.org

Bottom line:

• Newsletter + membership + occasional bonuses → Memberful
• Newsletter + substantial downloadable product library → Podia
• Primarily a paid publication/newsletter → Ghost

If you tell me roughly your subscriber count, monthly price, and whether you already have a website/newsletter platform, I can compare the actual fees and setup complexity for your situation.

Memberful is particularly well suited if you already have a website or want your own branded membership area. It supports recurring plans, gated content, newsletters, and digital downloads, with payments through your own Stripe account. Memberful Memberful

The important advantage for your use case is that you can make the newsletter subscription itself the entitlement: someone pays monthly/yearly → they're a member → they can access the appropriate newsletter content and bonus files. Memberful specifically supports including downloads with subscription plans. Memberful

memberful.com

When I'd choose Podia instead

Podia is compelling if your downloadable content is becoming a substantial product library. It combines memberships, email marketing, digital downloads, website/landing pages, and other digital products. Its download system supports customer accounts, re-downloads, bundles, and granting bonus products alongside purchases. Podia Podia

podia.com

When Ghost makes more sense

Ghost is attractive if the newsletter/publication is the product and downloadable bonuses are secondary. It's built around publishing and paid memberships, whereas Memberful and Podia are more oriented toward membership/product commerce.

For your specific requirement of securely gating downloadable files, I'd lean away from making Ghost the sole storefront: its native membership gating is excellent for content, but file-download protection can require additional implementation.

Yes. For a marketplace where multiple creators sell digital goods and receive automatic payouts, a particularly relevant option is Sharetribe + Stripe Connect.

Strong options

Sharetribe is specifically designed for marketplaces and has a digital-product marketplace setup with digital downloads, seller onboarding/KYC, automatic payouts, and marketplace commissions. Sharetribe Sharetribe

With Stripe Connect underneath, you can have:

• Customer pays $20 for a creator's digital product
• Your marketplace automatically takes, say, a 20% commission
• Creator receives the remaining $16
• Stripe handles seller onboarding, payout information, and payouts
• You can delay the creator payout until the transaction is considered complete Sharetribe Sharetribe

sharetribe.com

If you're building your own platform

I'd look closely at Stripe Connect directly. It is designed specifically for multi-sided marketplaces: it can onboard sellers, split payments between multiple parties, take platform fees, and automate payouts. Stripe Stripe

stripe.com

So the basic architecture would be:

Your marketplace → Stripe Connect → Creator's connected Stripe account → Creator's bank account

If you tell me whether you're looking for no-code, Shopify/WooCommerce, or a custom-built marketplace, I can narrow this down to the most suitable 3–5 platforms and compare their fees and payout mechanics.

If you're selling large datasets to enterprise customers, I’d separate the problem into two needs: secure delivery/access control and customer-facing analytics/auditability. The strongest options I’d shortlist are:

My take

For a turnkey enterprise product: Egnyte is probably the first one I'd evaluate. Its audit system covers file activity, logins, permissions and user provisioning, and it can report on downloads through share links. Egnyte Help Desk Egnyte Help Desk Its Document Room product is specifically designed around controlled external access, with granular permissions and reporting on user visits, file views/downloads and permissions. Egnyte Help Desk Egnyte

egnyte.com

If the experience is more "customer buys a dataset and gets a secure delivery room," Digify is interesting. Its API explicitly supports granular access, download restrictions, expiry and watermarking, while its event model tracks opens, views, downloads and revocations and exposes webhooks. Digify

digify.com

If you're building the actual marketplace/application yourself, I'd seriously consider object storage + your own entitlement layer rather than a traditional file-sharing product. Cloudflare R2 supports expiring presigned URLs, so your application can decide exactly which customer can download which object and for how long. Cloudflare Docs Cloudflare Docs R2's Data Access Logs can capture per-request object operations, including GetObject, HeadObject, uploads and deletes. Cloudflare Docs

cloudflare.com

One architectural distinction I'd make

If you're selling 10–500 GB+ datasets repeatedly, I'd lean toward:

Your application → customer entitlement/identity → signed download URL → object storage/CDN → centralized audit/analytics

rather than putting the datasets directly into Dropbox-style folders.

That lets you record events such as:

• Customer/account
• Individual user
• Dataset purchased/licensed
• Version of dataset
• File/object accessed
• Download started/completed
• Bytes transferred
• IP/device
• Timestamp
• Link/token used
• Expiration/revocation
• Number of downloads
• Last access
• Contract/license expiration

It also lets you distinguish "the customer was authorized to download Dataset X" from "Dataset X was actually downloaded 17 times." That's an important distinction for enterprise licensing and usage reporting.

If you tell me your approximate dataset size, number of customers, whether customers download files or query data via API, and whether you need billing/checkout, I can narrow this to a 3–4 option architecture comparison (e.g. Egnyte vs DocSend vs Digify vs S3/R2 + custom portal) and include estimated implementation complexity.

If the experience is more "customer buys a dataset and gets a secure delivery room," Digify is interesting. Its API explicitly supports granular access, download restrictions, expiry and watermarking, while its event model tracks opens, views, downloads and revocations and exposes webhooks. Digify

digify.com

If you're building the actual marketplace/application yourself, I'd seriously consider object storage + your own entitlement layer rather than a traditional file-sharing product. Cloudflare R2 supports expiring presigned URLs, so your application can decide exactly which customer can download which object and for how long. developers.cloudflare.com developers.cloudflare.com R2's Data Access Logs can capture per-request object operations, including GetObject, HeadObject, uploads and deletes. developers.cloudflare.com

cloudflare.com

One architectural distinction I'd make

If you're selling 10–500 GB+ datasets repeatedly, I'd lean toward:

Your application → customer entitlement/identity → signed download URL → object storage/CDN → centralized audit/analytics

For your use case, Payhip is probably the closest fit.

Payhip

Payhip explicitly supports pay-what-you-want pricing for digital products. You can enter:

• 0+ → customer can download for free or pay any amount
• 5+ → $5 minimum, but they can pay more

It also supports uploading PDFs, audio, video and other digital files, with automatic delivery after purchase. Payhip Help Center Payhip Help Center

That makes a setup like “Zine #12 — $0+” or “Album — $5+” straightforward. Payhip's free plan currently has a 5% transaction fee; paid plans reduce or eliminate that platform fee. Payhip

Gumroad

gumroad.com also has a proper PWYW feature. You can set a minimum amount and a suggested amount, which is particularly useful if you want to say “$5 suggested, pay what you can.” Gumroad

The tradeoff is cost: Gumroad currently charges 10% + $0.50 on direct/profile sales, before applicable payment-processing costs. Gumroad Gumroad

itch.io

If the zines/music are part of an independent-art/DIY publishing ecosystem, itch.io has unusually good PWYW support. Its pricing system lets you set a minimum—or make something free and explicitly solicit a donation—and users can pay above the minimum. itch.io

My practical shortlist: start with Payhip if you want a conventional storefront for both zines and music; consider Gumroad if you prioritize simplicity and its ecosystem; consider itch.io if the audience is particularly indie/DIY/creative.

One important distinction: if by “optional donations” you mean a separate donation amount in addition to purchasing the zine/music, rather than simply allowing customers to pay more than the listed price, I'd look specifically at the checkout mechanics before choosing. Payhip's PWYW model is fundamentally attached to the product purchase, while Ko-fi is more explicitly built around separate tips/support. Payhip Help Center ko-fi.com

If the goal is specifically “checkout should be a commerce service, not a frontend feature”, I’d shortlist commercetools, Saleor, Medusa, and Shopify—but they represent very different levels of control.

My architectural take

If checkout is strategically important and you expect unusual flows, I'd start with Saleor or commercetools.

commercetools is particularly interesting if you want checkout to become an independently evolving service. Its Checkout product has a dedicated Checkout API, and the SDKs support it directly; the platform is designed around composable commerce rather than treating headless as primarily a storefront concern. commercetools Documentation commercetools Documentation

Saleor is compelling if you want maximum control without building the entire commerce engine yourself. Its APIs are GraphQL-native, and Saleor explicitly supports decoupling the frontend while extending commerce behavior through APIs/webhooks. Saleor Commerce Saleor Commerce

Medusa makes sense if your team is strongly TypeScript/Node-oriented and wants to own the checkout domain. Its modular architecture is well suited to replacing pieces of the standard checkout rather than fighting a SaaS platform's prescribed flow. PowerGate Software OSSAlt

Shopify is the operationally simpler choice. Its current Storefront API supports custom storefronts, carts and checkout, and Shopify explicitly supports bringing your own frontend/framework. However, there's an important architectural distinction: you're consuming Shopify's checkout infrastructure rather than owning an independently deployable checkout domain. Shopify Shopify

One important Shopify detail: don't architect against the old Checkout API. Shopify deprecated the relevant Checkout APIs and directs headless implementations toward the Storefront Cart API/Checkout Kit. Shopify

The architecture I'd aim for

Rather than:

Frontend → Commerce platform → Checkout

I'd design:

Frontend(s)
→ Checkout API / Checkout BFF
→ Commerce platform
→ Payment provider
→ Tax / fraud / promotions / fulfillment

That gives you a stable checkout contract such as:

POST /checkout
POST /checkout/{id}/items
POST /checkout/{id}/shipping-address
POST /checkout/{id}/shipping-method
POST /checkout/{id}/payment
POST /checkout/{id}/complete

Your web app, native app, kiosk, marketplace UI, or future AI shopping interface can all consume the same checkout capability.

The key question is therefore how much of that checkout domain you want the commerce vendor to own:

• Vendor owns most of it: Shopify
• Vendor provides composable checkout primitives: commercetools
• You own the domain logic, platform supplies commerce primitives: Saleor / Medusa
• You want checkout to be a genuinely independent business capability: commercetools or Saleor are the first two I'd investigate.

If you tell me your stack (e.g. Next.js/React), B2C vs B2B, payment provider, countries, and whether checkout has bespoke logic, I can narrow this to a concrete architecture and platform choice.

If checkout is strategically important and you expect unusual flows, I'd start with Saleor or commercetools.

commercetools is particularly interesting if you want checkout to become an independently evolving service. Its Checkout product has a dedicated Checkout API, and the SDKs support it directly; the platform is designed around composable commerce rather than treating headless as primarily a storefront concern. commercetools Documentation commercetools Documentation

Saleor is compelling if you want maximum control without building the entire commerce engine yourself. Its APIs are GraphQL-native, and Saleor explicitly supports decoupling the frontend while extending commerce behavior through APIs/webhooks. Saleor Commerce Saleor Commerce

Medusa makes sense if your team is strongly TypeScript/Node-oriented and wants to own the checkout domain. Its modular architecture is well suited to replacing pieces of the standard checkout rather than fighting a SaaS platform's prescribed flow. PowerGate Software OSSAlt

Shopify is the operationally simpler choice. Its current Storefront API supports custom storefronts, carts and checkout, and Shopify explicitly supports bringing your own frontend/framework. However, there's an important architectural distinction: you're consuming Shopify's checkout infrastructure rather than owning an independently deployable checkout domain. Shopify Shopify

One important Shopify detail: don't architect against the old Checkout API. Shopify deprecated the relevant Checkout APIs and directs headless implementations toward the Storefront Cart API/Checkout Kit. Shopify

The architecture I'd aim for

Rather than:

Frontend → Commerce platform → Checkout

I'd design:

Frontend(s)
→ Checkout API / Checkout BFF
→ Commerce platform
→ Payment provider
→ Tax / fraud / promotions / fulfillment

That gives you a stable checkout contract such as:

POST /checkout
POST /checkout/{id}/items
POST /checkout/{id}/shipping-address
POST /checkout/{id}/shipping-method
POST /checkout/{id}/payment
POST /checkout/{id}/complete

Your web app, native app, kiosk, marketplace UI, or future AI shopping interface can all consume the same checkout capability.

The key question is therefore how much of that checkout domain you want the commerce vendor to own:

• Vendor owns most of it: Shopify
• Vendor provides composable checkout primitives: commercetools
• You own the domain logic, platform supplies commerce primitives: Saleor / Medusa
• You want checkout to be a genuinely independent business capability: commercetools or Saleor are the first two I'd investigate.

If you tell me your stack (e.g. Next.js/React), B2C vs B2B, payment provider, countries, and whether checkout has bespoke logic, I can narrow this to a concrete architecture and platform choice.

If your frontend is a custom iOS/Android app, I’d narrow the field to Shopify, Medusa, Saleor, and commercetools. The right choice depends mostly on how much commerce infrastructure you want to build yourself.

Quick comparison

My practical recommendation: Shopify

For a custom mobile app, Shopify is probably the strongest default choice unless you have unusual commerce requirements.

Shopify's Storefront API is explicitly designed for apps, including native iOS, Android, and React Native applications. It handles products, collections, search, carts, pricing, etc., while Shopify's Checkout Kit can present checkout inside the mobile app. Shopify Shopify

The architecture can look like:

┌─────────────────────────────┐
│     Custom Mobile App       │
│                             │
│  iOS / Android / React Native│
└──────────────┬──────────────┘
               │
        Storefront API
               │
               ▼
┌─────────────────────────────┐
│          Shopify            │
│                             │
│ Products                    │
│ Customers                   │
│ Cart                        │
│ Pricing                     │
│ Inventory                   │
│ Orders                      │
│ Checkout / Payments         │
└─────────────────────────────┘

Shopify also provides official mobile libraries and documentation for iOS, Android, and React Native. Shopify Shopify

shopify.dev

When I'd choose Medusa instead

I'd seriously consider Medusa if your app has commerce logic that doesn't fit naturally into Shopify—for example, highly customized checkout, marketplace/multi-vendor behavior, or unusual product/order workflows.

Medusa's Store API is explicitly intended for storefronts including commerce mobile apps, and its APIs are REST-based. Medusa Docs

The tradeoff is that you take on more responsibility for your commerce infrastructure.

When Saleor makes sense

Saleor is particularly interesting if your engineering team prefers GraphQL and a highly API-driven architecture. Saleor describes itself as GraphQL-native and technology-agnostic, with headless storefront and admin APIs. Saleor Commerce Saleor Commerce

I'd investigate it if your app is more of a custom commerce product than a conventional ecommerce storefront.

The key distinction

I'd use this rule:

• "I want to build a great mobile shopping experience without reinventing ecommerce." → Shopify
• "I want to own and heavily customize the commerce engine." → Medusa
• "I want a GraphQL-native, composable commerce backend." → Saleor
• "We're a large enterprise with complex composable commerce requirements." → commercetools

One particularly important point: don't choose based merely on whether a platform has an API. For a mobile app, evaluate the APIs for authentication, customer accounts, cart persistence, checkout, payments, inventory, webhooks, order management, discounts, and offline/poor-connectivity behavior. Checkout is often the part that determines whether an otherwise-good headless platform is actually pleasant to integrate.

If you tell me (1) iOS/Android/React Native, (2) B2C or B2B, (3) approximate catalog size, and (4) whether you need subscriptions/marketplace/multi-vendor, I can give you a much more specific architecture and platform comparison.

Shopify's Storefront API is explicitly designed for apps, including native iOS, Android, and React Native applications. It handles products, collections, search, carts, pricing, etc., while Shopify's Checkout Kit can present checkout inside the mobile app. Shopify Shopify

The architecture can look like:

┌─────────────────────────────┐
│     Custom Mobile App       │
│                             │
│  iOS / Android / React Native│
└──────────────┬──────────────┘
               │
        Storefront API
               │
               ▼
┌─────────────────────────────┐
│          Shopify            │
│                             │
│ Products                    │
│ Customers                   │
│ Cart                        │
│ Pricing                     │
│ Inventory                   │
│ Orders                      │
│ Checkout / Payments         │
└─────────────────────────────┘

Shopify also provides official mobile libraries and documentation for iOS, Android, and React Native. Shopify Shopify

shopify.dev

When I'd choose Medusa instead

I'd seriously consider Medusa if your app has commerce logic that doesn't fit naturally into Shopify—for example, highly customized checkout, marketplace/multi-vendor behavior, or unusual product/order workflows.

Medusa's Store API is explicitly intended for storefronts including commerce mobile apps, and its APIs are REST-based.

The tradeoff is that you take on more responsibility for your commerce infrastructure.

When Saleor makes sense

For a small agency building dropshipping stores for local clients, I’d avoid trying to run everything through a single “merchant account manager.” You’ll usually want a client operations stack: one layer for store ownership/access, one for reporting, one for fulfillment/apps, and one for internal project management.

A practical stack:

1. Store ownership & access: Shopify Partner account (if you’re mainly on Shopify)

Use shopify.com as your foundation.

Why:

• Create development stores for builds
• Request collaborator access instead of sharing passwords
• Keep clients as store owners
• Transfer ownership when the store launches
• Manage multiple client relationships under your agency

For most Shopify-focused agencies, this should be the backbone.

2. Multi-store dashboard / portfolio management

If you have 5–50+ client stores, add a portfolio dashboard:

• storelyst.com — built specifically around agency-style multi-store management, reporting, and switching between client stores. StoreLyst
• zovik.ai — focuses on multi-store analytics, reporting, and Shopify/WooCommerce portfolio views. Zovik

These are more useful once your team is constantly jumping between merchant dashboards.

3. Client reporting (so you look like an agency, not a freelancer)

For monthly client updates, consider:

• triplewhale.com — popular for ecommerce attribution and reporting
• klaviyo.com — useful if you manage email/SMS marketing
• lookerstudio.google.com — cheaper option for custom dashboards

A simple agency report should show:

• Revenue
• Ad spend
• ROAS
• Conversion rate
• AOV
• Best-selling products
• Refund rate
• Customer acquisition cost

4. Internal agency operations

Don’t manage clients inside Shopify notes. Use:

• clickup.com or asana.com for client workflows
• 1password.com for credentials (never shared spreadsheets)
• slack.com for client/team communication

Create a template per client:

• Store setup checklist
• Theme customization
• Product imports
• Payment setup
• Shipping rules
• Apps installed
• Launch checklist
• Monthly optimization tasks

5. Dropshipping-specific tools

This depends on your suppliers:

General product sourcing/fulfillment

• dsers.com (AliExpress workflows)
• autods.com (automation-heavy)
• spocket.co (supplier marketplace)

Profit tracking

• beprofit.co
• trueprofit.io

What I’d use for a small agency (5–30 clients)

Lean setup:

• Shopify Partner account
• ClickUp
• 1Password
• Looker Studio
• Klaviyo
• BeProfit/TrueProfit

More agency-style setup:

• Shopify Partner account
• StoreLyst or Zovik for portfolio management
• Triple Whale for reporting
• ClickUp
• 1Password
• Klaviyo

One important operational choice: have clients own their Shopify stores and billing whenever possible. Your agency should have collaborator access and manage the build/optimization, rather than becoming the merchant of record for every client. It reduces payment, liability, and account-transfer headaches as you scale.

If you tell me roughly how many stores you manage now (e.g., 5, 20, 100+) and whether you use Shopify, WooCommerce, or both, I can suggest a tighter stack and budget.

For a subscription-focused dropshipping store, I’d build around Shopify, then add dedicated apps for subscriptions and supplier fulfillment rather than trying to make one platform do everything.

Recommended setup

Shopify itself currently lists Shopify Subscriptions, Appstle, Recharge, Bold, Ordergroove, PayWhirl, and Chargebee among its subscription options. Shopify Subscriptions is particularly straightforward because it integrates directly with Shopify Payments and Shopify's admin. Shopify

For supplier management, DSers supports AliExpress/1688/Alibaba and U.S. suppliers, with automated order processing, tracking synchronization, supplier mapping, and multi-supplier/agent management on its higher tier. Shopify App Store Shopify App Store

What I'd use at different stages

• Starting / testing: Shopify + Shopify Subscriptions + DSers
• Growing subscription business: Shopify + Appstle + DSers
• Large subscription-first brand: Shopify + Recharge/Skio + a dedicated fulfillment/supplier system

The important distinction is that your subscription platform and supplier platform don't necessarily need to be the same thing. Your subscription system creates the recurring customer order; the fulfillment integration then needs to reliably send each subsequent order to the correct supplier.

One thing I'd be careful about: AliExpress-style dropshipping can become awkward for subscriptions because supplier stock, shipping times, product availability, and fulfillment consistency can change. For a genuinely subscription-focused business, I'd eventually prioritize a supplier that can provide stable inventory, predictable fulfillment times, recurring-order automation/API access, and preferably private labeling or branded packaging.

If you tell me what type of product you're planning to sell and whether you're targeting the U.S., I can lay out a specific Shopify + subscription app + supplier stack, including approximate monthly costs and how the recurring-order flow would work.

If your priority is mobile performance + a low-friction checkout for a dropshipping store, I’d choose Shopify.

How I’d compare them

Why Shopify stands out: Shopify Checkout is explicitly mobile-first and responsive, supports address autocomplete and accelerated payment methods, and runs on Shopify's infrastructure. Shopify Shopify

The bigger advantage for a mobile-heavy store is Shop Pay. Returning shoppers can use saved payment/shipping information rather than repeatedly typing it on a phone. Shopify reports substantially higher conversion versus standard checkout, although those figures are Shopify's own reported/commissioned measurements rather than an independent apples-to-apples benchmark. Shopify Shopify Help Center

WooCommerce has improved considerably—recent releases report faster cart/checkout interactions and a 19% checkout speed improvement—but your actual performance depends much more on hosting, WordPress configuration, plugins, theme, and payment setup. WooCommerce WooCommerce

BigCommerce also provides responsive storefronts and mobile-optimized checkout out of the box. BigCommerce

For a dropshipping storefront specifically

I'd build it roughly like this:

Shopify → lightweight theme → minimal apps → Shop Pay + Apple Pay/Google Pay → aggressive image optimization → very few third-party scripts.

The important caveat is that Shopify doesn't automatically make a store fast. A bloated theme, dozens of apps, oversized product images, review widgets, tracking scripts, and popups can make the shopping experience slow even though checkout itself is highly optimized.

If you're deciding between Shopify, WooCommerce, and BigCommerce, I can also give you a 2026 mobile-first comparison covering page speed, checkout conversion, dropshipping integrations, fees, customization, and scaling costs.

If your goal is a dropshipping store where you own the code, build custom supplier integrations, automate fulfillment, and avoid SaaS limitations, you should look beyond typical Shopify alternatives. The best choices are usually headless commerce platforms or highly extensible open-source carts. Open Business Network Toolradar

Here are the strongest options:

Open Source Groups OpenSourceProjects.cc## 1. Medusa — probably the best fit for a custom dropshipping operation

Medusa is designed more like a commerce engine than a website builder. You build the storefront separately (often with Next.js/React) and use Medusa as the backend. OSSAlt

Good for:

• Custom supplier APIs
• Multiple suppliers per product
• Automated order routing
• Custom pricing rules
• AI product enrichment pipelines
• Custom inventory syncing
• Marketplace-style workflows
• Mobile apps

A possible architecture:

Customer Storefront
        |
     Next.js
        |
     Medusa API
        |
 ----------------------
 |          |          |
Supplier A Supplier B ERP/WMS
 |          |          |
Dropship APIs / Feeds

For example, you could build logic like:

Customer buys Product X → system checks supplier inventory → selects cheapest supplier → sends order → updates tracking → emails customer

without fighting a SaaS platform's limits.

Tradeoff: you need development skills because you are building more of the experience yourself. Toolradar

2. Saleor — best if you want a serious multi-channel platform

Saleor is another API-first platform. It uses GraphQL and is aimed at complex commerce setups. Eryx Innovations Lab

Strong points:

• Multi-channel selling
• Multiple warehouses
• Complex catalogs
• International commerce
• Strong API approach

Good if you eventually want:

• Website
• Mobile app
• Wholesale portal
• Marketplace
• B2B customers

Tradeoff: more enterprise-oriented and heavier operationally than Medusa.

3. WooCommerce — best if you want to move quickly

WooCommerce is still one of the easiest open-source routes because of its ecosystem. Open Source Groups

Advantages:

• Thousands of plugins
• Easy admin interface
• Many dropshipping extensions
• Lots of developers available
• Easy content marketing through WordPress

You can customize:

• Supplier feeds
• Order automation
• Pricing engines
• Product importers
• Custom checkout logic

The downside is architectural: WordPress plugins can become messy at scale. If you expect millions of products or highly automated workflows, a headless system is usually cleaner.

4. PrestaShop — good middle ground

PrestaShop is a traditional ecommerce platform with a mature catalog system. Toolradar

Good for:

• Large product catalogs
• European markets
• Standard dropshipping workflows
• Stores that want a built-in admin

Less ideal for:

• Highly custom application logic
• Building a unique commerce engine

5. Bagisto — underrated if you know Laravel

Bagisto is worth considering if your developers prefer PHP/Laravel. OSSAlt

Good for:

• Custom business logic
• Marketplace features
• Laravel-based integrations

My recommendation by scenario

You want a serious automated dropshipping platform:

Medusa + Next.js

Best architecture for:

• supplier integrations
• custom automation
• scaling beyond basic dropshipping

You want to launch quickly and customize later:

WooCommerce

Best if:

• you are validating products
• you want plugins
• you want less engineering upfront

You want enterprise/multi-channel:

Saleor

Best if:

• you expect complex operations
• you have developers

You are a Laravel shop:

Bagisto

For a dropshipping business specifically, I would avoid choosing based only on "store features." The important question is whether the platform lets you create a product ingestion pipeline + supplier routing engine + fulfillment automation layer. For that, a headless platform like Medusa is usually the strongest foundation. OpenSourceProjects.cc

A modern stack I would consider:

• Frontend: Next.js
• Commerce engine: Medusa
• Database: PostgreSQL
• Queue/jobs: Redis + workers
• Search: Meilisearch or Elasticsearch
• Automation: custom Node services
• Payments: Stripe
• Analytics: your own event pipeline

That gives you something closer to building your own Shopify rather than just running a dropshipping store.

If your main goal is optimizing a dropshipping catalog—deciding which products to keep, kill, promote, bundle, or replace—I’d look primarily at product-level analytics, funnel data, attribution, inventory signals, and ease of custom reporting.

My comparison

Shopify — strongest overall for dropshipping

Shopify is probably the strongest choice if analytics-driven catalog optimization is the priority.

Its built-in analytics gives you product, sales, customer, acquisition, inventory, and conversion reporting, with customizable dashboards and the ability to modify reports or create custom data explorations. Shopify also supports ShopifyQL for deeper querying. Shopify Help Center Shopify Help Center

Particularly useful for dropshipping:

• Identify high-traffic / low-conversion products
• Find products with strong add-to-cart but weak checkout conversion
• Compare revenue, units sold, AOV and margins
• Analyze acquisition channels and ROAS
• See which products are purchased together
• Monitor inventory/fulfillment performance
• Export data for more sophisticated analysis
• Add dedicated analytics apps as your store grows

Shopify's current analytics also provides near-real-time dashboards and automatically generated insights, which is useful when you're testing lots of products. Shopify Help Center

shopify.com

BigCommerce — particularly good for larger catalogs

BigCommerce has strong native ecommerce reporting. Its analytics specifically emphasizes product and customer trends, including top sellers, low-converting products, AOV, promotions, and products that are lagging. BigCommerce

That makes it attractive if your dropshipping operation has hundreds or thousands of SKUs and you want merchandising/product-performance reporting built into the platform.

WooCommerce — most flexible if you're technical

WooCommerce has substantial analytics capabilities, including product, category, revenue, orders, customers, inventory and attribution reporting, with filtering, segmentation, CSV exports and customizable dashboards. WooCommerce WooCommerce

The advantage is flexibility: you can combine WooCommerce with GA4, BigQuery, Looker Studio, and other analytics tools. The downside is that creating a polished analytics stack generally requires more configuration than Shopify.

The bigger point: platform analytics isn't enough

For serious dropshipping, I'd build the catalog around a product-performance database, regardless of platform.

For every SKU, I'd want to see something like:

Traffic → Product views → Add-to-cart → Checkout → Purchases → Revenue → Ad spend → Gross profit → Refunds → Contribution margin

Then calculate:

• Conversion rate
• Add-to-cart rate
• Cost per acquisition
• ROAS
• Gross profit/order
• Contribution margin
• Revenue per visitor
• Profit per visitor
• Refund rate
• Repeat purchase rate
• Supplier/fulfillment cost
• Product velocity

This lets you distinguish between a product that's merely selling a lot and one that's actually worth scaling.

For example, a $40 product doing $10,000/month with $8,500 in advertising and fulfillment costs may be much less attractive than a $25 product doing $6,000 with $3,000 in total variable costs.

What I'd choose

For a new or growing dropshipping business, my architecture would be:

Shopify → GA4 → advertising platforms → specialized ecommerce analytics → spreadsheet/BI layer

Shopify gives you the commerce data and operational reporting; GA4 adds deeper behavioral/funnel analysis; and a specialized analytics product becomes useful once you're spending enough on advertising to justify sophisticated attribution. Shopify itself notes that tools such as Triple Whale can aggregate marketing data from platforms like Meta, Klaviyo and Google. Shopify

So if you're choosing the ecommerce platform specifically for analytics/reporting, I'd start with Shopify. The important caveat is that the best catalog-optimization system is usually Shopify + an analytics/BI layer, rather than Shopify's native reports alone.

If you tell me your approximate number of SKUs, monthly revenue/ad spend, and whether you're using Meta/TikTok/Google Ads, I can map out the specific analytics stack and dashboards I'd use for a dropshipping catalog.

For a dropshipping business selling through social channels + marketplaces + your own store, the platform that usually works best as the central hub is Shopify, often paired with marketplace/supplier apps. Shopify is designed to be the “source of truth” for products, inventory, customers, and orders while connecting to multiple sales channels. Shopify Shopify Help Center

Strong options for a centralized dropshipping stack

Shopify Nembol## A practical dropshipping setup

A common architecture:

Shopify (central hub)
→ Your website
→ Facebook/Instagram Shop
→ TikTok Shop
→ Google Shopping
→ Amazon/eBay/Walmart (via connectors)
→ Supplier fulfillment apps
→ Customer support + analytics

Shopify supports social channels such as Facebook, Instagram, and TikTok, and marketplace connections can be managed through tools such as Shopify Marketplace Connect for channels like Amazon, Walmart, and eBay. Shopify Help Center Shopify Help Center

My platform shortlist by business stage

Starting out (1–100 orders/day)

Shopify + supplier app + marketplace connector

• Fastest launch
• Easy product testing
• Good for TikTok/Instagram-driven sales
• Simple order dashboard

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

Shopify + Sellbrite/Linnworks/Nembol-style multichannel management

• Better listing automation
• Better inventory rules
• Fewer overselling problems

Marketplace-first business

If most revenue comes from Amazon/eBay/Walmart rather than your own store:

• Use a dedicated multichannel inventory system (for example, Linnworks/Sellbrite-type tools) with Shopify as the storefront.

Features to prioritize for dropshipping

Look for:

• ✅ Two-way inventory sync
• ✅ Automatic order routing to suppliers
• ✅ Bulk listing creation
• ✅ SKU mapping
• ✅ Price rule automation
• ✅ Tracking-number sync
• ✅ Returns/customer-service visibility
• ✅ Channel-specific pricing

For most new-to-growing dropshippers, I would start with Shopify as the central system, then add marketplace management software only when the number of channels/orders makes manual management difficult. Shopify Help Center Shopify

If you share your intended channels (e.g., TikTok Shop + Amazon + Shopify, or Etsy + eBay + store) and expected order volume, I can narrow this to a specific stack.

For a custom storefront centered on recurring subscription plans and APIs, I’d put Shopify + Hydrogen/Storefront API at the top of the shortlist, with Saleor and Medusa as alternatives if you want more backend control.

My recommendation: Shopify headless

Shopify is particularly compelling if recurring subscriptions are a core business feature rather than something you want to build from scratch.

Its Storefront API is GraphQL-based and explicitly supports products, carts, checkout, and selling plans for subscriptions. You can use it with Hydrogen, Next.js, or essentially any frontend framework. Shopify Shopify

For subscriptions, Shopify has a useful underlying model:

• SellingPlanGroup — groups subscription options such as weekly/monthly plans.
• SellingPlan — defines billing, delivery, pricing, and recurring behavior.
• SellingPlanAllocation — connects a variant to a particular subscription plan and exposes the resulting pricing. Shopify Shopify Shopify
• The Storefront API can retrieve subscription products and create carts containing subscription line items. Shopify
• Hydrogen has an official subscription implementation pattern, including displaying plans, adding subscription products to carts, and building subscription-management UI. Shopify

A typical architecture would be:

                 ┌──────────────────────┐
                 │  Custom Storefront   │
                 │ Next.js / Hydrogen   │
                 └──────────┬───────────┘
                            │
                       GraphQL API
                            │
                 ┌──────────▼───────────┐
                 │       Shopify        │
                 │ Products / Cart      │
                 │ Customers / Orders    │
                 │ Selling Plans         │
                 └──────────┬───────────┘
                            │
                 ┌──────────▼───────────┐
                 │ Subscription App     │
                 │ Billing / Lifecycle  │
                 └──────────────────────┘

The important distinction is that Shopify's selling-plan infrastructure handles the commerce representation of subscriptions, while a subscription app/integration generally handles the subscription lifecycle. Shopify's own Hydrogen documentation explicitly requires installing a subscriptions app for this implementation. Shopify

When I'd choose Saleor instead

Saleor makes more sense if API ownership and architectural control are more important than minimizing operational work. Saleor is GraphQL-native and designed around headless/composable commerce, with storefront and admin APIs intended to be decoupled from the frontend. Saleor Commerce Saleor Commerce

I'd investigate Saleor particularly if you need:

• Your own subscription/billing domain model
• Heavy customization of checkout/order logic
• Multiple commerce channels
• An open-source foundation
• A GraphQL-first architecture
• Your own services sitting between the storefront and commerce engine

The tradeoff is that you should expect to design more of the subscription system yourself.

When I'd choose Medusa

Medusa is worth considering if your engineering team is strongly TypeScript/Node.js-oriented and wants to own the commerce backend. Its modular architecture is well suited to building custom commerce workflows, but recurring billing becomes more of an engineering concern than with Shopify's established subscription ecosystem. OSSAlt

What I'd build

For a typical subscription business, I'd use:

Frontend: Next.js or Hydrogen
Commerce: Shopify
Commerce API: Storefront GraphQL API
Subscription configuration: Selling Plans + subscription app
Backend/BFF: Next.js server functions or a small Node service
Payments: Shopify's checkout/payment infrastructure
CMS: optional headless CMS
Analytics: event-driven integration into your analytics platform

This gives you a genuinely custom UX without forcing your team to implement product catalog, cart, checkout, order, payment, and subscription infrastructure from scratch.

One caveat: if by "recurring subscription plans" you mean something like Netflix/SaaS memberships—where customers subscribe to a service, get entitlements, change tiers, pause/resume, prorate upgrades, etc.—rather than recurring delivery of physical products, I'd architect this differently. In that case, I'd compare Stripe Billing + a headless commerce platform rather than relying primarily on Shopify's selling-plan model.

For perishable weekly subscription boxes with scheduled delivery windows, I’d generally look first at Shopify + a dedicated subscription app + a delivery-slot/routing app, rather than trying to make a basic ecommerce platform handle the whole workflow natively.

Why Shopify is a strong fit

Shopify supports recurring subscriptions, including weekly billing, and customers can pause, skip, resume, or cancel subscriptions. It also supports local delivery and pickup. Shopify Help Center Shopify Help Center

For local delivery, Shopify lets you define delivery areas by radius or ZIP/postal codes, set different delivery zones/prices, and manage local-delivery orders. Shopify Help Center Shopify

The important caveat is that delivery windows are more specialized than Shopify's native delivery-date functionality. Shopify's automated delivery dates are explicitly not available for subscription orders, so I'd use a specialized delivery-slot solution rather than relying on Shopify's standard delivery-date feature. Shopify Help Center

Architecture I'd consider

For example, your checkout could work like:

Weekly Farm Box — $45/week
→ Choose delivery day: Thursday
→ Choose window: 2–4 PM
→ Enter address
→ Subscribe
→ Every Thursday, generate that week's box order
→ Group Thursday orders by delivery zone/window
→ Produce driver routes
→ Deliver

One thing I'd prioritize

If you're delivering fresh produce, prepared meals, meat, seafood, flowers, baked goods, etc., don't choose the platform primarily based on its subscription functionality. The harder problem is usually operational scheduling:

• cutoff time for the upcoming week's orders
• delivery-day selection
• 1–2 hour delivery windows
• geographic delivery zones
• maximum deliveries per window
• recurring customers retaining their preferred window
• skipping a week
• vacation holds
• address changes
• route optimization
• substitutions/out-of-stock items
• cutoff for changing an order
• failed delivery handling

Shopify handles the commerce/subscription side well, but you'll likely want a delivery-specific app/system for those operational rules.

If you tell me whether you're doing local delivery, nationwide shipping, or both—and roughly how many boxes per week—I can compare Shopify, WooCommerce, BigCommerce, and purpose-built subscription/food-box platforms specifically for your workflow.

Architecture I'd consider

For example, your checkout could work like:

Weekly Farm Box — $45/week
→ Choose delivery day: Thursday
→ Choose window: 2–4 PM
→ Enter address
→ Subscribe
→ Every Thursday, generate that week's box order
→ Group Thursday orders by delivery zone/window
→ Produce driver routes
→ Deliver

One thing I'd prioritize

If you're delivering fresh produce, prepared meals, meat, seafood, flowers, baked goods, etc., don't choose the platform primarily based on its subscription functionality. The harder problem is usually operational scheduling:

• cutoff time for the upcoming week's orders
• delivery-day selection
• 1–2 hour delivery windows
• geographic delivery zones
• maximum deliveries per window
• recurring customers retaining their preferred window
• skipping a week
• vacation holds
• address changes
• route optimization
• substitutions/out-of-stock items
• cutoff for changing an order
• failed delivery handling

Shopify handles the commerce/subscription side well, but you'll likely want a delivery-specific app/system for those operational rules.

If you tell me whether you're doing local delivery, nationwide shipping, or both—and roughly how many boxes per week—I can compare Shopify, WooCommerce, BigCommerce, and purpose-built subscription/food-box platforms specifically for your workflow.

If your core requirement is customers building a box themselves and then subscribing to that customized box, I’d narrow the field considerably.

Platforms worth considering

Shopify is particularly compelling because the underlying platform can be paired with specialized bundle apps. For example, Bundles.app supports mix-and-match bundles, build-your-own boxes, subscription boxes, inventory synchronization, and recurring pricing. Shopify App Store

There's also an interesting all-in-one option: Supr Bundle & Subscription App combines bundle building and subscriptions, including customer-built boxes, recurring subscriptions, prepaid plans, and replenishment schedules. Shopify App Store

Another Shopify option, MBC Mix and Match Bundles, specifically supports build-your-own boxes, mix-and-match bundles, quantity breaks, and subscription integration with Recharge. Shopify App Store

The architecture I'd look at

If your product is something like:

"Choose any 6 products → get 15% off → save this box → receive it every month → swap products before each shipment"

I'd strongly consider:

Shopify + a sophisticated bundle builder + a dedicated subscription platform

rather than trying to make the ecommerce platform itself handle every piece.

That gives you separate control over:

• Box construction: customer chooses 6 of 20 products
• Rules: e.g. exactly 6 items, or minimum/maximum quantities
• Pricing: fixed box price vs. percentage discount
• Subscription: monthly/quarterly/etc.
• Customer portal: skip, pause, swap, modify
• Inventory: component-level inventory rather than treating the box as one SKU
• Fulfillment: actual individual products transmitted to the warehouse/3PL

The last point is especially important. A platform can make a beautiful "Build Your Box" experience while creating a nightmare for fulfillment if the resulting order doesn't properly represent the individual components.

My practical shortlist

• Shopify — particularly attractive if you want a polished DTC storefront and a large ecosystem of bundle/subscription apps.
• WooCommerce — worth considering if highly customized business logic is more important than turnkey administration.
• BigCommerce — worth investigating if you're operating a larger catalog or have more complex B2B/enterprise requirements.
• Shopify + Recharge/Skio + bundle builder — I'd investigate this architecture specifically if subscriptions are the heart of the business, rather than simply an optional purchase method.

One Shopify app that is unusually close to your exact use case is Supr: it explicitly combines "build a box" + subscriptions, rather than requiring two completely separate systems. Shopify App Store

If you tell me what you're selling, how many products customers can choose from, the box rules (e.g. "pick 5 of 20"), subscription frequency, and approximate monthly orders, I can narrow this down to a specific stack and explain the checkout, inventory, subscription, and fulfillment architecture I'd use.

If your product is something like:

"Choose any 6 products → get 15% off → save this box → receive it every month → swap products before each shipment"

I'd strongly consider:

Shopify + a sophisticated bundle builder + a dedicated subscription platform

Yes. If by prepaid subscription plans you mean customers pay upfront for a fixed period (e.g., 3, 6, or 12 months) and can then renew with minimal friction, several subscription-billing platforms support this.

• Chargebee — Supports subscription plans, prepaid credit pools, renewals, and self-service customer portals. It also supports charging future renewals in advance, which fits a prepaid model particularly well. Chargebee Chargebee API Documentation
• Recurly — Supports prepaid subscriptions and gift subscriptions, configurable billing terms, automatic renewals, and a hosted subscriber portal. Recurly Recurly Docs
• Stripe — Supports recurring subscriptions, customer self-service, saved payment methods, automatic retries, and customizable subscription schedules. It's a strong option if you want to build a very simple "Renew now" experience into your own website/app. Stripe Stripe

If your goal is specifically "one-click renewal"

A typical setup would be:

Customer buys 12-month prepaid plan → payment method is securely saved → subscription approaches expiration → customer receives "Renew for 12 months" → one click confirms renewal → payment is processed automatically.

For that particular workflow, Stripe Billing is attractive if you want maximum control over the customer experience, while Chargebee/Recurly are more purpose-built subscription-management platforms.

If you tell me what you're selling (SaaS, memberships, physical products, services, etc.) and whether you need automatic renewal or a customer-initiated one-click renewal, I can narrow it down to the most suitable tools.

If your core requirement is one cart that can contain both subscription items and one-time purchases, I’d narrow the field considerably.

Shortlist

My main recommendation: Shopify

Shopify is particularly well suited to this requirement because subscriptions are built into the platform's selling-plan model rather than being a completely separate checkout system.

A customer can put, for example:

• 1 × monthly coffee subscription
• 2 × one-time mugs
• 1 × one-time gift box

into the same cart and checkout. Shopify explicitly supports customers buying one-time purchases and subscriptions together. Shopify Shopify Help Center

It also handles subscription and one-time line items separately behind the scenes, while presenting them through the same checkout experience. Shopify Help Center

For a straightforward implementation, Shopify Subscriptions is the first thing I'd investigate. It's Shopify's own subscription app and supports weekly, monthly, and yearly recurring billing, subscription discounts, and customer self-service for pausing/skipping/canceling. Shopify Help Center

help.shopify.com

If the cart UX is the differentiator

I'd specifically look at Shopify's selling-plan/cart architecture rather than choosing a subscription service solely on its subscription-management features.

Shopify's Storefront API lets a custom storefront retrieve selling plans and create a cart containing subscription line items, which makes it viable for a highly customized/headless shopping experience too. Shopify

One important caveat: mixed fulfillment/shipping rules can get complicated. Shopify can calculate subscription and one-time shipping separately, but there are limitations around mixing delivery methods in a single subscription checkout. Shopify

When I'd choose something else

BigCommerce is worth considering if your catalog, pricing, B2B, or multi-store requirements are more complex. Its subscription capability is designed around integrations with recurring-billing providers rather than the same native selling-plan model Shopify uses. BigCommerce

WooCommerce makes sense if you're already heavily invested in WordPress and want maximum control over the checkout. The tradeoff is that you're assembling more of the system yourself.

Dedicated Shopify subscription apps such as Recharge, Skio, Loop, Appstle, etc. become interesting when subscription operations—dunning, retention, customer portals, analytics, migration, bundles, complex subscription rules—matter more than having the simplest stack. A current 2026 comparison covers these options. OneCart

Bottom line: if you mean “I want a normal ecommerce cart where customers can freely mix recurring and one-time products, without being sent through a separate subscription checkout”, Shopify is the platform I'd investigate first. Its native selling-plan architecture directly supports that model. Shopify

If you tell me whether you're selling physical products, digital products, or both, and whether this is new build vs. an existing store, I can narrow this to 2–3 specific stacks and compare their cart UX, fees, subscription management, and implementation effort.

Yes. If you mean one product where the customer can choose “ship weekly,” “ship monthly,” or “ship quarterly” at checkout, there are several options.

Shopify + Skio

Skio is particularly suited to this model. Its selling plans support multiple intervals for the same product, including different subscription intervals and different discounts for each interval. Its own documentation gives monthly and quarterly as an example. Skio Skio

So you could have:

• Weekly — $X / shipment
• Monthly — $Y / shipment
• Quarterly — $Z / shipment

all attached to the same Shopify product.

Shopify + Recharge

Recharge also supports multiple subscription frequencies for one product. Recharge describes product subscription plans as allowing different shipping frequencies, with frequencies configurable in days, weeks, and months. Recharge Support Recharge Support

This is another strong fit if shipping cadence is the core requirement.

Shopify's native Subscriptions app

Shopify's first-party Shopify Subscriptions app allows multiple subscription options on a product. It explicitly supports weekly, monthly, and yearly intervals and lets you add additional frequency options. Shopify Help Center Shopify Help Center

But there's an important limitation: the native UI documents weekly/monthly/yearly rather than an explicit quarterly (every 3 months) option. If quarterly is a hard requirement, I'd look at Skio or Recharge rather than relying on the native app.

One subtle distinction

If by "cadence" you mean shipping frequency independently from billing frequency, Shopify's underlying selling-plan architecture is capable of that. For example, Shopify supports separate billing and delivery policies, so you can theoretically have something like billed annually but shipped quarterly. shopify.dev shopify.dev

For your exact requirement, I'd shortlist Shopify + Skio and Shopify + Recharge. If you tell me whether you're selling physical products, consumables, or subscription boxes, I can compare those two on pricing, quarterly support, shipping-rate handling, customer self-service, and migration complexity.

Yes. A few tools fit that stack, depending on how much you want subscription billing and retention orchestration to live in one place.

Strong options

• Chargebee + HubSpot — probably the most straightforward if HubSpot is your CRM. Chargebee syncs subscription/customer data—including subscription status, plans, invoices, dues and MRR—into HubSpot, where you can segment customers and trigger marketing workflows. Chargebee HubSpot Marketplace

chargebee.com

• Recurly + Recurly Engage — more focused on subscription businesses and behavioral retention. Recurly Engage can use subscriber behavior to trigger personalized engagement, including retention, renewal and upsell campaigns, and connects with platforms such as Salesforce, Braze, Iterable and ActiveCampaign. Recurly Docs Recurly Docs
• Chargebee + HubSpot + Zapier — useful if you want more customized workflows. For example, a cancellation in Chargebee can automatically create a HubSpot engagement, allowing you to route the customer into a specific save/cancellation campaign. Zapier also supports triggers such as new subscription, cancellation and successful payment. Zapier Zapier

What a retention setup could look like

For example:

Subscription event → CRM profile → customer segment → personalized campaign

• Payment failed → identify high-value customer → send payment-recovery sequence
• Cancellation scheduled → ask cancellation reason → send appropriate save offer
• Usage declining → trigger engagement campaign
• Renewal approaching → personalized renewal messaging
• Long-term customer → upgrade/cross-sell campaign
• Recently downgraded → targeted win-back sequence

If you tell me which CRM and email platform you already use (e.g. HubSpot, Salesforce, Klaviyo, ActiveCampaign, Braze), I can narrow this to the tools that integrate with your existing stack and show you the exact architecture.

Yes. What you’re describing is generally a B2B/wholesale commerce platform, rather than a standard ecommerce catalog.

A few current options that specifically cover those requirements:

One particularly close match: BigCommerce B2B Edition

BigCommerce's B2B Edition has a fairly direct model for this:

• Company accounts represent your business customers.
• Customer groups can control which products/catalog and pricing a company sees. BigCommerce BigCommerce
• Account hierarchies support parent/child companies—for example, a corporate HQ with regional branches or individual locations. BigCommerce supports up to five hierarchy levels and 500 companies in a hierarchy. BigCommerce
• Buyer roles and permissions let you distinguish admins, senior buyers, junior buyers, etc. BigCommerce
• It also supports B2B workflows such as quotes, purchase orders, approval workflows, and net terms. BigCommerce

The caveat is MOQ: if minimum quantities need to vary by customer/account + product, I'd verify the exact rule model you'd need rather than assuming BigCommerce's native B2B features cover every MOQ scenario.

If MOQ is a core requirement

WizCommerce is worth looking at. It explicitly describes account-specific catalogs, contract pricing, case packs and order minimums, with those rules applied when the buyer signs in. It also supports parent/child customer hierarchies and multiple buyers/roles. Wiz Commerce Wiz Commerce

Virto Commerce is another option if you need a more sophisticated/custom B2B model. Its customer-specific commerce functionality is designed around account-, contract-, and role-specific catalogs, pricing and workflows. Virto Commerce

So if your data model looks something like:

Acme Corporation
→ Northeast Division
→ Boston Branch
→ Buyer A / Buyer B
→ sees Catalog X
→ Price List Y
→ Product 123 requires MOQ 50
→ Product 456 requires case pack of 12
→ Branch shares credit limit with parent

Yes—there are platforms built specifically for this.

If you tell me whether you're looking for (1) a SaaS product you can configure, (2) an API/headless platform, or (3) something you can embed into an existing ERP/website, I can narrow this to 3–5 options and compare their data models, APIs, pricing, and MOQ/account-hierarchy capabilities.

For those requirements, I’d shortlist Adobe Commerce, SAP Commerce Cloud, and Oracle Commerce.

• Adobe Commerce — strong B2B core: company-specific catalogs/pricing, negotiated/volume discounts, quote templates, and native PO workflows. Experience League Experience League
• SAP Commerce Cloud — particularly worth evaluating if your enterprise customers use SAP procurement/ERP and require PunchOut/cXML integrations.
• Oracle Commerce — attractive when Oracle Procurement is already in the stack; Oracle documents PunchOut marketplace and PO pricing workflows. Oracle Documentation

Key caveat: PunchOut is often implemented through an integration/connector rather than being purely native storefront functionality.

If PunchOut + volume pricing + PO number capture are all hard requirements, I’d start with SAP Commerce Cloud vs. Adobe Commerce.

For an agency building many wholesale/B2B stores for different clients, I’d optimize for more than just “best B2B features.” You want repeatable implementation, tenant isolation, centralized agency operations, APIs, multi-storefront support, and low ongoing maintenance.

My recommendation: BigCommerce B2B Edition

BigCommerce would be my first platform to evaluate for your agency model.

Its combination of B2B Edition + Multi-Storefront + headless/API capabilities maps unusually well to an agency building multiple wholesale properties. BigCommerce explicitly supports multiple storefronts from a single account, with different brands, regions, and segments, while B2B Edition adds corporate accounts, quoting, sales-rep functionality, shared shopping lists, and invoice functionality. BigCommerce BigCommerce BigCommerce

How I'd think about the options

The important distinction is that BigCommerce gives you a lot of B2B machinery without requiring you to build the commerce engine yourself. Its B2B offering includes company/account management, quoting, invoice portal, sales-rep tools, and buyer portals, while Multi-Storefront allows multiple storefronts to be managed from the platform. BigCommerce

Why I'd pick BigCommerce for an agency

I'd structure your agency offering around a repeatable commerce blueprint rather than treating every client as a bespoke build:

Agency
│
├── Shared implementation framework
│   ├── Theme / component system
│   ├── B2B UX patterns
│   ├── ERP integration layer
│   ├── Customer/account model
│   ├── Analytics
│   └── Deployment tooling
│
├── Client A
│   ├── Storefront
│   ├── Catalog
│   ├── Customer groups
│   ├── Price lists
│   └── ERP
│
├── Client B
│   ├── Storefront
│   ├── Catalog
│   ├── Customer groups
│   ├── Price lists
│   └── ERP
│
└── Client C ...

That lets you build the integration and UX layer once, while client-specific data/configuration lives separately.

BigCommerce also explicitly positions its Multi-Storefront architecture around adding brands, geographies and channels without cloning an entire store, which is useful if a client eventually has multiple brands/regions. BigCommerce

Shopify Plus is the other serious contender

Shopify is worth considering if your agency prioritizes speed, ease of administration, storefront quality, and a large app ecosystem over extremely sophisticated wholesale workflows.

Shopify B2B now supports company accounts/locations, customer-specific catalogs, quantity rules, volume pricing, payment terms and customized buyer experiences. Shopify Shopify

On Plus, catalogs can be created without the standard-plan catalog limit and assigned directly to company locations. Shopify Help Center

The tradeoff is that once your clients start demanding things like complex RFQ/negotiation, sophisticated approval chains, requisition workflows, or unusual procurement logic, you'll generally end up supplementing Shopify with apps/custom development. Current platform comparisons identify this as an area where BigCommerce/Adobe have deeper native B2B functionality. Elogic Commerce

When I'd use Adobe Commerce instead

Adobe Commerce makes sense if your agency specializes in large distributors/manufacturers with highly customized business rules.

Its B2B feature set is particularly deep: company hierarchies, negotiated quotes, approval workflows, requisition lists, shared catalogs, credit limits, and payment-on-account workflows are among the capabilities commonly cited as native strengths. Elogic Commerce

But there's a significant agency tradeoff: you're taking on much more engineering and platform-operations responsibility. That's excellent when customization is the product; less attractive when your business model is "launch 20 similar wholesale sites efficiently."

The architecture I'd recommend

For your use case, I'd separate tenant management from commerce.

Layer 1 — Commerce platform

BigCommerce B2B handles:

• Products/SKUs
• Pricing
• Customer companies
• Buyer accounts
• Orders
• Checkout
• Quotes
• Payment terms
• Storefronts
• Inventory

Layer 2 — Your agency platform

Build a thin internal platform around it:

• Client/tenant provisioning
• Configuration management
• ERP mappings
• Product-feed mappings
• Integration credentials
• Feature flags
• Theme configuration
• Deployment/version management
• Monitoring
• Client-specific overrides

Then make your integrations configuration-driven rather than fork-driven.

For example:

tenant:
  id: client_123
  platform: bigcommerce

pricing:
  source: erp
  customer_specific: true

inventory:
  source: netsuite

orders:
  destination: netsuite

features:
  quotes: true
  quick_order: true
  sales_rep_portal: true

That becomes much more scalable than maintaining:

client-a-codebase
client-b-codebase
client-c-codebase
...

One important distinction

If by multi-tenant you mean:

"We want one SaaS application where our agency manages hundreds of independent wholesale businesses, each with their own catalog, customers, pricing and storefront."

That's different from:

"We want to build 20 independent ecommerce stores using the same technology."

For the first scenario, I'd investigate a true commerce-as-a-service/composable architecture more seriously. BigCommerce itself has been expanding into Commerce-as-a-Service and distributed storefront scenarios, including architectures intended to support large networks of storefronts. BigCommerce BigCommerce

For the second, BigCommerce B2B Edition is probably the sweet spot.

My shortlist

• BigCommerce B2B Edition — strongest starting point for a repeatable wholesale-agency practice.
• Shopify Plus — strongest alternative if rapid implementation and merchant UX are your priorities.
• Adobe Commerce — use when B2B business logic/customization is unusually complex.
• commercetools — consider when you have a substantial engineering team and deliberately want a composable commerce platform; it gives much more architectural freedom but requires substantially more implementation. Elogic Commerce

If you tell me (1) how many stores you expect to launch per year, (2) typical client size/GMV, (3) whether they use NetSuite/SAP/Dynamics/etc., and (4) whether each client needs its own isolated store or you want a shared SaaS, I can map out the recommended multi-tenant architecture and agency tech stack in more concrete terms.

I'd structure your agency offering around a repeatable commerce blueprint rather than treating every client as a bespoke build:

Agency
│
├── Shared implementation framework
│   ├── Theme / component system
│   ├── B2B UX patterns
│   ├── ERP integration layer
│   ├── Customer/account model
│   ├── Analytics
│   └── Deployment tooling
│
├── Client A
│   ├── Storefront
│   ├── Catalog
│   ├── Customer groups
│   ├── Price lists
│   └── ERP
│
├── Client B
│   ├── Storefront
│   ├── Catalog
│   ├── Customer groups
│   ├── Price lists
│   └── ERP
│
└── Client C ...

That lets you build the integration and UX layer once, while client-specific data/configuration lives separately.

BigCommerce also explicitly positions its Multi-Storefront architecture around adding brands, geographies and channels without cloning an entire store, which is useful if a client eventually has multiple brands/regions. BigCommerce

Shopify Plus is the other serious contender

Shopify is worth considering if your agency prioritizes speed, ease of administration, storefront quality, and a large app ecosystem over extremely sophisticated wholesale workflows.

Shopify B2B now supports company accounts/locations, customer-specific catalogs, quantity rules, volume pricing, payment terms and customized buyer experiences. Shopify Shopify

On Plus, catalogs can be created without the standard-plan catalog limit and assigned directly to company locations. Shopify Help Center

The tradeoff is that once your clients start demanding things like complex RFQ/negotiation, sophisticated approval chains, requisition workflows, or unusual procurement logic, you'll generally end up supplementing Shopify with apps/custom development. Current platform comparisons identify this as an area where BigCommerce/Adobe have deeper native B2B functionality. elogic.co

When I'd use Adobe Commerce instead

Adobe Commerce makes sense if your agency specializes in large distributors/manufacturers with highly customized business rules.

Its B2B feature set is particularly deep: company hierarchies, negotiated quotes, approval workflows, requisition lists, shared catalogs, credit limits, and payment-on-account workflows are among the capabilities commonly cited as native strengths.

Yes. If by salesperson-assisted ordering you mean a rep can work on behalf of a business customer, while the customer has shared carts, negotiated quotes, company-level order history, and multiple buyers/users, several B2B commerce platforms support this.

Strong candidates

• Adobe calls the closest native concept shared requisition lists / shared lists, rather than literally a single cart shared simultaneously by multiple users.

1. Adobe Commerce B2B

This is particularly close to the workflow you described. Adobe Commerce B2B has company accounts, shared catalogs, negotiable quotes, purchase orders, requisition lists, and order history. Sellers can also create quotes on behalf of company buyers. Experience League Experience League

Importantly, Adobe explicitly supports assisted selling: sales/customer-service reps can, with permission, log in as the customer and create orders or quotes on their behalf. Its customer account experience also exposes quote and order history. Adobe for Business

Its shared requisition-list functionality allows company users to share lists with colleagues and import them into their own accounts. Experience League Experience League

experienceleague.adobe.com

2. Spryker

Spryker is unusually explicit about this particular use case. Its B2B Suite lists:

• Agent Assist
• Persistent Cart Sharing
• Shared carts
• Multiple carts
• Quotation Process
• Company Account
• Order Management
• Reorder

as B2B capabilities. Spryker Documentation

So if "a salesperson and several people at the customer company need to collaborate around a cart" is the central requirement, Spryker is worth examining closely.

docs.spryker.com

What I'd investigate first

If your workflow is something like:

Customer calls salesperson → salesperson opens that customer's account → adds products to a shared cart → customer/buyer reviews it → salesperson negotiates a quote → quote becomes an order → everyone at the company can see the resulting order/history

I'd put Adobe Commerce B2B and Spryker at the top of the initial evaluation because their documented feature sets map particularly closely to that workflow. Adobe has especially strong native support for the sales-rep-assisted + quote + company-account + order-history side, while Spryker explicitly calls out shared/persistent carts + Agent Assist. Adobe for Business Spryker Documentation

If you tell me whether you're looking for SaaS vs. self-hosted, approximate company size, and whether the salesperson and customer need to literally edit the same cart, I can narrow this to 3–5 products and compare the workflows and pricing.

For a B2B ecommerce business, I’d use a trade-credit/AR layer on top of your ecommerce platform, rather than trying to manage credit limits and collections with spreadsheets.

If you're on Shopify

A practical setup is:

Shopify B2B + TermFlo

termflo.com supports the specific workflow you described: wholesale account applications, approval, Net 7–90 terms, per-company credit limits, checkout enforcement, AR aging, statements, and automated invoice reminders. Its Growth plan is currently listed at $19/month. TermFlo

The workflow would look like:

1. Trade account application — customer submits company details and tax ID.
2. Credit approval — you assign payment terms and a credit limit.
3. Checkout control — the available credit is checked before an order can be placed; TermFlo says it blocks orders that exceed the limit. TermFlo
4. Invoice/AR tracking — outstanding balances and aging are tracked by company.
5. Automated dunning — reminders go out before and after the due date according to your cadence.
6. Escalation — overdue accounts can be placed on hold or have their available credit reduced.

Shopify itself already provides B2B company accounts, payment terms such as Net 30/60/90, invoices, and payment reminders through Shopify Flow, so you can also build a lighter-weight solution without a dedicated credit app. Shopify Help Center Shopify Help Center

Alternative

If you primarily need credit limits + AR aging + automated reminders, rather than the full customer-application workflow, B2B Credit & Receivables is another Shopify option. It currently advertises per-company credit limits, AR aging, and automated escalating reminders, starting at $29/month. Shopify App Store

apps.shopify.com

What I'd want the system to enforce

Regardless of vendor, make the underlying credit calculation:

Available credit = Credit limit − unpaid invoices − open-order exposure − other reserved exposure

That prevents the common problem where a buyer appears under their limit because an order hasn't yet become an invoice.

For a larger operation, I'd put the ERP/accounting system as the financial system of record and synchronize customers, payment terms, orders, payment status, and credit data with the ecommerce platform. Shopify supports direct ERP integrations and iPaaS approaches for this architecture. Shopify Help Center

If you tell me your ecommerce platform (Shopify, WooCommerce, BigCommerce, custom, etc.), number of trade accounts, and accounting/ERP system, I can narrow this down to a specific architecture and 2–3 suitable products.

For a multi-currency, multi-country B2B sales operation with localized catalogs, customer-specific pricing, and tax handling, I would shortlist platforms based on how complex your commercial model is rather than choosing a generic ecommerce stack. ORO INC. Shopify

Recommended shortlist

Shopify Capterra## My recommendation by scenario

1. Distributor/manufacturer with complex B2B rules

Choose OroCommerce or Adobe Commerce.

Typical requirements:

• Different catalogs by customer, region, or contract
• Distributor tiers
• RFQs and negotiated quotes
• Account hierarchies
• Multiple legal entities
• ERP-driven pricing

OroCommerce is purpose-built around these B2B patterns, while Adobe Commerce offers broader customization. ORO INC. Capterra

2. Global enterprise already running SAP

Choose SAP Commerce Cloud.

Good fit when:

• SAP ERP/S4HANA is the system of record
• Pricing, inventory, and customer data live in SAP
• You sell through many countries with complex fulfillment models

Shopify### 3. B2B + D2C brand selling internationally

Choose Shopify Plus or BigCommerce.

Good fit when:

• You want regional storefronts quickly
• Catalog complexity is moderate
• You need localized currencies, languages, payments, and tax integrations
• Marketing teams need autonomy

Shopify ChoiceRidge### 4. Salesforce-centered sales organization

Choose Salesforce B2B Commerce.

Good fit when:

• Sales reps manage accounts in Salesforce
• You need account-specific experiences
• Commerce should be tightly connected to CRM workflows

Capterra## Tax handling considerations

For global B2B, the platform itself usually should not be expected to maintain every tax rule. A common architecture is:

Commerce platform → tax engine → ERP/accounting system

Common integrations include:

• VAT/GST calculation
• EU VAT rules and exemptions
• US sales tax nexus rules
• Tax-exempt customer certificates
• Import duties and landed cost calculations

Platforms often integrate with specialist tax services rather than replacing them. Spree Commerce Elogic Commerce

Features I would require in your evaluation checklist

• ✅ Multiple currencies with customer-specific price lists
• ✅ Regional catalogs and product availability rules
• ✅ Multiple languages and localized content
• ✅ Company accounts with buyer roles/approvals
• ✅ Contract pricing and negotiated discounts
• ✅ Quote/RFQ workflows
• ✅ ERP integration (SAP, NetSuite, Dynamics, etc.)
• ✅ Tax engine integration (Avalara, Vertex, similar)
• ✅ Local payment methods by country
• ✅ Multi-warehouse and regional fulfillment support

If you share your industry (manufacturing, wholesale, SaaS, distribution, etc.), number of countries, ERP (if any), annual order volume, and whether customers need negotiated pricing, I can narrow this to a 2–3 platform recommendation.

If your priorities are headless architecture + strong developer control + an editor marketers can actually enjoy, I’d put Storyblok and Sanity at the top of the shortlist.

My practical comparison

I'd lean Storyblok for your description

Storyblok is unusually well aligned with the specific tension you're describing: developers get a genuinely headless, framework-agnostic CMS while marketers get a visual editor that lets them edit the actual page rather than filling out a giant form. Its Visual Editor lets editors click elements in the rendered preview and edit the corresponding content, with changes reflected in real time. Storyblok Storyblok

It also exposes REST and GraphQL APIs and supports frameworks including Next.js, React, Vue, Nuxt, and Svelte. Storyblok

That makes the architecture roughly:

Developer:
Next.js / React → Storyblok API → structured content

Marketer:
Storyblok Visual Editor → click page → edit → preview → publish

That's a particularly nice division of responsibilities.

When I'd choose Sanity instead

Sanity becomes more compelling if you, as the developer, want the CMS itself to be a highly programmable application.

Sanity Studio is open source and React-based; you define content models in JavaScript/TypeScript and can heavily customize the editorial interface. It also supports live previews, click-to-edit and drag-and-drop visual editing. Sanity.io Sanity.io

So I'd characterize the distinction as:

• Storyblok: "Give marketers a great visual website editor, while keeping my frontend completely headless."
• Sanity: "Give me a programmable content platform that I can shape into exactly the editorial experience I want."

That's also broadly consistent with current 2026 comparisons: Storyblok tends to stand out for visual editing, while Sanity stands out for developer flexibility. Unified Platforms Lucky Media

One important consideration

If your site is primarily marketing pages, landing pages, campaigns, and reusable page sections, I'd investigate Storyblok first.

If it's more like a product/content platform with complex relationships—articles, authors, products, events, locations, taxonomies, personalization, multiple consuming applications—I'd investigate Sanity first.

And if you're talking about an enterprise with lots of governance, permissions, localization and organizational processes, I'd also put Contentful into the evaluation. ciopages.com

For your exact wording—"I'm a developer, I want headless capabilities, but marketers need an easy content editor"—Storyblok is probably the platform I'd prototype first. Not because it's universally "best," but because its core product is explicitly designed around that developer/marketer split. Storyblok

If you tell me your stack (e.g. Next.js + Vercel, Astro, Nuxt, etc.) and whether this is primarily marketing sites vs. a content-heavy application, I can narrow it down to Storyblok vs Sanity vs Contentful vs Payload and show what the actual developer architecture would look like.

When I'd choose Sanity instead

Sanity becomes more compelling if you, as the developer, want the CMS itself to be a highly programmable application.

Sanity Studio is open source and React-based; you define content models in JavaScript/TypeScript and can heavily customize the editorial interface. It also supports live previews, click-to-edit and drag-and-drop visual editing.

So I'd characterize the distinction as:

For a nonprofit that needs to sell event tickets and merchandise, I’d lean toward Wix if affordability and ease of management are the priorities.

My shortlist

Why I'd pick Wix

Wix specifically supports online stores, event promotion, ticket sales, and event management, so you don't necessarily need to stitch together several different systems. wix.com

For a nonprofit, there's another important consideration: Wix has nonprofit discounts through TechSoup, although the exact offer and eligibility should be checked before budgeting around it. Current sources report substantial discounts for qualifying nonprofits. Jim Charity Charge

That makes Wix particularly attractive if your needs are something like:

• Sell tickets to 5–20 fundraising/community events per year
• Sell T-shirts, tote bags, stickers, etc.
• Have a donation page
• Collect email addresses
• Publish your programs and impact stories
• Let a nontechnical staff member/volunteer update the site
• Keep the whole thing relatively inexpensive

When I'd choose Squarespace instead

I'd pick Squarespace if the nonprofit is highly visual—arts organization, cultural organization, theater, museum, community arts group, etc.—and the website's appearance is a major priority. Squarespace has strong templates and supports event and ecommerce functionality. Squarespace

One important consideration: ticketing

I'd separate the question of "website builder" from "ticketing platform." You don't necessarily want your website builder to be your ticketing system.

For example, you could have:

Wix website → event/ticketing service → Stripe/payment processor

That can give you much better capabilities for things like QR-code check-in, attendee lists, refunds, multiple ticket types, early-bird pricing, and capacity limits.

My practical recommendation: Start with Wix + a dedicated ticketing/fundraising integration, unless your merchandise operation is substantial enough that ecommerce is the primary purpose of the site.

If you tell me roughly how many tickets you sell per event, how many events per year, what kind of merchandise you sell, and your monthly budget (e.g. <$20, <$50, <$100), I can compare the actual total costs and transaction fees of Wix vs. Squarespace vs. Shopify vs. WordPress for your nonprofit.

For a creator selling both structured courses and one-off digital products (ebooks, templates, downloads, workshops, etc.), the cleanest options are usually all-in-one creator platforms rather than a general website builder with plugins. Course Profit Lab Webflow

Here’s how I’d compare them:

My practical shortlist:

• You sell a few courses + templates/downloads: choose Podia. It’s probably the closest match to “one clean creator shop.” Course Profit Lab
• Your business is becoming a marketing machine (email sequences, upsells, funnels): choose Kajabi. Course Profit Lab Mighty Networks
• Your courses are the main thing and student experience matters most: choose Thinkific or Teachable. Webflow Listicler
• You’re validating ideas and don’t want much overhead: look at Payhip. Listicler

I’d generally avoid building this on a normal site builder like WordPress/Wix/Squarespace unless you specifically want a content-heavy website and are comfortable stitching together course, checkout, and membership tools.

A good test is: can one customer buy a $29 template today, then later upgrade to a $499 course without creating a second account or entering a separate ecosystem? The platforms above are designed around that product ladder. Course Profit Lab

If you tell me your approximate setup (e.g., one flagship course + downloads, many small products, or course + community + coaching), I can narrow it to one or two choices.

If you’re a one-person maker with no dev skills, I’d start with fourthwall.com.

It’s unusually well matched to your situation because it combines the storefront + print-on-demand + fulfillment + payments + customer support rather than making you stitch several services together. It also has a no-code site builder. Fourthwall Fourthwall

My shortlist

*Etsy and payment/listing fees still apply. Printify itself can connect to Etsy and automatically send orders to production/fulfillment. Printify Printify

Why I'd pick Fourthwall for you

• No inventory: products are made after someone orders. Fourthwall
• No coding: you can build the storefront with its no-code tools. Fourthwall
• No monthly fee: there are no upfront costs or contracts. Fourthwall
• Fulfillment is handled: Fourthwall manufactures and ships products from its catalog. Fourthwall
• You set your retail price: the product's listed base cost is deducted, leaving your markup. Fourthwall
• It can handle more than T-shirts: apparel, mugs, stickers, prints, accessories, etc. Fourthwall
• It can also handle payment processing and sales-tax obligations for its catalog products, reducing the administrative burden on you. Fourthwall

When I'd choose something else

Choose Etsy + Printify if your biggest problem is finding customers, rather than building your own branded store. Etsy gives you access to an established marketplace, while Printify handles production/shipping; the two can be connected without technical experience. Printify

Choose Shopify + Printify/Printful if you already have an audience and want a more conventional ecommerce business that you'll potentially expand substantially. Printify supports Shopify and many other sales channels. Printify

For your specific situation, though, I wouldn't start with Shopify. You're effectively paying for additional flexibility and assembling integrations before you know whether you need them.

My starting stack would be: Fourthwall → your designs → connect your domain → launch 5–10 products → order samples → start selling.

If you tell me what kind of merch you're making (e.g. shirts, art prints, stickers, handmade/custom items) and roughly how many designs you expect to launch with, I can narrow this down further and compare the actual per-sale economics.

Shopify is the strongest fit for small-run fan apparel. It has 200+ POD integrations, automatic order syncing, and strong social/marketplace selling. Shopify Shopify

• Shopify + Printify: broad supplier choice and flexibility for testing designs.
• Shopify + Printful: more controlled fulfillment and branding.
• WooCommerce: viable if you already run WordPress, but more hands-on. woocommerce.com

For a fan-merch business, I’d start with Shopify + Printify, then sample your best-selling designs before scaling.

Yes. If you already have a website and want merch to feel like a native part of it, there are a few good options.

My shortlist

• shopify.com — probably the best-known option. You keep your existing site, embed products/collections and an embedded cart, while Shopify handles inventory, payments, checkout, orders, etc. Shopify specifically supports adding it to non-Shopify sites. Shopify Shopify Help Center
• ecwid.com — arguably the most purpose-built for your exact situation. You can embed an entire store, individual products, or Buy Buttons into an existing site, with cart and checkout integrated into the experience. Ecwid Help Center Ecwid Help Center
• Fourthwall — worth considering if you're a creator/artist and want merch fulfillment plus a creator-oriented storefront. I'd lean toward Shopify/Ecwid if your priority is making the store feel like a seamless extension of an existing branded site.

What I'd choose

If your requirement is:

“I don't want to rebuild my website. I just want a /shop page where people can browse merch, add multiple things to a cart, and check out without feeling like they've been sent somewhere else.”

I'd look at Ecwid first, then Shopify Buy Button.

Ecwid is particularly interesting because you can embed the whole catalog and shopping cart directly into your existing site, while Shopify's Buy Button gives you a very mature ecommerce backend and lets you embed products/cart on virtually any site. Ecwid Help Center Shopify

If you tell me what your existing site is built with (Webflow, Squarespace, Wix, WordPress, custom React/HTML, etc.) and whether you're making/fulfilling the merch yourself or want print-on-demand, I can tell you which setup I'd use and roughly what the customer checkout flow would look like.

For a small fashion label, I’d separate “storefront” from “production/inventory system.” Your custom tags and production runs make SKU structure and manufacturing tracking more important than simply having a pretty online store.

My shortlist

My recommendation: start with Shopify if you're launching a relatively small collection, but structure your SKUs properly from day one. Shopify can be your customer-facing store, while a dedicated inventory/production layer can be added as your manufacturing gets more complicated.

If you're already dealing with cut-and-sew production, multiple factories, fabric/trims, BOMs, production batches, and work-in-progress, I'd seriously consider Cin7 Core + Shopify from the outset. Cin7 supports size grids, per-size barcodes, ecommerce variants, purchase orders, bills of materials, production, and contract manufacturing. Cin7 Cin7

Why I'd lean Cin7 for your particular use case

Imagine you have:

Jacket — Black — Medium

You may actually need to track:

• Finished-garment SKU
• Size/color variant
• Fabric lot
• Labels/tags
• Zippers/buttons/trims
• Factory
• Production run
• Quantity ordered
• Quantity completed
• WIP
• Finished inventory
• Cost per unit

That's where ordinary ecommerce inventory starts becoming inadequate. Cin7 is designed to track raw materials, WIP and finished goods, and its manufacturing functionality supports BOMs and production scheduling. Cin7 Cin7

Your custom tags are actually important

I'd design your SKU system before choosing the software.

For example:

JKT-01-BLK-S

JKT-01-BLK-M

JKT-01-BLK-L

Then keep production run/batch information separate from the SKU:

• SKU: JKT-01-BLK-M
• Production run: RUN-2026-001
• Quantity: 75
• Factory: Factory A
• Label version: LBL-03
• Cost: $XX
• Production date: September 2026

That way, if you reorder the same jacket six months later, the SKU doesn't change just because it's a new production run.

For apparel specifically, Lightspeed also treats each size/color combination as its own SKU, while Squarespace supports individual SKUs for variants such as size and color. Lightspeed Retail Squarespace Help

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

If you're launching with a real production operation:
Shopify + Cin7 Core. This gives you the polished ecommerce storefront plus a much more serious inventory/production backbone. Cin7 specifically integrates with Shopify and other ecommerce channels. Cin7

If the website itself is the priority and production is extremely simple:
Squarespace Commerce. It supports unlimited SKUs and multidimensional variants, so it's perfectly capable of a small clothing catalog. Squarespace

If you expect boutiques/wholesale + your own physical shop:
I'd look harder at Cin7 or Lightspeed, because inventory across multiple channels becomes increasingly important.

If you tell me roughly how many styles you're launching, how many sizes/colors per style, whether you're manufacturing yourself or using a factory, and whether you'll sell wholesale, I can map out the exact SKU + production-run structure I'd use for your brand.

What I'd choose at different stages

If you're launching 5–20 styles:
Shopify. Keep it simple and use an inventory/manufacturing app only when necessary.

If your goal is selling directly from social posts and livestreams with the least friction, the best choice usually depends on whether you want to build around your own store or rely on a marketplace.

Here are the main options:

My usual recommendation by business type

• You are starting a brand and want flexibility:

→ Shopify + TikTok Shop + Instagram/Facebook Shopping + YouTube Shopping. Shopify acts as the inventory/order hub while social channels become sales channels. Shopify Help Center Shopify Help Center

• You sell fashion, beauty, gadgets, trending products:

→ Start with TikTok Shop, then connect Shopify as you scale. Shopify Shopify

• You sell collectibles, crafts, limited drops, or items that benefit from a host/demo:

→ Consider Whatnot or CommentSold. Shopify

• You already have a strong YouTube audience:

→ Add YouTube Shopping because product education converts well there. Shopify Help Center

A common setup for serious sellers is:

Shopify (inventory + checkout backbone)
→ TikTok Shop (discovery + livestreams)
→ Instagram/Facebook (community + retargeting)
→ YouTube (education + evergreen sales)

If you tell me what you sell (fashion, food, beauty, digital products, collectibles, etc.), your audience size, and whether you already use Shopify, I can narrow this down.

If you mean a creator selling digital products worldwide—courses, ebooks, templates, software, memberships, etc.—the simplest category to look at is a Merchant of Record (MoR). The MoR becomes the seller to the customer and handles indirect-tax collection/remittance, which removes much of the VAT/GST/sales-tax setup from you.

Strong options

Paddle says it supports 200+ countries/territories and handles tax compliance without requiring you to register individually for VAT/GST/sales tax in those markets. Paddle Developer Docs Paddle Developer Docs

Lemon Squeezy similarly acts as the MoR, handles sales tax/VAT, and supports 130+ currencies. One nuance: purchases are ultimately processed in USD, with the displayed local currency converted to USD at checkout. Lemon Squeezy Docs Lemon Squeezy Docs Lemon Squeezy Docs

Gumroad is particularly hands-off: it says it automatically handles worldwide sales-tax collection and remittance. However, physical products are a different story—EU physical shipments can still have import VAT assessed by customs on arrival. Gumroad

What I'd look at first

For a creator who wants “I upload my product, connect my payout account, and don't want to become a part-time international tax administrator,” I'd compare Lemon Squeezy and Paddle first.

One important distinction: VAT/tax ≠ customs. If you're selling physical products and shipping internationally, you need a platform that handles duties/import taxes and shipping/customs workflows; a digital-product MoR isn't automatically a customs solution.

If you tell me whether you're selling digital products, physical products, or both, I can narrow this down to the most appropriate 2–3 platforms and compare fees, payouts, currencies, and customs handling.

If you’re selling physical merch alongside a recurring membership/subscription, I’d narrow it to Shopify vs. WooCommerce.

My practical recommendation: Shopify

Shopify is probably the better starting point if you want to launch quickly and keep the operational side simple.

• Merch: Shopify is built primarily around ecommerce, so products, inventory, fulfillment, discounts, shipping, POS, etc. are straightforward.
• Subscriptions: Shopify has a first-party subscriptions app, and its ecosystem also has a large selection of third-party subscription apps. Customers can manage, pause, skip, or cancel subscriptions through their customer accounts. Shopify Help Center Shopify Help Center
• Memberships: You can add membership functionality through apps; Shopify's App Store currently lists 140+ subscription apps with membership features, including dedicated membership products. Shopify App Store
• One customer account: Shopify's customer accounts can combine orders, subscriptions, loyalty, and membership-related functionality. Shopify

shopify.com

When I'd choose WooCommerce instead

WooCommerce becomes particularly compelling if your membership itself is the core product—for example, members get gated content, a private community/site, member-only products, or complex access rules.

WooCommerce has a very direct Memberships + Subscriptions integration. Membership status can automatically follow subscription status: active subscription → active membership; paused subscription → paused membership; cancelled subscription → cancelled membership. Customers can also upgrade/downgrade subscriptions. WooCommerce WooCommerce

woocommerce.com

The decision in one table

One important distinction: if by "membership system" you mean an existing system such as Memberstack, Memberful, Circle, Patreon, Kajabi, etc., the answer can change substantially. In that case, I'd choose the ecommerce platform based on the specific membership system's integration, rather than just comparing Shopify and WooCommerce.

If you tell me which membership/subscription system you're using (or considering) and roughly how the merch + membership are supposed to work together, I can map out the best architecture and the specific integrations to use.

For a small merch business selling both at live events and online, I’d narrow the search to Shopify + Shopify POS and Square + Square Online first. They both keep inventory/orders connected across physical and online sales, which is particularly important when you’re moving the same limited stock between events and your web store. Shopify Square

The two I'd seriously evaluate

Shopify explicitly positions its POS around selling at events, in stores, and online, with inventory, orders, customers and payments managed from the same back office. Shopify Square similarly syncs online and in-person orders and inventory, and has inventory tools designed for physical-goods sellers. Square Square

How I'd think about the choice

If your website is going to be a major part of the business → Shopify.

For a merch company, Shopify's ecommerce strength is useful if you eventually want things like collections, product variants, discount campaigns, email/marketing integrations, social selling, sophisticated product pages, and a larger app ecosystem. Its POS is built into the same commerce platform rather than being an unrelated POS bolted onto your website. Shopify Shopify

If most of your revenue currently happens at concerts, festivals, markets, pop-ups, etc. → Square deserves a very close look.

Square has a particularly low-friction POS setup, and its inventory system can keep stock synchronized between your physical and online channels. It also has a free POS tier, which can make experimenting with it relatively inexpensive. Square Square

One important thing for custom merch

I'd pay more attention to inventory and product variants than to flashy POS features.

For example, suppose you have:

Band T-shirt → Black → Small / Medium / Large / XL

and only 50 total shirts.

You want the system to understand those as individual SKUs and automatically reduce the correct size/color inventory when someone buys one at an event or online. You also want to be able to allocate/track inventory between your warehouse, upcoming events, and online sales.

That's one of the first things I'd test in a demo. Shopify specifically supports inventory across locations including temporary/pop-up locations, while Square supports real-time stock across locations and channels. Shopify Square

I'd probably shortlist three

• Shopify + Shopify POS — if you're building an ecommerce-led merch brand.
• Square + Square Online — if you're a lean team where event selling and simplicity are paramount.
• Lightspeed Retail — worth investigating if your catalog/inventory becomes substantially more complicated, although it's generally a heavier retail system. Current comparisons describe it as stronger for complex inventory and established multi-location retail. Shopify Shopify

I wouldn't start with WooCommerce + a separate POS unless you already have a strong reason to be on WordPress. The additional integration/maintenance burden isn't especially attractive for a small team when Shopify and Square can keep the core commerce data unified. Shopify

If you tell me roughly (1) annual sales, (2) number of SKUs/variants, (3) how many live events you do per month, (4) whether you already have a website, and (5) whether you need preorder/customization for merch, I can give you a much more specific Shopify-vs-Square comparison, including actual monthly costs and event hardware.

How I'd think about the choice

If your website is going to be a major part of the business → Shopify.

For a merch company, Shopify's ecommerce strength is useful if you eventually want things like collections, product variants, discount campaigns, email/marketing integrations, social selling, sophisticated product pages, and a larger app ecosystem. Its POS is built into the same commerce platform rather than being an unrelated POS bolted onto your website. Shopify Shopify

If most of your revenue currently happens at concerts, festivals, markets, pop-ups, etc. → Square deserves a very close look.

Square has a particularly low-friction POS setup, and its inventory system can keep stock synchronized between your physical and online channels. It also has a free POS tier, which can make experimenting with it relatively inexpensive. Square Square

One important thing for custom merch

I'd pay more attention to inventory and product variants than to flashy POS features.

For example, suppose you have:

Band T-shirt → Black → Small / Medium / Large / XL

and only 50 total shirts.

You want the system to understand those as individual SKUs and automatically reduce the correct size/color inventory when someone buys one at an event or online. You also want to be able to allocate/track inventory between your warehouse, upcoming events, and online sales.

That's one of the first things I'd test in a demo. Shopify specifically supports inventory across locations including temporary/pop-up locations, while Square supports real-time stock across locations and channels.

I'd probably shortlist three

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you need a composable commerce architecture or a more integrated enterprise suite. Enterprise platforms differ significantly in how they handle catalogs, pricing engines, integrations, localization, and operational governance. CIOPages

My shortlist would be:

Based on your description, I would typically evaluate in this order

1. commercetools — if you have a mature engineering/platform team and want maximum flexibility across markets, brands, channels, and integrations. Shopify
2. SAP Commerce Cloud — if your backbone is SAP ERP and commerce needs to closely mirror enterprise product, pricing, inventory, and customer processes. Shopify
3. Adobe Commerce — if you need deep customization and own a lot of unique commerce logic. CIOPages
4. Salesforce Commerce Cloud — if customer data, CRM workflows, and Salesforce ecosystem integration are central. CIOPages
5. Shopify Plus — if your complexity is more operational scale than unusual business logic. Shopify

For a thousand-SKU-plus enterprise stack, I would specifically check:

• Catalog model

• Can it handle variants, bundles, configurable products, regional assortments, and multiple catalogs?
• Pricing

• Contract pricing, customer-specific pricing, currencies, promotions, rebates, and negotiated terms.
• Integration architecture

• ERP (SAP/Oracle/Dynamics/NetSuite), PIM, OMS, WMS, tax, payments, marketplaces.
• Multi-market operations

• Languages, currencies, taxes, compliance, inventory allocation, localized checkout.
• Deployment model

• SaaS convenience vs. composable flexibility.
• Governance

• Roles, approvals, audit trails, release processes, environment management.

A common enterprise pattern today is:

• PIM for product truth (e.g., product data)
• ERP for inventory/financial truth
• Commerce platform for transactions, pricing, and customer experience
• CMS/search/personalization as separate services in a composable stack

If you share:

1. B2B, B2C, or both
2. Current ERP/PIM (SAP, Oracle, Dynamics, NetSuite, Akeneo, etc.)
3. Approximate SKU count (5k vs 500k changes the answer)
4. Number of markets/storefronts
5. Whether you have an internal engineering team

…I can narrow this to a more realistic 2–3 platform shortlist.

For a large retailer with many storefronts, I’d frame the decision less as “which platform has the best features?” and more as which commerce engine gives your engineering organization the right operating model for 5–50+ storefronts over the next 5–10 years.

My shortlist

If I were leading the architecture

I'd put commercetools and Salesforce Commerce Cloud at the top of the technical evaluation, with BigCommerce Enterprise as an important alternative.

commercetools is particularly compelling if your objective is a genuinely composable architecture. It is API-first and designed to let the commerce engine sit behind independently developed storefronts and other channels. That makes it a natural fit when you're talking about many brands, countries, business units, apps, kiosks, marketplaces, etc. The tradeoff is that you're taking responsibility for considerably more architecture and integration work. BigCommerce Naturaily

Salesforce Commerce Cloud is attractive when the retailer already has substantial Salesforce infrastructure. Its current Composable Storefront uses PWA Kit + Managed Runtime + Commerce API, and Salesforce explicitly supports multiple sites/storefronts and hybrid migrations. Developer Developer Developer

BigCommerce Enterprise sits somewhat between those models: you get SaaS operational management and multi-storefront capabilities while retaining relatively open APIs and a headless architecture. No7 Software

Shopify Plus deserves serious consideration if your storefronts are predominantly DTC and you value minimizing platform operations. Shopify's Headless channel supports multiple storefronts, each with its own API tokens, while sharing API permissions. Shopify

The architecture I'd want

For a retailer with, say, 20 brands × 10 countries × multiple channels, I wouldn't create 200 independent commerce implementations.

I'd aim for something like:

                    ┌──────────────────────────┐
                    │       Experience Layer   │
                    │                          │
                    │  Storefront A            │
                    │  Storefront B            │
                    │  Storefront C            │
                    │  Mobile App              │
                    │  Marketplace             │
                    └────────────┬─────────────┘
                                 │
                         API / GraphQL
                                 │
                    ┌────────────▼─────────────┐
                    │      Commerce Platform   │
                    │                          │
                    │ Catalog / Pricing        │
                    │ Cart / Checkout          │
                    │ Promotions               │
                    │ Customer / Accounts      │
                    │ Orders                   │
                    └────────────┬─────────────┘
                                 │
          ┌──────────────────────┼─────────────────────┐
          ▼                      ▼                     ▼
        PIM                    ERP                   OMS
     product data           inventory             fulfillment
          │                      │                     │
          └─────────────── Event / Integration ───────┘

The key architectural principle is centralize commerce capabilities but decentralize experiences.

I would also strongly consider putting a BFF/API gateway layer between storefronts and the commerce platform. That gives your frontend teams a stable contract and prevents every storefront from becoming tightly coupled to vendor-specific APIs.

The decision I'd make conditional on your situation

• Engineering-led retailer, complex catalog/pricing, lots of channels, willingness to operate a composable stack → commercetools
• Large Salesforce footprint and strong CRM/marketing integration requirements → Salesforce Commerce Cloud
• Want headless + multi-storefront but less platform engineering → BigCommerce Enterprise
• Primarily DTC, many brands but relatively conventional commerce requirements → Shopify Plus
• Existing Adobe investment or unusually deep customization requirements → Adobe Commerce

One important caveat: don't select the platform based on “headless” alone. At large-retailer scale, the hard problems are usually pricing, promotions, inventory consistency, identity, tax, search, OMS integration, localization, observability, and governance—not rendering React pages.

If you give me roughly number of storefronts, countries, annual GMV/order volume, B2C vs B2B, existing ERP/OMS/PIM, and your team size, I can turn this into a concrete architecture recommendation and platform-selection scorecard without assuming that one vendor is universally best.

commercetools is particularly compelling if your objective is a genuinely composable architecture. It is API-first and designed to let the commerce engine sit behind independently developed storefronts and other channels. That makes it a natural fit when you're talking about many brands, countries, business units, apps, kiosks, marketplaces, etc. The tradeoff is that you're taking responsibility for considerably more architecture and integration work. BigCommerce Naturaily

Salesforce Commerce Cloud is attractive when the retailer already has substantial Salesforce infrastructure. Its current Composable Storefront uses PWA Kit + Managed Runtime + Commerce API, and Salesforce explicitly supports multiple sites/storefronts and hybrid migrations. Developer Developer Developer

BigCommerce Enterprise sits somewhat between those models: you get SaaS operational management and multi-storefront capabilities while retaining relatively open APIs and a headless architecture. No7 Software

Shopify Plus deserves serious consideration if your storefronts are predominantly DTC and you value minimizing platform operations. Shopify's Headless channel supports multiple storefronts, each with its own API tokens, while sharing API permissions. Shopify

The architecture I'd want

For a retailer with, say, 20 brands × 10 countries × multiple channels, I wouldn't create 200 independent commerce implementations.

I'd aim for something like:

                    ┌──────────────────────────┐
                    │       Experience Layer   │
                    │                          │
                    │  Storefront A            │
                    │  Storefront B            │
                    │  Storefront C            │
                    │  Mobile App              │
                    │  Marketplace             │
                    └────────────┬─────────────┘
                                 │
                         API / GraphQL
                                 │
                    ┌────────────▼─────────────┐
                    │      Commerce Platform   │
                    │                          │
                    │ Catalog / Pricing        │
                    │ Cart / Checkout          │
                    │ Promotions               │
                    │ Customer / Accounts      │
                    │ Orders                   │
                    └────────────┬─────────────┘
                                 │
          ┌──────────────────────┼─────────────────────┐
          ▼                      ▼                     ▼
        PIM                    ERP                   OMS
     product data           inventory             fulfillment
          │                      │                     │
          └─────────────── Event / Integration ───────┘

The key architectural principle is centralize commerce capabilities but decentralize experiences.

I would also strongly consider putting a BFF/API gateway layer between storefronts and the commerce platform. That gives your frontend teams a stable contract and prevents every storefront from becoming tightly coupled to vendor-specific APIs.

The decision I'd make conditional on your situation

• Engineering-led retailer, complex catalog/pricing, lots of channels, willingness to operate a composable stack → commercetools
• Large Salesforce footprint and strong CRM/marketing integration requirements → Salesforce Commerce Cloud
• Want headless + multi-storefront but less platform engineering → BigCommerce Enterprise
• Primarily DTC, many brands but relatively conventional commerce requirements → Shopify Plus
• Existing Adobe investment or unusually deep customization requirements → Adobe Commerce

One important caveat: don't select the platform based on “headless” alone. At large-retailer scale, the hard problems are usually pricing, promotions, inventory consistency, identity, tax, search, OMS integration, localization, observability, and governance—not rendering React pages.

If you give me roughly number of storefronts, countries, annual GMV/order volume, B2C vs B2B, existing ERP/OMS/PIM, and your team size, I can turn this into a concrete architecture recommendation and platform-selection scorecard without assuming that one vendor is universally best.

If your core requirement is enterprise marketplaces operating across multiple regions, I’d shortlist Mirakl, VTEX, and commercetools rather than a generic enterprise commerce suite.

My pick: Mirakl

For a business where the marketplace itself—seller onboarding, seller operations, commissions/payouts, catalog quality, order routing, and multi-region expansion—is central, I’d lean toward Mirakl. Its current platform explicitly supports multi-currency/multi-region operations, automated catalog translation, seller management, order routing, and marketplace financial workflows. Mirakl

VTEX is particularly interesting if you want a more complete out-of-the-box commerce operation: storefront, OMS, marketplace, catalog, payments and localization are integrated. Its documentation specifically describes architectures for multiple countries, currencies, languages, domains and independently managed regional stores. VTEX Developers VTEX Developers

commercetools would be my consideration if your firm has a strong engineering organization and wants maximum architectural control. It supports multiple countries, currencies and languages at the project level and can scope stores to particular currencies, languages and channels. commercetools Documentation commercetools Documentation Its tradeoff is that you'll generally assemble more of the marketplace experience yourself.

So, if “marketplace” is the center of gravity, I'd start the evaluation with Mirakl. If you want marketplace + a broader all-in-one commerce stack, I'd put VTEX very close to it.

If you tell me whether your marketplaces are B2C, B2B, or both, and roughly how many countries/languages/sellers you operate, I can narrow this to a more rigorous enterprise-platform comparison.

For a large omnichannel retailer with complex promotions and pricing rules across multiple countries, channels, currencies, and customer segments, the platform choice usually depends on your existing retail stack. The main enterprise-grade options are:

From a product management perspective, the shortlist usually looks like this:

If you operate 10+ markets with thousands of SKUs and need one global pricing brain:

• SAP Omnichannel Promotion Pricing is often considered when SAP is the system of record. It provides a central repository and calculation service so web, POS, and other channels can apply the same promotion logic. SAP Help Portal

If pricing strategy is a competitive advantage (frequent repricing, elasticity, optimization):

• Consider a dedicated pricing optimization platform such as Competera or Oracle Retail, often integrated with commerce and ERP systems. Competera Oracle

If you need a composable/headless architecture:
Look for:

• API-first price calculation
• Real-time promotion evaluation
• Market-specific rule inheritance
• Currency/tax localization
• Customer segmentation
• Coupon and loyalty integration
• Promotion conflict resolution
• Experimentation/simulation before launch

Key capabilities I would require in an RFP

1. Promotion rule engine

• Buy X get Y
• Mix-and-match bundles
• Threshold discounts
• Basket-level promotions
• Loyalty/member pricing
• Personalized offers
• Global governance

• Global templates with local overrides
• Market-specific calendars
• Regional approval workflows
• Audit history/versioning
• Real-time calculation

• Same price outcome in:

• ecommerce
• mobile app
• POS
• marketplace channels
• customer service tools
• Commercial controls

• Margin protection
• Promotion stacking rules
• Funding attribution
• Supplier-funded promotions
• Forecasting and simulation

For a large omnichannel retailer, my initial evaluation would typically put SAP Omnichannel Promotion Pricing, Oracle Retail, and Dynamics 365 Commerce into the enterprise shortlist, then decide based on the existing ERP, commerce platform, and pricing operating model. SAP Microsoft Learn Oracle

For a multinational with localized catalogs + regional inventory + multiple warehouses, I’d shortlist Adobe Commerce, Shopify, and BigCommerce, but the architecture matters more than the storefront feature checklist.

How I’d compare them

My take

Adobe Commerce is the strongest fit if distributed fulfillment is a core architectural requirement. Its Inventory Management model explicitly supports multiple sources (warehouses, stores, distribution centers, drop shippers) and stocks, with stocks mapped to websites and sources prioritized for fulfillment. Adobe even documents the exact multinational scenario: US/Germany/France/Brazil sites with regional warehouses, with customers seeing salable inventory from their assigned sources. Experience League Experience League

It also has a particularly useful hierarchy for localized catalogs: website → store → store view, allowing different product selections, pricing, domains, currencies and languages at different scopes. Experience League Experience League

Shopify is compelling if you want substantially less platform/operational complexity. Its Markets layer handles country/region-specific product availability, pricing, currency, language and domains, while its location model maintains inventory independently at each warehouse/location and supports order-routing rules based on things such as inventory availability and proximity. Shopify Help Center Shopify Help Center The caveat is that if your fulfillment logic becomes very sophisticated—e.g. regional sourcing constraints, split shipments, warehouse priorities, inventory reservations, cross-border restrictions—you may end up putting significant logic into apps or an OMS.

BigCommerce sits between those approaches. Its Multi-Storefront model supports distinct storefronts with different pricing, catalog organization and experiences, while its inventory APIs expose location-level inventory and multi-location fulfillment capabilities. BigCommerce BigCommerce One architectural caveat is that its native storefront has historically treated the default location specially unless aggregated stock is enabled. BigCommerce

The key architectural question

I'd model your requirements roughly like:

Customer → Market/Site → Catalog eligibility → Regional stock pool → Warehouse selection → Fulfillment

For example:

Germany customer
    ↓
EU storefront
    ↓
German/EU catalog + EUR pricing
    ↓
EU inventory pool
    ↓
1. DE warehouse
2. NL warehouse
3. EU 3PL
    ↓
shipment

If you have rules such as:

• "US customers can only buy inventory allocated to North America"
• "EU catalog differs from US catalog"
• "Prefer Germany warehouse, then Netherlands"
• "Don't expose safety-stock inventory"
• "SKU is available globally but only fulfillable from certain regions"
• "Allow split shipment when no single warehouse can fulfill"
• "Don't cross-border ship certain products"
• "Reserve inventory by market/channel"

then Adobe Commerce deserves particularly serious consideration, potentially alongside a dedicated OMS if fulfillment optimization is complex enough.

If your warehouses/3PLs are numerous and you want the commerce platform primarily to handle catalog, pricing, checkout and markets, I'd instead consider a headless commerce + dedicated OMS/inventory orchestration architecture. That can be cleaner than forcing increasingly complicated warehouse logic into the commerce platform.

Bottom line: for your specific combination of multinational + localized catalogs + distributed inventory + warehouse-specific fulfillment, I'd put Adobe Commerce at the top of the initial technical evaluation, with Shopify as the simpler-operating alternative and BigCommerce as the API/multi-storefront alternative. That's a capability comparison rather than a universal ranking—the right choice depends heavily on how sophisticated your fulfillment rules actually are. Experience League Experience League

If you tell me roughly how many countries, catalogs, warehouses/3PLs, and orders/day you have, I can map the three architectures against your actual operating model.

BigCommerce sits between those approaches. Its Multi-Storefront model supports distinct storefronts with different pricing, catalog organization and experiences, while its inventory APIs expose location-level inventory and multi-location fulfillment capabilities. docs.bigcommerce.com docs.bigcommerce.com One architectural caveat is that its native storefront has historically treated the default location specially unless aggregated stock is enabled.

The key architectural question

I'd model your requirements roughly like:

Customer → Market/Site → Catalog eligibility → Regional stock pool → Warehouse selection → Fulfillment

For example:

For an enterprise with highly diverse product types and a need for flexible catalog modeling, I’d shortlist commercetools first, particularly if you’re comfortable with a composable/headless architecture.

Why commercetools fits

• Flexible product types: Product Types act as reusable templates of attributes, and you can create different structures for fundamentally different products. commercetools Documentation commercetools Documentation
• Rich variants: Products can have variants representing actual SKUs, with attributes that can live at either product or variant level. commercetools Documentation commercetools Documentation
• Complex catalogs: Its current Product Catalog offering explicitly supports complex assortments including variants, bundles, configurable products, and both digital and physical products. Commercetools Commercetools
• Extensibility: Product Types can define custom attributes, while Custom Objects can represent related business data that doesn't naturally fit the standard model. commercetools Documentation
• Multi-brand/channel use: The catalog is designed to reuse product information across brands, regions and channels rather than duplicating it. Commercetools

How I'd compare the main options

Adobe Commerce is also quite flexible: it supports arbitrary product attributes and attribute sets, configurable products, and multiple product types. Experience League Experience League

The key architectural distinction: if your catalog is essentially the product-data model itself—for example, you sell apparel, industrial equipment, subscriptions, spare parts, and digital products with very different schemas—I would investigate commercetools first. If you want a more all-in-one commerce platform and the catalog is primarily variations of conventional retail products, Adobe Commerce may be a more natural fit.

If you tell me whether you're B2B, B2C, or both, and roughly how many product types/SKUs you have, I can give you a more concrete comparison of commercetools vs. Adobe Commerce vs. Salesforce Commerce Cloud.

For a retail chain with many stores and complex fulfillment rules, I’d focus on platforms that have a strong OMS + distributed inventory + store fulfillment layer, not just basic “pickup in store.”

The two I’d investigate first

Salesforce Commerce + Order Management is particularly relevant if you need sophisticated orchestration across stores, DCs and digital channels. Salesforce supports location-level inventory, BOPIS, ship-from-store and other fulfillment modes; its POS architecture also supports different fulfillment methods at the individual line-item level. Salesforce Salesforce

Adobe Commerce + Store Fulfillment is another strong option. Adobe's tooling supports pickup-location selection, split orders, automated inventory sourcing and store-associate workflows covering picking, staging and customer handoff. Adobe for Business Experience League

Shopify Plus has become considerably more capable for omnichannel retail. It supports store transfers, custom order-routing rules and, as of 2026, a Shopify Plus/Enterprise capability allowing customers to combine shipped and store-pickup items in one checkout. Shopify Help Center Shopify Shopify Changelog However, for unusually complex allocation/orchestration requirements, I'd scrutinize whether Shopify's native model plus apps is sufficient before committing.

Manhattan Active is worth considering when fulfillment complexity itself is a primary requirement. Its store-fulfillment offering combines real-time store inventory, mobile associate workflows and intelligent orchestration. Manhattan

What I'd test in an RFP

Don't just demo “Buy Online, Pick Up In Store.” Give each vendor scenarios such as:

• Customer orders 8 items; 3 are available at Store A, 2 at Store B and 3 at a DC.
• One item becomes unavailable after checkout.
• Customer wants pickup for some items and shipping for others.
• Inventory needs to be reserved while another order is being processed.
• Store A can fulfill an order, but Store B is closer to the customer.
• Customer changes pickup store after ordering.
• Curbside pickup vs. in-store pickup.
• Partial pickup, partial cancellation and substitutions.
• Returns at a different store from the fulfillment location.
• Ship-from-store competing with BOPIS for the same inventory.
• Transfers between stores when the designated pickup store is out of stock.

Those scenarios will reveal much more than a standard BOPIS demo.

If your chain is enterprise-scale and fulfillment complexity is the primary criterion, Salesforce Commerce/Order Management and Adobe Commerce are the two I'd put through the deepest technical evaluation; Shopify Plus is particularly worth evaluating if implementation speed and ecosystem flexibility are major considerations. That's a description of their documented capabilities rather than an overall ranking.

Shopify Plus has become considerably more capable for omnichannel retail. It supports store transfers, custom order-routing rules and, as of 2026, a Shopify Plus/Enterprise capability allowing customers to combine shipped and store-pickup items in one checkout. help.shopify.com shopify.dev changelog.shopify.com However, for unusually complex allocation/orchestration requirements, I'd scrutinize whether Shopify's native model plus apps is sufficient before committing.

Manhattan Active is worth considering when fulfillment complexity itself is a primary requirement. Its store-fulfillment offering combines real-time store inventory, mobile associate workflows and intelligent orchestration.

What I'd test in an RFP

Don't just demo “Buy Online, Pick Up In Store.” Give each vendor scenarios such as: