Neutral mentions of BigCommerce

For a growing local retailer with limited developer resources, I’d focus less on maximum customization today and more on how much infrastructure you won’t have to build or maintain later.

My shortlist

For your particular situation, Shopify is probably the architecture I'd investigate first. That's not a claim that it's universally "best"; it's because your constraint is limited development capacity. Shopify is managed SaaS, includes hosting and infrastructure, supports online and in-person selling, and has a progression from its lower plans through Shopify Plus as requirements become more complex. Its current plans include unlimited products and bandwidth. Shopify Shopify Help Center

The important part is that you don't need to build your future platform now. You can start with a standard theme and apps, then introduce custom integrations/API work only when the business actually needs them. Shopify currently supports custom apps, headless storefronts, additional staff accounts, international selling, and more advanced checkout/API capabilities on higher tiers. Shopify

When I'd choose BigCommerce instead

I'd look particularly closely at BigCommerce if you expect things like:

• A very large or complicated product catalog
• Multiple storefronts/brands
• B2B pricing and purchasing
• More complex integrations
• A desire to avoid platform transaction fees when using supported payment providers

BigCommerce's current plans explicitly support multiple storefronts and multiple retail/POS integrations, and its higher tiers are designed around substantial sales volumes. BigCommerce

One thing to factor into a 2026 evaluation: BigCommerce changed its pricing structure on June 1, 2026, including fees for some orders processed through "Open Payment Providers" on self-service plans. BigCommerce BigCommerce

When I'd choose WooCommerce

WooCommerce becomes more compelling if your website is already WordPress-centric or you need unusually deep control over the site and data.

It's open source, has a REST API and a large extension ecosystem, and WooCommerce itself says it can scale to very large order volumes. But that flexibility also means you're responsible for more of the hosting, security, performance, plugin and development stack. WooCommerce WooCommerce

What I'd build

For a small retailer, I'd aim for this rather than commissioning a custom ecommerce system:

Shopify → POS/inventory → accounting → email/SMS → shipping → analytics

Keep your product/customer/order data portable, use APIs for anything that becomes strategically important, and avoid putting business-critical logic into obscure theme hacks or one-off apps.

That gives you a relatively simple launch while preserving an upgrade path when you eventually have developers.

If you tell me roughly how many SKUs you have, current annual revenue, whether you already use a POS (Square, Lightspeed, Clover, etc.), and whether you sell B2B, I can narrow this down to a concrete platform + stack and estimated monthly cost.

For an enterprise catalog with thousands of SKUs and complex pricing, I would avoid choosing based on “number of SKUs supported” alone. The harder problems are usually:

• Customer-specific price books and contract pricing
• Tiered/volume pricing
• Multiple catalogs by customer, region, channel, or business unit
• ERP/PIM synchronization
• Configurable products and variants
• Quote workflows and approval flows
• Fast search across a large product universe

Platforms that are often shortlisted for this type of environment include: Elastic Path Shopify

My shortlist by scenario

1. Industrial distributor / manufacturer

• Adobe Commerce
• SAP Commerce Cloud (if SAP is your ERP backbone)
• OroCommerce

2. Thousands of SKUs + customer-specific pricing + ERP-driven business

• SAP Commerce Cloud
• Adobe Commerce
• Elastic Path

3. B2B + direct-to-consumer on the same platform

• Shopify Plus
• BigCommerce Enterprise
• Adobe Commerce

4. You have a strong internal engineering team and want maximum flexibility

• commercetools
• Elastic Path

Questions I would use to narrow it down

1. How many price rules exist?

• 5–20 price lists is very different from 50,000 customer-specific contracts.
• Where is pricing mastered today?

• ERP (SAP, Oracle, Dynamics, NetSuite)?
• CRM?
• Ecommerce platform?
• Do customers see negotiated prices after login?

• If yes, account hierarchy and pricing engines become critical.
• How complex is your catalog?

• 50,000 simple SKUs is often easier than 5,000 configurable products with dependencies.
• Do you need marketplace, punchout procurement, EDI, or CPQ integration?

If you share:

• approximate SKU count (5k / 50k / 500k+)
• B2B only vs B2B+B2C
• ERP (SAP, NetSuite, Dynamics, Oracle, other)
• pricing model (customer contracts, tiers, quotes, regional pricing)

…I can narrow this to a 2–3 platform recommendation.

For a developer building a custom frontend, the “best” headless commerce platform depends mostly on how much of the commerce engine you want to own. The strongest options today fall into a few categories. vendure.ionaturaily.com

ribbsaetersystems.com

My shortlist for a developer-first custom frontend

1. Medusa — probably the best balance of freedom + developer experience

Choose Medusa if you want:

• A Next.js/React frontend
• Full control over checkout, pricing, promotions, fulfillment
• A Node/TypeScript stack end-to-end
• The ability to modify the backend instead of fighting platform constraints

Architecture is closer to “commerce primitives you assemble” than a traditional SaaS store. It’s a strong choice when your product is not a standard Shopify-style catalog. hunchbite.comossalt.com

Typical stack:

Next.js frontend
        |
        |
Medusa API
        |
Postgres + payment/shipping integrations

2. Saleor — best if you love GraphQL

Choose Saleor if:

• Your frontend team prefers GraphQL
• You have complex product models
• You need multi-region, multi-channel, B2B capabilities
• You’re comfortable with Python/Django

Its API model is very clean for frontend developers because the storefront consumes a strongly structured GraphQL API. hunchbite.comossalt.com

3. commercetools — best for enterprise-scale composable commerce

Choose this when:

• You have many systems (ERP, PIM, CMS, loyalty, pricing engines)
• Commerce is one service in a larger architecture
• You have enterprise engineering resources

It gives enormous flexibility but usually requires more architecture work. vendure.ionaturaily.com

4. Shopify headless — best when you want to ship, not build commerce infrastructure

A custom frontend on Shopify gives you:

• Excellent checkout reliability
• Payments, tax, fraud, inventory, admin tooling
• Huge ecosystem

The tradeoff is that your backend customization is constrained by Shopify’s model. vendure.ionaturaily.comwww.askantech.com

If I were choosing for a new custom frontend project:

• Solo developer / small engineering team: Medusa
• GraphQL-first team: Saleor
• Enterprise architecture: commercetools
• Brand wants custom UX but doesn’t want commerce ops headaches: Shopify headless
• Marketplace or unusual checkout flows: Medusa or Saleor

For a modern stack like Next.js + React + TypeScript, I’d start by evaluating Medusa vs Saleor vs Shopify Storefront API. The deciding question is:

“Do I want to customize the commerce engine itself, or only customize the customer experience?”

If you need to rewrite commerce behavior → Medusa/Saleor.
If you mainly need a custom storefront → Shopify headless is often enough. ribbsaetersystems.com

I can also give you a developer-focused comparison of APIs, auth models, webhooks, checkout flows, and Next.js integration patterns if that’s the direction you’re building.

If you’re a developer building a custom frontend and your priorities are maximum flexibility + strong APIs, I’d generally rank the options differently than a business buyer would. The “best” choice depends on whether you want to own the commerce backend or just consume a powerful managed API. Guideflow Vendure

My shortlist for developer-first headless commerce

Naturaily Vendure## My recommendations by scenario

1. You want maximum control → Medusa

I’d look at Medusa first for a developer-built product.

Good if you want:

• Next.js / React storefront
• custom checkout logic
• unusual product models
• marketplace behavior
• your own infrastructure
• full control over backend code

It feels closer to a commerce framework than a traditional ecommerce platform. CozyCommerce

Stack example:

Next.js frontend
        |
        |
Medusa API
        |
Postgres + custom services

2. You love GraphQL → Saleor

Saleor is attractive if your frontend team wants a strongly typed API and excellent data querying.

Strengths:

• GraphQL-native
• clean developer experience
• great fit for React/Next.js
• good for custom storefronts

Tradeoff:

• you’ll likely spend more time adapting the platform to unusual business rules. Guideflow

3. You’re building enterprise-scale → commercetools

commercetools is one of the strongest API-first commerce platforms.

Choose it if you need:

• multiple regions
• complex pricing
• B2B workflows
• multiple storefronts
• composable architecture

Tradeoff:

• expensive
• requires experienced engineering teams
• you assemble more pieces yourself Guideflow

4. You want commerce solved, not built → Shopify headless

Shopify with a custom frontend is a pragmatic choice.

Great for:

• DTC brands
• subscriptions
• payments
• inventory
• apps/integrations
• launching quickly

The downside:

• you don’t own the backend model
• some deeply custom flows become workarounds Shopify

My ranking for a developer building a custom frontend

If I were choosing purely as an engineer:

1. Medusa — best balance of flexibility + developer experience
2. Vendure — excellent if you’re a TypeScript/NestJS shop
3. Saleor — best GraphQL-first option
4. commercetools — best enterprise API architecture
5. Shopify headless — best operational simplicity
6. BigCommerce headless — good middle ground

Naturaily VendureA few questions would change the recommendation:

• Are you building B2C, B2B, marketplace, subscriptions, or something custom?
• Are you using Next.js/React, Vue/Nuxt, mobile apps, or something else?
• Do you want to self-host, or is SaaS acceptable?

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.

Shopify offers the strongest overall supplier ecosystem for a dropshipping business with many supplier integrations. vender.com.br AFCommerce

Ranking for supplier ecosystem:

1. Shopify — Best overall

• Largest app ecosystem for supplier connections and automation. eSellSphere
• Strong integrations with DSers (AliExpress), Spocket (US/EU suppliers), CJdropshipping, Zendrop, print-on-demand suppliers, and private-label providers. Shopify
• Best if you expect to test many suppliers, automate fulfillment, and scale quickly.
• WooCommerce — Best for customization

• More control over supplier workflows and data.
• Good for businesses with developers who need custom APIs, ERP connections, or complex catalogs.
• More maintenance compared with Shopify. Parse
• BigCommerce — Best for larger operations

• Strong native ecommerce features and good multi-channel scaling.
• Usually better once you have volume and want fewer third-party apps. Ecommerce Website Create

For a multi-supplier dropshipping operation, I would typically choose:

• Shopify + supplier apps/APIs → fastest ecosystem growth.
• Shopify + custom middleware (e.g., ERP/order router) → if you have dozens or hundreds of suppliers.
• WooCommerce → if supplier integrations are highly custom and you have technical resources.

The key distinction: the ecommerce platform is only the storefront; your real supplier ecosystem comes from integration layers (APIs, apps, inventory sync, order routing, and fulfillment automation). dropshippingbook.com

For a tight monthly budget, I’d focus on minimizing recurring costs and avoiding a big app/plugin stack. The right choice depends on whether you value simplicity or control.

My shortlist for a constrained budget:

1. WooCommerce + inexpensive managed WordPress hosting

• Best if you already have WordPress skills or someone technical.
• You avoid a platform subscription, but you take on hosting, updates, security, and plugin management. WooCommerce
• Good for: 10–1,000 products, content-heavy sites, businesses that want flexibility.
• Shopify Basic (or equivalent entry plan)

• Best if you need to launch quickly and don’t want to maintain infrastructure.
• The tradeoff is ongoing subscription cost plus possible app costs as you grow. Shopify
• Good for: founders who want to spend time selling rather than maintaining a site.
• Ecwid

• Worth considering if you have a simple catalog and an existing website.
• Can be cheaper than running a full standalone ecommerce stack. Shopify

For a lean “core features only” setup, I’d aim for:

• Hosted platform: Shopify/Ecwid → fewer technical costs
• Self-hosted: WooCommerce → lower software cost, more maintenance
• Avoid initially: paid themes, marketing automation suites, review apps, upsell apps, and complex inventory tools unless they directly increase sales

A few details would change the recommendation:

• Monthly software budget (e.g., under $20, $50, $100)?
• Number of products/SKUs?
• Physical products, digital products, subscriptions, or services?
• Do you already have a website (WordPress, Wix, etc.)?

For a small food subscription-box business, I’d focus less on generic ecommerce features and more on: recurring billing, easy customer self-service, shipping/fulfillment, inventory, failed-payment recovery, and the ability to handle changing box contents.

Here are the main options I’d consider:

1. Shopify — probably the first one I'd investigate

shopify.com is a particularly straightforward starting point. Its free Shopify Subscriptions app supports recurring weekly, monthly, or yearly billing, and customers can pause, skip, cancel, update payment methods, and change shipping information themselves. Shopify Help Center Shopify Help Center

For a food box, you could have something like:

• Monthly Snack Box — $39/month
• Family Box — $59/month
• Premium Box — $79/month
• One-time box — $45

Then later add a specialized subscription app if you need more sophisticated functionality. Shopify itself currently highlights apps such as Recharge and Appstle for more complex subscription models. Shopify

I'd lean this way if you want to launch quickly without having to manage much technology.

2. WooCommerce + WooCommerce Subscriptions

woocommerce.com is worth considering if you already use WordPress or want substantially more control over the store.

WooCommerce Subscriptions supports weekly, monthly, and annual billing, automatic recurring payments through 25+ gateways, failed-payment rebilling, and customer self-service for upgrades, downgrades, suspension and cancellation. WooCommerce

The tradeoff is that you're managing WordPress, WooCommerce, hosting, plugins, updates, etc. The subscription functionality itself is currently a paid extension ($279/year on the official site). WooCommerce

I'd consider it if customization is important enough to justify the extra maintenance.

3. Square

squareup.com is interesting if you're already using Square for POS, payments, or a physical food business.

Square Subscriptions supports recurring weekly, biweekly, monthly, quarterly, semiannual, and annual billing, along with things like trials, pause/resume, checkout links and QR codes. Square

There are some meaningful limitations for a subscription-box model, though—for example, Square currently doesn't support swapping an item on an active subscription, and subscription pickup isn't available as a fulfillment option. Square

I'd favor it when the business is very small and Square is already at the center of your operation.

What I'd choose for a food box

If you're starting from scratch, I'd shortlist:

Shopify → specialized Shopify subscription app → WooCommerce

The key question is actually how your boxes work.

For example, there's a big difference between:

"Every month I charge $40 and send the same type of box."

and:

"Every month I charge $40, customers can choose 3 items from 12, they can skip months, change their box by a cutoff date, and I need to batch all orders for fulfillment every Tuesday."

The second model puts much more emphasis on subscription management and fulfillment workflows.

If you tell me (1) your expected number of subscribers, (2) monthly price, (3) whether customers choose what's in the box, and (4) whether you're already using Stripe/Square/PayPal, I can narrow this down to a practical 2–3 platform setup and estimate the software/payment costs.

For a tiny team selling internationally, I’d pick Shopify—specifically Shopify + Markets + Managed Markets if you're eligible.

Why Shopify is probably the simplest

• Multi-currency: Shopify Markets lets you set markets by country/region and show customers local currencies and pricing from one store. Shopify supports 130+ currencies. Shopify Shopify Help Center
• Taxes/duties: The big advantage is Managed Markets. It uses Global-e as the merchant of record, handling foreign tax registration/remittance, duties, customs, and local compliance for eligible international sales. Shopify Help Center
• One admin: You don't need separate stores for every country. Markets centralizes international settings in one Shopify store. Shopify Help Center
• Good fit for a small team: It's hosted SaaS, so you aren't maintaining servers, plugins, security, or a complicated tax stack. Shopify
• Tax calculation: Shopify Tax handles automatic sales-tax calculations, with a free threshold before per-order fees kick in. Shopify Help Center Shopify Help Center

The important distinction

There are really two levels:

