Neutral mentions of BigCommerce

For an enterprise catalog with thousands of SKUs, complex pricing, and likely B2B workflows, I would focus less on “which ecommerce platform has the most features” and more on how well it handles:

• customer-specific pricing and contract pricing
• multiple price lists
• large product attribute models
• ERP/PIM integration
• buyer permissions and account hierarchies
• quote/RFQ workflows
• bulk ordering and repeat purchases
• regional catalogs, currencies, and inventory rules

Complex B2B catalogs often need these capabilities natively rather than through many custom extensions. Elastic Path Webscale

Platforms I would shortlist

Shopify Alkali## My likely recommendations by scenario

If you are a distributor/manufacturer

Look hardest at:

1. Adobe Commerce
2. OroCommerce
3. SAP Commerce Cloud (especially if SAP ERP is central)

These are stronger when your pricing model looks like:

• Customer A gets negotiated prices
• Customer B sees a different catalog
• Volume breaks change pricing
• Sales reps negotiate quotes
• Buyers have approval chains

Alkali Ivris Tech### If your catalog is huge but you want flexibility

Consider:

• commercetools
• Elastic Path

These work well when commerce is one layer in a broader architecture with ERP, PIM, search, pricing engines, and custom customer experiences. Elastic Path

If you want faster implementation and lower operational overhead

Consider:

• BigCommerce
• Shopify Plus

They can be excellent choices if your pricing complexity is manageable and you value SaaS simplicity. Shopify

Questions that would narrow this down quickly

1. Is this primarily B2B, B2C, or both?
2. How many SKUs: ~5,000, 50,000, 500,000+?
3. Where does pricing live today: ERP, CPQ system, spreadsheets, ecommerce platform?
4. Which ERP/PIM do you use (SAP, Oracle, NetSuite, Dynamics, Infor, custom)?
5. Do customers need login-based catalogs with negotiated pricing?
6. Are you replacing an existing platform or starting fresh?

With those answers, the shortlist usually shrinks from ~8 platforms to 2–3 realistic candidates.

For thousands of SKUs + complex pricing, I’d focus less on storefront features and more on how well the platform handles catalog scale, customer-specific price lists, contract pricing, quantity breaks, ERP/PIM integration, and rules-driven pricing.

My shortlist

If pricing is the hard part, I'd start with Adobe Commerce

Adobe Commerce's B2B functionality is particularly relevant to your situation. It supports shared catalogs with company-specific product selections and pricing, multiple pricing structures, customer/company assignments, tier pricing, and catalog price rules. experienceleague.adobe.com

It also supports pricing at website scope and has explicit mechanisms for managing large numbers of shared catalogs; Adobe recommends its direct-product price-assignment capability when merchants have many shared catalogs. experienceleague.adobe.com

I'd therefore put it at the top if your pricing looks something like:

SKU × customer/account × region × quantity × contract × channel × effective date

Shopify Plus is the "simpler operations" alternative

Shopify Plus has become considerably more capable for B2B. Its catalogs can control both product availability and customer-specific pricing, and Plus allows unlimited B2B catalogs and direct assignment to companies/company locations. It also supports quantity rules and volume pricing. help.shopify.com

I'd favor it when your pricing can be represented reasonably cleanly as catalogs/price lists rather than requiring a highly customized pricing engine.

Consider composable if your catalog/pricing is really complicated

commercetools is attractive when you have an engineering organization capable of building around APIs and you want commerce to be one component of a broader architecture. Shopify's current enterprise comparison also places commercetools among the platforms aimed at custom catalogs, pricing and account hierarchies. www.shopify.com

Similarly, SAP Commerce Cloud becomes particularly compelling if SAP is already the system of record for products, customers, contracts, inventory and pricing.

One important caveat

"Thousands of SKUs" by itself isn't particularly scary for modern enterprise platforms. The number of pricing relationships is what I'd use to choose the architecture.

For example, there's a huge difference between:

• 50,000 SKUs × 10 price lists
• 50,000 SKUs × 5,000 customers
• 50,000 SKUs × customer-specific contracts × quantity breaks × currencies × regions
• prices calculated dynamically from an ERP/CPQ rather than stored in ecommerce

In the last two cases, I'd be much more cautious about selecting a platform primarily because its admin UI handles large catalogs.

My initial recommendation: shortlist Adobe Commerce, Shopify Plus, and commercetools, then add SAP Commerce Cloud if you're SAP-centric and Salesforce Commerce Cloud if Salesforce is your commercial backbone.

If you tell me (1) approximate SKU count, (2) number of customers, (3) B2B vs B2C, (4) what determines a price, and (5) your ERP/PIM, I can narrow this to 2–3 platforms and explain which architecture I'd choose.

If you’re a developer building a fully custom frontend and your priorities are flexibility, clean APIs, and avoiding frontend constraints, I’d generally rank the options like this:

PowerGate Software Naturaily## My recommendation by developer profile

If you’re building with Next.js + TypeScript

I’d start with Medusa.

Why:

• Same ecosystem as your frontend (TypeScript/Node)
• You can customize checkout, pricing, fulfillment, promotions, and workflows
• No fighting a SaaS platform’s internal assumptions
• Good fit for custom product experiences, marketplaces, subscriptions, or unusual flows

The tradeoff: you own more infrastructure and operational complexity. Hunchbite

If you want the cleanest API model

Look hard at Saleor.

Strengths:

• GraphQL-first
• Strong product/catalog modeling
• Good fit for multi-channel and B2B scenarios
• Open source and self-hostable

The tradeoff:

• Python/Django backend
• Smaller ecosystem than Shopify
• More backend complexity if your team is primarily JS/TS. Hunchbite

If this is a large enterprise architecture

Choose commercetools.

It shines when you need:

• Multiple brands/storefronts
• Complex pricing rules
• International markets
• ERP/PIM/CRM integrations
• A composable architecture

The downside is cost and implementation effort. Naturaily

When Shopify is still the right answer

A lot of developers underestimate Shopify because it is less "pure" headless. It is still a strong choice when you need:

• Reliable checkout
• Payments handled
• Huge app ecosystem
• Merchandising tools
• Non-technical operators managing the store

But if your goal is "I want the commerce backend to behave like my own service," Shopify can feel restrictive. Naturaily

My default stack for a custom frontend in 2026

For a greenfield build:

Frontend

• Next.js / React
• Tailwind
• Custom design system

Commerce

• Medusa (most cases)
• Saleor (GraphQL-heavy teams)
• commercetools (enterprise)

Supporting services

• Headless CMS: Sanity, Contentful, Strapi, etc.
• Search: Algolia, Meilisearch, Elasticsearch
• Payments: Stripe
• Auth: Auth.js, Clerk, custom OAuth

Short answer

• Maximum flexibility: Medusa or Saleor
• Best enterprise API architecture: commercetools
• Fastest path to production: Shopify headless
• Best fit for a TypeScript developer: Medusa

If you tell me your stack (Next.js? React Native? mobile app too?), catalog size, B2C vs B2B, and whether you need custom checkout logic, I can narrow it down.

For a developer building a custom frontend, the “best” headless commerce platform depends on whether you want maximum control or minimum backend work. The strongest options today fall into a few categories. Naturaily Netguru

My shortlist for flexibility + APIs

PowerGate Software Naturaily## If I were choosing as an engineer

1. Maximum flexibility: commercetools

Pick this if your frontend is a competitive advantage and you expect complex requirements:

• Multiple storefronts
• Multi-region catalogs
• Custom pricing rules
• B2B workflows
• ERP/PIM/OMS integrations
• Marketplace or marketplace-like models

Its APIs and data model are designed around composable commerce rather than extending a traditional ecommerce platform. LaunchTry Netguru

Typical stack:

• Next.js / React frontend
• commercetools APIs
• Contentful/Sanity for CMS
• Algolia/Elastic for search
• Custom backend-for-frontend layer

Downside: you own a lot of architecture.

2. Best developer experience: Medusa

For a smaller engineering team that wants control, I would seriously consider Medusa.

Good fit if you want:

• TypeScript/Node ecosystem
• Own your database and infrastructure
• Custom checkout logic
• Custom product models
• Your own APIs/services around commerce

It feels closer to building your own commerce engine without starting from zero. Guideflow Pharos Production

3. Best GraphQL-first option: Saleor

Saleor is attractive if your team likes GraphQL and Python.

Strengths:

• Clean GraphQL API
• Open source
• Good fit for custom storefronts
• Strong developer control

Less ideal if you need a huge ecosystem of ready-made commerce integrations.

4. Pragmatic choice: Shopify headless

If the business wants to sell quickly, Shopify is hard to ignore.

You get:

• Payments
• Checkout
• Admin tooling
• Inventory/order workflows
• Huge app ecosystem

Then build your frontend separately using the Storefront API/Hydrogen approach. Vendure

The limitation is that Shopify remains the commerce core; you are customizing the experience around it rather than owning the entire commerce model.

My ranking by scenario

• Building a unique commerce product/platform: Medusa or commercetools
• Enterprise retailer with many channels: commercetools
• Startup with strong engineering team: Medusa
• Content-heavy brand site: Shopify headless + modern CMS
• B2B with complex pricing/workflows: commercetools, Medusa, or Elastic Path
• Need to launch in months, not years: Shopify headless

For a greenfield custom frontend, my default picks would be:

1. Medusa if your team wants ownership and speed of iteration
2. commercetools if this is a serious enterprise commerce platform
3. Shopify headless if business operations matter more than backend freedom

A few questions would change the recommendation significantly:

• Are you building B2C, B2B, or marketplace?
• Expected scale (SKUs/orders/day)?
• Frontend stack (Next.js, React Native, Vue, etc.)?
• Do you need custom checkout/pricing logic, or mostly a custom UI?

For a brick-and-mortar + online business, Shopify is probably the best default choice if you want one system to be the inventory “source of truth.”

My shortlist

Shopify's current setup can sync inventory across stores, warehouses, your online store, social channels, and marketplaces, with stock adjusting as products are sold, returned, transferred, or received. Shopify Shopify

It also supports genuinely omnichannel workflows such as buy online/pick up in store, buy in store/ship to customer, online returns in store, and ship-from-store. Shopify Shopify

shopify.com

When I'd choose something else

• Choose Lightspeed if your physical retail operation is the center of the business and you need particularly strong retail/POS functionality.
• Choose Cin7 if you have multiple warehouses, lots of SKUs, wholesale/B2B, Amazon/eBay/Walmart, kitting/bundles, or complicated purchasing and fulfillment. In that scenario, a dedicated inventory/OMS layer can be more appropriate than making the ecommerce platform the inventory brain.
• Choose Square if you're relatively small and primarily need straightforward store + website inventory without a lot of operational complexity.

The key question

The best platform actually depends heavily on what your other channels are.

If you tell me:

1. What ecommerce platform you use now (Shopify, WooCommerce, BigCommerce, etc.)
2. Your POS
3. Marketplaces (Amazon, eBay, Walmart, Etsy, etc.)
4. Rough number of SKUs
5. Number of physical locations/warehouses
6. Whether you do wholesale/B2B

…I can narrow it down to 2–3 specific setups and tell you which one I'd pick for your business, including where the inventory master should live.

For a subscription-box business, I’d start with Shopify + a dedicated subscription app rather than choosing an ecommerce platform based on recurring billing alone.

My picks

1. Best overall for a new subscription box: Shopify + Appstle.
Shopify's current subscription-app ecosystem specifically supports subscription boxes, and Appstle is one of the prominent options. Shopify highlights Appstle's ability to handle curated boxes, customer skip/pause controls, and subscription-specific workflows. www.shopify.com

2. Best if you expect to scale: Shopify + Recharge/Skio.
Skio is particularly interesting if your boxes involve build-a-box, prepaid plans, different delivery cadences, sophisticated payment recovery, or retention flows. Its current plans support Subscribe & Save, prepaid subscriptions, and Build-a-Box, while its billing system handles recurring order generation and payment retries. help.skio.com

One important 2026 wrinkle: Skio joined Recharge in June 2026, so I'd evaluate them as part of the same broader ecosystem rather than treating them as completely independent long-term bets. skio.com

3. Shopify Subscriptions is fine if your model is simple.
If every customer gets essentially the same box every month and you don't need elaborate customization, Shopify's native option keeps billing and store administration nicely unified. www.shopify.com

The fulfillment piece matters

I'd separate subscription billing from physical fulfillment in your architecture:

Shopify → subscription app → orders → 3PL/fulfillment provider

That gives you freedom to change warehouses later without migrating your subscription customers. For boxes involving kitting several products together, look specifically for a 3PL that supports kitting/bill-of-materials, not merely pick-and-pack. Current fulfillment guidance emphasizes that subscription businesses eventually need the commerce platform, billing engine, 3PL, carriers, and inventory systems to work together. www.swell.is

What I'd choose

If you're just launching: Shopify + Appstle + a subscription-friendly 3PL.

If you already expect hundreds/thousands of subscribers, customized boxes, or aggressive retention marketing: Shopify + Recharge/Skio + a capable 3PL.

If you tell me (1) what goes in the box, (2) monthly price, (3) expected subscribers in year 1, and (4) whether customers choose their contents, I can narrow this down to the best 2–3 setups and compare their likely costs.

If your primary goal is minimizing PCI compliance effort and security operations, a fully hosted SaaS ecommerce platform is usually the best choice. The platform should handle the infrastructure, checkout security, patching, and payment environment so your team focuses on merchant-side controls (accounts, apps, policies, and access). LeadingIT Shopify

A practical ranking for lowest compliance burden:

BigCommerce WooCommerce## My recommendation by priority

If you want the least compliance overhead: Shopify

Shopify is usually the easiest route because it is a fully managed platform: hosting, infrastructure security, SSL, and payment handling are largely handled by Shopify. Your responsibilities are mainly operational:

• Use strong admin passwords and MFA
• Limit staff access
• Vet installed apps
• Avoid storing cardholder data yourself
• Complete any required PCI self-assessment steps for your payment setup

Shopify Shopify### If you need more enterprise commerce features: BigCommerce

BigCommerce is also a strong choice for reducing operational burden. It provides hosted infrastructure and PCI DSS compliance support while giving merchants more native features for catalogs, B2B, and international selling. BigCommerce BigCommerce

If compliance simplicity matters more than customization: avoid self-hosted WooCommerce

WooCommerce can be secure, but the responsibility is more distributed: hosting, WordPress security, plugin updates, vulnerability management, backups, and configuration all become part of your compliance program. WooCommerce

Features that reduce PCI scope regardless of platform

Look for:

• Hosted checkout (avoid handling raw card numbers)
• Tokenized payments
• Built-in MFA and role-based permissions
• Automatic security updates
• Minimal third-party plugins/apps
• Clear PCI documentation and Attestation of Compliance (AOC)

A common “low-burden” setup is:
Shopify + Shopify Payments (or another hosted PCI-compliant gateway) + minimal apps + MFA enforced for all admins. Shopify

If you tell me your size (startup, SMB, enterprise), whether you need B2B features, and whether you have an IT/security team, I can narrow this to a shortlist.

If your priority is minimizing PCI DSS compliance work, I’d generally favor a fully hosted SaaS ecommerce platform with a hosted/redirected checkout, rather than a self-hosted platform.

My shortlist

The important distinction is that “PCI compliant platform” does not mean your business has zero PCI responsibilities. PCI SSC explicitly says even merchants using outsourced payment processing can have responsibilities such as securing their web environment and, under current SAQ A rules, external vulnerability scanning. PCI Security Standards Council PCI Security Standards Council

What I'd choose

For the least compliance headache: Shopify + Shopify Payments, assuming Shopify Payments is available for your business and meets your payment requirements.

The architectural principle matters more than the brand, though: keep raw card data completely out of your infrastructure. PCI SSC says merchants can qualify for the simpler SAQ A path when the payment page's elements originate directly from a PCI-validated third party. PCI Security Standards Council PCI Security Standards Council

A redirect to a fully hosted payment page is particularly attractive from a compliance perspective. PCI SSC distinguishes this from payment forms generated by your own site: the latter can put substantially more security controls on you. PCI Security Standards Council PCI Security Standards Council

One wrinkle: embedded payment iframes aren't necessarily equivalent to a redirect anymore. Under PCI DSS v4.0.1, SAQ A has additional requirements concerning script attacks for merchants using embedded payment pages, whereas those particular criteria don't apply to redirect-based checkout. PCI Security Standards Council PCI Perspectives

So, if I were ranking purely for “I want the smallest PCI/security team burden”:

1. Shopify with hosted checkout
2. BigCommerce with hosted checkout
3. Wix with hosted checkout
4. WooCommerce + hosted payment provider
5. Self-hosted/custom ecommerce + payment API — highest burden

If you tell me your approximate annual sales, number of orders, B2C vs. B2B, countries you sell into, and whether you need subscriptions, I can narrow this to the best 2–3 choices and compare their actual PCI responsibilities.

The important distinction is that “PCI compliant platform” does not mean your business has zero PCI responsibilities. PCI SSC explicitly says even merchants using outsourced payment processing can have responsibilities such as securing their web environment and, under current SAQ A rules, external vulnerability scanning. PCI Security Standards Council PCI Security Standards Council

What I'd choose

For the least compliance headache: Shopify + Shopify Payments, assuming Shopify Payments is available for your business and meets your payment requirements.

The architectural principle matters more than the brand, though: keep raw card data completely out of your infrastructure. PCI SSC says merchants can qualify for the simpler SAQ A path when the payment page's elements originate directly from a PCI-validated third party. PCI Security Standards Council PCI Security Standards Council

A redirect to a fully hosted payment page is particularly attractive from a compliance perspective. PCI SSC distinguishes this from payment forms generated by your own site: the latter can put substantially more security controls on you. PCI Security Standards Council PCI Security Standards Council

One wrinkle: embedded payment iframes aren't necessarily equivalent to a redirect anymore. Under PCI DSS v4.0.1, SAQ A has additional requirements concerning script attacks for merchants using embedded payment pages, whereas those particular criteria don't apply to redirect-based checkout.

So, if I were ranking purely for “I want the smallest PCI/security team burden”:

If you’re an agency building and maintaining stores for multiple clients, I’d pick Shopify for most agency workflows—especially after Shopify’s 2026 changes to Partner organizations.

My ranking

1. Shopify — best overall for an agency

The big advantage is that Shopify now treats your agency itself as an organization. As of March 2026, Shopify consolidated dev stores, client-transfer stores, and collaborator stores into the Partner Dev Dashboard, with organization-level roles and permissions. Shopify Shopify

That maps very nicely to an agency workflow:

Agency
→ developers/designers/project managers
→ Client A store
→ Client B store
→ Client C store
→ dev stores / staging
→ transferred production stores

You can give employees roles such as Store Admin, Store User Admin, App Developer, etc., and scope store access rather than giving everyone unrestricted access to everything. Shopify Help Center Shopify Help Center

For new client builds, Shopify's client transfer stores are particularly useful: you build the store under your Partner organization, then transfer ownership to the client when it's ready, while retaining collaborator access for ongoing work. Shopify

shopify.com

2. BigCommerce — potentially better for true multi-store operations

There's an important distinction here.

If by "multi-store management" you mean:

We have 20 different client brands, each with its own independent store

Shopify is probably the better agency ecosystem.

But if you mean:

One client has 5–20 storefronts/brands/regions and we want them all operating from one commerce backend

I'd seriously consider BigCommerce.

Its Multi-Storefront architecture lets you manage multiple storefronts from a single BigCommerce store/account, while sharing products/catalog infrastructure and centralizing orders, customers and analytics. Each storefront can have its own branding, domain, currency, pricing, etc. BigCommerce BigCommerce

bigcommerce.com

The key distinction

I'd choose based on your agency's business model:

Agency → lots of independent clients → Shopify

You want:

• Easy client handoff
• Huge app ecosystem
• Strong theme ecosystem
• Easy hiring/training
• Partner tooling
• Dev → client transfer workflow
• Granular employee access
• Lots of third-party integrations

One enterprise client → many storefronts → BigCommerce

You want:

• One catalog powering multiple storefronts
• Shared backend
• Different brands/regions/domains
• Centralized operations
• B2B + B2C
• More complex commerce architecture

What I'd do if I were building your agency

I'd standardize your agency around Shopify + Shopify Partners, and build an internal operating model like:

