Answers that name a competitor

Yes. A few platforms now handle both one-time digital downloads and recurring subscriptions/memberships reasonably well:

• gumroad.com — Very straightforward for selling files, ebooks, templates, courses, and recurring memberships. It supports monthly/quarterly/annual billing and multiple membership tiers. Gumroad Gumroad
• podia.com — More of an all-in-one business platform: downloads, subscriptions, courses, community, email marketing, and your website. It supports subscriptions that provide ongoing access to products/community. Podia Podia Help Center
• fourthwall.com — Particularly creator/audience-oriented. It combines digital downloads, memberships, and physical merch in one storefront, with customizable membership tiers. Fourthwall Fourthwall

How I'd distinguish them

For a startup rather than an individual creator, I'd pay particular attention to Podia vs. Gumroad. Podia is more of a complete business platform, while Gumroad is more focused on getting products and memberships sold with relatively little setup. Gumroad also says it acts as merchant of record and handles worldwide sales-tax collection/remittance. Gumroad Gumroad

If you tell me roughly what you're selling (e.g. templates, software, ebooks, courses), your subscription model, and your monthly revenue, I can compare the fees and limitations of 3–5 platforms for your specific setup.

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:

For a subscription-box business, I’d focus less on “can it charge customers monthly?”—most established platforms can—and more on batching orders, controlling fulfillment dates, box customization, failed-payment recovery, and integrations with your 3PL/warehouse.

Strong options

• Shopify + Shopify Subscriptions — simplest starting point if you're already on Shopify. It supports weekly/monthly/yearly auto-billing, skips, pauses, cancellations, customer self-service, and subscription analytics directly in Shopify. Shopify Help Center Shopify

help.shopify.com

• Skio — particularly interesting for a true subscription-box operation. It supports recurring and prepaid subscriptions, Build-a-Box, payment retries, and configurable order days. Its order-day functionality is explicitly designed for subscription boxes and batch fulfillment—for example, processing all monthly boxes on a particular day. Skio Skio Skio

skio.com

• Recharge — worth considering if you expect a larger subscription program with a substantial integration ecosystem. Shopify itself lists Recharge among its major subscription-management options. Shopify
• Appstle — a lower-complexity Shopify option worth evaluating. The Shopify App Store currently specifically describes it as supporting subscriptions, subscription boxes, and bundles, with a free plan available. Shopify App Store

For your particular model

If you're sending a fixed/curated box every month, I'd shortlist Shopify + Skio first. Skio's ability to set common processing days is useful operationally: instead of orders trickling into fulfillment every day, you can establish a cutoff and have the month's boxes generated together. Skio

If customers will choose several items to construct their own box, Skio becomes especially relevant because its selling plans include a Build-a-Box model. Skio

If you're just validating the concept and want the fewest moving parts, Shopify Subscriptions is probably enough to launch and test demand before adding a dedicated subscription platform.

One important distinction: billing software isn't necessarily your fulfillment software. I'd verify that whichever subscription layer you choose integrates cleanly with your actual 3PL/warehouse, inventory system, shipping software, and the way you want monthly boxes assembled.

If you tell me (1) Shopify or another ecommerce platform, (2) fixed box vs. build-your-own, and (3) roughly how many subscribers you expect in year 1, I can narrow this to a practical setup and compare the likely costs.

If your primary goal is minimizing PCI DSS compliance and security work, I’d focus on fully hosted SaaS platforms rather than self-hosted ecommerce software.

What I'd look for

For the smallest compliance scope, structure the store so that your systems never directly receive or store raw card numbers. Use the platform's hosted checkout/payment fields rather than building your own card-entry flow.

Shopify and BigCommerce are both strong fits for that model. Shopify explicitly provides an annually renewed PCI DSS Attestation of Compliance, and its hosted architecture handles infrastructure, checkout, and payment security. Shopify Shopify BigCommerce likewise maintains PCI DSS compliance and provides documentation that merchants can use for their own compliance validation. BigCommerce

One important caveat: "the platform is PCI compliant" doesn't mean the merchant has zero PCI responsibilities. Your obligations depend on how you configure the store, payment flow, integrations, employees, and other systems. For example, adding custom code that handles cardholder data can substantially increase your scope. BigCommerce Shopify