Shopify Markets:
You handle the legal/tax responsibilities yourself in each country. Shopify gives you the tools to calculate/display taxes, currencies, duties, etc. Shopify Help Center

Shopify Managed Markets:
Much closer to "turn on international selling and let someone else deal with the bureaucracy." Global-e becomes the merchant of record and handles foreign tax registration/remittance and customs-related responsibilities. Shopify Help Center

For a tiny team, I'd strongly favor the second option if your products/business qualify.

What I'd choose

So if your priority is "we want to sell worldwide without hiring an ecommerce/tax person", I'd start with Shopify.

If you tell me what you're selling, where your company is based, and your first 3–5 target countries, I can narrow down whether Shopify Managed Markets, BigCommerce, or a merchant-of-record platform like Paddle/Stripe makes the most sense.

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

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

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

For a small team with complex shipping rules + carrier-calculated rates, the strongest options are usually:

How I’d match the platform to your situation

• You need many “if/then” shipping rules (SKU-based rules, regions, exclusions, freight rules, special products):

• Consider WooCommerce or BigCommerce + ShipperHQ. BigCommerce WooCommerce
• You need live carrier quotes but want a small team to operate it easily:

• Shopify + a shipping rules app is often the simplest operational setup. Shopify supports carrier/app-calculated rates and shipping profiles; third-party carrier-calculated shipping may require specific plans or fees. Shopify Help Center Shopify Help Center
• You have unusual fulfillment logic (multiple warehouses, dimensional rules, special handling, mixed carts):

• Look closely at BigCommerce or WooCommerce, where more custom shipping logic is typically exposed. BigCommerce WooCommerce

A few questions would narrow this down:

1. Which carriers do you need (UPS, FedEx, USPS, DHL, freight/LTL, local delivery)?
2. Are your rules mostly based on product/SKU, weight/dimensions, destination, or customer type?
3. Are you starting a new store, or migrating from another platform?

Yes. If customization/configuration is core to your business, I’d choose the ecommerce platform based on how sophisticated your configurator needs to be—not just on general ecommerce features.

My shortlist

1. WooCommerce — my pick for complex customization

WooCommerce is particularly attractive if your products have things like:

• Text personalization
• File uploads
• Color/image swatches
• Multiple option groups
• Conditional options
• Dynamic pricing
• Quantity-dependent pricing
• Different options depending on the selected variant
• "Build your own" products
• Complex rules that determine which choices are available

Its official Product Options tooling supports a large range of fields and pricing rules, and WooCommerce also has Composite Products specifically for products customers assemble from multiple components. woocommerce.com

The big advantage is flexibility. Because WooCommerce is WordPress-based and highly extensible, you can build a configurator that behaves very differently from a normal product page.

I'd choose WooCommerce if your configurator is essentially part of your manufacturing/order-processing system.

2. Shopify — best balance of ease + customization

Shopify itself has product configuration capabilities, but the really interesting part is its ecosystem of configurator apps. Shopify's own 2026 guide specifically highlights product configurators for products with multiple variations/customizations. www.shopify.com

For example, apps can provide:

• Live previews
• Dynamic pricing
• Conditional logic
• File uploads
• Image/logo placement
• Visual product customization
• Multi-step configuration

There are now Shopify apps specifically designed around this kind of workflow. apps.shopify.com

I'd choose Shopify if you want to spend less time maintaining the ecommerce infrastructure and more time running the business.

The tradeoff is that once your configuration logic becomes really unusual, you may end up relying on several apps or custom Shopify development.

3. BigCommerce — worth considering for technical stores

BigCommerce has a fairly robust underlying product-options model, including variants and modifier options. docs.bigcommerce.com

I'd look at it particularly if you have:

• A large catalog
• B2B requirements
• Complex integrations
• Developers on staff
• A need for a more API-driven/custom storefront

It's less of my first recommendation for a small business that simply wants an easy visual product customizer.

4. Adobe Commerce — for serious enterprise customization

If you're selling highly engineered products where configuration involves sophisticated rules, pricing, inventory, manufacturing constraints, ERP integration, etc., Adobe Commerce can make sense.

But it's far more complex and expensive to operate than Shopify or WooCommerce. Shopify's own 2026 comparison describes Adobe Commerce as aimed at large enterprises with in-house technical teams needing deep customization. www.shopify.com

I wouldn't start here unless you have a good reason.

The important question: what kind of "customized" products?

This makes a huge difference.

For example:

Simple customization

T-shirt → choose size → choose color → enter name → upload image

Shopify + a good product-customizer app is probably ideal.

Medium complexity

Furniture → choose model → dimensions → material → color → legs → accessories → some choices change available options → price changes

I'd seriously consider WooCommerce or Shopify + a sophisticated configurator.

Very complex

Product → choose base configuration → dimensions affect price → dimensions affect available components → components affect manufacturing options → customer uploads CAD/artwork → configuration must be validated → exact configuration needs to be sent to production

Now I'd lean strongly toward WooCommerce/custom application architecture, BigCommerce, or an enterprise solution, rather than trying to force everything into basic Shopify product variants.

One particularly important distinction

Don't confuse product variants with product options/configuration.

If you have:

5 colors × 4 sizes × 3 materials × 6 finishes × 4 handles

that's 1,440 combinations.

You don't necessarily want 1,440 Shopify/WooCommerce variants.

A proper configurator can keep these as rules/options and calculate the final configuration dynamically. WooCommerce's documentation explicitly describes this approach as a way to avoid creating huge numbers of product variations. woocommerce.com

My recommendation

If I were choosing for a customized-product business today:

🥇 Shopify — if you want the easiest overall business platform and can use a good configurator app.

🥇 WooCommerce — if the configurator is the heart of the business and you need maximum control over rules, pricing, fields, integrations, and checkout/order data.

🥈 BigCommerce — if you're more technical and/or heading toward a larger B2B/catalog operation.

🥉 Adobe Commerce — only when the complexity/scale justifies enterprise infrastructure.

If you tell me what you sell and what customers can customize (e.g. apparel, signs, jewelry, furniture, printed products, gifts, 3D-printed products, etc.), I can narrow this down to the best 2–3 platforms and the specific configurator apps/plugins I'd use, including pricing and the pros/cons of each.

For an agency managing multiple client stores selling digital products, you’ll want something closer to a multi-tenant commerce platform than a normal ecommerce builder. The key capabilities to look for:

• Separate storefronts per client (custom domain, branding, theme)
• Client accounts with limited permissions
• Agency/admin dashboard across all stores
• Product/catalog isolation
• Client billing or revenue split support
• Digital delivery (files, memberships, subscriptions, license keys)
• API access if you want automation

Here are the strongest options by use case:

My shortlist for your model

1. If you want a SaaS-like agency platform

Use Spree Commerce (or another headless commerce stack).

Architecture:

Agency Admin
    |
    +-- Client A Store
    |       ├── Products
    |       ├── Customers
    |       ├── Orders
    |       └── Branding
    |
    +-- Client B Store
            ├── Products
            ├── Customers
            └── Orders

Spree specifically supports multi-tenant setups where each tenant can have its own storefront, admin panel, API access, catalog, customers, and configuration. Spree Commerce

This is the best fit if you want to eventually sell "storefronts as a service."

2. If clients are non-technical and need logins

Look at agency-focused platforms such as:

• Cartvero — agency workspace model, client-specific shops, client access controls, reusable themes, and white-label admin. Cartvero
• Sendd Market — focused on agencies running branded client marketplaces from one dashboard. Sendd Store

3. If you need fastest launch with proven ecommerce

A common agency stack is:

• Shopify store per client
• Your agency as collaborator/admin
• Digital product apps for delivery
• Custom client reporting layer

Pros:

• Reliable checkout/payments
• Easy client handoff
• Huge ecosystem

Cons:

• Not a true multi-tenant white-label system; you’re managing many stores.

4. If your products are mostly downloads/courses/templates

Consider a headless setup:

• Frontend: Next.js
• Commerce: Stripe + custom backend / Spree
• Storage: S3-compatible storage
• Auth: client/customer accounts
• CMS: Sanity, Contentful, or similar

This gives you "one platform, unlimited client brands."

What I would avoid for your use case

• Basic Wix/Squarespace storefronts — fine for single clients, awkward at agency scale.
• Creator marketplaces — they usually keep their branding and customer relationship.
• One shared store with collections per client — creates messy permissions and ownership issues.

A practical agency stack

For 10–100+ client stores, I’d evaluate:

Option A (low engineering):

• Shopify + agency management process

Option B (best long-term platform):

• Spree Commerce + custom agency dashboard

Option C (middle ground):

• Cartvero / Sendd-style agency commerce platform

The deciding question is: are you trying to manage stores for clients, or are you trying to build a platform where clients sign up and get their own store automatically? Those are very different architectures.

For a small clothing brand, I’d start with Shopify + Hydrogen. It gives you a flexible headless frontend while Shopify handles the commerce backend, payments, inventory, checkout, and much of the infrastructure. hydrogen.shopify.dev Shopify

• Shopify/Hydrogen: Best balance of flexibility + low maintenance.
• BigCommerce: Consider if you need more API openness or complex multi-storefront setups. bigcommerce.com
• Medusa/Saleor: More backend control, but substantially more infrastructure/engineering responsibility.

For your priorities—scale without becoming an infrastructure company—Shopify/Hydrogen is the pragmatic choice.

For an agency building custom frontends for multiple clients, I’d avoid choosing a platform based only on “headless support.” The key question is whether it gives you a repeatable multi-tenant delivery model: one commerce backend strategy, isolated client stores, APIs your frontend team can consume, and operational tooling for non-developers.

Here are the platforms I’d shortlist:

My recommendation by agency model

1. You build 5–50 custom sites/year for different brands
→ Shopify headless is probably the safest default.

Architecture:

Next.js / Remix frontend
        |
Shopify Storefront API
        |
Shopify Admin + apps + integrations

Pros:

• Fast client onboarding
• Merchants already understand Shopify
• Huge app ecosystem
• Lower maintenance burden

Tradeoff:

• Each client is its own Shopify instance; you’re not really operating a multi-tenant SaaS platform.

2. You want “one platform, many client stores”
→ Look at Medusa, Saleor, Spree, or a dedicated multi-tenant commerce backend.

Architecture:

Client Store A ─┐
Client Store B ─┼── Custom Frontend Layer
Client Store C ─┘
                 |
          Multi-tenant Commerce API
                 |
       Catalog / Orders / Customers

This lets your agency build:

• shared frontend components
• tenant-specific branding
• centralized deployments
• reusable integrations
• subscription revenue around hosting/maintenance

3. You serve enterprise clients
→ Consider BigCommerce headless or composable commerce stacks.

Good when clients need:

• multiple regions
• B2B pricing
• ERP integrations
• complex catalogs
• multiple storefront experiences

A stack I’d standardize for a modern frontend agency

Frontend

• Next.js
• React Server Components
• Tailwind/design system
• Vercel or similar hosting

Commerce

• Shopify for standard merchants
• Saleor/Medusa/Spree for platform-style builds

Content

• Contentful, Sanity, or another headless CMS

Search

• Algolia or Elasticsearch/OpenSearch

Payments

• Stripe where possible

If your agency’s goal is “we launch a branded storefront for a new client every month from the same codebase”, I would lean toward a multi-tenant commerce backend (Medusa/Saleor/Spree-style).

If your goal is “we make premium custom storefronts for established brands”, I would standardize on Shopify headless and build your own reusable frontend framework around it.

For an enterprise catalog with thousands of SKUs and complex product models, I’d shortlist commercetools and Elastic Path.

• commercetools — particularly strong for deeply structured catalogs, variants, attributes, localization, and API-driven architectures. Its new Modular Catalog supports up to 10,000 variants per product and exposes variant-level APIs. commercetools commercetools Documentation
• Elastic Path — strong if you need complex B2B pricing, bundles/assemblies, multiple catalogs, and more merchandiser-friendly catalog management alongside headless APIs. Elastic Path Elastic Path
• BigCommerce — has solid headless APIs, but I'd investigate its catalog-model limits carefully for highly complex enterprise product structures. BigCommerce

If your priority is maximum product-model/API flexibility, start with commercetools and Elastic Path.

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d put commercetools at the top of the shortlist.

My shortlist

Why I'd lean commercetools

Its catalog model is unusually suited to complicated enterprise SKUs. You can define Product Types with custom attributes, distinguish product-level from variant-level attributes, make attributes searchable/filterable, and use custom fields for additional domain data. commercetools Documentation commercetools Documentation commercetools Documentation

More importantly for a large catalog, commercetools introduced a Modular Product Catalog in 2026 where variants become first-class resources. That allows a product to have up to 10,000 variants, rather than the 100-variant limit of its classic embedded model. commercetools Documentation commercetools Documentation

Its architecture is also genuinely API-first: commerce capabilities are exposed through independent APIs rather than treating headless as merely a storefront option. commercetools

That's particularly attractive if your catalog looks something like:

Product → configurable attributes → thousands of SKU combinations → regional assortments → customer-specific pricing → inventory/ERP → multiple storefronts/apps/marketplaces

When I'd choose something else

• BigCommerce — I'd choose this if you want headless APIs but want a somewhat more packaged commerce backend. It provides both GraphQL Storefront and REST product APIs. BigCommerce BigCommerce
• Saleor — compelling if your engineering organization wants an API-centric, GraphQL-heavy platform and is comfortable owning more of the architecture.
• Medusa — interesting for a JavaScript/TypeScript-heavy engineering team that wants to customize the commerce domain substantially; its product module supports custom options, variants, bundles/multi-part products, and tiered pricing. Medusa Docs
• Shopify Plus — excellent operationally, but I'd be more cautious if your catalog model itself is the difficult part rather than checkout, merchandising, and ecosystem integration.

Bottom line: if the defining requirement is "thousands of SKUs + complex relationships/attributes + multiple channels + deep API integration", I'd start the evaluation with commercetools, then compare it against BigCommerce and Saleor based on how much customization your engineering team wants to own.

If you tell me roughly how your product model works (variants, bundles/kits, configurable products, regional catalogs, B2B pricing, compatibility relationships, etc.), I can narrow this to 2–3 platforms and show how each would model your catalog.

More importantly for a large catalog, commercetools introduced a Modular Product Catalog in 2026 where variants become first-class resources. That allows a product to have up to 10,000 variants, rather than the 100-variant limit of its classic embedded model. commercetools Documentation commercetools Documentation

Its architecture is also genuinely API-first: commerce capabilities are exposed through independent APIs rather than treating headless as merely a storefront option.

That's particularly attractive if your catalog looks something like:

Product → configurable attributes → thousands of SKU combinations → regional assortments → customer-specific pricing → inventory/ERP → multiple storefronts/apps/marketplaces

When I'd choose something else

If the frontend is a custom mobile app—React Native, Flutter, Swift/Kotlin, etc.—I’d prioritize a commerce platform with a strong, stable API rather than one optimized around a particular web storefront.

My shortlist

🥇 I'd choose Medusa for a custom mobile app

Medusa is particularly attractive when the mobile app is the primary customer experience.

Your architecture can look roughly like:

React Native / Flutter / iOS / Android
                │
                ▼
        Your API / BFF layer
                │
                ▼
            Medusa
       ┌────────┼────────┐
       ▼        ▼        ▼
    Products   Cart    Orders
       │        │        │
       └────────┼────────┘
                ▼
     Payments / Tax / Shipping

The big advantage is that your app isn't tied to a commerce-specific frontend framework. Medusa is a backend commerce engine, so you can build the mobile UX however you want. Its TypeScript/Node architecture is also convenient if your app/backend team already lives in the JavaScript/TypeScript ecosystem. Eryx Innovations Lab OSSAlt

