ChatGPT answers, unedited

For an enterprise team with complex integrations, thousands of SKUs, and multi-market expansion, I’d shortlist Shopify Plus, commercetools, Adobe Commerce, and Salesforce Commerce Cloud. The right answer depends heavily on whether you want to minimize platform engineering or maximize architectural control.

My shortlist

1. My default recommendation: Shopify Plus

For your description, I'd start with shopify.com unless you have unusually complex commerce logic.

The important thing is that Shopify Plus isn't limited to a simple DTC storefront anymore. Its current enterprise offering supports headless architectures, APIs, B2B, international markets, and large catalogs; Shopify says the platform supports over one million products/variants and unlimited SKUs. Shopify Shopify

For multi-market specifically, Shopify Markets lets you control products, pricing, currencies, languages, domains, taxes/duties and market-specific experiences from a centralized platform. Shopify Shopify

That's attractive if your architecture looks something like:

ERP/PIM/OMS → integration layer → Shopify Plus → localized storefronts/marketplaces

rather than making the commerce platform itself responsible for every piece of business logic.

One particularly important consideration: if you're doing complex B2B, Plus supports unlimited B2B market catalogs and direct catalog assignment to individual companies/company locations. Shopify Help Center

I'd pick Shopify Plus if: your differentiation is primarily in the product/customer experience and integrations, rather than needing to reinvent the commerce engine itself.

2. commercetools if your engineering team wants maximum control

commercetools.com would be my choice if "complex integrations" really means a highly composable enterprise architecture.

It's API-first and designed around independently composable commerce capabilities rather than one large commerce application. Current enterprise comparisons position it particularly strongly for organizations with substantial engineering capacity and differentiated multi-brand/multi-channel experiences. CIOPages Elogic Commerce

The tradeoff is significant:

• More architectural freedom
• Better fit for sophisticated ERP/PIM/OMS/data architectures
• Excellent for multiple brands/channels/markets
• Easier to replace individual components
• Much more engineering responsibility

I'd choose this over Shopify when you have a strong platform engineering organization and commerce is essentially another set of services in your enterprise architecture.

3. Adobe Commerce if catalog/pricing complexity is the monster

business.adobe.com deserves serious consideration if your thousands of SKUs come with very complicated product relationships, customer-specific pricing, B2B rules, catalogs, promotions, or workflows.

It remains a strong choice for organizations that need extensive customization rather than wanting the commerce vendor to dictate the operating model. Current enterprise comparisons continue to position Adobe strongly for complex B2B/B2C commerce. CIOPages Elogic Commerce

I'd be more cautious about it if your priority is rapid international expansion with minimal platform maintenance. Shopify's SaaS model generally gives you less infrastructure/platform work.

4. Salesforce Commerce Cloud if Salesforce is already your center of gravity

If your organization is heavily invested in salesforce.com—Sales Cloud, Service Cloud, Marketing Cloud, CRM data, etc.—then Salesforce Commerce Cloud becomes much more compelling.

The advantage isn't necessarily that it beats Shopify or commercetools at every commerce capability. It's that the customer, sales, service and commerce ecosystem can be tightly integrated.

I'd put it high on the list if your enterprise architecture is already Salesforce-heavy.

What I'd actually do in your situation

I'd avoid choosing based on "how many SKUs can it handle." Thousands of SKUs is not particularly difficult for today's enterprise platforms. The harder problems are:

1. Product master data — PIM vs commerce ownership.
2. Market-specific assortment — which products exist in which countries.
3. Pricing — currencies, customer groups, price books, regional pricing.
4. Inventory — ERP/WMS/OMS ownership and real-time availability.
5. Localization — language, tax, legal content, payments and shipping.
6. Order orchestration — cancellations, split shipments, returns, exchanges.
7. Integration resilience — retries, queues, idempotency and observability.
8. Market rollout — whether adding country #15 is configuration or a six-month engineering project.

For a sophisticated enterprise, I'd strongly favor keeping the system of record outside the commerce platform:

PIM → product/catalog master
ERP → financial/product/inventory authority
OMS/WMS → fulfillment/inventory orchestration
CDP/CRM → customer data
Commerce platform → assortment + pricing presentation + cart + checkout + commerce experience
Integration/iPaaS/event layer → synchronization/orchestration

That architecture makes the commerce platform much easier to scale across markets.

My ranking for your stated requirements

If I knew nothing else:

1. 🥇 Shopify Plus — best balance of enterprise scale, internationalization, integrations and operational simplicity.
2. 🥈 commercetools — best if your engineering organization wants a truly composable architecture.
3. 🥉 Adobe Commerce — best when catalog/B2B/business-rule complexity outweighs operational simplicity.
4. Salesforce Commerce Cloud — potentially #1 if you're deeply invested in Salesforce.

The key question I'd use to separate Shopify Plus vs. commercetools vs. Adobe is: How much of your commerce logic do you want the platform to own versus your engineering team? That usually determines the winner much more reliably than SKU count or GMV.

4. Salesforce Commerce Cloud if Salesforce is already your center of gravity

If your organization is heavily invested in salesforce.com—Sales Cloud, Service Cloud, Marketing Cloud, CRM data, etc.—then Salesforce Commerce Cloud becomes much more compelling.

The advantage isn't necessarily that it beats Shopify or commercetools at every commerce capability. It's that the customer, sales, service and commerce ecosystem can be tightly integrated.

I'd put it high on the list if your enterprise architecture is already Salesforce-heavy.

What I'd actually do in your situation

Given enterprise scale + complex integrations + thousands of SKUs + multiple markets, I’d focus less on “which ecommerce platform has the most features” and more on which architecture can keep your ERP/PIM/OMS/CRM and regional storefronts from becoming tightly coupled.

My shortlist

My default recommendation: commercetools

For the requirements you gave, commercetools would be my first technical evaluation.

Its architecture is specifically designed around API-first, modular commerce, and its current product catalog can handle variants, bundles, localized data, market-specific assortments, pricing and availability without duplicating the underlying product model. commercetools.com

That's particularly valuable if you have something like:

ERP → PIM → commerce → OMS → search → CMS → tax → payments → marketplaces → analytics

rather than wanting ecommerce to become the system that owns everything.

It also explicitly supports multi-catalog scenarios across regions, business lines and customer segments, and integrations with ERP, CRM, OMS and procurement systems. Its search is designed for large technical catalogs, including hundreds of thousands of SKUs and part numbers. commercetools.com

The tradeoff is important: commercetools gives you architectural freedom, but your team has to operate that architecture. You're effectively buying a highly capable commerce engine rather than buying an entire ecommerce operating model.

When I'd choose Shopify Plus instead

I'd seriously consider Shopify Plus if your priority is:

• launching markets quickly
• minimizing platform maintenance
• strong DTC + B2B on the same ecosystem
• leveraging a huge integration/app ecosystem
• allowing merchandising teams to operate independently of engineering

Shopify Markets now supports market-specific currencies, pricing, catalogs, product availability, language, domains, taxes/duties and shipping. Plus also removes the three-catalog limitation that applies to lower plans and supports direct catalogs for individual companies/company locations. help.shopify.com

Shopify also has explicit patterns for connecting ERP, CRM, PIM and other external systems through direct integrations, iPaaS or APIs. help.shopify.com

So I'd frame it as:

Shopify Plus = simpler enterprise operating model

commercetools = greater architectural control

One architectural point I'd strongly recommend

With thousands of SKUs, don't make the ecommerce platform your master product database by default.

I'd aim for something closer to:

                 ┌──────────────┐
                 │     ERP      │
                 └──────┬───────┘
                        │
                 ┌──────▼───────┐
                 │     PIM      │
                 │ Product      │
                 │ master       │
                 └──────┬───────┘
                        │
             ┌──────────▼──────────┐
             │   Commerce Engine   │
             │                    │
             │ catalog / pricing  │
             │ cart / checkout    │
             │ customer context   │
             └───────┬─────┬──────┘
                     │     │
          ┌──────────┘     └──────────┐
          ▼                           ▼
    Market A                      Market B
    storefront                   storefront
    currency                     currency
    assortment                   assortment
    language                     language

The key is separating global product truth from market-specific commercial context.

For example, SKU ABC-123 might be one global product, but:

• US price = $149
• UK price = £139
• EU assortment = available
• Japan assortment = unavailable
• Germany description = German
• US B2B customer = $119
• UK distributor = £101
• Market A = ships from warehouse 1
• Market B = ships from warehouse 3

Your commerce architecture needs to model those dimensions without creating thousands of duplicated products.

How I'd narrow the decision

If you tell me your ERP/PIM/OMS (e.g. SAP, Salesforce, Dynamics, Akeneo, Salsify, etc.), approximate SKU count, number of markets, B2B vs B2C mix, and whether you want headless, I can give you a much more specific 2–3 platform recommendation and target architecture rather than a generic enterprise-platform list.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d shortlist the platforms differently than I would for a typical DTC brand.

My shortlist

1. Shopify Plus — my default recommendation

I'd start here unless your integration/business requirements specifically push you toward composable commerce.

Shopify has gotten considerably more enterprise-oriented. Shopify Markets supports market-specific catalogs, pricing, currencies, languages, domains, and fulfillment, while allowing markets to be managed centrally. Shopify Shopify

For the integration side, Shopify provides REST/GraphQL APIs, SDKs, Functions, automation, headless capabilities, and integrations with systems such as SAP, Microsoft, NetSuite, and others. Shopify

That combination is compelling when you have:

• 10,000+ SKUs
• multiple countries/currencies
• ERP/PIM/OMS/WMS integrations
• multiple brands or storefronts
• B2B + DTC
• significant custom business logic
• a desire to avoid maintaining the commerce platform itself

Shopify Plus currently starts at $2,500/month on a 1-year term or $2,300/month on a 3-year term, with variable platform fees possible for more complex structures. Shopify

The big question I'd investigate is whether your product/catalog/pricing model fits Shopify's data model cleanly. If it does, I'd strongly favor Shopify because you can spend your engineering resources on your differentiating integrations and experiences rather than maintaining commerce infrastructure.

2. commercetools — if your architecture is genuinely complex

If you have a sophisticated engineering organization and want commerce to be one component of a broader architecture, commercetools is probably the most interesting alternative.

It's API-first and composable, allowing you to separate commerce capabilities from the frontend and other services. It supports multi-region, multi-currency and multi-language configurations from a common backend. Shopify

I'd consider it when you have things like:

• multiple brands/business units
• highly unusual pricing logic
• multiple storefront technologies
• custom checkout/order orchestration
• lots of downstream systems
• a strong internal platform engineering team
• a requirement to swap individual components over time

The tradeoff is important: composable gives you freedom, but also gives you more things to own. For a team without substantial engineering/platform resources, Shopify will generally be much easier.

3. SAP Commerce Cloud — if SAP is at the center of your world

If you're already running SAP S/4HANA/ERP and your commerce operation has complicated B2B structures, pricing, accounts, workflows, and catalogs, SAP Commerce deserves serious consideration.

It's particularly suited to large enterprises with complex B2B/B2C operations and deep SAP integration requirements. Shopify

I wouldn't choose it simply because you have "lots of SKUs." I'd choose it because your business processes themselves are unusually complex and SAP is already foundational to them.

4. Salesforce Commerce Cloud

I'd put Salesforce high on the list if your customer data, CRM, marketing, service, and commerce operations are already heavily Salesforce-centric.

The advantage is less "best ecommerce technology in isolation" and more how effectively commerce fits into your existing Salesforce ecosystem.

If Salesforce is already your customer-data backbone, it's worth comparing seriously against Shopify Plus.

5. Adobe Commerce

Adobe Commerce remains interesting for organizations that need substantial customization around catalog, pricing, customer hierarchies, workflows, and storefront behavior.

But I'd be cautious about selecting it merely because you're an enterprise. The implementation/maintenance burden can become substantial. In 2026, I'd want a very specific reason why Adobe's flexibility is worth that operational complexity.

What I'd actually do in your situation

I'd narrow the evaluation to Shopify Plus vs. commercetools vs. SAP Commerce/Salesforce, depending on your existing stack.

The architecture I'd want to see looks roughly like:

PIM → Commerce → OMS → ERP/WMS

with:

CMS + search + personalization + payments + tax + localization integrated around it.

The critical point is that I would not use the ecommerce platform as your master product-information system just because it has a catalog. With thousands of SKUs, I'd generally want a dedicated PIM if product attributes, localization, enrichment, variants, technical specifications, market-specific assortment, etc. are substantial.

Likewise, I'd avoid turning the ecommerce platform into your ERP/OMS by accumulating custom workflows.

My ranking for your description

If I knew nothing else:

1. Shopify Plus — best balance of enterprise scale, internationalization, integrations, and operational simplicity.
2. commercetools — best if your team is technically sophisticated and your requirements genuinely demand composability.
3. SAP Commerce Cloud — move this to #1 if you're deeply SAP-centric and have very complex B2B processes.
4. Salesforce Commerce Cloud — move this up if Salesforce is already your strategic customer platform.
5. Adobe Commerce — compelling for highly customized commerce, but I'd demand a strong business case for the additional complexity.

One thing I'd not use as the deciding factor is raw SKU count. 10,000 vs. 500,000 SKUs isn't necessarily the difficult part. The harder questions are how many product attributes/variants you have, how pricing works, how many markets/entities you operate, how inventory is distributed, how frequently product data changes, and how many systems need to participate in an order.

If you give me your ERP/PIM/OMS stack, approximate SKU count, number of markets, B2B vs. B2C mix, number of storefronts/brands, and your major integrations, I can narrow this to a 2–3 platform recommendation and lay out the architecture I'd use.

4. Salesforce Commerce Cloud

I'd put Salesforce high on the list if your customer data, CRM, marketing, service, and commerce operations are already heavily Salesforce-centric.

The advantage is less "best ecommerce technology in isolation" and more how effectively commerce fits into your existing Salesforce ecosystem.

If Salesforce is already your customer-data backbone, it's worth comparing seriously against Shopify Plus.

5. Adobe Commerce

Adobe Commerce remains interesting for organizations that need substantial customization around catalog, pricing, customer hierarchies, workflows, and storefront behavior.

But I'd be cautious about selecting it merely because you're an enterprise. The implementation/maintenance burden can become substantial. In 2026, I'd want a very specific reason why Adobe's flexibility is worth that operational complexity.

What I'd actually do in your situation

I'd narrow the evaluation to Shopify Plus vs. commercetools vs. SAP Commerce/Salesforce, depending on your existing stack.

The architecture I'd want to see looks roughly like:

PIM → Commerce → OMS → ERP/WMS

with:

CMS + search + personalization + payments + tax + localization integrated around it.

The critical point is that I would not use the ecommerce platform as your master product-information system just because it has a catalog. With thousands of SKUs, I'd generally want a dedicated PIM if product attributes, localization, enrichment, variants, technical specifications, market-specific assortment, etc. are substantial.

Likewise, I'd avoid turning the ecommerce platform into your ERP/OMS by accumulating custom workflows.

My ranking for your description

If I knew nothing else:

1. Shopify Plus — best balance of enterprise scale, internationalization, integrations, and operational simplicity.
2. commercetools — best if your team is technically sophisticated and your requirements genuinely demand composability.
3. SAP Commerce Cloud — move this to #1 if you're deeply SAP-centric and have very complex B2B processes.
4. Salesforce Commerce Cloud — move this up if Salesforce is already your strategic customer platform.
5. Adobe Commerce — compelling for highly customized commerce, but I'd demand a strong business case for the additional complexity.

One thing I'd not use as the deciding factor is raw SKU count. 10,000 vs. 500,000 SKUs isn't necessarily the difficult part. The harder questions are how many product attributes/variants you have, how pricing works, how many markets/entities you operate, how inventory is distributed, how frequently product data changes, and how many systems need to participate in an order.

If you give me your ERP/PIM/OMS stack, approximate SKU count, number of markets, B2B vs. B2C mix, number of storefronts/brands, and your major integrations, I can narrow this to a 2–3 platform recommendation and lay out the architecture I'd use.

For an enterprise team with thousands of SKUs, complex integrations, and multi-market requirements, I would avoid choosing based on storefront features alone. The key decision is your commerce architecture: how much flexibility you need, how many back-office systems must connect, and whether you want a suite or a composable stack. Enterprise platforms increasingly differentiate around API-first/composable architectures, ERP/PIM integration depth, multi-region support, and B2B complexity. www.ciopages.comwww.scayle.com

A strong shortlist would be:

My recommendation by operating model

1. You have a strong engineering team and expect constant change
→ commercetools

Typical architecture:

• Commerce engine: commercetools
• PIM: Akeneo / Salsify / Pimcore
• Search: Algolia / Elasticsearch / Coveo
• CMS: Contentful / Contentstack
• OMS: Manhattan / Fluent / custom
• ERP: SAP / Oracle / Dynamics

This gives the most long-term flexibility but requires mature technical ownership. www.guideflow.com

2. You are a manufacturer, distributor, or B2B enterprise
→ SAP Commerce Cloud or Adobe Commerce

Prioritize:

• account hierarchies
• negotiated pricing
• quotes/RFQs
• customer-specific catalogs
• ERP synchronization
• EDI workflows

These tend to matter more than storefront design. www.scayle.com

3. You sell primarily DTC across many countries
→ Salesforce Commerce Cloud, Shopify Plus, or BigCommerce Enterprise

Focus on:

• localization
• tax/currency handling
• merchandising speed
• marketing integration
• operational simplicity

4. You are replacing a legacy monolith
→ Lean toward composable

Avoid recreating another tightly coupled system. A common enterprise failure mode is migrating to a new platform but keeping the same integration problems.

Evaluation criteria I would use for your team

Score vendors on:

1. Catalog scale
   • SKU count
   • variants/options
   • regional assortment rules
   • product enrichment workflows

2. Integration architecture
   • ERP
   • PIM
   • OMS
   • CRM
   • tax engines
   • marketplaces
   • warehouses

3. Multi-market capability
   • storefront separation
   • currencies
   • languages
   • pricing rules
   • tax compliance
   • inventory localization

4. Business-user autonomy
   • Can merchandisers launch campaigns without developers?
   • Can regional teams manage markets safely?

5. Total operating model
   • Do you have the engineering capacity to run composable commerce?
   • Or do you need more managed functionality?

For a large enterprise with thousands of SKUs and complex integrations, my default shortlist would be:

1. commercetools — if your team is technically mature and wants maximum flexibility
2. SAP Commerce Cloud — if ERP/B2B complexity dominates
3. Salesforce Commerce Cloud — if Salesforce is already your enterprise backbone
4. Adobe Commerce — if customization is a primary requirement
5. VTEX — if marketplaces and global retail expansion are central

If you share your ERP (SAP/Oracle/Dynamics/etc.), B2B vs B2C mix, number of markets, and whether you need headless, I can narrow this to a 2–3 platform shortlist.

For an enterprise with thousands of SKUs, many integrations, and multiple countries/markets, I’d shortlist Shopify Plus, commercetools, SAP Commerce Cloud, Salesforce Commerce Cloud, and VTEX. The right choice depends less on SKU count itself and more on how complicated your catalog, pricing, fulfillment, and market-specific rules are.

My shortlist

My recommendation for your situation

I'd start with Shopify Plus vs. commercetools.

Shopify Plus is surprisingly capable at the scale you're describing. Shopify says Plus supports unlimited SKUs and has customers operating catalogs with more than a million products/variants. Its Markets functionality supports localized catalogs, pricing, currencies, languages, domains, and market-specific experiences, while expansion stores let enterprises operate separate regional/B2B storefronts under centralized organization management. www.shopify.com

That's why I'd choose Shopify Plus if your objective is:

• Lots of markets but a desire to centralize operations
• Thousands → potentially hundreds of thousands/millions of SKUs
• ERP/PIM/OMS/3PL/payment integrations
• A relatively fast implementation
• Strong merchandising and marketing autonomy
• A large partner/app ecosystem
• Not wanting your engineering organization to effectively become a commerce-platform company

commercetools becomes more attractive if your architecture is already heavily API-driven and you need commerce to be a collection of services rather than an application. It is specifically designed around composable/API-first architecture and supports multi-region, multi-currency and multi-language implementations from a shared backend. www.shopify.com

I'd lean commercetools if you have things like:

• A sophisticated PIM + ERP + OMS architecture already in place
• Multiple storefronts/brands/channels
• Very complicated pricing/promotions/catalog rules
• Headless experiences across web, mobile, marketplaces, kiosks, etc.
• A strong internal engineering/platform team
• A willingness to own more of the architecture

The big architectural question

With thousands of SKUs, I wouldn't make the ecommerce platform your system of record for product data.

I'd generally want something closer to:

ERP → financial/order/business truth
PIM → product/catalog truth
DAM → media
Commerce platform → cart, checkout, pricing, promotions, customer-facing commerce
OMS → order orchestration
Tax/payment services → specialized transaction infrastructure
CMS/search/personalization → experience layer
Data platform → analytics/customer intelligence

Then the ecommerce platform becomes the orchestration layer, rather than a giant database containing every piece of business logic.

That's particularly important when you have thousands of SKUs and multiple markets. The complexity usually comes from market-specific assortment + pricing + tax + inventory + fulfillment + content + payment + regulatory rules, not from the raw SKU count.

One important Shopify consideration

Shopify's current Markets tooling is quite strong, but there are limits/architectural decisions to examine carefully. For example, Shopify documents up to 50 markets natively, with an API/other approaches available when you exceed that; Plus also adds more sophisticated B2B catalog capabilities and business-entity management. help.shopify.com

So if you're talking about, say, 15 countries and 20,000 SKUs, Shopify Plus would be very high on my list.

If you're talking about 40 countries, 500,000 SKUs, 12 brands, highly differentiated regional catalogs, complex contract pricing, multiple ERPs and a dozen downstream commerce channels, I'd spend much more time evaluating commercetools/SAP/VTEX before committing to Shopify.

If you give me your approximate SKU count, number of markets, ERP/PIM/OMS (e.g. SAP, NetSuite, Akeneo, Salsify, Salesforce), B2B vs B2C mix, and whether you're currently monolithic or composable, I can narrow this to 2–3 platforms and lay out the architecture I'd use.

Given enterprise scale + complex integrations + thousands of SKUs + multiple markets, I would not optimize primarily for “easy ecommerce.” I’d optimize for catalog/data architecture, integration flexibility, market localization, and operational scalability.

My shortlist

1. commercetools — my first choice for your description

If “complex integrations” is the defining characteristic, I'd put commercetools at the top.

It's API-first and composable, so you can keep commerce as the core while connecting your own PIM, ERP, OMS, search, CMS, pricing, tax, payments, etc. rather than forcing everything into one suite. commercetools specifically positions its architecture around connecting enterprise ecosystems through APIs, and has examples of multi-brand/multi-country deployments. commercetools.com

The catch: you are taking responsibility for the architecture. Composable commerce gives you flexibility but requires a sophisticated engineering organization. That's a feature for a mature enterprise team and a liability for a small one. www.ciopages.com

I'd choose it if:

• You have a serious internal engineering/platform team.
• Your ERP/PIM/OMS are already established.
• You expect lots of custom business logic.
• Different markets have substantially different rules.
• You want to avoid vendor lock-in.
• Headless/composable is part of your long-term architecture.

2. Adobe Commerce — probably the safest "complex enterprise commerce" choice

Adobe Commerce would be my second choice, and potentially #1 if you want more functionality inside the commerce platform.

It's particularly compelling with thousands of SKUs and complicated inventory/catalog structures. Its inventory model supports multiple warehouses, stores, drop shippers, websites and regional stocks, including mapping different stocks to different websites/regions. experienceleague.adobe.com

I'd lean Adobe when you need things like:

• Complex catalog structures
• B2B + B2C
• Customer-specific pricing
• Multiple websites/stores
• Complicated promotions
• Multiple inventory sources
• Extensive customization
• Deep ERP/PIM integrations

The downside is that you'll own more implementation and technical complexity than with a pure SaaS platform.

3. Salesforce Commerce Cloud — excellent if you're already Salesforce-heavy

If your enterprise runs heavily on Salesforce, I'd put Salesforce Commerce Cloud very high on the list.

It has strong multi-site architecture and supports multi-language/multi-currency operations, while allowing shared and market-specific catalogs, price books, promotions, content, etc. www.salesforce.com

This becomes especially attractive when commerce needs to interact tightly with:

CRM → customer → sales → service → marketing → commerce → data

rather than operating as an isolated ecommerce application.

I'd avoid choosing it just because you already have Salesforce, though. If your commerce architecture needs to remain highly decoupled, commercetools may be the better technical foundation.

4. BigCommerce Enterprise — the dark horse

I'd absolutely put BigCommerce Enterprise in the RFP.

Its Multi-Storefront capability lets you manage multiple brands/regions/customer segments from one backend, with localized products, currencies, pricing, checkout, promotions, payments and shipping. commercetools.comwww.bigcommerce.comhelp.shopify.comwww.ciopages.com

That gives you a nice middle ground:

less platform engineering than commercetools/Adobe ↔ more flexibility than a basic SaaS storefront.

For an enterprise that wants to move quickly without building a huge commerce platform organization, this could actually be the best economic choice.

5. Shopify Plus — I'd consider it, but not automatically

Shopify Plus has become substantially more capable for international and B2B commerce. Its Markets model can handle country/region markets, B2B markets, localized pricing, catalogs, currencies, taxes/duties and product availability. help.shopify.com

But for “thousands of SKUs + complex integrations”, I'd make Shopify prove that your requirements fit its model rather than assuming its ecosystem will solve everything.

It's particularly compelling if your priority is:

"We want our teams focused on merchandising and growth, not operating ecommerce infrastructure."

Less compelling if your priority is:

"Commerce is a core enterprise application that needs to behave differently in 30 countries and integrate deeply with 15 internal systems."

What I'd recommend architecturally

For your profile, I'd actually evaluate the whole commerce stack, not just the storefront platform:

PIM
↓
Commerce engine
↓
OMS / inventory
↓
ERP
↓
Payments / tax / fraud / shipping

with an integration/event layer between them.

For thousands of SKUs, I'd strongly consider making a PIM the system of record for product information rather than allowing the ecommerce platform to become the master catalog.

Likewise, don't make ecommerce your inventory master if you already have an ERP/OMS.

That leads to a cleaner model:

ERP = financial/product supply truth
PIM = product/content truth
Commerce = selling/pricing/cart/checkout
OMS = order/fulfillment truth
CDP/CRM = customer truth

That architecture makes adding market #12 much less painful than duplicating the entire ecommerce stack.

My ranking for your particular description

If you have a large engineering team:

1. 🥇 commercetools
2. 🥈 Adobe Commerce
3. 🥉 Salesforce Commerce Cloud
4. BigCommerce Enterprise
5. Shopify Plus

If you want maximum operational simplicity:

1. 🥇 BigCommerce Enterprise
2. 🥈 Shopify Plus
3. Salesforce Commerce Cloud
4. Adobe Commerce
5. commercetools

The important distinction is that commercetools isn't necessarily "better" than Shopify Plus—it transfers more responsibility to your architecture team. For an enterprise with genuinely complex integrations, that can be exactly what you want. commercetools.comwww.ciopages.com

If you give me your approximate SKU count, number of markets/countries, B2B vs B2C, ERP/PIM/OMS (e.g. SAP, NetSuite, Akeneo, Salsify), and whether you need headless, I can narrow this to a 2–3 platform recommendation and a proposed reference architecture.

For an enterprise team with complex integrations, thousands of SKUs, and multiple markets, I’d narrow the field to Shopify Plus, Adobe Commerce, commercetools, and Salesforce Commerce. The right choice depends less on SKU count and more on how much of your commerce logic you want the platform to own versus your engineering team.

My shortlist

What I'd recommend for your description

I'd start with Shopify Plus and Adobe Commerce as the two finalists, with commercetools added if your engineering organization is genuinely committed to composable commerce.

Shopify Plus has become much more capable for this use case. Its Markets architecture supports market-specific currencies, catalogs, pricing, domains, localization, and product availability, while Plus adds unlimited B2B market catalogs and more granular company-location capabilities. help.shopify.com

Its biggest advantage is that your thousands of SKUs and integrations don't automatically translate into thousands of things your team has to operate. Shopify handles the core commerce infrastructure while you integrate ERP/PIM/OMS/CRM/etc. around it. Shopify also supports headless architectures and extensive APIs if you don't want a conventional Shopify storefront. www.shopify.com

Adobe Commerce becomes more attractive if your complexity is genuinely in the catalog, pricing, merchandising, B2B rules, or multi-brand/multi-site model. Adobe specifically positions Commerce for multiple sites, brands, markets, and millions of SKUs, with shared catalogs/content/promotions plus market-specific customization. business.adobe.com

commercetools is the one I'd investigate if you have a substantial engineering/platform team and already think in terms of PIM + CMS + search + pricing + promotions + OMS + checkout as separate services. It's explicitly designed around composable architecture and claims support for millions of SKUs and high-traffic peaks. commercetools.com

The architecture I'd actually evaluate

For your scenario, I wouldn't choose a platform in isolation. I'd evaluate the commerce stack:

ERP → PIM → Commerce platform → Search → CMS → OMS/fulfillment → Payments/tax → Analytics/CDP

The critical question is: where is the system of record for each domain?

For example:

• PIM: product master, attributes, taxonomy, localization
• ERP: inventory/cost/accounting
• Commerce: carts, checkout, customer pricing, promotions, orders
• OMS: fulfillment and order orchestration
• CMS: editorial content
• Search: merchandising/search relevance
• Tax: Avalara/Vertex/etc.
• Integration layer: event bus/iPaaS/API gateway

That matters enormously. A platform that can technically hold 5 million SKUs isn't necessarily the best platform if you're importing product, inventory, pricing, and availability from six enterprise systems.

My rough decision rule

Choose Shopify Plus if:
You want global expansion, strong operational scalability, and a relatively small platform-maintenance burden, and your unusual business logic can live in integrations/apps/services.

Choose Adobe Commerce if:
Your competitive advantage depends on complicated catalog structures, pricing, customer segmentation, B2B workflows, or multi-brand/multi-store behavior.

Choose commercetools if:
You have a strong engineering organization and want commerce to be an API-driven component of a broader enterprise architecture rather than the center of it.

Choose Salesforce Commerce if:
Your company is already heavily standardized on Salesforce and customer/account data is central to the commerce experience.

One important caveat: "thousands of SKUs" alone wouldn't push me toward the more complex platforms. Thousands is not particularly intimidating for modern enterprise commerce. I'd be much more interested in number of markets, number of catalogs, price lists, product variants, ERP/PIM integrations, B2B account structures, order volume, and how different each market's business rules are.

If you give me those numbers—e.g. SKU count, countries/markets, B2B vs B2C, ERP/PIM/OMS, annual orders/GMV, number of storefronts, and whether you need headless—I can narrow this to a 2–3 platform recommendation and a reference architecture.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d shortlist Shopify Plus, commercetools, Adobe Commerce, and SAP Commerce Cloud—but the right answer depends heavily on how much complexity belongs in the commerce platform versus your surrounding systems.

My shortlist

What I'd pick for your description

I'd start with Shopify Plus unless your integrations and business rules are unusually complex.

Shopify Plus has become considerably more enterprise-capable. Its Markets functionality supports localized currencies, domains, pricing, catalogs, taxes/duties and product availability, while Plus supports unlimited B2B market catalogs and customer/company-specific catalogs. help.shopify.com

It also has REST/GraphQL APIs, custom apps, Shopify Functions, automation, and documented ERP/CRM/PIM integration patterns—including iPaaS options such as Boomi, Jitterbit and Celigo. www.shopify.com

The important architectural distinction is:

Don't make Shopify your system of record.

For a catalog of thousands of SKUs, I'd typically architect it something like:

ERP / PIM / MDM
↓
iPaaS / integration layer
↓
Shopify Plus
↓
Localized storefronts / markets / B2B
↓
OMS / payments / tax / fulfillment / analytics

That keeps product master data, inventory, financials, etc. where they belong rather than turning the commerce platform into a giant integration hub.

When I'd choose commercetools instead

If by "complex integrations" you mean a large engineering organization, many bespoke workflows, multiple frontends/channels, and a strong desire to own the architecture, I'd seriously consider commercetools.

It's API-first/composable rather than an all-in-one storefront platform, which gives you considerably more freedom over the architecture. Current enterprise comparisons characterize it as the strongest option when maximum architectural flexibility is the priority. elogic.co

The tradeoff is substantial: you are buying architectural freedom in exchange for engineering responsibility. Composable commerce can be fantastic when you have the team to operate it; it's painful when you don't.

When Adobe makes more sense

I'd put Adobe Commerce near the top if your business has things like:

• extremely complicated B2B pricing
• customer/account-specific catalogs
• complex product configuration
• unusual promotions
• complicated quoting/workflows
• significant custom commerce logic
• a willingness to maintain substantial customizations

It's particularly compelling when the business model itself is more complicated than the storefront.

One thing I'd avoid

I wouldn't select a platform based primarily on "how many SKUs can it handle?"

Thousands of SKUs isn't especially unusual for modern enterprise commerce. The harder problems are usually:

SKU × markets × currencies × languages × customer segments × price lists × inventory locations × tax rules × fulfillment rules × integrations.

That's the matrix you should benchmark.

A recent 2026 enterprise-commerce guide makes essentially the same architectural point: the decision is less about feature checklists and more about whether the platform's operating model matches your team's ability to manage the resulting integrations and architecture. www.ciopages.com

My ranking for your situation

If I knew nothing else:

1. Shopify Plus — best default enterprise choice
2. commercetools — best if you're a strong engineering/composable-commerce organization
3. Adobe Commerce — best for unusually complex commerce/B2B logic
4. SAP Commerce Cloud — best when SAP is already deeply embedded

If you tell me (1) B2B vs B2C, (2) approximate SKU count, (3) number of countries/markets, (4) ERP/PIM/OMS you use, and (5) whether you want headless, I can narrow this to a 2–3 platform recommendation and an architecture I'd actually deploy.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d shortlist commercetools, Shopify Plus, Adobe Commerce, and Salesforce Commerce Cloud—but the right answer depends heavily on how much of your commerce model is standard vs. highly customized.

My ranking

1. commercetools — my pick if your integrations are genuinely complex

This would be my first evaluation if you're talking about dozens of upstream/downstream systems, multiple ERPs/PIMs/OMSs, many storefronts, regional business rules, and a large engineering organization.

Its API-first/composable architecture lets you treat commerce as a set of services rather than forcing your business processes into a monolithic platform. commercetools specifically positions its enterprise platform for millions of SKUs and global traffic, and its current Sphere platform is designed around headless, modular commerce. commercetools.com

Choose it if:

• Your product/catalog model is complicated.
• You need multiple front ends/channels.
• Markets have materially different business rules.
• You want ERP/PIM/OMS/payment/search systems to remain independent.
• You have the engineering/architecture capability to own a composable stack.

Tradeoff: You are buying architectural freedom, but you're also accepting more architectural responsibility. For an enterprise team without strong platform engineering, that can become expensive.

2. Shopify Plus — my default recommendation for most enterprises

I'd strongly consider Shopify Plus before assuming you need a fully composable platform.

Shopify now has mature multi-market capabilities: market-specific catalogs/pricing, currencies, localization, domains, languages, and centralized management across regions. It also provides APIs, headless capabilities, ERP/PIM integrations, and extensive automation. www.shopify.com

For 2026 specifically, Shopify has also expanded its native B2B capabilities substantially, while Plus retains the more advanced functionality such as unlimited catalogs and customer/location-specific catalog assignment. www.shopify.com

The important question is therefore:

Are your integrations complex because your business is complex, or because your current commerce platform makes integrations painful?

If it's mostly the latter, Shopify Plus can eliminate a lot of infrastructure you otherwise have to operate.

I'd favor it when you want global expansion, multiple brands/markets, thousands or even very large numbers of SKUs, strong APIs, and a relatively low operational burden.

3. Adobe Commerce — worth serious consideration for complex catalog/B2B

Adobe Commerce remains compelling when the commerce rules themselves are complicated: customer groups, sophisticated pricing, catalogs, promotions, B2B purchasing workflows, etc.

I'd put it ahead of Shopify if you have requirements that are deeply embedded in the commerce engine and don't fit neatly into Shopify's model.

The downside is the operational/implementation burden. At enterprise scale, you need to evaluate the total cost of ownership and implementation complexity, not just license cost.

4. Salesforce Commerce Cloud

I'd move Salesforce Commerce Cloud way up the list if your organization already runs heavily on Salesforce CRM, Service, CPQ, Marketing Cloud, and customer/account data.

In that situation, the value isn't necessarily that Commerce Cloud is universally "better"; it's that you can potentially create a much more coherent Salesforce-centered customer and commerce architecture.

The architecture I'd actually recommend

For your description, I wouldn't evaluate ecommerce platforms in isolation.

I'd design the stack roughly like:

ERP(s)
↓
Integration/iPaaS layer
↓
PIM / product master → Commerce platform ← OMS / inventory
↓
Search / merchandising
↓
CMS / experience layer
↓
Regional storefronts / marketplaces / B2B portals

The critical architectural decision is where the source of truth lives.

For example, I generally wouldn't want thousands of SKUs being independently maintained in every regional Shopify/Adobe/commercetools instance. I'd want a centralized product model, with the commerce layer receiving the appropriate assortment, pricing, inventory, localization, and market rules.

My practical shortlist

If I were running your RFP, I'd start with:

A. Shopify Plus — baseline/reference architecture
B. commercetools — maximum-complexity architecture
C. Adobe Commerce — complex catalog/B2B alternative
D. Salesforce Commerce Cloud — only if Salesforce is strategically central

A recent 2026 enterprise-platform review similarly frames the decision around architecture and operating model rather than feature checklists—particularly the tradeoff between composable flexibility and the organizational capacity required to operate it. www.ciopages.com

If you tell me roughly (1) SKU count, (2) number of countries/markets, (3) B2C vs B2B, (4) ERP/PIM/OMS you're using, and (5) whether you have a 10+ person engineering team, I can narrow this to a specific recommendation and architecture.

For an enterprise team with thousands of SKUs, multiple markets, and complex integrations, I would avoid choosing based on storefront features alone. The right platform depends heavily on your ERP/PIM/OMS architecture, B2B vs. B2C complexity, localization needs, engineering capacity, and operating model. Enterprise commerce platforms generally split into integrated suites vs. composable/headless architectures. www.ciopages.com

A shortlist I would evaluate:

www.mobiloud.com

My recommendation by scenario

1. Global B2B + B2C + thousands of SKUs + ERP complexity

• Shortlist: SAP Commerce Cloud, Adobe Commerce, commercetools
• Especially if you have:
  • customer-specific pricing
  • contracts
  • negotiated catalogs
  • approval workflows
  • regional inventory rules
  • distributor portals

2. Global DTC with many countries and brands

• Shortlist: Salesforce Commerce Cloud, Shopify Plus, commercetools
• Prioritize:
  • localization
  • tax/VAT
  • payments
  • merchandising speed
  • experimentation

3. You have a strong engineering organization and want maximum flexibility

• Shortlist: commercetools + best-of-breed stack
• Typical architecture:
  • Commerce engine: commercetools
  • PIM: Akeneo / Salsify / Contentserv
  • Search: Algolia / Elasticsearch
  • CMS: Contentful / similar
  • OMS: dedicated OMS
  • Integration layer: MuleSoft / Boomi / custom services

4. You want to reduce platform maintenance

• Shortlist: Shopify Plus or BigCommerce Enterprise
• SaaS platforms reduce infrastructure ownership, but you need to confirm they can handle your business rules. www.shopify.com

The architecture I would expect for a serious enterprise setup

ERP (SAP / Oracle / Dynamics)
        |
        |
Integration Layer (MuleSoft / Boomi / APIs)
        |
        +---- PIM (product master)
        |
        +---- OMS (orders/inventory)
        |
        +---- Commerce Platform
        |
        +---- CMS + Search + Personalization
        |
        +---- Marketplaces / Retail Channels

The commerce platform should not become your product master, pricing engine, or integration hub. For thousands of SKUs, the PIM/ERP/data governance layer is often more important than the storefront choice.

My default enterprise shortlist would be:

1. SAP Commerce Cloud — if SAP is central and B2B complexity is high
2. commercetools — if your engineering team wants a future-proof composable architecture
3. Adobe Commerce — if customization and catalog complexity dominate
4. Salesforce Commerce Cloud — if Salesforce is your customer platform backbone
5. Shopify Plus — if speed, operational simplicity, and global DTC are priorities

To narrow this properly, I’d want to know:

• Are you primarily B2B, B2C, or B2B2C?
• Current ERP (SAP, Oracle, Dynamics, NetSuite, custom)?
• Approximate SKU count (10k, 100k, 1M+)?
• Number of markets/languages/currencies?
• Do you need marketplace capabilities?
• How large is your engineering team?

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d narrow the field to commercetools, Adobe Commerce, and Shopify Plus—with the right choice depending heavily on how much engineering complexity you want to own.

My shortlist

1. I'd look hardest at commercetools

Given your description—complex integrations + thousands of SKUs + multi-market—this is probably my first technical evaluation.

commercetools is API-first and designed around composable commerce. Its enterprise offering explicitly targets millions of SKUs and global scale, while its product architecture lets you use its catalog, commerce, checkout, etc. as modular components. commercetools.com

That matters if you have an architecture something like:

ERP → PIM → commerce → OMS → payments → tax → search → marketplaces → CDP/CRM

rather than wanting the ecommerce platform to own everything.

I'd choose it when: your engineering organization is sophisticated and you expect the commerce architecture itself to evolve over the next 5–10 years.

2. Adobe Commerce if catalog/business rules are exceptionally complicated

Adobe is particularly interesting if you have lots of catalog permutations, pricing rules, brands, regions, customer types, and B2B requirements.

Its multi-site architecture supports multiple websites, stores and store views, with different catalogs, pricing, branding, languages and domains. Adobe specifically positions Commerce for multi-brand/multi-storefront operations and very large SKU counts. experienceleague.adobe.com

The tradeoff is that you're taking on considerably more architectural and operational complexity than with a SaaS-first platform.

I'd choose it when: your commerce rules are unusually complex and you want substantial control over the commerce engine.

3. Shopify Plus if you want to reduce operational burden

Don't dismiss Shopify because you're enterprise. Shopify Plus's current Markets functionality is substantially more sophisticated than the old "one store per country" model: markets can control currencies, domains, languages, pricing, product availability and localized experiences. Its B2B Markets capabilities also support market-specific catalogs and pricing. help.shopify.com

The big advantage is what you don't have to operate.

I'd favor Shopify Plus if your complexity is primarily in integrations and market operations, rather than in radically customized commerce logic.

The decision I'd make

I'd use this rule of thumb:

Choose Shopify Plus
→ if you want the fastest path to a scalable global operation and can adapt your processes to Shopify's model.

Choose Adobe Commerce
→ if your catalog, pricing, customer segmentation and B2B rules are exceptionally complex.

Choose commercetools
→ if your company is essentially building a digital commerce platform, with engineering/integration complexity being a core part of the business.

For the profile you gave, I'd start the RFP with commercetools + Adobe Commerce + Shopify Plus, rather than evaluating 10+ vendors. A current 2026 enterprise-platform comparison similarly puts those three alongside Salesforce, SAP, BigCommerce and others, but emphasizes that architecture/team capacity—not feature checklists—is the key differentiator. www.ciopages.com

One important caveat

"Thousands of SKUs" alone isn't the deciding factor. I'd want to know:

• How many markets/countries?
• B2C, B2B, or both?
• Do you have customer-specific pricing?
• How many ERP/PIM/OMS integrations?
• Are products highly configurable/variant-heavy?
• How many orders/day and peak orders/minute?
• Multiple brands/storefronts?
• Do markets have materially different catalogs?
• How much of the existing stack do you want ecommerce to replace?
• How large is your engineering/platform team?

Those answers could move my recommendation quite dramatically. For example, 5,000 SKUs + 20 markets + 15 integrations points to a different architecture than 500,000 SKUs + 8 markets + highly individualized B2B pricing.

If you give me those numbers, I can turn this into a specific architecture recommendation and a 3-platform scorecard (including PIM, ERP, OMS, search, CMS, integration layer, localization, and total cost/complexity).

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d avoid choosing primarily on storefront features. Your architecture and integration model will matter much more.

My shortlist

My default recommendation: Adobe Commerce

For the profile you described, Adobe Commerce would probably be my first platform to evaluate.

Adobe specifically positions its catalog architecture for millions of SKUs and thousands of prices per SKU, while supporting multiple brands, markets, languages, currencies and B2B/B2C models. It also provides APIs and integration capabilities for ERP, CRM, PIM, WMS and OMS systems. business.adobe.com

That's important because "thousands of SKUs" isn't actually the difficult part. The difficult part is usually something like:

ERP → PIM → pricing → inventory → commerce → OMS → fulfillment → marketplaces → analytics

with different rules for each country/market.

Adobe is particularly strong when you need the commerce layer to accommodate a lot of those business rules rather than forcing everything into third-party apps. business.adobe.com

When I'd choose commercetools instead

If you have a large engineering organization and genuinely want composable commerce, I'd put commercetools at the top of the evaluation.

I'd choose this route when your architecture looks more like:

PIM + ERP + custom pricing service + search + CMS + commerce engine + OMS + CDP

rather than expecting one platform to provide most of those capabilities.

The upside is enormous architectural flexibility. The downside is that you become responsible for making the pieces work together. Enterprise composable commerce can be fantastic, but it's not automatically simpler just because the APIs are cleaner.

Shopify Plus is the "reduce complexity" option

Don't dismiss Shopify Plus simply because you're enterprise. Its current Markets tooling supports localized currencies, domains, catalogs, pricing and regional experiences, while Plus adds substantially more B2B catalog flexibility. help.shopify.com

It's particularly attractive if your priority is:

"We want to launch and operate 20+ markets without building a giant commerce engineering organization."

Shopify also supports headless implementations and extensive API/app integrations. www.shopify.com

I'd be more cautious if you have highly unusual pricing engines, sophisticated account hierarchies, complex quoting/approval workflows, or a lot of commerce logic that doesn't map naturally to Shopify.

SAP Commerce if SAP is already your backbone

If you're deeply invested in SAP ERP/S/4HANA, I'd give SAP Commerce Cloud a serious look before introducing another major platform. SAP explicitly targets large enterprises with complex B2B, B2C and B2B2C commerce, complex catalogs and deep integration with SAP business data. www.sap.com

How I'd make the decision

I wouldn't run a generic "which ecommerce platform is best?" RFP.

I'd build a realistic architecture test around 5–10 of your nastiest SKUs and business scenarios:

1. Product complexity — variants, bundles, configurable products, attributes, regional availability.
2. Pricing — customer-specific prices, currencies, volume tiers, promotions and price books.
3. Markets — 10+ countries with different catalogs, taxes, currencies, payment methods and content.
4. Integration — ERP + PIM + OMS + WMS + CRM, including failure/retry scenarios.
5. Scale — bulk catalog updates, price updates, inventory feeds and order volumes.
6. B2B — account hierarchies, permissions, approvals, negotiated pricing and quotes.
7. Operational model — who actually maintains all this at 2 a.m. when an integration breaks?

I'd also insist that vendors demonstrate your actual integration flows, rather than showing polished storefront demos.

My rough ranking for your description

1. Adobe Commerce — best overall fit for complex enterprise commerce
2. commercetools — best if your engineering organization wants true composable architecture
3. SAP Commerce Cloud — potentially #1 if you're heavily SAP-centric
4. Shopify Plus — best if operational simplicity and speed outweigh extreme customization
5. Salesforce Commerce Cloud — very compelling if Salesforce is already your core customer platform

One other architectural recommendation: don't make ecommerce your master product database just because it has a catalog. With thousands of SKUs, I'd normally want a dedicated PIM as product source of truth, ERP for core commercial/operational data, OMS for order orchestration, and commerce focused on the customer-facing transaction layer.

If you tell me (a) B2B vs B2C, (b) number of markets, (c) ERP/PIM/OMS you use, (d) approximate SKU/variant count, and (e) whether you have a large engineering team, I can narrow this to a 2–3 platform architecture recommendation.

For an enterprise team with thousands of SKUs, complex integrations, multiple countries/markets, and likely multiple pricing/catalog rules, I would narrow the field considerably. The key question isn't "which ecommerce platform has the most features?"—it's which platform can become the reliable commerce layer without turning your integration architecture into a nightmare.

My shortlist

1. My first choice: commercetools

If by "complex integrations" you mean ERP + PIM + OMS + WMS + CRM + custom pricing + multiple front ends + marketplaces, I'd put commercetools at the top.

It's API-first and composable, so commerce doesn't have to own every piece of your architecture. That's particularly valuable when your SKU/catalog data lives in a PIM and inventory/order truth lives elsewhere. commercetools.com

Choose it if:

• You have a substantial engineering/platform team.
• You want headless/composable architecture.
• You expect the business model to become more complex over time.
• You don't want the ecommerce vendor dictating how your ERP/PIM/OMS architecture works.

Tradeoff: you're buying architectural freedom, but you're also buying more engineering responsibility.

2. Adobe Commerce — probably the strongest for extreme catalog complexity

I'd seriously evaluate Adobe if "thousands of SKUs" is actually shorthand for tens/hundreds of thousands or millions, with complicated price books, customer-specific catalogs, brands, regions and B2B rules.

Adobe currently positions Commerce around millions of SKUs and thousands of prices per SKU, multi-brand/multi-geography deployments, B2B/B2C, and extensive ERP/PIM/OMS integration. commercetools.combusiness.adobe.com

Its newer Commerce Optimizer is particularly interesting for very large catalogs: Adobe says it can support 250M+ SKUs and 30,000 price points per SKU and operate across hundreds of sites. business.adobe.com

I'd favor Adobe over commercetools if: your complexity is primarily catalog, pricing, merchandising, B2B account structures and multi-site commerce, rather than architectural flexibility.

3. Shopify Plus — don't dismiss it because you're "enterprise"

Shopify Plus has become much more credible for sophisticated multi-market organizations.

Markets lets you manage regional experiences—including currency, catalogs, pricing, product availability and localized experiences—from a common administration layer. Plus also supports unlimited B2B market catalogs and direct catalogs for individual company locations. help.shopify.com

Shopify also supports assigning different business entities to markets, which matters if you're operating through separate legal entities internationally. help.shopify.com

I'd choose Shopify Plus when:

• You want to minimize infrastructure/platform ownership.
• Your team wants to move quickly.
• Your integrations can be cleanly separated through middleware/event-driven services.
• You don't need the commerce platform itself to be the ultimate source of truth for every complex business rule.

The important architectural distinction is: don't try to make Shopify your ERP/PIM/OMS. Let it be the commerce execution layer.

4. BigCommerce Enterprise — the underrated option

BigCommerce is worth putting into the RFP. Its Multi-Storefront architecture lets you operate different brands, regions or customer segments from one backend, while B2B Edition adds company accounts, quoting, shared lists, invoice workflows and headless support. www.bigcommerce.com

I'd put it ahead of Shopify if you need more native B2B flexibility but don't want to take on the engineering burden of commercetools.

5. Salesforce Commerce Cloud

If your enterprise already runs heavily on Salesforce—particularly Sales Cloud + Service Cloud + Data Cloud—SFCC deserves serious consideration.

Its current B2B offering includes multiple storefronts and increasingly integrated order management, analytics, segmentation and personalization. www.salesforce.com

But I wouldn't choose it merely because Salesforce is your CRM. I'd want to see the entire integration architecture and economics first.

What I'd do in your situation

I'd run an RFP with four finalists:

commercetools → Adobe Commerce → Shopify Plus → BigCommerce Enterprise

Then score them heavily on:

1. PIM integration — bulk catalog ingestion, taxonomy, attributes, media
2. ERP integration — SAP/Dynamics/Oracle/etc.
3. Pricing complexity — customer, region, currency, volume, contract pricing
4. Catalog scale — SKU count and number of variants/attributes/price points
5. Multi-market architecture — countries, currencies, languages, tax, domains
6. Multi-brand/storefront management
7. OMS/WMS integration
8. API/event architecture
9. Bulk updates — e.g. "change 80,000 SKUs in five minutes"
10. Operational ownership — how much engineering effort is required just to keep the platform healthy
11. Deployment/release model
12. Total 3–5 year TCO, including implementation partners and engineering—not just license fees.

The biggest trap I'd avoid is selecting based on front-end features. With your profile, the real architecture should probably look something like:

PIM → commerce platform → OMS → ERP/WMS, with an integration/event layer connecting everything, rather than stuffing all of those responsibilities into the ecommerce platform.

My quick recommendation

• Best architecture: commercetools
• Best for massive/complex catalogs: Adobe Commerce
• Best operational simplicity: Shopify Plus
• Best pragmatic middle ground: BigCommerce Enterprise
• Best Salesforce ecosystem play: Salesforce Commerce Cloud

If you tell me roughly SKU count, number of markets/countries, B2B vs B2C, ERP/PIM/OMS you're using, number of storefronts/brands, and whether you have a 5-person or 50-person engineering team, I can turn this into a much more specific enterprise architecture recommendation and vendor scorecard.

For an enterprise team with complex integrations, thousands of SKUs, and multiple markets, I’d shortlist commercetools, Salesforce Commerce Cloud, Adobe Commerce, and VTEX. I’d put Shopify Plus in the evaluation too, but mainly if you value operational simplicity over maximum architectural flexibility.

My ranking

1. commercetools — my first choice

For the requirements you gave, commercetools is probably where I'd start.

It's API-first/composable, designed specifically around enterprise integrations, and its current catalog capabilities are aimed at complex products, variants, pricing, assortments, localization, brands, regions and channels. It explicitly supports catalogs with millions of SKUs. commercetools.comcommercetools.com

The big advantage is that you don't have to force your entire enterprise architecture into the commerce platform. You can have something like:

ERP → PIM → commercetools → CMS/search → storefronts → OMS/payment/tax → marketplaces

That tends to work particularly well when you've already accumulated a lot of enterprise systems.

Its catalog module can also be adopted independently, which is interesting if your immediate problem is catalog complexity rather than replacing the entire commerce stack. commercetools.comcommercetools.com

I'd choose it if: your engineering organization is sophisticated and you want the commerce layer to remain flexible for the next 5–10 years.

2. Salesforce Commerce Cloud — best enterprise-suite choice

If you're already heavily invested in Salesforce, Salesforce Commerce Cloud becomes a very compelling option.

It has strong multi-site architecture, allowing brands/regions to share or specialize catalogs, pricing, promotions and content. Salesforce also supports multi-language and multi-currency operations from its Business Manager. www.salesforce.com

The key question is whether your organization wants maximum composability or maximum consolidation around a major enterprise vendor.

I'd choose it if: Salesforce CRM/CDP/Marketing/Service is already central to your architecture.

3. Adobe Commerce — particularly strong for catalog + B2B complexity

Adobe Commerce is worth serious consideration if your "thousands of SKUs" actually means highly complicated product relationships, customer-specific catalogs, pricing, inventory and B2B rules.

Adobe supports multi-site international configurations and explicitly supports millions of SKUs across brands and regions. Its inventory model can also map websites to different warehouses, stores, drop-shippers and regional stocks. business.adobe.com

Its B2B functionality includes company accounts, organizational structures, permissions, customer-specific catalogs and pricing. experienceleague.adobe.com

I'd choose it if: catalog and B2B complexity outweigh the desire for a lightweight composable architecture.

4. VTEX — underrated for global complexity

I'd put VTEX high on the RFP if you're selling across many countries/channels or potentially operating a marketplace.

VTEX is built around multi-country, multi-brand and multi-channel operations, with API-first/MACH architecture. It also combines B2B, B2C and marketplace capabilities in one platform. www.vtex.com

Its marketplace tooling is particularly interesting if you're aggregating third-party sellers: catalog integration, SKU matching, catalog normalization, seller onboarding, split payments and order routing are built into the platform. www.vtex.com

I'd choose it if: "multi-market" also means marketplaces, third-party sellers, complicated fulfillment or multiple business models.

5. Shopify Plus — don't dismiss it

Shopify Plus is much more capable at enterprise scale than its reputation sometimes suggests.

Its Markets architecture handles market-specific catalogs, pricing, currencies, languages, domains and product availability, while Plus adds extensive API/integration capabilities. www.shopify.com

But I'd be careful about choosing it purely because it's easier.

For thousands of SKUs + dozens of integrations + highly customized pricing/catalog/checkout logic, I'd want to test your hardest requirements against Shopify's data model before committing. It can be an excellent platform, but your architecture shouldn't become a collection of workarounds around the platform's opinionated model.

I'd choose it if: your priority is getting global markets operational quickly while minimizing commerce-platform infrastructure and maintenance.

What I'd actually do in your situation

I'd run a serious RFP with three finalists:

commercetools vs. Salesforce Commerce Cloud vs. Adobe Commerce

Then add VTEX if marketplaces/B2B/multi-channel are significant, and Shopify Plus as the "can we dramatically simplify this?" benchmark.

The most important thing is not SKU count itself. I'd score vendors against these dimensions:

1. Catalog model — variants, bundles, kits, relationships, attributes, regional assortment.
2. Market model — country × language × currency × tax × assortment × pricing.
3. Integration architecture — ERP/PIM/OMS/WMS/CRM/CDP/payment/tax/search.
4. API/event capabilities — especially bulk catalog updates and near-real-time inventory.
5. Pricing complexity — market, customer, channel, contract and promotional pricing.
6. Multi-brand architecture — shared vs. isolated data.
7. Localization — content, SEO, URLs, currencies, legal/compliance.
8. Operational scalability — catalog imports, indexing, promotions, traffic spikes.
9. B2B requirements — accounts, hierarchies, approval workflows and negotiated pricing.
10. Total architecture cost — not just license cost; include implementation, integration and ongoing engineering.

One architectural recommendation: don't make the commerce platform your master product-data system just because it has a catalog. With your integration complexity, I'd generally want a PIM/MDM as the product-data authority, ERP as the financial/inventory authority, and commerce to consume the appropriately enriched/market-specific assortment.

If you tell me (a) B2B vs B2C, (b) number of markets/countries, (c) approximate SKU/variant count, (d) your ERP/PIM/OMS, and (e) whether you're headless, I can narrow this down to a 2–3 platform recommendation and proposed target architecture.