Agency Shopify Organization
│
├── Dev / Staging Stores
│
├── Client A
│   └── Production Store
│
├── Client B
│   └── Production Store
│
├── Client C
│   └── Production Store
│
└── Internal Tools / Apps / Themes

Then create standardized roles for developers, designers, PMs, and account managers, rather than sharing credentials. Shopify's new Partner organization model is specifically designed around this kind of structure. Shopify

One caveat: if your actual requirement is "I want one admin where my agency can operate 50 completely separate client stores, switch between them, push products/themes/apps across them, and monitor them all centrally," that's a more specific requirement than simply "multi-store." In that case, I'd compare Shopify Partners vs BigCommerce Multi-Storefront vs a third-party agency management layer rather than automatically choosing Shopify.

If you tell me roughly how many stores you expect (10 / 50 / 500), whether they're independent clients or multiple stores per client, and whether you need centralized product/order management, I can recommend the architecture I'd use.

There's an important distinction here.

If by "multi-store management" you mean:

We have 20 different client brands, each with its own independent store

Shopify is probably the better agency ecosystem.

But if you mean:

One client has 5–20 storefronts/brands/regions and we want them all operating from one commerce backend

I'd seriously consider BigCommerce.

Its Multi-Storefront architecture lets you manage multiple storefronts from a single BigCommerce store/account, while sharing products/catalog infrastructure and centralizing orders, customers and analytics. Each storefront can have its own branding, domain, currency, pricing, etc. bigcommerce.com docs.bigcommerce.com

bigcommerce.com

The key distinction

I'd choose based on your agency's business model:

Agency → lots of independent clients → Shopify

You want:

If your priority is developer-friendly mobile commerce integrations, I’d put Shopify first for most teams.

Why Shopify wins

Shopify has unusually strong first-party mobile support. Its Storefront API handles products, search, carts and checkout, while Checkout Kit embeds Shopify checkout directly into iOS, Android, or React Native apps. Shopify also provides official iOS and Android client libraries. shopify.dev

That means your architecture can be roughly:

Mobile app → Shopify Storefront API → Shopify cart → Checkout Kit → Shopify payments/order

You don't have to build the complicated commerce infrastructure yourself.

Shopify mobile commerce docs

When I'd choose something else

BigCommerce is compelling if API flexibility is more important than turnkey mobile tooling. Its GraphQL Storefront API is specifically designed for frontend applications and covers catalog, carts, checkout and customer authentication. docs.bigcommerce.com

commercetools is stronger if you're building a sophisticated enterprise architecture. It has type-safe SDKs for TypeScript, Java/Kotlin, PHP and .NET, plus APIs for commerce, checkout and other services. It explicitly documents mobile/browser implementations. docs.commercetools.com

My recommendation

If you're building a new consumer mobile storefront and want to ship quickly, I'd choose Shopify.

If you're building a commerce platform where you need maximum control over the backend and business logic, I'd look harder at commercetools or BigCommerce.

If you tell me whether you're using React Native, Flutter, Swift/Kotlin, or another stack, I can also compare the actual mobile integration experience and API architecture for the top 3.

If your main priority is having the broadest and easiest-to-manage supplier ecosystem, I’d choose shopify.com.

My ranking for a multi-supplier dropshipping business

Why Shopify wins

Shopify has an unusually deep ecosystem of supplier and sourcing apps. Its own recommendations include Shopify Collective, Syncee, DropCommerce, Spocket, and others, while the App Store has integrations for AliExpress, Alibaba, CJ Dropshipping, print-on-demand suppliers, wholesale suppliers, and more. Shopify Help Center Shopify App Store

For example, DSers provides AliExpress/Alibaba/1688 connectivity, multi-supplier/agent management, supplier mapping, automatic inventory/price/order updates, and multi-channel management. Shopify App Store

That matters if your model is something like:

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations. BigCommerce BigCommerce

It also supports dropshipping tools such as Avasam and Spocket. BigCommerce

So I'd frame it this way:

• Shopify: best if you want to connect lots of existing suppliers quickly.
• BigCommerce: best if you eventually want to build sophisticated/custom supplier infrastructure.
• WooCommerce: best if you want maximum technical control and don't mind managing more infrastructure.

One important distinction

If by "supplier ecosystem" you mean you want to build a platform where hundreds/thousands of suppliers themselves connect to your store/network, rather than simply operating a dropshipping store using suppliers, my answer changes somewhat.

In that case, I'd look closely at BigCommerce vs Shopify, particularly their APIs, webhooks, catalog/variant handling, inventory synchronization, order routing, and multi-store capabilities. Those become more important than simply counting the number of dropshipping apps.

If you tell me whether you're planning (1) one dropshipping store with many suppliers, (2) multiple stores, or (3) a marketplace/platform connecting suppliers to retailers, I can give you a much more specific recommendation.

Customer → Shopify → supplier/agent A, B, C, D → fulfillment → tracking back to Shopify

You can mix suppliers rather than being locked into one sourcing network.

Where BigCommerce becomes interesting

If you're building something much larger and more operationally complex, I'd seriously consider BigCommerce.

BigCommerce has a large app ecosystem and particularly strong APIs/webhooks for building custom supplier integrations. Its documentation specifically highlights real-time webhooks, APIs, app extensions, and an App Marketplace with hundreds of integrations.

If the priority is tight monthly spend + solid core ecommerce, I’d narrow it to WooCommerce vs. Shopify.

My recommendation

1. WooCommerce — best if every dollar matters

WooCommerce itself has no monthly platform fee, unlimited products/orders, and no platform revenue share. You pay for hosting and only the extensions you actually need. WooCommerce currently estimates hosting at roughly $25–$350/month, although a small store can often operate toward the lower end of that range. WooCommerce WooCommerce

Core capabilities include:

• Product/catalog management
• Cart and checkout
• Payments
• Inventory
• Shipping
• Coupons
• Order management
• SEO/customization
• Lots of integrations

The catch is that you are responsible for more of the stack—hosting, updates, security, plugins, etc. WooCommerce

woocommerce.com

2. Shopify — best if you want less technical overhead

Shopify Basic is currently $29/month when billed annually ($39 month-to-month), with unlimited products, a full online store, checkout, inventory, multiple sales channels and in-person selling included. Shopify Shopify

That's a very strong package if you don't want to spend time maintaining WordPress and plugins.

The downside for a very budget-conscious business is that apps can gradually turn a $29/month store into a much more expensive one. Shopify also charges additional transaction fees when you use a third-party payment provider rather than Shopify Payments. Shopify

shopify.com

3. BigCommerce — probably unnecessary initially

BigCommerce is powerful and has more functionality built into the platform, but I'd only choose it if you already know you'll need things like more sophisticated catalog/B2B/multichannel capabilities. Its entry-level offering is around $29/month annually, so the price isn't dramatically different from Shopify, but it may be more platform than you need. Shopify

What I'd do

If your monthly software budget is under ~$50: start with WooCommerce.

If ~$30–$75/month is comfortable and you value simplicity: choose Shopify Basic.

If you have unusual B2B/catalog requirements: consider BigCommerce.

For a lean ecommerce operation, I'd actually avoid buying a bunch of apps/extensions at launch. Get products → checkout → payments → shipping → inventory → basic analytics/SEO working first, then add functionality only when there's a demonstrated business need.

If you tell me your approximate monthly software budget (e.g. $30, $50, $100) and whether you're selling physical or digital products, I can give you a much more specific stack.

For a tiny team selling internationally, I’d pick Shopify—specifically Shopify with Markets + Managed Markets.

My ranking

1. Shopify — simplest overall

• Markets lets you set up different countries/regions with local currencies and pricing. Shopify Help Center Shopify Help Center
• Managed Markets is the big advantage for a small team: it can handle international tax registration/remittance, duties, local payment methods, customs, and localization through its merchant-of-record arrangement. Shopify Help Center
• It can also give customers duties/taxes-inclusive pricing, reducing surprise charges at delivery. Shopify Changelog
• The tradeoff is cost: Managed Markets charges a 3.5% transaction fee on Basic/Grow/Advanced, plus 1.5% currency conversion, on top of Shopify Payments fees. Shopify Help Center
• Wix — simplest if you're mostly a website business

• Wix supports local-currency display and international payments, and integrates with Avalara for automated tax calculations. wix.com
• I'd choose it if ecommerce is relatively secondary to the website/brand experience.
• BigCommerce — powerful, but I'd avoid it for a tiny team unless you need its flexibility

• It can pair with Stripe Tax to automate VAT/GST/sales-tax calculations internationally. BigCommerce
• But you're likely to end up making more decisions about integrations and configuration than you would with Shopify.

The important distinction

There's a difference between "calculate the right tax at checkout" and "take international tax compliance off our plate."

If you want the latter, Shopify Managed Markets is the compelling option. Shopify describes it as handling the international merchant-of-record responsibilities, including tax registration/remittance and duties. Shopify Help Center

So for a 2–5 person team, my default would be:

Shopify → Shopify Payments → Markets → Managed Markets for countries where you don't want to manage local tax compliance yourself.

If you tell me what you're selling, where your company is based, and your top 3–5 countries, I can tell you whether Managed Markets is actually worth the fees for your situation.

If your priorities are self-hosting, ownership of the database, and a migration that doesn't become a giant custom-development project, I'd shortlist these:

My pick: WooCommerce

For a migration where you want full control without making the migration itself a major software project, WooCommerce is probably the safest choice. Product data lives in your WordPress database, and WooCommerce provides built-in CSV import/export plus WordPress-level migration options. WooCommerce

The enormous WordPress/WooCommerce ecosystem also means you're much more likely to find an existing importer for whatever hosted platform you're leaving.

If you're a larger/complex business: Shopware 6

I'd choose Shopware 6 Community Edition over WooCommerce if you have complex catalogs, multiple sales channels, B2B requirements, sophisticated pricing, or substantial integrations.

Shopware explicitly supports self-hosting with local data storage and extensive customization. It also has a dedicated Migration Assistant and migration documentation covering customers, orders, products and other store data. Shopware Shopware

One nice characteristic is that Shopware's migration process can be run iteratively against a staging store, allowing you to test and correct mappings before going live. Shopware

If you want maximum technical control: Medusa

Medusa is interesting if you have developers and want an API-first/headless architecture rather than a traditional all-in-one storefront.

Its current migration tooling specifically supports importing products, variants, prices, images, inventory, collections/categories, and potentially orders/customers from other platforms. Its API-based approach can be idempotent, resumable, and rerunnable, which is excellent for a complicated migration. Medusa Docs Medusa Docs

The tradeoff is that you'll be building more yourself. I wouldn't choose it just because you want to escape SaaS.

Bottom line

• Want the easiest migration + huge ecosystem: WooCommerce
• Want serious commerce capabilities + self-hosting: Shopware 6
• Have a strong development team + want an API/headless platform: Medusa
• Want something simpler and lightweight: OpenCart

One important distinction: "I own my data" and "I control my infrastructure" aren't quite the same thing. If your goal is genuinely to eliminate vendor dependency, I'd favor a platform where you can directly access the database, files, backups, and application code—not merely a platform that offers a "self-hosted" deployment.

If you tell me what hosted platform you're migrating from (Shopify, BigCommerce, Wix, Squarespace, etc.), approximate product/order count, and whether you need subscriptions/B2B/multiple stores, I can narrow this to one recommendation and explain exactly how I'd approach the migration.

If you're a larger/complex business: Shopware 6

I'd choose Shopware 6 Community Edition over WooCommerce if you have complex catalogs, multiple sales channels, B2B requirements, sophisticated pricing, or substantial integrations.

Shopware explicitly supports self-hosting with local data storage and extensive customization. It also has a dedicated Migration Assistant and migration documentation covering customers, orders, products and other store data. shopware.com docs.shopware.com

One nice characteristic is that Shopware's migration process can be run iteratively against a staging store, allowing you to test and correct mappings before going live. docs.shopware.com

If you want maximum technical control: Medusa

Medusa is interesting if you have developers and want an API-first/headless architecture rather than a traditional all-in-one storefront.

Its current migration tooling specifically supports importing products, variants, prices, images, inventory, collections/categories, and potentially orders/customers from other platforms. Its API-based approach can be idempotent, resumable, and rerunnable, which is excellent for a complicated migration.

The tradeoff is that you'll be building more yourself. I wouldn't choose it just because you want to escape SaaS.

Bottom line

If your priority is full control over data and a manageable migration from a hosted ecommerce platform, I’d usually shortlist these:

SwingIntel Open Source Groups## My practical recommendation

Choose WooCommerce if you want the smoothest exit from a hosted platform

WooCommerce is often the easiest migration path because it has mature import/export tooling and a large ecosystem. You can host it anywhere, own the database, and directly access products, customers, orders, content, and media. WooCommerce WooCommerce

Good choice if you have:

• Fewer than ~10,000 products (or a catalog that is not extremely complex)
• A marketing/content-heavy site
• A team comfortable managing WordPress
• A desire to avoid a large engineering project

Watch out for:

• Too many plugins creating maintenance issues
• Performance tuning as traffic and catalog size grow

Choose PrestaShop if you want a "real ecommerce system" without Magento complexity

PrestaShop is a standalone ecommerce application rather than a CMS plugin. It is a good middle ground for merchants who want product/catalog/order management built around commerce from the start. Elogic Commerce Datafirefly

Good choice if you have:

• Multiple languages or regions
• A traditional retail catalog
• A need for more ecommerce-native workflows

Choose Magento Open Source if your business is already complex

Magento gives the most flexibility, but the migration and ongoing operations are significantly more demanding. It makes sense when you need things like:

• Large catalogs
• Multiple stores
• Advanced pricing rules
• B2B purchasing workflows
• Heavy customization

It is usually not the "easy migration" choice. SwingIntel

Migration approach I’d use regardless of platform

1. Export everything first

• Products and variants
• Categories
• Customers
• Orders
• Discounts
• Reviews
• Images/files
• SEO URLs and metadata
• Run both systems temporarily

• Build the new store privately
• Import and validate data
• Test checkout, payments, emails, tax, shipping
• Preserve URLs

• Map old URLs to new URLs
• Keep redirects
• Monitor search traffic after launch
• Keep your data portable

• Use your own database backups
• Avoid storing critical business logic only in proprietary plugins
• Prefer open APIs and documented schemas

A simple rule of thumb

• Solo/small team → WooCommerce
• Growing retail brand → PrestaShop or Shopware
• Enterprise/B2B → Magento Open Source
• Engineering team wanting a custom stack → Saleor or Medusa

If you tell me what hosted platform you’re leaving (Shopify, BigCommerce, Wix, Squarespace, etc.), your product count, and whether you need subscriptions/B2B/multistore, I can narrow this down considerably.

For a nonprofit selling PDFs, training materials, and other digital downloads on a tight budget, I’d narrow it to two choices:

My recommendation

1. Payhip — best if you want the cheapest/easiest setup

payhip.com is probably where I’d start if you don’t already have a WordPress site or don't want to maintain software.

• $0/month on its Free Forever plan.
• Takes 5% per transaction, plus the normal Stripe/PayPal processing fee. Payhip Payhip
• Unlimited products and unlimited revenue even on the free plan.
• Handles file delivery automatically after purchase.
• Supports PDFs and multiple files, with files up to 5 GB. Payhip Payhip Help Center
• Supports pay-what-you-want pricing, which is particularly useful for nonprofits. For example, you can set a $10 minimum and let supporters pay $10, $15, $25, etc. Payhip Help Center
• Payhip says it offers charity discounts, so I'd contact them about your nonprofit status. Payhip

The big advantage is that you don't have to worry about hosting, download security, updates, backups, or configuring a payment system.

For a small nonprofit, I'd seriously consider this the default choice.

2. WooCommerce — best if you already use WordPress

woocommerce.com is my choice if you already have a WordPress website and are comfortable maintaining it.

WooCommerce itself is free and open source, with no monthly subscription and no revenue share. WooCommerce WooCommerce It natively supports downloadable products, including controls for how customers receive their files. WooCommerce

That means your basic stack could be:

WordPress → WooCommerce → Stripe/PayPal → PDF download

Your main costs would be hosting and payment-processing fees. WooCommerce currently estimates typical hosting at roughly $25–$350/month, although a very small nonprofit store can potentially operate below that depending on the host and setup. WooCommerce

The upside is ownership and flexibility: your website, customer data, products, and store aren't locked into a SaaS platform.

The downside is that you're responsible for WordPress/WooCommerce updates, backups, security, and troubleshooting.

What I'd choose for your situation

One other option: Easy Digital Downloads

If you're already on WordPress and almost everything you sell is digital, I'd also look at easydigitaldownloads.com. It's specifically designed around digital products rather than physical merchandise. Edd Sell Services Easy Digital Downloads

I'd rank it:

Payhip → easiest/lowest maintenance
WooCommerce → best open-source/value option
Easy Digital Downloads → best WordPress-centric digital-download specialist

For a tight-budget nonprofit, I wouldn't start with Shopify, BigCommerce, or a complicated self-hosted ecommerce stack unless you have a specific need they solve.

If you tell me roughly how many PDFs you sell, your monthly sales volume, whether you already have WordPress, and whether you need memberships/courses or just one-time downloads, I can recommend the cheapest setup—including the payment processor and approximate monthly cost.

If speed-to-launch is the overriding constraint, I’d shortlist Shopify + Hydrogen and BigCommerce + Catalyst rather than jumping straight to a fully composable stack.

My ranking for a mid-size retailer

1. Shopify + Hydrogen — best overall for speed

• Shopify handles the commerce backend, checkout, payments, catalog, orders, etc.
• Hydrogen gives you a React-based headless storefront with prebuilt Shopify-specific components, utilities, and tooling. Shopify also provides Oxygen hosting. Shopify Shopify
• Shopify specifically positions Hydrogen as a way to accelerate a headless build rather than starting from a blank React application. Shopify
• I'd choose this if: you're primarily DTC, want a relatively small engineering footprint, and don't have unusually complex commerce requirements.
• BigCommerce + Catalyst — best if you need more backend flexibility

• Catalyst is a Next.js/React headless storefront with a GraphQL Storefront API and a production-ready B2C funnel, so you're not building basic commerce functionality yourself. BigCommerce
• BigCommerce explicitly supports headless starter solutions and positions Catalyst as its fast-track implementation path. BigCommerce BigCommerce
• I'd choose this if: you have more complicated catalog/pricing requirements, multiple storefronts, or want less dependence on Shopify's ecosystem.
• commercetools — powerful, but probably wrong for a tight deadline

• It's attractive when you're deliberately building a highly composable architecture, but that flexibility generally means more architecture, integration and implementation work.
• I'd choose it if: you're optimizing for a sophisticated long-term enterprise architecture rather than the fastest credible migration.

What I'd actually do

For a mid-size retailer under serious time pressure, I'd aim for:

Shopify → Hydrogen → existing/selected CMS → existing PIM/search/ERP integrations → Oxygen

rather than trying to make every part of the stack composable on day one.

The important trick is not making the migration itself a giant re-platforming project. Keep the commerce backend and operational systems as stable as possible, replace the customer-facing layer first, and defer architectural cleanup.

If you're already on Shopify, the case is particularly strong: Shopify documents a migration path where carts can remain compatible between the existing storefront and Hydrogen, and checkout remains Shopify-hosted. Shopify

If you're already on BigCommerce, I'd strongly favor Catalyst rather than switching commerce platforms just to go headless.

shopify.dev
docs.bigcommerce.com

If you tell me your current commerce platform, approximate annual GMV, CMS/PIM, and target launch window (e.g. 8 weeks vs. 6 months), I can narrow this down to a specific stack and implementation approach.

If speed to launch is the #1 constraint, I’d narrow it to Shopify Hydrogen and BigCommerce Catalyst rather than starting with a fully custom composable stack.

My ranking for a mid-size retailer

My default choice: Shopify Hydrogen if your commerce backend is already Shopify. Shopify positions Hydrogen/Oxygen specifically as its recommended headless stack, with prebuilt commerce components, CLI tooling, and integrated deployment. Hydrogen Shopify

hydrogen.shopify.dev

BigCommerce Catalyst is probably the strongest alternative if you're on BigCommerce or want a more explicitly composable mid-market setup. Catalyst gives you a working Next.js/React storefront, GraphQL API client, product/search/cart functionality, and hosted checkout rather than making your team assemble those pieces. BigCommerce BigCommerce

catalyst.dev

What I'd do under a tight deadline