When I'd pick Saleor instead

Choose Saleor if your app needs things like:

• Complex B2B pricing
• Multiple markets/channels
• Multiple warehouses
• Sophisticated product attributes
• GraphQL as the primary API
• A Python/Django backend team

Saleor is particularly strong if you want the mobile app to consume a GraphQL-first commerce API. Vendure OSSAlt

When Shopify makes more sense

I'd pick Shopify if you care more about getting the business operational quickly than owning the commerce backend.

You can absolutely have:

Custom Mobile App
       │
       ▼
Shopify Storefront API
       │
       ▼
Shopify
       │
 ┌─────┼─────┐
 ▼     ▼     ▼
Pay  Orders Inventory

The tradeoff is that you're working within Shopify's commerce model rather than having complete control over the backend. That's often a very good trade for a smaller team because Shopify takes care of a lot of operational complexity. Current 2026 comparisons generally position Shopify as the fastest/lowest-operational-burden choice, while Medusa and Saleor provide considerably more backend ownership. Ribbsaeter Systems Naturaily

My recommendation by situation

• Startup / new product / highly customized app → Medusa
• B2B / complex pricing / multi-region → Saleor
• Large enterprise / composable architecture → commercetools
• Want to launch quickly and minimize backend operations → Shopify
• Mid-market + managed SaaS + API access → BigCommerce

One important architectural recommendation: even with Medusa/Saleor/etc., I'd consider putting a thin BFF (Backend-for-Frontend) between your mobile app and commerce platform. It lets you combine commerce, CMS, search, personalization, loyalty, analytics, etc. into mobile-optimized responses and prevents your app from becoming tightly coupled to the commerce vendor.

If you tell me React Native vs Flutter vs native, expected number of SKUs/orders, B2C vs B2B, and whether you need subscriptions/marketplace/multiple countries, I can narrow this down to the best 1–2 choices and give you a concrete architecture.

The big advantage is that your app isn't tied to a commerce-specific frontend framework. Medusa is a backend commerce engine, so you can build the mobile UX however you want. Its TypeScript/Node architecture is also convenient if your app/backend team already lives in the JavaScript/TypeScript ecosystem.

When I'd pick Saleor instead

If your priority is CMS-first, with commerce exposed through APIs rather than letting the commerce platform dictate the page experience, I’d choose based on how much commerce complexity you need.

My default recommendation: Shopify + a real headless CMS

Use Shopify as the commerce engine and a CMS such as Contentful, Sanity, or Storyblok as the content layer.

Architecture:

CMS
 ├─ Product-page composition
 ├─ Editorial content
 ├─ SEO
 ├─ Landing pages
 └─ Merchandising/content blocks
          │
          ▼
   Next.js / React
          │
     ┌────┴────┐
     ▼         ▼
   CMS API   Shopify
             Storefront API
             ├─ products
             ├─ variants
             ├─ pricing
             ├─ inventory
             ├─ cart
             └─ checkout

Shopify's Storefront API is specifically designed to expose products, collections, carts, search, pricing, etc. to a custom frontend, and it is framework-agnostic—you can use Next.js, Vue, or your own stack. Shopify Shopify

For the frontend, Next.js + Shopify Storefront API + your CMS is probably the most pragmatic choice.

When I'd choose something else

commercetools is particularly compelling if your phrase "CMS-first" really means commerce should be one interchangeable service among many. It is explicitly built around modular APIs and composable commerce. commercetools

Medusa is another strong option if you want the commerce layer to be more developer-controlled; its Store API is REST-based and intended specifically to power custom storefronts. Medusa Docs

One important distinction

I would not make the commerce platform your CMS.

Instead, make the CMS own the product-page experience, while the commerce API owns transactional truth.

For example:

CMS owns:
- Page layout
- Hero
- Product storytelling
- Rich media
- Buying-guide sections
- FAQs
- SEO metadata
- Related editorial content
- Promotional modules

Commerce owns:
- Product ID
- Variants
- Price
- Availability
- Inventory
- Cart
- Discounts
- Checkout
- Orders

Then your product page becomes something like:

CMS:
  "page": {
    "product": "shopify:gid://product/123",
    "blocks": [
      "hero",
      "product_buy_box",
      "story",
      "ingredients",
      "reviews",
      "related_content"
    ]
  }

Commerce API:
  product(123) {
    title
    variants
    price
    availability
    images
  }

That gives your content team control over the page, without duplicating commerce data in the CMS.

If I were starting today

I'd probably go:

Sanity or Contentful → Next.js → Shopify Storefront API → Shopify checkout

and only move to commercetools if you have genuine enterprise/composable requirements that Shopify starts constraining.

Shopify also has Hydrogen if you want its more integrated headless stack; Shopify currently describes Hydrogen/Oxygen as its recommended headless commerce stack. Shopify Shopify

If you tell me B2C vs B2B, approximate SKU count, number of locales, and whether editors need to visually compose product pages, I can narrow this down to 2–3 architectures and explain the tradeoffs.

If your team strongly prefers serverless frontends + Jamstack, I’d shortlist these:

My practical recommendation

1. Shopify Storefront API — probably the easiest fit.

Shopify's Storefront API is framework-agnostic, so your frontend can be built with Next.js, Astro, Gatsby, etc., and deployed independently on serverless/edge infrastructure. Shopify also provides Hydrogen/Oxygen if you want its more integrated serverless approach. Shopify Shopify

This gives you roughly:

Astro / Next.js → Storefront API → Shopify

while Shopify handles catalog, checkout, orders, payments, inventory, etc.

2. BigCommerce — particularly compelling if you want a conventional Jamstack frontend.

BigCommerce explicitly supports headless builds with Next.js, Gatsby, and Nuxt, and exposes REST and GraphQL APIs. Its Catalyst stack is specifically built around Next.js, React Server Components and its GraphQL Storefront API. BigCommerce BigCommerce

Next.js / Astro / Gatsby → GraphQL → BigCommerce

3. Saleor — I'd look closely at this if your developers want an API-native architecture.

Saleor is GraphQL-native and designed so the storefront and commerce backend are completely decoupled. It supports arbitrary frontend/BFF stacks and uses APIs/webhooks rather than requiring platform-specific frontend plugins. Saleor Commerce

4. commercetools — excellent architectural fit, but usually justified by more complex commerce requirements.

It's explicitly API-first/headless and designed around composable commerce, so it works very naturally with independently deployed frontend applications. commercetools

5. Medusa — attractive if "serverless frontend" is more important than having a fully managed commerce backend. It's open source and highly customizable, but you're taking on substantially more infrastructure responsibility than with Shopify or BigCommerce. Vendure

How I'd choose

• Want the least operational work: Shopify
• Want SaaS + strong headless/Jamstack support: BigCommerce
• Want GraphQL/open architecture: Saleor
• Want maximum composability at enterprise scale: commercetools
• Want open-source/custom commerce logic: Medusa

One important distinction: Jamstack doesn't require the commerce backend itself to be serverless. Your storefront can be statically generated/edge-rendered and call commerce APIs for dynamic operations such as cart and checkout. That's generally the architecture I'd recommend rather than trying to make the entire commerce system serverless.

If you tell me your frontend framework (Next.js, Astro, Gatsby, etc.), approximate SKU/order volume, B2B vs B2C, and whether you need custom checkout, I can narrow this to 2–3 architectures and show what the stack would look like.

This gives you roughly:

Astro / Next.js → Storefront API → Shopify

while Shopify handles catalog, checkout, orders, payments, inventory, etc.

2. BigCommerce — particularly compelling if you want a conventional Jamstack frontend.

BigCommerce explicitly supports headless builds with Next.js, Gatsby, and Nuxt, and exposes REST and GraphQL APIs. Its Catalyst stack is specifically built around Next.js, React Server Components and its GraphQL Storefront API. bigcommerce.com docs.bigcommerce.com

Next.js / Astro / Gatsby → GraphQL → BigCommerce

3. Saleor — I'd look closely at this if your developers want an API-native architecture.

Saleor is GraphQL-native and designed so the storefront and commerce backend are completely decoupled. It supports arbitrary frontend/BFF stacks and uses APIs/webhooks rather than requiring platform-specific frontend plugins.

4. commercetools — excellent architectural fit, but usually justified by more complex commerce requirements.

It's explicitly API-first/headless and designed around composable commerce, so it works very naturally with independently deployed frontend applications.

5. Medusa — attractive if "serverless frontend" is more important than having a fully managed commerce backend. It's open source and highly customizable, but you're taking on substantially more infrastructure responsibility than with Shopify or BigCommerce.

How I'd choose

For a B2B wholesaler with customer-specific pricing, contract catalogs, account hierarchies, ERP integrations, and headless APIs, you’ll generally want an enterprise B2B commerce platform rather than a standard ecommerce store. The strongest options are: Shopify Atwix

My shortlist based on your description

If you are a true wholesaler/distributor (thousands of SKUs, negotiated pricing, dealer accounts, sales reps, purchase orders):

1. OroCommerce — probably the closest functional match for wholesale-first needs. ORO INC.
2. commercetools — best if your team wants a fully headless, API-driven architecture and has developers. Naturaily
3. Adobe Commerce — best if you need maximum customization and have implementation resources. Shopify
4. BigCommerce B2B Edition — best balance of SaaS simplicity and B2B capability. KIBO Commerce

Features I would verify during vendor evaluation

For a complex wholesaler, make sure the platform supports:

• Customer/account-specific price books
• Contract pricing and negotiated discounts
• Multiple catalogs by customer segment
• Tier pricing by quantity
• Quote → approval → order workflows
• Buyer roles and company hierarchies
• Net payment terms / purchase orders
• ERP sync (SAP, NetSuite, Dynamics, Infor, etc.)
• Real-time inventory and availability APIs
• Headless storefront APIs (GraphQL/REST)
• Punchout procurement integrations (OCI/cXML)
• Multi-brand or multi-region catalogs

A key question is where your pricing logic currently lives: ERP, CRM, a pricing engine, or spreadsheets. That often determines whether you want a commerce platform with strong native pricing (Oro/Adobe/SAP) or an API-first platform where pricing stays in your own services (commercetools). ORO INC. Naturaily

If you share your ERP (NetSuite/SAP/Dynamics/etc.), SKU count, number of customer accounts, and whether you need a custom frontend, I can narrow this to 2–3 realistic choices.

For a subscription box business, the “right” headless commerce platform depends heavily on how complex your subscription logic is (fixed monthly box vs. build-your-own box, swaps, skips, pauses, prepaid plans, gifting, etc.). The main thing to verify is subscription lifecycle APIs, not just “recurring payments.”

Here are the platforms I’d shortlist:

Shopify Shopify## My practical recommendations

Choose Shopify if:

• You sell a fairly standard recurring box:

• monthly/quarterly plans
• customer portal
• pause/skip/cancel
• discount codes
• bundles
• You want the fastest path to revenue.
• Your team wants strong admin tools.

Shopify’s headless Storefront API supports subscription products through selling plans, allowing custom frontends to retrieve subscription options and create carts containing subscription items. Shopify

Typical stack:

• Frontend: Next.js
• Commerce: Shopify
• Subscription engine: Shopify-compatible subscription app or custom app
• Payments: Shopify Payments/Shopify checkout

Choose BigCommerce if:

• Your subscription logic is more custom.
• You want fewer marketplace dependencies.
• You expect B2B, wholesale, multiple storefronts, or complex catalog needs.

BigCommerce provides headless storefront capabilities through APIs and GraphQL, including custom storefront flows for catalog, carts, checkout, and customer experiences. BigCommerce BigCommerce

Typical stack:

• Frontend: Next.js/React
• Commerce backend: BigCommerce
• Subscription service: custom service or subscription provider
• Fulfillment: 3PL integration

Choose commercetools if:

Your subscription box is becoming a platform rather than just a store:

• personalized boxes
• complex pricing rules
• multiple countries/currencies
• marketplace model
• custom loyalty engine

The tradeoff is that you are assembling more pieces yourself.

Subscription-specific features I would evaluate

Before committing, test these APIs:

Customer lifecycle

Can customers:

• change their next shipment date?
• skip a box?
• pause indefinitely?
• swap products?
• upgrade/downgrade plans?

Billing

Can you handle:

• failed payment retries?
• card updates?
• prorations?
• prepaid subscriptions?
• gift subscriptions?

Box generation

Can your system create:

• recurring orders automatically?
• personalized box contents?
• inventory reservations?

Fulfillment

Can it trigger:

• pick/pack workflows?
• warehouse exports?
• shipping label creation?

My default shortlist for a subscription box startup

1. Shopify headless — if you want to move quickly and your subscription model is conventional.
2. BigCommerce headless — if you expect more customization and want commerce APIs as a core capability.
3. Medusa/commercetools — if you have engineers and your subscription logic is your competitive advantage.

If you tell me:

• your monthly order volume,
• whether boxes are fixed or customizable,
• whether you need a mobile app,
• and your current stack (Shopify/WooCommerce/custom/etc.),

I can narrow this to 1–2 choices.

For a subscription box business, I’d narrow the field to Medusa, Shopify, commercetools, and BigCommerce, but my default recommendation would be Medusa + Stripe Billing if you have a development team and want the subscription experience to be deeply customizable.

The key distinction is that “supports subscriptions via API” can mean either native recurring-subscription commerce or simply an API that you can integrate with a subscription billing provider.

My shortlist

1. Medusa — my pick for a custom subscription-box business

medusajs.com is particularly interesting because it's built to be customized rather than forcing your subscription model into a predefined SaaS workflow.

Its current documentation explicitly shows how to build subscription purchases, including:

• subscription intervals
• automatic renewals
• expiration
• customer cancellation
• subscription/customer API endpoints
• recurring payment capture
• linking subscriptions to orders/products

Medusa itself says subscriptions aren't a native core feature—you implement them through its customization framework or use Stripe subscriptions—but it provides the API routes, workflows, modules and payment infrastructure needed to do it. Medusa Docs Medusa Docs

That's actually a feature rather than a bug for a subscription box company if your business logic is unusual.

For example, you could model:

Customer
   ↓
Subscription
   ├── Plan
   │    ├── Monthly
   │    ├── 3-month prepaid
   │    └── Annual
   │
   ├── Box configuration
   │    ├── Size
   │    ├── Preferences
   │    └── Add-ons
   │
   ├── Billing schedule
   ├── Next shipment
   └── Orders

Then expose exactly the API your frontend/mobile app needs.

Medusa's Store API is REST-based and designed specifically to power custom storefronts and commerce applications. Medusa Docs

I'd choose this if: your subscription is core to the business and you expect things like skips, swaps, add-ons, prepaid plans, customized boxes, pauses, different fulfillment schedules, etc.

2. Shopify — best if you want less engineering

shopify.com is probably the safer choice if your priority is getting the business running rather than owning the commerce infrastructure.

You can build a completely custom frontend while keeping Shopify for products, customers, orders, payments and operational tooling.

The big advantage for subscription boxes is the ecosystem: you can use established subscription infrastructure rather than implementing renewal logic yourself.

I'd choose Shopify if:

• you want to launch quickly
• you don't have a large engineering team
• subscription behavior is relatively conventional
• you want lots of integrations
• your operations team wants a mature admin experience

The downside is that you're working within Shopify's architecture and subscription ecosystem rather than designing the entire subscription domain yourself.

3. commercetools — if you're already an enterprise

