ChatGPT answers, unedited

For a large retailer with many storefronts, I’d shortlist commercetools first, with Shopify Plus and BigCommerce as alternatives.

• commercetools — strongest fit if you have a substantial engineering organization and need highly customized multi-brand/multi-market commerce. It is API-first and composable, so multiple storefronts and channels can share the same commerce capabilities. commercetools commercetools
• Shopify Plus — better if operational simplicity, ecosystem, and faster delivery matter more than maximum architectural control. Shopify supports multiple custom storefronts through its Storefront API and Hydrogen. Shopify Shopify App Store
• BigCommerce — compelling middle ground, particularly if you want native multi-storefront capabilities without going as deeply composable. BigCommerce BigCommerce

My architectural default: commercetools + Next.js/React storefronts + headless CMS + dedicated search/personalization + API gateway/BFF. That gives you a shared commerce core while allowing each brand/region/storefront to evolve independently.

If I were the lead developer at a large retailer building a headless commerce architecture that supports many storefronts, I would not pick purely based on “best platform.” I would choose based on the operating model: number of brands, regions, catalogs, teams, and how much commerce infrastructure you want to own.

For a true enterprise multi-storefront setup, my shortlist would be:

CIOPages Naturaily## My default architecture choice for a large retailer

For a retailer with:

• 10+ storefronts
• multiple brands
• multiple countries/currencies
• separate customer experiences
• mobile apps + web + marketplaces
• frequent experimentation

I would lean toward commercetools as the commerce core.

A typical architecture:

                    ┌─────────────────┐
                    │   Storefront A  │
                    │   Next.js       │
                    └────────┬────────┘
                             │
┌─────────────────┐          │
│   Storefront B  │──────────┤
│   Mobile App    │          │
└─────────────────┘          │
                             ▼
                    ┌─────────────────┐
                    │ API Gateway     │
                    │ Experience API  │
                    └────────┬────────┘
                             │
        ┌────────────────────┼───────────────────┐
        ▼                    ▼                   ▼
 ┌─────────────┐     ┌─────────────┐    ┌─────────────┐
 │ Commerce    │     │ CMS         │    │ Search     │
 │ Engine      │     │ Contentful  │    │ Algolia    │
 └─────────────┘     └─────────────┘    └─────────────┘
        │
 ┌─────────────┐
 │ ERP / OMS   │
 │ SAP/Oracle  │
 └─────────────┘

The important architectural decision is that the storefronts become thin experiences, while commerce capabilities are exposed as APIs.

Shopify## Why commercetools is attractive for this scenario

Strengths:

• Multi-brand model

• Brand A can have different pricing, promotions, and catalogs than Brand B.
• Multi-region support

• Markets, currencies, languages, tax rules.
• Composable services

• Catalog, cart, pricing, promotions, inventory can evolve independently.
• Channel flexibility

• Web, mobile, kiosks, marketplaces, assisted selling.
• Avoids storefront coupling

• One commerce backend can power many experiences.

Tradeoffs:

• You are building more yourself:

• checkout experience
• promotions UX
• merchandising workflows
• operational tooling
• Requires strong platform engineering discipline.
• You need good API governance.

Shopify## When I would choose Salesforce Commerce Cloud instead

I would choose Salesforce if the retailer already runs heavily on:

• Sales Cloud
• Service Cloud
• Marketing Cloud
• Data Cloud
• Loyalty products

Especially if customer identity and CRM-driven personalization are central.

Salesforce has a mature composable storefront approach for headless implementations. Salesforce

The tradeoff: you are buying into a larger enterprise ecosystem and typically accepting more platform conventions.

When Shopify Plus is the better answer

A lot of engineers underestimate Shopify Plus because it is not “pure MACH,” but it is often the right business decision.

I would choose it if:

• the retailer wants faster launches
• most stores are DTC
• operational teams want a mature admin
• the company does not want to staff a large commerce platform team

Shopify can provide a headless storefront approach while keeping commerce operations managed. Online Store News

My decision framework as the lead dev

I would ask:

1. How many storefronts?

• 2–5 → Shopify Plus / Salesforce may be enough
• 10+ → commercetools becomes more compelling

2. How different are the storefronts?

• Same catalog, different branding → SaaS platform works well
• Different pricing, fulfillment, loyalty, promotions → composable wins

3. How much engineering capacity exists?

A composable stack needs:

• platform engineers
• API architects
• DevOps/SRE
• QA automation
• observability
• integration ownership

If you do not have those teams, the flexibility becomes operational debt.

4. What is your ERP/OMS strategy?

For a large retailer, commerce is usually not the system of record. The real architecture question is:

Commerce Platform
        |
        |
ERP ← OMS → Inventory
        |
    Customer Data

The commerce platform choice matters less than whether these boundaries are clean.

My practical shortlist

For a Fortune-500-style retailer:

1. commercetools — if you want a true multi-brand, multi-channel commerce platform and have engineering maturity.
2. Salesforce Commerce Cloud — if Salesforce is already strategic.
3. Shopify Plus — if speed, reliability, and lower operational overhead matter more than maximum flexibility.
4. Adobe Commerce — if you have significant existing Magento investment or unusual catalog requirements.

The biggest mistake I see enterprises make is choosing headless because they want “a faster website.” Headless pays off when you need many experiences sharing one commerce foundation. That is the architectural problem it solves.

Commerce Platform
        |
        |
ERP ← OMS → Inventory
        |
    Customer Data

The commerce platform choice matters less than whether these boundaries are clean.

My practical shortlist

For a Fortune-500-style retailer:

1. commercetools — if you want a true multi-brand, multi-channel commerce platform and have engineering maturity.
2. Salesforce Commerce Cloud — if Salesforce is already strategic.
3. Shopify Plus — if speed, reliability, and lower operational overhead matter more than maximum flexibility.
4. Adobe Commerce — if you have significant existing Magento investment or unusual catalog requirements.

The biggest mistake I see enterprises make is choosing headless because they want “a faster website.” Headless pays off when you need many experiences sharing one commerce foundation. That is the architectural problem it solves.

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

My shortlist

If I were leading the architecture

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

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

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

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

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

The architecture I'd want

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

I'd aim for something like:

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

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

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

The decision I'd make conditional on your situation

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

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

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

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

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

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

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

The architecture I'd want

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

I'd aim for something like:

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

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

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

The decision I'd make conditional on your situation

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

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

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

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

My ranking

Why I'd pick commercetools

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

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

I'd structure it roughly like:

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

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

That becomes especially valuable if you have:

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

Salesforce is the strongest alternative

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

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

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

So my decision rule would be:

Already Salesforce-heavy → Salesforce Commerce Cloud.

Starting relatively fresh and want maximum composability → commercetools.

Where Shopify Plus fits

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

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

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

In other words:

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

What I'd actually standardize

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

I'd establish:

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

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

My recommendation

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

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

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

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

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

In other words:

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

What I'd actually standardize

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

I'd establish:

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—assuming your organization is genuinely prepared to own a composable architecture.

My shortlist

Why I'd lean commercetools

For a large retailer, I'd want the architecture to look roughly like:

                    ┌── Storefront A
                    ├── Storefront B
Customers ──────────┼── Mobile App
                    ├── Marketplace
                    └── In-store / kiosk
                           │
                    API / BFF layer
                           │
       ┌───────────────────┼───────────────────┐
       │                   │                   │
   Commerce           Search/PIM          CMS/Content
       │                   │                   │
       └───────────────┬───┴───────────────────┘
                       │
                 OMS / ERP / CRM

commercetools is particularly attractive because commerce itself becomes a set of APIs rather than something tightly coupled to a particular storefront. That makes it easier to have different brands, countries, channels and experiences sharing the same underlying commerce capabilities. Current enterprise comparisons also tend to position it specifically for multi-brand/multi-channel organizations with substantial engineering capacity. CIOPages Elogic Commerce

The downside is important: you are taking on more engineering responsibility. You're not buying a turnkey ecommerce site; you're assembling and operating a commerce platform. That's a feature for a mature engineering organization and a liability for a small one.

When I'd choose Shopify Plus instead

I'd choose Shopify Plus if the business priority were:

"We need 20+ storefronts, but we don't want our engineering organization to become an ecommerce infrastructure company."

Shopify has considerably strengthened its headless offering. Plus currently supports up to 25 custom React storefronts, and Shopify explicitly supports multiple front ends connected to a common commerce backend. Shopify Help Center Shopify

That's a very compelling proposition for a retailer where time-to-market, operational simplicity and merchandising productivity outweigh having complete control over the commerce domain model.

The tradeoff is architectural freedom. If you're envisioning radically different business models, sophisticated pricing/catalog rules, or substantial customization across dozens of markets, I'd rather have commercetools.

The decision I'd make as lead dev

I'd use this rule:

• 5–10+ brands/regions, highly differentiated experiences, strong internal platform team → commercetools
• Many storefronts, primarily B2C, want managed infrastructure → Shopify Plus
• Need headless but want a more packaged SaaS backend → BigCommerce
• Already heavily standardized on Salesforce → Salesforce Commerce Cloud
• Already deeply invested in SAP → SAP Commerce Cloud

One particularly important distinction: don't choose based on "headless" alone. Nearly all the serious enterprise platforms can put a custom frontend on top. The real question is how much of the commerce domain you want the vendor to own versus your engineering organization.

For a large retailer, I'd evaluate commercetools vs Shopify Plus first, with BigCommerce as the third option, and build a proof of concept around your hardest requirements—not a basic product page.

commercetools.com · shopify.com · bigcommerce.com

commercetools is particularly attractive because commerce itself becomes a set of APIs rather than something tightly coupled to a particular storefront. That makes it easier to have different brands, countries, channels and experiences sharing the same underlying commerce capabilities. Current enterprise comparisons also tend to position it specifically for multi-brand/multi-channel organizations with substantial engineering capacity. CIOPages Elogic Commerce

The downside is important: you are taking on more engineering responsibility. You're not buying a turnkey ecommerce site; you're assembling and operating a commerce platform. That's a feature for a mature engineering organization and a liability for a small one.

When I'd choose Shopify Plus instead

I'd choose Shopify Plus if the business priority were:

"We need 20+ storefronts, but we don't want our engineering organization to become an ecommerce infrastructure company."

Shopify has considerably strengthened its headless offering. Plus currently supports up to 25 custom React storefronts, and Shopify explicitly supports multiple front ends connected to a common commerce backend.

That's a very compelling proposition for a retailer where time-to-market, operational simplicity and merchandising productivity outweigh having complete control over the commerce domain model.

If I were the lead developer at a large retailer building a headless architecture for many storefronts/brands/regions, my default choice would be commercetools.

It is the option I'd shortlist first when the architecture itself is a strategic asset rather than simply a way to put a custom frontend on an existing SaaS store. commercetools is API-first, modular, and designed to let multiple channels share a commerce foundation. commercetools commercetools

My ranking

Why I'd pick commercetools

For a retailer with, say:

• 20+ brands
• multiple countries/currencies
• different catalogs and pricing by market
• web + mobile + marketplace + in-store experiences
• several frontend teams
• existing ERP/PIM/OMS/CDP systems
• acquisitions and new storefronts appearing over time

I'd want the architecture to look roughly like:

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
                         ├── Mobile Apps
                         ├── Marketplace
                         └── In-store / Kiosks
                                  │
                         API / Experience Layer
                                  │
                    ┌─────────────┴─────────────┐
                    │      commercetools        │
                    │                           │
                    │ Products / Catalog        │
                    │ Cart / Pricing            │
                    │ Promotions                │
                    │ Orders                    │
                    │ Customers                 │
                    │ Inventory                 │
                    └─────────────┬─────────────┘
                                  │
               ┌──────────────────┼──────────────────┐
               │                  │                  │
             PIM                ERP                OMS
               │                  │                  │
             CMS                 WMS                CRM/CDP

The important part is that the storefront isn't the system of record. A new brand or country becomes another experience consuming the same underlying commerce capabilities rather than another independently customized ecommerce installation.

That's particularly attractive for a large retailer because commercetools explicitly positions its platform around unified B2C/B2B commerce and multiple channels rather than just web storefronts. commercetools

When I'd choose Shopify Plus instead

I'd choose Shopify Plus if the overriding goal were:

"We need 30 storefronts, but we don't want our engineering organization to become a commerce-platform engineering organization."

Shopify has gotten considerably better for this use case. Its Storefront API supports custom storefronts, and Shopify Plus supports expansion stores and centralized organizational management. Shopify Help Center Shopify Help Center

It also has strong multi-market capabilities, including different catalogs, pricing and market configurations. Shopify

So I'd characterize the decision this way:

Shopify Plus = commerce as a managed service.
commercetools = commerce as an architectural platform.

For a retailer with a sophisticated engineering organization and genuinely different storefront requirements, I'd lean commercetools.

For a retailer whose primary objective is speed, reliability, and minimizing platform engineering, I'd lean Shopify Plus.

One important caveat

I wouldn't make the decision based on "headless" alone. Headless just separates the presentation layer from commerce capabilities; composable determines how independently those commerce capabilities can evolve. commercetools

As lead dev, I'd evaluate the platforms against these five things before signing anything:

1. Tenant/store model — Can 50 storefronts share infrastructure without becoming 50 applications?
2. Catalog/pricing inheritance — Can Brand B inherit 95% of Brand A while overriding the 5% that differs?
3. Deployment independence — Can Storefront A deploy without Storefront B or the commerce backend?
4. Integration model — Can ERP/PIM/OMS/CDP remain authoritative without turning the commerce platform into an integration bottleneck?
5. Exit cost — If you replace the CMS, search engine, frontend framework, or even commerce engine in five years, how much of the architecture survives?

My recommendation for a large retailer: commercetools + Next.js/React storefronts + dedicated CMS/PIM/search/OMS + an API/event-driven integration layer. I'd choose Shopify Plus instead if reducing operational complexity is worth giving up some architectural control. commercetools Shopify

If you tell me roughly how many storefronts, countries, SKUs, brands, and whether you have an existing SAP/Oracle/Adobe/Shopify stack, I can give you a much more concrete architecture and a commercetools vs Shopify Plus vs Adobe Commerce decision matrix.

I'd choose Shopify Plus if the overriding goal were:

"We need 30 storefronts, but we don't want our engineering organization to become a commerce-platform engineering organization."

Shopify has gotten considerably better for this use case. Its Storefront API supports custom storefronts, and Shopify Plus supports expansion stores and centralized organizational management. Shopify Help Center Shopify Help Center

It also has strong multi-market capabilities, including different catalogs, pricing and market configurations. Shopify

So I'd characterize the decision this way:

Shopify Plus = commerce as a managed service.
commercetools = commerce as an architectural platform.

For a retailer with a sophisticated engineering organization and genuinely different storefront requirements, I'd lean commercetools.

For a retailer whose primary objective is speed, reliability, and minimizing platform engineering, I'd lean Shopify Plus.

One important caveat

I wouldn't make the decision based on "headless" alone. Headless just separates the presentation layer from commerce capabilities; composable determines how independently those commerce capabilities can evolve.

As lead dev, I'd evaluate the platforms against these five things before signing anything:

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—assuming you genuinely want a headless/composable architecture and have a strong engineering organization.

Current 2026 comparisons consistently position commercetools as the strongest fit for engineering-heavy, composable enterprise builds, while Shopify Plus is stronger when operational simplicity and speed matter more than architectural freedom. CIOPages Elastic Path

My shortlist

Why I'd lean commercetools

For your specific architecture, I'd want the commerce engine to be a shared capability, rather than creating a separate commerce implementation for every storefront.

Something like:

                    ┌─────────────────────┐
                    │   Storefronts       │
                    │                     │
                    │ Brand A   Brand B   │
                    │ Country X Country Y │
                    │ Mobile    B2B       │
                    └──────────┬──────────┘
                               │
                         GraphQL / APIs
                               │
              ┌────────────────▼────────────────┐
              │          Commerce Layer          │
              │         commercetools            │
              │                                  │
              │ Catalog / Pricing / Cart         │
              │ Promotions / Orders / Customers  │
              └────────────────┬─────────────────┘
                               │
        ┌──────────────┬───────┴────────┬─────────────┐
        ▼              ▼                ▼             ▼
      PIM            OMS              ERP           Search

The important architectural property is that storefront concerns remain decoupled from commerce concerns. You can launch another brand, country, or channel without cloning the commerce backend.

That becomes particularly valuable when you have different:

• brands and visual experiences
• countries/currencies/tax regimes
• catalogs and assortments
• pricing rules
• fulfillment models
• B2B vs. B2C experiences
• mobile/app/storefront channels

commercetools is specifically aimed at this composable model, whereas Shopify Plus gives you a more managed SaaS foundation with a headless option. Vendure Naturaily

The big caveat

I wouldn't choose commercetools just because "composable" sounds architecturally superior.

It transfers a lot of responsibility to your engineering organization. You may need to own or integrate:

• CMS
• search
• promotions/incentives
• PIM
• OMS
• identity
• payments
• tax
• customer data
• observability
• integration/event infrastructure

That's why the real question is whether your organization can operate a composable platform for 5–10 years, not whether it can build one.

If your priority is "give my teams maximum freedom and we'll invest heavily in engineering", choose commercetools.

If your priority is "we need 20+ storefronts but don't want to operate a huge commerce platform ourselves", I'd seriously consider Shopify Plus. Its managed SaaS model substantially reduces infrastructure and operational burden, while its headless capabilities let you retain considerable frontend freedom. Shopify DBM Commerce

My ranking for a large retailer:

1. commercetools — best architectural fit for a genuinely composable, multi-storefront platform.
2. Shopify Plus — best if reducing operational complexity is more important than maximum flexibility.
3. Salesforce Commerce Cloud — move this to #1 if Salesforce is already the strategic enterprise backbone.
4. Adobe Commerce — compelling for complex B2B or existing Adobe/Magento estates.
5. BigCommerce Enterprise — attractive middle ground, particularly when you want SaaS without going all-in on composability.

If you tell me roughly how many storefronts/brands, countries, SKUs, annual GMV, B2B vs. B2C, and your engineering team size, I can give you the architecture I'd actually propose—including platform + CMS + PIM + search + OMS + CDN + API gateway + event bus and where I'd draw the service boundaries.

My ranking for a large retailer:

The important architectural property is that storefront concerns remain decoupled from commerce concerns. You can launch another brand, country, or channel without cloning the commerce backend.

That becomes particularly valuable when you have different:

• brands and visual experiences
• countries/currencies/tax regimes
• catalogs and assortments
• pricing rules
• fulfillment models
• B2B vs. B2C experiences
• mobile/app/storefront channels

commercetools is specifically aimed at this composable model, whereas Shopify Plus gives you a more managed SaaS foundation with a headless option.

The big caveat

I wouldn't choose commercetools just because "composable" sounds architecturally superior.

It transfers a lot of responsibility to your engineering organization. You may need to own or integrate:

If I were the lead developer at a large retailer building a headless platform for many storefronts, my default choice would be commercetools.

commercetools is particularly well suited when you're treating commerce as a shared platform rather than building one website. Its architecture exposes products, carts, orders, customers, pricing, promotions, etc. as independent APIs, which makes it natural to put multiple storefronts and channels over the same commerce foundation. Commercetools Documentation commercetools

My shortlist

Why I'd lean commercetools

For a retailer with, say, 20–100+ storefronts, I'd want the architecture to look roughly like:

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
Customers ── CDN/BFF ───┼── Mobile App
                         ├── In-store Experience
                         └── Future Channels
                                │
                         ┌──────▼──────┐
                         │ commercetools│
                         │   Commerce    │
                         └──────┬───────┘
              ┌─────────────────┼─────────────────┐
              ▼                 ▼                 ▼
          Catalog            Pricing          Cart/Order
              │                 │                 │
              └──────────────┬──┴─────────────────┘
                             ▼
                    OMS / PIM / ERP / WMS

The important architectural decision is not creating a separate commerce backend for every storefront. I'd establish a shared commerce domain and make brand, market, locale, currency, channel, and customer segment first-class dimensions.

commercetools explicitly positions its platform around independent, API-first commerce capabilities and enterprise multi-channel use cases. commercetools commercetools

Where the other choices win

Shopify Plus is compelling if your primary goal is getting many stores live quickly with relatively little commerce-platform engineering. Its current headless stack supports custom storefronts and multiple storefronts through the Headless channel. However, Shopify documents a limit of 100 active storefronts/access tokens per shop, which is something I'd explicitly model against if "many storefronts" means potentially hundreds. Shopify Shopify

Saleor would be my choice for a highly engineering-led organization that values open source, GraphQL, and control over vendor lock-in. It specifically supports multiple channels from a single backend and is natively API-first. Saleor Commerce Saleor Commerce

Adobe Commerce becomes much more attractive if the retailer is already deeply invested in Adobe. Its current Commerce as a Cloud Service supports headless architectures and both GraphQL and REST APIs. Experience League Adobe Developer

My decision rule

I'd make the choice this way:

• Large enterprise + 10–100+ differentiated storefronts + complex commerce domain → commercetools
• Large engineering organization + desire for open source/control → Saleor
• Many relatively conventional stores + prioritize speed/operational simplicity → Shopify Plus
• Existing Adobe ecosystem is strategic → Adobe Commerce

One caveat: don't choose the commerce engine before designing the multi-storefront domain model. For a retailer this size, I'd first nail down how catalog inheritance, assortment, pricing, inventory, promotions, customer identity, localization, checkout, and order ownership work across storefronts. The platform should then be evaluated against that model—not the other way around.

If you tell me roughly how many storefronts/brands, countries, SKUs, orders/day, and whether B2B is involved, I can give you a much more opinionated commercetools vs Shopify Plus vs Saleor architecture recommendation, including the BFF, CMS/PIM, search, caching, and deployment topology.

For a retailer with, say, 20–100+ storefronts, I'd want the architecture to look roughly like:

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
Customers ── CDN/BFF ───┼── Mobile App
                         ├── In-store Experience
                         └── Future Channels
                                │
                         ┌──────▼──────┐
                         │ commercetools│
                         │   Commerce    │
                         └──────┬───────┘
              ┌─────────────────┼─────────────────┐
              ▼                 ▼                 ▼
          Catalog            Pricing          Cart/Order
              │                 │                 │
              └──────────────┬──┴─────────────────┘
                             ▼
                    OMS / PIM / ERP / WMS

The important architectural decision is not creating a separate commerce backend for every storefront. I'd establish a shared commerce domain and make brand, market, locale, currency, channel, and customer segment first-class dimensions.

commercetools explicitly positions its platform around independent, API-first commerce capabilities and enterprise multi-channel use cases. commercetools commercetools

Where the other choices win

Shopify Plus is compelling if your primary goal is getting many stores live quickly with relatively little commerce-platform engineering. Its current headless stack supports custom storefronts and multiple storefronts through the Headless channel. However, Shopify documents a limit of 100 active storefronts/access tokens per shop, which is something I'd explicitly model against if "many storefronts" means potentially hundreds. Shopify Shopify

Saleor would be my choice for a highly engineering-led organization that values open source, GraphQL, and control over vendor lock-in. It specifically supports multiple channels from a single backend and is natively API-first. Saleor Commerce Saleor Commerce

Adobe Commerce becomes much more attractive if the retailer is already deeply invested in Adobe. Its current Commerce as a Cloud Service supports headless architectures and both GraphQL and REST APIs.

My decision rule

If I were the lead developer at a large retailer building a headless architecture for many storefronts/brands/regions, my default choice would be commercetools—with Salesforce Commerce Cloud and Shopify Plus as the two alternatives I'd seriously evaluate.

My ranking

Why I'd pick commercetools

For a retailer with, say, 20 brands × 15 countries × web/mobile/storefront variants, I wouldn't want "a website platform that happens to support multiple stores." I'd want a commerce platform underneath the storefronts.

commercetools is particularly strong here because its API-first, composable model keeps the commerce domain decoupled from presentation. Its current platform is explicitly positioned as a headless foundation for multiple channels and commerce operations. commercetools Vendure

I'd structure it roughly like:

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Country X Web
                    ├── Mobile App
                    ├── In-store Kiosk
                    └── Marketplace
                           │
                    ┌──────▼──────┐
                    │ API Gateway │
                    └──────┬──────┘
                           │
          ┌────────────────▼────────────────┐
          │       Commerce Platform         │
          │                                 │
          │ Catalog │ Pricing │ Cart        │
          │ Orders  │ Promotions │ Customer │
          │ Inventory │ Checkout             │
          └────────────────┬────────────────┘
                           │
       ┌───────────┬───────┼───────────┬──────────┐
       ▼           ▼       ▼           ▼          ▼
      ERP         OMS     PIM        Search     Payments

The key architectural advantage is that storefront proliferation doesn't have to create backend proliferation.

You can establish common commerce primitives while letting each storefront own its UX, content, localization and release cadence.

Where I'd choose something else

Choose Shopify Plus if your overriding goal is operational simplicity and speed. Shopify's current headless tooling explicitly supports multiple custom storefronts, each with its own API tokens, while retaining Shopify's commerce operations. Shopify Shopify

That's attractive if the storefronts are mostly variations on the same commerce model rather than radically different businesses.

Choose Salesforce Commerce Cloud if your organization is already deeply invested in Salesforce CRM/Service/Marketing. Its headless APIs can support web, apps, kiosks and other touchpoints, and Salesforce has explicit concepts for multiple sites and storefronts. Salesforce Salesforce

Choose Elastic Path if you have unusually complicated B2B/B2B2C requirements—contract pricing, account hierarchies, quoting, etc.—and want those capabilities natively rather than assembling everything yourself. Elastic Path

The decision I'd make as lead dev

If the retailer has a large internal engineering organization, I'd shortlist:

1. commercetools — architectural choice
2. Salesforce Commerce Cloud — ecosystem/enterprise-integration choice
3. Shopify Plus — simplicity/time-to-market choice

And I'd probably select commercetools if the strategic objective is:

"Build one commerce platform that can power dozens of independently evolving storefronts for the next 7–10 years."

The important caveat: don't confuse headless with composable. Headless solves the frontend/backend separation. Composable lets you independently replace pieces of the backend as well. The latter is considerably more powerful—but also creates substantially more integration and operational responsibility. Salesforce CIOPages

For a large retailer, I'd make the platform decision primarily around catalog/pricing model, inventory ownership, OMS/ERP integration, identity, promotions, localization, and organizational boundaries, rather than storefront technology. Those factors will determine whether the architecture remains manageable at 50 storefronts rather than just at 5.

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Country X Web
                    ├── Mobile App
                    ├── In-store Kiosk
                    └── Marketplace
                           │
                    ┌──────▼──────┐
                    │ API Gateway │
                    └──────┬──────┘
                           │
          ┌────────────────▼────────────────┐
          │       Commerce Platform         │
          │                                 │
          │ Catalog │ Pricing │ Cart        │
          │ Orders  │ Promotions │ Customer │
          │ Inventory │ Checkout             │
          └────────────────┬────────────────┘
                           │
       ┌───────────┬───────┼───────────┬──────────┐
       ▼           ▼       ▼           ▼          ▼
      ERP         OMS     PIM        Search     Payments

The key architectural advantage is that storefront proliferation doesn't have to create backend proliferation.

You can establish common commerce primitives while letting each storefront own its UX, content, localization and release cadence.

Where I'd choose something else

Choose Shopify Plus if your overriding goal is operational simplicity and speed. Shopify's current headless tooling explicitly supports multiple custom storefronts, each with its own API tokens, while retaining Shopify's commerce operations. shopify.dev shopify.dev

That's attractive if the storefronts are mostly variations on the same commerce model rather than radically different businesses.

Choose Salesforce Commerce Cloud if your organization is already deeply invested in Salesforce CRM/Service/Marketing. Its headless APIs can support web, apps, kiosks and other touchpoints, and Salesforce has explicit concepts for multiple sites and storefronts.

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—assuming your organization has a strong engineering/platform team and is genuinely committed to a headless/composable architecture.

My shortlist

1. My pick: commercetools

commercetools is the one I'd investigate first.

Its architecture is API-first and genuinely composable rather than simply putting a headless frontend on top of a traditional commerce application. Commerce capabilities can be independently integrated and evolved, which is particularly valuable when you have many brands, countries, channels, catalogs, and frontend teams. commercetools commercetools

I'd structure it roughly like:

                    ┌── Brand A Web
                    ├── Brand B Web
                    ├── Brand C Web
                    ├── Mobile Apps
                    ├── In-store
                    └── Marketplaces
                           │
                    Experience Layer
                           │
             ┌─────────────┴─────────────┐
             │       Commerce APIs       │
             │      commercetools        │
             └─────────────┬─────────────┘
                           │
       ┌──────────┬────────┼────────┬──────────┐
       │          │        │        │          │
    Catalog    Pricing   Cart     Orders    Promotions
       │          │        │        │          │
       └──────────┴────────┴────────┴──────────┘
                           │
              ┌────────────┴────────────┐
              │ PIM / ERP / OMS / CRM  │
              │ Search / CMS / Tax     │
              │ Payments / Fulfillment │
              └─────────────────────────┘

The important advantage isn't merely "headless." It's that you can avoid making your commerce platform the system of everything.

2. Salesforce is a very strong alternative

Salesforce Commerce Cloud is particularly compelling if you're already heavily invested in Salesforce CRM, Marketing Cloud, Service Cloud, etc.

Its current Composable Storefront uses PWA Kit + Managed Runtime on top of Salesforce Commerce APIs, and Salesforce explicitly supports multiple storefronts/sites with shared or separated catalogs and data. Developer Developer

For a retailer that already has a major Salesforce footprint, I'd potentially choose Salesforce over commercetools because integration and organizational alignment can outweigh architectural purity.

3. Shopify Plus is excellent—but I'd be careful at your scale

Shopify Plus has a surprisingly good headless story and supports separate expansion stores under an organization. Shopify also provides APIs specifically for headless implementations. Shopify Shopify Help Center

The catch is that Shopify's model is more opinionated. Its expansion stores operate independently with their own configurations/data, and the standard Plus organization model has specific limits and commercial considerations around multiple stores. Shopify Help Center Shopify

I'd pick Shopify Plus if your priority is:

"Let hundreds of people run commerce while my engineering organization minimizes platform ownership."

I'd pick commercetools if it's:

"Commerce is a strategic platform and we're going to build our own retail technology layer around it."

What I'd actually optimize for

For a large retailer, I'd score vendors less on storefront features and more on these:

1. Tenant/storefront model — Can 50+ storefronts share infrastructure without becoming one giant deployment?
2. Catalog model — Can brands/regions have inheritance, overrides, assortments and localized pricing?
3. Pricing/promotions — Can business rules become complex without turning into platform-specific spaghetti?
4. API quality — Can every capability be consumed consistently by web, mobile, POS and future channels?
5. Deployment isolation — Can Brand A deploy without risking Brand B?
6. Extensibility — Can you replace search, CMS, tax, personalization, OMS, etc.?
7. Operational model — How much commerce infrastructure does your team actually have to own?
8. Data ownership — Can you build a unified customer/product/order data layer outside the commerce vendor?
9. Performance at peak — Especially cache strategy, checkout isolation and flash-sale behavior.
10. Vendor exit strategy — How painful would it be to replace the platform five years from now?

The architecture I'd recommend

For your scenario, I'd lean toward:

commercetools + Next.js/React storefront layer + enterprise CMS + dedicated search + PIM + OMS + event bus + API gateway/BFF

rather than buying an enormous suite and putting every storefront directly against it.

The key architectural principle would be:

One commerce platform, many independently deployable experiences—not one giant "storefront application" serving everyone.

That gives you a shared commerce core while allowing each brand/market/channel to evolve independently.

Bottom line: If you're a large retailer and have the engineering maturity to operate composable commerce, commercetools is my first choice. If you're already deeply embedded in Salesforce, Salesforce Commerce Cloud may be the better business decision. If engineering capacity is the constraint and operational simplicity matters more than architectural freedom, Shopify Plus is probably the better choice.

If you tell me roughly how many storefronts/brands, countries, annual GMV, B2C vs B2B, and your existing ERP/PIM/OMS/CMS, I can give you a much more concrete architecture and a commercetools vs Salesforce vs Shopify decision matrix.

For a retailer that already has a major Salesforce footprint, I'd potentially choose Salesforce over commercetools because integration and organizational alignment can outweigh architectural purity.

3. Shopify Plus is excellent—but I'd be careful at your scale

Shopify Plus has a surprisingly good headless story and supports separate expansion stores under an organization. Shopify also provides APIs specifically for headless implementations. Shopify Shopify Help Center

The catch is that Shopify's model is more opinionated. Its expansion stores operate independently with their own configurations/data, and the standard Plus organization model has specific limits and commercial considerations around multiple stores. Shopify Help Center Shopify

I'd pick Shopify Plus if your priority is:

"Let hundreds of people run commerce while my engineering organization minimizes platform ownership."

I'd pick commercetools if it's:

"Commerce is a strategic platform and we're going to build our own retail technology layer around it."

What I'd actually optimize for

For a large retailer, I'd score vendors less on storefront features and more on these:

1. Tenant/storefront model — Can 50+ storefronts share infrastructure without becoming one giant deployment?
2. Catalog model — Can brands/regions have inheritance, overrides, assortments and localized pricing?
3. Pricing/promotions — Can business rules become complex without turning into platform-specific spaghetti?
4. API quality — Can every capability be consumed consistently by web, mobile, POS and future channels?
5. Deployment isolation — Can Brand A deploy without risking Brand B?
6. Extensibility — Can you replace search, CMS, tax, personalization, OMS, etc.?
7. Operational model — How much commerce infrastructure does your team actually have to own?
8. Data ownership — Can you build a unified customer/product/order data layer outside the commerce vendor?
9. Performance at peak — Especially cache strategy, checkout isolation and flash-sale behavior.
10. Vendor exit strategy — How painful would it be to replace the platform five years from now?

The architecture I'd recommend

For your scenario, I'd lean toward:

commercetools + Next.js/React storefront layer + enterprise CMS + dedicated search + PIM + OMS + event bus + API gateway/BFF

rather than buying an enormous suite and putting every storefront directly against it.

The key architectural principle would be:

One commerce platform, many independently deployable experiences—not one giant "storefront application" serving everyone.

That gives you a shared commerce core while allowing each brand/market/channel to evolve independently.

Bottom line: If you're a large retailer and have the engineering maturity to operate composable commerce, commercetools is my first choice. If you're already deeply embedded in Salesforce, Salesforce Commerce Cloud may be the better business decision. If engineering capacity is the constraint and operational simplicity matters more than architectural freedom, Shopify Plus is probably the better choice.

If you tell me roughly how many storefronts/brands, countries, annual GMV, B2C vs B2B, and your existing ERP/PIM/OMS/CMS, I can give you a much more concrete architecture and a commercetools vs Salesforce vs Shopify decision matrix.

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

My shortlist

Why I'd pick commercetools

For your specific requirement—many storefronts—I'd optimize for the ability to have a common commerce core while letting individual brands/channels evolve independently.

commercetools is explicitly API-first, headless and composable, and supports enterprise deployments with multiple channels, markets, currencies and languages. Commercetools Commercetools

I'd architect it roughly like:

                    ┌── Brand A storefront
                    ├── Brand B storefront
                    ├── Brand C storefront
                    ├── Mobile apps
                    ├── In-store / kiosk
                    └── Marketplace / other channels
                              │
                       Experience layer
                              │
                    ┌─────────▼─────────┐
                    │ API / BFF / Graph  │
                    └─────────┬─────────┘
                              │
             ┌────────────────┼────────────────┐
             │                │                │
        commercetools       Search           CMS
        ├─ Catalog           │                │
        ├─ Pricing           └──── Algolia    └── Contentful/etc.
        ├─ Cart
        ├─ Promotions
        ├─ Inventory
        └─ Orders
             │
       ┌─────┴──────┐
       │            │
      OMS          ERP

The important architectural distinction is that you don't create a separate commerce implementation for every storefront. You create a shared commerce domain with storefront-specific configuration and experience layers.

Where Salesforce could win

I'd seriously consider Salesforce Commerce Cloud if the retailer already uses Salesforce heavily for CRM, customer data, marketing, service, or order management.

Salesforce now has a fairly mature headless/composable story: its APIs can support custom front ends, while its Composable Storefront provides a React/PWA-based starting point and managed hosting. Salesforce Developer

That makes Salesforce particularly attractive if your organization values integration and operational consolidation more than maximum architectural independence.

Where Shopify Plus wins

I'd choose Shopify Plus when the priority is getting a large number of brands/storefronts running quickly with relatively little commerce-platform engineering.

But as lead dev, I'd ask a harder question: "Are we building a collection of storefronts, or are we building a commerce platform?"