Don't build "headless architecture" as a technology project. Build a thin vertical slice:

1. Catalog → PDP → cart → checkout
2. Search/category pages
3. CMS/content
4. Analytics and critical integrations
5. Only then migrate the remaining experience

For a mid-size retailer, I'd specifically avoid starting with commercetools + a separate CMS + search + personalization + custom checkout unless you have requirements that genuinely demand it. The integration surface can eat your schedule.

If you tell me your current commerce platform, CMS, ERP/PIM, and target launch timeframe (e.g. 8 weeks vs. 6 months), I can give you a much more concrete recommendation and a proposed stack.

BigCommerce Catalyst is probably the strongest alternative if you're on BigCommerce or want a more explicitly composable mid-market setup. Catalyst gives you a working Next.js/React storefront, GraphQL API client, product/search/cart functionality, and hosted checkout rather than making your team assemble those pieces.

For a startup with limited funding, I’d put Medusa at the top of the list—especially if you have a capable JavaScript/TypeScript developer or agency.

My ranking

🥇 Best overall: Medusa

medusajs.com is particularly attractive because its commerce engine is open source, there are no GMV/platform fees, and its managed Cloud starts at $29/month, with a production-oriented Launch tier starting at $99/month. Medusa Medusa Docs

You get a surprisingly complete foundation: products, orders, customers, sales channels, regions/currencies, promotions, payments, fulfillment, and a modular architecture that you can customize rather than fighting against. Medusa's current Cloud pricing explicitly lists unlimited products, orders, sales channels, regions and currencies without additional commerce-feature fees. Medusa Docs

Why I'd choose it for a funded-but-budget-conscious startup:

• Very low initial software cost.
• You retain considerable control over the backend.
• Excellent fit with a Next.js/React storefront.
• No percentage-of-GMV platform fee.
• You can start on inexpensive infrastructure and scale later.
• Custom business logic is much easier than on traditional SaaS platforms.

The catch is that you are taking on more engineering responsibility than with Shopify.

🥈 Shopify + Hydrogen if engineering resources are scarce

If "limited funding" also means limited developer time, I'd actually choose Shopify.

Shopify gives you the mature commerce backend, checkout, payments, inventory, apps, and operational tooling, while Hydrogen lets you build a custom headless storefront. The tradeoff is recurring Shopify cost and less control over the underlying commerce engine.

So I'd use this rule:

Limited money + strong developers → Medusa.
Limited money + limited developers → Shopify.

🥉 Saleor if you already know you'll need sophisticated commerce

saleor.io is technically excellent, particularly for GraphQL-first development, international commerce, B2B, and complex catalogs. But its managed Cloud is dramatically more expensive: the current Select tier starts at $1,599/month, while the higher-volume tier starts at $3,999/month. Saleor Commerce

That's hard to justify for a cash-constrained startup unless Saleor's capabilities directly solve an important requirement.

What I'd actually do

For a typical startup launching a new DTC brand, I'd build:

Next.js storefront → Medusa → PostgreSQL → Stripe → managed hosting/CDN

Start around the lowest practical infrastructure cost, validate product-market fit, and only introduce more specialized infrastructure as traffic and requirements justify it.

One important caveat: headless itself costs engineering money. A 2026 comparison estimates headless implementations commonly have substantially higher development costs than conventional Shopify/WooCommerce setups. Teamz Lab If your storefront doesn't genuinely need a highly customized experience, a conventional Shopify store can be the financially smarter startup choice.

Bottom line: Medusa gives you the best cost/features balance for a technically capable startup; Shopify gives you the best cost/time-to-market balance.

For thousands of SKUs plus genuinely complex product models, I’d put commercetools and Elastic Path at the top of the shortlist, with Saleor as the strongest open-source/API-first alternative.

My first choice: commercetools

For an enterprise catalog, commercetools is particularly compelling. Its catalog model separates Products, Variants, Product Types, Categories, Product Selections and Product Projections, giving you considerably more control than a typical SaaS storefront platform. commercetools Documentation commercetools Documentation

More importantly for your use case, its Modular Catalog is now in public beta. Variants can be first-class resources rather than embedded inside Products, with support for up to 10,000 variants per Product versus the classic 100-variant model. That is a meaningful improvement if your SKU structures are unusually large. commercetools Documentation commercetools Documentation

It is also genuinely API-first rather than simply putting an API in front of a traditional commerce application.

Elastic Path deserves a very close look

If "complex product models" means things like configurable products, B2B assortments, multiple catalogs/price books, bundles, subscriptions, or sophisticated product relationships, I'd evaluate Elastic Path alongside commercetools.

Its Product Experience Manager is explicitly designed around API-first/headless delivery and says it is built to handle thousands of SKUs, catalogs and price books. Elastic Path

A recent 2026 comparison also puts Elastic Path specifically in the category of complex enterprise B2B/configurable commerce, while positioning commercetools as the broader enterprise composable choice. Vendure

When I'd choose Saleor

If you have a strong engineering organization and want GraphQL-native APIs plus much more ownership of the underlying platform, Saleor is interesting. Its storefront and admin are headless/API-driven, with GraphQL and extensive webhooks; its current platform also emphasizes dynamic product models and structured attributes. Saleor Commerce Saleor Commerce

I'd choose it over commercetools if avoiding proprietary platform lock-in and having code-level control are major priorities.

What I'd actually shortlist

For your description, I'd run an RFP/POC with:

1. commercetools — best overall enterprise/composable candidate.
2. Elastic Path — potentially better if your catalog has unusually complex B2B/configuration requirements.
3. Saleor — best challenger if your engineering team favors GraphQL and open source.
4. Adobe Commerce — worth considering if you're already heavily invested in Adobe.
5. BigCommerce — only if your catalog complexity is moderate and operational simplicity matters more than maximum modeling flexibility.

The key thing I'd test isn't simply "how many SKUs can it hold." I'd give each vendor your actual hardest 20–50 product types and test variant inheritance, bundles/configurations, regional assortments, price books, inventory relationships, search/filtering, bulk imports, and API payload/query performance.

If you tell me what makes your product models complex (e.g. 10k variants/SKU families, configurable products, B2B customer-specific catalogs, bundles, technical attributes, regional catalogs, etc.), I can narrow this to the 2–3 platforms I'd seriously consider and explain the architectural tradeoffs.

It is also genuinely API-first rather than simply putting an API in front of a traditional commerce application.

Elastic Path deserves a very close look

If "complex product models" means things like configurable products, B2B assortments, multiple catalogs/price books, bundles, subscriptions, or sophisticated product relationships, I'd evaluate Elastic Path alongside commercetools.

Its Product Experience Manager is explicitly designed around API-first/headless delivery and says it is built to handle thousands of SKUs, catalogs and price books. Elastic Path

A recent 2026 comparison also puts Elastic Path specifically in the category of complex enterprise B2B/configurable commerce, while positioning commercetools as the broader enterprise composable choice. Vendure

When I'd choose Saleor

If you have a strong engineering organization and want GraphQL-native APIs plus much more ownership of the underlying platform, Saleor is interesting. Its storefront and admin are headless/API-driven, with GraphQL and extensive webhooks; its current platform also emphasizes dynamic product models and structured attributes.

I'd choose it over commercetools if avoiding proprietary platform lock-in and having code-level control are major priorities.

What I'd actually shortlist

For your description, I'd run an RFP/POC with:

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d shortlist commercetools and Elastic Path first. The better choice depends on whether your complexity is primarily product/variant modeling or B2B catalog, pricing, and assortment rules.

My pick: commercetools

commercetools.com is probably the strongest general-purpose enterprise headless option.

Its catalog model separates Products, Product Types, Variants, Categories, Product Selections, pricing, and search, which gives you a lot of control over complicated schemas. Its newer modular catalog model can support up to 10,000 variants per product, compared with 100 in the classic model. commercetools Documentation commercetools Documentation

It also provides REST APIs plus GraphQL, and the platform is explicitly designed around composable/API-driven commerce. commercetools Documentation commercetools

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

ERP/PIM → commerce catalog → search → custom frontend(s) → OMS/fulfillment

rather than expecting the commerce platform to own everything.

Elastic Path is worth serious consideration

elasticpath.com may actually be the better choice if your "complex catalog" means things like:

• thousands/millions of SKUs
• multiple catalogs for different customers/regions
• customer-specific assortments
• complex B2B price books
• bundles/configurable products
• account hierarchies
• contract/volume pricing
• manufacturer/distributor use cases

Elastic Path specifically positions its catalog/PXM around complex B2B catalogs, with multiple catalogs, product attributes, bundles, variations and rules-based pricing. Elastic Path Elastic Path Its catalog architecture also separates products, hierarchies, catalogs and price books, which can be valuable when the same underlying products appear differently across markets or customer groups. Elastic Path

The important distinction

If you mean:

"We have complicated product schemas, lots of attributes, variants, relationships, and need clean APIs for several custom storefronts."

→ commercetools

If you mean:

"We are a manufacturer/distributor with complicated assortments, customer-specific catalogs, pricing, bundles, and B2B purchasing rules."

→ Elastic Path

If you're already deeply invested in SAP ERP/S4HANA, I'd put SAP Commerce Cloud into the evaluation despite its heavier architecture.

One thing I'd not use as the primary selection criterion is simply "how many SKUs can it store." Thousands of SKUs isn't particularly challenging for any of these platforms. The harder question is whether your product model, relationships, pricing, catalog segmentation, search, and APIs remain manageable as the catalog evolves.

If you tell me roughly (1) SKU count, (2) number of attributes/variants per product, (3) B2B vs B2C, (4) whether you have SAP/Oracle/other ERP, and (5) how many storefronts/channels, I can give you a much tighter commercetools vs Elastic Path vs SAP vs BigCommerce recommendation.

If the goal is to decouple checkout from the frontend (meaning your web/mobile/IoT experiences own the UX while commerce services provide carts, pricing, promotions, payments, and orders through APIs), you should evaluate platforms based on checkout composability, not just “headless storefront” support.

The strongest options are:

commercetools Documentation Commercetools## My shortlist for a true decoupled checkout architecture

1. commercetools — best if checkout is a strategic capability

For a company saying “checkout is a platform capability we want to own,” commercetools is usually the strongest architectural fit.

Advantages:

• Fully API-first commerce model
• Checkout can be treated as a service, not a page
• Supports multiple channels (web, mobile, kiosks, marketplaces, conversational commerce)
• Better fit for complex pricing, promotions, B2B rules, regionalization, and orchestration

Its Checkout product supports both a complete checkout flow and payment-only scenarios, which is useful if you want to gradually replace parts of an existing checkout stack. commercetools Documentation

Good fit:

• Global retailers
• Marketplaces
• Complex B2B
• Multiple brands/sites
• Companies building their own commerce experience layer

2. BigCommerce — best pragmatic headless choice

BigCommerce is a good middle ground if you want headless checkout without building as much commerce infrastructure yourself.

It supports:

• Headless storefronts
• Cart and checkout APIs
• Custom checkout experiences
• External applications controlling checkout flows BigCommerce BigCommerce

Good fit:

• You want a modern frontend (React/Next.js/mobile apps)
• You need faster implementation
• You still want SaaS-managed commerce operations

3. Shopify Plus — best if operational simplicity matters

Shopify is excellent when the business wants:

• Fast launches
• Huge app ecosystem
• Strong merchant tooling

However, if the requirement is “we want checkout to become our own domain/service”, Shopify can become limiting because checkout behavior is intentionally controlled by Shopify. It works better when you want a custom frontend but are comfortable with Shopify managing much of checkout.

Architecture I would recommend

A flexible headless checkout stack usually looks like:

Frontend Channels
(Web / Mobile / App / Store Associate UI)
          |
          |
Checkout Experience Layer
(Your UX + orchestration)
          |
          |
Commerce APIs
 |
 |-- Cart
 |-- Pricing
 |-- Promotions
 |-- Inventory
 |-- Customer
 |-- Tax
 |-- Payments
 |-- Order Management

The key decision is whether you want:

A. Headless storefront

“Our frontend is separate, but commerce still owns checkout.”

→ Shopify Plus / BigCommerce

B. Composable checkout

“Checkout itself is a business capability we control and evolve.”

→ commercetools / Saleor / custom services

Questions that would change the recommendation

1. Are you replacing only the checkout UI, or also checkout logic (promotions, shipping, payment orchestration)?
2. Is this B2C, B2B, marketplace, or subscription commerce?
3. Do you need the same checkout across web + mobile apps + in-store?
4. What frontend stack are you moving to (Next.js, native apps, something else)?
5. Are you trying to migrate from an existing platform (Magento, Salesforce Commerce Cloud, Shopify, etc.)?

For a large enterprise building a long-lived commerce platform, I would start with commercetools vs BigCommerce as the primary evaluation. Commercetools BigCommerce

A flexible headless checkout stack usually looks like:

Frontend Channels
(Web / Mobile / App / Store Associate UI)
          |
          |
Checkout Experience Layer
(Your UX + orchestration)
          |
          |
Commerce APIs
 |
 |-- Cart
 |-- Pricing
 |-- Promotions
 |-- Inventory
 |-- Customer
 |-- Tax
 |-- Payments
 |-- Order Management

The key decision is whether you want:

A. Headless storefront

“Our frontend is separate, but commerce still owns checkout.”

→ Shopify Plus / BigCommerce

B. Composable checkout

“Checkout itself is a business capability we control and evolve.”

→ commercetools / Saleor / custom services

Questions that would change the recommendation

If the goal is specifically to decouple checkout from the frontend and preserve the ability to radically change the checkout experience later, I’d shortlist commercetools, Medusa, and Saleor rather than making Shopify the default.

My recommendation

For an enterprise architecture, I'd pick commercetools. It explicitly supports both a prebuilt headless Checkout and building a completely custom checkout using its APIs. Its checkout architecture exposes payment lifecycles, events, and extension points rather than making the checkout UI inseparable from the commerce platform. Commercetools Documentation commercetools

commercetools.com

If you're trying to maximize control

Medusa is probably the most interesting option. Its modular architecture lets you own the commerce backend and customize things like cart, pricing, payment, inventory, and fulfillment. That makes it attractive if "checkout" is really going to become a business-specific application rather than a standard ecommerce page. Ribbsaeter Systems Vendure

The tradeoff is that you're taking on more engineering and operational responsibility.

If GraphQL is important

I'd look hard at Saleor. It is API-first and GraphQL-native, with checkout and storefront functionality exposed through the API rather than requiring a particular frontend technology. Saleor also supports multiple channels, which becomes valuable if you're separating checkout from several storefronts, apps, or markets. Saleor Commerce

saleor.io

What I would avoid

I wouldn't choose Shopify primarily because it's easy to go headless if your actual requirement is:

"We want checkout to be an independently deployable/application-level capability that we can completely control."

Shopify is excellent when you want a managed checkout with a custom frontend, but there's still a meaningful distinction between decoupling the storefront and owning the checkout. Current comparisons continue to identify Shopify's checkout as the major customization boundary versus platforms such as Medusa and Saleor. Ribbsaeter Systems Hunchbite

Architecture I'd target

I'd make the boundary look roughly like:

                 ┌─────────────────────┐
                 │   Web / Mobile /    │
                 │   Other Frontends   │
                 └──────────┬──────────┘
                            │
                       Checkout API
                            │
                 ┌──────────▼──────────┐
                 │   Checkout Service  │
                 │                     │
                 │ address             │
                 │ shipping            │
                 │ promotions          │
                 │ tax                 │
                 │ payment             │
                 │ fraud               │
                 │ order orchestration │
                 └──────────┬──────────┘
                            │
                 ┌──────────▼──────────┐
                 │ Commerce Platform  │
                 │                     │
                 │ catalog             │
                 │ pricing             │
                 │ inventory           │
                 │ orders              │
                 └─────────────────────┘

The key is don't make the frontend talk directly to a bunch of commerce APIs. Put a stable Checkout API/BFF in front of the commerce engine. Then you can replace the web frontend, add native apps, introduce an agentic/voice checkout, or even replace the commerce platform without rewriting every client.

So my default decision would be:

• $10M–$100M+ GMV / complex markets / enterprise: commercetools
• Engineering-heavy team wanting maximum ownership: Medusa
• GraphQL + B2B/multi-channel: Saleor
• "We mostly want Shopify, but with a custom frontend": Shopify

If you tell me your GMV, B2C vs B2B, number of markets/currencies, payment provider, and whether you need subscriptions, I can narrow this to a specific architecture and platform.

For an enterprise architecture, I'd pick commercetools. It explicitly supports both a prebuilt headless Checkout and building a completely custom checkout using its APIs. Its checkout architecture exposes payment lifecycles, events, and extension points rather than making the checkout UI inseparable from the commerce platform. Commercetools Documentation commercetools

commercetools.com

If you're trying to maximize control

Medusa is probably the most interesting option. Its modular architecture lets you own the commerce backend and customize things like cart, pricing, payment, inventory, and fulfillment. That makes it attractive if "checkout" is really going to become a business-specific application rather than a standard ecommerce page. Ribbsaeter Systems Vendure

The tradeoff is that you're taking on more engineering and operational responsibility.

If GraphQL is important

I'd look hard at Saleor. It is API-first and GraphQL-native, with checkout and storefront functionality exposed through the API rather than requiring a particular frontend technology. Saleor also supports multiple channels, which becomes valuable if you're separating checkout from several storefronts, apps, or markets. Saleor Commerce

saleor.io

What I would avoid

I wouldn't choose Shopify primarily because it's easy to go headless if your actual requirement is:

"We want checkout to be an independently deployable/application-level capability that we can completely control."

Shopify is excellent when you want a managed checkout with a custom frontend, but there's still a meaningful distinction between decoupling the storefront and owning the checkout. Current comparisons continue to identify Shopify's checkout as the major customization boundary versus platforms such as Medusa and Saleor. Ribbsaeter Systems Hunchbite

Architecture I'd target

I'd make the boundary look roughly like:

                 ┌─────────────────────┐
                 │   Web / Mobile /    │
                 │   Other Frontends   │
                 └──────────┬──────────┘
                            │
                       Checkout API
                            │
                 ┌──────────▼──────────┐
                 │   Checkout Service  │
                 │                     │
                 │ address             │
                 │ shipping            │
                 │ promotions          │
                 │ tax                 │
                 │ payment             │
                 │ fraud               │
                 │ order orchestration │
                 └──────────┬──────────┘
                            │
                 ┌──────────▼──────────┐
                 │ Commerce Platform  │
                 │                     │
                 │ catalog             │
                 │ pricing             │
                 │ inventory           │
                 │ orders              │
                 └─────────────────────┘

The key is don't make the frontend talk directly to a bunch of commerce APIs. Put a stable Checkout API/BFF in front of the commerce engine. Then you can replace the web frontend, add native apps, introduce an agentic/voice checkout, or even replace the commerce platform without rewriting every client.

So my default decision would be:

• $10M–$100M+ GMV / complex markets / enterprise: commercetools
• Engineering-heavy team wanting maximum ownership: Medusa
• GraphQL + B2B/multi-channel: Saleor
• "We mostly want Shopify, but with a custom frontend": Shopify

If you tell me your GMV, B2C vs B2B, number of markets/currencies, payment provider, and whether you need subscriptions, I can narrow this to a specific architecture and platform.

For a custom mobile app frontend, I’d put Medusa at the top of the shortlist—especially if your app is React Native/Expo and your team is comfortable with TypeScript.

Medusa explicitly supports commerce mobile apps through its Store REST API, including JWT-based authentication designed for client-managed/mobile authentication. Medusa Docs Medusa Docs

My ranking

1. 🥇 Medusa — my default recommendation

medusajs.com

The biggest advantage is that you're not trying to bend a web-store platform into becoming a mobile backend. Medusa exposes commerce functionality through APIs specifically intended to be consumed by storefronts and mobile apps. Medusa Docs

It's particularly attractive if you need things like:

• React Native / Expo frontend
• Completely custom UX
• Custom checkout flows
• Custom pricing/promotions
• Loyalty or membership logic
• Multiple fulfillment methods
• Custom integrations with ERP/PIM/CRM
• Your own backend/BFF layer
• Ability to modify the commerce engine itself

Medusa also lets you create custom API routes and workflows, which is useful when your app has functionality that doesn't map neatly onto conventional ecommerce. Medusa Docs Medusa Docs

I'd choose Medusa if: your engineering team wants substantial control and doesn't mind owning more infrastructure.