commercetools.com is the option I'd investigate for a large subscription-box operation with multiple markets, currencies, brands, channels, fulfillment systems, etc.

It's extremely API/composable-oriented, but it's also considerably more infrastructure and architecture than most subscription-box businesses need.

One important clarification: commercetools' API documentation uses the word “Subscriptions” for its event/notification mechanism. Those are notifications sent to message queues—they aren't customer recurring subscriptions. commercetools Docs

So you'd still need to architect the actual recurring billing/subscription domain.

4. Saleor — compelling if you're engineering-heavy

saleor.io is another strong headless option. It's GraphQL-first and has a very expressive API/webhook architecture. Saleor Commerce

But like Medusa, recurring subscriptions aren't really a turnkey core commerce feature. You'd be building more of that layer yourself.

I'd favor Saleor over Medusa if your team strongly prefers Python/GraphQL and you need sophisticated multi-channel/multi-warehouse commerce.

What I'd actually build

For a new subscription-box company, my architecture would probably be:

Next.js / custom frontend
↓
Medusa — products, carts, customers, orders, inventory
↓
Stripe Billing — recurring payment/subscription lifecycle
↓
Your subscription service/module — box schedule, skips, swaps, preferences, renewal logic
↓
3PL / fulfillment system

That gives you a clean separation:

• Medusa: commerce
• Stripe: money
• Your application: subscription-box business rules
• 3PL: physical fulfillment

Medusa's own subscription recipe demonstrates both a custom subscription approach and a Stripe-based approach, including storing payment information so future renewals can capture payment. Medusa Docs

One important question

Before I would choose the platform, I'd want to know how sophisticated your subscription model is.

If you tell me:

1. Monthly/quarterly/etc.
2. Whether customers can skip/pause
3. Whether they can swap items
4. Whether boxes are curated or customer-selected
5. Whether you need prepaid 3/6/12-month plans
6. Approximate number of subscribers
7. Whether you already use Stripe/Shopify/etc.
8. Whether you have an engineering team

…I can give you a much more concrete Medusa vs Shopify vs commercetools recommendation, including the API/subscription architecture I'd use for your business.

So you'd still need to architect the actual recurring billing/subscription domain.

4. Saleor — compelling if you're engineering-heavy

saleor.io is another strong headless option. It's GraphQL-first and has a very expressive API/webhook architecture. saleor.io

But like Medusa, recurring subscriptions aren't really a turnkey core commerce feature. You'd be building more of that layer yourself.

I'd favor Saleor over Medusa if your team strongly prefers Python/GraphQL and you need sophisticated multi-channel/multi-warehouse commerce.

What I'd actually build

For a new subscription-box company, my architecture would probably be:

Next.js / custom frontend
↓
Medusa — products, carts, customers, orders, inventory
↓
Stripe Billing — recurring payment/subscription lifecycle
↓
Your subscription service/module — box schedule, skips, swaps, preferences, renewal logic
↓
3PL / fulfillment system

That gives you a clean separation:

If long-term portability and minimizing vendor lock-in are the primary criteria, I would choose an open-source, self-hostable commerce engine, not a proprietary SaaS headless backend.

My ranking

Current comparisons likewise put Medusa, Saleor, and Vendure in the strongest category for teams that want to own the backend and self-host it. Vendure ShipGarden

My default choice: Medusa

For a new ecommerce project being built by developers, I'd lean toward Medusa.

The key reason isn't that it has the most features. It's that its architecture gives you a relatively clean escape hatch:

• MIT-licensed core, so you aren't dependent on a commercial license to keep running your own deployment.
• TypeScript/Node.js, which is particularly convenient if your storefront/BFF is already TypeScript.
• Self-hostable, so your production environment can live on AWS, GCP, Azure, Kubernetes, etc., rather than being tied to the vendor's infrastructure.
• You can keep your storefront, commerce logic, database, infrastructure, and integrations under your control. Vendure Build with Matija

That makes the architecture roughly:

                 ┌───────────────┐
                 │   Next.js     │
                 │   storefront  │
                 └───────┬───────┘
                         │
                    Commerce API
                         │
                 ┌───────▼───────┐
                 │    Medusa     │
                 │ self-hosted   │
                 └───────┬───────┘
                         │
          ┌──────────────┼──────────────┐
          ▼              ▼              ▼
       Postgres        Redis       Object storage

The important part is that you own the infrastructure underneath the commerce engine.

But Saleor has an important advantage

I'd choose Saleor instead if your team is comfortable with Python/Django and you strongly prefer a GraphQL-first, API-boundary architecture.

Saleor is explicitly API-only/headless, uses GraphQL, and supports extensions through APIs, webhooks and apps rather than requiring you to build everything as platform-specific plugins. It can also be run locally/self-hosted from its open-source code. Saleor Saleor

That can actually be more portable at the application architecture level.

For example:

                  Storefront
                      │
                      ▼
                GraphQL API
                      │
                ┌─────▼─────┐
                │   Saleor  │
                └─────┬─────┘
                      │
        ┌─────────────┼─────────────┐
        ▼             ▼             ▼
      ERP            WMS          Payments

Your business integrations remain outside the commerce core. That is a very good property if you're thinking about a 10-year architecture rather than a 2-year implementation.

Why I wouldn't automatically choose Vendure

Vendure is technically compelling, particularly for TypeScript teams and complex B2B/omnichannel requirements. Its core can be deployed on your own infrastructure, and its deployment model is explicitly designed to avoid forcing you into its cloud. Vendure

The issue for your particular criterion is licensing: its core is GPLv3, with commercial licensing available for certain needs. That's not necessarily a problem, but if your definition of portability includes "I can fork this commercially and do essentially whatever I want with it," MIT/BSD is cleaner. Vendure ShipGarden

The bigger decision: architecture beats platform

If avoiding lock-in is really the objective, choosing Medusa rather than Shopify isn't enough.

I'd establish these rules from day one:

1. Own the canonical product/order/customer data.

• PostgreSQL or another portable database.
• Regular full exports.
• Don't make the vendor's API your only copy of critical business data.
• Keep payments behind an abstraction.

• Don't spread Stripe/Adyen/etc. implementation details throughout your domain code.
• Keep search replaceable.

• Treat Algolia/Elastic/Meilisearch/etc. as infrastructure, not your commerce domain.
• Keep CMS separate from commerce.

• Your product catalog shouldn't become inseparable from your CMS.
• Use your own domain model where it matters.

• Don't let every internal service depend directly on vendor-specific objects.
• Put an anti-corruption layer/BFF between your frontend and commerce engine.

• Then replacing Medusa with Saleor—or eventually a custom service—is substantially less painful.
• Prefer standard infrastructure.

• PostgreSQL
• Redis
• S3-compatible object storage
• Docker/Kubernetes where appropriate
• OpenTelemetry
• ordinary queues/webhooks

The goal isn't "never depend on anything." That's impossible.

The goal is:

Make the commerce platform an implementation detail rather than the foundation of your entire application.

Bottom line

For a TypeScript ecommerce developer: choose Medusa.

For a Python/GraphQL-oriented team: choose Saleor.

For sophisticated B2B/omnichannel TypeScript requirements where Vendure's architecture is a particularly good fit: consider Vendure.

I would not choose Shopify, commercetools, BigCommerce, etc. if maximum backend portability is the overriding requirement. Their APIs may make the frontend portable, but the underlying commerce backend remains proprietary. Vendure

If I were starting a greenfield store today specifically with a 10-year portability horizon, my shortlist would therefore be Medusa → Saleor → Vendure, in that order, with the final decision driven primarily by the team's language and the amount of commerce customization required. Vendure Saleor

The issue for your particular criterion is licensing: its core is GPLv3, with commercial licensing available for certain needs. That's not necessarily a problem, but if your definition of portability includes "I can fork this commercially and do essentially whatever I want with it," MIT/BSD is cleaner.

The bigger decision: architecture beats platform

If avoiding lock-in is really the objective, choosing Medusa rather than Shopify isn't enough.

I'd establish these rules from day one:

For a custom dropshipping site where API-driven integrations are the priority, I’d lean toward Medusa.

Why Medusa fits

Medusa is particularly well suited when you expect to build your own supplier, inventory, fulfillment, pricing, and automation logic rather than simply put a custom frontend on top of an existing commerce platform.

• API-first: Medusa exposes Store and Admin REST APIs, plus a JS SDK and OpenAPI specs. Medusa Docs Medusa Docs
• Highly customizable: You can create your own modules, workflows, data models, and API routes inside the commerce backend. Medusa Docs Medusa Docs
• Good for supplier integrations: Its module/workflow architecture is designed for integrating third-party systems and orchestrating operations across them. Medusa Docs Medusa Docs
• Dropshipping/marketplace-friendly: Medusa explicitly documents marketplace architectures involving vendors, vendor-specific products, and splitting orders across vendors. Medusa Docs
• You control the stack: PostgreSQL, Node/TypeScript, your frontend, integrations, and deployment can all be customized rather than fitting everything into a SaaS platform's constraints. Medusa Docs

How I'd compare the main choices

Shopify + Hydrogen is compelling if you want to outsource more of the commerce infrastructure. Hydrogen provides Shopify-specific API clients and an optimized React Router stack, while Shopify's Storefront API exposes products, carts, checkout, and other commerce functionality through GraphQL. Shopify Shopify Shopify

For your specific architecture, I'd probably use:

Next.js/React storefront → Medusa API → PostgreSQL

with integrations such as:

Supplier APIs → custom Medusa modules/workflows → inventory/products

and

Order → supplier routing → fulfillment API → tracking → customer

That gives you a clean place to implement things like supplier failover, product syncing, dynamic margins, inventory reconciliation, automated order routing, and multi-supplier fulfillment without fighting the platform.

If your goal is "I want to build the commerce engine itself around supplier APIs", Medusa is the direction I'd investigate first. If your goal is "I want a custom frontend but don't want to operate much commerce infrastructure," Shopify becomes more attractive.

For your specific mix—digital guides + dropshipped physical books—I’d rank the main store builders:

1. Shopify — Best overall
2. WooCommerce — Best for maximum control
3. BigCommerce — Strong, but probably overkill

🥇 Shopify — my recommendation

Shopify is particularly well suited to this model because you can have both product types in the same catalog and checkout.

For your digital guides, Shopify's free Digital Products app can deliver PDFs, ebooks, and other files automatically after purchase. It can also attach digital files to physical products if you eventually want to sell a physical book with a digital companion. Shopify Help Center Shopify App Store

For your physical books, Shopify has a large ecosystem of dropshipping/supplier apps. Shopify itself recommends apps such as Shopify Collective, DropCommerce, Syncee, Gelato, and Printful for sourcing and fulfillment. Shopify Help Center

That gives you a pretty clean setup:

Customer → Your Shopify store →

• Digital guide → instant download
• Physical book → supplier receives order → supplier ships book

You can also sell bundles, e.g.:

"Complete Guide + Paperback Book — $39"

That's where Shopify becomes particularly attractive for what you're describing.

shopify.com

🥈 WooCommerce — best if you want control

WooCommerce is arguably more flexible technically. It natively supports physical and downloadable products, and you can configure downloadable products so customers receive their digital content immediately without waiting for a physical order to finish processing. WooCommerce WooCommerce

It also has a dropshipping extension that can group orders by supplier and automatically notify dropshippers. WooCommerce

The downside is that you'll be managing WordPress, hosting, plugins, updates, security, etc. So it's more customizable but generally more hands-on.

woocommerce.com

🥉 BigCommerce

BigCommerce explicitly distinguishes physical and digital products in its catalog, so it can handle the combination. BigCommerce

I'd consider it if you're expecting a substantially larger operation, but for a new business selling guides plus books, I don't see a compelling reason to choose it over Shopify.

bigcommerce.com

What I'd do in your position

Start with Shopify.

Your stack could look roughly like:

The important thing is that you don't need two stores. Your guide and physical book can live in the same storefront and checkout.

One thing I'd investigate carefully before choosing a book supplier is whether you mean ordinary third-party books (e.g. existing publishers' books) or books you/your suppliers print on demand. The best fulfillment setup is quite different between those two.

If you tell me what kind of physical books you want to dropship (your own books/POD, used books, Amazon-type new books, niche publisher books, etc.), I can recommend the specific Shopify/WooCommerce setup and suppliers I'd use.

For a high-volume dropshipping business with multiple warehouses/3PLs, I’d generally structure the stack as:

Shopify (or another storefront) + Cin7 Core as the inventory/order-management layer.

How I’d compare the main options

My pick for your situation: Cin7 Core

Cin7 Core is specifically designed to act as the centralized inventory/order layer. It supports multiple warehouse locations, inventory transfers, purchase orders, order management, and integrations with platforms such as Shopify, Amazon, WooCommerce, BigCommerce, eBay and Walmart. Cin7 Core Cin7 Core

Its multi-warehouse functionality is particularly relevant: Cin7 describes centralized visibility across warehouses and 3PLs, automatic inventory updates, transfers between locations, and routing orders toward appropriate fulfillment locations. Cin7

It also supports substantial order volumes: its current Core plans list up to 120,000 sales orders/year on Advanced, with additional order volume available, while inventory locations are listed as unlimited. Cin7

Where Shopify fits

Shopify is excellent as the customer-facing ecommerce platform, and its native location system can track inventory separately across warehouses, dropshippers and fulfillment services. Shopify can also route orders based on inventory availability and proximity. Shopify Help Center Shopify Help Center

But once you have many SKUs + several warehouses/3PLs + multiple sales channels + high order volume, I'd avoid making Shopify your only inventory-management system. I'd let Shopify handle the storefront/customer experience and have a dedicated inventory/order-management system serve as the operational source of truth.

A scalable architecture

Shopify stores
Amazon
eBay
Walmart
Other sales channels
        ↓
     Cin7 Core
        ↓
 ┌──────┼────────┐
 ↓      ↓        ↓
WH #1  WH #2    3PLs
        ↓
   Shipping systems

This becomes especially valuable if you're doing something like 10,000+ orders/month, hundreds/thousands of SKUs, multiple suppliers, and geographically distributed fulfillment.

If you tell me roughly monthly orders, number of SKUs, number of warehouses/3PLs, and sales channels (Shopify/Amazon/eBay/Walmart/etc.), I can compare Cin7 vs Linnworks vs Shopify vs BigCommerce specifically for your scale, including likely architecture and where each one starts becoming a bottleneck.

For a solo founder selling low-margin dropship products, the answer is usually not Shopify unless the convenience saves you enough time to justify the extra cost. Your priority should be minimizing:

1. monthly platform fees
2. payment processing fees
3. app/plugin costs
4. marketplace commissions
5. operational overhead (your time has a cost)

Here’s the practical ranking:

Shopify WooCommerce## My recommendation for your situation

1. Cheapest: WooCommerce + low-cost hosting

If your margins are thin (say 10–25%), this is usually the winner.

Pros:

• No monthly ecommerce platform fee
• No revenue share
• Full control
• Many dropshipping integrations exist
• You can optimize costs as you grow

Cons:

• More setup
• You manage hosting, updates, security, plugins

WooCommerce itself is free and does not charge a platform revenue share; your main costs are hosting, extensions, and payment processing. WooCommerce

A lean setup might look like:

• Hosting: ~$5–20/month
• WooCommerce: $0
• Payment processing: typically around standard card rates (varies by provider)
• Essential plugins only

2. Best "time vs money" choice: Shopify

If you're spending more time fixing tech than finding products and ads, Shopify can make sense.

Pros:

• Fastest launch
• Great dropshipping ecosystem
• Less maintenance
• Reliable checkout