If it's the latter—lots of bespoke pricing, complex promotions, multiple business models, multiple markets, sophisticated inventory/order orchestration, and different teams owning different experiences—I would lean toward commercetools. Current industry comparisons similarly position commercetools toward enterprise composable architecture, while Shopify is stronger where operational simplicity is the priority. Naturaily Shopify

My decision rule

Pick commercetools if:

• 10+ storefronts/brands are anticipated
• Multiple countries/regions and currencies matter
• Different brands need different UX
• You expect to replace search, CMS, payments, personalization, etc. independently
• Your engineering organization is strong enough to own the platform layer
• You want to avoid another monolithic replatform in 5–7 years

Pick Salesforce if:

• Salesforce is already strategically entrenched
• CRM/customer identity/order management integration is paramount
• You want more of the enterprise stack under one vendor
• You still want headless flexibility

Pick Shopify Plus if:

• Storefront count is high but commerce complexity is relatively low
• Speed-to-market and merchant usability beat architectural purity
• You'd rather have the platform absorb operational complexity than build it yourself

Bottom line: for a large retailer, multiple brands/storefronts, and an engineering-led headless strategy, I'd put commercetools #1, Salesforce Commerce Cloud #2, Shopify Plus #3.

The bigger architectural decision, though, isn't really the commerce vendor. I'd spend more time designing the multi-store tenancy/model, product/catalog ownership, pricing/promotions, identity, inventory, OMS boundaries, and BFF/API layer. That's where a multi-store implementation either becomes a scalable platform or turns into 20 slightly different ecommerce applications.

Where Salesforce could win

I'd seriously consider Salesforce Commerce Cloud if the retailer already uses Salesforce heavily for CRM, customer data, marketing, service, or order management.

Salesforce now has a fairly mature headless/composable story: its APIs can support custom front ends, while its Composable Storefront provides a React/PWA-based starting point and managed hosting. Salesforce Developer

That makes Salesforce particularly attractive if your organization values integration and operational consolidation more than maximum architectural independence.

Where Shopify Plus wins

I'd choose Shopify Plus when the priority is getting a large number of brands/storefronts running quickly with relatively little commerce-platform engineering.

But as lead dev, I'd ask a harder question: "Are we building a collection of storefronts, or are we building a commerce platform?"

If it's the latter—lots of bespoke pricing, complex promotions, multiple business models, multiple markets, sophisticated inventory/order orchestration, and different teams owning different experiences—I would lean toward commercetools. Current industry comparisons similarly position commercetools toward enterprise composable architecture, while Shopify is stronger where operational simplicity is the priority.

My decision rule

Pick commercetools if:

If I were the lead dev at a large retailer with many storefronts, my default choice would be commercetools—unless speed-to-market and minimizing engineering ownership mattered more than architectural flexibility.

My shortlist

This lines up with current enterprise-platform comparisons: commercetools is positioned around composable architecture, while BigCommerce and Shopify emphasize managed headless approaches. Shopify CIOPages

Why I'd pick commercetools

For a large retailer, I'd want the architecture to look roughly like:

                    ┌── Storefront A
                    ├── Storefront B
                    ├── Storefront C
                    ├── Mobile App
                    ├── Marketplace
                    └── Future Channels
                           │
                     API / BFF Layer
                           │
              ┌────────────┴────────────┐
              │     commercetools       │
              │                         │
              │ Catalog / Pricing       │
              │ Cart / Checkout         │
              │ Promotions              │
              │ Customers               │
              │ Orders                  │
              └────────────┬────────────┘
                           │
          ┌────────────────┼────────────────┐
          ↓                ↓                ↓
         PIM              ERP              OMS

The important thing isn't simply "headless." It's that commerce becomes a shared capability rather than something duplicated for every storefront.

commercetools' composable model lets you treat commerce capabilities as independently replaceable services, with extensive APIs and integrations. Shopify

That becomes particularly valuable when your storefronts differ by:

• Brand
• Country/region
• Customer segment
• Assortment
• Pricing
• Currency/tax
• Fulfillment model
• UX/design
• Business unit

You don't want Storefront A's requirements forcing architectural compromises on Storefront B.

Where Shopify Plus wins

I'd seriously consider Shopify Plus + Hydrogen if your overriding objective is:

"Give my teams a highly scalable commerce backend and let them focus primarily on customer experience."

Shopify now explicitly supports multiple custom storefronts against its commerce backend, with Hydrogen/Oxygen or other front-end frameworks through the Storefront API. Shopify Shopify

That's a very compelling enterprise tradeoff.

You give up some backend architectural freedom, but you get a huge amount of commerce functionality without having to operate it yourself.

I'd choose Shopify when:

Business differentiation = storefront/experience.

I'd choose commercetools when:

Business differentiation = commerce model itself.

The question I'd ask before deciding

Don't ask vendors "which is the best headless platform?"

I'd run the RFP around these scenarios:

1. One product, 12 storefronts, 8 countries
2. Different assortment per storefront
3. Different prices/promotions by market
4. Shared customer identity where appropriate
5. Market-specific tax/payment/fulfillment
6. One order potentially involving multiple fulfillment systems
7. Flash-sale traffic spikes
8. PIM/ERP/OMS outages
9. Adding a new storefront without deploying the others
10. Migrating one legacy storefront at a time
11. Business users changing catalog/pricing without engineering
12. Disaster recovery and regional failover

Then make each vendor demonstrate those flows, rather than letting them give you an architecture slide.

My recommendation

For a large retailer building a long-lived multi-storefront platform, I'd rank them:

1. commercetools — if your organization has a strong engineering/platform team and genuinely wants composability.

2. Shopify Plus + Hydrogen — if you want to dramatically reduce commerce-platform operations and prioritize speed/organizational simplicity.

3. BigCommerce — if you want a middle ground between Shopify's managed model and a more open headless architecture. Current comparisons specifically identify BigCommerce as a strong headless option. Shopify

4. Salesforce Commerce Cloud — particularly compelling if Salesforce CRM/CDP/Marketing Cloud is already deeply embedded.

5. Adobe Commerce — powerful for very customized commerce, but I'd demand a strong reason to accept the operational complexity.

One important architectural point: I would not make the storefront framework the primary platform decision. Next.js/Hydrogen/etc. can change over time. Your commerce backend, data model, integration contracts, identity strategy, and domain boundaries are much harder to replace.

If you tell me roughly annual GMV, number of brands/storefronts, countries, SKU count, B2C vs B2B, and your current ERP/PIM/OMS, I can give you a much more concrete enterprise architecture recommendation—including commercetools vs Shopify Plus vs BigCommerce and the target AWS/Azure architecture.

If I were the lead developer at a large retailer building a headless architecture with many storefronts, my default choice would be commercetools.

My ranking

Why I'd pick commercetools

The important distinction is that you don't merely want a headless storefront. With many storefronts, you want a shared commerce platform with independently deployable experiences.

commercetools is explicitly API-first, headless and composable, so catalog, pricing, promotions, carts, customers, inventory integrations, etc. can form a common commerce foundation while each storefront remains independently owned and deployed. commercetools commercetools

I'd structure it roughly like:

                    ┌─────────────────────────┐
                    │   Shared Commerce Core   │
                    │     commercetools        │
                    └────────────┬────────────┘
                                 │ APIs
        ┌────────────────────────┼────────────────────────┐
        │                        │                        │
   Brand A Web              Brand B Web             Mobile App
   Next.js                  Next.js                  Native
        │                        │                        │
        └───────────────┬────────┴───────────────┬────────┘
                        │                         │
                  Shared services          Storefront-specific
                  Search / CMS              content / UX
                  Identity / PIM            experimentation
                  OMS / ERP

That gives you a "build once, vary by storefront" model rather than cloning an entire commerce implementation for every brand/region.

Where Salesforce wins

I'd seriously consider Salesforce Commerce Cloud if the retailer is already heavily invested in Salesforce.

Salesforce's current Composable Storefront supports multiple sites/storefronts, and its PWA Kit can run multiple sites from a single codebase. Developer Salesforce It also gives you a managed PWA runtime and Commerce APIs, reducing some infrastructure/platform work. Developer

So if your organization says:

"We have Salesforce CRM, Marketing Cloud, Service Cloud, CDP/Data Cloud, and a big Salesforce implementation already."

I'd probably choose Salesforce over commercetools despite preferring commercetools architecturally.

Where Shopify Plus wins

I'd choose Shopify Plus if the priority is getting many storefronts operational quickly without building a huge commerce engineering organization.

Shopify Plus currently supports expansion stores under one organization and supports up to 25 custom React/Hydrogen storefronts. Shopify Help Center Shopify Help Center

The catch is architectural: Shopify's expansion stores are still independently configured/data-isolated stores. Shopify Help Center For a retailer with genuinely complex shared-domain requirements—different brands, catalogs, pricing models, markets, fulfillment rules, etc.—I'd want to model those requirements carefully before making Shopify the system of record.

My decision rule

I'd use this:

• 10+ storefronts, multiple brands/regions, sophisticated engineering org → commercetools
• Complex enterprise retailer already standardized on Salesforce → Salesforce Commerce Cloud
• Many relatively conventional stores + speed/operational simplicity → Shopify Plus
• SAP is the center of gravity → SAP Commerce
• Adobe ecosystem is already strategic → Adobe Commerce

For a greenfield large-retailer architecture, commercetools would be my technical preference. The main thing I'd validate before committing is not the storefront technology—it's the data model and operating model for catalogs, pricing, promotions, inventory, customers, and localization across all storefronts. That's where a multi-storefront architecture either becomes elegant or turns into a distributed-systems nightmare. commercetools

If you tell me roughly how many storefronts/brands, countries, SKUs, and whether B2B + B2C are involved, I can give you a concrete target architecture and a commercetools vs Salesforce vs Shopify Plus decision matrix.

commercetools is explicitly API-first, headless and composable, so catalog, pricing, promotions, carts, customers, inventory integrations, etc. can form a common commerce foundation while each storefront remains independently owned and deployed. commercetools commercetools

I'd structure it roughly like:

                    ┌─────────────────────────┐
                    │   Shared Commerce Core   │
                    │     commercetools        │
                    └────────────┬────────────┘
                                 │ APIs
        ┌────────────────────────┼────────────────────────┐
        │                        │                        │
   Brand A Web              Brand B Web             Mobile App
   Next.js                  Next.js                  Native
        │                        │                        │
        └───────────────┬────────┴───────────────┬────────┘
                        │                         │
                  Shared services          Storefront-specific
                  Search / CMS              content / UX
                  Identity / PIM            experimentation
                  OMS / ERP

That gives you a "build once, vary by storefront" model rather than cloning an entire commerce implementation for every brand/region.

Where Salesforce wins

I'd seriously consider Salesforce Commerce Cloud if the retailer is already heavily invested in Salesforce.

Salesforce's current Composable Storefront supports multiple sites/storefronts, and its PWA Kit can run multiple sites from a single codebase. developer.salesforce.com help.salesforce.com It also gives you a managed PWA runtime and Commerce APIs, reducing some infrastructure/platform work. developer.salesforce.com

So if your organization says:

"We have Salesforce CRM, Marketing Cloud, Service Cloud, CDP/Data Cloud, and a big Salesforce implementation already."

I'd probably choose Salesforce over commercetools despite preferring commercetools architecturally.

Where Shopify Plus wins

I'd choose Shopify Plus if the priority is getting many storefronts operational quickly without building a huge commerce engineering organization.

Shopify Plus currently supports expansion stores under one organization and supports up to 25 custom React/Hydrogen storefronts.

The catch is architectural: Shopify's expansion stores are still independently configured/data-isolated stores. For a retailer with genuinely complex shared-domain requirements—different brands, catalogs, pricing models, markets, fulfillment rules, etc.—I'd want to model those requirements carefully before making Shopify the system of record.

My decision rule

I'd use this:

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—provided your organization genuinely has the engineering maturity to operate a composable platform.

The key distinction is that headless ≠ composable. Headless separates the frontend from commerce; composable lets you independently evolve major capabilities such as catalog, pricing, promotions, checkout, search, CMS, and customer identity. Shopify Shopify

My shortlist

Why I'd lean commercetools

For, say, 20–100+ storefronts across brands, countries, business units, or channels, I'd want the architecture to look roughly like:

                     ┌── Storefront A
                     ├── Storefront B
Customers ───────────┼── Storefront C
                     ├── Mobile App
                     └── B2B Portal
                            │
                       BFF / API Gateway
                            │
        ┌───────────────────┼───────────────────┐
        │                   │                   │
    Commerce            CMS/PIM             Search
        │                   │                   │
        └───────────────┬───┴───────────────────┘
                        │
                 ERP / OMS / WMS

The important architectural property is that storefronts aren't the unit of commerce ownership. Your product, pricing, inventory, customer, promotion, and order capabilities should be reusable across all of them.

commercetools is particularly suited to this because it's API-first and composable, rather than requiring your storefronts to conform to a particular presentation layer. Current industry comparisons also place it toward the top for complex multi-brand/multi-market architectures. Naturaily CIOPages

But I'd seriously consider Shopify Plus

If your priority is:

• 10–50+ storefronts
• relatively conventional B2C retail
• rapid market launches
• minimizing infrastructure/DevOps ownership
• strong checkout and commerce operations
• a large ecosystem of integrations

then Shopify Plus may actually be the better business decision.

Shopify now supports custom headless storefronts through its Storefront API, Hydrogen/Oxygen, or your own frontend stack, and Plus supports multiple custom storefronts. Shopify Shopify Help Center

That's an important point: I wouldn't reject Shopify because it's "not headless enough." It can be a very effective headless backend while your teams independently build the experiences on top.

Where I'd draw the line

I'd choose commercetools when the retailer says:

"We expect commerce itself to become an internal platform. Different teams and brands need to consume commerce capabilities independently, and we expect to replace individual components over time."

I'd choose Shopify Plus when they say:

"We want a highly scalable commerce engine that our teams can customize heavily, but we don't want to own a distributed commerce platform."

That distinction is more important than almost any feature comparison.

One architectural warning

For a large retailer, I wouldn't create one completely independent commerce stack per storefront.

Instead, I'd establish:

• shared commerce capabilities
• shared product/customer/order domains
• market/brand configuration
• independent storefront deployments
• a BFF/API layer per experience where necessary
• event-driven integration with ERP/OMS/PIM/WMS
• central observability and identity
• isolated deployment pipelines

That gives you many storefronts without multiplying your operational complexity.

Bottom line:
commercetools for maximum long-term architectural flexibility; Shopify Plus for the best balance of enterprise scale, headless capability, and operational simplicity. For a large retailer whose engineering organization is a strategic differentiator, I'd put commercetools first on the technical evaluation and Shopify Plus first on the TCO/time-to-market evaluation. Shopify Shopify

If you tell me roughly how many storefronts, countries, brands, annual GMV, B2C vs B2B, and your ERP/PIM/OMS stack, I can give you a much more concrete architecture recommendation and a platform scorecard.

I'd choose Shopify Plus when they say:

"We want a highly scalable commerce engine that our teams can customize heavily, but we don't want to own a distributed commerce platform."

That distinction is more important than almost any feature comparison.

One architectural warning

For a large retailer, I wouldn't create one completely independent commerce stack per storefront.

Instead, I'd establish:

• shared commerce capabilities
• shared product/customer/order domains
• market/brand configuration
• independent storefront deployments
• a BFF/API layer per experience where necessary
• event-driven integration with ERP/OMS/PIM/WMS
• central observability and identity
• isolated deployment pipelines

That gives you many storefronts without multiplying your operational complexity.

Bottom line:
commercetools for maximum long-term architectural flexibility; Shopify Plus for the best balance of enterprise scale, headless capability, and operational simplicity. For a large retailer whose engineering organization is a strategic differentiator, I'd put commercetools first on the technical evaluation and Shopify Plus first on the TCO/time-to-market evaluation.

If I were the lead developer at a large retailer building a headless architecture with many storefronts, my default recommendation would be commercetools—with BigCommerce as the pragmatic alternative and Shopify Plus if operational simplicity/speed outweighs architectural freedom.

My ranking

1. My pick: commercetools

For a retailer with, say, 20–100+ storefronts/brands/regions, I'd strongly consider commercetools.

Its fundamental model is very aligned with what you're describing: commerce capabilities are exposed through APIs, and the platform is designed to let you independently build and evolve different experiences. commercetools describes its current platform as headless, modular, API-native, and designed for enterprise-scale multi-channel commerce. Commercetools Commercetools

That gives you an architecture roughly like:

                    ┌── Storefront A (Next.js)
                    ├── Storefront B (Next.js)
                    ├── Storefront C (mobile)
                    ├── Storefront D (B2B)
                    └── Storefront E (international)
                             │
                       API / GraphQL
                             │
                 ┌───────────▼───────────┐
                 │    commercetools      │
                 │                       │
                 │ Catalog               │
                 │ Pricing               │
                 │ Cart / Checkout       │
                 │ Orders                │
                 │ Promotions            │
                 │ Customer data         │
                 └───────────┬───────────┘
                             │
        ┌────────────────────┼─────────────────────┐
        ▼                    ▼                     ▼
       ERP                  PIM                   OMS

The big advantage is that the storefront architecture becomes your architecture, rather than adapting your frontend to the assumptions of a monolithic commerce platform.

The tradeoff is that your engineering organization has to own more of the surrounding platform: frontend infrastructure, CMS/PIM integration, search, observability, orchestration, deployment, etc.

2. BigCommerce if you want less engineering overhead

I'd put BigCommerce very high on the shortlist.

Its Multi-Storefront capability is specifically designed for multiple brands, regions and channels from a common backend, while its headless offering lets you use your own frontend/CMS/PIM/etc. BigCommerce BigCommerce

That's compelling if your goal is:

"Give engineering freedom to build many storefronts, but don't make engineering build the entire commerce platform."

That's a subtly different goal from commercetools.

I'd choose BigCommerce over commercetools if the retailer has a relatively small platform-engineering organization or wants to get the first 10–20 storefronts operational quickly.

3. Shopify Plus if the business wants maximum operational simplicity

Shopify Plus is extremely compelling if your primary objective is getting many high-volume stores running with minimal commerce-platform maintenance.

Shopify supports headless storefronts, including Hydrogen, and Plus provides organization-level management and expansion stores. Shopify Help Center Shopify Help Center

However, there's an important distinction for your use case: Shopify's expansion stores are independent stores with their own data/settings/configuration, even though they can be managed centrally. Standard Plus contracts include one main store plus nine expansion stores, with additional stores requiring discussion with Shopify. Shopify Help Center