2. 🥈 commercetools — best enterprise choice

commercetools.com

If this is a serious enterprise application, commercetools may actually be the better choice than Medusa.

Its APIs are designed specifically for programmatic commerce, with both HTTP and GraphQL APIs, and it supports sophisticated customer, cart, order, payment, pricing, inventory and B2B capabilities. commercetools Documentation commercetools Documentation

It's particularly strong if your architecture looks like:

                 ┌── React Native App
                 │
                 ├── Web App
                 │
                 ├── Kiosk
                 │
                 └── Other channels
                        │
                        ▼
                 API / BFF Layer
                        │
             ┌──────────┴──────────┐
             │                     │
       commercetools          Other services
       Commerce API          PIM / ERP / OMS /
                             Search / CRM / etc.

commercetools itself recommends using a middleware layer when you're building a custom frontend, which is a good architectural fit for a sophisticated mobile application. commercetools Documentation

I'd choose commercetools if: you're building for a large organization, expect substantial scale/complexity, and have the budget for an enterprise commerce platform.

3. 🥉 Saleor — excellent if you want GraphQL

Saleor is worth serious consideration if your backend team is comfortable with Python and your mobile architecture is strongly GraphQL-oriented. Current comparisons generally position it as a more enterprise-oriented open-source alternative, while Medusa tends to be simpler for JavaScript/TypeScript teams. OSSAlt

What I would actually pick

If you told me:

"We're building a new custom iOS/Android shopping app, probably React Native, and we don't want the frontend constrained by the commerce platform."

I'd choose:

Medusa → React Native/Expo → your own thin BFF/API layer

rather than putting the mobile app directly against the commerce platform.

That gives you:

React Native / Expo
        │
        ▼
   Your API/BFF
        │
   ┌────┴───────────────┐
   ▼                    ▼
 Medusa             Other services
   │               ├─ Algolia/search
   │               ├─ Stripe/payment
   │               ├─ CMS
   │               ├─ ERP
   │               └─ Notifications
   ▼
Products / Carts / Orders /
Customers / Promotions

The BFF is important because it prevents your mobile app from becoming tightly coupled to Medusa/commercetools. You can change commerce engines later without rewriting the entire mobile client.

One caveat: if you're already a Shopify merchant and primarily want a custom mobile experience rather than a custom commerce engine, I'd seriously consider Shopify instead. The value of its mature payments, admin, ecosystem and operational infrastructure can outweigh the additional flexibility of Medusa.

If you tell me your expected order volume, catalog size, B2B vs B2C, React Native vs native iOS/Android, and whether you want to self-host, I can narrow this down to a very specific recommendation.

If your primary requirement is a custom mobile app frontend—iOS/Android built in React Native, Flutter, Swift/Kotlin, etc.—I’d prioritize API quality, checkout flexibility, authentication, webhooks, SDKs, and how much of the commerce backend you need to customize rather than how good the platform’s web storefront is.

My ranking

🥇 My default choice: Medusa

For a new custom mobile app, I'd probably choose Medusa unless you have enterprise-scale requirements.

Medusa is particularly attractive because it's a headless, Node.js/TypeScript commerce engine. Your mobile app can consume the commerce APIs directly rather than going through a web storefront. Its modular architecture also gives you substantially more control over things like pricing, promotions, fulfillment, payments, and custom business logic. PowerGate Software WPBundle

A typical architecture would look like:

iOS / Android App
   │
   │ HTTPS / API
   ▼
Your API / BFF
   │
   ├── Medusa
   ├── Payment provider
   ├── Search
   ├── CMS
   ├── Notifications
   └── Analytics

That is a very natural architecture if the app is going to become a major product experience rather than simply a mobile version of a website.

🏢 When I'd choose commercetools instead

If you're building for a large organization with:

• multiple countries/currencies
• complex pricing
• B2B accounts
• multiple brands/channels
• sophisticated inventory/fulfillment
• multiple frontends beyond the app
• a dedicated commerce engineering team

I'd strongly consider commercetools.

It's API-first and was designed specifically for headless/composable commerce, making it an excellent foundation for mobile, web, kiosks, marketplaces, etc. Commercetools

The downside is that you're buying into a much more sophisticated architecture—and corresponding cost and engineering overhead.

🧩 When I'd choose Saleor

Saleor is probably my second choice for a technically sophisticated custom app.

It's GraphQL-first and particularly strong if you need multi-channel, multi-warehouse, multi-currency, or B2B functionality. Vendure WPBundle

I'd favor it over Medusa if your team is comfortable with Python/Django and you specifically want a GraphQL-native commerce API.

🛍️ When I'd choose Shopify

Don't discount Shopify.

If the business already uses Shopify, or the priority is getting the app launched quickly while minimizing backend operations, Shopify's Storefront API is an extremely pragmatic choice. You can keep Shopify handling products, orders, payments, customers, etc., while your mobile app is completely custom. Vendure Pharos Production

The tradeoff is that you're accepting Shopify's underlying commerce model. If you eventually need radically custom checkout, pricing, order orchestration, or marketplace logic, an API-first commerce engine such as Medusa or commercetools gives you more freedom.

My decision rule

I'd make the choice roughly like this:

• Startup / new product / TypeScript team → Medusa
• Enterprise / complex global commerce → commercetools
• GraphQL + B2B + multi-channel → Saleor
• Already on Shopify / fastest path to market → Shopify
• Managed SaaS but more headless openness → BigCommerce
• TypeScript + highly customizable backend → Vendure

For a React Native or Flutter app specifically, my personal shortlist would be Medusa vs. Saleor vs. commercetools, with Shopify entering the shortlist if operational simplicity is more important than backend control.

If you tell me (1) B2C vs B2B, (2) approximate SKU count, (3) expected order volume, (4) whether you need subscriptions, and (5) React Native/Flutter/native, I can narrow this to the best 1–2 choices and lay out the recommended mobile architecture.

It's GraphQL-first and particularly strong if you need multi-channel, multi-warehouse, multi-currency, or B2B functionality. Vendure WPBundle

I'd favor it over Medusa if your team is comfortable with Python/Django and you specifically want a GraphQL-native commerce API.

🛍️ When I'd choose Shopify

Don't discount Shopify.

If the business already uses Shopify, or the priority is getting the app launched quickly while minimizing backend operations, Shopify's Storefront API is an extremely pragmatic choice. You can keep Shopify handling products, orders, payments, customers, etc., while your mobile app is completely custom.

The tradeoff is that you're accepting Shopify's underlying commerce model. If you eventually need radically custom checkout, pricing, order orchestration, or marketplace logic, an API-first commerce engine such as Medusa or commercetools gives you more freedom.

My decision rule

I'd make the choice roughly like this:

For a CMS-first commerce architecture (where editors own the product storytelling/page experience and commerce APIs provide catalog, pricing, cart, checkout), I’d usually avoid letting the commerce platform “own” the product page layout. Instead:

Headless CMS = page composition + merchandising story
Commerce API = product truth + transactions

The best platform depends on your scale and how much control you want.

Best fits

1. Shopify + headless CMS — best default for most brands

Good choice if you want:

• Fast implementation
• Strong merchant tooling
• Reliable checkout, payments, inventory
• A CMS layer for richer product pages

Typical stack:

• CMS: Sanity, Contentful, or Storyblok
• Commerce: Shopify Storefront API
• Frontend: Next.js

Shopify supports custom storefronts where the frontend is separated from Shopify’s commerce backend and consumes commerce data through APIs. Shopify Shopify

Choose this if: you’re DTC, mid-market, or want the best balance of flexibility and operational simplicity.

2. BigCommerce + CMS — best if API-first commerce is a priority

Good choice if:

• You need more open commerce APIs
• You have B2B requirements
• You want multi-storefront capability
• You expect more composable architecture

BigCommerce explicitly supports headless builds using CMS platforms, Next.js, GraphQL storefront APIs, and custom frontends. BigCommerce BigCommerce

Choose this if: commerce complexity matters more than having the largest app ecosystem.

3. commercetools + CMS — best enterprise option

Good choice if:

• Product models are complex
• You have ERP/PIM integrations
• You need multiple channels (web, app, kiosks, marketplaces)
• You have engineering resources

It’s designed for composable commerce and commonly paired with CMS platforms to separate content modeling from commerce capabilities. commercetools Documentation

Choose this if: you are building a long-lived commerce platform, not just a storefront.

4. Medusa + CMS — best for engineering-led teams

Good choice if:

• You want ownership of the stack
• You need custom workflows
• You have developers comfortable maintaining infrastructure

Choose this if: you want maximum control and accept more engineering responsibility.

My recommendation by scenario

Product page architecture I’d use

A CMS-driven product page might own:

• Hero media
• Brand story
• Editorial copy
• Lifestyle content
• Buying guides
• FAQs
• SEO fields
• Related content blocks
• Merchandising rules

Commerce API owns:

• SKU
• Price
• Inventory
• Variants
• Promotions
• Cart
• Checkout
• Customer accounts

A common mistake is putting everything in the CMS, including price and inventory. Keep transactional data in commerce.

For most teams today, I’d start with Next.js + Sanity (or Contentful) + Shopify Storefront API unless you already know you have enterprise-scale commerce requirements. Shopify’s API-first approach is specifically designed to support custom storefronts and integrations with CMS/PIM/ERP systems. Shopify

If you tell me your scale (SKU count, B2C vs B2B, number of markets, and whether editors need drag-and-drop page building), I can narrow this to a specific stack.

For most teams today, I’d start with Next.js + Sanity (or Contentful) + Shopify Storefront API unless you already know you have enterprise-scale commerce requirements. Shopify’s API-first approach is specifically designed to support custom storefronts and integrations with CMS/PIM/ERP systems.

For a team that already prefers serverless frontends + JAMstack, I’d bias toward commerce platforms that are truly API-first, work well with Next.js/Astro/Nuxt-style frontends, and don’t require you to run a traditional ecommerce application server. JAMstack/headless commerce works by separating the storefront from the commerce backend, with APIs connecting the two layers. Shopify

The best fits usually fall into these groups:

My shortlist by team profile

1. “We build mostly Next.js/Astro and want minimal ops”

Pick:

• Shopify headless
• Medusa

This gives you:

• serverless frontend deployment
• CDN-friendly pages
• API-driven product/catalog data
• webhooks for revalidation
• no ecommerce backend in your frontend runtime

A common stack:

Next.js / Astro
        |
        | API calls
        |
Commerce backend
        |
Payments / inventory / fulfillment

2. “Our developers want maximum control”

Look at:

• Medusa
• Saleor
• Vendure

These are better when you expect unusual workflows:

• marketplaces
• custom pricing
• complex product logic
• nonstandard checkout flows

The tradeoff is more engineering ownership. CozyCommerce Your Next Store

3. “We are enterprise-scale”

Look at:

• commercetools
• Commerce Layer

These make sense when you need:

• multiple regions
• multiple storefronts
• ERP/PIM/OMS integrations
• many sales channels

They are powerful but usually require a stronger platform engineering team. Vendure

Don’t forget the CMS layer

A JAMstack commerce build often separates:

• Commerce engine: products, cart, checkout, orders
• Headless CMS: landing pages, editorial content, merchandising

Popular pairings:

• Shopify + Sanity
• Medusa + Sanity
• Saleor + Contentful
• Commerce Layer + Contentful

AlphansoLabs |For most teams already committed to serverless frontends, my practical ranking would be:

1. Shopify headless — fastest path to a production-grade store
2. Medusa — best developer experience if you want ownership
3. Saleor — best GraphQL-native option
4. commercetools — best when enterprise complexity justifies it

The deciding question is usually: do you want commerce to be a managed business capability, or do you want it to become part of your product engineering platform?

If your priority is developer experience + SDK quality + modern frontend frameworks, my pick in 2026 is Shopify’s headless stack, with Medusa as the best choice if you want maximum backend control.

The interesting part is that Shopify has changed the equation recently: its new Hydrogen developer preview is moving from an opinionated React framework toward a framework-agnostic commerce SDK/toolkit. It supports Next.js, SvelteKit, Nuxt, SolidStart, React Router, and other JavaScript frameworks/runtimes. Hydrogen Shopify

My ranking for frontend developers

🥇 Shopify Hydrogen — best overall

If I were starting a new project where frontend developer productivity was the primary criterion, I'd choose Shopify.

The new Hydrogen toolkit provides a typed Storefront API client, cart/product/collection primitives, Shop Pay integration, analytics, server-driven cart handling, and framework bindings. Crucially, Shopify now explicitly supports using it with Next.js, SvelteKit, Nuxt, SolidStart, and React Router, rather than forcing you into one frontend framework. Shopify

That's a significant advantage over traditional "headless" platforms where you're essentially given an API and expected to build the commerce plumbing yourself.

You can also use Shopify's Storefront API without Hydrogen if you want a completely custom architecture. Shopify

Best for: Next.js/React teams, DTC brands, teams wanting managed infrastructure, fast implementation.

Big caveat: You're still building on Shopify's commerce model. If your business logic fundamentally doesn't fit Shopify, the excellent frontend tooling won't solve that.

🥈 Medusa — best for developers who want ownership

Medusa is probably my favorite alternative for a team that says:

"We want commerce infrastructure, not a SaaS platform telling us how commerce works."

It's TypeScript/Node-based, modular, open source, and designed to let you customize the backend extensively. That makes it particularly attractive if your frontend is Next.js and you want your commerce code to live in the same general JavaScript/TypeScript ecosystem. Ribbsaeter Systems ZORC

The tradeoff is that you own more of the system—deployment, infrastructure, upgrades, and operational concerns.

Best for: Next.js + TypeScript teams, custom checkout/business logic, marketplaces, unusual commerce models.

🥉 Saleor — best API architecture

Saleor is extremely compelling if your frontend team loves GraphQL.

Its API is GraphQL-first, and its documentation has strong API references, tutorials, extensions, dashboard apps, and recipes for multi-region commerce, marketplaces, custom shipping, etc. Saleor Documentation

The main downside compared with Medusa is the backend ecosystem: Saleor is Python/Django, so a TypeScript-heavy frontend organization has to cross that boundary. Hunchbite

Best for: GraphQL-heavy teams, international/multi-channel commerce, sophisticated catalog models.

Enterprise: commercetools

commercetools is the one I'd put ahead of the others for a large enterprise composable architecture.

Its SDK/API ecosystem is mature, and its frontend tooling includes an SDK designed for SSR/Next.js applications. commercetools Documentation

But it's a different proposition from Medusa or Shopify. You're buying into a much more elaborate composable-commerce architecture, which makes sense when you have the organizational complexity to justify it—not necessarily for a startup or small frontend team.

So, what would I choose?

For a modern Next.js/React storefront:

1. Shopify Hydrogen — best developer experience and lowest plumbing burden.
2. Medusa — best if backend ownership/customization matters.
3. Saleor — best if GraphQL is central to your architecture.
4. commercetools — best for large enterprise composable commerce.
5. Vendure — worth serious consideration if you want a TypeScript/NestJS-centric stack.

The particularly interesting choice right now is Shopify. Its 2026 Hydrogen developer preview essentially acknowledges that modern frontend teams don't necessarily want an ecommerce-specific framework: Shopify is turning Hydrogen into commerce primitives + SDK + tooling that can sit inside the framework you already use. Hydrogen Shopify

So if your stack is Next.js + TypeScript + Tailwind + Vercel, I'd lean Shopify Hydrogen/Storefront API unless you have a strong reason to own the commerce backend. If you're building something where the commerce model itself is highly customized, I'd choose Medusa instead.

If I were starting a new project where frontend developer productivity was the primary criterion, I'd choose Shopify.

The new Hydrogen toolkit provides a typed Storefront API client, cart/product/collection primitives, Shop Pay integration, analytics, server-driven cart handling, and framework bindings. Crucially, Shopify now explicitly supports using it with Next.js, SvelteKit, Nuxt, SolidStart, and React Router, rather than forcing you into one frontend framework. Shopify

That's a significant advantage over traditional "headless" platforms where you're essentially given an API and expected to build the commerce plumbing yourself.

You can also use Shopify's Storefront API without Hydrogen if you want a completely custom architecture. Shopify

Best for: Next.js/React teams, DTC brands, teams wanting managed infrastructure, fast implementation.

Big caveat: You're still building on Shopify's commerce model. If your business logic fundamentally doesn't fit Shopify, the excellent frontend tooling won't solve that.

🥈 Medusa — best for developers who want ownership

Medusa is probably my favorite alternative for a team that says:

"We want commerce infrastructure, not a SaaS platform telling us how commerce works."

It's TypeScript/Node-based, modular, open source, and designed to let you customize the backend extensively. That makes it particularly attractive if your frontend is Next.js and you want your commerce code to live in the same general JavaScript/TypeScript ecosystem. Ribbsaeter Systems ZORC

The tradeoff is that you own more of the system—deployment, infrastructure, upgrades, and operational concerns.

Best for: Next.js + TypeScript teams, custom checkout/business logic, marketplaces, unusual commerce models.

🥉 Saleor — best API architecture

Saleor is extremely compelling if your frontend team loves GraphQL.

Its API is GraphQL-first, and its documentation has strong API references, tutorials, extensions, dashboard apps, and recipes for multi-region commerce, marketplaces, custom shipping, etc. Saleor Documentation

The main downside compared with Medusa is the backend ecosystem: Saleor is Python/Django, so a TypeScript-heavy frontend organization has to cross that boundary. Hunchbite

Best for: GraphQL-heavy teams, international/multi-channel commerce, sophisticated catalog models.

Enterprise: commercetools

commercetools is the one I'd put ahead of the others for a large enterprise composable architecture.

Its SDK/API ecosystem is mature, and its frontend tooling includes an SDK designed for SSR/Next.js applications. docs.commercetools.com

But it's a different proposition from Medusa or Shopify. You're buying into a much more elaborate composable-commerce architecture, which makes sense when you have the organizational complexity to justify it—not necessarily for a startup or small frontend team.

So, what would I choose?

For a modern Next.js/React storefront:

For a B2B wholesaler with complex customer-specific pricing + a headless/API-first storefront, I’d shortlist Adobe Commerce and commercetools first.

My recommendation: Adobe Commerce B2B

For your specific requirements, Adobe Commerce B2B is probably the safest choice if your pricing model is genuinely complicated.

It has native company accounts, shared catalogs, customer-specific pricing, tier pricing, negotiated quotes, purchase orders/approval rules, requisition lists, quick order, and payment-on-account/credit. developer.adobe.com

The shared-catalog model is particularly relevant for wholesale: you can create custom catalogs assigned to companies and give each company its own product assortment and prices. Custom prices can be fixed amounts, percentages, and quantity-based tiers. experienceleague.adobe.com

It also exposes B2B functionality through REST APIs, including shared-catalog management, making it viable for a headless storefront. developer.adobe.com

Choose Adobe if: your business has lots of customer-specific rules, ERP integration, negotiated pricing, complex catalogs, multiple buyer roles, or workflows that will require customization.

When I'd choose commercetools instead

If headless/API-first architecture is the #1 requirement, I'd seriously consider commercetools.

Its pricing model can scope prices by customer group, channel, country, and currency, and its current B2B offering includes APIs for business-unit hierarchies, granular buyer permissions, approvals, and quote management. docs.commercetools.com

The tradeoff is that you're buying a composable commerce platform rather than an all-in-one B2B application. You'll generally need a stronger engineering team and more surrounding services.

The decision I'd make

Adobe Commerce B2B → best if you want deep B2B functionality out of the box and are willing to customize it.

commercetools → best if you want maximum architectural flexibility and API-first/headless commerce, and you have the engineering capability to assemble the platform.

BigCommerce B2B → worth evaluating if you want something simpler/faster to deploy without going all the way into enterprise composable architecture.

If you tell me roughly how you calculate customer pricing (e.g. customer × SKU × quantity × contract × region) and what ERP you're integrating with, I can narrow this down to the best 2–3 platforms and compare their APIs, pricing engines, quote workflows, and implementation complexity.

For a subscription box business, I’d focus less on “does it have a subscription API?” and more on how much subscription logic you want the platform to own. Subscription boxes often need things like:

• recurring billing
• skip/pause/swap boxes
• build-a-box flows
• prepaid plans (3/6/12 months)
• customer portal
• inventory allocation before renewal
• upcoming box previews
• add-ons and upsells
• failed payment recovery
• fulfillment scheduling