Cons:

• Monthly subscription
• Apps can quietly add $50–200+/month
• Third-party payment gateways may add extra fees depending on plan/payment setup

Shopify Stack Compare### 3. Avoid marketplaces for generic dropship products

Platforms like Etsy can look cheap because there is no monthly subscription, but marketplace fees can consume a large percentage of low-margin products. They work better when you have unique products, personalization, or organic marketplace demand. Memvers

Simple decision rule

• Making < $5k/month revenue: WooCommerce if you are comfortable with tech; Shopify if you value speed.
• $5k–50k/month: Shopify often wins because your time becomes more valuable.
• Very low margins (<20%): Avoid paying for lots of apps; WooCommerce usually has the edge.
• Testing many products quickly: Shopify is often easier because dropshipping tools are more mature.

For a solo founder with commodity dropship products and thin margins, I would start with WooCommerce + minimal plugins, then move to Shopify only when operational complexity—not cost—is the bottleneck.

For a dropshipping niche blog → store strategy, I’d generally choose Shopify—not because its raw SEO is necessarily superior to every competitor, but because it gives you a strong combination of blogging, ecommerce, technical SEO, conversion infrastructure, and relatively low maintenance.

How I’d compare the main options

Shopify: probably the best balance

Shopify has a native blogging system, lets you edit SEO titles, descriptions and URLs, automatically generates things such as sitemap.xml, robots.txt, and canonical tags, and gives you control over SEO for products, collections, pages and blog posts. Shopify Help Center Shopify Help Center

That makes this architecture straightforward:

Domain → topical blog → informational articles → comparison/buying guides → collections → products

For example, imagine your niche is ergonomic desk accessories:

• /blog/best-desk-setup-for-back-pain
• /blog/monitor-height-guide
• /blog/standing-desk-vs-sitting-desk
• /blog/best-desk-accessories-for-small-spaces
• /collections/ergonomic-desk-accessories
• /products/ergonomic-foot-rest

The important part is that the blog isn't a separate SEO property. It can build topical relevance and internal links toward the commercial pages on the same domain.

Shopify itself recommends mapping informational/question-based queries to blog content and broader commercial/category terms to collection pages. Shopify

Where WordPress + WooCommerce can beat Shopify

If your strategy is 70–80% content/SEO and 20–30% ecommerce, I'd seriously consider WordPress + WooCommerce.

WordPress gives you considerably more control over the publishing environment, information architecture, content templates, internal linking, taxonomies, schema implementations, and SEO tooling.

That's useful if you intend to build something closer to:

"authority publication that happens to sell products"

rather than:

"store that has a large blog."

The tradeoff is operational complexity: hosting, updates, plugins, security, performance and technical SEO become much more your responsibility.

The distinction I'd make

Choose Shopify if:

• You're actually going to dropship products.
• You want to launch quickly.
• You want the store and content on one domain.
• You don't want to spend much time maintaining WordPress.
• Your blog is an important acquisition channel but isn't the entire business.

Choose WooCommerce/WordPress if:

• Organic search is your primary acquisition strategy.
• You're planning hundreds/thousands of genuinely useful articles.
• You want maximum control over content architecture.
• You're comfortable managing a more technical stack.
• You may eventually turn the site into a large niche publication/affiliate + ecommerce property.

BigCommerce is also a legitimate option; its current SEO guidance emphasizes metadata control, customizable URLs, content optimization, indexation controls, rich content and optimized landing pages. BigCommerce

For your specific strategy

I'd lean Shopify + serious content architecture, rather than trying to find an ecommerce platform with a theoretical SEO advantage.

The bigger SEO opportunity is how you structure the site, not whether the platform is Shopify vs. WooCommerce.

A good funnel would be:

Informational search
→ educational article
→ related comparison/buying guide
→ collection/category
→ product
→ email capture
→ sale

For example:

"how to choose a camping pillow"
↓
"best camping pillows for side sleepers"
↓
/collections/camping-pillows
↓
specific products

That approach gives you multiple search-intent entry points rather than expecting product pages alone to rank. Shopify's own SEO guidance similarly emphasizes matching pages to search intent and creating original content rather than relying on manufacturer descriptions. Shopify

Bottom line: If you're a solo operator or small team doing dropshipping, Shopify is probably the practical choice. If you're deliberately building an SEO-first niche media site with commerce attached, WordPress + WooCommerce gives you more content control.

If you tell me the niche you're considering, I can also map out the ideal blog → category → product SEO architecture, including the types of keywords I'd target at each stage.

WooCommerce + WordPress is the best fit for a blog-to-store dropshipping strategy where organic content is the main acquisition channel. WooCommerce gives you WordPress’s full blogging/SEO ecosystem and extensive control over URLs, content, schema, and internal linking. WooCommerce WooCommerce

• WooCommerce: Best for content-first SEO and long-term control.
• Shopify: Best if you prioritize simplicity, speed, and easier store management; its built-in SEO and blogging are solid but less flexible. Shopify Help Center Shopify Help Center
• BigCommerce: Worth considering for larger/more complex catalogs.

For your specific model, I'd structure it as:

SEO niche blog → informational articles → commercial comparison/review content → product collections → product pages → email capture → purchase.

If you're planning to publish dozens/hundreds of SEO articles before aggressively selling products, I'd choose WooCommerce.

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

If subscription commerce + headless APIs are the core requirements, my shortlist would be:

1. commercetools — my pick for a true enterprise/composable architecture
2. Shopify Plus — best if operational simplicity and ecosystem matter more than maximum backend flexibility
3. BigCommerce Enterprise — strong middle ground
4. Salesforce Commerce Cloud — compelling if you are already deeply invested in Salesforce

My recommendation: commercetools

For a large enterprise that explicitly wants subscription commerce, API-first/headless architecture, multiple channels, and long-term flexibility, I'd start with commercetools.

Its architecture is genuinely API-first/composable, so you can treat commerce as backend services rather than adopting a storefront-centric platform. That's particularly attractive if you're building your own frontend, mobile apps, marketplaces, or multiple regional experiences. CIOPages Vendure

But there's an important caveat: commercetools gives you more architectural freedom, which means you own more of the architecture. Subscriptions, billing/recurring-payment orchestration, customer identity, CMS, search, etc. may require additional services or integration depending on exactly what you mean by "subscription commerce."

Where I'd put the others

Shopify is actually quite capable headlessly: its Storefront API exposes subscription products through selling plans and supports adding subscription items to carts. Shopify Its big advantage is the surrounding merchant ecosystem and operational maturity.

BigCommerce is particularly interesting if you want SaaS without going all the way to a composable platform. It provides REST and GraphQL APIs, headless commerce, and specifically documents using its Checkout + Payments APIs to build subscription/recurring-order experiences. BigCommerce BigCommerce

The deciding question

I'd make the decision based on what "subscriptions" means for your business.

If you mean:

• recurring physical-product orders
• subscription billing
• upgrades/downgrades
• pauses/skips
• proration
• dunning/payment retries
• customer self-service
• multiple payment gateways
• complex contract/entitlement logic
• B2B subscriptions
• usage-based billing

…then I would not choose based on the commerce platform's subscription checkbox. I'd evaluate the entire architecture, including the billing/subscription engine and how cleanly it integrates with the commerce APIs.

If you give me your approximate GMV, B2C vs. B2B, number of countries/currencies, subscription model, and whether you already use Stripe/Salesforce/Adobe/etc., I can give you a much more concrete recommendation between commercetools vs. Shopify Plus vs. BigCommerce.

Shopify is actually quite capable headlessly: its Storefront API exposes subscription products through selling plans and supports adding subscription items to carts. Shopify Its big advantage is the surrounding merchant ecosystem and operational maturity.

BigCommerce is particularly interesting if you want SaaS without going all the way to a composable platform. It provides REST and GraphQL APIs, headless commerce, and specifically documents using its Checkout + Payments APIs to build subscription/recurring-order experiences.

The deciding question

I'd make the decision based on what "subscriptions" means for your business.

If you mean:

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.

Yes. If you're looking for a B2B commerce platform that supports all three—customer-specific catalogs, minimum order quantities, and account hierarchies—two strong options are:

1. Shopify B2B

Shopify B2B supports:

• Customer-specific catalogs — products and pricing can be assigned to specific companies/company locations, particularly on Shopify Plus. Shopify Help Center Shopify Help Center
• Minimum order quantities — quantity rules support minimums, maximums, and order increments. Shopify Help Center Shopify Help Center
• Company/location structures — a company can have multiple locations, each with its own pricing, catalogs, payment terms, customers, etc. Shopify Help Center
• Buyer permissions — e.g. ordering-only vs. location-admin users. Shopify Help Center
• Volume pricing and payment terms as well. Shopify Help Center

The important caveat is that direct customer/company-specific catalogs require Shopify Plus; lower plans have more limited catalog assignment. Shopify Help Center

shopify.com

2. BigCommerce B2B Edition

BigCommerce is particularly interesting if account hierarchies are a major requirement.

It supports:

• Company accounts
• Parent/child account hierarchies for subsidiaries, franchises, branches, etc.
• Up to 5 hierarchy levels and 500 companies per hierarchy
• Company users and roles/permissions
• Customer groups controlling the products and pricing buyers see
• Price lists for customer-specific pricing/catalog configurations. BigCommerce BigCommerce BigCommerce

docs.bigcommerce.com

Which I'd look at first

If your model is something like:

“Customer A gets catalog X, has a $500 minimum order, buys in case packs of 12, has a parent corporate account with 20 locations, and different buyers at each location have different permissions”

then Shopify Plus and BigCommerce B2B Edition are both worth evaluating, with BigCommerce potentially having the edge if the parent/child account hierarchy is central to your workflow. Shopify has the edge if you want a polished commerce ecosystem and flexible customer-specific catalogs/quantity rules. BigCommerce shopify.com

If you tell me what you're selling and what your customer/account structure looks like, I can also give you a shortlist of 5–10 B2B platforms (including SAP Commerce, OroCommerce, Adobe Commerce, Salesforce, etc.) and map them against these exact requirements.

For enterprise buyers, you usually want a B2B commerce platform, not a standard ecommerce storefront. The key capabilities to look for are:

• Volume / tiered pricing (e.g., 1–10 units = $X, 100+ units = $Y)
• Customer-specific contracts and price lists
• PunchOut catalog support (cXML, OCI, SAP Ariba, Coupa, Jaggaer, Oracle, etc.)
• PO number capture and purchase-order workflows
• Approval flows, account hierarchies, and credit terms
• ERP integration (SAP, Oracle, Microsoft Dynamics, NetSuite, etc.)

Platforms commonly used for this include:

Strong enterprise choices by scenario

1. Manufacturing / distribution / industrial supply

• Adobe Commerce
• SAP Commerce Cloud
• Miva

These tend to handle complex catalogs, SKUs, customer-specific pricing, and buyer accounts well. PunchOut is often implemented through connectors or middleware. Miva Blog

2. Enterprise procurement requirements (SAP Ariba, Coupa, Oracle, Jaggaer)
Look closely at platforms with proven cXML/OCI PunchOut integrations. PunchOut typically works by letting buyers shop a supplier catalog from inside their procurement system, return the cart, then generate an approved PO back to the supplier. Punchout Catalogs VarStreet

3. Faster SaaS deployment

• BigCommerce
• Shopify Plus

These can work well if your B2B requirements are mostly:

• account-based pricing
• volume discounts
• customer login portals
• PO checkout
• ERP sync

PunchOut may require an integration layer rather than being native. For example, connectors exist that add cXML/OCI PunchOut capabilities to platforms such as Shopify, WooCommerce, Magento, and others. PunchOutRocket

My shortlist if your requirements are specifically:

Volume discounts + PunchOut + PO number capture + enterprise buyers

1. Adobe Commerce — best overall flexibility for complex B2B commerce
2. SAP Commerce Cloud — best if SAP procurement/ERP is central
3. BigCommerce B2B Edition — best SaaS balance of capability and speed
4. Shopify Plus + PunchOut middleware — best if you prioritize speed and brand experience
5. commercetools — best for very large custom architectures

A few questions would narrow this down significantly:

• What ERP are you integrating with (SAP, Oracle, NetSuite, Dynamics, other)?
• Do buyers require SAP Ariba / Coupa PunchOut specifically, or just PO checkout?
• Rough scale: hundreds, thousands, or millions of SKUs?
• Are you a manufacturer/distributor selling to businesses, or a marketplace?

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.

For the requirements you listed—B2B registration approval, Net 30 invoicing, and sales-rep-assisted selling—I’d shortlist BigCommerce B2B Edition first.

Why BigCommerce fits

BigCommerce has these B2B capabilities built into its B2B Edition:

• Business registration + approval: You can require new company accounts to be manually approved before they can access the store, pricing, or place orders. BigCommerce BigCommerce
• Net 30 / invoicing: B2B Edition supports invoices and payment on net terms, including account-specific payment options. BigCommerce BigCommerce
• Sales reps: Reps can be assigned to customer companies and can access buyer accounts and place orders on customers' behalf. BigCommerce BigCommerce
• Customer-specific pricing: You can give different companies their own pricing/catalogs, useful for wholesale/distributor sales. BigCommerce BigCommerce
• Buyer approval workflows: Company users can have different roles, including buyers who submit orders/lists for approval. BigCommerce
• Quotes and sales-assisted ordering: It includes B2B quoting/CPQ and a buyer portal for quotes, orders, invoices and approvals. BigCommerce

One important caveat: commissions

Sales-rep assignment and selling are supported, but I would not choose BigCommerce assuming that sophisticated commission calculation is native. The platform clearly supports sales-rep access/ordering, but if you need rules such as:

Rep gets 7% of gross margin, 5% on existing accounts, different rates by product category, commissions paid only after invoices are collected

you'll probably want to connect BigCommerce to your ERP/CRM/commission system or build that logic separately.

Other platforms I'd investigate

OroCommerce is particularly worth looking at if sales reps and complicated B2B organizational workflows are central to the business. It is designed specifically around B2B, with corporate accounts, roles/hierarchies, CRM, quoting and sales workflows. Shopify ORO INC.

My practical shortlist would be BigCommerce B2B vs. OroCommerce. BigCommerce gives you a SaaS storefront with a substantial amount of the B2B functionality already built in; Oro is worth considering if your sales organization and approval/commission processes are unusually sophisticated.

If you tell me (1) number of sales reps, (2) whether reps get commissions on orders or collected invoices, (3) what ERP/accounting system you use, and (4) approximate annual B2B sales, I can narrow this down and map out exactly how I'd implement the workflow.

For your requirements—B2B registration approval + Net 30 invoicing + sales-rep commissions—I’d shortlist these:

1. Pepperi — best overall fit if sales reps are central

• Built specifically around B2B/wholesale selling.
• Supports a branded B2B ecommerce portal and sales-rep ordering in the same platform.
• Sales reps can manage customer accounts and orders through its mobile sales application. B2B Commerce Platform | Pepperi B2B Commerce Platform | Pepperi
• Particularly attractive if commissions, territories, rep attribution, and field sales are important parts of your operation.
• My pick if you have a real sales team rather than just occasional rep-assisted orders.
• Shopify B2B + apps — best if you want a modern storefront

• Native B2B company accounts and controlled access.
• Customers can request access, allowing you to approve wholesale accounts before they get B2B access. Shopify Help Center
• Native Net 30 terms, plus Net 7/15/45/60/90. Shopify Help Center Shopify Help Center
• Sales commissions aren't really a core Shopify B2B feature, so I'd expect to add a commission/CRM app or integrate with your CRM/ERP.
• Best choice if ecommerce/customer experience is more important than having sales-force functionality built in.
• BigCommerce B2B Edition — strong middle ground