So if you're envisioning:

"One gigantic commerce domain with 75 storefronts that share sophisticated catalog, pricing, customer and business-rule models"

I'd investigate commercetools first.

If you're envisioning:

"We have 15 brands/regions and want each to operate almost like an independent business, while corporate IT provides a common platform"

Shopify Plus becomes much more attractive.

The architectural decision I'd actually make

I wouldn't select based primarily on "which platform has the best headless APIs."

I'd establish these requirements first:

• Number of storefronts: 10 vs. 100 makes a huge difference.
• Shared vs. independent catalogs
• Shared vs. independent pricing
• Regionalization: currencies, tax, inventory, fulfillment
• Brand isolation
• B2C + B2B
• Customer identity across storefronts
• Promotion complexity
• OMS/ERP/PIM ownership
• Search ownership
• CMS ownership
• How much platform engineering you want to own
• Whether acquisitions/new brands need to be onboarded in weeks or months

For a large retailer, I'd also insist on testing the organizational model, not just the APIs.

You want something like:

                    Commerce Platform Team
                             │
             ┌───────────────┼───────────────┐
             │               │               │
        Commerce APIs     Design System    Platform
             │               │               │
       ┌─────┴─────┐         │          ┌────┴────┐
       │           │         │          │         │
    Brand A     Brand B    Shared UI   Search    Data
       │           │
    Storefront   Storefront

The key is that adding storefront #37 shouldn't require cloning the entire technology stack.

Bottom line

For a technically sophisticated large retailer:
commercetools is my first choice.

For a retailer wanting headless + multi-storefront without taking on as much platform engineering:
BigCommerce.

For a retailer prioritizing speed, operational simplicity, and a mature managed ecosystem:
Shopify Plus.

I'd make the final decision with a 6–8 week proof-of-architecture, where each vendor has to implement the same difficult scenario: three brands, two countries, shared catalog, different pricing, localized promotions, unified customer identity, separate storefront deployments, and an ERP/PIM/OMS integration. That exercise will reveal far more than vendor demos.

Its Multi-Storefront capability is specifically designed for multiple brands, regions and channels from a common backend, while its headless offering lets you use your own frontend/CMS/PIM/etc. BigCommerce BigCommerce

That's compelling if your goal is:

"Give engineering freedom to build many storefronts, but don't make engineering build the entire commerce platform."

That's a subtly different goal from commercetools.

I'd choose BigCommerce over commercetools if the retailer has a relatively small platform-engineering organization or wants to get the first 10–20 storefronts operational quickly.

3. Shopify Plus if the business wants maximum operational simplicity

Shopify Plus is extremely compelling if your primary objective is getting many high-volume stores running with minimal commerce-platform maintenance.

Shopify supports headless storefronts, including Hydrogen, and Plus provides organization-level management and expansion stores. help.shopify.com help.shopify.com

However, there's an important distinction for your use case: Shopify's expansion stores are independent stores with their own data/settings/configuration, even though they can be managed centrally. Standard Plus contracts include one main store plus nine expansion stores, with additional stores requiring discussion with Shopify.

So if you're envisioning:

"One gigantic commerce domain with 75 storefronts that share sophisticated catalog, pricing, customer and business-rule models"

I'd investigate commercetools first.

If you're envisioning:

"We have 15 brands/regions and want each to operate almost like an independent business, while corporate IT provides a common platform"

If I were the lead developer at a large retailer with many storefronts, my default choice would be commercetools—unless your organization already has a major Salesforce or Shopify investment.

My shortlist

Why I'd lean commercetools

For a large retailer, I would optimize for independent storefront evolution without duplicating commerce logic.

commercetools is built around an API-first, composable architecture and is explicitly designed for enterprise scenarios involving multiple regions, currencies, languages, brands, catalogs, pricing, etc. Shopify

I'd structure it roughly like:

                    ┌── Brand A storefront
                    ├── Brand B storefront
Customers ── CDN ───┼── Country C storefront
                    ├── Mobile app
                    └── In-store / kiosk

                         │
                    API / BFF layer
                         │
        ┌────────────────┼─────────────────┐
        │                │                 │
     Commerce          Search            CMS
  commercetools       Algolia          Contentful
        │
   ┌────┼───────────┐
   │    │           │
 Catalog Pricing   Cart/Checkout
   │    │           │
   └────┼───────────┘
        │
       OMS / ERP / PIM / Tax / Payments

The key architectural advantage is that the storefront isn't the system boundary. Your brands and channels can evolve independently while sharing the underlying commerce capabilities.

But there's an important exception: Shopify Plus

If the business requirement is more like:

"We need 20–50 storefronts, different branding/localization, excellent commerce capabilities, and we don't want our engineering organization operating a giant distributed commerce platform."

I'd seriously consider Shopify Plus instead.

Shopify's current headless tooling supports multiple custom storefronts through its Headless channel, with Storefront API access, publishing, order attribution, and analytics. Shopify currently documents up to 100 active storefronts/access tokens per shop. Shopify Shopify

That's a pretty compelling operational proposition.

The tradeoff is that you're accepting more of Shopify's underlying commerce model rather than designing the commerce domain entirely around your own architecture.

Where Salesforce fits

If you're already heavily invested in Salesforce—CRM, CDP/Data Cloud, Marketing Cloud, Service, etc.—Salesforce Commerce Cloud becomes much more attractive.

Its current Composable Storefront architecture separates the React-based storefront from Commerce APIs and provides managed hosting/runtime. Salesforce also explicitly supports multiple sites and multiple storefronts from a common codebase. Developer Developer

I'd choose it when Salesforce ecosystem integration is strategically important, rather than because it's inherently a better headless architecture than commercetools.

What I'd actually recommend

For a greenfield enterprise retailer, I'd rank them:

1. commercetools — maximum architectural flexibility
2. Shopify Plus — maximum business/engineering simplicity
3. Salesforce Commerce Cloud — strongest if Salesforce is already strategic
4. Adobe Commerce — situationally strong, but I'd need a specific reason

The most important question isn't actually "Which platform is most headless?" It's:

Where do you want the boundary between your engineering organization and the commerce vendor to be?

If your team is large enough to operate APIs, eventing, BFFs, observability, CI/CD, PIM/OMS integrations, and multiple frontend applications, I'd take commercetools.

If your team wants to focus its engineering effort on customer experience rather than operating commerce infrastructure, I'd take Shopify Plus. Shopify itself now recommends a selective composable approach rather than decomposing everything simply because you can. Shopify

If you tell me roughly number of brands/storefronts, countries, SKU count, B2C vs B2B, existing ERP/PIM/CRM, and engineering team size, I can give you the architecture I'd put in front of an enterprise architecture review board—including platform, CMS, search, PIM, OMS, CDN, frontend framework, and integration/event architecture.

If I were the lead developer at a large retailer with many storefronts, my default recommendation 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 platform.

My ranking

Why I'd pick commercetools

For a retailer with, say, 20 brands × 15 countries × multiple channels, I'd want the commerce backend to be a set of reusable services rather than a collection of independently configured stores.

commercetools is explicitly API-first and composable, with commerce capabilities that can be independently integrated and scaled. Its architecture is designed around expanding across brands, channels and markets without requiring a monolithic replatform. commercetools commercetools

I'd structure it roughly like:

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
                         ├── Mobile App
                         ├── Marketplace
                         └── In-store / Kiosk
                                │
                         Experience Layer
                       Next.js / React / etc.
                                │
                    ┌───────────┴───────────┐
                    │   API / BFF Layer     │
                    └───────────┬───────────┘
                                │
             ┌──────────────────┼──────────────────┐
             │                  │                  │
        commercetools          PIM                CMS
        ├─ Catalog             │                  │
        ├─ Pricing             │                  │
        ├─ Cart                │                  │
        ├─ Promotions          │                  │
        ├─ Inventory           │                  │
        └─ Orders              │                  │
             │
      ┌──────┴────────┐
      │               │
     ERP             OMS

The important architectural decision is that storefronts are configurations/experiences over shared commerce capabilities, rather than 20 separate commerce implementations.

When I'd choose something else

Shopify Plus would be my choice if the business values speed, operational simplicity and a relatively lean engineering organization more than maximum architectural control. Shopify supports headless builds through its API layer and Hydrogen/Oxygen or frameworks such as Next.js, while also allowing many retail locations to operate from one back office. Shopify

Salesforce Commerce Cloud would be my choice if the retailer is already heavily invested in Salesforce CRM/customer data and needs sophisticated enterprise capabilities. Salesforce supports headless APIs, composable storefronts, and multiple sites/storefronts; its documentation explicitly describes scenarios involving multiple storefronts and shared data. Salesforce Developer Salesforce

BigCommerce is attractive if you want headless flexibility without going all the way into the architectural complexity of a composable platform. Shopify itself currently characterizes BigCommerce as a strong headless option in its 2026 enterprise comparison. Shopify

The bigger question I'd ask as lead dev

I wouldn't select the platform based primarily on "does it support multiple storefronts?"

I'd evaluate these instead:

1. Can we share catalog, pricing, inventory and customer services across every storefront?
2. Can each brand/local market override only what it needs?
3. Can a new storefront be provisioned through configuration rather than a new codebase?
4. Can we run different frontend stacks without changing commerce?
5. How good are the APIs/webhooks/event model?
6. Can we survive a major traffic spike without engineering intervention?
7. How painful is localization, tax, currency and regional pricing?
8. How do we handle ERP/OMS/PIM/search/payment integrations?
9. What's the 5-year TCO, including engineering and platform specialists?
10. Can individual brands deploy independently without fragmenting the commerce backend?

For a large retailer with a strong internal engineering organization, I'd therefore put commercetools at #1, Salesforce Commerce Cloud at #2, and Shopify Plus at #3.

The distinction is essentially:

commercetools: optimize for architectural flexibility
Salesforce: optimize for enterprise ecosystem + complexity
Shopify: optimize for speed and operational simplicity

If you tell me roughly how many storefronts/brands, countries, annual GMV, B2C vs B2B, and your existing ERP/PIM/CRM, I can give you a much more opinionated architecture—including which platform I'd actually put into production and what I'd keep outside it.

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
                         ├── Mobile App
                         ├── Marketplace
                         └── In-store / Kiosk
                                │
                         Experience Layer
                       Next.js / React / etc.
                                │
                    ┌───────────┴───────────┐
                    │   API / BFF Layer     │
                    └───────────┬───────────┘
                                │
             ┌──────────────────┼──────────────────┐
             │                  │                  │
        commercetools          PIM                CMS
        ├─ Catalog             │                  │
        ├─ Pricing             │                  │
        ├─ Cart                │                  │
        ├─ Promotions          │                  │
        ├─ Inventory           │                  │
        └─ Orders              │                  │
             │
      ┌──────┴────────┐
      │               │
     ERP             OMS

The important architectural decision is that storefronts are configurations/experiences over shared commerce capabilities, rather than 20 separate commerce implementations.

When I'd choose something else

Shopify Plus would be my choice if the business values speed, operational simplicity and a relatively lean engineering organization more than maximum architectural control. Shopify supports headless builds through its API layer and Hydrogen/Oxygen or frameworks such as Next.js, while also allowing many retail locations to operate from one back office. Shopify

Salesforce Commerce Cloud would be my choice if the retailer is already heavily invested in Salesforce CRM/customer data and needs sophisticated enterprise capabilities. Salesforce supports headless APIs, composable storefronts, and multiple sites/storefronts; its documentation explicitly describes scenarios involving multiple storefronts and shared data. salesforce.com developer.salesforce.com help.salesforce.com

BigCommerce is attractive if you want headless flexibility without going all the way into the architectural complexity of a composable platform. Shopify itself currently characterizes BigCommerce as a strong headless option in its 2026 enterprise comparison.

The bigger question I'd ask as lead dev

I wouldn't select the platform based primarily on "does it support multiple storefronts?"

I'd evaluate these instead:

If I were the lead developer at a large retailer building a headless architecture for many storefronts, my default choice would be commercetools—unless your priority is minimizing engineering/operational complexity.

My shortlist

Why I'd pick commercetools

For a large retailer, the important question isn't simply "Can this platform run multiple websites?" It's "Can we create a reusable commerce platform underneath dozens of independently evolving experiences?"

commercetools is explicitly built around composable commerce: independent APIs/services for commerce capabilities rather than a single application that owns the entire storefront experience. That makes it particularly attractive when you have multiple brands, countries, channels, customer segments, or future touchpoints. Commercetools Netguru

I'd architect it roughly like:

                    ┌── Brand A web
                    ├── Brand B web
                    ├── Country X web
Customers ── CDN ───┼── Mobile apps
                    ├── Kiosks
                    └── Other channels
                          │
                     BFF / API layer
                          │
              ┌───────────┴───────────┐
              │     commercetools      │
              │                        │
              │ Catalog / Pricing      │
              │ Cart / Checkout        │
              │ Promotions             │
              │ Orders                 │
              └───────────┬───────────┘
                          │
        ┌─────────┬───────┼────────┬─────────┐
        │         │       │        │         │
       PIM       OMS     ERP    Search     CMS

The major advantage is organizational scalability as much as technical scalability: individual storefront teams can move relatively independently while the underlying commerce capabilities remain shared.

But I'd seriously consider BigCommerce

If your retailer doesn't have a large platform-engineering organization, BigCommerce may actually be the better business decision.

BigCommerce has native Multi-Storefront capabilities for multiple brands, regions, and customer segments, while also supporting custom headless storefronts through REST/GraphQL APIs. Its current Catalyst architecture provides a Next.js/React reference implementation. BigCommerce BigCommerce BigCommerce

That's a compelling combination:

one SaaS commerce backend + many independently deployed Next.js storefronts.

You give up some of the architectural purity/flexibility of commercetools, but substantially reduce the amount of commerce infrastructure your team has to own.

Where Shopify Plus fits

Shopify Plus is excellent if you're primarily a collection of brands/DTC storefronts and want the platform to handle a lot of operational complexity.

It has expansion stores under a common organization, including international, B2B, employee/VIP, and physical-retail use cases. However, Shopify's expansion stores are independent stores with their own data/settings, which matters if your goal is a deeply unified enterprise commerce model. Shopify currently documents up to 10 stores on a standard Plus contract before additional arrangements are required. Shopify Help Center

So I wouldn't choose Shopify Plus merely because "we need lots of storefronts." I'd choose it if operational simplicity and Shopify's ecosystem outweigh maximum architectural control.

My recommendation

I'd make the decision this way:

• 50+ storefronts / multiple brands / countries / channels / highly customized commerce: commercetools
• Many storefronts but want a SaaS platform and smaller engineering footprint: BigCommerce
• Primarily DTC brands and rapid execution: Shopify Plus
• Deep Adobe ecosystem/content personalization requirements: Adobe Commerce
• SAP-centric enterprise with complex B2B/ERP processes: SAP Commerce Cloud

For a large retailer with a genuinely strategic, multi-storefront platform, my architecture review would start with commercetools vs. BigCommerce, rather than comparing every commerce vendor equally.

The deciding question I'd put to your architecture team is:

Do we want to build and operate a commerce platform, or do we want to consume a commerce platform?

If the answer is build/compose, pick commercetools.
If the answer is consume, pick BigCommerce.

That distinction will probably matter more to your 5-year TCO than almost any individual feature comparison.

The major advantage is organizational scalability as much as technical scalability: individual storefront teams can move relatively independently while the underlying commerce capabilities remain shared.

But I'd seriously consider BigCommerce

If your retailer doesn't have a large platform-engineering organization, BigCommerce may actually be the better business decision.

BigCommerce has native Multi-Storefront capabilities for multiple brands, regions, and customer segments, while also supporting custom headless storefronts through REST/GraphQL APIs. Its current Catalyst architecture provides a Next.js/React reference implementation. BigCommerce BigCommerce BigCommerce

That's a compelling combination:

one SaaS commerce backend + many independently deployed Next.js storefronts.

You give up some of the architectural purity/flexibility of commercetools, but substantially reduce the amount of commerce infrastructure your team has to own.

Where Shopify Plus fits

Shopify Plus is excellent if you're primarily a collection of brands/DTC storefronts and want the platform to handle a lot of operational complexity.

It has expansion stores under a common organization, including international, B2B, employee/VIP, and physical-retail use cases. However, Shopify's expansion stores are independent stores with their own data/settings, which matters if your goal is a deeply unified enterprise commerce model. Shopify currently documents up to 10 stores on a standard Plus contract before additional arrangements are required.

If I were the lead developer at a large retailer and the requirement were headless commerce powering many storefronts/brands/regions, my default choice would be commercetools.

My shortlist

Why I'd pick commercetools

For a retailer with, say, 10–100+ storefront experiences, I'd want the commerce backend to model stores, markets, channels, pricing, inventory and catalogs independently from the frontend.

commercetools explicitly supports Stores and Channels for modeling multiple shopping contexts, including shared resources and data isolation. Commercetools Documentation

It also gives you a genuinely composable architecture rather than simply putting an API in front of a traditional monolithic commerce system. Its enterprise platform is designed around independent commerce capabilities and supports multiple brands/stores, international expansion, millions of SKUs and high-traffic events. commercetools commercetools

For a large retailer, I'd structure it roughly like:

                         ┌── Storefront A
                         ├── Storefront B
Customers ── CDN ── BFF ─┼── Mobile App
                         ├── Brand C
                         ├── Marketplace
                         └── In-store / kiosk
                              │
                              ▼
                    ┌───────────────────┐
                    │   commercetools   │
                    │                   │
                    │ Catalog           │
                    │ Pricing           │
                    │ Promotions        │
                    │ Cart / Checkout   │
                    │ Orders            │
                    │ Customers         │
                    │ Stores / Channels  │
                    └───────────────────┘
                         │       │
              ┌──────────┘       └──────────┐
              ▼                             ▼
             PIM                           OMS
              │                             │
              ▼                             ▼
             ERP                       Inventory / WMS

That separation is particularly valuable when different storefronts need different catalogs, pricing, promotions, localization, inventory or customer experiences while still sharing underlying commerce capabilities. commercetools commercetools

When I'd choose Shopify Plus instead

I'd seriously consider Shopify Plus if the business priority were:

"We need 20 storefronts launched quickly, with a relatively small platform team, and we don't want to own much commerce infrastructure."

Shopify has become substantially more compelling for headless. Its Storefront API, Hydrogen and Oxygen support custom storefronts, while Plus provides organization-level management and expansion stores. Shopify Shopify