My shortlist:

My recommendation by business stage

If you have <10k subscribers

I’d usually choose:

Shopify + a subscription engine
You get:

• proven checkout
• payments
• tax/shipping ecosystem
• less engineering

Use your own headless frontend if you need it, but don’t rebuild subscription billing unless your model is unusual.

If subscriptions are your core product

Example: every customer has a highly personalized box, swaps items monthly, has credits, tiers, loyalty, etc.

I’d lean toward:

Medusa + Stripe Billing (or another billing provider)

Why:

• you control the subscription data model
• you can expose your own API
• you can build custom workflows around boxes, inventory, and fulfillment

Medusa specifically documents building subscription purchases with custom workflows, API routes, and renewal handling rather than forcing a fixed subscription model. Medusa Docs Medusa Docs

If you’re doing $5M+ GMV or have a large engineering team

Consider:

commercetools

It is very flexible, but you’ll be assembling more pieces yourself. It’s powerful when you have the team to own the architecture. commercetools Documentation

Architecture I’d pick for a serious subscription box company

A common strong setup:

• Frontend: Next.js
• Commerce: Medusa or Shopify headless
• Billing: Stripe Billing
• CMS: Sanity / Contentful
• Search: Algolia / Elastic
• Customer data: Segment + your CRM
• Fulfillment: custom service or 3PL integration

The key question

Which category are you in?

1. Monthly curated box (same concept every month, maybe swaps)
2. Build-your-own box (customers choose items)
3. Personalized subscription (quiz/profile drives contents)
4. Membership + recurring perks
5. Wholesale/B2B subscription boxes

The answer changes the best platform quite a bit.

Consider:

commercetools

If international commerce is the primary requirement, I’d shortlist commercetools and Saleor, with the choice depending on how much enterprise complexity you need.

My ranking

🥇 Most robust: commercetools

If by "robust" you mean many countries, currencies, languages, price books, tax rules, regional catalogs, localized payment methods, multiple storefronts, and complex business rules, I'd pick commercetools.

Its project configuration explicitly models countries, currencies, and languages, while its frontend architecture supports multi-language and multi-region deployments. docs.commercetools.com

The big advantage is that internationalization isn't just a storefront concern. You can model regional commerce rules throughout the commerce layer. That's particularly valuable when you eventually have things like:

• USD / EUR / GBP / JPY / CAD pricing
• country-specific price lists
• different catalogs by market
• regional tax/VAT behavior
• different payment providers
• localized product data
• multiple brands/storefronts
• B2B + B2C
• country-specific fulfillment

Downside: it's considerably more enterprise-oriented and architecturally involved. You're buying a powerful commerce infrastructure rather than a particularly opinionated ecommerce application.

🥈 Best modern alternative: Saleor

I'd take a very serious look at Saleor if you're building a new system today.

Saleor's channel model maps particularly nicely to international commerce: channels can represent markets with their own currency, pricing, stock, payment methods and shipping configuration. Its documentation also has explicit multi-region functionality. saleor.io

The current Saleor storefront architecture supports URLs such as:

/en/us/... → English + US/USD
/en/uk/... → English + UK/GBP
/pl/pl/... → Polish + Poland/PLN

including translated product slugs and locale-aware SEO/hreflang handling. github.com

That's unusually good for an international headless build because market and language are separate concepts. You can have English-US, English-UK, French-CA, etc., without turning your architecture into a mess.

Saleor also supports currency-specific channels, regional taxes, shipping zones, payment integrations, and dynamic tax/shipping logic. saleor.io

When I'd choose each

Choose commercetools if:

• you're a large enterprise
• 10+ markets are likely
• complex pricing/catalog rules are expected
• B2B is important
• you need sophisticated integrations with ERP/PIM/OMS
• you have a strong commerce engineering team
• this platform needs to last 7–10+ years

Choose Saleor if:

• you're building a modern headless stack from scratch
• GraphQL is attractive
• international DTC is the core use case
• you want excellent market/channel modeling without quite as much enterprise machinery
• you want more control over the application architecture
• you're using Next.js/React

Choose Shopify/Hydrogen if:

• minimizing operational burden matters more than maximum architectural control
• you want the fastest route to production
• Shopify's international capabilities already cover most of your business requirements.

My recommendation

For a new international brand, I'd probably choose:

Saleor → unless you have very complex enterprise requirements → commercetools.

For example, if you're selling in US + Canada + UK + EU + Australia + Japan, with localized languages/currencies, regional pricing, payment methods, taxes and inventory, Saleor is an extremely compelling fit. Its current architecture was explicitly designed around channels, regions and localization. saleor.io

If you're talking about something more like Nike/Adidas/L'Oréal-scale commerce, where the commerce engine needs to become a central piece of a huge enterprise ecosystem, I'd lean commercetools.

If you tell me your approximate number of countries, languages, currencies, SKU count, B2B vs B2C, and whether you need regional pricing/catalogs, I can give you a much more definitive Saleor vs commercetools vs Shopify Hydrogen recommendation.

For a high-volume dropshipping business with multiple warehouses, my top choice is Shopify Plus, but there’s an important caveat: at your scale, the ecommerce platform should be the storefront/order hub, while a dedicated OMS/WMS/ERP handles complex warehouse and supplier operations.

My ranking

🥇 Shopify Plus

Shopify currently supports inventory allocation across up to 1,000 warehouses, fulfillment centers, and stores, along with purchase orders, inventory transfers, bulk inventory management, and inventory automation. www.shopify.com

For a dropshipping operation, the big advantage is the ecosystem. You can connect supplier feeds, fulfillment providers, marketplaces, 3PLs, shipping systems, and an external inventory/OMS layer without having to build everything yourself. Shopify Plus also provides centralized management across locations. www.shopify.com

Shopify Plus

🥈 BigCommerce Enterprise

I'd seriously consider BigCommerce Enterprise if you have a complicated catalog, lots of custom integrations, multiple storefronts, or want more API/control flexibility.

BigCommerce has location-aware inventory APIs that can track inventory across multiple locations and support multi-location fulfillment. It also centralizes orders and inventory across channels. www.shopify.comwww.bigcommerce.com

One limitation to be aware of: its standard plans have relatively low native location limits, while Enterprise supports 100 locations with customization available. docs.bigcommerce.com

BigCommerce Enterprise

🥉 Adobe Commerce

Adobe Commerce becomes attractive if you're talking about very large enterprise scale, extremely complex fulfillment rules, custom pricing/catalogs, or an in-house engineering/IT team. It's much more customizable, but also substantially more complicated to implement and maintain.

What I'd actually build

For a serious dropshipping operation, I'd use:

Shopify Plus → OMS/Inventory system → multiple warehouses/3PLs → suppliers

Rather than trying to make Shopify itself do everything.

The critical capabilities I'd prioritize are:

• Real-time inventory synchronization between warehouses
• Automatic order routing to the optimal warehouse
• Supplier inventory feeds/API synchronization
• Oversell prevention
• Purchase-order/replenishment automation
• Split-order fulfillment
• Tracking-number synchronization
• Returns/refunds synchronization
• Marketplace integration
• Bulk SKU/product management
• Webhooks/API access
• Centralized order management
• Inventory forecasting and safety stock

Bottom line: If you're choosing one platform today, I'd pick Shopify Plus for most high-volume dropshipping businesses. If your operation is unusually complex and API/integration flexibility is more important than ease of use, BigCommerce Enterprise is probably the better alternative.

If you tell me roughly monthly order volume, number of SKUs, number of warehouses, sales channels (Shopify/Amazon/eBay/TikTok/etc.), and whether the warehouses are yours or 3PLs, I can narrow this down to the best Shopify Plus vs BigCommerce vs dedicated OMS/WMS stack for your specific operation.

If mobile performance + checkout conversion are your top priorities for a dropshipping store, I’d choose Shopify.

My ranking

\*WooCommerce performance varies much more with hosting, theme, plugins, and implementation.

Why Shopify wins

1. Checkout is the biggest advantage.
Shopify's checkout is natively responsive/mobile-first, with address autocomplete and accelerated payment options. www.shopify.comwww.shopify.comwww.shopify.comwww.shopify.com

More importantly, Shop Pay eliminates much of the painful typing that kills mobile conversion. Shopify reports up to 50% higher checkout conversion versus guest checkout, and says Shop Pay is at least 10% ahead of other accelerated checkouts. www.shopify.com

For a dropshipping store where you're likely buying traffic from TikTok/Meta/Google and sending people directly from a phone to a product page, that's a major advantage.

2. You don't have to engineer the checkout.
With WooCommerce, you can make an extremely fast checkout—but you're responsible for hosting, caching, plugins, payment integrations, updates, etc. WooCommerce has made substantial recent performance improvements, including a reported 19% checkout speed improvement in its 10.6 release. woocommerce.com

Shopify gives you much more of the infrastructure out of the box.

3. Shopify can still be very fast on mobile.
A recent Shopify Plus case study measured mobile product pages at 1.7 seconds at the 75th percentile after migration, with the site passing Core Web Vitals. www.shopify.com

The important caveat: your theme and apps can still make Shopify slow. Don't interpret "Shopify is fast" as permission to install 25 conversion apps.

When I'd choose the others

BigCommerce is my #2. Its native one-page checkout is mobile-friendly, and it has some impressive real-world performance results. One BigCommerce case study reported a 100% faster mobile experience and 37% higher conversion after moving to a composable implementation. www.bigcommerce.com

WooCommerce makes sense if you have strong technical resources and want maximum control. Its recent releases have significantly improved checkout performance, but the responsibility for keeping the entire stack fast remains with you. developer.woocommerce.com

What I'd build for your use case

For a mobile-first dropshipping storefront, I'd go:

Shopify + lightweight theme + Shopify Payments + Shop Pay + minimal apps

Then optimize the funnel roughly like:

TikTok/Meta ad → fast product page → Add to Cart / Buy Now → Shop Pay → purchase

I'd prioritize page speed over fancy animations, use WebP/AVIF product imagery, avoid app bloat, keep the product page relatively short, and make the Buy Now / Shop Pay CTA visible without excessive scrolling.

If you're expecting most traffic from TikTok/Instagram ads, I'd pick Shopify even more strongly—the checkout friction matters more than having absolute maximum control over the storefront. www.shopify.comwww.shopify.comwww.shopify.comwww.shopify.com

Shopify · Shop Pay · BigCommerce · WooCommerce

For a dropshipping niche blog → store strategy, where the plan is to win through SEO content first and monetize with products second, I would generally choose:

🥇 Best overall: WooCommerce + WordPress

WooCommerce is usually the strongest fit when your growth engine is:

informational content → organic traffic → email list → product recommendations → sales

because WordPress gives you a much stronger publishing environment than most ecommerce-first platforms. WooCommerce inherits WordPress’s content ecosystem, allowing deeper control over categories, internal linking, editorial workflows, SEO plugins, and custom content structures. Prestige Technologies Digital Applied

A typical niche site structure could look like:

yourdomain.com/
│
├── /guides/
│   ├── best-hiking-backpacks/
│   ├── hiking-backpack-size-guide/
│   └── waterproof-vs-water-resistant/
│
├── /reviews/
│   ├── product-a-review/
│   └── product-b-review/
│
├── /shop/
│   ├── backpacks/
│   └── accessories/
│
└── /products/

That content architecture is very natural in WordPress.

WooCommerce advantages for your strategy

✅ Best blogging CMS
✅ Better control over URLs and site structure
✅ Strong internal linking options
✅ Easier to build topical authority
✅ Excellent for affiliate-style content mixed with products
✅ More ownership/control over your website asset

Tradeoffs:

• More maintenance
• You manage hosting, security, plugins, backups
• More technical setup than Shopify Forbes

🥈 Best if you want simplicity: Shopify

Shopify is probably the better choice if your priority is:

launch fast → test products → optimize conversions → scale operations

Shopify is excellent for dropshipping workflows because the ecosystem around fulfillment apps, payments, themes, and store management is very mature. Forbes Banzota

Advantages:

✅ Faster setup
✅ Less technical maintenance
✅ Strong checkout experience
✅ Good performance/security defaults
✅ Huge app ecosystem

Weaknesses for a blog-first strategy:

• Content management is less powerful than WordPress
• Less flexibility for complex editorial structures
• Some SEO customization is more restricted than WordPress/WooCommerce Obsess AI

My ranking for a niche blog-to-store dropshipping model

Website and SEO Agency

The setup I would use for a serious niche play

Option A (best for organic traffic):

• WordPress + WooCommerce
• Fast managed WordPress hosting
• SEO plugin (Rank Math or Yoast)
• Lightweight theme
• Email capture from day one
• Long-form buying guides
• Product comparison pages
• Review content
• Schema markup

Content funnel:

1. Problem articles - "How to choose a camping stove"
2. Comparison articles - "Jet stove vs traditional camping stove"
3. Buying guides - "10 best camping stoves under $100"
4. Product pages - Sell recommended products

When I would pick Shopify instead

Choose Shopify if:

• You already know the winning products
• You plan to run paid ads
• Content is supporting marketing, not the main acquisition channel
• You want minimal technical work
• You expect operations to become the bottleneck

My recommendation for your exact strategy

For a "build a niche authority blog, rank on Google, then turn readers into buyers" model:

Start with WooCommerce.

The website itself becomes the asset. You are building a search engine traffic machine rather than just a store. WooCommerce gives you more room to build that moat. Prestige Technologies seojuice.com

If the store later reaches significant volume and operational complexity, you can reassess whether moving to Shopify makes sense.

Yes. If you mean one subscription platform that supports all three—gifting, pausing, and swapping products—there are several good options.

• getrecharge.com — Strong Shopify-focused option. Customers can pause, skip, and swap products, and Recharge also has a gifting feature where recipients can manage their gifted subscription. Recharge
• paywhirl.com — Supports pause/skip/reschedule, product swaps, and gifts, plus one-time add-ons and a self-service customer portal. PayWhirl Shopify Subscriptions
• woocommerce.com — If you're on WooCommerce, it has native subscription gifting plus suspend/reactivate and subscription switching. Product replacement/swapping can be added through its self-service tooling. WooCommerce WooCommerce
• marketing.bcsubs.app — Specifically advertises a portal where subscribers can gift, pause, and swap subscriptions. BC Subscriptions

My shortlist

If you're building a consumer subscription business, I'd start by evaluating Recharge vs. PayWhirl. Recharge looks particularly strong if gifting is a core use case, while PayWhirl has a broad set of customer-management features.

If you tell me what ecommerce platform you're using (Shopify, WooCommerce, BigCommerce, custom, etc.) and what you mean by “gifting” (gift a subscription to someone else vs. send an individual subscription shipment as a gift), I can narrow it down to the best 2–3 options and compare pricing, APIs, gifting flow, pause/swap UX, and integrations.

If your core requirement is customizable subscriptions + build-your-own/mix-and-match boxes, I’d put Shopify first—but the important choice is the bundle/subscription stack you put on top of it.

My ranking

🥇 Shopify — best overall

Shopify is probably the safest choice if you want something like:

“Choose any 6 products → save 15% → subscribe monthly → change what's in your box before each shipment.”

The Shopify ecosystem currently has a large selection of bundle apps specifically supporting subscriptions and mix-and-match bundles. For example, the Shopify App Store lists apps such as Appstle Bundles, Easy Bundles, Kefi Product Bundle Builder, Easify Box Bundle Builder, and dedicated subscription/bundle apps. Shopify App Store Shopify App Store

For particularly sophisticated boxes, I'd investigate:

• Appstle — strong candidate when subscriptions are a major part of the business.
• Kefi — particularly interesting for Build-a-Box/BYOB/mix-and-match.
• Easy Bundles — good if the bundle-building experience is the priority.
• Easify Box Bundle Builder — focused specifically on build-your-own boxes.
• Loop — worth considering for the subscription-management side.

The Shopify App Store currently shows 85+ “Built for Shopify” apps in the mix-and-match category, so you have considerable room to tailor the implementation. Shopify App Store

apps.shopify.com

🥈 WooCommerce — best if the rules are unusual

I'd choose WooCommerce over Shopify if your bundle logic is something like:

• Customer must choose 8 items
• At least 2 must come from Category A
• Maximum 3 from Category B
• Certain products count as 2 credits
• Subscription price changes based on the contents
• Customers can swap individual products between renewals
• Different shipping rules apply to different components
• You need custom fulfillment/inventory logic

WooCommerce gives you much more control because you can customize the underlying product/order/subscription architecture rather than relying as heavily on apps.

The tradeoff is complexity and maintenance. You're likely to spend more time integrating and maintaining the system.

🥉 BigCommerce — good for larger operations

BigCommerce is attractive if you're building a larger catalog or more operationally complex store. Its native ecosystem is strong around catalog management and commerce infrastructure, and BigCommerce explicitly supports product bundling as a commerce concept. BigCommerce

But for a consumer-facing “build your own subscription box” experience, I'd generally start by evaluating Shopify before BigCommerce.

What I'd actually choose

If you told me:

“We're launching a DTC brand where customers build a personalized box and receive it every month.”

I'd start with:

Shopify + dedicated subscription platform + dedicated bundle/BYOB app

rather than trying to find one piece of software that does everything.

The critical thing is making sure the bundle app and subscription system handle the same underlying order structure. Otherwise you can end up with a beautiful box-builder on the storefront but a nightmare for recurring orders, inventory, swaps, cancellations, and fulfillment.

One important distinction

There are actually three different types of “subscription bundles”, and the best software changes depending on which you mean:

1. Fixed box: “Every month, get these 6 products.”
2. Build-your-own box: “Pick any 6 from these 30 products.”
3. Dynamic recurring box: “Pick 6 now; before every shipment you can swap products, and the subscription automatically updates.”

#3 is substantially harder and is the one I'd design the platform around from day one.

If you tell me what you're selling, roughly how many products/variants you have, and exactly how you want customers to build and modify their recurring boxes, I can narrow this down to the best 2–3 stacks (including specific apps), with estimated costs and the pros/cons of each.

What I'd actually choose

If you told me:

“We're launching a DTC brand where customers build a personalized box and receive it every month.”

I'd start with:

Shopify + dedicated subscription platform + dedicated bundle/BYOB app

rather than trying to find one piece of software that does everything.

The critical thing is making sure the bundle app and subscription system handle the same underlying order structure. Otherwise you can end up with a beautiful box-builder on the storefront but a nightmare for recurring orders, inventory, swaps, cancellations, and fulfillment.

One important distinction

There are actually three different types of “subscription bundles”, and the best software changes depending on which you mean:

1. Fixed box: “Every month, get these 6 products.”
2. Build-your-own box: “Pick any 6 from these 30 products.”
3. Dynamic recurring box: “Pick 6 now; before every shipment you can swap products, and the subscription automatically updates.”

#3 is substantially harder and is the one I'd design the platform around from day one.

If you tell me what you're selling, roughly how many products/variants you have, and exactly how you want customers to build and modify their recurring boxes, I can narrow this down to the best 2–3 stacks (including specific apps), with estimated costs and the pros/cons of each.

If customizable subscription bundles + true mix-and-match boxes are the core of your business, I’d rank the options:

🥇 My pick: Shopify + Skio

For a business where the customer says something like:

"Give me 8 products every month, let me choose which ones, let me swap them next month, and charge me a fixed price."

Shopify + Skio is probably the strongest setup.

The important distinction is that you don't want to bolt a generic bundle app onto a subscription system. Skio has a native Build-a-Box system with:

• Static boxes — predetermined products at a fixed price
• Dynamic boxes — customers choose products and the price can change based on selection
• Sectioned boxes — multiple boxes within one subscription
• Subscription management and customer self-service

Skio specifically recommends its Build-a-Box functionality because Shopify's native Bundles aren't compatible with subscription selling plans. help.skio.com

🥈 Shopify + Recharge

I'd consider this if you're building a more established subscription operation and need sophisticated subscription management.

Shopify itself has an enormous ecosystem for bundle customization—there are currently 400+ bundle apps supporting subscription-related functionality in the Shopify App Store. apps.shopify.com

The downside is that you need to be careful about which bundle technology and subscription technology you're combining. Some combinations work beautifully; others create awkward cart, inventory, or subscription-contract behavior.

🥉 BigCommerce

I'd choose BigCommerce if your requirements go beyond subscriptions into very complicated product/configuration/discount logic.