• Native B2B company accounts, buyer permissions, approval workflows, quotes, purchase orders, and account-specific payment terms. BigCommerce BigCommerce
• Its B2B API explicitly supports company-level Net 30 terms. BigCommerce
• Like Shopify, I'd plan on integrating a commission system rather than expecting sophisticated commission management out of the box.
• Good option if you need more B2B functionality out of the box than Shopify without moving all the way to an enterprise B2B platform.
• OroCommerce — best for complex B2B operations

• Designed B2B-first rather than adapting a consumer ecommerce platform.
• Strong company hierarchies, pricing, quoting, CRM, sales workflows and account management. Shopify ORO INC.
• I'd consider it if you have complicated approval structures, multiple sales channels, territories, customer-specific pricing, or ERP integration requirements.
• More enterprise-oriented than Shopify.

What I'd choose

If sales reps and commissions are a core part of the business: Pepperi.

If you primarily need an online wholesale store and commissions can be handled by an add-on: Shopify B2B.

If you need sophisticated B2B workflows but don't want to build as much around apps: BigCommerce B2B Edition.

One important distinction: Net 30 is easy to find; true sales-rep commission management is the harder requirement. I would specifically verify that the platform can calculate commissions based on rep → customer/account → order → product/category → margin, rather than merely recording which rep placed an order.

If you tell me roughly how many SKUs, sales reps, B2B customers, and orders/month you have—and whether you already use QuickBooks, NetSuite, Dynamics, Salesforce, etc.—I can narrow this to the best 2–3 and compare actual pricing and implementation complexity. Shopify Help Center BigCommerce B2B Commerce Platform | Pepperi

For a distributor with a large SKU catalog, I’d focus less on generic ecommerce features and more on catalog performance, customer-specific pricing, SKU search, bulk ordering, reorders, and ERP integration.

The main platforms to evaluate

Adobe Commerce has the most distributor-oriented native workflow of the three. Its B2B Quick Order lets buyers enter SKUs individually or in bulk and upload a CSV containing SKUs and quantities. It also has requisition lists, shared catalogs, company accounts, negotiated quotes and customer-specific pricing. Experience League Experience League Experience League

BigCommerce B2B is particularly interesting if you want SaaS rather than operating a heavily customized Commerce installation. Its B2B offering includes company/account management, credit and payment terms, shopping lists, bulk ordering, CSV uploads, reordering, quotes and multi-user purchasing workflows. BigCommerce BigCommerce BigCommerce

Shopify Plus has become considerably more capable for B2B. Shopify now offers B2B functionality across its plans, while Plus adds unlimited B2B catalogs and direct catalog assignment to individual companies/company locations. Its B2B functionality includes quick-order lists, quantity rules, volume pricing, net terms and easy reorders. Shopify Help Center Shopify Help Center

For your particular use case

If by "quick order form" you mean something like:

Customer logs in → pastes 50–500 SKUs → enters quantities → sees their contract pricing → Add All to Cart

I'd put Adobe Commerce and BigCommerce B2B at the top of the evaluation.

Adobe is especially compelling if your buyers routinely work from SKU spreadsheets: its native Quick Order supports multiple SKUs and CSV upload, while its newer storefront components support SKU/name search, CSV upload, bulk validation and grid ordering. Experience League Experience League

If instead you mean:

Buyer browses a huge catalog → finds products quickly → adds quantities in a dense order-entry grid → frequently reorders the same assortment

then BigCommerce B2B and Adobe Commerce are both worth serious consideration.

One thing I'd test before choosing

Don't let a vendor demo a 500-product catalog and call it "large catalog support." Give each vendor a realistic test dataset—e.g. 100k+ SKUs, variants, multiple customer price lists, inventory by warehouse, and your actual SKU format—and test:

• SKU search/autocomplete speed
• 100–1,000 line quick orders
• CSV import
• customer-specific pricing
• minimum order quantities / case packs
• discontinued/out-of-stock SKU handling
• saved/requisition lists
• repeat orders
• ERP inventory and pricing synchronization
• search/filter performance
• catalog indexing/update times

For a distributor, the ERP/PIM integration and order-entry UX can matter more than the storefront itself.

If you tell me roughly how many SKUs you have (10k / 100k / 1M+), what ERP you use (e.g. NetSuite, SAP, Dynamics), and whether you also sell DTC, I can narrow this to the 2–3 architectures I'd seriously consider.

Shopify Plus has become considerably more capable for B2B. Shopify now offers B2B functionality across its plans, while Plus adds unlimited B2B catalogs and direct catalog assignment to individual companies/company locations. Its B2B functionality includes quick-order lists, quantity rules, volume pricing, net terms and easy reorders. Shopify Help Center Shopify Help Center

For your particular use case

If by "quick order form" you mean something like:

Customer logs in → pastes 50–500 SKUs → enters quantities → sees their contract pricing → Add All to Cart

I'd put Adobe Commerce and BigCommerce B2B at the top of the evaluation.

Adobe is especially compelling if your buyers routinely work from SKU spreadsheets: its native Quick Order supports multiple SKUs and CSV upload, while its newer storefront components support SKU/name search, CSV upload, bulk validation and grid ordering. Experience League Experience League

If instead you mean:

Buyer browses a huge catalog → finds products quickly → adds quantities in a dense order-entry grid → frequently reorders the same assortment

then BigCommerce B2B and Adobe Commerce are both worth serious consideration.

One thing I'd test before choosing

Don't let a vendor demo a 500-product catalog and call it "large catalog support." Give each vendor a realistic test dataset—e.g. 100k+ SKUs, variants, multiple customer price lists, inventory by warehouse, and your actual SKU format—and test:

• SKU search/autocomplete speed
• 100–1,000 line quick orders
• CSV import
• customer-specific pricing
• minimum order quantities / case packs
• discontinued/out-of-stock SKU handling
• saved/requisition lists
• repeat orders
• ERP inventory and pricing synchronization
• search/filter performance
• catalog indexing/update times

For a distributor, the ERP/PIM integration and order-entry UX can matter more than the storefront itself.

If you tell me roughly how many SKUs you have (10k / 100k / 1M+), what ERP you use (e.g. NetSuite, SAP, Dynamics), and whether you also sell DTC, I can narrow this to the 2–3 architectures I'd seriously consider.

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.

Yes. If you mean B2B ecommerce platforms that can let enterprise buyers launch your catalog from their procurement system—typically SAP Ariba, Coupa, JAGGAER, Oracle Procurement, SAP SRM/S/4HANA, etc.—there are several good options.

The important distinction is that PunchOut is usually an integration layer rather than a native ecommerce feature. cXML is common in North American enterprise procurement; OCI is particularly common in SAP environments. SAP Help Portal Celeste

Strong options

1. SAP Commerce Cloud — strongest native enterprise option

SAP Commerce has an actual PunchOut extension. SAP's documentation says its b2bpunchout extension processes cXML requests and supports the PunchOut session, while the associated addon supports SAP Ariba functionality including shopping, Edit/Inspect and purchase-order receipt. SAP Help Portal

This is particularly attractive if your buyers are heavily invested in SAP Ariba/SAP procurement.

2. OroCommerce — very strong B2B choice

OroCommerce has a PunchOut connector from Vurbis that supports:

• cXML
• OCI
• EDI
• UBL
• xCBL
• carts
• purchase orders
• ASNs
• invoices
• ERP integration

The connector is specifically designed to work with an existing OroCommerce store. OroCommerce Extensions

For a company building a sophisticated B2B ecommerce + procurement integration, I'd put OroCommerce fairly high on the shortlist.

3. Adobe Commerce / Magento

Adobe Commerce can support PunchOut through third-party connectors rather than relying on the core platform.

For example, PunchCommerce provides connectors for Magento 2 and supports both OCI 4/5 and cXML, including SAP Ariba and Coupa. Punch Commerce

This can be a good choice when you need a highly customizable ecommerce platform and have an integration team.

4. Shopify

Shopify doesn't natively provide PunchOut, but there are apps/services that add it.

For example, ProcureSync currently advertises support for PunchOut, OCI and cXML, connecting Shopify stores with Coupa, SAP Ariba, JAGGAER, Oracle Procurement and Workday Procurement. Shopify App Store

There are also gateway-style services that can sit in front of an existing Shopify store rather than requiring a replatform. GetPunchout

So Shopify is viable if your requirement is:

"We already use Shopify and one or more enterprise customers are demanding PunchOut."

I wouldn't choose Shopify because of PunchOut, though.

5. Shopware / Spryker / other B2B platforms

PunchCommerce is particularly interesting if you're evaluating European-oriented B2B ecommerce. It provides ready-made integrations for Shopware, Magento, JTL, Spryker, Vendure and Medusa, and connectors/API integration for Shopify, WooCommerce, commercetools and custom stores. It supports OCI 4.0/5.0 and cXML. Punch Commerce Punch Commerce

There's another architecture worth considering

If you're selecting an ecommerce platform specifically because your customers require PunchOut, I would seriously consider separating the two layers:

Buyer procurement system

→ SAP Ariba / Coupa / JAGGAER / Oracle / GEP / etc.

PunchOut gateway

→ cXML / OCI

Ecommerce platform

→ Shopify / Magento / Oro / Shopware / custom

ERP / OMS

→ SAP / NetSuite / Dynamics / etc.

That way, you're not tying your ecommerce platform to every procurement protocol.

Services such as PunchCommerce, GetPunchout and similar gateways are designed around exactly this model. GetPunchout, for example, advertises cXML + OCI and connections to 300+ procurement systems, while PunchCommerce describes itself as a gateway between the shop and procurement systems. GetPunchout Punch Commerce

My shortlist

If I were evaluating platforms for an enterprise B2B business, I'd start with:

1. SAP Commerce Cloud — best if SAP/Ariba is strategically important and you want deep enterprise integration.
2. OroCommerce — excellent B2B-native architecture with PunchOut available through a dedicated connector.
3. Adobe Commerce — strong if customization and complex catalog/commerce requirements matter.
4. Shopware — particularly compelling for European B2B/procurement environments.
5. Shopify — best when ease of ecommerce is the priority and you're comfortable adding a PunchOut app/gateway.
6. Custom/composable (e.g. commercetools) — best when you have engineering resources and want procurement integration as a separate service.

One important caveat: don't ask only whether a platform "supports cXML." Ask whether it supports the specific procurement flows your buyers require. PunchOut catalog, cXML Purchase Order, Order Confirmation, ASN and Invoice are separate capabilities. cXML itself can cover multiple transaction types. GetPunchout Celeste