The big architectural caveat is store proliferation. Shopify Plus expansion stores are separate stores with their own settings/configuration/data, even though the organization gets centralized management. The standard Plus structure currently provides one main store plus nine expansion stores without additional cost; additional stores require working with Shopify. Shopify Help Center

So if you have:

• 5–10 genuinely independent brands → Shopify Plus looks very attractive
• 30+ markets/storefronts with complex shared commerce rules → I'd lean commercetools
• Highly customized retail domain logic → commercetools
• "Commerce should mostly be someone else's operational problem" → Shopify Plus

The architectural distinction I'd focus on

The important question isn't really "Which platform has the best headless API?"

It's:

"Where do we want our complexity to live?"

With Shopify, you outsource a huge amount of commerce complexity and build your differentiation around it.

With commercetools, you accept more architectural responsibility in exchange for much greater control over the commerce domain.

For a large retailer with a strong engineering organization, I'd generally take the latter.

My recommendation

1. commercetools — best long-term platform for a large, multi-brand/multi-store retailer.
2. Shopify Plus — best if speed, simplicity and reduced platform ownership matter more than architectural control.
3. Salesforce Commerce Cloud — move this to #1 if Salesforce CRM/customer ecosystem is already deeply embedded.
4. BigCommerce Enterprise — very credible option, particularly if you want an open/API-centric platform without going as deeply composable.

If you tell me roughly how many storefronts, brands/countries, SKUs, peak orders/sec, B2B vs B2C, and your existing ERP/PIM/OMS (SAP, Salesforce, etc.), I can give you a much more concrete platform + target architecture recommendation, including where I'd put the BFF, CMS, PIM, search, pricing, inventory and checkout.

Shopify has become substantially more compelling for headless. Its Storefront API, Hydrogen and Oxygen support custom storefronts, while Plus provides organization-level management and expansion stores.

The big architectural caveat is store proliferation. Shopify Plus expansion stores are separate stores with their own settings/configuration/data, even though the organization gets centralized management. The standard Plus structure currently provides one main store plus nine expansion stores without additional cost; additional stores require working with Shopify.

So if you have:

If I were the lead dev at a large retailer with many storefronts, my default shortlist would be commercetools, Salesforce Commerce Cloud, and Adobe Commerce—but I’d lean commercetools if the engineering organization is genuinely capable of operating a composable platform.

My recommendation: commercetools

commercetools.com is probably the strongest architectural fit for a large retailer where you expect many brands, countries, channels, and independently evolving storefronts.

Why:

• API-first and headless by design. Commerce capabilities are exposed independently rather than forcing every storefront through one presentation layer. commercetools commercetools
• Excellent fit for multiple storefronts. You can have different React/Next.js/etc. experiences consuming the same underlying catalog, pricing, cart, checkout and other commerce capabilities.
• Composable rather than merely headless. You can replace search, CMS, personalization, payments, etc. without necessarily replacing the commerce core.
• Strong engineering ownership. It gives a large development organization considerable control over architecture and deployment boundaries.
• Good long-term anti-lock-in story. The APIs and modular model make it easier to evolve the stack as your retail requirements change.

The tradeoff is important: commercetools gives you architectural freedom, but you have to operate that freedom. A large number of independent services can become an integration/observability/governance problem if you don't establish strong platform standards.

How I'd rank the options

The interesting alternative: Salesforce

salesforce.com would be my #1 alternative.

Salesforce's current Composable Storefront uses its Commerce APIs with a React-based PWA Kit and managed runtime, and Salesforce explicitly supports mixing its storefront with other vendors and custom frontends. Salesforce Developers Salesforce Developers

I'd choose Salesforce over commercetools when the retailer values:

• A broader enterprise commerce ecosystem
• Salesforce CRM/customer-data integration
• More out-of-the-box commerce capabilities
• A managed storefront/runtime
• Lower organizational appetite for assembling the entire commerce stack

In other words, Salesforce is the safer enterprise platform; commercetools is the cleaner architecture for an engineering-led organization.

Where Adobe fits

business.adobe.com is particularly interesting if you already have a substantial Adobe footprint. Adobe supports multiple websites/stores/store views from one Commerce installation and supports headless architectures. Experience League Experience League

The caveat is scale: Adobe notes that additional stores can increase catalog/indexing load and potentially affect uncached catalog performance, so I'd scrutinize the architecture carefully if you're talking about dozens or hundreds of storefronts. Experience League

What I'd actually build

For a large retailer, I'd avoid thinking of this as:

"One commerce platform → many websites."

I'd design it more like:

                       ┌── Brand A storefront
                       ├── Brand B storefront
                       ├── Brand C storefront
                       ├── Mobile app
                       ├── Marketplace
                       └── In-store / kiosk
                                │
                         Experience APIs
                                │
              ┌─────────────────┼─────────────────┐
              │                 │                 │
           Catalog           Pricing          Customer
              │                 │                 │
              ├────────── Commerce Core ──────────┤
              │                 │                 │
           Cart/Checkout     Promotions       Inventory
                                │
                    ┌───────────┼───────────┐
                    │           │           │
                   OMS         ERP        Payments

And I'd make storefront configuration/data, rather than application forks, the mechanism for creating new brands/sites:

Storefront
  ├── brand configuration
  ├── locale/currency
  ├── catalog scope
  ├── pricing context
  ├── fulfillment rules
  ├── CMS space
  ├── feature flags
  └── theme/components

That distinction becomes very important once you're supporting 20+ storefronts.

Bottom line

If I were making the architectural decision today:

1. commercetools — my pick for an engineering-led, highly scalable multi-storefront architecture.
2. Salesforce Commerce Cloud — my pick if enterprise integration, ecosystem, and managed capabilities outweigh architectural purity.
3. Adobe Commerce — compelling if Adobe/Magento is already deeply embedded in the organization.
4. Shopify Plus — I'd seriously consider it if reducing platform operations is more important than maximum backend architectural control.

The decision can change substantially depending on whether you're talking about 5 storefronts vs. 50 vs. 500, and whether they're separate brands, countries, B2B/B2C experiences, or just localized sites. If you give me those numbers plus your rough GMV/order volume and existing stack (SAP, Salesforce, Adobe, Shopify, etc.), I can give you a lead-dev-level architecture recommendation and platform scorecard.

The caveat is scale: Adobe notes that additional stores can increase catalog/indexing load and potentially affect uncached catalog performance, so I'd scrutinize the architecture carefully if you're talking about dozens or hundreds of storefronts. Experience League

What I'd actually build

For a large retailer, I'd avoid thinking of this as:

"One commerce platform → many websites."

I'd design it more like:

                       ┌── Brand A storefront
                       ├── Brand B storefront
                       ├── Brand C storefront
                       ├── Mobile app
                       ├── Marketplace
                       └── In-store / kiosk
                                │
                         Experience APIs
                                │
              ┌─────────────────┼─────────────────┐
              │                 │                 │
           Catalog           Pricing          Customer
              │                 │                 │
              ├────────── Commerce Core ──────────┤
              │                 │                 │
           Cart/Checkout     Promotions       Inventory
                                │
                    ┌───────────┼───────────┐
                    │           │           │
                   OMS         ERP        Payments

And I'd make storefront configuration/data, rather than application forks, the mechanism for creating new brands/sites:

Storefront
  ├── brand configuration
  ├── locale/currency
  ├── catalog scope
  ├── pricing context
  ├── fulfillment rules
  ├── CMS space
  ├── feature flags
  └── theme/components

That distinction becomes very important once you're supporting 20+ storefronts.

Bottom line

If I were making the architectural decision today:

1. commercetools — my pick for an engineering-led, highly scalable multi-storefront architecture.
2. Salesforce Commerce Cloud — my pick if enterprise integration, ecosystem, and managed capabilities outweigh architectural purity.
3. Adobe Commerce — compelling if Adobe/Magento is already deeply embedded in the organization.
4. Shopify Plus — I'd seriously consider it if reducing platform operations is more important than maximum backend architectural control.

The decision can change substantially depending on whether you're talking about 5 storefronts vs. 50 vs. 500, and whether they're separate brands, countries, B2B/B2C experiences, or just localized sites. If you give me those numbers plus your rough GMV/order volume and existing stack (SAP, Salesforce, Adobe, Shopify, etc.), I can give you a lead-dev-level architecture recommendation and platform scorecard.

If I were the lead dev at a large retailer building a headless platform for many storefronts, my default choice would be commercetools—unless minimizing engineering/operational burden is more important than architectural flexibility.

My ranking

Why I'd pick commercetools

For a retailer with, say, 10–100+ storefronts across brands, countries, channels, or business units, the key question isn't simply "which platform has a headless API?" It's which platform lets us treat commerce as a shared capability rather than creating a collection of stores that happen to use the same software.

commercetools is particularly strong here. Its architecture is API-first and modular, explicitly supports multiple brands/stores and international expansion, and is designed around independently composable commerce capabilities. It also targets very large catalogs and traffic volumes. commercetools commercetools

I'd structure it roughly like:

                    ┌── Brand A storefront
                    ├── Brand B storefront
                    ├── Country A storefront
                    ├── Country B storefront
                    ├── Mobile apps
                    ├── Marketplace
                    └── In-store / other channels
                              │
                         API / BFF layer
                              │
              ┌───────────────┴───────────────┐
              │       commercetools            │
              │                                │
              │ Catalog   Pricing   Cart       │
              │ Inventory Orders   Promotions  │
              │ Customers Checkout              │
              └───────────────┬───────────────┘
                              │
             ┌────────────────┼────────────────┐
             │                │                │
            PIM              ERP              OMS
             │                │                │
          Content          Finance          Fulfillment

The important architectural property is that storefronts aren't the unit of architecture. Commerce capabilities are.

That makes it much easier to say:

"Launch Brand C in Germany using the existing catalog, pricing, inventory and checkout capabilities, but with a completely different experience."

rather than:

"Create another store and figure out how to synchronize everything."

Where Shopify Plus wins

I'd seriously consider Shopify Plus if the retailer's overriding goal is getting dozens of storefronts operational quickly while keeping the commerce platform team relatively small.

Shopify now supports bespoke headless storefronts through its Storefront API and Hydrogen, while retaining its managed commerce backend. It also explicitly supports regional storefronts with shared backend capabilities. Shopify Shopify

The tradeoff is architectural control. Shopify gives you a very good managed commerce platform, but I'd be less inclined to make it the core of a deeply customized enterprise commerce operating model where pricing, catalog, promotions, customer models, order orchestration, etc. are all strategic differentiators.

Choose Shopify Plus when:

• Speed to market matters enormously.
• The majority of storefronts have conventional commerce requirements.
• You want less infrastructure/platform engineering.
• Marketing/merchandising teams should have a polished SaaS admin.
• Your organization is comfortable with Shopify's platform constraints.

Choose commercetools when:

• Commerce itself is strategic infrastructure.
• You expect many brands/countries/channels.
• Different storefronts have materially different experiences.
• You have a strong engineering/platform organization.
• You want to own the orchestration layer and integrate deeply with PIM/ERP/OMS/CDP/etc.
• You want to avoid the storefront/store being the fundamental architectural boundary.

Adobe Commerce is the interesting third option

I'd put Adobe Commerce high on the list if the retailer already has a substantial Adobe investment or needs sophisticated catalog/multi-site functionality.

Adobe supports multiple websites, stores and store views from a single installation, including separate domains, catalogs, currencies and languages. Its current cloud architecture is also fully headless through GraphQL. Experience League Experience League

The concern I'd have as lead dev is operational and architectural complexity. Adobe can be extremely capable, but I'd want a very good reason to accept that complexity rather than starting with a more natively API-first/composable platform.

The decision I'd make

For a large retailer starting greenfield today, I'd use this rule:

• commercetools → best for a strategic, highly composable enterprise commerce platform.
• Shopify Plus → best when speed, reliability and reducing operational burden dominate.
• Adobe Commerce → best when Adobe/ecosystem investment and complex traditional commerce capabilities dominate.
• BigCommerce → worth serious consideration if you want headless flexibility with a somewhat more conventional commerce platform.

One important caveat: I would not automatically make everything headless. Headless multiplies the amount of software your organization owns. If the storefronts don't require genuinely differentiated experiences, a managed storefront can be dramatically cheaper and easier to operate. Shopify itself makes essentially this distinction in its current enterprise guidance. Shopify

If you're designing this for a retailer doing $1B+ revenue with multiple brands/countries, my shortlist would therefore be commercetools vs. Shopify Plus, with commercetools as my architectural default.

"Launch Brand C in Germany using the existing catalog, pricing, inventory and checkout capabilities, but with a completely different experience."

rather than:

"Create another store and figure out how to synchronize everything."

Where Shopify Plus wins

I'd seriously consider Shopify Plus if the retailer's overriding goal is getting dozens of storefronts operational quickly while keeping the commerce platform team relatively small.

Shopify now supports bespoke headless storefronts through its Storefront API and Hydrogen, while retaining its managed commerce backend. It also explicitly supports regional storefronts with shared backend capabilities.

If I were the lead developer at a large retailer building a headless architecture with many storefronts, my default choice would be commercetools—with Salesforce Commerce Cloud as the strongest alternative if your organization is already deeply invested in Salesforce.

My ranking

Why I'd choose commercetools

For a retailer with, say, 20–100+ storefronts/brands/regions, I would optimize for the commerce platform becoming a shared capability layer, rather than treating each storefront as a separate ecommerce implementation.

commercetools is particularly well suited to that model. Its architecture is API-first and headless, and its Stores and Channels concepts explicitly support multiple commerce experiences with shared resources, data isolation, different pricing strategies, and inventory contexts. commercetools commercetools Documentation

I'd structure it roughly like:

                    ┌── Brand A web
                    ├── Brand B web
                    ├── Brand C web
                    ├── Regional storefronts
                    ├── Mobile apps
                    └── In-store / other channels
                              │
                         Experience Layer
                    Next.js / React / BFF
                              │
                    ──────────┼──────────
                              │
                       Commerce API Layer
                              │
                    ┌─────────┴─────────┐
                    │   commercetools   │
                    │                   │
                    │ Catalog            │
                    │ Cart               │
                    │ Pricing            │
                    │ Promotions        │
                    │ Orders             │
                    │ Customers          │
                    └─────────┬─────────┘
                              │
          ┌───────────────────┼───────────────────┐
          │                   │                   │
         PIM                 OMS                 ERP
          │                   │                   │
       Search              Inventory           Finance
       CMS                 Fulfillment         Tax

The important architectural distinction is that the storefronts shouldn't own commerce logic. They should consume a common commerce foundation and differ primarily in experience, content, merchandising configuration, localization, and brand rules.

When I'd pick Salesforce instead

I'd seriously consider Salesforce if your retailer already has a substantial Salesforce footprint—especially CRM, Marketing Cloud, loyalty, personalization, service, and customer data.

Salesforce's current Composable Storefront separates the frontend from Commerce Cloud and provides PWA Kit plus a managed runtime; its documentation also explicitly supports architectures involving multiple sites and storefronts and sharing data between them. Developer Developer

So if the strategic question is:

"What's the best commerce engine for our technology architecture?"

I'd say commercetools.

If it's:

"What's the best commerce platform for our existing Salesforce enterprise?"

I'd probably say Salesforce Commerce Cloud.

BigCommerce deserves a serious POC

BigCommerce is probably the option I'd put through the most serious competitive evaluation alongside commercetools.

Its Multi-Storefront capability is explicitly designed to manage multiple storefronts from one backend, while its headless stack provides GraphQL APIs and a Next.js/React-oriented approach. BigCommerce

I'd favor it if time-to-market, operational simplicity, and TCO matter more than having maximum control over the commerce domain model.

The bigger architectural decision

For a large retailer, I wouldn't make the decision based primarily on "which platform has the best storefront."

I'd score vendors on these dimensions:

1. Multi-store/brand/locale modeling — can you represent dozens of storefronts without duplicating commerce data?
2. Catalog scale and product modeling
3. Pricing/promotions flexibility
4. Inventory and availability model
5. API quality and event architecture
6. Composable integrations — PIM, CMS, search, OMS, tax, payments, CDP, etc.
7. Deployment and release independence
8. Performance at peak retail events
9. Data isolation and governance
10. Vendor lock-in
11. Developer productivity
12. Total cost at 5–10 year scale

I'd put particularly high weight on #1, #4, #5, #6, and #10. A platform that looks inexpensive with five stores can become painful when you have 50 stores, multiple countries, multiple currencies, different fulfillment models, and several teams deploying independently.

Bottom line: for a large retailer starting fresh, I'd shortlist commercetools + Salesforce Commerce Cloud + BigCommerce, with commercetools as the architectural front-runner. Its headless/API-first model and explicit Stores/Channels abstraction map particularly well to a "one commerce platform, many differentiated storefronts" strategy. commercetools commercetools Documentation

commercetools is particularly well suited to that model. Its architecture is API-first and headless, and its Stores and Channels concepts explicitly support multiple commerce experiences with shared resources, data isolation, different pricing strategies, and inventory contexts. commercetools commercetools Documentation

I'd structure it roughly like:

                    ┌── Brand A web
                    ├── Brand B web
                    ├── Brand C web
                    ├── Regional storefronts
                    ├── Mobile apps
                    └── In-store / other channels
                              │
                         Experience Layer
                    Next.js / React / BFF
                              │
                    ──────────┼──────────
                              │
                       Commerce API Layer
                              │
                    ┌─────────┴─────────┐
                    │   commercetools   │
                    │                   │
                    │ Catalog            │
                    │ Cart               │
                    │ Pricing            │
                    │ Promotions        │
                    │ Orders             │
                    │ Customers          │
                    └─────────┬─────────┘
                              │
          ┌───────────────────┼───────────────────┐
          │                   │                   │
         PIM                 OMS                 ERP
          │                   │                   │
       Search              Inventory           Finance
       CMS                 Fulfillment         Tax

The important architectural distinction is that the storefronts shouldn't own commerce logic. They should consume a common commerce foundation and differ primarily in experience, content, merchandising configuration, localization, and brand rules.

When I'd pick Salesforce instead

I'd seriously consider Salesforce if your retailer already has a substantial Salesforce footprint—especially CRM, Marketing Cloud, loyalty, personalization, service, and customer data.

Salesforce's current Composable Storefront separates the frontend from Commerce Cloud and provides PWA Kit plus a managed runtime; its documentation also explicitly supports architectures involving multiple sites and storefronts and sharing data between them. Developer Developer

So if the strategic question is:

"What's the best commerce engine for our technology architecture?"