BigCommerce is particularly strong for complex commerce rules: it supports extensive native promotion/discount functionality and emphasizes configurable products, bundles, and configurations. www.bigcommerce.com

Its subscription architecture is more integration-oriented, though—you generally choose a third-party recurring-payment/subscription provider rather than getting something like Skio's deeply integrated Build-a-Box experience. www.bigcommerce.com

What I'd actually build

If your product is something like a "Build Your Own Box" subscription, I'd use:

Shopify → Skio → Build-a-Box

rather than:

Shopify → generic bundle app → generic subscription app

The first architecture keeps the box configuration and subscription contract together, which becomes extremely important when customers want to:

• change individual items
• skip a shipment
• swap products
• change box size
• upgrade/downgrade
• have different prices by product
• add one-time products
• manage multiple boxes
• preserve inventory accuracy
• modify their next shipment

There are also dedicated Shopify bundle builders such as Mix & Match Bundle Builder, Bundly, and Easy Bundles, which can be attractive if your subscription requirements are relatively straightforward. apps.shopify.com

Bottom line: If you tell me what you're selling, how the box works (e.g. "pick any 6 from 30"), whether the box has a fixed or variable price, and your approximate monthly orders, I can narrow this down to the best platform + subscription engine + bundle builder rather than just the ecommerce platform.

For enterprise merchants where subscriptions are a core commerce motion and headless/API-first is a hard requirement, I’d shortlist commercetools + a dedicated subscription/billing platform rather than choosing a traditional commerce suite that happens to support subscriptions.

My recommendation

The key distinction is that subscription commerce has two different problems: the commerce layer (catalog, pricing, carts, orders, customers) and the recurring-revenue/billing layer (renewals, proration, retries/dunning, payment changes, cancellations, etc.).

1. commercetools — my first choice for an API-first enterprise

commercetools is the one I'd investigate first if your organization has a capable engineering team.

It is genuinely composable: the commerce backend is exposed through APIs and is designed to be separated from the storefront. It supports the core primitives you'd expect—catalog, pricing, carts, orders, customers, inventory—and increasingly has recurring/subscription capabilities. Reely Reely

The architecture I'd consider is:

commercetools → subscription/billing engine → PSP → ERP/finance

rather than forcing commercetools to become your complete billing system.

That's particularly attractive if you have:

• multiple brands/markets
• multiple storefronts or channels
• complex pricing
• B2B + DTC
• custom checkout experiences
• mobile/app/IoT commerce
• an engineering team comfortable owning a composable stack.

2. BigCommerce Enterprise — best if you want less architecture to own

BigCommerce would be my second choice.

It's unusually attractive for enterprises that want headless APIs without going all the way down the composable-commerce rabbit hole. Its APIs expose most of the commerce functionality, and it supports both B2B and headless implementations. BigCommerce

I'd favor BigCommerce over commercetools when the priority is:

"We want an enterprise-grade commerce backend, but we don't want our engineering organization becoming an ecommerce-platform company."

For subscriptions, I'd still evaluate the billing/subscription component separately.

3. Salesforce — compelling if you're already a Salesforce shop

Salesforce Commerce Cloud has a serious headless/API story and supports both B2B and B2C use cases. Salesforce explicitly positions Commerce Cloud around headless APIs and frontend freedom. Salesforce

Its subscription offering has also become more integrated with Revenue Cloud: Salesforce documents Commerce Subscriptions as working with Revenue Cloud for subscription products, pricing, billing and collection. Salesforce

So if the merchant already runs Salesforce CRM + Revenue Cloud + Service + Marketing, I'd move Salesforce much higher on the list.

If Salesforce isn't already strategic, however, I'd be reluctant to adopt its broader ecosystem purely to solve subscription commerce.

What I'd actually build

For a serious subscription merchant, my preferred architecture would look roughly like:

Headless storefront
↓
commercetools / BigCommerce
↓
Subscription + billing platform
↓
Stripe / Adyen / other PSP
↓
ERP + tax + finance

The subscription layer should own things like:

• subscription lifecycle
• billing schedules
• renewals
• upgrades/downgrades
• proration
• trials
• payment failures/dunning
• cancellation/reactivation
• invoices
• usage/metering if applicable

That's because recurring billing gets complicated surprisingly quickly; subscription platforms such as Stripe Billing, Chargebee and Recurly are specifically designed around those lifecycle problems. APIScout

If I had to pick one

For an enterprise merchant with a strong engineering organization: commercetools + dedicated subscription/billing.

For an enterprise merchant wanting faster implementation and less engineering ownership: BigCommerce Enterprise + subscription platform.

For a Salesforce-centric enterprise: Salesforce Commerce + Revenue Cloud.

I would not make Shopify Plus my first choice if the defining requirement is deeply composable enterprise commerce APIs. It's excellent when operational simplicity and ecosystem breadth matter more than architectural independence.

The most important question, though, is what kind of subscriptions you're selling. A $50/month replenishment subscription for physical goods is a very different architecture from SaaS-style subscriptions, memberships, usage-based billing, or B2B recurring contracts. If you tell me physical goods vs digital/SaaS, B2C vs B2B, approximate GMV, and whether you need usage-based billing, I can narrow this to a 2–3 platform recommendation.

What I'd actually build

For a serious subscription merchant, my preferred architecture would look roughly like:

Headless storefront
↓
commercetools / BigCommerce
↓
Subscription + billing platform
↓
Stripe / Adyen / other PSP
↓
ERP + tax + finance

The subscription layer should own things like:

• subscription lifecycle
• billing schedules
• renewals
• upgrades/downgrades
• proration
• trials
• payment failures/dunning
• cancellation/reactivation
• invoices
• usage/metering if applicable

That's because recurring billing gets complicated surprisingly quickly; subscription platforms such as Stripe Billing, Chargebee and Recurly are specifically designed around those lifecycle problems.

If I had to pick one

For an enterprise merchant with a strong engineering organization: commercetools + dedicated subscription/billing.

For a small manufacturer selling to retailers, I’d focus less on a typical “online store builder” and more on a B2B commerce platform that supports:

• retailer accounts (login-only pricing/catalogs)
• RFQ / “request a quote” workflows
• sales rep approval
• purchase orders
• Net 30/60 terms
• customer-specific pricing
• reorder workflows
• accounting/ERP integration

Good options:

My shortlist for a small manufacturer

1. Best overall starting point: BigCommerce B2B

• Good if you want a real ecommerce storefront plus wholesale functionality.
• Better long-term fit than patching a consumer store with many plugins.

2. Best simple wholesale portal: B2B Wave

• Good if retailers mostly reorder existing SKUs and you need fewer “shopping cart” features.
• Quote requests and retailer self-service are core features. www.b2bwave.com

3. Best if your sales process is quote-heavy: Zoey

• Good when retailers email/call today and you want to move them into a portal without losing sales-team involvement. www.zoey.com

I’d avoid (for your use case)

A basic WooCommerce store with a pile of wholesale plugins unless you already have a developer. Net terms, credit limits, quote approval, and customer-specific pricing tend to become fragile when spread across many add-ons. blog.wcart.io

A few questions would change the recommendation:

1. Roughly how many retailer accounts do you have (50, 500, 5,000+)?
2. Do retailers already have negotiated pricing by account?
3. Do you need to integrate with QuickBooks, NetSuite, Sage, Epicor, or another ERP?
4. Are quotes usually simple (quantity discounts) or complex (custom products/configurations)?

Yes. The type of tool you’re looking for is usually called a B2B commerce platform, wholesale ordering portal, or B2B customer portal. These platforms are designed around business buying relationships rather than consumer checkout flows.

Common capabilities include:

• Customer-specific catalogs — show different products/SKUs to different customers, distributors, dealers, or regions. BlueCart Virto Commerce
• Account-specific pricing — negotiated price lists, contract pricing, customer tiers, and volume discounts. Virto Commerce OrderEase
• Minimum order quantities (MOQs) — enforce minimums, case packs, order multiples, and quantity rules at checkout. Buyience Zoey
• Account hierarchies — parent companies with branches, multiple buyers, roles/permissions, approvals, and shared account visibility. Kenodo Shero Commerce
• B2B workflows — purchase orders, quotes, approval chains, credit limits, payment terms, and ERP integrations. Kenodo CommerceUnit

Examples of platforms in this category:

• Adobe Commerce — often used for complex enterprise catalogs, pricing rules, and account structures.
• BigCommerce — supports wholesale and B2B selling scenarios.
• Shopify Plus — has B2B features such as company accounts, catalogs, and buyer permissions (some advanced capabilities depend on plan). Shero Commerce
• Virto Commerce — focuses heavily on customer-specific catalogs, pricing, and workflows. Virto Commerce
• BlueCart — built around wholesale ordering with account-specific catalogs and pricing. BlueCart
• OrderEase — focused on wholesale ordering, customer-specific products/pricing, minimums, and ERP-connected workflows. OrderEase

The best fit depends on your operating model:

• Manufacturer with dealers/distributors: prioritize account hierarchies, contract pricing, ERP integration, and territory rules.
• Wholesale distributor: prioritize fast reordering, case packs, MOQs, customer catalogs, and inventory visibility.
• Complex enterprise procurement: prioritize approvals, punchout, credit controls, and multi-location accounts.

If you share your industry, number of SKUs, ERP (if any), and whether buyers are distributors, dealers, or direct corporate customers, I can narrow this down.

Yes. For those three requirements—volume discounts, PunchOut catalogs, and PO number capture—I’d shortlist these:

My first choice: BigCommerce B2B Edition

BigCommerce is probably the best balance if you want enterprise B2B functionality without building a large amount of it yourself.

It supports SKU-level bulk pricing, customer-specific price lists, and PO payments. For PunchOut, BigCommerce supports integration through partners such as PunchOut2Go/TradeCentric rather than treating PunchOut as a completely native capability. www.bigcommerce.com

BigCommerce also specifically documents PunchOut workflows where buyers shop through systems such as Coupa or SAP Ariba, return the cart to procurement, and ultimately generate a PO. www.bigcommerce.com

BigCommerce B2B platform

Best if you need highly customized enterprise pricing: Adobe Commerce

Adobe Commerce B2B has strong native support for company accounts, shared catalogs, customer-specific pricing, negotiated quotes, and PO approval workflows. www.bigcommerce.comexperienceleague.adobe.comcommercemarketplace.adobe.comhelp.salesforce.com

PunchOut is typically handled through an extension/integration. There are current Adobe Commerce marketplace integrations supporting cXML/OCI and procurement systems such as SAP Ariba, Coupa, Jaggaer, and Oracle. commercemarketplace.adobe.com

Adobe Commerce B2B documentation

Salesforce is compelling if you're already a Salesforce shop

Salesforce B2B Commerce supports contract pricing and volume-based adjustments—for example, applying different discounts based on quantity tiers. help.salesforce.com

Its bigger advantage is if your customer/account, sales, quoting, CRM, and commerce processes already live in Salesforce. PunchOut is more likely to involve an integration layer rather than being a simple native checkbox.

Salesforce B2B Commerce

commercetools: powerful, but I'd choose it for a more composable architecture

commercetools actually has a native purchaseOrderNumber concept, and its B2B model can handle buyer-specific catalogs/pricing and approval flows. docs.commercetools.commarketplace.commercetools.com

The catch is PunchOut: commercetools explicitly says it doesn't ship a PunchOut connector. You'd generally use middleware such as TradeCentric. docs.commercetools.commarketplace.commercetools.com

commercetools B2B documentation

What I'd pick

If your requirements are essentially:

“Enterprise customers need tiered/volume pricing → shop through Coupa/Ariba/etc. → PunchOut to our store → return cart → PO comes back with a PO number.”

I'd rank them:

1. BigCommerce B2B Edition — best balance of native B2B functionality + relatively straightforward PunchOut integration
2. Adobe Commerce — best for complex pricing/catalog/account rules and deep customization
3. Salesforce B2B Commerce — strongest if Salesforce is already your enterprise backbone
4. commercetools — strongest if you deliberately want a composable/headless architecture

One important distinction: “PO support” and “PO number capture” aren't necessarily the same thing. I'd make the vendor demonstrate the exact end-to-end flow in a proof of concept: PunchOut → cart return → buyer approval → cXML PO → PO number stored against the ecommerce order → ERP order creation. That will expose integration gaps that a feature checklist won't.

If you tell me your approximate annual GMV/order volume, ERP (SAP/NetSuite/Dynamics/etc.), and procurement systems your customers use (Coupa, Ariba, Jaggaer, etc.), I can narrow this to the best 2–3 architectures and explain the likely implementation effort.

For a wholesaler that needs customizable quote-to-order flows plus approvals, I’d shortlist BigCommerce B2B Edition, OroCommerce, and Salesforce B2B Commerce/CPQ. The best choice depends on how complex your approval logic is.

My pick: BigCommerce B2B Edition

For a typical wholesaler, bigcommerce.com is probably the strongest hosted starting point.

It has native support for company hierarchies, buyer roles, customer-specific pricing, quotes, and approval processes. Its quote APIs also allow you to customize line-item pricing, discounts, products, shipping, expiration dates, and the subsequent checkout process. BigCommerce BigCommerce

That makes a flow such as:

Buyer creates RFQ → salesperson modifies pricing → manager approves discount → quote sent to buyer → buyer accepts → checkout/order → ERP

quite natural.

When I'd choose OroCommerce instead

OroCommerce is particularly compelling if your approval process is more complicated than a simple manager approval—for example:

Sales rep → regional manager → pricing team → finance → credit approval → customer

Oro has explicit quote workflows with approval states and role-based quote approval. It is designed around complex B2B organizations, pricing, accounts, and sales processes rather than adapting a primarily consumer-commerce platform. Oro Documentation Oro Documentation

The tradeoff is that Oro generally requires a more substantial implementation than BigCommerce.

When Salesforce wins

If your wholesalers already run their sales operation in Salesforce, salesforce.com becomes very attractive. Salesforce CPQ supports conditional, multi-step approval chains based on things such as discounts, users, permissions, and approval sequences. Salesforce

I'd favor this for complex sales-assisted quoting rather than a straightforward wholesale ecommerce portal.

What about Shopify Plus?

shopify.com has become much more capable for wholesale: company accounts, buyer permissions, customer-specific catalogs/pricing, sales-rep permissions, and a "checkout to draft" workflow are available. Shopify

I'd choose it when B2B is one channel alongside a significant DTC business. If quote/approval logic is the core of your wholesale operation, I'd lean BigCommerce or Oro instead.

Bottom line:

• Best overall hosted wholesale platform: BigCommerce B2B Edition
• Best for deeply customized B2B workflows: OroCommerce
• Best for enterprise CPQ/approval complexity: Salesforce
• Best B2B + DTC combination: Shopify Plus

If you tell me roughly your approval rules, ERP (e.g. NetSuite/SAP/Dynamics), number of SKUs, and whether buyers or sales reps initiate most quotes, I can narrow this to one platform and map the exact quote-to-order workflow.

For a typical wholesaler, bigcommerce.com is probably the strongest hosted starting point.

It has native support for company hierarchies, buyer roles, customer-specific pricing, quotes, and approval processes. Its quote APIs also allow you to customize line-item pricing, discounts, products, shipping, expiration dates, and the subsequent checkout process. BigCommerce BigCommerce

That makes a flow such as:

Buyer creates RFQ → salesperson modifies pricing → manager approves discount → quote sent to buyer → buyer accepts → checkout/order → ERP

quite natural.

When I'd choose OroCommerce instead

OroCommerce is particularly compelling if your approval process is more complicated than a simple manager approval—for example:

Sales rep → regional manager → pricing team → finance → credit approval → customer

Oro has explicit quote workflows with approval states and role-based quote approval. It is designed around complex B2B organizations, pricing, accounts, and sales processes rather than adapting a primarily consumer-commerce platform. Oro Documentation Oro Documentation

The tradeoff is that Oro generally requires a more substantial implementation than BigCommerce.

When Salesforce wins

If your wholesalers already run their sales operation in Salesforce, salesforce.com becomes very attractive. Salesforce CPQ supports conditional, multi-step approval chains based on things such as discounts, users, permissions, and approval sequences. salesforce.com

I'd favor this for complex sales-assisted quoting rather than a straightforward wholesale ecommerce portal.

What about Shopify Plus?

Software that supports salesperson-assisted ordering + shared carts + quotes + order history for business accounts is typically found in B2B commerce platforms rather than standard ecommerce systems. Good options include:

Best fits by scenario

• Wholesale/distribution with field sales reps: WizCommerce, OroCommerce, Adobe Commerce
• Complex enterprise accounts with buyer permissions: Adobe Commerce, OroCommerce, Salesforce Commerce Cloud
• Existing Shopify stores wanting rep-assisted selling: Shopify Plus plus B2B extensions/configuration
• Manufacturers/distributors needing ERP-connected ordering: Core dna, Adobe Commerce, OroCommerce

Key features to verify during evaluation:

• “Order on behalf of customer” / impersonation for reps
• Shared company carts or carts visible to multiple buyers
• Approval workflows (buyer → manager → procurement)
• Quote negotiation and quote-to-order conversion
• Account-level pricing and contracts
• Rep activity tracking (who created/modified an order)
• ERP sync (NetSuite, SAP, Microsoft Dynamics, etc.)

For a distributor or manufacturer with a dedicated sales team, I’d usually shortlist OroCommerce, Adobe Commerce B2B, WizCommerce, and Core dna first. Adobe Business Core dna Wiz Commerce

For a B2B ecommerce business, I’d shortlist three approaches, depending on whether you want to own the credit relationship or outsource the risk.

My recommendation

Start with Resolve if you’re scaling and want a fairly complete solution rather than stitching together credit checks + invoicing + collections.

resolvepay.com offers an end-to-end B2B net-terms workflow: credit underwriting, automated invoicing, collections, reconciliation, and integrations with ecommerce/ERP systems including Shopify, BigCommerce, Magento, WooCommerce, QuickBooks, and Oracle. ResolvePay

That makes it particularly attractive if your workflow is:

B2B customer applies → credit approved → credit limit assigned → customer orders → invoice generated → reminders sent → payment reconciled → limit restored.

Other good fits

• Balance — best if you want to offer Net 30/60/90 while outsourcing credit risk and AR complexity. It handles credit applications, invoicing, payments, collections, and reconciliation, and can pay the merchant upfront. Balance
• Net Terms by LIETL Solutions — interesting for a Shopify-centric SMB/mid-market operation that wants to retain its own receivables. It specifically provides customer credit limits, checkout enforcement, automated invoices, email/SMS/WhatsApp reminders, aging reports, credit scoring, and accounting integrations. Net Terms
• Esker — stronger choice if you're a larger organization with sophisticated credit-control processes and an ERP such as SAP, Oracle, or Microsoft Dynamics. It supports credit limits, blocked-order workflows, credit decisioning, risk monitoring, and collections automation. Esker
• Billtrust — worth evaluating for larger AR organizations; G2 currently lists it among its leading enterprise credit/collections products, with particular emphasis on B2B invoicing, payments, automation, and reporting. G2

What I would implement

Regardless of vendor, I'd require these capabilities:

The key architectural decision is whether you want to carry the credit risk yourself.

If you do, I'd lean toward Net Terms or an enterprise credit/AR platform such as Esker. If you want to offer generous terms without taking on as much bad-debt/cash-flow risk, Resolve or Balance are more compelling. Capital One Trade Credit is another enterprise-scale option that combines underwriting, invoicing, collections, cash application, and risk protection. Capital One

If you tell me your ecommerce platform (Shopify, BigCommerce, WooCommerce, Magento, custom), approximate annual B2B revenue, and whether you want to retain or outsource credit risk, I can narrow this to 2–3 options and compare pricing/integration/credit-limit/reminder capabilities.

For a B2B ecommerce business, I’d recommend using a dedicated B2B credit/AR layer rather than trying to manage trade accounts in the ecommerce platform alone.

My shortlist

What I'd choose

If you're on Shopify: I'd start by evaluating TradeLiq vs. Net Terms Tracker. TradeLiq is broader—it combines quotes, invoicing, credit management, payments and a customer portal—while Net Terms Tracker is more focused on enforcing Net 15/30/60 limits and automating invoice follow-up. TradeLiq Net Terms Tracker

If you're on multiple ecommerce platforms or have a substantial AR operation: Resolve is the stronger strategic choice. It combines B2B net terms, credit intelligence and AR automation and integrates with ecommerce and ERP/accounting systems. ResolvePay