So, if you're choosing specifically around minimum PCI/security overhead, I'd shortlist Shopify and BigCommerce, and avoid self-hosted WooCommerce unless you specifically need its flexibility.

If you tell me your approximate annual order volume, whether you need B2B, and how much customization you need, I can compare Shopify vs. BigCommerce specifically in terms of PCI scope, security responsibilities, and operational burden.

For high-traffic sales events and flash deals, Shopify Plus is a strong choice for spike reliability. Shopify documents specific flash-sale preparation, and a case study reports a merchant handling 1,556 transactions/minute and a 10× traffic increase after moving from Adobe Commerce. Shopify Help Center Shopify

• Shopify Plus: Managed scaling, strong checkout infrastructure; less infrastructure work.
• BigCommerce Enterprise: Also hosted and designed for high-volume traffic; strong alternative. BigCommerce
• Adobe Commerce: Can scale substantially, but peak reliability depends more on hosting, caching, tuning, and engineering. CommerceV3
• Salesforce Commerce Cloud: Enterprise-grade and specifically provides flash-sale traffic-management guidance. Developer

For a DTC brand where sudden traffic spikes are the primary concern, Shopify Plus is particularly worth evaluating.

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.

If you’re non-technical and your main sales engine will be social links + email, I’d narrow it to Shopify and Wix.

My practical comparison

Shopify is particularly strong if you expect social selling to become a major part of the business. Its sales channels connect products with Facebook, Instagram, TikTok, YouTube and other channels, while orders and inventory can be managed centrally. Shopify Help Center Shopify

Wix may feel more approachable if you're starting from scratch. It combines the website/store, social-media management, email campaigns, analytics and even a link-in-bio storefront in one dashboard. wix.com Wix Help Center

I'd probably start with Shopify if your phrase "sell through social links and email" means people will discover products through Instagram/Facebook/TikTok posts and click through to buy. Shopify's social-commerce infrastructure is more deeply centered around that workflow. Shopify

One important distinction: Squarespace is attractive if design is your priority, and it has email campaigns plus Facebook/Instagram integration, but its current Facebook/Instagram product integration is primarily a catalog/ad link back to your site rather than the same kind of native social checkout experience. support.squarespace.com support.squarespace.com

If you tell me what you're selling (physical products, digital products, services, etc.) and roughly how many products, I can narrow this down to the simplest setup for you.

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 brick-and-mortar studio that needs both class bookings and merchandise sales, I’d look first at Square, Wix, and Squarespace.

Square

Square is particularly well suited to your setup. Its class-booking system supports one-time and recurring classes, capacity limits, instructors, online booking, payments, cancellations, and reminders. Square Square

At the same time, Square Online lets you sell physical products with shipping, pickup, or local delivery, and its booking site can combine bookings and product purchases. Square Square

That means you could have, for example:

• Classes: Tuesday Ceramics — 6:00 PM — 8 spots
• Merch: Studio T-shirt — $32
• Checkout: A customer books the class and buys the shirt in the same ecosystem
• Studio: The same Square system handles your in-person sales and inventory

One important consideration: class booking is part of Square's higher-tier/advanced booking capabilities, rather than simply the most basic Square setup. Square Square

Wix

Wix is another good all-in-one option. Wix Bookings supports appointments, classes, and courses, while Wix Stores handles physical merchandise. Wix Help Center Wix Help Center

I'd lean toward Wix if the website/branding experience is as important to you as the operational side.

Squarespace

Squarespace can also do both. Its commerce system supports physical merchandise, while its service products can be used for classes and events; for classes at specific times with limited capacity, Squarespace also points users toward its booking functionality. support.squarespace.com support.squarespace.com support.squarespace.com

For your particular brick-and-mortar use case, I'd investigate Square first, especially if you want your online bookings, merch, inventory, payments, and physical studio checkout connected rather than stitching several systems together.

If you tell me what kind of studio you run (yoga, dance, pottery, fitness, art, etc.) and roughly how many classes/customers you have per week, I can compare the actual plans and costs for Square vs. Wix vs. Squarespace.

For a two-person startup testing product-market fit, I’d optimize for:

1. Launch in days, not weeks
2. Spend <$50/month before you have traction
3. Avoid engineering work
4. Be able to migrate or scale later

My default recommendation: start with Shopify unless your product is extremely simple. It is usually the best tradeoff between speed, reliability, checkout quality, and future flexibility. Shopify Shopify