I'd say commercetools.

If it's:

"What's the best commerce platform for our existing Salesforce enterprise?"

I'd probably say Salesforce Commerce Cloud.

BigCommerce deserves a serious POC

BigCommerce is probably the option I'd put through the most serious competitive evaluation alongside commercetools.

Its Multi-Storefront capability is explicitly designed to manage multiple storefronts from one backend, while its headless stack provides GraphQL APIs and a Next.js/React-oriented approach.

I'd favor it if time-to-market, operational simplicity, and TCO matter more than having maximum control over the commerce domain model.

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.

For a large retailer with many storefronts, I’d make commercetools the default choice if your organization genuinely has the engineering maturity to operate a composable platform.

commercetools is purpose-built as an API-first, headless commerce platform, and its current enterprise offering is explicitly aimed at running commerce across multiple channels and touchpoints from a shared foundation. commercetools.com

My shortlist

Why I'd lean commercetools

For your use case, I'd optimize for one commerce platform → many independently deployable experiences, rather than treating every storefront as a separate commerce implementation.

A good target architecture would look roughly like:

                       ┌── Storefront A
                       ├── Storefront B
Customers ── CDN ──────┼── Storefront C
                       ├── Mobile App
                       ├── Marketplace
                       └── In-store / kiosk

                              │
                         Experience/API
                              │
                 ┌────────────┴────────────┐
                 │                         │
          commercetools              CMS / PIM
                 │
       ┌─────────┼──────────┐
       │         │          │
    Catalog    Pricing    Promotions
       │         │          │
       └─────────┼──────────┘
                 │
       ┌─────────┼─────────────┐
       │         │             │
      OMS       ERP          Payments

The key architectural property is that storefronts aren't the system of record. They consume commerce capabilities through APIs, so you can launch or retire brands, regions, channels, and experiences without cloning the commerce backend.

That is exactly where commercetools' headless/API-first model is attractive. commercetools.com

But don't automatically choose commercetools

This is the important caveat.

If you're a large retailer but your storefronts are primarily regional variations of the same business, I'd seriously consider Shopify Plus instead. Shopify supports headless storefronts through its Storefront API and has centralized organization management plus expansion stores. commercetools.comhelp.shopify.comwww.shopify.com

Shopify Plus currently supports a main store plus nine expansion stores under the standard arrangement, with additional-store options, and its headless stack can be hosted independently. help.shopify.com

So I'd frame the decision this way:

Choose commercetools if:

• You have 10s–100s of storefronts/channels
• Multiple brands have materially different commerce rules
• Pricing/promotions/catalogs vary substantially by market
• You expect to compose your own PIM, CMS, search, OMS, personalization, etc.
• You have a strong platform engineering organization
• Avoiding vendor lock-in is strategically important
• Commerce is becoming an internal platform rather than simply an ecommerce site

Choose Shopify Plus if:

• Most storefronts are variations of a common commerce model
• You want dramatically less platform engineering/operations
• Speed to market is more important than maximum architectural freedom
• Your differentiating investment is primarily in the frontend experience
• You want merchants/operations teams to have a mature admin experience out of the box

Shopify itself now explicitly positions Plus as a composable foundation where the transactional core stays managed while teams customize the experience layer. www.shopify.com

What I'd do as lead dev

I wouldn't make "headless" the primary architectural decision. I'd establish these principles first:

1. Single canonical product/customer/order model
2. Storefronts are disposable
3. No business logic duplicated in frontend applications
4. API-first commerce capabilities
5. Centralized identity, observability, feature flags and experimentation
6. Independent deployment of each storefront
7. Explicit tenant/brand/market configuration
8. Event-driven integration with ERP/OMS/PIM
9. Platform team owns the commerce primitives; product teams own experiences
10. Don't make everything microservices just because you can

That last point matters. Composable commerce can turn into a very expensive distributed-systems project if you decompose capabilities that don't actually need independent ownership or scaling. Even Shopify's current guidance acknowledges that composability is worthwhile when it solves a real bottleneck rather than simply because it's architecturally fashionable. commercetools.comhelp.shopify.comwww.shopify.com

Bottom line: for a large retailer with genuinely complex multi-store/multi-brand requirements, I'd shortlist commercetools first and Shopify Plus second. If your main problem is operational scale and storefront proliferation, Shopify Plus may win. If your main problem is architectural flexibility and radically different commerce models across the organization, I'd choose commercetools.

For a large retailer with many storefronts, my default recommendation would be commercetools.

commercetools.com

The reason isn't simply that it's "headless." It's that it is particularly well suited to treating commerce as a shared platform underneath many independently evolving experiences.

My shortlist

Why I'd choose commercetools

For your architecture, I'd want something like:

                         ┌── Storefront A
                         ├── Storefront B
                         ├── Storefront C
                         ├── Mobile App
                         ├── Marketplace
                         └── In-store / Kiosk
                                  │
                         ┌────────▼────────┐
                         │ API / Experience│
                         │    Layer        │
                         └────────┬────────┘
                                  │
              ┌───────────────────▼───────────────────┐
              │            commercetools               │
              │                                        │
              │ Catalog │ Pricing │ Cart │ Promotions │
              │ Orders  │ Checkout│ Inventory │ etc. │
              └───────────────────┬───────────────────┘
                                  │
                 ┌────────────────┼─────────────────┐
                 ▼                ▼                 ▼
               ERP              PIM               OMS

The important architectural property is that the storefront isn't the system of record. You can create multiple experiences over the same commerce capabilities, while allowing individual brands/regions to diverge where necessary.

commercetools explicitly supports multiple brands and stores, regional catalogs, currencies and languages, and describes its platform as API-native and modular. Its retail offering also calls out multi-brand/multi-catalog operations and a single backend for global/local experiences. commercetools commercetools

The big architectural decision

I would not create one giant "universal storefront application."

Instead, I'd establish a shared storefront platform with independently deployable storefronts:

• Shared design system
• Shared authentication/session infrastructure
• Shared observability
• Shared API/client SDKs
• Shared commerce domain services
• Shared experimentation/personalization infrastructure
• Storefront-specific composition and branding
• Region/brand-specific configuration

That gives you platform standardization without forcing every brand onto the same release cycle.

When I'd pick Salesforce instead

If your retailer is already deeply invested in Salesforce CRM, Marketing Cloud, Service Cloud, loyalty, and customer data, I'd seriously consider Salesforce Commerce Cloud.

salesforce.com

Salesforce supports headless APIs, arbitrary frontend frameworks, B2C/B2B experiences, and multiple sites/storefronts. Its documentation specifically describes configurations ranging from one site/multiple storefronts to multiple sites/multiple storefronts. Salesforce Salesforce

I'd choose it over commercetools when Salesforce ecosystem integration is a strategic requirement, rather than because its headless capabilities are inherently superior.

When I'd pick Shopify Plus

I'd pick Shopify Plus if your priority is:

"We need many stores, excellent commerce operations, fast delivery, and don't want our engineering organization to become a commerce-platform company."

That's a very legitimate choice.

But for a large retailer where engineering wants to own the experience architecture and expects extensive integration, complex pricing/catalog models, multiple business units, and potentially dozens of storefronts, I'd lean commercetools.

My recommendation

If I were the lead developer making the architectural decision, I'd rank them:

1. commercetools — best strategic fit
2. Salesforce Commerce Cloud — if Salesforce is already central
3. Shopify Plus — if operational simplicity/time-to-market dominates
4. Adobe Commerce — if Adobe is already deeply embedded
5. BigCommerce — strong but less compelling for extreme enterprise complexity

The crucial caveat: don't select the commerce platform in isolation. For a retailer of significant scale, I'd evaluate the combination of commerce engine + PIM + search + CMS + OMS + pricing/promotions + identity + CDN/edge + frontend platform. The commerce engine should be one component of the architecture, not the architecture itself.

If you give me roughly number of storefronts, countries, SKUs, order volume, B2C/B2B mix, and whether you already use Salesforce/Adobe/SAP, I can give you a much more concrete enterprise reference architecture and platform recommendation.

If I were the lead dev at a large retailer with many brands/regions/storefronts, my default choice would be commercetools—assuming the organization is genuinely ready for a composable architecture.

My ranking

Why I'd pick commercetools

The biggest reason is multi-storefront architecture without turning every new brand or country into another technology stack.

commercetools explicitly supports native multi-site deployments, allowing different storefronts to have their own catalogs/product selections, pricing, currencies, languages, inventory and promotions while sharing underlying commerce capabilities. commercetools commercetools

That's particularly attractive for a retailer where you might eventually have:

                    ┌── Brand A / US
                    ├── Brand A / CA
                    ├── Brand A / EU
                    ├── Brand B / US
Commerce Platform ──┼── Brand B / EU
                    ├── Outlet / US
                    ├── Marketplace
                    ├── Mobile app
                    └── In-store / kiosk

Rather than:

Storefront A → Commerce Instance A
Storefront B → Commerce Instance B
Storefront C → Commerce Instance C
...

You get a shared commerce capability layer with independently deployable experience layers.

commercetools is also deliberately API-first and modular, so search, CMS, personalization, payments, tax, OMS, etc. can be selected independently rather than forcing the entire retailer onto one vendor's stack. commercetools commercetools

Where Salesforce could beat it

I'd seriously consider Salesforce Commerce Cloud if the retailer already has substantial Salesforce investment.

Salesforce's current Composable Storefront architecture separates the frontend from commerce logic and provides PWA Kit + Managed Runtime, while its APIs cover products, catalogs, baskets, promotions, inventory, shipping and billing. It also supports multiple storefronts/sites. Developer Salesforce

That's a compelling choice if your architecture looks like:

Salesforce CRM + Marketing + Service + Commerce + customer data

rather than a best-of-breed composable stack.

Salesforce also has a particularly attractive migration story: its current architecture supports hybrid storefronts, so you don't necessarily have to headless-rebuild the entire retailer at once. Salesforce

The architecture I'd aim for

For a large retailer, I wouldn't make the commerce platform responsible for everything:

                    EXPERIENCE LAYER
       ┌──────────────┬──────────────┬──────────────┐
       │ Brand A Web  │ Brand B Web  │ Mobile / App │
       └──────────────┴──────────────┴──────────────┘
                          │
                    API / BFF Layer
                          │
       ┌──────────────────┼───────────────────┐
       │                  │                   │
  Commerce           CMS / Content       Search / PLP
(commercetools)          │                (Algolia/etc.)
       │                  │
       ├── Catalog        │
       ├── Pricing        │
       ├── Cart           │
       ├── Promotions     │
       ├── Inventory      │
       └── Checkout       │
                          │
       ┌──────────────────┼───────────────────┐
       │                  │                   │
      PIM                OMS                 ERP
       │                  │                   │
   Product data       Fulfillment          Finance

The key architectural decision is to make storefront identity/configuration a first-class concept rather than cloning an application for every brand.

I'd want each storefront to specify things like:

• catalog/product assortment
• price books
• currency
• locale
• market
• promotions
• fulfillment options
• CMS space
• feature flags
• theme/design system
• payment methods
• tax configuration

while the underlying commerce capabilities remain shared.

One important caveat

I wouldn't choose commercetools simply because "headless = modern." Composable commerce transfers significant responsibility to your engineering organization. The platform gives you flexibility, but you now own the integration architecture.

If your team isn't equipped to operate that complexity, Salesforce or Shopify Plus can produce a better business outcome despite being less architecturally pure.

So my decision rule would be:

Strong engineering organization + many differentiated storefronts + long-term need for flexibility → commercetools.
Salesforce-heavy enterprise → Salesforce Commerce Cloud.
Standardized stores + prioritize speed/operational simplicity → Shopify Plus.
SAP-centric enterprise → SAP Commerce Cloud.

For the specific scenario you described—large retailer + headless + many storefronts—I'd put commercetools at #1, with Salesforce as the strongest alternative. commercetools commercetools

If you're evaluating this for an actual enterprise RFP, the next step I'd recommend is comparing commercetools vs Salesforce vs Shopify Plus across multi-tenancy, catalog/pricing, checkout, promotions, PIM/OMS integration, deployment model, developer experience, TCO, and peak-event scalability rather than comparing generic "headless" feature lists.

commercetools is also deliberately API-first and modular, so search, CMS, personalization, payments, tax, OMS, etc. can be selected independently rather than forcing the entire retailer onto one vendor's stack. commercetools commercetools

Where Salesforce could beat it

I'd seriously consider Salesforce Commerce Cloud if the retailer already has substantial Salesforce investment.

Salesforce's current Composable Storefront architecture separates the frontend from commerce logic and provides PWA Kit + Managed Runtime, while its APIs cover products, catalogs, baskets, promotions, inventory, shipping and billing. It also supports multiple storefronts/sites. Developer Salesforce

That's a compelling choice if your architecture looks like:

Salesforce CRM + Marketing + Service + Commerce + customer data

rather than a best-of-breed composable stack.

Salesforce also has a particularly attractive migration story: its current architecture supports hybrid storefronts, so you don't necessarily have to headless-rebuild the entire retailer at once. Salesforce

The architecture I'd aim for

For a large retailer, I wouldn't make the commerce platform responsible for everything:

                    EXPERIENCE LAYER
       ┌──────────────┬──────────────┬──────────────┐
       │ Brand A Web  │ Brand B Web  │ Mobile / App │
       └──────────────┴──────────────┴──────────────┘
                          │
                    API / BFF Layer
                          │
       ┌──────────────────┼───────────────────┐
       │                  │                   │
  Commerce           CMS / Content       Search / PLP
(commercetools)          │                (Algolia/etc.)
       │                  │
       ├── Catalog        │
       ├── Pricing        │
       ├── Cart           │
       ├── Promotions     │
       ├── Inventory      │
       └── Checkout       │
                          │
       ┌──────────────────┼───────────────────┐
       │                  │                   │
      PIM                OMS                 ERP
       │                  │                   │
   Product data       Fulfillment          Finance

The key architectural decision is to make storefront identity/configuration a first-class concept rather than cloning an application for every brand.

I'd want each storefront to specify things like:

• catalog/product assortment
• price books
• currency
• locale
• market
• promotions
• fulfillment options
• CMS space
• feature flags
• theme/design system
• payment methods
• tax configuration

while the underlying commerce capabilities remain shared.

One important caveat

I wouldn't choose commercetools simply because "headless = modern." Composable commerce transfers significant responsibility to your engineering organization. The platform gives you flexibility, but you now own the integration architecture.

If your team isn't equipped to operate that complexity, Salesforce or Shopify Plus can produce a better business outcome despite being less architecturally pure.

So my decision rule would be:

Strong engineering organization + many differentiated storefronts + long-term need for flexibility → commercetools.
Salesforce-heavy enterprise → Salesforce Commerce Cloud.
Standardized stores + prioritize speed/operational simplicity → Shopify Plus.
SAP-centric enterprise → SAP Commerce Cloud.

For the specific scenario you described—large retailer + headless + many storefronts—I'd put commercetools at #1, with Salesforce as the strongest alternative.

For a large retailer with many storefronts, my default recommendation would be commercetools—unless your overriding priority is minimizing engineering and operational complexity, in which case BigCommerce or Shopify Enterprise can be better fits.

My ranking

Why I'd choose commercetools

For a retailer operating dozens or hundreds of experiences, I'd want the commerce platform to be a shared commerce capability layer, rather than treating each storefront as a separate ecommerce application.

commercetools is particularly suited to that model: it's API-first and modular, with commerce capabilities exposed independently, and explicitly targets enterprise-scale multi-channel architectures. It currently reports supporting 550+ enterprises, 140M+ SKUs and 700M+ annualized orders. commercetools.com

I'd architect it roughly like:

                    ┌─────────────────────────┐
                    │       Experience         │
                    │                          │
                    │ Brand A  Brand B  Brand C│
                    │ Web      Web      Web     │
                    │ Mobile   Mobile   Mobile  │
                    └────────────┬────────────┘
                                 │
                         Experience APIs
                                 │
              ┌──────────────────▼──────────────────┐
              │          Commerce Platform           │
              │                                      │
              │ Catalog │ Pricing │ Cart │ Checkout │
              │ Customer│ Orders  │ Promotions       │
              └──────────────────┬──────────────────┘
                                 │
              ┌──────────────────▼──────────────────┐
              │        Enterprise Integration       │
              │                                    │
              │ PIM │ ERP │ OMS │ WMS │ CRM │ Tax  │
              └────────────────────────────────────┘

The key is not creating a separate commerce backend per storefront. Instead, establish common commerce capabilities and let each brand/region/channel configure what differs.

Where BigCommerce gets interesting

I'd seriously evaluate BigCommerce if your organization wants a less ambitious composable architecture.

Its Multi-Storefront model is specifically designed to manage multiple brands, regions and customer segments from one backend, with distinct pricing, domains, catalogs and experiences. Its APIs also support custom headless storefronts. www.bigcommerce.com

That's a very attractive proposition for a retailer where:

"We need 40 storefronts, but we don't want 40 commerce implementations."

BigCommerce also has Catalyst, its Next.js/React headless framework, so your team can standardize the frontend technology while retaining a SaaS commerce backend. www.bigcommerce.com

If I were optimizing for total engineering effort rather than architectural purity, I'd probably pick BigCommerce.

Shopify Enterprise

Shopify is compelling if the organization is primarily DTC and wants the platform to absorb as much operational complexity as possible. Shopify supports headless storefronts through its API layer and offers enterprise support and high-scale infrastructure. www.shopify.com

The tradeoff is that I'd be more cautious about making Shopify the foundational commerce abstraction for a retailer with unusually complex pricing, catalog, fulfillment, B2B, organizational, or multi-brand requirements.

The decision I'd make as lead dev

I'd use this rule:

• Complex enterprise retailer + many brands/channels + significant internal engineering → commercetools
• Many storefronts + conventional retail requirements + want SaaS simplicity → BigCommerce
• DTC-first + speed/operational simplicity are paramount → Shopify
• Need extreme customization and are willing to own more infrastructure → Saleor/Medusa/Vendure
• Existing major Adobe investment → Adobe Commerce

One important architectural point: don't let "headless" become the architecture. Headless is just the separation of presentation from commerce. For a large retailer, I'd spend considerably more design effort on catalog ownership, pricing, inventory, customer identity, order orchestration, eventing, search, CMS, observability, and tenant/storefront configuration than on choosing Next.js versus another frontend framework.

If you tell me roughly how many storefronts/brands, countries, SKUs, annual orders, B2B vs B2C, and whether you already have an ERP/OMS/PIM, I can give you a much more opinionated platform choice and reference architecture.