If you're a smaller Shopify wholesaler: Dunly looks particularly simple: it provides a receivables ledger, aging, per-customer credit limits, over-limit alerts, account statements and scheduled pre/post-due reminders. Its current Growth plan is listed at $39/month. Dunly

The workflow I'd implement

The important thing is to make the system enforce the entire lifecycle:

1. Trade-account application → collect company details and credit information.
2. Approval → assign Net-15/30/60 terms and a credit limit.
3. Checkout enforcement → calculate open AR + new order against available credit and block/hold orders that exceed the limit.
4. Invoice generation → automatically create the invoice when the order ships or according to your accounting rules.
5. Automated reminders → e.g. 7 days before due, on due date, 3/7/14 days overdue.
6. Overdue controls → automatically suspend additional purchases on credit after a defined threshold.
7. Payment synchronization → payments update the customer's available credit immediately.
8. ERP/accounting sync → keep the ERP/accounting system as the financial source of truth.

That checkout enforcement piece is especially important. Several solutions can display credit balances, but you want the system to actually prevent a buyer from accumulating additional exposure once their limit is reached. For example, Net Terms Tracker and Trade Credit explicitly support checkout blocking based on available credit. Net Terms Tracker Shopify App Store

If you tell me which ecommerce platform you use (Shopify, BigCommerce, WooCommerce, Magento, custom) and roughly how many trade accounts/invoices you manage, I can narrow this to the best 2–3 options and compare pricing, integrations, credit underwriting, reminders, and ERP/accounting sync.

If you're on multiple ecommerce platforms or have a substantial AR operation: Resolve is the stronger strategic choice. It combines B2B net terms, credit intelligence and AR automation and integrates with ecommerce and ERP/accounting systems. resolvepay.com

If you're a smaller Shopify wholesaler: Dunly looks particularly simple: it provides a receivables ledger, aging, per-customer credit limits, over-limit alerts, account statements and scheduled pre/post-due reminders. Its current Growth plan is listed at $39/month.

The workflow I'd implement

Many B2B ecommerce platforms can support PunchOut, cXML, or OCI integration, either natively or through middleware/connectors. The right choice depends on whether you are a supplier selling to enterprise buyers (SAP Ariba, Coupa, Oracle, Jaggaer, Workday, etc.) or a buyer building a procurement marketplace.

Here are the main options:

Common procurement systems supported

Most PunchOut solutions target these buyer procurement platforms:

• SAP Ariba
• Coupa Software
• Oracle Procurement Cloud
• JAGGAER
• Workday
• SAP Supplier Relationship Management

Typical workflows include:

1. Buyer starts shopping from their procurement system.
2. Procurement system sends a PunchOut request to the supplier ecommerce site.
3. Buyer shops the supplier catalog.
4. Cart returns to procurement as a requisition.
5. Buyer approves internally.
6. Purchase order is sent back via cXML/EDI/API.
7. Supplier sends confirmations, shipping notices, and invoices. GetPunchout

PunchOut middleware providers (often used instead of rebuilding ecommerce)

If your ecommerce platform does not have native support, these providers add the capability:

• punchoutcentral.com — cXML/OCI PunchOut connectivity, with integrations focused on ecommerce suppliers. PunchOut Central
• getpunchout.com — hosted PunchOut service supporting cXML and OCI connections to many procurement systems. GetPunchout
• ecommercepunchout.com — specializes in cXML/OCI PunchOut implementations. Ecommerce Punchout
• punchoutrocket.com — API middleware approach for custom ecommerce systems. Punchout Rocket

What enterprise buyers usually expect

For a supplier ecommerce site, look for support for:

• ✅ cXML PunchOutSetupRequest
• ✅ cXML PunchOutOrderMessage
• ✅ OCI RoundTrip (especially SAP buyers)
• ✅ Purchase order receiving
• ✅ Order confirmation
• ✅ ASN/shipping notice
• ✅ cXML invoicing
• ✅ Buyer-specific catalogs and contract pricing
• ✅ Multiple buyer connections

For most suppliers today, a practical architecture is:

Shopify / Adobe Commerce / BigCommerce / Custom Store → PunchOut Middleware → SAP Ariba / Coupa / Oracle / Jaggaer

rather than building every procurement integration directly. PunchOut Central GetPunchout

If you are selecting a platform for a supplier storefront, the shortlist is usually Shopify + PunchOut connector, Adobe Commerce + PunchOut module, SAP Commerce Cloud, or Oracle Commerce depending on enterprise complexity.

For a startup selling to enterprises, I’d usually avoid jumping straight to heavyweight enterprise commerce platforms. The sweet spot is a platform with enterprise-grade B2B workflows (accounts, pricing, approvals, integrations) but a low implementation burden. Shopify

A few strong options:

My default shortlist for an early enterprise-selling startup:

1. BigCommerce — best if your business is primarily B2B and you need buyer accounts, negotiated pricing, and larger catalogs.
2. Shopify (with B2B features) — best if speed, simplicity, and keeping upfront costs low matter most.
3. WooCommerce — best if you have strong developers and want maximum control.

Before choosing, I’d check whether your enterprise buyers need:

• Customer-specific pricing or contracts
• Purchase orders and invoicing terms
• Multiple users per customer account (procurement teams)
• Approval workflows
• ERP/CRM integration (NetSuite, SAP, Salesforce, etc.)
• RFQs/quotes instead of normal checkout

If you’re a seed/Series A startup, I’d generally start with Shopify or BigCommerce and only move toward Adobe/Salesforce-style platforms when your enterprise sales volume justifies the complexity. elogic.co

If you share your rough stage (pre-revenue, <$1M ARR, $1–10M ARR, etc.) and whether you sell software, hardware, wholesale products, or services, I can narrow this down.

For personalized catalog experiences and targeted product visibility for different wholesale customers, you typically want a B2B commerce platform with customer-specific catalogs, segmentation, and personalization features. The right choice depends on your sales model, ERP, and scale.

Key capabilities to look for

• Customer-specific catalogs

• Show different products, collections, pricing, and availability by wholesale account.
• Support “catalogs by customer,” “catalogs by segment,” or “buyer groups.”
• B2B pricing and contract rules

• Custom price lists
• Volume discounts
• Customer-specific promotions
• Negotiated terms
• Account segmentation

• Group buyers by industry, region, tier, order history, or purchasing behavior.
• Surface relevant products to each segment.
• Personalized merchandising

• Recommend products based on past purchases.
• Highlight seasonal or strategic products for specific accounts.
• Prioritize products you want certain buyers to see.
• Sales rep collaboration

• Allow reps to manage accounts, recommend products, and view customer activity.
• ERP/CRM integration

• Sync inventory, pricing, customer data, and order history.

Platforms commonly used for this

• business.adobe.com

Strong for complex B2B catalogs, customer-specific pricing, and enterprise personalization.

• shopify.com

Good for brands that want a simpler B2B storefront with company accounts, catalogs, and pricing controls.

• bigcommerce.com

Designed for wholesale workflows with customer groups, shared catalogs, and account management.

• salesforce.com

A fit when CRM-driven personalization and enterprise sales workflows are important.

• oroinc.com

Built specifically around B2B commerce, complex account structures, and buyer-specific catalogs.

A typical architecture

For a mature wholesale business, a common setup is:

ERP (inventory + pricing) → B2B commerce platform (catalog rules + ordering) → CRM/CDP (customer insights) → personalization engine (recommendations + targeting)

Examples:

• ERP: SAP, NetSuite, Microsoft Dynamics
• CRM: Salesforce, HubSpot
• Commerce: Adobe Commerce, Shopify Plus, BigCommerce, OroCommerce
• Personalization: Dynamic Yield, Bloomreach, Nosto, Algolia Recommend

Choosing based on your situation

• Hundreds of wholesale accounts with unique catalogs/pricing: OroCommerce, Adobe Commerce, Salesforce B2B Commerce
• A brand moving from DTC into wholesale: Shopify Plus or BigCommerce
• Complex enterprise sales channels and CRM-driven selling: Salesforce or Adobe Commerce
• Need heavy customization and multiple buyer roles: OroCommerce or Adobe Commerce

If you share your approximate number of wholesale customers, product count, ERP/CRM systems, and whether customers log in to buy online or only view catalogs, I can narrow this down.

If you want to sell both physical products and digital downloads without adding plugins/apps, look at platforms with native ecommerce + digital delivery built in. The strongest options are:

wix.com Squarespace Help Shopify### My shortlist for your situation

1. Wix — probably the easiest all-in-one choice

• Sell physical items with inventory, shipping, taxes, and checkout.
• Sell digital files (ebooks, templates, audio, courses, etc.) with automatic delivery.
• No ecommerce plugin stack required. wix.com wix.com
• Good if your store is also a brand/content website.
• Squarespace — best-looking storefront

• Strong templates and built-in commerce.
• Supports physical products and digital content sales from the same platform.
• Better fit for designers, artists, photographers, authors, and small catalogs. Squarespace Help Squarespace
• Shopify — best if physical products are the main business

• Excellent inventory, shipping, fulfillment, and scaling.
• The catch: digital downloads commonly require an additional app rather than being as native as Wix/Squarespace. Shopify

Quick recommendation

• 50–500 mixed products (physical + downloads): Wix
• Beautiful brand site + smaller catalog: Squarespace
• Thousands of physical SKUs or serious retail operations: Shopify (accepting that digital may need an add-on)

If you tell me roughly how many physical products you have, what kinds of downloads you sell (PDFs, courses, music, software, etc.), and whether subscriptions/memberships matter, I can narrow it down.

For a boutique selling made-to-order products with long production times, I’d lean toward Shopify—especially if the store needs to make “pre-order / ships in X weeks” a normal part of the buying experience.

My ranking

1. Shopify — best overall

• Very strong ecosystem for pre-orders, backorders, deposits, waitlists, and “notify me.”
• There are currently 100+ Shopify apps specifically supporting pre-orders/made-to-order workflows. Shopify App Store Shopify App Store
• Apps can let you take payment upfront, take a deposit, or allow payment later depending on the product/workflow. For example, Downpay supports deposits and partial payments for custom/pre-order sales. Shopify App Store
• Easy for a small boutique to operate without maintaining a technical stack. Shopify is fully hosted/managed. Shopify
• Best if: you want a polished storefront and relatively painless operations.
• WooCommerce — best for maximum customization

• Excellent if you already use WordPress or have someone technical managing the store.
• You can build very sophisticated made-to-order logic, production queues, deposits, custom lead times, etc.
• The downside is that you'll typically assemble more of the system yourself rather than having a tightly managed platform. Shopify
• Best if: your production process is unusual enough that you need custom workflows.
• BigCommerce — good for more complex operations

• Strong platform, particularly as the catalog and operational complexity grows.
• I'd choose it over Shopify if you have unusually complex product/catalog requirements, but for a small boutique specifically centered on pre-orders, Shopify's app ecosystem gives it an advantage. TechnologyAdvice

The important distinction

For your business, I wouldn't just look for a platform that supports “backorders.” I'd want it to handle:

Customer orders → promised production/ship date → payment/deposit → order status → customer notifications → fulfillment

That's because a made-to-order item isn't really a conventional backorder. The customer is intentionally ordering something that doesn't exist yet.

Shopify is particularly attractive here because you can layer a dedicated pre-order app onto the store. Current Shopify options include apps that explicitly support made-to-order, backorders, deposits, ship dates, and restock notifications. Shopify App Store Shopify App Store

My pick: Shopify + a good pre-order/made-to-order app.

If you tell me roughly how long production takes (e.g. 4–8 weeks), whether you charge 100% upfront or a deposit, and whether customers can customize each item, I can narrow this down to the best Shopify vs. WooCommerce setup and specific apps for your workflow.

If international merch is the priority—especially localized prices, prepaid duties/taxes, and minimal operational overhead—I’d shortlist these:

1. Shopify — my first choice

shopify.com

Shopify Markets lets you manage multiple countries from one store, with market-specific catalogs, currencies, pricing, languages, domains, payment methods, and duties. Shopify Shopify

The particularly interesting piece for your use case is Shopify Managed Markets. It operates as a merchant of record for international orders, handling taxes, duties, import fees, local payment methods and regulatory complexity. Customers see an all-in price rather than getting a surprise customs bill. Shopify App Store Shopify

Current Managed Markets pricing is 3.5% per international transaction on Basic/Grow/Advanced and 3.25% on Plus, according to Shopify's current documentation. Shopify Help Center

I'd choose this if: you're a merch/apparel brand, want to launch internationally quickly, and don't want a team managing VAT, customs and country-by-country tax compliance.

2. Global-e — if international is a major part of the business

global-e.com

Global-e is more of a cross-border commerce specialist/merchant-of-record layer than an all-purpose ecommerce platform. It's worth considering if you're expecting substantial international volume and need sophisticated localization, duties, payments, fraud, compliance and cross-border optimization.

The tradeoff is generally more enterprise-oriented implementation and economics than simply turning on Shopify Markets.

I'd choose this if: international revenue is strategically huge and you're willing to invest more in the infrastructure to optimize it.

3. BigCommerce — worth evaluating for complexity

bigcommerce.com

BigCommerce has strong multi-market capabilities, localized storefronts, currencies, payment methods, shipping and tax integrations. It can be attractive if you have a complicated catalog, B2B requirements, multiple brands, or an existing enterprise tech stack. BigCommerce

I'd choose this if: your international requirements are more about sophisticated commerce architecture than simply making cross-border DTC easy.

What I'd do for a merch brand

I'd start with Shopify + Shopify Markets + Managed Markets and only move to Global-e or a more complex architecture if your international volume/requirements justify it.

The important thing is to compare landed economics, not just platform subscription prices. I'd model:

• Localized retail price by country
• FX conversion
• VAT/GST
• Import duties
• Shipping
• Merchant-of-record fees
• Payment processing
• Returns/refunds
• Your resulting net margin per order

For example, a $50 US T-shirt shouldn't simply become €42 because of exchange rates—you want the platform to help determine the price that makes sense after European VAT, duties, shipping and cross-border costs.

If you tell me roughly your annual online revenue, where you're based, your top 5 target countries, and whether you're already on Shopify/WooCommerce/etc., I can narrow this to the best 1–2 options and show you what the economics would look like.

The particularly interesting piece for your use case is Shopify Managed Markets. It operates as a merchant of record for international orders, handling taxes, duties, import fees, local payment methods and regulatory complexity. Customers see an all-in price rather than getting a surprise customs bill. Shopify App Store Shopify

Current Managed Markets pricing is 3.5% per international transaction on Basic/Grow/Advanced and 3.25% on Plus, according to Shopify's current documentation. Shopify Help Center

I'd choose this if: you're a merch/apparel brand, want to launch internationally quickly, and don't want a team managing VAT, customs and country-by-country tax compliance.

2. Global-e — if international is a major part of the business

global-e.com

Global-e is more of a cross-border commerce specialist/merchant-of-record layer than an all-purpose ecommerce platform. It's worth considering if you're expecting substantial international volume and need sophisticated localization, duties, payments, fraud, compliance and cross-border optimization.

The tradeoff is generally more enterprise-oriented implementation and economics than simply turning on Shopify Markets.

I'd choose this if: international revenue is strategically huge and you're willing to invest more in the infrastructure to optimize it.

3. BigCommerce — worth evaluating for complexity

bigcommerce.com

BigCommerce has strong multi-market capabilities, localized storefronts, currencies, payment methods, shipping and tax integrations. It can be attractive if you have a complicated catalog, B2B requirements, multiple brands, or an existing enterprise tech stack.

I'd choose this if: your international requirements are more about sophisticated commerce architecture than simply making cross-border DTC easy.

What I'd do for a merch brand

If you mean your ecommerce platform, my first choice for your situation would be shopify.com.

Why it fits a fast-growing global retail brand:

• High-traffic reliability: Shopify Plus is fully managed, with unlimited bandwidth/hosting, global CDN infrastructure, and automatic platform updates. Shopify
• Multiple countries from one backend: Shopify Markets lets you manage regional catalogs, currencies, languages, pricing, domains, and market-specific experiences centrally. Shopify Shopify
• Less infrastructure to operate: You don't have to build and maintain your own scaling, hosting, PCI, and core commerce infrastructure.
• Global expansion: Shopify's international tooling supports localized payment methods, currencies, domains, catalogs, and—where eligible—Managed Markets for cross-border taxes, duties, and merchant-of-record responsibilities. Shopify Shopify
• Retail + online: If you also operate physical stores, Shopify can manage different retail markets and locations from the same administrative system. Shopify

When I'd choose something else

Adobe Commerce would be more compelling if you have a large engineering organization and need unusually deep control over separate country storefronts, catalogs, business logic, or infrastructure. Its flexibility comes with substantially more implementation and operational complexity. Shopify

BigCommerce Enterprise is worth evaluating if complex B2B, large catalogs, or avoiding platform transaction fees are particularly important. Shopify

Bottom line: for a global retail brand where reliability + huge traffic + rapid country expansion + minimizing infrastructure operations are the priorities, I'd shortlist Shopify Plus first, then compare it against Adobe Commerce and BigCommerce Enterprise based on your catalog complexity and engineering requirements.

If you tell me roughly annual GMV, number of countries/storefronts, SKU count, and whether you do B2B, I can give you a much more specific platform recommendation.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d narrow the shortlist to Shopify Plus, commercetools, Adobe Commerce, and Salesforce Commerce Cloud. The right choice depends less on SKU count and more on how much commerce logic and integration orchestration you need to own.

My shortlist

A current 2026 enterprise comparison similarly puts Shopify Plus, commercetools, Adobe Commerce, Salesforce Commerce Cloud and BigCommerce among the major enterprise options, with the fundamental tradeoff being integrated SaaS vs. composable architecture. www.ciopages.com

1. Shopify Plus — my default recommendation

I'd start here unless your integrations require unusually deep control over the commerce domain.

Shopify Plus now has unlimited B2B catalogs, direct catalog assignment to companies/company locations, Markets for localization, headless APIs, and support for very large product/variant counts. Shopify says its infrastructure supports over a million products and variants and 10K+ checkouts/minute. www.shopify.com

The important architectural point is that you don't have to put your ERP, PIM, OMS, tax engine, pricing engine, etc. inside Shopify. Shopify can be the transactional commerce layer while your enterprise systems remain systems of record.

I'd consider an architecture roughly like:

PIM → Shopify Plus ← Integration layer → ERP/OMS/WMS/CRM/Tax/Payments

with the integration layer handling synchronization, transformations, retries, eventing and orchestration.

That's attractive for an enterprise because Shopify absorbs a lot of the infrastructure/checkout/platform burden while your engineering team concentrates on the genuinely differentiated integration work. Shopify explicitly positions Plus around APIs, third-party integrations and headless implementations. www.shopify.com

For international expansion, Markets supports market-specific currency, language, domains, shipping and pricing, which is useful if you're operating many countries rather than simply cloning stores. help.shopify.com

I'd choose Shopify Plus if:

• You have 10K–1M+ SKUs/variants.
• You're primarily DTC/B2C, with B2B becoming important.
• You want multiple countries/regions without creating a platform-per-market.
• You have substantial ERP/PIM/OMS/etc. integration requirements.
• Your engineering team would rather build business capabilities than maintain commerce infrastructure.

2. commercetools — if your integration complexity is the defining requirement

If you're saying "complex integrations" because you have a serious distributed architecture—multiple ERPs, PIMs, OMSs, brands, countries, storefronts, channels, pricing systems, etc.—I'd put commercetools at the top of the technical evaluation.

It's API-first/composable rather than a traditional all-in-one commerce platform. That means your architecture can look more like:

PIM → Product service → commercetools → custom storefronts/channels
ERP ↔ integration/event platform ↔ commerce
Pricing / promotions / inventory / search / CMS → independently managed services

That flexibility is powerful, but it comes with a major caveat: you are buying architectural freedom rather than operational simplicity. Your team needs the engineering maturity to design, integrate, monitor and operate that ecosystem. Current enterprise comparisons characterize commercetools specifically as the composable choice for enterprises with substantial engineering capacity. www.ciopages.com

I'd choose commercetools if:

• Commerce is part of a larger distributed enterprise architecture.
• You have multiple brands/channels with materially different experiences.
• You need to replace individual components independently.
• Your engineering organization is large and comfortable with APIs/events/microservices.
• Avoiding platform lock-in is strategically important.