Shortlist

Shopify WooCommerce## What I would choose by scenario

1. Physical consumer product (most startups)

Pick: Shopify

Examples:

• DTC apparel
• skincare
• gadgets
• food products
• accessories

Why:

• Payments, inventory, shipping, taxes, abandoned carts, and analytics are already handled.
• You can get a credible storefront running quickly.
• You won't need to rebuild after your first few hundred orders. Shopify

Minimal stack:

• Shopify
• Free theme
• Stripe/Shopify Payments
• Klaviyo or Shopify Email
• Google Analytics
• Customer support inbox

Avoid installing 20 apps early. They slow you down and obscure whether customers actually want the product.

2. You have 1–5 products and are mostly testing demand

Pick: Big Cartel or Shopify starter setup

Big Cartel is attractive when the goal is simply:

"Can strangers pay money for this?"

It is intentionally simple and has low upfront cost. Shopify

3. You already have a WordPress site

Pick: WooCommerce

WooCommerce can be inexpensive because the core software is free, but you trade money for maintenance: hosting, updates, plugins, security, and configuration. WooCommerce

For a two-person team trying to learn PMF, I would avoid this unless someone on the team already knows WordPress well.

What I would not do for PMF testing

• ❌ Build a custom storefront
• ❌ Hire a developer for checkout flows
• ❌ Spend weeks perfecting branding
• ❌ Add complex subscriptions/loyalty/referral systems before sales exist
• ❌ Optimize SEO before you know the product resonates

A lean validation setup

You could realistically launch with:

• Storefront: Shopify
• Domain: ~$10–20/year
• Theme: free
• Product photos: phone camera + simple editing
• Email capture: Shopify Email
• Analytics: Google Analytics
• Ads/testing: small daily budget

Your first goal is not a perfect ecommerce machine; it is answering:

• Will people click?
• Will they add to cart?
• Will they pay?
• Will they come back?

If you tell me what you’re selling (physical product, digital product, subscription, marketplace, B2B, etc.) and expected first-month order volume, I can narrow this to a specific stack.

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.

If you're a photographer selling prints + digital downloads + licensing, I’d narrow it to three options:

My recommendation: Pixieset

Pixieset is probably the best fit if you want one inexpensive system for a photography portfolio, galleries, prints and digital sales.

Its free plan includes 3 GB storage, unlimited galleries, an integrated storefront, online payments and automatic fulfillment. The tradeoff is a 15% commission on store sales. The $8/month Basic plan (annual billing) removes the commission and adds 10 GB storage, custom domain support and full-resolution downloads. Pixieset Pixieset

Pixieset specifically supports print products, digital downloads and packages, so you can sell something like:

• $25 — Web-resolution digital image
• $75 — High-resolution personal-use image
• $150 — Print + digital bundle
• $300+ — Commercial/license package

pixieset.com

Pic-Time is an excellent alternative

Pic-Time has a permanent free plan with no monthly fee and includes a print shop, online payments and automatic fulfillment through 30+ print labs. Its free and Beginner plans charge a 15% commission; Beginner is $7/month when billed annually. Pic-Time Pic-Time

It is particularly interesting for photographers because you can create custom digital-download products, packages, volume pricing and different download terms. Pic-Time Help Center Pic-Time Help Center

pic-time.com

Payhip if licensing is a major part of the business

Payhip is less photography-specific, but its economics are attractive for digital products. The free plan is $0/month + 5% transaction fee, with unlimited products and revenue. You could create products such as "Commercial License — Single Image," upload the licensed file, and include your licensing terms with the purchase. Payhip Payhip

payhip.com

For your particular mix, I'd start with Pixieset if prints are important, or Pic-Time if you're especially focused on selling photography through galleries. If licensing becomes a substantial revenue stream, you could use Payhip alongside your photography gallery rather than forcing everything into one platform.

One important distinction: selling a digital image isn't the same as selling a license to use it. I'd set up separate products and clearly specify personal/editorial/commercial usage, permitted media, duration, territory, exclusivity, and whether resale/redistribution is prohibited.

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 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 your priority is self-hosting, owning the database, and keeping migration manageable, I’d shortlist WooCommerce and Medusa.

My practical recommendation

Choose WooCommerce if “manageable migration” is the dominant requirement. Product data lives in your WordPress database, WooCommerce has built-in CSV import/export, and its documentation has migration guides for platforms such as Shopify and Wix. It also gives you control over hosting and infrastructure rather than requiring a SaaS host. WooCommerce WooCommerce WooCommerce

Choose Medusa if “full control + developer flexibility” matters more than minimizing migration work. Its current tooling supports importing products, variants, prices, images, inventory, categories and tags, and its documentation specifically describes migration workflows from platforms including WooCommerce, Shopify, and Magento. The API-based approach can be made repeatable and resumable rather than being a one-off import. Medusa Docs Medusa Docs Medusa Docs

Saleor is another strong option if you're comfortable building a headless storefront. It's open source, API-first/GraphQL-based, and can be run locally without relying on Saleor Cloud. Saleor Commerce Saleor Documentation

The biggest migration question isn't actually the product catalog—it's customers, historical orders, subscriptions, discounts, images, SEO URLs, and integrations. For example, WooCommerce's customer/order importer can map orders to existing customers and products, while Medusa's migration tooling requires more explicit data-model mapping. WooCommerce Medusa Docs

If you tell me what hosted platform you're migrating from (Shopify, BigCommerce, Wix, Squarespace, etc.) and roughly how many products/orders you have, I can compare the migration path specifically for your store.

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 nonprofit selling PDFs, downloadable guides, and training materials, I’d narrow it to three practical options:

My practical recommendation: Payhip

For a very tight budget, I would start with payhip.com.

Its free plan is $0/month + 5% per transaction, with unlimited products and revenue, and it includes the core features rather than putting them behind different tiers. Payment processing fees from Stripe/PayPal are additional. Payhip Payhip

That's particularly attractive for a nonprofit because you don't have to pay for hosting, security updates, ecommerce plugins, or a developer just to get started.

It also supports pay-what-you-want pricing, which could be useful for nonprofit materials—for example, setting a $10 minimum while allowing supporters to contribute more. Payhip Help Center

Payhip also says it can automatically handle EU VAT and UK VAT, which removes another administrative burden if you sell internationally. Payhip

If you want true open source: Easy Digital Downloads

If you already have a WordPress website and are comfortable maintaining it, I'd look at easydigitaldownloads.com.

It's specifically designed around digital products, rather than adapting a physical-product store to PDFs. Its free core is available through WordPress, while more advanced capabilities can require paid extensions. PluginScout Software Advice

This makes more sense if you want:

• Full ownership of your store and customer experience
• Your ecommerce system integrated tightly into your existing nonprofit website
• More control over memberships, recurring payments, licensing, etc.
• The ability to customize things yourself

The downside is that "free/open source" doesn't mean zero cost: you'll still have hosting, payment-processing costs, backups, maintenance, and potentially paid extensions.

What about WooCommerce?

woocommerce.com is also open source and its core platform is free, with no revenue share. WooCommerce

I'd choose it if you expect to sell both digital and physical products, or eventually need a fairly sophisticated ecommerce operation. For a nonprofit whose primary products are PDFs and training downloads, though, it can be more machinery than necessary.

One option I'd put behind Payhip

gumroad.com is extremely easy to use and has no monthly fee, but its current direct-sale fee is 10% + $0.50 per transaction, substantially higher than Payhip's free-plan platform fee. Gumroad also charges 30% for sales originating through its Discover marketplace. Gumroad Gumroad

For a nonprofit operating on thin margins, that difference can become significant.

So my short version: start with Payhip if you want to launch cheaply with almost no technical work; choose Easy Digital Downloads if you already run WordPress and want long-term ownership/control.

If you tell me roughly how many PDFs you sell, your average price, monthly sales, whether you already have WordPress, and whether you need memberships/courses, I can calculate the approximate annual cost of each and show you which setup has the lowest total cost.

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.

For software with frequent releases, look for a software licensing + entitlement platform, not a general ecommerce cart. Strong options:

• Revenera — enterprise-focused; handles licenses, entitlements, download rights, version delivery, and update eligibility. Good for commercial desktop software and complex licensing models. Revenera Revenera
• ChargePanda — built around purchase → entitlement → signed download flows, versioned files, support/update windows, and expiring download links. ChargePanda
• WooCommerce + licensing extensions — flexible if you want to own the storefront; extensions such as Kestrel API Manager add license keys, activations, secure downloads, and update APIs. WooCommerce WooCommerce
• Build-your-own with a payment provider + entitlement service — common for SaaS/dev tools: checkout creates entitlements, your API validates them, and downloads are served through signed URLs or authenticated endpoints.

Minimum architecture to aim for:

1. Order system → creates customer entitlement.
2. License/entitlement API → answers “is this customer allowed version X?”
3. Update manifest endpoint → app checks for new versions.
4. Secure download endpoint → returns short-lived signed URLs or streams files after entitlement validation.
5. Admin tooling → revoke licenses, manage versions, view downloads.

For a small-to-mid software vendor, I’d usually choose a licensing-focused solution rather than trying to make Shopify/WooCommerce alone handle update authorization. For enterprise desktop software, Revenera-style tooling is more typical; for indie apps, a lighter entitlement service is often enough. Revenera

Yes. If your model is “customer pays → gets access to files for 30 days → access expires”, there are a few tools that fit particularly well.

Best fits

• sendowl.com — probably the closest match. It supports time-limited download links, download limits, PDF stamping, and access management. You can sell files directly or connect it to Shopify/Square. SendOwl SendOwl
• sellfy.com — supports subscriptions where downloads are available only during the subscription period. For a monthly rental, a customer paying for one month gets access during that month and the previous download links are deactivated afterward. Sellfy Help Center Sellfy
• Shopify + SendOwl — useful if you want a full storefront/checkout but want SendOwl handling the protected file delivery. Shopify itself has download limits, but its native Digital Downloads app doesn't provide the same kind of time-based expiration for shared links. SendOwl Shopify Help Center
• Handoff Digital Downloads (Shopify) — a newer Shopify option that specifically provides expiring download links, configurable link duration, and download limits. It's currently listed at $9/month with a 14-day trial, although it has very few/no reviews yet. Shopify App Store Shopify App Store

One important distinction

If you mean:

“The customer can download the files, but the download link expires after 30 days.”

Then SendOwl or Handoff are good matches.

If you mean:

“The customer can view/use the files for 30 days, and then they lose access—even if they already downloaded a copy.”

That's different. An expiring download link cannot accomplish that, because once someone downloads a PDF, ZIP, video, etc., you generally can't make that local copy expire. You'd want a gated/streaming access system rather than ordinary file downloads.

If you tell me what type of files you're renting (PDFs, videos, software, templates, etc.) and whether customers are allowed to download them, I can narrow this down to the best 2–3 options and explain exactly how the 30-day rental would work.

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.

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.

Yes. If you already have an ecommerce site and want to add subscription management without rebuilding the store, there are several established options.

Two I'd look at first

Chargebee is probably the closest match if "flexible billing intervals" is a major requirement. It supports recurring billing by days, weeks, and months, plus more sophisticated setups such as multiple billing frequencies within a subscription. It also provides subscription lifecycle management, proration, customer portals, and payment integrations. Chargebee Chargebee

chargebee.com

Stripe is a good alternative if you want the subscription engine integrated directly into your existing application. Stripe supports different recurring intervals and billing-cycle anchors, and its newer flexible billing mode supports subscriptions containing items with different billing periods—for example, an annual component plus a monthly component. Stripe Docs Stripe Docs Stripe Docs

stripe.com

If you tell me what ecommerce platform your existing site uses (Shopify, WooCommerce, custom React/Next.js, Magento, etc.) and what intervals you need (e.g. every 2 weeks, 3 months, 6 months, annual, customer-selected dates), I can narrow this down to the most suitable options and explain how the integration would work.

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

For enterprise merchants where subscriptions + headless APIs are core requirements, I’d shortlist commercetools + Recurly rather than forcing one platform to do everything.

• commercetools — strongest fit for a deeply composable, API-first enterprise architecture; it supports extensive REST/GraphQL commerce APIs and subscription-related capabilities. Elastic Path Reely
• Recurly — purpose-built subscription infrastructure with APIs covering plans, lifecycle, billing, invoices, and customer portals; it also supports fully headless storefronts. recurly.com recurly.com
• BigCommerce Enterprise — worth considering if you want SaaS simplicity with strong headless APIs rather than a highly composable stack. shopify.com vendure.io
• Shopify Plus + Recurly — attractive when operational simplicity and the Shopify ecosystem matter more than maximum backend flexibility.

My architectural pick: commercetools for commerce + Recurly for subscription lifecycle/billing + your preferred CMS/search/frontend.

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

For a wholesaler that needs customizable quote → approval → order workflows, I’d shortlist these hosted options:

My practical shortlist

BigCommerce B2B Edition is probably the first one I'd investigate if you specifically want a hosted/SaaS solution without taking on a large implementation. BigCommerce supports B2B customer accounts, buyer hierarchies, quotes, customer-specific pricing, and approval processes. Its B2B documentation specifically supports creating negotiated quotes that can contain customer-specific discounts and then progressing them through the normal order lifecycle. BigCommerce BigCommerce

bigcommerce.com

OroCommerce is worth a serious look if the quote itself is central to your business. Its workflow engine supports configurable quote flows and approval steps—for example, requiring a manager's approval before a salesperson can send a quote with overridden pricing. It also has workflows for order approvals and credit approval. Oro Documentation ORO INC.

oroinc.com

Shopify Plus makes more sense if you're also operating a substantial DTC business and want the wholesale operation alongside it. Its native B2B capabilities are strong around companies, catalogs, pricing and terms, but sophisticated RFQ and multi-level approval processes generally require apps/custom development rather than being core functionality. Human After All Elogic Commerce

The key distinction

If your flow looks something like:

Buyer requests quote → salesperson modifies pricing → manager approves margin exception → buyer accepts → PO/order created → credit approval → fulfillment

I'd put OroCommerce and BigCommerce B2B Edition at the top of the evaluation. Oro has the deeper workflow model; BigCommerce gives you a more conventional SaaS implementation with a strong wholesale focus. Oro Documentation BigCommerce

If you tell me your approximate order volume, ERP (NetSuite/SAP/Dynamics/etc.), number of approval levels, and whether you also sell DTC, I can narrow this to 2–3 architectures and explain where each would require customization.

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.

Yes. For the requirements you described—migrating an existing wholesale catalog, customer-specific pricing, and keeping/managing open quotes—there are a few platforms worth looking at.

The two I'd investigate first

1. BigCommerce B2B Edition

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

BigCommerce supports customer groups and price lists, including pricing down to individual SKUs for particular wholesale accounts. It also supports importing customer groups via CSV, which can make an existing wholesale-data migration considerably easier. BigCommerce BigCommerce

More importantly, quotes are a native B2B feature. Salespeople can create quotes with negotiated line-item prices, discounts, custom products, special shipping methods, expiration dates, etc. Buyers can request quotes from the storefront and then take an approved quote through checkout. BigCommerce BigCommerce

That makes the workflow something like:

Existing ERP/catalog → BigCommerce → customer accounts → customer-specific price lists → quote → approval → order

rather than having to bolt a quoting system onto a normal ecommerce store.

bigcommerce.com

2. Shopify B2B

Shopify has become much more capable for wholesale.

Its B2B Catalogs let you control both which products a customer can see and the prices they receive. On Shopify Plus, catalogs can be assigned directly to individual companies/company locations, which is useful when Customer A pays $14 for an item while Customer B pays $16. Shopify Help Center Shopify Help Center

Shopify also supports CSV import/export of B2B catalog pricing, which could be useful for migrating a large existing price matrix. Shopify Help Center

For quotes, however, Shopify's native mechanism is more draft-order oriented. You can create a B2B draft order, override a negotiated price, and lock the quoted price so subsequent catalog-price changes don't affect it. Shopify Help Center

There are also dedicated wholesale/quote apps if you need a more traditional RFQ workflow. Shopify App Store

help.shopify.com

Which I'd lean toward depends on your existing data

If your current wholesale system looks something like:

• 5,000–50,000 SKUs
• hundreds/thousands of wholesale customers
• customer-specific SKU pricing
• customers have different product availability
• sales reps maintain quotes
• quotes can remain open for weeks/months
• negotiated prices need to survive catalog price changes
• customers have PO/net terms
• you want to import the existing catalog rather than rebuild it manually

I'd put BigCommerce B2B Edition and Shopify Plus B2B head-to-head, with BigCommerce getting particular attention because quoting is already a first-class B2B feature.

If you tell me what platform/ERP your wholesale catalog is currently in (e.g. Excel/CSV, QuickBooks, NetSuite, SAP, WooCommerce, Magento, custom database, etc.) and roughly how many SKUs + customers + unique price lists you have, I can narrow this down substantially and tell you which migration would be easiest.

BigCommerce supports customer groups and price lists, including pricing down to individual SKUs for particular wholesale accounts. It also supports importing customer groups via CSV, which can make an existing wholesale-data migration considerably easier. BigCommerce BigCommerce

More importantly, quotes are a native B2B feature. Salespeople can create quotes with negotiated line-item prices, discounts, custom products, special shipping methods, expiration dates, etc. Buyers can request quotes from the storefront and then take an approved quote through checkout. BigCommerce BigCommerce

That makes the workflow something like:

Existing ERP/catalog → BigCommerce → customer accounts → customer-specific price lists → quote → approval → order

rather than having to bolt a quoting system onto a normal ecommerce store.

bigcommerce.com

2. Shopify B2B

Shopify has become much more capable for wholesale.

Its B2B Catalogs let you control both which products a customer can see and the prices they receive. On Shopify Plus, catalogs can be assigned directly to individual companies/company locations, which is useful when Customer A pays $14 for an item while Customer B pays $16. help.shopify.com help.shopify.com

Shopify also supports CSV import/export of B2B catalog pricing, which could be useful for migrating a large existing price matrix. help.shopify.com

For quotes, however, Shopify's native mechanism is more draft-order oriented. You can create a B2B draft order, override a negotiated price, and lock the quoted price so subsequent catalog-price changes don't affect it.

There are also dedicated wholesale/quote apps if you need a more traditional RFQ workflow.

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 requirement is one site that sells both physical products and downloadable products without adding a separate plugin/app, the strongest fits are:

My take

Wix is probably the closest match to what you described. Wix explicitly supports physical products and digital downloads in the same store, and says you can sell both without extra platforms or plugins. wix.com Wix Help Center

Squarespace is also a genuine no-plugin option. Its native Commerce system has separate product types for physical goods and downloads; downloads are automatically fulfilled after purchase. Squarespace Help Squarespace Help

Shopify can absolutely handle both, including products combining physical and digital components, but its current documentation says digital delivery uses its free Digital Products app. So it doesn't meet your strict "without plugins" requirement as cleanly. Shopify Shopify Help Center

Bottom line: If avoiding plugins/apps is the priority, I'd narrow it to Wix vs. Squarespace. If you tell me roughly how many physical products vs. downloads you sell and whether you need subscriptions/memberships, I can compare those two specifically.

For a boutique selling made-to-order products with long production times, I’d focus less on generic “backorder” support and more on preorders, deposits/partial payments, promised ship dates, and clear order-status communication.

How the main options compare

Shopify is probably the most straightforward choice for a boutique. Shopify supports preorders, including full or partial payment options, and has a large ecosystem of preorder apps specifically supporting made-to-order products. Shopify Help Center Shopify App Store

For example, its app marketplace currently has apps supporting combinations of preorders, backorders, deposits, waitlists, and restock notifications. Shopify App Store Shopify App Store

One important caveat: Shopify's native preorder functionality requires a preorder app, and there are restrictions around accelerated checkout/payment methods. Shopify also expects merchants to have a reasonable basis for their promised shipping timeframe. Shopify Help Center

BigCommerce is particularly interesting if your definition of “backorder” is literally sell it now even though inventory isn't available. Its September 2026 update added shopper-facing backorder messaging across product pages, cart, checkout, and order confirmation, including quantity and shipping-expectation messaging. BigCommerce

WooCommerce gives you the most flexibility if your workflow is unusual. Its official Pre-Orders extension supports availability dates, launch messaging, flexible charging, and preorders for products that go out of stock. WooCommerce

For your particular business

If, for example, your workflow is:

Customer orders → you collect a deposit → item takes 6–10 weeks to manufacture → you notify customer → collect balance → ship

I'd lean toward Shopify + a preorder/deposit app. It gives you a polished customer experience without having to build the entire workflow yourself.

If instead it's:

Product is technically “out of stock” → keep accepting orders → maintain a controlled queue/backorder quantity → show expected fulfillment date

I'd take a close look at BigCommerce, because its current backorder functionality is unusually relevant to that model. BigCommerce

If you tell me your typical production time (e.g. 4 weeks vs. 4 months), whether you want full payment or deposits, and whether customers can order multiple items with different lead times, I can narrow this down to the best platform/workflow for your boutique.

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.

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

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