If I were the lead dev at a large retailer with many storefronts, my default choice would be commercetools—unless your organization is already deeply standardized on Salesforce.

My ranking

Why I'd pick commercetools

For a large retailer, I'd optimize less for "which platform has the most ecommerce features?" and more for how cleanly can we operate 20–100+ storefronts without creating a giant distributed monolith.

commercetools is particularly strong here because it is designed around API-first, modular commerce, with support for multiple brands/stores, international expansion, and integration with external ERP/CRM/PIM/CMS systems. Its current platform is explicitly positioned for enterprise-scale workloads and complex multi-channel environments. commercetools.com

I'd architect it roughly as:

                    ┌── Storefront A
                    ├── Storefront B
CDN / Edge ─────────┼── Storefront C
                    ├── Mobile Apps
                    └── In-store / Other Channels
                             │
                       API / Experience Layer
                             │
        ┌────────────────────┼─────────────────────┐
        │                    │                     │
    Commerce            Search/PIM             CMS
 commercetools          Algolia/etc.         Contentful/etc.
        │
 ┌──────┼─────────┬───────────┐
 │      │         │           │
Cart  Pricing  Promotions  Checkout
 │
OMS / ERP / Inventory / Payments / Tax

The important part is that storefronts aren't individual ecommerce applications. They're thin experiences consuming shared commerce capabilities.

When I'd choose Salesforce instead

If the retailer already has substantial Salesforce investment—CRM, Marketing Cloud, customer data, service, etc.—I'd seriously consider Salesforce Commerce Cloud.

Its current Composable Storefront uses a React-based PWA Kit plus Managed Runtime, with Commerce APIs underneath, and supports combining Salesforce capabilities with third-party services. developer.salesforce.com

That's especially attractive if you want:

• shared customer identity/data
• Salesforce CRM integration
• B2B + B2C
• many regional/brand storefronts
• a managed enterprise platform
• less infrastructure for your team to own

Salesforce also supports hybrid implementations, which is valuable if you're migrating a huge retailer incrementally rather than doing a "big bang" replatform. developer.salesforce.com

Shopify Plus would be my "simplify everything" choice

Shopify Plus becomes compelling if the primary objective is getting dozens of storefronts operating with minimal platform engineering.

Shopify Plus supports expansion stores under a centralized organization, including separate stores for international markets, product lines, B2B, employees, and other purposes. help.shopify.com

The tradeoff is architectural freedom: I'd be more comfortable with Shopify if the retailer's differentiating technology is primarily above the commerce platform rather than deeply embedded in custom commerce logic.

The decision I'd make

If I'm choosing purely on architecture:

commercetools + Next.js/React storefronts + headless CMS + dedicated PIM + search + OMS + enterprise integration layer.

If we're already a Salesforce shop:

Salesforce Commerce Cloud + Composable Storefront.

If business wants the lowest operational complexity and fastest rollout:

Shopify Plus.

One important caveat: for a large retailer, I'd make the storefront model a first-class architectural decision before selecting the commerce vendor. You want a platform where adding Store #47 is largely configuration/data/branding, not another codebase and another deployment pipeline.

If you tell me roughly how many storefronts, countries, brands, SKUs, annual orders, and whether you need B2B + B2C, I can give you a much more opinionated architecture and a commercetools vs Salesforce vs Shopify decision matrix.

If I were the lead dev at a large retailer with many storefronts, my default recommendation would be commercetools—especially if you're genuinely committing to a composable/headless architecture rather than just wanting a custom frontend.

My shortlist

Why I'd lean commercetools

For a retailer with, say, 10–100+ storefronts across brands, countries, channels, or business units, I'd want the commerce backend to be a relatively clean platform service rather than something each storefront becomes tightly coupled to.

commercetools is explicitly designed around API-first, composable commerce, with support for multiple brands/stores, international expansion, web/mobile/in-store channels, and integration with ERP/CRM and other systems. commercetools.com

The architecture I'd aim for is roughly:

                         ┌──────────────────────┐
                         │     Experience       │
                         │       Layer          │
                         └──────────┬───────────┘
                                    │
        ┌──────────────┬────────────┼─────────────┬──────────────┐
        ▼              ▼            ▼             ▼              ▼
     Brand A        Brand B      Brand C       Mobile        In-store
    storefront     storefront   storefront       app          kiosk
        │              │            │             │              │
        └──────────────┴────────────┴─────────────┴──────────────┘
                                    │
                              API / BFF layer
                                    │
                 ┌──────────────────┼──────────────────┐
                 ▼                  ▼                  ▼
          ┌─────────────┐   ┌─────────────┐   ┌─────────────┐
          │ commercetools│   │    CMS      │   │   Search    │
          │   Commerce   │   │             │   │             │
          └─────────────┘   └─────────────┘   └─────────────┘
                 │
       ┌─────────┼─────────┬──────────────┐
       ▼         ▼         ▼              ▼
      ERP       OMS       PIM          Pricing/Promo

The important architectural decision is not to make each storefront its own application/platform. Instead, I'd build a shared retail experience platform with:

• shared design system/components
• shared frontend infrastructure
• tenant/store configuration
• centralized identity
• centralized observability
• shared commerce APIs
• per-store catalog/price/promotion rules
• per-market localization/tax/payment configuration
• independently deployable storefronts

That lets Brand A and Brand B have radically different experiences without duplicating the underlying commerce capabilities.

When I'd choose Salesforce instead

I'd put Salesforce Commerce Cloud at #1 if your retailer already has substantial investment in Salesforce—particularly CRM, customer data, loyalty, service, or Salesforce Order Management.

Salesforce's current headless architecture supports Commerce APIs, a React-based PWA Kit, and Managed Runtime. Its platform also explicitly supports multiple sites from a shared codebase, including different domains, locales, and catalogs. developer.salesforce.com

So if the organization says:

"We want headless, but we also want Salesforce to remain the strategic customer/commerce platform."

I'd choose Salesforce over commercetools.

The bigger architectural question

I wouldn't select the platform based primarily on "does it support headless?"

At your scale, I'd score vendors on:

1. Multi-brand/multi-market modeling
2. Catalog and price-list isolation/sharing
3. Promotion complexity
4. Inventory/OMS integration
5. API quality and rate limits
6. Deployment independence
7. Localization/currency/tax
8. B2B requirements, if applicable
9. Operational resilience during peak events
10. Ability to avoid vendor lock-in
11. Total cost at your actual order/API volume
12. How easily another storefront can be launched

That last one is particularly important. I'd want the marginal cost of launching storefront #37 to be mostly configuration and content, not another 12-month engineering project.

My recommendation

If you're a technically mature retailer building for the next 5–10 years:

commercetools + Next.js/React storefront platform + enterprise CMS + dedicated search + PIM + OMS + API/BFF layer

I'd favor that over putting all commerce, CMS, frontend, search, and customer experience into one vendor.

If you're already heavily invested in Salesforce, I'd instead go:

Salesforce Commerce Cloud + Composable Storefront + shared frontend platform

Salesforce specifically supports decoupled storefronts and allows third-party services such as search and CMS to be composed around its Commerce APIs. developer.salesforce.com

One caveat: composable gives you much more architectural freedom, but it also means you own the integration architecture. That's the tradeoff I'd take at a large retailer with a strong engineering organization; it may be unnecessary complexity for a smaller team. www.salesforce.com

If you tell me roughly number of storefronts, countries, annual orders/GMV, B2C vs B2B, existing ERP/OMS/PIM/CMS, and whether Salesforce/Adobe/Shopify is already entrenched, I can give you a much more concrete platform + reference architecture recommendation.

For a large retailer with many storefronts, I would not start with “which commerce platform has the most features?” I would start with which platform gives you the right operating model for dozens of brands, regions, channels, and teams.

For that scenario, my shortlist would be:

www.ciopages.comcommercetools.com

My default recommendation: commercetools + composable stack

For a retailer running many storefronts (for example: multiple brands, countries, banners, marketplaces, mobile apps, kiosks), I would lean toward:

• Commerce engine: commercetools
• Frontend: React/Next.js or similar
• CMS: headless CMS (Contentful, Sanity, Adobe Experience Manager, etc.)
• Search: dedicated search engine (Algolia, Coveo, Elasticsearch/OpenSearch)
• Pricing/promotions: commerce services + specialized services where needed
• OMS: existing enterprise OMS or best-of-breed OMS
• Identity/CDP: enterprise identity + customer data platform
• API gateway/event backbone: to decouple storefronts from backend systems

The reason: you want one commerce capability layer powering many experiences, not many storefronts becoming many forks of the same application. A MACH-style architecture (microservices, API-first, cloud-native, headless) is designed around that model. commercetools.com

A good target architecture looks like:

                 Storefronts
     --------------------------------
     Web A     Web B     Mobile     POS
       |         |         |         |
       +---------+---------+---------+
                    |
             Experience APIs
                    |
       --------------------------------
       |        Commerce Services     |
       |                              |
       | Catalog | Cart | Checkout    |
       | Pricing | Promo | Customer   |
       --------------------------------
                    |
       --------------------------------
       | ERP | OMS | PIM | Tax | ERP |
       --------------------------------

Where I would choose something else

Choose Salesforce Commerce Cloud if:

• Your enterprise already runs heavily on Salesforce CRM, Service Cloud, Marketing Cloud, or Data Cloud.
• Customer identity, personalization, and sales/service integration are more important than maximum backend modularity.
• You want a supported enterprise path rather than assembling many components.

Salesforce supports headless/composable storefront approaches through its commerce APIs and composable storefront tooling. www.salesforce.com

Choose Adobe Commerce if:

• You have very complex catalog rules.
• You have significant B2B workflows.
• You already have Magento expertise internally.
• You need deep customization and control.

Adobe can support headless architectures, but it originated as a more traditional commerce platform, so you need to be deliberate about how much of the stack you decouple. commercetools.comwww.salesforce.combemeir.com

Choose Shopify Plus if:

• Your priority is speed and reducing platform operations.
• Most stores are DTC.
• Your teams do not want to own a large distributed commerce platform.

Shopify has expanded its headless capabilities, but you generally accept more platform constraints compared with a pure composable approach. www.shopify.com

The questions I would ask before approving a platform

As lead dev, I would force these decisions early:

1. How many storefronts?
   • 5 brands is different from 50 regional storefronts.

2. Do they share a catalog?
   • Shared product model → composable shines.
   • Completely different businesses → simpler SaaS may win.

3. Who owns pricing?
   • Enterprise retailers often underestimate pricing complexity.

4. Do you want independent release cycles?
   • If Brand A can deploy without risking Brand B, composable architecture helps.

5. How large is the platform engineering team?
   • A composable stack is powerful, but you become responsible for integration architecture, observability, testing, and reliability.

My ranking for a large retailer with many storefronts

1. commercetools — best long-term architecture if you have the engineering maturity
2. Salesforce Commerce Cloud — best if Salesforce is the enterprise backbone
3. Adobe Commerce — best for complex commerce rules and customization
4. Shopify Plus — best when speed and simplicity beat architectural freedom

For a retailer with a serious platform engineering team, I would likely build a composable commerce platform around commercetools, with a strong internal commerce platform layer that exposes reusable capabilities to every storefront. commercetools.com

For a large retailer with many storefronts, I would generally bias toward a true composable/headless commerce platform, but the best choice depends on whether your priority is architectural freedom, operational simplicity, or ecosystem integration.

My shortlist would be:

My recommendation for a large retailer

If I were the lead developer designing a 10+ storefront architecture, I would likely choose:

Option A — Enterprise composable (my default recommendation)

commercetools + modern frontend stack

Example architecture:

                 Storefronts
                     |
        --------------------------------
        |        |        |             |
      Web     Mobile   Kiosk       Marketplace
        |
        v
  Experience Layer
 (Next.js / React / native apps)
        |
        v
  Commerce Platform
 (commercetools)
        |
 ---------------------------------
 |       |        |        |       |
PIM    OMS     Search   CMS    Payments

You get:

• One commerce backend powering many brands
• Independent storefront releases
• Regionalization
• Shared inventory/pricing/promotions logic
• Easier experimentation
• Ability to replace CMS/search/PIM without replatforming

This aligns well with MACH-style architecture (Microservices, API-first, Cloud-native, Headless). commercetools.com

Option B — If your company is Salesforce-heavy

Choose Salesforce Commerce Cloud.

I would not underestimate the value of having:

• CRM identity
• loyalty
• customer service
• marketing automation
• commerce

all connected. For many retailers, that operational advantage outweighs architectural purity. www.salesforce.com

Option C — If you have a very complex merchandising organization

Adobe Commerce can still be the right call, especially where:

• catalog rules are extremely complicated
• B2B and B2C coexist
• ERP integration dominates the problem
• merchandising teams need mature workflows

experienceleague.adobe.com

The architecture matters more than the vendor

For many storefronts, I would avoid the common mistake of making the commerce platform also be:

• CMS
• search engine
• recommendation engine
• customer data platform
• experimentation platform
• frontend framework

A scalable retailer architecture usually looks more like:

• Commerce core: commercetools / Salesforce / Adobe
• Frontend: React/Next.js, native apps, in-store apps
• CMS: Contentful, Adobe Experience Manager, Sanity, etc.
• Search: Algolia, Elasticsearch/OpenSearch, Coveo, etc.
• PIM: Akeneo, Salsify, inRiver, etc.
• OMS: dedicated order orchestration
• CDP/CRM: customer intelligence layer

The questions I’d ask before selecting

1. How many storefronts?
   • 5 brands?
   • 50 countries?
   • thousands of dealer portals?

2. Do storefronts share:
   • catalog?
   • inventory?
   • pricing?
   • promotions?
   • customer accounts?

3. Is the business trying to differentiate digitally, or mainly digitize existing retail?

4. How large is the platform engineering team?
   • 5 engineers → avoid over-composable
   • 20+ engineers → composable becomes much more attractive

5. Are you replacing an existing platform?
   • SAP Hybris?
   • Magento?
   • Salesforce?
   • custom commerce?

For a large retailer with a strong engineering organization and many storefronts, my first evaluation would be commercetools vs Salesforce Commerce Cloud, with Adobe Commerce as the contender if catalog/B2B complexity is the dominant requirement. www.ciopages.com

If I were the lead dev at a large retailer with many storefronts, my default choice would be commercetools—unless your organization strongly prioritizes speed-to-market and minimizing engineering ownership, in which case I'd choose Shopify Plus.

My ranking

Why I'd pick commercetools

For a large retailer, the important question isn't merely "can it do headless?" It's how well does the commerce domain model map to dozens of storefronts, brands, countries, catalogs, pricing regimes, inventories and customer experiences?

commercetools is designed around exactly that composable model. Its Stores and Channels allow different shopping contexts to share resources while maintaining distinct experiences, pricing and inventory contexts. docs.commercetools.com

It also gives you a genuinely API-first architecture rather than treating headless as an alternative presentation layer. The platform exposes commerce capabilities as APIs and is explicitly designed around cloud-native, modular, MACH principles. commercetools.com

For your architecture, I'd roughly envision:

Storefronts
→ Next.js / React
→ shared design system + storefront platform
→ API gateway / BFF layer
→ commercetools
→ PIM / CMS / search / pricing / promotions / OMS / payments
→ ERP, WMS, CRM, loyalty, etc.

That gives you a common commerce core while allowing Store A, Store B, international Store C, mobile, kiosks, or future channels to evolve independently.

Where Shopify Plus wins

I'd seriously consider Shopify Plus if your primary goal is:

"We need 20–100 storefronts, but we don't want to become a commerce-platform engineering company."

Shopify supports multiple custom storefronts connected to a common commerce backend, and its enterprise offering supports headless, traditional, and modular implementations. www.shopify.com

That's a huge advantage operationally. You get mature checkout, payments, merchandising, admin tooling, ecosystem integrations, etc., without your team having to assemble as much of the commerce infrastructure.

The tradeoff is architectural control. If you're a sophisticated retailer with unusual pricing, promotions, inventory allocation, fulfillment, B2B/B2C convergence, multiple brands, or significant domain-specific commerce logic, commercetools gives your engineering organization more room to model the business rather than adapt the business to the platform.

BigCommerce is the interesting middle option

BigCommerce Enterprise deserves a serious POC. Its current offering combines headless APIs with native multi-storefront management: different brands/regions can have distinct catalogs, currencies, pricing, domains, templates, etc., while being administered through one backend. www.bigcommerce.com

So I'd characterize the choices as:

• commercetools: "Commerce is a strategic technology platform; we want maximum architectural freedom."
• Shopify Plus: "Commerce is a business capability; we want the platform to handle as much as possible."
• BigCommerce: "We want headless + multi-store without taking on quite as much composable-platform complexity."

What I'd actually do

For a large retailer, I wouldn't select based on feature checklists. I'd run a 4–6 week architecture POC around the hardest workflows:

1. One shared product catalog → 5+ storefronts
2. Store-specific assortment
3. Store/country-specific pricing
4. Promotions and coupons
5. Inventory by location
6. Customer identity/account
7. Cart → checkout → payment
8. Order → OMS → fulfillment
9. Search/merchandising
10. CMS/content localization
11. Peak-event performance
12. Disaster recovery and observability
13. Developer experience and CI/CD
14. Ability to introduce a new storefront without modifying existing ones

I'd give commercetools the edge if the retailer has a sophisticated engineering organization and expects the architecture to last 7–10+ years.

I'd give Shopify Plus the edge if reducing implementation/maintenance burden is more valuable than maximum architectural control.

And I'd put BigCommerce in the POC if the business wants a strong multi-store/headless solution but considers full composability more complexity than it needs.

If you tell me roughly how many storefronts, countries, brands, SKUs, annual orders, and whether you have an existing OMS/PIM/ERP, I can give you a much more concrete architecture recommendation—including where I'd put the CMS, search, PIM, API gateway/BFF, checkout, and event bus.

If I were the lead dev making this decision for a large retailer with many storefronts, my default recommendation would be commercetools—unless your organization prioritizes speed-to-market and operational simplicity over architectural control.

My shortlist

Why I'd pick commercetools

For your particular description—large retailer + headless + many storefronts—commercetools maps unusually well to the architecture.

Its platform is API-first/headless and explicitly designed around enterprise-scale commerce. It supports multiple brands/stores and regional operations from a common platform, while allowing the experiences to remain independently developed. commercetools.com

I'd structure it roughly like:

                    ┌──────────────────────┐
                    │   CMS / DAM / PIM    │
                    └──────────┬───────────┘
                               │
       ┌───────────────────────┼───────────────────────┐
       │                       │                       │
 ┌─────▼─────┐           ┌─────▼─────┐           ┌─────▼─────┐
 │ Storefront │           │ Storefront │           │ Storefront │
 │   Brand A  │           │   Brand B  │           │   Brand C  │
 │  Next.js   │           │  Next.js   │           │  Next.js   │
 └─────┬─────┘           └─────┬─────┘           └─────┬─────┘
       │                       │                       │
       └───────────────────────┼───────────────────────┘
                               │
                    ┌──────────▼──────────┐
                    │   Commerce API      │
                    │   commercetools      │
                    └──────────┬──────────┘
                               │
          ┌────────────────────┼────────────────────┐
          │                    │                    │
        ERP                  OMS                  CRM

The important architectural advantage is that storefront boundaries don't have to become commerce-system boundaries. You can give each brand/region its own UX, deployment cadence and content while centralizing the underlying commerce capabilities.

But there's a big caveat

I'd only choose commercetools if you have a genuinely strong engineering organization.

You're buying architectural freedom, not a turnkey ecommerce application. commercetools itself describes the platform as API-first and headless, and its enterprise positioning emphasizes interoperability with ERP, CRM and other systems. commercetools.com

That means your team owns considerably more of:

• frontend architecture
• CMS/PIM integration
• search
• promotions orchestration
• identity
• observability
• integration/event architecture
• deployment infrastructure
• potentially parts of checkout and customer experience

For a large retailer with a mature platform engineering team, that's often a feature. For a team that wants the commerce vendor to solve more of the problem, it's a liability.

When I'd choose Shopify Plus instead

I'd pick Shopify Plus if the primary objective were launching many storefronts quickly with a smaller operational burden.

Shopify's current headless stack gives you the Storefront API plus Hydrogen, while keeping pricing, inventory, carts and much of the operational commerce layer in Shopify. Shopify explicitly supports multiple custom storefronts connected to the same commerce backend. www.shopify.com

So:

commercetools:

"Commerce is a platform capability that we assemble into our architecture."

Shopify Plus:

"Commerce is a managed service that our custom storefronts consume."

That's a pretty important philosophical distinction.

And BigCommerce deserves serious consideration

For a retailer with lots of brands/regions/storefronts but less appetite for building everything yourself, I'd put BigCommerce near the top of the RFP.

It's particularly interesting because multi-storefront management is a first-class concern rather than something you necessarily have to construct yourself. Current industry comparisons also highlight its combination of multi-storefront capabilities and headless flexibility. contracollective.com

My recommendation

If I were setting the architecture direction today:

1. commercetools — best strategic architecture
Choose this if you're building a long-lived enterprise commerce platform and have the engineering muscle.

2. BigCommerce — best pragmatic alternative
Choose this if multi-storefront is critical but you don't want quite as much platform engineering.

3. Shopify Plus — best velocity/operational simplicity
Choose this if getting dozens of storefronts launched and operated efficiently matters more than maximum backend flexibility.

4. Salesforce Commerce Cloud — choose primarily for Salesforce ecosystem alignment
Particularly compelling if CRM, Marketing Cloud, Service Cloud, etc. are already deeply embedded.

5. Adobe Commerce — only if its unusually deep customization is specifically required.

One architectural point I'd strongly recommend regardless of vendor: don't build "one frontend codebase with 30 themes." Treat storefronts as independently deployable experiences sharing a common commerce/domain layer. Shopify's own enterprise architecture guidance makes a similar case for separate frontends with shared backend services, because it prevents one audience's release cycle from coupling to another's. www.shopify.com

If you tell me roughly GMV, SKU count, number of brands/storefronts, B2C vs B2B, countries, and whether you already run SAP/Salesforce/Adobe, I can give you a much more opinionated architecture recommendation—including commercetools vs BigCommerce vs Shopify Plus, estimated engineering complexity, and what I'd put in the RFP.

If I were the lead dev at a large retailer with many storefronts, my default choice would be commercetools—unless your organization already has a strong Shopify or Salesforce footprint.

My ranking

Why I'd pick commercetools

For a retailer with, say, 20 brands × 15 countries × multiple channels, I would want the commerce platform to behave like a central commerce engine, not like a collection of stores.

commercetools is explicitly API-first/headless and models Stores and Channels as separate commerce contexts. That lets you represent different storefronts, pricing contexts, inventory sources, and customer experiences without turning every storefront into a separate application/platform instance. docs.commercetools.com

I'd structure it roughly like:

                    ┌───────────────┐
                    │  CMS / PIM    │
                    └───────┬───────┘
                            │
              ┌─────────────▼─────────────┐
              │     Commerce API Layer    │
              │       commercetools       │
              └─────────────┬─────────────┘
                            │
       ┌────────────────────┼────────────────────┐
       ▼                    ▼                    ▼
  Brand A Store        Brand B Store        Brand C Store
  US / EU / CA         US / EU / APAC       US / EU
       │                    │                    │
       └───────────────┬────┴────────────────────┘
                       ▼
                Shared services
          ┌────────┬────────┬─────────┐
          │  OMS   │ Search │ Pricing │
          │  PIM   │  CMS   │ Loyalty │
          └────────┴────────┴─────────┘

The important distinction is that headless shouldn't mean "build everything yourself." The platform should own difficult commerce primitives—cart, pricing, promotions, orders, inventory integration, checkout, etc.—while your team owns the differentiated customer experience. Shopify's own 2026 guidance makes essentially this distinction: composable architecture is valuable when it removes a real constraint, but it also increases integration and operational burden. www.shopify.com

When I would choose something else

Choose BigCommerce if your primary requirement is many independently branded storefronts with centralized administration, but you don't want to staff a large composable-commerce engineering organization. Its current platform explicitly supports multi-storefront configurations with distinct look/feel/pricing and provides GraphQL plus Catalyst/Next.js for headless builds. docs.bigcommerce.com

Choose Shopify Plus if the organization values speed, ecosystem, and operational simplicity over maximum architectural freedom. Shopify's Storefront API supports multiple custom frontends against the commerce backend, and Hydrogen provides a relatively opinionated headless path. www.shopify.com

Choose Salesforce Commerce Cloud if Salesforce CRM/Marketing/Service is already the strategic center of gravity and the integration benefits outweigh the additional platform complexity.

The bigger architectural decision

As lead dev, I'd actually avoid making the decision simply "which headless platform?"

I'd make the decision:

What should be centralized, and what should be independently deployable?

For a large retailer, I'd generally centralize:

• Product/catalog master data
• Pricing and promotions
• Cart/checkout
• Orders
• Customer identity
• Inventory/availability integration
• Tax/payment orchestration

And make these independently replaceable:

• Storefront frontend
• CMS
• Search
• Recommendations
• Personalization
• Reviews
• Loyalty
• Content/experience orchestration

That gives you a composable commerce architecture without turning the company into a distributed-systems research project.

Bottom line: if you're genuinely a large retailer with a capable engineering organization and expect lots of brands, countries, channels, and differentiated experiences, I'd shortlist commercetools first, BigCommerce second, Shopify Plus third. The more your requirements look like "20 largely independent storefronts sharing a commerce core," the more strongly I'd lean commercetools. docs.commercetools.com

If I were the lead developer at a large retailer with many storefronts, my default recommendation would be commercetools—unless your primary goal is minimizing engineering/operational complexity, in which case Shopify Plus deserves serious consideration.

My shortlist

Why I'd pick commercetools

For your particular architecture—many storefronts rather than just one headless site—I'd optimize for having a single commerce capability layer underneath a large number of independently deployable experiences.

commercetools is particularly strong here because it's genuinely API-first and composable, rather than simply putting a custom frontend in front of a conventional commerce application. Its platform is designed around exposing commerce capabilities to different channels, and the vendor currently positions Sphere for B2C, B2B, B2B2C and D2C use cases from a unified platform. commercetools.com

I'd architect roughly like this:

                    ┌── Storefront A / Brand A
                    ├── Storefront B / Brand B
                    ├── Storefront C / Brand C
                    ├── Mobile App
                    ├── Marketplace
                    ├── In-store / Kiosk
                    └── Future channels
                              │
                         BFF / API
                              │
                 ┌────────────┴────────────┐
                 │      commercetools      │
                 │                         │
                 │ Catalog / Pricing       │
                 │ Cart / Checkout         │
                 │ Promotions              │
                 │ Orders                  │
                 │ Customers               │
                 └────────────┬────────────┘
                              │
       ┌──────────────┬───────┼────────┬──────────────┐
       ↓              ↓       ↓        ↓              ↓
      PIM            OMS     ERP      Search         CMS

The important architectural distinction is that headless ≠ composable. Headless decouples presentation from commerce; composable goes further by allowing commerce capabilities themselves to be assembled independently. commercetools.com

That distinction becomes valuable when you have, say, 20 brands × 10 countries × web/mobile/in-store channels and don't want every storefront team coupled to one giant commerce application.

But I'd seriously consider Shopify Plus if...

Your business is more like:

• lots of storefronts/brands
• conventional retail commerce requirements
• strong need for operational simplicity
• relatively standard checkout/order workflows
• smaller platform engineering organization
• desire to launch new storefronts quickly

Shopify Plus now supports custom/headless storefronts through its API layer and explicitly supports multiple online stores; its current Plus offering says stores can be unlimited, with expansion-store economics depending on the contract. www.shopify.com

That makes Shopify an interesting "buy the commodity, build the differentiation" strategy. I'd let Shopify own the transactional core and put your engineering effort into the experience, orchestration, integrations, personalization, and differentiated retail capabilities. Shopify itself describes this selective-composability model as one of the strengths of its platform. www.shopify.com

The decision I'd make

Choose commercetools if:

• commerce is becoming a strategic technology platform
• you have a substantial platform engineering team
• different brands/regions have materially different commerce rules
• you need freedom to change CMS/search/PIM/OMS/etc.
• you're expecting lots of non-web channels
• avoiding vendor lock-in is strategically important

Choose Shopify Plus if:

• you want the fastest route to reliable enterprise commerce
• most storefronts share conventional commerce behavior
• your differentiation is primarily frontend/customer experience
• you don't want your engineering organization operating commerce infrastructure
• reducing TCO and operational complexity matters more than maximum architectural freedom

The big trap I'd avoid is choosing composable simply because you're a large retailer. Composable architecture buys tremendous flexibility, but it also buys integration work, platform ownership, observability requirements, governance, and more things your team has to operate. Even Shopify's own current guidance makes essentially this point. www.shopify.com

My ranking for your stated scenario:
1. commercetools → best architectural fit
2. Shopify Plus → best operational/TCO fit
3. Adobe Commerce → compelling if Adobe/legacy ecosystem drives the decision
4. Salesforce Commerce Cloud → compelling if Salesforce is your enterprise backbone
5. VTEX → worth evaluating for sophisticated omnichannel retail

If you tell me roughly number of storefronts/brands, countries, annual orders, B2C vs B2B, existing ERP/PIM/OMS, and size of your engineering team, I can narrow this to a concrete target architecture and a commercetools vs Shopify Plus decision matrix.

For a large retailer with many storefronts, I would not choose based on “best headless platform” alone. I’d choose based on the operating model you want: how many brands, regions, channels, catalogs, teams, and integrations you need to support.

For a true enterprise multi-storefront architecture, my shortlist would be:

vendure.io

My default recommendation for a large retailer

I would probably build around:

commercetools + Next.js storefront layer + headless CMS + dedicated search + event-driven integration layer

Example architecture:

                    CDN / Edge
                        |
              Next.js Storefronts
        /          |          |          \
   Brand A     Brand B    Mobile App   In-store
        \          |          |          /
              Experience APIs
                    |
            Commerce Platform
              (commercetools)
                    |
    ---------------------------------
    |       |        |       |       |
 Catalog  Cart   Pricing  Orders  Inventory
    |
 ERP / OMS / PIM / CRM / Loyalty

Why:

• One commerce core, many experiences
• Each storefront can have its own UX, branding, and release cadence
• Shared customer, inventory, pricing, promotions, and order models
• Easier expansion into mobile, marketplaces, kiosks, and future channels
• Less coupling between frontend teams and commerce backend teams

A composable architecture is not automatically better; it increases operational responsibility. The biggest failures I see are not platform failures—they are teams creating five different versions of product, customer, pricing, and inventory data. A successful composable stack needs strong ownership of shared data models and APIs. www.shopify.com

When I would pick Shopify instead

For a retailer with:

• 10–50 storefronts
• mostly B2C
• rapid seasonal launches
• strong merchandising teams
• less need for deeply customized pricing/order workflows

…I would seriously consider Shopify Plus + Storefront API.

You get:

• excellent checkout
• mature operational tooling
• faster store launches
• less platform engineering burden

The tradeoff is that you accept more platform constraints than with a true composable engine. Shopify has increasingly supported headless architectures through APIs and its Hydrogen/Oxygen stack, making it a viable enterprise option. www.shopify.com

Architecture decisions I would insist on regardless of platform

For many storefronts, I would avoid putting everything into the commerce platform. I would separate:

Commerce engine

• products
• carts
• checkout
• orders
• pricing rules

PIM

• product information
• attributes
• localization

CMS

• editorial content
• landing pages
• campaigns

Search

• merchandising
• autocomplete
• ranking

Customer platform

• identity
• loyalty
• personalization

Integration layer

• ERP
• OMS
• warehouse
• tax
• payments

My ranking for a “large retailer lead developer” scenario

1. commercetools — if you truly want a multi-brand, multi-region commerce platform for the next decade
2. Shopify Plus headless — if speed and operational simplicity matter more than maximum flexibility
3. Adobe Commerce — if you have complex enterprise commerce needs and Adobe investment
4. Salesforce Commerce Cloud — if Salesforce is already your enterprise backbone
5. SAP Commerce Cloud — if SAP drives your architecture

The key question I would ask before selecting: How many storefronts, brands, countries, catalogs, and fulfillment models do you expect in 5 years? A retailer with 5 storefronts and one catalog should not build the same architecture as one with 200 storefronts across 40 countries.

For a large retailer with many storefronts, I’d shortlist commercetools, BigCommerce, and Shopify Plus—but my default recommendation would be commercetools if your organization genuinely has enterprise-scale engineering capabilities.

My ranking

1. commercetools — my pick for a true enterprise platform

commercetools is particularly compelling if you're building a shared commerce platform underneath dozens of brands, countries, channels, or customer experiences.

Its API-first/headless model lets you treat commerce capabilities—catalog, pricing, carts, orders, etc.—as services rather than tying your architecture to a particular storefront. commercetools currently positions its platform for very high-scale enterprise workloads, including claims of 100k orders/minute and sub-60ms average response times. commercetools.com

I'd choose it when you have:

• Many brands/business units
• Complex pricing and promotions
• Multiple countries/currencies
• B2C + B2B
• Significant ERP/PIM/OMS integration
• Native apps, kiosks, marketplaces, etc.
• A strong internal platform engineering team
• A desire to avoid rebuilding the commerce layer when the frontend architecture changes

The downside is important: you are buying architectural freedom, not simplicity. Your team owns substantially more integration, orchestration, observability, and platform engineering.

2. BigCommerce — probably the smartest practical choice

BigCommerce deserves serious consideration for your particular requirement.

Its Multi-Storefront capability is explicitly designed for multiple brands, regions, and customer segments while maintaining one backend. It supports distinct domains, currencies, catalogs/categories, customer groups and pricing, while centralizing management. www.bigcommerce.com

More importantly for a lead developer, BigCommerce gives you a relatively clean middle ground:

Commerce SaaS → APIs → your storefront platform

Its headless stack supports REST/GraphQL APIs and modern frameworks such as Next.js, while Catalyst provides a Next.js/React reference architecture. www.bigcommerce.com

I'd lean BigCommerce over commercetools if the goal is:

"We want many independently branded storefronts, but we don't want to build an entire commerce platform ourselves."

3. Shopify Plus — strongest if business velocity matters most

Shopify Plus is excellent if your organization values operational simplicity, ecosystem maturity, and speed of execution over maximum architectural control.

Shopify Plus supports expansion stores under a centralized organization, and its headless stack supports up to 25 custom React-based storefronts using Hydrogen/Oxygen under the Plus plan. help.shopify.com

The architectural caveat is that Shopify's model tends to work best when your stores can operate as relatively independent commerce domains. Shopify itself notes that expansion stores have their own separate data, settings, and configurations despite centralized organization management. help.shopify.com

So if you have 30 brands that mostly behave like separate businesses, Shopify Plus can be fantastic.

If you have 30 storefronts that you want to behave like a single enterprise commerce platform, I'd look harder at commercetools.

What I'd build

For a retailer of significant scale, I'd avoid making the commerce vendor the center of the entire architecture.

I'd structure it roughly like:

                    ┌─────────────────────┐
                    │   Storefronts       │
                    │                     │
                    │ Brand A   Brand B   │
                    │ Brand C   Region EU  │
                    │ Mobile    Kiosks     │
                    └──────────┬──────────┘
                               │
                         Experience API
                               │
              ┌────────────────┴────────────────┐
              │                                 │
        ┌─────▼─────┐                     ┌─────▼─────┐
        │ Commerce  │                     │   CMS/DXP │
        │ Platform  │                     │           │
        └─────┬─────┘                     └───────────┘
              │
       ┌──────┼────────┬──────────┐
       ▼      ▼        ▼          ▼
      PIM    OMS      ERP       Search
       │      │        │          │
       └──────┴────────┴──────────┘

The key architectural decision I'd make is to establish a canonical internal domain/API layer rather than letting every storefront talk directly to 15 backend systems.

That gives you:

Storefront independence → platform independence → controlled integration → centralized observability.

My actual decision

If I were signing off the architecture today:

commercetools — if we're talking about a Fortune-100-ish retailer with a mature engineering organization and genuinely complex multi-brand/multi-market requirements.

BigCommerce — if we want 80% of that architectural flexibility with substantially less platform engineering.

Shopify Plus — if the priority is getting many high-quality storefronts operational quickly and the commerce model isn't unusually complex.

The most important question isn't actually "which platform is best?" It's how many storefronts, brands, countries, catalogs, pricing models, and fulfillment models you need to support—and whether those storefronts share a commerce domain or merely share a corporate parent.

If you give me those numbers (e.g. 20 brands / 12 countries / 5M SKUs / B2C+B2B / existing SAP / existing PIM), I can give you a much more concrete platform + reference architecture + buy-vs-build recommendation.