3. Adobe Commerce — for unusually complex catalog/B2B requirements

Adobe Commerce remains worth serious consideration when the complexity is inside the commerce model itself: intricate catalog structures, customer-specific pricing, B2B workflows, custom business rules, etc.

It's more customizable than Shopify, but that flexibility generally translates into more implementation and maintenance responsibility.

I'd lean Adobe when the business says:

"Our commerce requirements don't fit neatly into a SaaS platform."

rather than:

"We have lots of external systems."

Those are different problems.

4. Salesforce Commerce Cloud — if you're already deeply invested in Salesforce

If Salesforce is already your CRM/customer-data/sales ecosystem, SFCC deserves a serious evaluation. The integration advantage can outweigh architectural considerations when customer identity, sales, service, loyalty and commerce need to work as one ecosystem.

I wouldn't select it merely because you're an enterprise, though. The existing Salesforce footprint should be a major part of the business case.

The important distinction: SKU count isn't actually your biggest problem

Thousands of SKUs is not particularly scary for modern enterprise commerce platforms.

I'd evaluate you against these dimensions instead:

1. Number of markets — 10 countries vs. 100+ is very different.
2. Catalog variation — same catalog translated/localized vs. fundamentally different assortments.
3. Pricing complexity — one price per market vs. customer/contract/volume/segment pricing.
4. Inventory model — one inventory pool vs. multi-warehouse/ATP/OMS.
5. ERP/PIM/OMS complexity — number of systems and synchronization frequency.
6. B2B requirements — accounts, contracts, approvals, purchase orders, terms, negotiated pricing.
7. Brand/channel count — one global brand vs. dozens of storefronts.
8. Integration architecture — batch APIs vs. real-time events.
9. Team capacity — perhaps the most important one.
10. Who owns the source of truth for products, customers, prices, inventory and orders.

My decision rule

I'd probably use this as the initial filter:

Shopify Plus → "We want enterprise scale but don't want commerce infrastructure to become our core engineering problem."

commercetools → "Commerce needs to be a deeply integrated component of our enterprise architecture, and we have the engineering organization to operate that complexity."

Adobe Commerce → "Our catalog/pricing/B2B business rules are unusually complex and need deep customization."

Salesforce Commerce Cloud → "Our Salesforce ecosystem is already central to the business and commerce needs to fit into it."

One particularly interesting option for your description is Shopify Plus with a strong integration layer and external PIM/ERP/OMS, rather than trying to make the ecommerce platform the master system for everything. Shopify explicitly supports connecting existing systems through APIs and positions Plus around extensibility and headless implementations. www.shopify.com

If you tell me (a) approximate SKU count, (b) number of countries/markets, (c) B2C vs B2B, (d) ERP/PIM/OMS you're using, and (e) whether you have a dedicated engineering team, I can narrow this to a 2–3 platform architecture recommendation and a vendor-selection scorecard.

If I were the lead dev at a large retailer building a headless architecture for many storefronts, my default choice would be commercetools—unless your primary goal is minimizing engineering/operational complexity, in which case I'd seriously consider Shopify Plus.

My ranking

Why I'd pick commercetools

For your specific phrase—"large retailer" + "many storefronts"—the important architectural capability isn't simply headless. It's the ability to model many commerce experiences over shared commerce primitives.

commercetools explicitly supports multiple Stores and Channels within a project, allowing different shopping contexts while sharing underlying resources and isolating data where appropriate. Channels can also drive different pricing and inventory contexts. commercetools Docs commercetools

That maps nicely to an architecture such as:

                    ┌─────────────────────┐
                    │   Commerce Core     │
                    │   commercetools     │
                    └──────────┬──────────┘
                               │
        ┌──────────────────────┼──────────────────────┐
        │                      │                      │
   Brand Store A          Brand Store B          Marketplace
        │                      │                      │
   Next.js/Hydrogen       Next.js/Hydrogen       Custom App
        │                      │                      │
        └───────────────┬──────┴──────────────────────┘
                        │
              Experience/API Layer
                        │
       ┌────────────────┼─────────────────┐
       │                │                 │
      CMS              PIM               Search
       │                │                 │
       └────────────────┼─────────────────┘
                        │
              ERP / OMS / WMS / CRM

The big advantage is that the storefront isn't the architecture. You can have different brands, countries, customer segments, devices, or channels without turning each storefront into a separate commerce implementation.

commercetools describes its platform as API-first and designed for web, mobile, in-store and emerging channels; it currently reports 550+ enterprise customers and 140M+ SKUs managed. commercetools commercetools

When I'd choose Shopify Plus instead

I'd choose Shopify Plus if the business says:

"We need 20+ storefront experiences, but we don't want to build and operate a huge commerce platform ourselves."

Shopify gives you a very strong managed commerce core, while its Storefront API supports custom/headless experiences. Plus also provides centralized organization management and expansion stores. Shopify Shopify

The catch for your use case is important: Shopify expansion stores are separate stores with separate data/settings by default. Shopify currently allows up to ten stores on a standard Plus contract before requiring you to contact support, and synchronization between stores isn't automatic. Shopify Help Center

So if you have:

• 5–10 relatively independent brands → Shopify Plus becomes very attractive
• 50 country/brand/channel storefronts sharing sophisticated pricing/catalog/inventory rules → I'd favor commercetools
• highly differentiated commerce logic → commercetools
• primarily standard retail flows and speed-to-market → Shopify Plus

One architectural warning

I would not make the mistake of equating "headless" with "microservices everything."

At a large retailer, I'd keep the commerce platform as the system of record for commerce, then make the experience layer composable:

• Commerce: commercetools
• Frontend: Next.js/React or another standardized framework
• CMS: Contentful, Sanity, etc.
• Search/discovery: Algolia, Elasticsearch/OpenSearch, etc.
• PIM: dedicated PIM
• CDP/customer: existing enterprise customer platform
• OMS/ERP: existing systems
• API/event layer: Kafka + API gateway
• Identity: enterprise IAM
• Observability: OpenTelemetry + centralized logging/metrics

The goal should be shared platform capabilities + independently deployable storefront experiences, rather than 30 completely independent stacks.

Bottom line

For a large retailer starting fresh, I'd shortlist commercetools and Shopify Plus, with commercetools as my architectural default.

I'd choose commercetools when the retailer's differentiator is scale, multi-brand/multi-market complexity, sophisticated pricing/catalog/inventory, and long-term architectural flexibility. I'd choose Shopify Plus when the differentiator is getting many storefronts running quickly with substantially less platform engineering.

The distinction is essentially:

commercetools = build a commerce platform around your business

Shopify Plus = build your experiences around an existing commerce platform

That's the tradeoff I'd put in front of the CTO. commercetools Shopify

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—especially if the goal is a genuinely headless/composable architecture rather than simply putting a custom frontend on top of a traditional commerce suite.

My shortlist

Why I'd pick commercetools

For a large retailer, the important question isn't merely "Does it have headless APIs?" Almost all the serious platforms do. The question is how well the platform becomes a shared commerce backend for dozens of experiences without forcing those experiences into the same implementation model.

commercetools is particularly strong here. Its current enterprise offering explicitly targets unified commerce across web, mobile, stores, social and marketplaces, while supporting multiple brands/stores and large catalogs on a cloud-native architecture. Commercetools Commercetools

I'd structure it roughly like:

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Brand C Web
                    ├── Mobile Apps
                    ├── Marketplace
                    ├── In-store / Kiosks
                    └── Other channels
                              │
                       API / Experience Layer
                              │
                 ┌────────────┴────────────┐
                 │                         │
             Commerce                 Experience
          commercetools                   CMS
                 │                         │
       ┌─────────┼─────────┐              │
       │         │         │              │
    Catalog    Cart     Checkout       Personalization
       │         │         │              │
       └─────────┴─────────┴──────────────┘
                       │
              ERP / OMS / PIM / WMS

The key architectural advantage is that storefronts don't have to be the unit of commerce architecture. You can establish shared product, pricing, cart, inventory, promotion, customer and order capabilities while allowing each brand/channel to evolve independently.

When I'd choose Salesforce instead

If your retailer already has a substantial Salesforce footprint—CRM, Marketing Cloud, Service Cloud, Data Cloud, etc.—I'd seriously consider Salesforce Commerce Cloud instead.

Salesforce's current Composable Storefront is explicitly designed around headless commerce, with its PWA Kit, Managed Runtime and Commerce APIs. Its APIs cover shopper functions such as browsing, carts and checkout as well as administrative capabilities such as products, orders, inventory and customers. Developer

It's also attractive for a retailer that wants a hybrid migration. Salesforce supports running traditional storefront functionality alongside headless Composable Storefront components, which can substantially reduce the risk of a big-bang replatform. Developer

So my decision rule would be:

• Greenfield / maximum architectural independence → commercetools
• Already heavily invested in Salesforce → Salesforce Commerce Cloud
• Adobe ecosystem is strategically important → Adobe Commerce
• Operational simplicity and rapid rollout across many relatively independent stores → Shopify Plus
• Want API-first/headless but less composable complexity → BigCommerce

One architectural warning

I wouldn't create one frontend application per storefront unless the brands genuinely need independent technology stacks.

For 20–100 storefronts, I'd want a shared storefront platform with configuration/tenant boundaries:

                    Shared Storefront Platform
                              │
          ┌───────────────────┼───────────────────┐
          │                   │                   │
      storefront A        storefront B        storefront C
       config/theme        config/theme        config/theme
          │                   │                   │
          └───────────────────┼───────────────────┘
                              │
                       Shared APIs/SDKs
                              │
                       Commerce Platform

That gives you centralized engineering, observability, CI/CD, security and performance improvements while preserving brand-level autonomy.

If I had to make the platform decision today, without knowing anything else about your retailer, I'd put commercetools first and Salesforce Commerce Cloud second. The deciding factor would be whether your organization values maximum composability or integration with an existing enterprise Salesforce estate. Commercetools Developer

If you tell me roughly how many storefronts/brands, B2C vs. B2B, countries, SKU count, and your existing ERP/PIM/OMS, I can narrow this down to a concrete target architecture and platform recommendation.

If your retailer already has a substantial Salesforce footprint—CRM, Marketing Cloud, Service Cloud, Data Cloud, etc.—I'd seriously consider Salesforce Commerce Cloud instead.

Salesforce's current Composable Storefront is explicitly designed around headless commerce, with its PWA Kit, Managed Runtime and Commerce APIs. Its APIs cover shopper functions such as browsing, carts and checkout as well as administrative capabilities such as products, orders, inventory and customers.

If heavy API usage + strong developer tooling are your top criteria, I’d shortlist commercetools, Shopify Plus, and BigCommerce—but my recommendation depends on how much architectural control your engineering team wants.

My ranking

1. commercetools — best for engineering-led enterprises

• API-first, headless, cloud-native, and highly modular.
• Gives a strong engineering team substantial control over architecture and integrations.
• Particularly attractive if commerce is one component of a larger distributed system rather than the center of your stack.
• Tradeoff: you take on more of the architecture and integration work yourself. BigCommerce CIOPages
• Shopify Plus — best balance of APIs + operational simplicity

• Excellent developer ecosystem and mature GraphQL tooling.
• Shopify Plus currently provides 1,000 GraphQL Admin API points/second per app/store, versus 100 on standard Shopify. Its Storefront API has no request-rate limit. Shopify
• Shopify is pushing developers toward GraphQL; its REST Admin API is now considered legacy. Shopify
• The big advantage is that your team gets serious API capabilities without having to own as much commerce infrastructure.
• Tradeoff: you're working within Shopify's platform model rather than getting the architectural freedom of a pure composable platform.
• BigCommerce — worth considering for API-heavy headless commerce

• Strong headless/API positioning and particularly good if you want SaaS commerce while retaining more frontend/architecture flexibility.
• I'd put it ahead of Shopify if your requirements lean heavily toward B2B and avoiding platform-specific constraints.

What I'd choose

For a large engineering organization building a highly customized commerce stack: commercetools.

For an enterprise that wants developers to have excellent APIs but doesn't want the engineering organization to become responsible for the entire commerce architecture: Shopify Plus.

That's an important distinction. "Best developer tooling" isn't necessarily the same as "most APIs." A platform can expose enormous API surface area while still making developers fight its underlying abstractions.

For a team doing genuinely heavy API workloads, I'd evaluate these specifically:

One caveat: don't compare API limits simply by requests/second. Shopify's GraphQL limits are based on calculated query cost, so a sophisticated query can consume substantially more capacity than a simple one. Shopify explicitly recommends bulk operations for very large datasets. Shopify

If you tell me roughly (a) API calls/day, (b) number of SKUs/orders, (c) B2B vs B2C, and (d) whether you want headless, I can give you a much more definitive Shopify Plus vs commercetools vs BigCommerce recommendation for your architecture.

For an enterprise team with heavy API usage and strong developer tooling requirements, I would shortlist platforms differently than a typical ecommerce buyer. The key questions are: API maturity, documentation quality, SDKs, webhooks/events, rate limits, extensibility, deployment model, and how much commerce logic your engineers need to own.

My recommendations:

My ranking for a heavy-API engineering environment

1. commercetools — best if your company has a strong platform engineering team and wants commerce as an API layer.
2. Shopify Plus — best balance of developer experience, scale, and reduced operational overhead.
3. Salesforce Commerce Cloud — best if CRM/customer data workflows are central.
4. BigCommerce Enterprise — good pragmatic API-first SaaS choice.
5. Adobe Commerce — choose when customization outweighs operational simplicity.

What I would evaluate in a technical proof-of-concept

For your situation, I would not focus on storefront features first. I would test:

• API throughput and rate-limit behavior under your real workload
• Bulk catalog updates (millions of SKUs if applicable)
• Webhook reliability and retry behavior
• API versioning/deprecation policy
• SDK quality and language support
• GraphQL query performance
• Event-driven integration patterns
• Local developer workflow (CLI, sandbox environments, test data)
• Observability: logs, tracing, API analytics
• Permission models for service accounts

If your team is building multiple front ends (web, mobile, marketplaces, internal apps, partner portals) or integrating deeply with ERP/PIM/OMS systems, I would lean commercetools. If your priority is high API usage but you do not want your engineers owning commerce infrastructure, I would lean Shopify Plus. www.guideflow.comwww.shopify.com

A few details would change the recommendation significantly: your approximate API volume (requests/day), B2B vs B2C, catalog size, number of regions/currencies, and whether you want SaaS-managed infrastructure or full control.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

stripe.com is probably the strongest fit for the billing side. It is purpose-built for subscriptions, recurring invoices, usage-based billing, proration, payment recovery, and global payments. Stripe reports 200M+ active subscriptions managed on Stripe Billing, $1.9T in 2025 payment volume, and 99.999% historical uptime. Stripe Trust Stripe

For the ecommerce layer, I'd shortlist:

• commercetools — best if you have a strong engineering organization and need extremely flexible, API-first, composable architecture. It's particularly attractive when millions of customers generate complex catalog, pricing, entitlement, and regional requirements.
• BigCommerce Enterprise — better if you want more of the commerce platform managed for you. It supports high traffic and headless implementations, while recurring billing is typically handled through integrated payment/subscription providers rather than being its core strength. BigCommerce Shopify
• Shopify Plus — excellent operationally and very scalable, but I'd be less inclined to make it the central subscription system for a business where recurring billing is the dominant workload. Shopify itself points to Shopify Subscriptions and third-party subscription systems for recurring payments. Shopify

What I'd choose for your scenario

The key architectural point is that I wouldn't ask the ecommerce platform to be the subscription ledger. Let the commerce layer handle products, cart, checkout, orders, etc., while a dedicated billing system owns subscription state, invoices, retries, proration, usage, and payment lifecycle.

For millions of customers, that separation also makes it much easier to scale billing independently from storefront traffic and avoid coupling a huge recurring-payment workload to checkout traffic.

If you tell me roughly monthly transactions/subscription renewals, B2C vs. B2B, and whether you need usage-based billing, I can narrow this to 2–3 architectures.

For an enterprise with diverse product types and a strong need for flexible catalog modeling, I’d recommend commercetools.

Why commercetools

• Flexible product model: It separates Product Types, Attributes, Products, Product Variants, and Categories, letting you model fundamentally different product families without forcing everything into one rigid schema. commercetools Documentation commercetools Documentation
• Good for heterogeneous catalogs: Its model is designed for complex assortments including physical/digital products, bundles, and configurable products. Commercetools
• Enterprise multi-market support: Catalog data can be localized and reused across brands, regions, channels, and markets without duplicating the underlying product data. Commercetools
• API-first/composable: This is particularly attractive if your enterprise has multiple storefronts, mobile apps, marketplaces, or other commerce touchpoints.
• Strong separation of product vs. SKU: Products provide the conceptual parent while variants represent the actual sellable SKUs, which is useful when different product categories have very different variation structures. commercetools Documentation

How I'd rank the main options

Adobe Commerce is the strongest alternative I'd consider. It supports custom attributes and attribute sets, plus product types such as simple, configurable, grouped, bundle, virtual, and downloadable products. Experience League Experience League Its attribute-set approach is quite flexible, but for an enterprise whose primary architectural requirement is an extensible product data model, I would give commercetools the edge.

One important caveat: commercetools isn't infinitely schema-free. Each product has one Product Type, and the classic catalog model allows up to 100 variants per Product, so extremely variant-heavy products need careful modeling. commercetools Documentation

Bottom line: If you have, say, electronics + apparel + industrial equipment + subscriptions + digital goods, with different attributes, variants, pricing rules, markets, and channels, I'd start with commercetools. Commercetools Commercetools

commercetools.com

If you tell me your product types, number of SKUs, B2B/B2C mix, and whether you need PIM functionality, I can narrow this down between commercetools, Adobe Commerce, Salesforce, and other enterprise options.

For an enterprise ecommerce stack with complex ERP + PIM integrations, the “best” platform usually depends less on storefront features and more on how well it handles master data ownership, integration patterns, B2B complexity, and ecosystem maturity. The strongest candidates are typically:

CIOPages## My typical shortlist by scenario

If your ERP is SAP

Shortlist:

1. SAP Commerce Cloud
2. Adobe Commerce
3. commercetools

SAP Commerce Cloud is often the natural choice when SAP is the operational backbone because product, pricing, customer, inventory, and order processes can align closely with SAP processes. ERP Research Adobe Commerce is also frequently used in SAP landscapes when companies want more storefront flexibility. Experience League

If your ERP is Oracle, Microsoft Dynamics, Infor, Epicor, etc.

Shortlist:

1. Adobe Commerce
2. commercetools
3. BigCommerce Enterprise

Adobe Commerce tends to be a strong “integration hub” choice because it is designed to connect with ERP, PIM, OMS, CRM, and WMS ecosystems through APIs and connectors. Adobe Business

If your business is B2B distribution/manufacturing

Prioritize:

• Contract pricing
• Customer-specific catalogs
• Account hierarchies
• Quote workflows
• Punchout procurement
• Real-time inventory/ATP
• Complex SKU structures

The winners are usually:

• SAP Commerce Cloud
• Adobe Commerce
• commercetools
• Specialized B2B platforms depending on requirements

Architecture pattern I’d recommend for a complex stack

Avoid making ecommerce the master system. A common enterprise pattern is:

ERP
 ├── Inventory
 ├── Pricing
 ├── Customers/accounts
 └── Orders

PIM
 ├── Product master
 ├── Attributes
 └── Digital assets

Integration layer / iPaaS
 ├── Data transformation
 ├── Event handling
 ├── Error management

Commerce platform
 ├── Experience
 ├── Cart
 ├── Checkout
 ├── Search
 └── Customer experience

For complex environments, an integration layer such as an iPaaS is often as important as the commerce platform itself. Enterprise options commonly include platforms such as Boomi, MuleSoft, Jitterbit, or similar integration middleware. ERP Research ERP Research

Questions that would narrow this down quickly

1. Which ERP(s) are you integrating with? (SAP S/4, Oracle, Dynamics, NetSuite, Infor, Epicor, custom?)
2. Is this primarily B2B, B2C, or B2B2C?
3. Which PIM do you use (Akeneo, Salsify, Informatica, Stibo, Pimcore, custom)?
4. Do you need real-time pricing/inventory, or is batch synchronization acceptable?
5. Are you aiming for a packaged suite or a composable/headless architecture?

With those answers, the shortlist usually drops from ~6 platforms to 2–3 realistic choices.