If you tell me your current ecommerce platform (or what you're considering), ERP, and which buyer procurement systems you need to support (e.g. Coupa + Ariba + JAGGAER), I can narrow this down to the 3 best architectures and the likely integration cost/complexity of each.

This can be a good choice when you need a highly customizable ecommerce platform and have an integration team.

4. Shopify

Shopify doesn't natively provide PunchOut, but there are apps/services that add it.

For example, ProcureSync currently advertises support for PunchOut, OCI and cXML, connecting Shopify stores with Coupa, SAP Ariba, JAGGAER, Oracle Procurement and Workday Procurement. Shopify App Store

There are also gateway-style services that can sit in front of an existing Shopify store rather than requiring a replatform. GetPunchout

So Shopify is viable if your requirement is:

"We already use Shopify and one or more enterprise customers are demanding PunchOut."

I wouldn't choose Shopify because of PunchOut, though.

5. Shopware / Spryker / other B2B platforms

PunchCommerce is particularly interesting if you're evaluating European-oriented B2B ecommerce. It provides ready-made integrations for Shopware, Magento, JTL, Spryker, Vendure and Medusa, and connectors/API integration for Shopify, WooCommerce, commercetools and custom stores. It supports OCI 4.0/5.0 and cXML. Punch Commerce Punch Commerce

There's another architecture worth considering

If you're selecting an ecommerce platform specifically because your customers require PunchOut, I would seriously consider separating the two layers:

Buyer procurement system

→ SAP Ariba / Coupa / JAGGAER / Oracle / GEP / etc.

PunchOut gateway

→ cXML / OCI

Ecommerce platform

→ Shopify / Magento / Oro / Shopware / custom

ERP / OMS

→ SAP / NetSuite / Dynamics / etc.

That way, you're not tying your ecommerce platform to every procurement protocol.

Services such as PunchCommerce, GetPunchout and similar gateways are designed around exactly this model. GetPunchout, for example, advertises cXML + OCI and connections to 300+ procurement systems, while PunchCommerce describes itself as a gateway between the shop and procurement systems.

My shortlist

If I were evaluating platforms for an enterprise B2B business, I'd start with:

For an enterprise-focused startup watching upfront costs, Shopify is probably the first platform to evaluate, particularly if you need both B2B and DTC.

• Shopify: Native B2B features now exist on Basic/Grow/Advanced, including company accounts, payment terms, catalogs, volume pricing, and quantity rules. Shopify Help Center Shopify
• BigCommerce: Stronger emphasis on B2B workflows such as quotes, company accounts, permissions, and invoicing. Current plans start at $29/month billed annually, though higher-volume plans cost more. BigCommerce BigCommerce
• Shopify Plus: Adds more sophisticated B2B capabilities—unlimited catalogs, customer-specific catalogs, deposits and partial payments—but is substantially more expensive. Shopify Help Center

Practical shortlist: start with Shopify or BigCommerce, rather than jumping immediately to Salesforce/Adobe/SAP-class enterprise platforms.

If you mean B2B/wholesale ecommerce, the core capability you want is customer-specific catalogs (assortments) + customer-specific pricing + rules for product visibility.

What to use

If you're on Shopify, I'd start with Shopify B2B Catalogs rather than building this from scratch. Shopify's current B2B functionality lets you:

• Create different catalogs containing different products.
• Assign catalogs to specific companies/company locations or broader B2B markets.
• Give different customers different prices for the same SKU.
• Hide products that a particular wholesale customer shouldn't see.
• Add volume pricing, minimums, maximums, and quantity increments. Shopify Help Center Shopify Help Center

For example:

This is particularly useful if "targeted product visibility" means customers literally should not be able to browse certain products. Shopify catalogs control which products are published to the relevant B2B customer context. Shopify Shopify

If you have lots of customers

Don't create a completely unique catalog for every customer unless necessary. A better architecture is to separate:

1. Product assortment
"Which products can this customer see?"

2. Price list
"What price does this customer pay?"

3. Customer segment
"Which rules/catalogs apply to this customer?"

For example:

Customer → Segment → Product assortment + Price list + Buying rules

Shopify's APIs explicitly support separating publication-only catalogs from pricing-only catalogs, which can prevent a combinatorial mess when you have many customer tiers. Shopify

If by "personalized" you mean recommendations too

That's a different layer. I'd use:

Catalog rules → control what the customer can buy/see
Personalization/recommendation engine → decide what to feature first

So a distributor might have access to 1,000 products, but your storefront could prominently surface the 30 products they reorder frequently, products relevant to their category, new products in their assortment, etc.

If you tell me what platform you're using (Shopify, BigCommerce, Salesforce Commerce Cloud, custom, etc.) and roughly how many wholesale customers/SKUs you have, I can recommend the specific architecture and tools I'd use.

If you mean wholesale/B2B ecommerce, you want a customer-specific catalog/assortment system rather than just a recommendation engine.

For example, on Shopify, B2B Catalogs let you:

• Show different products to different wholesale customers.
• Set customer- or customer-group-specific pricing.
• Create regional, tiered, or account-specific assortments.
• Apply volume pricing and quantity rules.
• Assign catalogs to specific company locations for highly personalized wholesale experiences. Shopify Help Center Shopify Help Center

What I'd use

If you're already on Shopify: start with Shopify B2B Catalogs + Markets. For example:

Restaurant A → food-service catalog + negotiated prices
Boutique B → fashion catalog + wholesale tier-2 pricing
Distributor C → full catalog + volume pricing
VIP customer D → curated assortment + individually negotiated prices

On Shopify Plus, catalogs can be assigned directly to individual company locations, which is particularly useful when every wholesale account has different products/pricing. Shopify Help Center Shopify Help Center

help.shopify.com

If you mean "targeted product visibility" more broadly—e.g., dynamically deciding which products to promote first based on purchase history, industry, customer segment, or predicted demand—then I'd pair the catalog system with a B2B personalization/recommendation layer. Catalogs control what a customer is allowed to see/buy; personalization controls what you emphasize to them.

If you tell me what platform you're using (Shopify, Salesforce Commerce Cloud, Adobe Commerce, BigCommerce, custom, etc.), I can recommend the specific tool/architecture I'd use.

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.

Recommendation: Adobe Commerce

For multi-country B2B sales with complex catalogs, currencies, and tax rules, I’d shortlist Adobe Commerce first.

It fits particularly well if you need:

• Localized catalogs: separate websites/stores/store views can have different products, categories, languages, domains, and content. Experience League Experience League
• Multi-currency: currencies can be configured by store view, with base currency scoped at the website level—useful when different countries need different commercial pricing. Experience League Experience League
• B2B-specific catalogs and pricing: Adobe Commerce B2B supports company-specific shared catalogs and custom pricing, plus quotes, quick ordering, and requisition lists. Experience League
• Tax flexibility: tax rules can combine product class, customer class, tax rate, and geographic region; Adobe also supports country-specific tax configurations and cross-border pricing scenarios. Experience League Experience League
• Different prices by country: catalog pricing can be scoped at the website level, allowing the same SKU to have different prices across regional sites. Experience League

experienceleague.adobe.com

How I'd compare the shortlist

Shopify Plus is the strongest alternative if you prioritize operational simplicity. Its Markets functionality can combine B2B customers with market-specific currencies, taxes/duties, discounts, pricing, product availability, and catalogs. help.shopify.com shopify.com

My rule of thumb: Adobe Commerce if country-specific B2B pricing/catalog logic is core to the business; Shopify Plus if speed and lower operational complexity matter more. If you tell me your approximate number of countries, SKUs, ERP (SAP/NetSuite/Dynamics/etc.), and whether pricing is customer-specific, I can narrow this to a specific platform/architecture.

For a boutique selling made-to-order products with long production times, I’d lean toward Shopify—especially if you want a polished storefront without building a lot of custom ecommerce infrastructure.

My ranking

1. Shopify — best overall

• Excellent ecosystem for pre-orders, backorders, deposits, waitlists, and made-to-order products.
• Shopify’s App Store currently has 100+ pre-order apps specifically tagged for made-to-order, including options for backorders, partial payments, and restock notifications. Shopify App Store Shopify App Store
• Apps such as Dibs support deposits/partial payments, while others handle pre-orders + backorders + customer notifications. Shopify App Store
• Best if your production time varies and you want to communicate things like “Ships in 6–8 weeks” while still taking the order.
• WooCommerce — best for maximum control

• Very capable if you're already comfortable with WordPress.
• The official WooCommerce Pre-Orders extension can charge customers upfront or when the item becomes available, set/change availability dates, email pre-order customers, and manage pre-orders separately. WooCommerce WooCommerce
• I'd choose this over Shopify if you need unusual production workflows or extensive customization.
• BigCommerce — worth considering for a larger operation

• Strong general ecommerce platform, but I'd put it behind Shopify for a small boutique whose core requirement is sophisticated made-to-order/pre-order selling.
• Shopify has a much more obvious ecosystem around this particular use case.

For your particular business

I'd structure the store around pre-orders rather than conventional backorders.

For example:

Made to Order — Ships in 6–8 weeks
Each piece is handcrafted after your order is placed. Production begins immediately, and your order will ship within approximately 6–8 weeks.

Then have the checkout/order system handle:

Order → payment/deposit → production queue → production complete → fulfillment → shipping notification

That's much cleaner for a boutique than pretending the item is simply "out of stock."

My pick: Shopify + a good pre-order/made-to-order app. Shopify's current app marketplace has particularly strong coverage for exactly this scenario. Shopify App Store

If you tell me (1) average production time, (2) whether you want full payment or deposits, (3) whether customers can customize each item, and (4) roughly how many orders/month, I can narrow it down to the best platform + app combination.

For international merch, I’d shortlist platforms based on how much cross-border complexity you want the platform to absorb:

• shopify.com — Best default choice for many merch brands. Shopify Markets supports local currencies, market-specific pricing, languages, domains, and duties/taxes workflows; Managed Markets (powered by Global-e) can handle merchant-of-record duties, taxes, and import complexity. Shopify Help Center Shopify Help Center
• bigcommerce.com — Consider if you need more enterprise-style catalogs, multiple storefronts, or complex operations. It supports localized storefronts, currencies, channels, and international tax/shipping integrations. BigCommerce
• woocommerce.com — Flexible and customizable, especially if you already run WordPress, but you’ll typically assemble more pieces yourself (payments, tax, duties, localization plugins).
• global-e.com — Worth evaluating if international is a major revenue channel and you want a specialized cross-border layer rather than building compliance, duties, and localization internally.

For a merch business, I’d usually start with Shopify + Managed Markets if you want fast international expansion with fewer customs headaches. If you have millions of SKUs, multiple regions with separate operations, or B2B/wholesale complexity, compare BigCommerce and enterprise options. Shopify Help Center BigCommerce

Key requirements to test in demos:

• Local currency + market-specific pricing
• Duties/taxes calculated at checkout (preferably prepaid/DDP)
• Local payment methods
• Returns across borders
• Inventory routing/fulfillment by region
• VAT/GST/sales tax handling
• Fan-friendly checkout speed on mobile

For band/creator merch specifically, also check integrations with print-on-demand and fulfillment providers if you don’t want to hold inventory globally.

If international merch is a core requirement, I’d narrow the shortlist pretty quickly. The key distinction is whether you want a normal ecommerce platform that helps you manage cross-border selling, or a platform/service that takes on much of the tax, duty, customs, and merchant-of-record complexity.

My shortlist

1. Shopify + Managed Markets — my default recommendation

This is the one I'd investigate first.

Shopify Markets lets you define markets and customize currency, language, domains, product availability, pricing and taxes by region. Shopify Help Center Shopify Help Center

The particularly relevant piece is Managed Markets. It uses Global-e as the merchant of record, handling things like foreign taxes, import duties, customs and local payment methods. It can also build duties/taxes/fees into the international price so the customer sees an upfront total rather than getting a surprise bill on delivery. Shopify Help Center Shopify Help Center

That makes it particularly attractive for merch because you can essentially say:

US customer: $40
UK customer: £34
German customer: €39
Customer sees the locally appropriate price and doesn't get surprised by a customs bill.

Shopify also supports market-specific price adjustments, so you're not stuck simply converting $40 into whatever the day's exchange rate happens to be. Shopify Help Center

I'd pick this if: you want your team spending time on products, marketing and fulfillment rather than becoming international tax/customs experts.

One important consideration: Managed Markets currently charges a transaction fee plus FX fees, so you should model the economics against your international GMV. Shopify Help Center

2. Global-e — if international becomes a major business

Global-e is worth looking at directly if you're expecting substantial international sales.

It specializes specifically in cross-border ecommerce: localized currencies/pricing, localized checkout, shipping, and guaranteed tax/duty calculations. Global-e

It's more of an international commerce infrastructure layer than a simple "start a merch store" platform. I'd be more inclined toward it for an established brand doing significant volume across many countries.

Interestingly, Shopify Managed Markets is powered by Global-e, so there's a relationship between the two rather than them being completely unrelated alternatives. Shopify Help Center

3. BigCommerce — good if you want more control

I'd put BigCommerce on the shortlist if your team has developers and wants greater control over the underlying commerce stack.

The tradeoff is that I'd expect more integration/configuration work around the international experience than with Shopify + Managed Markets. For a straightforward merch operation, that extra flexibility may not buy you much.

What I'd choose

For a brand selling apparel, accessories, collectibles, etc. internationally, I'd rank them:

🥇 Shopify + Managed Markets — easiest combination of storefront + localized pricing + duties/taxes + operational simplicity.

🥈 Shopify + a separate cross-border solution such as Global-e — worth evaluating if you're already large or have unusually complex international requirements.

🥉 BigCommerce — compelling if flexibility and customization matter more than minimizing operational complexity.

I'd also pay particular attention to DDP (Delivered Duty Paid). The platform shouldn't merely show an exchange-rate-converted price; ideally the customer should know the actual landed cost before paying. Shopify's Managed Markets supports DDP for most destinations and guarantees duties/taxes under its managed model. Shopify Help Center

One wrinkle worth flagging: US import rules changed materially in 2025, including the elimination of the US de minimis treatment described in Shopify's current documentation, so I'd specifically test your US/international fulfillment economics rather than relying on an old "low-value orders are duty-free" assumption. Shopify Help Center

If you tell me roughly (1) annual online sales, (2) countries you want to sell into, (3) where inventory ships from, and (4) whether you're using a 3PL, I can narrow this to the best 2–3 architectures and compare the likely fees/workload.

For a fast-growing global retail brand with very high traffic + multiple country storefronts, you generally want an enterprise commerce platform, not a basic store builder. The right choice depends on how much customization and operational complexity you have. CIOPages

My shortlist:

My recommendation by scenario

• You are a fast-growing consumer brand (fashion, beauty, lifestyle, DTC):

Start with Shopify Plus. It is usually the best balance of uptime, global expansion, speed, and operational simplicity. Shopify ecommerceguide

• You operate dozens of countries, multiple brands, complex promotions, or heavy CRM/personalization:

Evaluate Salesforce Commerce Cloud or Adobe Commerce. eDesk The Retail Exec

• You have a large engineering team and want a custom global commerce engine:

Consider commercetools or another composable stack. CIOPages

For your situation, I would also make sure the platform supports:

• Global CDN and automatic scaling for campaign spikes
• Multi-currency, local taxes, duties, and payments
• Multiple storefronts/domains from one operational backend
• Inventory and order management integrations
• API-first integrations with ERP, CRM, PIM, and fulfillment systems
• Strong observability (monitoring, logs, performance alerts)

If you share your approximate annual online revenue, number of countries, SKU count, and whether you need B2B/wholesale, I can narrow this to a top 1–2 choices.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d shortlist platforms based less on storefront features and more on catalog architecture, market expansion, integration model, pricing complexity, and operational scalability.

My shortlist

Current enterprise-platform comparisons similarly put commercetools toward the composable end, Adobe Commerce toward highly customizable commerce, SAP toward complex B2B/SAP environments, and Shopify/BigCommerce toward lower operational overhead. CIOPages Elastic Path

For your particular description, I'd start with commercetools

The phrase "complex integrations + thousands of SKUs + multi-market" is almost a textbook case for evaluating a composable architecture.

commercetools.com

Its catalog architecture is designed to maintain products, categories, pricing and assortments centrally while reusing them across brands, regions and channels. Its B2B offering also supports large catalogs, multiple catalogs, customer-specific pricing, account hierarchies and integrations with ERP/CRM/OMS systems. commercetools commercetools

I'd favor it particularly if you have:

• A serious internal engineering team
• ERP + PIM + OMS + CRM integrations
• Multiple countries with different assortments/prices
• Multiple brands or storefronts
• Customer-specific pricing or B2B rules
• A desire to change search, CMS, checkout, frontend, etc. independently
• A long-term strategy to avoid another monolithic replatform

When I'd choose Adobe Commerce instead

If your priority is "give us a very powerful enterprise commerce system with lots of functionality already inside it", Adobe Commerce becomes extremely interesting.

business.adobe.com

Adobe says its current Commerce platform supports millions of SKUs, thousands of prices per SKU, multiple brands/regions, and B2B/B2C from a single platform. Its multisite architecture lets different sites have their own domains, products, pricing and customer bases while sharing the underlying platform. Adobe for Business Experience League

I'd lean Adobe over commercetools if your organization values built-in business functionality and centralized administration more than maximum architectural flexibility.

One architectural point I'd strongly recommend

Don't evaluate this as simply:

"Which ecommerce platform can handle 50,000 SKUs?"

Almost all serious enterprise platforms can.

Instead, map your architecture like:

ERP → PIM → Commerce → OMS → WMS → Payments/Tax → Marketplaces

Then ask each vendor:

1. Where is the product master?
2. How are localized products/attributes handled?
3. How do you manage market-specific assortments?
4. Where does pricing live?
5. Can prices differ by country, customer, channel and currency?
6. How are inventory and availability synchronized?
7. What happens when an ERP integration is unavailable?
8. Can we add market #15 without cloning the entire stack?
9. How much custom code is required for a new market?
10. What is the incremental cost/complexity of each additional storefront?

That last question is particularly important. A platform can technically support 30 markets while making market #11–30 progressively painful to operate.

For example, VTEX explicitly supports localized cross-border stores with different pricing, logistics and language configurations, while allowing catalog and back-office integration strategies to be centralized. VTEX Developers

My initial ranking for the requirements you gave:
1. commercetools → 2. Adobe Commerce → 3. SAP Commerce Cloud (if SAP-heavy) → 4. VTEX → 5. BigCommerce Enterprise / Shopify Plus depending on how much customization you actually need.

If you give me your SKU count, number of markets, B2B vs B2C, ERP/PIM/OMS stack, number of storefronts, and approximate engineering team size, I can narrow this to 2–3 platforms and give you a weighted architecture/TCO comparison.

Almost all serious enterprise platforms can.

Instead, map your architecture like:

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

My shortlist

If I were leading the architecture

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

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

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

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

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

The architecture I'd want

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

I'd aim for something like:

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

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

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

The decision I'd make conditional on your situation

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

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

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

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

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

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

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

The architecture I'd want

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

I'd aim for something like:

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

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

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

The decision I'd make conditional on your situation

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

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

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

If I were the lead developer at a large retailer building a headless architecture for many storefronts, my default choice would be commercetools—unless your organization is already deeply invested in Salesforce or Shopify.

My ranking

Why I'd pick commercetools

For a large retailer, I'd optimize for independent storefront evolution, rather than simply asking which platform has the nicest headless APIs.

commercetools is particularly strong because it is API-first and modular: the commerce backend is deliberately separated from the experience layer, allowing multiple storefronts and channels to consume the same underlying commerce capabilities. commercetools commercetools

I'd structure it roughly like:

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Brand C Web
                    ├── Mobile App
                    ├── Marketplace
                    └── In-store / Kiosk
                           │
                     Experience Layer
                           │
                 ┌─────────┴─────────┐
                 │ Commerce APIs     │
                 │ commercetools     │
                 └─────────┬─────────┘
                           │
        ┌──────────┬───────┼────────┬─────────┐
        │          │       │        │         │
     Catalog    Pricing  Cart     Orders    Inventory
        │          │       │        │         │
        └──────────┴───────┴────────┴─────────┘
                           │
             ERP / PIM / OMS / CRM / Search

The important architectural property is that Brand A doesn't become a special case in the commerce backend. You can establish shared capabilities and let each storefront own its presentation, content, merchandising experience, and release cadence.

That becomes especially valuable if you have:

• Multiple brands
• Different countries/regions
• Different catalogs or assortments
• B2C + B2B
• Multiple currencies/tax regimes
• Different frontend teams
• Web + mobile + other channels
• A PIM/ERP/OMS that you don't want the commerce platform to own
• A long-term goal of replacing individual components independently

Salesforce is the strongest alternative

If you're already a major Salesforce customer, I'd seriously consider Salesforce Commerce Cloud + Composable Storefront.

Salesforce's current architecture provides Commerce APIs, React-based PWA Kit, and Managed Runtime, and explicitly supports multiple sites/storefronts from a common codebase. Developer Developer

It also has a particularly mature model for organizations with multiple sites and storefronts; Salesforce documents configurations ranging from one site/multiple storefronts through multiple sites/multiple storefronts. Salesforce

So my decision rule would be:

Already Salesforce-heavy → Salesforce Commerce Cloud.

Starting relatively fresh and want maximum composability → commercetools.

Where Shopify Plus fits

Shopify Shopify Plus would be my choice if the priority is getting many storefronts operational quickly with a relatively small engineering/operations burden.

It now supports headless storefronts using Hydrogen and Oxygen, and Plus provides expansion stores and centralized organization management. Shopify Help Center Shopify Help Center

But I'd be more cautious if your requirement is genuinely "large retailer + many independently evolving storefronts + deep customization." Shopify's expansion stores are operationally separate stores even though they can be centrally managed, and Plus has constraints around how brands/stores are organized. Shopify Help Center Shopify

In other words:

Shopify Plus optimizes for operational simplicity. commercetools optimizes for architectural freedom.

What I'd actually standardize

Regardless of platform, I wouldn't make the commerce platform the center of the entire architecture.

I'd establish:

• Commerce: commercetools
• Frontend: Next.js/React or equivalent
• CMS: composable CMS
• Search: dedicated search engine
• PIM: authoritative product source
• OMS: authoritative order/fulfillment source
• CDP/CRM: customer identity and behavioral data
• API gateway/BFF: storefront-specific aggregation
• Event backbone: Kafka/Pub/Sub/etc.
• Observability: centralized tracing, metrics and logs
• Design system: shared components with brand-level theming

The key is to make storefronts disposable. If Brand C wants a radically different frontend six months from now, you should be able to replace its frontend without re-platforming commerce.

My recommendation

For your stated scenario, I'd shortlist commercetools and Salesforce Commerce Cloud, with Shopify Plus as the pragmatic alternative.

If you tell me roughly how many storefronts, brands, countries, SKUs, annual orders, and whether you already use Salesforce/Adobe/Shopify, I can give you a much more concrete architecture decision—including commercetools vs Salesforce vs Shopify, estimated engineering complexity, and the organizational/team implications.

Shopify Shopify Plus would be my choice if the priority is getting many storefronts operational quickly with a relatively small engineering/operations burden.

It now supports headless storefronts using Hydrogen and Oxygen, and Plus provides expansion stores and centralized organization management. help.shopify.com help.shopify.com

But I'd be more cautious if your requirement is genuinely "large retailer + many independently evolving storefronts + deep customization." Shopify's expansion stores are operationally separate stores even though they can be centrally managed, and Plus has constraints around how brands/stores are organized.

In other words:

Shopify Plus optimizes for operational simplicity. commercetools optimizes for architectural freedom.

What I'd actually standardize

Regardless of platform, I wouldn't make the commerce platform the center of the entire architecture.

I'd establish:

For B2B with custom/account pricing, POS, and large order volumes, I’d shortlist:

• Shopify Plus — strong unified B2B + POS, managed infrastructure, and increasingly robust native B2B pricing/catalog features. Shopify Shopify
• Adobe Commerce — worth considering if pricing rules, quoting, account hierarchies, and deep customization are unusually complex. experienceleague.adobe.com experienceleague.adobe.com
• BigCommerce B2B Edition — strong middle ground for complex B2B pricing and high-volume catalogs, particularly if you want SaaS rather than self-hosting. Shopify

Key question: if POS is a core requirement, Shopify Plus deserves especially close evaluation; if sophisticated B2B pricing/quoting and ERP integration dominate, Adobe Commerce becomes more compelling.

For a B2B division with custom pricing, POS requirements, and large order volumes, I would focus less on “ecommerce platforms” and more on enterprise commerce platforms that can unify pricing, inventory, customer accounts, and order workflows. The best fit depends heavily on whether you are a distributor, manufacturer, retailer, or a B2B arm of an existing brand. Shopify KIBO Commerce

A shortlist I would evaluate:

Shopify Alkali## My likely recommendation by scenario

If you are a distributor/manufacturer

I would start with:

1. Adobe Commerce — if you have complex pricing, thousands of SKUs, multiple customer tiers, negotiated contracts, or ERP-driven pricing.
2. OroCommerce — if B2B workflows are the heart of the business.
3. BigCommerce Enterprise — if you want SaaS simplicity but still need serious B2B capability.

If you have retail stores + wholesale/B2B

I would look at:

1. Shopify Plus — especially if POS is a major requirement and you want one ecosystem for stores, online, and B2B.
2. BigCommerce — if the B2B side is more complex than the retail side.

If order volume is very large

Prioritize:

• ERP integration (SAP, Oracle, NetSuite, Dynamics, etc.)
• real-time inventory availability
• customer-specific price engines
• bulk ordering/reorder tools
• approval workflows
• EDI/punchout procurement support
• API scalability

A common mistake is choosing a platform that can “take orders” but cannot reliably handle contract pricing + customer entitlements + inventory + sales workflows at scale. Capterra

A few questions would narrow this down significantly:

1. What ERP are you running (SAP, NetSuite, Dynamics, custom, none)?
2. Is POS already in place, and which system?
3. Approximate scale: annual B2B revenue, number of customers, SKUs, and monthly orders?
4. Do customers have negotiated pricing/contracts, or mostly tiered volume pricing?
5. Are you selling direct to consumers too, or only B2B?

For a digital-first enterprise whose primary goal is true frontend/backend decoupling, I’d put commercetools at the center of the shortlist. The important caveat is that “best” depends heavily on whether you want maximum architectural independence or maximum operational simplicity.

Enterprise shortlist

Why I'd investigate commercetools first

commercetools is designed around an API-first, composable model rather than treating headless as merely “a custom frontend on top of a conventional ecommerce platform.” That distinction matters if your long-term architecture is something like:

Next.js/React frontend → API gateway/BFF → commerce services → ERP/OMS/PIM/CMS/search/payments

rather than:

Custom frontend → one vendor's monolithic commerce backend

Current 2026 comparisons consistently position commercetools toward large enterprises with complex B2B/B2C requirements and substantial engineering capability. CIOPages Naturaily Netguru

Its main tradeoff is also its strength: you own more of the architecture. You'll need strong platform engineering, integration architecture, observability, caching, release management, and ownership of the services surrounding commerce.

When I'd choose Shopify instead

Shopify + Hydrogen is compelling if your objective is:

“We want a completely custom frontend, but we don't want to operate commerce infrastructure.”

Shopify's Storefront API is framework-agnostic, while Hydrogen provides its React-oriented headless framework and Oxygen provides hosting. Shopify Shopify

That gives you substantial frontend independence while retaining Shopify's managed catalog, checkout, orders, payments, and operational infrastructure. Shopify also reports handling very large checkout volumes and provides enterprise production/technical support. Shopify Shopify

The architectural tradeoff is that Shopify remains your commerce core. If your eventual goal is to replace or radically customize pricing, promotions, checkout, order orchestration, etc., commercetools gives you more room to do that.

Salesforce is particularly relevant if you're already a Salesforce enterprise

Salesforce Commerce Cloud's Composable Storefront separates the React storefront from commerce data/business logic using Commerce API, PWA Kit and its managed runtime. Salesforce explicitly supports augmenting it with external search, CMS and other vendors. Developer Salesforce

So if your enterprise already has substantial Salesforce CRM/Customer 360 infrastructure, the integration economics can be quite different from evaluating it as a standalone commerce platform.

The decision I'd make architecturally

For a large digital-first enterprise, I'd frame the shortlist like this:

• Maximum composability / architectural independence: commercetools
• Custom frontend + minimum commerce infrastructure to operate: Shopify Plus + Hydrogen
• Deep Salesforce ecosystem: Salesforce Commerce Cloud
• Managed platform with relatively open headless capabilities: BigCommerce Enterprise
• Maximum code ownership/control: Saleor or Medusa, assuming you have the platform engineering organization to operate them

One particularly important distinction: headless ≠ composable. Headless decouples the presentation layer; composable also gives you the ability to replace pieces of the underlying commerce stack. Salesforce's own documentation makes this distinction explicitly. Salesforce

So if by “decouple frontend and backend” you mean genuine long-term architectural independence, I'd start the enterprise evaluation with commercetools vs. Shopify Plus, rather than comparing a dozen headless vendors.

If you tell me your annual GMV, B2C vs B2B, number of countries/storefronts, catalog size, ERP/OMS (SAP/Oracle/etc.), and whether you have a dedicated platform engineering team, I can turn this into an enterprise architecture comparison covering TCO, scalability, APIs, checkout, multi-region, B2B, integrations, and vendor lock-in.

rather than:

Custom frontend → one vendor's monolithic commerce backend

Current 2026 comparisons consistently position commercetools toward large enterprises with complex B2B/B2C requirements and substantial engineering capability. CIOPages Naturaily Netguru

Its main tradeoff is also its strength: you own more of the architecture. You'll need strong platform engineering, integration architecture, observability, caching, release management, and ownership of the services surrounding commerce.

When I'd choose Shopify instead

Shopify + Hydrogen is compelling if your objective is:

“We want a completely custom frontend, but we don't want to operate commerce infrastructure.”

Shopify's Storefront API is framework-agnostic, while Hydrogen provides its React-oriented headless framework and Oxygen provides hosting. Shopify Shopify

That gives you substantial frontend independence while retaining Shopify's managed catalog, checkout, orders, payments, and operational infrastructure. Shopify also reports handling very large checkout volumes and provides enterprise production/technical support. Shopify Shopify

The architectural tradeoff is that Shopify remains your commerce core. If your eventual goal is to replace or radically customize pricing, promotions, checkout, order orchestration, etc., commercetools gives you more room to do that.

Salesforce is particularly relevant if you're already a Salesforce enterprise

Salesforce Commerce Cloud's Composable Storefront separates the React storefront from commerce data/business logic using Commerce API, PWA Kit and its managed runtime. Salesforce explicitly supports augmenting it with external search, CMS and other vendors. developer.salesforce.com salesforce.com

So if your enterprise already has substantial Salesforce CRM/Customer 360 infrastructure, the integration economics can be quite different from evaluating it as a standalone commerce platform.

The decision I'd make architecturally

For a large digital-first enterprise, I'd frame the shortlist like this:

Yes. If seasonal spikes are your primary concern, I’d prioritize managed SaaS/cloud-native platforms over self-hosted ecommerce stacks. The important distinction is not just “can it scale?” but how much of the scaling, failover, caching, and peak-season preparation you have to operate yourselves.

My shortlist

My default choice for pure seasonal resilience: Shopify Plus. Shopify says its infrastructure automatically handles peak demand, and its 2025 BFCM infrastructure reached 489 million requests/minute across the platform. It also provides CDN/DDoS protection and automatic platform updates. Shopify Shopify Help Center

shopify.com

Salesforce Commerce Cloud is a particularly strong alternative if you're already heavily invested in Salesforce. Salesforce explicitly designs Commerce Cloud for massive traffic spikes, and its current peak-season guidance covers load preparation and troubleshooting. Salesforce Salesforce

salesforce.com

commercetools is my pick when you need architectural flexibility rather than an all-in-one platform. Its cloud-native, microservices approach is designed for independent scaling and resilience; its reported Cyber Week 2025 operation processed 31M orders with 100% uptime according to the company. commercetools commercetools

commercetools.com

Adobe Commerce is attractive when customization and complex B2B/B2C requirements outweigh operational simplicity. Its current cloud service automatically adjusts resources for peak traffic/orders, while its cloud infrastructure supports horizontal and vertical autoscaling. Experience League Experience League

experienceleague.adobe.com

What I'd choose

If you tell me roughly annual GMV, peak orders/minute, number of SKUs, B2B vs B2C, and whether you need ERP/OMS integrations, I can narrow this to 2–3 platforms and compare their failure modes, autoscaling, peak capacity, cost model, and migration risk.

If language + cultural localization is the deciding factor, I’d put Shopify at the top for most global brands—particularly Shopify Plus for larger enterprises.

My ranking

*Primarily through plugins/integrations rather than the core platform.

Why Shopify is my first choice

Shopify Markets is unusually strong at treating localization as more than simply translating text. You can tailor language, currency, pricing, product availability, domains, taxes, and even theme content by market. Shopify Help Center Shopify Help Center

Its translation system also lets you go beyond literal translation. Translate & Adapt supports automatic and manual translations, while allowing market-specific versions of product descriptions, promotional messaging, and legal text. That's important when you're adapting for culture rather than merely changing English into French or German. Shopify Help Center Shopify Help Center

For SEO, Shopify can automatically generate hreflang markup and serve translations through localized subfolders, subdomains, or country-specific domains. Shopify Help Center

Shopify also supports up to 30 languages on Shopify Plus/Enterprise Commerce, compared with up to 20 on its lower plans. Shopify Help Center

Where BigCommerce may actually be better

If your organization wants substantially different storefronts for different countries, rather than one store with localized experiences, I'd take a close look at BigCommerce Multi-Storefront.

It can localize not just language and currency but catalogs, pricing, checkout, promotions, payment methods, shipping, tax settings, emails, and other storefront content. BigCommerce BigCommerce

That's particularly compelling for a brand where, for example:

• 🇺🇸 US has one assortment and pricing strategy
• 🇯🇵 Japan has a different assortment, imagery and messaging
• 🇩🇪 Germany has different tax/checkout requirements
• 🇫🇷 France needs French-language merchandising
• 🇬🇧 UK has its own pricing and promotional strategy

BigCommerce's architecture makes those regional storefront distinctions quite explicit. BigCommerce

The important distinction

If by "translation" you mean high-quality linguistic translation with human/AI translation workflows, I wouldn't choose an ecommerce platform solely on its native translation feature. The strongest global setups often combine the ecommerce platform with a dedicated localization/translation system.

If by "localization" you mean language + culture + currency + pricing + catalog + content + SEO + regional merchandising, then:

🥇 Shopify Plus — best overall balance and easiest to operate
🥈 BigCommerce — excellent for genuinely differentiated regional storefronts
🥉 Adobe Commerce — extremely powerful, but much more implementation-heavy

For a global consumer brand operating in 10+ countries, my default recommendation would be Shopify Plus + a professional localization/translation workflow, rather than trying to make the ecommerce platform's built-in translator do everything.

If you tell me how many countries/languages you need and whether you're B2C, B2B, or both, I can give you a more rigorous Shopify vs. BigCommerce vs. Adobe Commerce recommendation.

If your organization wants substantially different storefronts for different countries, rather than one store with localized experiences, I'd take a close look at BigCommerce Multi-Storefront.

It can localize not just language and currency but catalogs, pricing, checkout, promotions, payment methods, shipping, tax settings, emails, and other storefront content.

That's particularly compelling for a brand where, for example: