ChatGPT answers, unedited

For an enterprise team with thousands of SKUs, multiple markets, and complex integrations, I’d focus less on “which ecommerce platform is best?” and more on which architecture can handle your catalog, localization, integrations, and organizational complexity without becoming a maintenance bottleneck.

My shortlist would be:

My first two to evaluate

commercetools would be high on my list if your team is genuinely engineering-heavy. Its platform is API-first and designed for multi-channel commerce, international expansion, multiple brands/stores, and very large catalogs. Its newer Product Catalog module is specifically designed around complex assortments, localization, pricing, and reuse of product data across markets/channels. commercetools commercetools commercetools

commercetools.com

Adobe Commerce is worth serious consideration if you need a powerful commerce application rather than wanting to build much of the commerce layer yourself. Adobe supports multiple brands/storefronts from a centralized administration layer and explicitly targets millions of SKUs, multiple regions, currencies, languages, inventory locations, and tax policies. Adobe for Business Adobe for Business

business.adobe.com

When I'd choose the others

• SAP Commerce Cloud — particularly compelling if you're already deeply invested in SAP. It supports multicountry/multicurrency catalogs and localized storefronts, while SAP's broader commerce stack is designed for complex enterprise processes. SAP
• Salesforce Commerce Cloud — investigate if Salesforce CRM, Service Cloud, Marketing Cloud, etc. already form the center of your customer architecture. That existing ecosystem can materially change the integration equation.
• VTEX — interesting if you need a combination of international commerce, B2B/B2C, marketplace, and unified commerce functionality rather than wanting to construct every component independently.

The architecture I'd use as the decision filter

With your description, I'd explicitly evaluate:

PIM → Commerce → Pricing → Inventory/OMS → ERP → Tax → Payments → Search → CMS → Analytics

rather than treating ecommerce as a single application.

For example, if your thousands of SKUs have complicated attributes, regional assortments, localized content, customer-specific pricing, bundles, or different availability by country, catalog architecture becomes just as important as the storefront. commercetools, Adobe, and SAP all have capabilities aimed at this kind of complexity. commercetools Adobe for Business SAP

And don't underestimate the operating-model question: current enterprise-platform research consistently highlights that composable platforms give engineering teams substantially more architectural freedom, but also shift more integration and operational responsibility onto that team. CIOPages Elogic Commerce

If you tell me your ERP (SAP/Oracle/Dynamics/etc.), number of markets, B2B vs B2C mix, approximate SKU count, and whether you want headless/composable, I can narrow this to a 2–3 platform shortlist and map the architecture/integration tradeoffs.

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you need a composable commerce architecture or a more integrated enterprise suite. Enterprise platforms differ significantly in how they handle catalogs, pricing engines, integrations, localization, and operational governance. CIOPages

My shortlist would be:

Based on your description, I would typically evaluate in this order

1. commercetools — if you have a mature engineering/platform team and want maximum flexibility across markets, brands, channels, and integrations. Shopify
2. SAP Commerce Cloud — if your backbone is SAP ERP and commerce needs to closely mirror enterprise product, pricing, inventory, and customer processes. Shopify
3. Adobe Commerce — if you need deep customization and own a lot of unique commerce logic. CIOPages
4. Salesforce Commerce Cloud — if customer data, CRM workflows, and Salesforce ecosystem integration are central. CIOPages
5. Shopify Plus — if your complexity is more operational scale than unusual business logic. Shopify

For a thousand-SKU-plus enterprise stack, I would specifically check:

• Catalog model

• Can it handle variants, bundles, configurable products, regional assortments, and multiple catalogs?
• Pricing

• Contract pricing, customer-specific pricing, currencies, promotions, rebates, and negotiated terms.
• Integration architecture

• ERP (SAP/Oracle/Dynamics/NetSuite), PIM, OMS, WMS, tax, payments, marketplaces.
• Multi-market operations

• Languages, currencies, taxes, compliance, inventory allocation, localized checkout.
• Deployment model

• SaaS convenience vs. composable flexibility.
• Governance

• Roles, approvals, audit trails, release processes, environment management.

A common enterprise pattern today is:

• PIM for product truth (e.g., product data)
• ERP for inventory/financial truth
• Commerce platform for transactions, pricing, and customer experience
• CMS/search/personalization as separate services in a composable stack

If you share:

1. B2B, B2C, or both
2. Current ERP/PIM (SAP, Oracle, Dynamics, NetSuite, Akeneo, etc.)
3. Approximate SKU count (5k vs 500k changes the answer)
4. Number of markets/storefronts
5. Whether you have an internal engineering team

…I can narrow this to a more realistic 2–3 platform shortlist.

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

My shortlist

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

For your particular description, I'd start with commercetools

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

commercetools.com

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

I'd favor it particularly if you have:

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

When I'd choose Adobe Commerce instead

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

business.adobe.com

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

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

One architectural point I'd strongly recommend

Don't evaluate this as simply:

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

Almost all serious enterprise platforms can.

Instead, map your architecture like:

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

Then ask each vendor:

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

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

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

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

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

Almost all serious enterprise platforms can.

Instead, map your architecture like:

For an enterprise team with complex integrations, thousands of SKUs, and multiple markets, I’d avoid choosing purely on storefront features. The important question is which platform can become the commerce orchestration layer between your ERP/PIM/OMS/CRM/payment stack and all your regional storefronts and channels.

My shortlist

Current enterprise comparisons broadly put commercetools/VTEX in the composable category, while Adobe, Salesforce and SAP are stronger choices when the surrounding enterprise stack or B2B requirements drive the architecture. CIOPages Elastic Path

My first choice for your description: commercetools

If by "complex integrations" you mean things like:

• ERP + PIM + OMS + CRM
• multiple countries/currencies/tax regimes
• localized pricing and assortments
• thousands or millions of SKUs
• multiple brands/storefronts
• marketplaces and other channels
• headless/custom front ends
• frequent integration changes
• a serious internal engineering team

I'd put commercetools at the top of the RFP.

Its architecture is explicitly designed around API-driven, composable commerce, and the vendor specifically positions it for millions of SKUs, multiple brands/stores, international expansion and integration with ERP/CRM systems. commercetools

commercetools.com

The tradeoff is important: composable doesn't eliminate complexity; it moves complexity into your architecture. If you have a strong platform engineering/integration team, that's often a good trade. If you don't, an integrated platform can be substantially easier to operate. CIOPages

When I'd choose Adobe Commerce instead

I'd move Adobe Commerce to #1 if your complexity is primarily catalog + B2B business rules rather than architecture.

For example, if you need:

• customer-specific catalogs
• contract pricing
• account/company hierarchies
• quotes
• SKU-based quick ordering
• complicated product relationships
• many websites with different catalogs/prices
• extensive customization

Adobe has particularly mature functionality here. Its B2B implementation supports shared catalogs, company-specific pricing, quotes and quick ordering, while a single installation can support multiple websites/stores/store views. Experience League Experience League

One caveat for your "thousands of SKUs" comment: Adobe itself warns that additional websites/stores expand catalog data and can increase indexing time and response times, so I'd want to validate your actual SKU × market × price × customer-segment matrix, not just the raw SKU count. Experience League

experienceleague.adobe.com

VTEX deserves a serious look

I'd put VTEX particularly high if you're operating lots of countries and/or marketplaces and want more functionality packaged together rather than assembling a large composable stack.

It's especially interesting if your requirements include marketplaces, sellers, omnichannel and international expansion alongside conventional D2C/B2B commerce. Guideflow

The architecture I'd actually evaluate

For an enterprise like yours, I wouldn't evaluate these as simply "which ecommerce website is best?"

I'd map something closer to:

ERP → PIM → Commerce platform → OMS → Payments / tax / shipping
↓
Search / personalization
↓
Regional storefronts + marketplaces

The key architectural question is where the system of record lives for product, price, inventory, customer and order data.

For example, I would not want the commerce platform becoming an accidental master database for 5,000 SKUs, 30 countries, 12 price lists, 8 customer segments and several ERP instances just because it can technically store all of it.

My ranking for your stated situation

1. commercetools — if you have strong engineering/integration capabilities.
2. VTEX — if global/multi-market and marketplace operations are particularly important.
3. Adobe Commerce — if catalog/B2B complexity and customization dominate.
4. Salesforce Commerce — if Salesforce is already deeply embedded.
5. Shopify Plus — if reducing operational complexity is more important than architectural flexibility.
6. SAP Commerce Cloud — if SAP is the unavoidable center of your enterprise architecture.

I wouldn't make the decision from the SKU count alone. "5,000 SKUs across 20 markets with relatively identical pricing" is a much easier problem than "5,000 SKUs × 20 markets × 15 customer segments × localized catalogs × ERP-derived pricing."

If you give me your number of markets, approximate SKU count, B2B vs B2C split, ERP/PIM/OMS (e.g. SAP, Dynamics, NetSuite, Akeneo), and whether you have an internal engineering team, I can narrow this to a 2–3 platform shortlist and lay out the target architecture + integration model.

It's especially interesting if your requirements include marketplaces, sellers, omnichannel and international expansion alongside conventional D2C/B2B commerce. Guideflow

The architecture I'd actually evaluate

For an enterprise like yours, I wouldn't evaluate these as simply "which ecommerce website is best?"

I'd map something closer to:

ERP → PIM → Commerce platform → OMS → Payments / tax / shipping
↓
Search / personalization
↓
Regional storefronts + marketplaces

The key architectural question is where the system of record lives for product, price, inventory, customer and order data.

For example, I would not want the commerce platform becoming an accidental master database for 5,000 SKUs, 30 countries, 12 price lists, 8 customer segments and several ERP instances just because it can technically store all of it.

My ranking for your stated situation

1. commercetools — if you have strong engineering/integration capabilities.
2. VTEX — if global/multi-market and marketplace operations are particularly important.
3. Adobe Commerce — if catalog/B2B complexity and customization dominate.
4. Salesforce Commerce — if Salesforce is already deeply embedded.
5. Shopify Plus — if reducing operational complexity is more important than architectural flexibility.
6. SAP Commerce Cloud — if SAP is the unavoidable center of your enterprise architecture.

I wouldn't make the decision from the SKU count alone. "5,000 SKUs across 20 markets with relatively identical pricing" is a much easier problem than "5,000 SKUs × 20 markets × 15 customer segments × localized catalogs × ERP-derived pricing."

If you give me your number of markets, approximate SKU count, B2B vs B2C split, ERP/PIM/OMS (e.g. SAP, Dynamics, NetSuite, Akeneo), and whether you have an internal engineering team, I can narrow this to a 2–3 platform shortlist and lay out the target architecture + integration model.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d avoid choosing based on storefront features alone. Your architecture, catalog model, integration layer, and ability to operate the platform at scale matter more.

My shortlist would be:

My recommendation: commercetools vs. Adobe Commerce

For the profile you described, I'd start with these two.

Choose commercetools if you have a substantial engineering/architecture organization and expect commerce to be one component of a broader platform. Its composable, API-first approach is particularly well suited to separating commerce from PIM, search, CMS, pricing, OMS, payments, and custom services. The tradeoff is that you're taking responsibility for more architecture and implementation yourself. CIOPages Elastic Path

Choose Adobe Commerce if you want more commerce functionality in the platform itself—particularly complex catalogs, customer-specific pricing, B2B workflows, multiple storefronts, and customization. Adobe specifically supports multiple brands/geographies from one administration layer and says its architecture can manage millions of SKUs. Adobe for Business

Where BigCommerce fits

I'd put BigCommerce Enterprise high on the list if your goal is "we need enterprise scale and integrations, but we don't want to build an entire commerce platform ourselves." Its Multi-Storefront capabilities support localized product information and international experiences, while its APIs make headless/integration-heavy architectures feasible. BigCommerce

One important distinction

"Thousands of SKUs" by itself isn't the hard part.

I'd evaluate platforms based on whether you have:

• Multiple countries/currencies/languages
• Country-specific catalogs and assortment
• Customer-specific pricing
• Multiple ERP instances
• PIM → commerce → marketplace feeds
• OMS/inventory synchronization
• Complex promotions
• B2B account hierarchies and approvals
• Multiple brands/storefronts
• Marketplaces or wholesale channels
• Regional tax/payment/shipping requirements
• Real-time inventory/pricing requirements
• A need to launch new markets without engineering every time

If most of those are true, I'd lean commercetools or Adobe Commerce, rather than Shopify Plus.

If you tell me your ERP (SAP/Oracle/Dynamics/etc.), PIM, number of markets, B2B vs. B2C mix, approximate SKU count, and whether you have 5 vs. 50+ engineers, I can give you a much more opinionated architecture recommendation and a commercetools vs. Adobe vs. BigCommerce vs. Shopify Plus scorecard.

Choose commercetools if you have a substantial engineering/architecture organization and expect commerce to be one component of a broader platform. Its composable, API-first approach is particularly well suited to separating commerce from PIM, search, CMS, pricing, OMS, payments, and custom services. The tradeoff is that you're taking responsibility for more architecture and implementation yourself. CIOPages Elastic Path

Choose Adobe Commerce if you want more commerce functionality in the platform itself—particularly complex catalogs, customer-specific pricing, B2B workflows, multiple storefronts, and customization. Adobe specifically supports multiple brands/geographies from one administration layer and says its architecture can manage millions of SKUs.

Where BigCommerce fits

I'd put BigCommerce Enterprise high on the list if your goal is "we need enterprise scale and integrations, but we don't want to build an entire commerce platform ourselves." Its Multi-Storefront capabilities support localized product information and international experiences, while its APIs make headless/integration-heavy architectures feasible.

One important distinction

"Thousands of SKUs" by itself isn't the hard part.

I'd evaluate platforms based on whether you have:

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d avoid choosing primarily on storefront features. The key question is how well the platform can become the commerce orchestration layer between your ERP/PIM/OMS/CRM, payment systems, tax, marketplaces, and regional storefronts.

My shortlist would be:

Current enterprise comparisons similarly put commercetools, Adobe, Salesforce, SAP, Shopify, BigCommerce and VTEX into the serious enterprise consideration set, but their architectural tradeoffs are quite different. CIOPages Virto Commerce

What I'd pick for your description

1. commercetools — if your integration architecture is genuinely complex

This would be my first technical evaluation if you have a strong engineering organization.

It's API-first/composable, so you can keep your PIM, ERP, OMS, search, CMS, pricing engine, identity, and frontend as independent systems rather than forcing everything into the commerce platform. That's particularly attractive when you have many markets and channels that need different experiences. CIOPages Naturaily

The catch: composable means you own more architecture. If your team doesn't want to build and operate significant commerce infrastructure, it can become expensive and slow.

2. Adobe Commerce — if catalog/business-rule complexity is the harder problem

I'd strongly consider Adobe if "thousands of SKUs" actually means things like:

• complicated product configurations
• customer-specific pricing
• multiple price lists
• B2B account hierarchies
• approval workflows
• negotiated pricing/RFQ
• complicated promotions
• extensive ERP integration
• substantial customization

Adobe's strength is that much of this commerce functionality is closer to the platform rather than something you have to assemble yourself. Elogic Commerce Elogic Commerce

3. VTEX — particularly interesting for multi-market/multi-brand operations

I'd put VTEX high on the list if you're operating numerous countries, brands, marketplaces, or sales channels. It combines composable elements with more packaged commerce functionality, including marketplace capabilities. CIOPages Virto Commerce

Where Shopify Plus fits

I wouldn't dismiss Shopify Plus just because you're enterprise.

It's actually compelling if your primary objective is running lots of markets without owning lots of infrastructure. Shopify has pushed considerably further into enterprise international commerce, including its Managed Markets capabilities. Shopify

But I'd be more cautious if your thousands of SKUs come with very complicated product/pricing/ordering rules rather than simply a large catalog.

The architecture I'd aim for

For your situation, I would generally want something like:

PIM → Commerce Platform → OMS → ERP

with:

CMS / Search / Pricing / Tax / Payments / DAM / CDP / Marketplaces

connected through APIs/event infrastructure rather than making the ecommerce platform the master system for everything.

That distinction matters enormously. 10,000 SKUs isn't necessarily difficult. Ten thousand SKUs × 30 countries × 8 price lists × customer-specific pricing × localized attributes × ERP inventory × marketplace feeds is difficult.

My recommended evaluation

I'd probably run a serious bake-off between:

1. commercetools
2. Adobe Commerce
3. VTEX
4. Salesforce Commerce Cloud — if you're heavily invested in Salesforce
5. Shopify Plus — as the "simpler architecture" control case

And I'd make vendors demonstrate your actual integration architecture, not a generic demo.

The most important POC would be: one product → one customer → one order → one ERP → one fulfillment flow across two different countries, including localized catalog, inventory, pricing, tax, payment, promotions, returns and order changes.

That will reveal much more than a standard feature checklist.

If you tell me B2B vs B2C, approximate SKU count, number of countries/markets, ERP/PIM/OMS (e.g. SAP, Oracle, Akeneo, Salsify), and whether you have a 10+ person engineering team, I can narrow this to a top 2–3 architecture and give you a vendor scorecard.

The architecture I'd aim for

For your situation, I would generally want something like:

PIM → Commerce Platform → OMS → ERP

with:

CMS / Search / Pricing / Tax / Payments / DAM / CDP / Marketplaces

connected through APIs/event infrastructure rather than making the ecommerce platform the master system for everything.

That distinction matters enormously. 10,000 SKUs isn't necessarily difficult. Ten thousand SKUs × 30 countries × 8 price lists × customer-specific pricing × localized attributes × ERP inventory × marketplace feeds is difficult.

My recommended evaluation

I'd probably run a serious bake-off between:

For an enterprise team with thousands of SKUs, multiple markets, and complex integrations, I’d avoid choosing purely on storefront features. Your architecture, catalog model, ERP/PIM/OMS integrations, localization, and ability to operate the platform at scale matter more.

My shortlist

Current enterprise comparisons similarly put commercetools at the composable end, Adobe/SAP/Salesforce toward more integrated enterprise stacks, and Shopify/BigCommerce toward easier-to-operate SaaS. CIOPages Elastic Path

What I'd choose for your situation

1. commercetools — if your engineering organization is strong

This would be my first evaluation if "complex integrations" is the defining requirement. It is API-first and composable, so you can treat commerce as one part of a broader architecture rather than forcing ERP, PIM, search, CMS, pricing, payments, etc. into one platform. commercetools specifically positions itself for millions of SKUs, multiple brands/stores, international expansion, and integration with ERP/CRM systems. Commercetools commercetools Documentation

The catch is important: you are buying architectural freedom, not a turnkey ecommerce application. Your team/SI has to build and operate more of the surrounding system.

2. Adobe Commerce — if you want more functionality out of the box

I'd put Adobe very close to commercetools for your use case. Its multi-site architecture is specifically designed for multiple brands, regions and storefronts, and Adobe says its platform can manage millions of SKUs across brands and regions. Adobe Business Adobe Business

I'd favor it when you have requirements like sophisticated catalog rules, customer-specific pricing, B2B workflows, promotions, and extensive customization, but don't want to assemble quite as much commerce functionality yourself.

3. SAP Commerce Cloud — if you're already deeply invested in SAP

If your architecture is SAP S/4HANA-centric and ecommerce is essentially a digital channel on top of that ecosystem, SAP Commerce deserves a serious evaluation. The integration architecture and organizational familiarity can outweigh the advantages of moving to a more fashionable composable stack. Elastic Path

The architecture I'd evaluate

For thousands of SKUs, I wouldn't make the ecommerce platform the master of everything.

A typical enterprise architecture I'd want to evaluate looks roughly like:

ERP → inventory, orders, financial/product master data
PIM → product enrichment, attributes, localization
Commerce → carts, checkout, pricing, promotions, customer experience
OMS → fulfillment/order orchestration
Search → product discovery
CMS → content/experience
CDP/CRM → customer data/personalization
Integration layer/event bus → synchronization and orchestration

That distinction becomes particularly important with composable commerce: commercetools itself recommends explicitly determining whether the PIM or ERP owns each piece of product information rather than treating the commerce platform as the universal source of truth. commercetools Documentation

My decision rule

I'd narrow it to:

• commercetools if you have a mature engineering/integration team and expect the architecture to keep evolving.
• Adobe Commerce if you need substantial native commerce/B2B functionality and customization.
• SAP Commerce Cloud if SAP is deeply embedded in your business processes.
• Salesforce Commerce Cloud if Salesforce is already your dominant customer/CRM ecosystem.
• Shopify Plus if operational simplicity and speed outweigh extreme architectural flexibility.
• BigCommerce Enterprise if you want a relatively straightforward SaaS platform while retaining stronger API/headless flexibility.

One particularly important warning: don't let "thousands of SKUs" drive the decision by itself. Thousands of SKUs is easy for modern enterprise platforms. The harder questions are how many product attributes/variants, how many price lists, how many markets, how many currencies/tax regimes, how many customer-specific catalogs, how frequently inventory changes, and how many systems need real-time synchronization. Those determine the architecture.

If you give me your ERP/PIM/OMS stack, approximate SKU count, number of countries/markets, B2B vs B2C mix, and whether you have a large in-house engineering team, I can turn this into a much more specific enterprise platform scorecard and shortlist.

1. commercetools — if your engineering organization is strong

This would be my first evaluation if "complex integrations" is the defining requirement. It is API-first and composable, so you can treat commerce as one part of a broader architecture rather than forcing ERP, PIM, search, CMS, pricing, payments, etc. into one platform. commercetools specifically positions itself for millions of SKUs, multiple brands/stores, international expansion, and integration with ERP/CRM systems. Commercetools commercetools Documentation

The catch is important: you are buying architectural freedom, not a turnkey ecommerce application. Your team/SI has to build and operate more of the surrounding system.

2. Adobe Commerce — if you want more functionality out of the box

I'd put Adobe very close to commercetools for your use case. Its multi-site architecture is specifically designed for multiple brands, regions and storefronts, and Adobe says its platform can manage millions of SKUs across brands and regions. Adobe Business Adobe Business

I'd favor it when you have requirements like sophisticated catalog rules, customer-specific pricing, B2B workflows, promotions, and extensive customization, but don't want to assemble quite as much commerce functionality yourself.

3. SAP Commerce Cloud — if you're already deeply invested in SAP

If your architecture is SAP S/4HANA-centric and ecommerce is essentially a digital channel on top of that ecosystem, SAP Commerce deserves a serious evaluation. The integration architecture and organizational familiarity can outweigh the advantages of moving to a more fashionable composable stack. Elastic Path

The architecture I'd evaluate

For thousands of SKUs, I wouldn't make the ecommerce platform the master of everything.

A typical enterprise architecture I'd want to evaluate looks roughly like:

ERP → inventory, orders, financial/product master data
PIM → product enrichment, attributes, localization
Commerce → carts, checkout, pricing, promotions, customer experience
OMS → fulfillment/order orchestration
Search → product discovery
CMS → content/experience
CDP/CRM → customer data/personalization
Integration layer/event bus → synchronization and orchestration

That distinction becomes particularly important with composable commerce: commercetools itself recommends explicitly determining whether the PIM or ERP owns each piece of product information rather than treating the commerce platform as the universal source of truth.

My decision rule

I'd narrow it to:

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely multiple brands/channels, I’d shortlist these rather than defaulting to a simpler SMB platform.

My first choice: commercetools

Based on the characteristics you gave, I'd put commercetools at the top of the evaluation list.

The key distinction is architectural. Instead of making the commerce platform the center of everything, you can treat it as a commerce capability within your broader enterprise architecture. Its APIs and composable approach are specifically designed to integrate with ERP, CRM and other systems, while its enterprise offering explicitly targets multiple brands, stores and international markets. Commercetools Commercetools

That matters if you have something like:

PIM → Commerce → OMS → ERP → WMS → tax → payments → search → CDP/CRM → marketplaces

rather than wanting your ecommerce platform to own every piece.

commercetools also currently claims infrastructure capable of handling millions of SKUs and very high transaction volumes, so "thousands of SKUs" shouldn't be remotely close to its architectural ceiling. Commercetools Commercetools

When I'd choose Shopify Plus instead

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

• getting markets live quickly
• minimizing platform engineering
• having a mature ecosystem of integrations
• centralized administration
• international localization
• B2B + D2C
• letting your team spend more time on merchandising and growth than infrastructure

Shopify's current Markets functionality supports market-specific catalogs, pricing, currencies, languages, domains and fulfillment configuration. Plus also supports expansion stores and extensive API/customization capabilities. Shopify Shopify Help Center Shopify Help Center

The question I'd ask isn't "Can Shopify handle thousands of SKUs?" It can.

I'd ask "How much of our business logic are we comfortable adapting to Shopify's model?"

That's where the difference between Shopify Plus and commercetools becomes much more important.

A useful decision rule

I'd roughly frame it this way:

• High integration complexity + highly customized business rules + many markets/channels → commercetools
• High complexity but Shopify-compatible operating model + speed is paramount → Shopify Plus
• Deep Adobe investment → Adobe Commerce
• Deep Salesforce investment → Salesforce Commerce Cloud
• Deep SAP investment → SAP Commerce Cloud

One other important consideration: don't evaluate the commerce engine in isolation. With thousands of SKUs, your PIM, search, pricing, inventory, order management, localization and integration architecture can matter more than the storefront itself.

If you tell me (1) B2B vs B2C, (2) number of countries/markets, (3) current ERP/PIM/OMS, (4) number of storefronts/brands, and (5) whether you have a substantial engineering team, I can narrow this to a 2–3 platform recommendation and a reference architecture for your environment.

rather than wanting your ecommerce platform to own every piece.

commercetools also currently claims infrastructure capable of handling millions of SKUs and very high transaction volumes, so "thousands of SKUs" shouldn't be remotely close to its architectural ceiling.

When I'd choose Shopify Plus instead

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

For an enterprise team with thousands of SKUs, complex integrations, multiple countries/markets, and likely significant customization, I’d shortlist these rather than treating all ecommerce platforms equally:

My recommendation

Given the specific combination of complex integrations + thousands of SKUs + multi-market, I'd put commercetools, Adobe Commerce, and Shopify Plus at the top of the evaluation.

1. commercetools — if engineering flexibility is paramount

This is the one I'd investigate first if you have a strong internal engineering/platform team. Its composable/API-first approach makes it well suited to situations where your ERP, PIM, OMS, search, pricing, CMS, checkout, and storefront need to evolve independently.

The downside is important: you're taking on more architecture and integration responsibility. Composable commerce can be extremely powerful, but you're effectively operating a commerce platform rather than buying a turnkey ecommerce system.

2. Adobe Commerce — if catalog/B2B complexity is the bigger problem

Adobe is particularly compelling when you have complicated product structures, customer-specific pricing, multiple brands/sites, B2B workflows, and lots of business rules. Adobe explicitly supports multiple websites/stores/store views, and its B2B functionality includes shared catalogs, company-specific pricing, quotes, and SKU-based quick ordering. Experience League Experience League

Adobe also specifically positions Commerce for multi-brand/multi-storefront operations and very large catalogs. Adobe Business

The caveat is scale architecture: Adobe notes that additional stores increase catalog data and can increase indexing/response overhead, so I'd want your implementation partner to demonstrate the architecture against your actual SKU/store/channel volumes, rather than relying on generic scalability claims. Experience League

3. Shopify Plus — if you want to reduce platform complexity

Don't dismiss Shopify Plus because you're enterprise. Its Markets architecture now supports market-specific catalogs, pricing, currencies, languages, domains, product availability, and B2B market configurations. Plus also supports unlimited catalogs and direct catalog assignment to company locations. Shopify Shopify Help Center

That makes it attractive if your complexity is primarily integration complexity rather than extremely unusual commerce logic. You can let Shopify handle more of the commodity commerce infrastructure and concentrate your engineering effort on integrations and differentiated experiences.

The tradeoff is that once your requirements become highly customized—especially around complex pricing, product relationships, checkout/order orchestration, or unusual business processes—you may find yourself working around the platform rather than extending it.

The architecture I'd seriously consider

For your description, I wouldn't necessarily look for one system to do everything.

I'd consider:

ERP → PIM → commerce platform → OMS/fulfillment
↕
Search / CMS / CDP / pricing
↕
Regional storefronts

And put an integration/event layer between the major systems rather than creating dozens of point-to-point integrations.

That architecture makes the choice of commerce platform much more consequential: commercetools becomes particularly attractive if you want each component to remain independently replaceable; Adobe Commerce if you want more functionality consolidated into commerce; Shopify Plus if you want the commerce layer itself to require less operational ownership.

What I'd use as the deciding criteria

For a team like yours, I'd weight the evaluation roughly:

• 25% — integration architecture/API/event capabilities
• 20% — catalog/PIM complexity and SKU performance
• 15% — multi-market pricing, currencies, tax, localization
• 15% — order/OMS/ERP integration
• 10% — B2B/customer-specific catalogs and pricing
• 10% — operational scalability and reliability
• 5% — merchandising/admin usability

I would not make storefront design, built-in marketing features, or the number of apps/integrations the primary decision criteria. Those are relatively easy compared with getting a 50-system enterprise integration architecture right.

If you tell me roughly (1) SKU count, (2) number of countries/sites, (3) B2C vs B2B, (4) ERP/PIM/OMS you use, and (5) whether you have a strong internal engineering team, I can narrow this to a 2–3 platform recommendation and proposed architecture for your situation.

This is the one I'd investigate first if you have a strong internal engineering/platform team. Its composable/API-first approach makes it well suited to situations where your ERP, PIM, OMS, search, pricing, CMS, checkout, and storefront need to evolve independently.

The downside is important: you're taking on more architecture and integration responsibility. Composable commerce can be extremely powerful, but you're effectively operating a commerce platform rather than buying a turnkey ecommerce system.

2. Adobe Commerce — if catalog/B2B complexity is the bigger problem

Adobe is particularly compelling when you have complicated product structures, customer-specific pricing, multiple brands/sites, B2B workflows, and lots of business rules. Adobe explicitly supports multiple websites/stores/store views, and its B2B functionality includes shared catalogs, company-specific pricing, quotes, and SKU-based quick ordering. Experience League Experience League

Adobe also specifically positions Commerce for multi-brand/multi-storefront operations and very large catalogs. Adobe Business

The caveat is scale architecture: Adobe notes that additional stores increase catalog data and can increase indexing/response overhead, so I'd want your implementation partner to demonstrate the architecture against your actual SKU/store/channel volumes, rather than relying on generic scalability claims. Experience League

3. Shopify Plus — if you want to reduce platform complexity

Don't dismiss Shopify Plus because you're enterprise. Its Markets architecture now supports market-specific catalogs, pricing, currencies, languages, domains, product availability, and B2B market configurations. Plus also supports unlimited catalogs and direct catalog assignment to company locations. Shopify Shopify Help Center

That makes it attractive if your complexity is primarily integration complexity rather than extremely unusual commerce logic. You can let Shopify handle more of the commodity commerce infrastructure and concentrate your engineering effort on integrations and differentiated experiences.

The tradeoff is that once your requirements become highly customized—especially around complex pricing, product relationships, checkout/order orchestration, or unusual business processes—you may find yourself working around the platform rather than extending it.

The architecture I'd seriously consider

For your description, I wouldn't necessarily look for one system to do everything.

I'd consider:

ERP → PIM → commerce platform → OMS/fulfillment
↕
Search / CMS / CDP / pricing
↕
Regional storefronts

And put an integration/event layer between the major systems rather than creating dozens of point-to-point integrations.

That architecture makes the choice of commerce platform much more consequential: commercetools becomes particularly attractive if you want each component to remain independently replaceable; Adobe Commerce if you want more functionality consolidated into commerce; Shopify Plus if you want the commerce layer itself to require less operational ownership.

What I'd use as the deciding criteria

For a team like yours, I'd weight the evaluation roughly:

• 25% — integration architecture/API/event capabilities
• 20% — catalog/PIM complexity and SKU performance
• 15% — multi-market pricing, currencies, tax, localization
• 15% — order/OMS/ERP integration
• 10% — B2B/customer-specific catalogs and pricing
• 10% — operational scalability and reliability
• 5% — merchandising/admin usability

I would not make storefront design, built-in marketing features, or the number of apps/integrations the primary decision criteria. Those are relatively easy compared with getting a 50-system enterprise integration architecture right.

If you tell me roughly (1) SKU count, (2) number of countries/sites, (3) B2C vs B2B, (4) ERP/PIM/OMS you use, and (5) whether you have a strong internal engineering team, I can narrow this to a 2–3 platform recommendation and proposed architecture for your situation.

Given enterprise complexity + thousands of SKUs + many integrations + multiple markets, I would not pick based primarily on storefront features. I’d optimize for catalog complexity, integration architecture, market localization, governance, and how much engineering ownership your team wants.

My shortlist

A current enterprise-platform comparison similarly puts Shopify, commercetools, Adobe Commerce, Salesforce Commerce Cloud and SAP Commerce among the major enterprise choices, with composable platforms trading operational simplicity for architectural flexibility. CIOPages Guideflow

My recommendation for your description

1. commercetools — if "complex integrations" is the defining requirement

I'd put commercetools at the top of the technical evaluation.

It's API-first/composable, so rather than forcing your ERP, PIM, OMS, search, CMS, pricing, etc. into one platform, you can build the commerce layer around the systems you already have. It is specifically designed around modular commerce capabilities and supports multi-region, multi-currency and multi-language setups. Shopify

That makes it particularly attractive if you have things like:

• SAP/Oracle/Dynamics ERP
• Dedicated PIM
• Multiple OMS/3PLs
• Complex pricing engines
• Multiple payment providers
• Multiple brands
• Different catalogs by country/channel/customer
• Headless storefronts
• Multiple web/app/marketplace experiences
• A substantial internal engineering team

Tradeoff: composable doesn't magically make things simpler. You're taking responsibility for architecture, integration orchestration, observability, deployment and some business logic that a suite might provide natively.

2. Shopify Plus — if you want to dramatically reduce platform operations

I'd choose Shopify Plus instead if your team wants to spend engineering capacity on the business rather than operating a commerce platform.

Shopify's current Markets functionality supports localized currencies, languages, domains, product availability, pricing and fulfillment configurations across markets. Shopify Shopify Help Center

For B2B, Plus also supports unlimited B2B market catalogs and direct catalog assignment to companies/company locations. Shopify Help Center Shopify Help Center

The question I'd investigate carefully is whether your catalog/pricing/order/integration model is more complex than Shopify's native abstractions want it to be.

If you're managing thousands of SKUs but the products themselves are relatively straightforward, Shopify can be excellent. If you're managing thousands of SKUs plus highly variable customer-specific pricing, assortments, product relationships, regional rules and ERP-driven availability, I'd lean toward commercetools or Adobe.

3. Adobe Commerce — if catalog/business-rule complexity is unusually high

I'd put Adobe Commerce high on the list if you have sophisticated B2B requirements and need a lot of control over:

• Websites/store views
• Catalogs
• Customer groups
• Pricing
• Promotions
• B2B workflows
• ERP integration
• Custom business logic

It's a particularly interesting middle ground: considerably more customizable than a pure SaaS approach without necessarily going all the way to a fully composable architecture.

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

If your customer, sales, service and marketing ecosystem is already Salesforce-centric, Commerce Cloud becomes much more compelling.

I'd primarily consider it when commerce is part of a larger Salesforce architecture, rather than choosing it solely because you need multi-market ecommerce.

The architecture I'd actually evaluate

For an enterprise like yours, I'd avoid thinking of this as:

"Which ecommerce platform should we buy?"

I'd frame it as:

ERP → PIM → Commerce → OMS → Payments/Tax → Search → Marketplaces → Analytics

with the ecommerce platform being one component.

For example:

                    ┌───────────────┐
                    │      ERP      │
                    └───────┬───────┘
                            │
                    ┌───────▼───────┐
                    │      PIM      │
                    └───────┬───────┘
                            │
        ┌───────────────────▼───────────────────┐
        │             COMMERCE                  │
        │                                       │
        │ catalog / pricing / cart / checkout  │
        │ customers / promotions / markets     │
        └───────┬───────────┬───────────┬───────┘
                │           │           │
             Search       OMS        Payments
                │           │           │
             Storefronts   3PLs      Tax/Fraud
                │
       ┌────────┼────────┐
       │        │        │
      US       EU       APAC

That architecture is where commercetools becomes particularly compelling, because it is designed to sit inside this kind of composable ecosystem.

One thing I'd pay special attention to

Don't confuse "thousands of SKUs" with "complex commerce."

10,000 relatively simple products isn't necessarily difficult.

2,000 products with:

• 30 customer-specific price lists
• regional assortment rules
• contract pricing
• inventory from multiple warehouses
• country-specific compliance
• multiple currencies
• bundles/configurations
• channel-specific availability
• ERP-controlled product data
• B2B account hierarchies
• different tax treatment
• multiple fulfillment models

…is much harder.

If that's closer to your environment, I'd rank the options:

commercetools → Adobe Commerce → Shopify Plus → Salesforce Commerce Cloud

If the integrations are numerous but relatively standardized and your priority is getting markets live quickly with minimal platform maintenance, I'd reverse the first two and consider:

Shopify Plus → commercetools → Adobe Commerce → Salesforce Commerce Cloud

If you tell me (1) B2B vs B2C, (2) approximate SKU count, (3) number of countries/markets, (4) ERP/PIM/OMS you're using, and (5) whether you have a large internal engineering team, I can give you a much more opinionated architecture recommendation and a Shopify Plus vs commercetools vs Adobe Commerce scorecard for your situation.

ERP → PIM → Commerce → OMS → Payments/Tax → Search → Marketplaces → Analytics

with the ecommerce platform being one component.

For example:

                    ┌───────────────┐
                    │      ERP      │
                    └───────┬───────┘
                            │
                    ┌───────▼───────┐
                    │      PIM      │
                    └───────┬───────┘
                            │
        ┌───────────────────▼───────────────────┐
        │             COMMERCE                  │
        │                                       │
        │ catalog / pricing / cart / checkout  │
        │ customers / promotions / markets     │
        └───────┬───────────┬───────────┬───────┘
                │           │           │
             Search       OMS        Payments
                │           │           │
             Storefronts   3PLs      Tax/Fraud
                │
       ┌────────┼────────┐
       │        │        │
      US       EU       APAC

That architecture is where commercetools becomes particularly compelling, because it is designed to sit inside this kind of composable ecosystem.

One thing I'd pay special attention to

Don't confuse "thousands of SKUs" with "complex commerce."

10,000 relatively simple products isn't necessarily difficult.

2,000 products with:

• 30 customer-specific price lists
• regional assortment rules
• contract pricing
• inventory from multiple warehouses
• country-specific compliance
• multiple currencies
• bundles/configurations
• channel-specific availability
• ERP-controlled product data
• B2B account hierarchies
• different tax treatment
• multiple fulfillment models

…is much harder.

If that's closer to your environment, I'd rank the options:

commercetools → Adobe Commerce → Shopify Plus → Salesforce Commerce Cloud

If the integrations are numerous but relatively standardized and your priority is getting markets live quickly with minimal platform maintenance, I'd reverse the first two and consider:

Shopify Plus → commercetools → Adobe Commerce → Salesforce Commerce Cloud

If you tell me (1) B2B vs B2C, (2) approximate SKU count, (3) number of countries/markets, (4) ERP/PIM/OMS you're using, and (5) whether you have a large internal engineering team, I can give you a much more opinionated architecture recommendation and a Shopify Plus vs commercetools vs Adobe Commerce scorecard for your situation.

For an enterprise team with thousands of SKUs, complex integrations, and multiple international markets, I’d narrow the field to commercetools, Adobe Commerce, Salesforce Commerce Cloud, and Shopify Plus. I would not start with a generic mid-market platform.

My shortlist

1. My first choice: commercetools

If by "complex integrations" you mean ERP + PIM + OMS + tax + payments + multiple warehouses + marketplaces + custom customer/account logic, I'd put commercetools at the top of the evaluation.

It's explicitly designed around composable architecture and enterprise-scale deployments, with cloud-native infrastructure that the vendor says is capable of handling millions of SKUs. Commercetools

The important distinction is that you're buying a commerce engine, not an all-in-one suite. That makes it particularly attractive if you already have—or want to build around—best-of-breed systems for:

• PIM
• ERP
• OMS
• search
• CMS/DXP
• pricing
• promotions
• tax
• payments
• customer data

The tradeoff is substantial: your engineering organization owns more of the architecture.

commercetools.com

2. Adobe Commerce

I'd put Adobe Commerce very close to commercetools if your requirements are more catalog-, pricing-, merchandising-, or B2B-heavy.

Adobe has a mature multi-site model: one installation can support multiple websites, stores and store views, with different languages, domains, currencies, catalogs and configurations. Experience League Experience League

It also has unusually useful native inventory architecture for complex organizations. You can map websites to stocks and multiple physical sources such as warehouses, stores and dropshippers. Experience League Experience League

That's compelling if you have something like:

Global catalog → regional catalogs → country storefronts → regional inventory → localized pricing/promotions → shared ERP/PIM/OMS

The downside is that Adobe can become very implementation-heavy. Its multi-store architecture also requires careful performance planning as catalog/site complexity grows; Adobe itself warns that additional stores can increase catalog indexing time and affect response times. Experience League

business.adobe.com

3. Salesforce Commerce Cloud

I'd choose this primarily when Salesforce is already strategically important to the business.

If you're deeply invested in Salesforce CRM, Marketing Cloud, Service Cloud, CDP/Data Cloud, etc., the integration and organizational benefits can outweigh the architectural advantages of a more headless/composable platform.

I'd be less inclined to choose it if you're trying to build a highly independent commerce architecture around an existing SAP/Oracle/custom ecosystem.

salesforce.com

4. Shopify Plus

Don't dismiss Shopify Plus simply because you're an enterprise.

For organizations where the main objective is global expansion without maintaining a huge commerce infrastructure, it's extremely compelling. Shopify's current enterprise offering supports B2B, DTC and POS, and its Managed Markets product is designed for international selling. Shopify

I'd choose Shopify Plus over commercetools/Adobe when:

• the commerce experience isn't radically bespoke;
• you want faster market launches;
• you want SaaS rather than infrastructure ownership;
• your integrations can be cleanly handled through APIs/events/middleware;
• your organization values operational simplicity over maximum architectural control.

I'd hesitate if you have very unusual pricing, product configuration, order orchestration, account hierarchies, or transaction workflows that don't map cleanly to Shopify's model.

shopify.com

What I'd actually recommend for your situation

Given just the description you gave, I'd run an RFP with:

1. commercetools
2. Adobe Commerce
3. Shopify Plus
4. Salesforce Commerce Cloud

And I'd make the decision based less on "how many SKUs can it handle?" and more on where the complexity lives.

For example:

• Complex integrations + strong engineering team → commercetools
• Complex catalog/B2B/merchandising + customization → Adobe Commerce
• Salesforce is the center of gravity → Salesforce Commerce Cloud
• Global expansion + speed + lower operational burden → Shopify Plus

One architectural point I'd emphasize: don't make the ecommerce platform your PIM, ERP, OMS, or master data system just because it technically can hold that information. With thousands of SKUs and multiple markets, I'd generally want a clean architecture where commerce is the transactional/customer-facing layer and specialized systems own their respective domains.

If you tell me your SKU count, number of markets/stores, B2B vs B2C mix, ERP/PIM/OMS (e.g. SAP, Oracle, Akeneo, Salsify), and approximate annual GMV/orders, I can give you a much more opinionated 2–3 platform recommendation and target architecture.

Global catalog → regional catalogs → country storefronts → regional inventory → localized pricing/promotions → shared ERP/PIM/OMS

The downside is that Adobe can become very implementation-heavy. Its multi-store architecture also requires careful performance planning as catalog/site complexity grows; Adobe itself warns that additional stores can increase catalog indexing time and affect response times. Experience League

business.adobe.com

3. Salesforce Commerce Cloud

I'd choose this primarily when Salesforce is already strategically important to the business.

If you're deeply invested in Salesforce CRM, Marketing Cloud, Service Cloud, CDP/Data Cloud, etc., the integration and organizational benefits can outweigh the architectural advantages of a more headless/composable platform.

I'd be less inclined to choose it if you're trying to build a highly independent commerce architecture around an existing SAP/Oracle/custom ecosystem.

salesforce.com

4. Shopify Plus

Don't dismiss Shopify Plus simply because you're an enterprise.

For an enterprise team with complex integrations, thousands of SKUs, and multiple markets, I’d narrow the field to commercetools, Adobe Commerce, Shopify Plus, Salesforce Commerce Cloud, and SAP Commerce Cloud. The right choice depends less on SKU count itself and more on how complex your catalog, pricing, ERP/OMS, localization, and business rules are.

My shortlist

1. 🥇 commercetools — if integrations and architecture are your priority

commercetools would be my first platform to evaluate if you have a strong engineering organization.

It's particularly attractive when you need to connect commerce deeply to ERP, PIM, OMS, pricing engines, search, customer data, marketplaces, and bespoke services rather than having the commerce platform dictate your architecture. Independent research also puts commercetools at the high end of architectural freedom for enterprise commerce. CIOPages Elastic Path

Choose it if:

• You already operate a sophisticated integration/API layer.
• Different markets have substantially different business rules.
• Your catalog/pricing model is complicated.
• You want headless/composable architecture.
• Your engineering team is comfortable owning more of the solution.

Tradeoff: composable commerce gives you tremendous flexibility, but you are assembling and operating more pieces yourself.

2. 🥈 Adobe Commerce — probably the safest enterprise shortlist

Adobe Commerce is particularly compelling when you have lots of SKUs, complex product relationships, multiple storefronts, B2B requirements, multiple warehouses, and market-specific pricing/catalogs.

Adobe supports multiple websites/stores from one Commerce instance, with different products, categories, currencies, languages, domains, etc. Experience League Its inventory system also supports multi-source networks spanning warehouses, stores, drop shippers and fulfillment locations. Experience League Experience League

I'd favor Adobe over Shopify if your requirements look like:

"One global commerce engine, but Germany needs different products/prices/tax rules, the US has different fulfillment, B2B customers get negotiated pricing, and our ERP/OMS/PIM all have to remain authoritative."

That's exactly the kind of complexity where Adobe starts making sense.

Big caveat: Adobe's flexibility can become implementation complexity. Its own documentation warns that adding many websites/stores expands catalog data and can affect indexing/performance, so architecture matters at your scale. Experience League

3. 🥉 Shopify Plus — best if operational simplicity matters

Shopify Plus is much more enterprise-capable than its historical reputation suggests.

Its Markets functionality supports market-specific currency, language, domains, catalogs, pricing, product availability, shipping, taxes/duties and localization. Shopify Plus also supports unlimited catalogs and direct catalog assignment to B2B company locations. Shopify Help Center Shopify Help Center

I'd choose Shopify Plus when the requirement is:

"We want sophisticated integrations and global commerce, but we don't want our team spending its life maintaining the commerce platform."

That's a very different proposition from commercetools.

Shopify currently supports up to 50 markets natively, with additional approaches available when you need more. Shopify Help Center

Where I'd hesitate: extremely complicated pricing logic, product models, checkout behavior, or business processes that don't map cleanly onto Shopify's model. You can extend Shopify substantially, but eventually you're fighting the platform rather than leveraging it.

What I'd choose for your situation

Based solely on "enterprise + complex integrations + thousands of SKUs + multi-market", my initial ranking would be:

1. commercetools — if you have a strong engineering/platform team
2. Adobe Commerce — if you want a powerful enterprise commerce application with substantial native functionality
3. Shopify Plus — if reducing operational complexity and accelerating market launches is more important
4. Salesforce Commerce Cloud — if Salesforce is already deeply embedded
5. SAP Commerce Cloud — if SAP is the backbone of your product/order/customer ecosystem

One important distinction: thousands of SKUs isn't particularly scary for these platforms. I'd focus the evaluation on the complexity around those SKUs: variants, bundles/configurators, regional assortment, customer-specific pricing, inventory sources, translations, tax, promotions, subscriptions, B2B contracts, and how many systems can modify product/order data.

The architecture I'd investigate

For a sophisticated enterprise, I'd avoid making the commerce platform the master of everything:

PIM → Commerce → OMS → ERP/WMS

with things like:

Search | CDP/CRM | Tax | Payments | Pricing | DAM | Marketplaces

connected through an API/event layer.

That architecture makes commercetools particularly attractive, while Adobe Commerce is compelling if you want more of that functionality consolidated into the commerce platform.

If you tell me your ERP (SAP/NetSuite/Dynamics/etc.), PIM, OMS, number of countries/markets, B2B vs B2C, and whether you have a large engineering team, I can narrow this to a 2–3 platform recommendation and give you an enterprise evaluation scorecard.

For an enterprise team with complex integrations and thousands of SKUs, I’d narrow the field to commercetools, VTEX, Shopify Plus, and Adobe Commerce. The right choice depends heavily on whether your complexity is primarily technical/integration, B2B, international/multi-market, or catalog/merchandising.

My shortlist

1. My default recommendation: commercetools

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

It is explicitly designed around composable, API-driven commerce and says its platform can handle millions of SKUs, multiple brands/stores, international expansion, and integrations with ERP/CRM and other systems. commercetools commercetools

That's particularly attractive if you want something like:

PIM → commercetools → custom storefronts
ERP → pricing/inventory/order services → commercetools
commercetools → OMS/WMS/3PL
CDP/CRM → personalization

rather than forcing your commerce platform to become the system of record for everything.

I'd choose this when architectural flexibility and long-term scalability matter more than minimizing implementation effort.

2. VTEX if you want more functionality out of the box

I'd look very seriously at VTEX if you're selling across many countries, brands, channels, B2B/B2C segments, or marketplaces.

VTEX positions itself as a unified platform for B2B, B2C and marketplaces, with multi-brand, multi-country and multi-channel management built in. It also has native marketplace functionality and extensive API/integration capabilities. VTEX VTEX

This makes it particularly interesting for a business where the requirement is:

"We have lots of complexity, but we don't want to assemble 15 separate commerce components ourselves."

I'd probably put VTEX ahead of commercetools if marketplace functionality, B2B and unified commerce are major requirements.

3. Shopify Plus if speed and operational simplicity win

Don't dismiss Shopify Plus simply because you're an enterprise.

Its current Markets capabilities support market-specific currencies, pricing, catalogs, product availability, domains and localization; Plus also provides unlimited B2B catalogs and direct catalog assignment to companies/company locations. Shopify Help Center Shopify Help Center

Shopify also provides APIs and an enormous integration ecosystem, so you can keep systems like your PIM/ERP/OMS outside Shopify. Shopify Shopify

I'd pick it when:

• You have thousands or tens of thousands of SKUs but not extraordinarily complex product logic
• You want to launch markets quickly
• Your team would rather configure than build
• Checkout and operational reliability are priorities
• Your integrations can be cleanly separated through APIs/middleware

I would not make Shopify my first choice if you have highly unusual pricing, catalog inheritance, workflow, checkout, or order orchestration requirements that need to behave differently by market.

4. Adobe Commerce for catalog-heavy complexity

Adobe Commerce becomes interesting when the catalog itself is the monster.

Adobe currently describes Commerce Optimizer as supporting millions of products, thousands of prices per product, hundreds of sites, and updates across tens of millions of SKUs. It also specifically supports complex multi-brand, multi-geography and B2B2X catalog structures. Adobe for Business

So if your "thousands of SKUs" actually means:

50k+ products × hundreds of customer segments × market-specific assortments × complicated pricing × multiple websites

I'd put Adobe much higher on the list.

The downside is that I'd expect a heavier implementation and greater technical ownership than Shopify Plus.

How I'd decide

For your description alone, my ranking would be:

1. commercetools — if your enterprise architecture/integrations are the dominant concern
2. VTEX — if multi-market + B2B/B2C + marketplace/unified commerce are dominant
3. Shopify Plus — if speed, reliability and operational simplicity are dominant
4. Adobe Commerce — if catalog/pricing/site complexity is dominant

One important point: don't evaluate these platforms based primarily on SKU count. Thousands of SKUs isn't particularly challenging for modern enterprise platforms. The harder questions are:

• How many markets/countries/currencies?
• How many brands/storefronts?
• B2C, B2B, or both?
• How complicated is product data?
• How many price lists/customer segments?
• Is inventory coming from one ERP or multiple systems?
• How many orders/day and peak orders/minute?
• Do you need marketplaces?
• How much of the storefront needs to be headless?
• Who owns the system of record for products, customers, prices, inventory and orders?
• How much custom business logic do you anticipate?

If you give me roughly # SKUs, # markets/countries, B2B vs B2C, ERP/PIM/OMS you're using, order volume, and whether you want headless, I can narrow this to the 2–3 platforms I'd actually put through an enterprise RFP, including a suggested target architecture and where each will hurt you.

Adobe currently describes Commerce Optimizer as supporting millions of products, thousands of prices per product, hundreds of sites, and updates across tens of millions of SKUs. It also specifically supports complex multi-brand, multi-geography and B2B2X catalog structures. Adobe for Business

So if your "thousands of SKUs" actually means:

50k+ products × hundreds of customer segments × market-specific assortments × complicated pricing × multiple websites

I'd put Adobe much higher on the list.

The downside is that I'd expect a heavier implementation and greater technical ownership than Shopify Plus.

How I'd decide

For your description alone, my ranking would be:

1. commercetools — if your enterprise architecture/integrations are the dominant concern
2. VTEX — if multi-market + B2B/B2C + marketplace/unified commerce are dominant
3. Shopify Plus — if speed, reliability and operational simplicity are dominant
4. Adobe Commerce — if catalog/pricing/site complexity is dominant

One important point: don't evaluate these platforms based primarily on SKU count. Thousands of SKUs isn't particularly challenging for modern enterprise platforms. The harder questions are:

• How many markets/countries/currencies?
• How many brands/storefronts?
• B2C, B2B, or both?
• How complicated is product data?
• How many price lists/customer segments?
• Is inventory coming from one ERP or multiple systems?
• How many orders/day and peak orders/minute?
• Do you need marketplaces?
• How much of the storefront needs to be headless?
• Who owns the system of record for products, customers, prices, inventory and orders?
• How much custom business logic do you anticipate?

If you give me roughly # SKUs, # markets/countries, B2B vs B2C, ERP/PIM/OMS you're using, order volume, and whether you want headless, I can narrow this to the 2–3 platforms I'd actually put through an enterprise RFP, including a suggested target architecture and where each will hurt you.

3. Shopify Plus if speed and operational simplicity win

Don't dismiss Shopify Plus simply because you're an enterprise.

Its current Markets capabilities support market-specific currencies, pricing, catalogs, product availability, domains and localization; Plus also provides unlimited B2B catalogs and direct catalog assignment to companies/company locations.

For an enterprise with thousands of SKUs, complex integrations, multiple markets, and likely substantial ERP/PIM/OMS/CRM dependencies, I’d shortlist commercetools, Shopify Plus, Adobe Commerce, and VTEX rather than treating this as a generic “best ecommerce platform” decision.

My shortlist

1. My first choice: commercetools

If by "complex integrations" you mean ERP + PIM + OMS + CRM + multiple payment/tax/shipping systems + multiple storefronts/brands/channels, I'd put commercetools at the top.

It's an API-first, composable architecture, so commerce doesn't have to dictate your entire technology stack. That's particularly valuable when you have an engineering organization capable of operating a distributed commerce architecture. Independent storefront, search, CMS, promotions, checkout, etc. can evolve without replacing the entire commerce platform. CIOPages Elogic Commerce

I'd choose it when: your complexity is strategic and you expect the architecture itself to be a competitive advantage.

I'd avoid it when: you don't have a strong internal engineering/platform team. Composable commerce can turn into a collection of systems that you have to operate.

2. Shopify Plus — probably the best pragmatic choice

I'd seriously consider shopify.com if your primary goal is to scale globally without making ecommerce infrastructure a huge internal engineering project.

Shopify currently supports very large catalogs—its enterprise material specifically describes brands hosting 1M+ products and variants—and provides APIs, an extensive partner ecosystem, headless capabilities, and international market functionality. Shopify

For B2B, Plus supports unlimited catalogs, direct catalog assignment to companies/company locations, quantity rules, volume pricing, and market-specific experiences. Shopify Help Center Shopify Help Center

That makes it surprisingly capable for a large SKU footprint.

I'd choose it when: you want enterprise scale but want to minimize platform maintenance and custom infrastructure.

The big caveat: if your pricing, product hierarchy, order orchestration, or business rules are exceptionally bespoke, you may eventually find yourself designing around Shopify's model rather than designing your own.

3. Adobe Commerce

Adobe Commerce becomes particularly attractive if your organization needs very deep catalog, pricing, customer, B2B, and ERP customization.

It's a good candidate when you have unusual requirements that can't comfortably be expressed through a SaaS platform's extension/API model.

The tradeoff is complexity: you gain considerable control, but you're also taking on a heavier implementation and operating model. Independent industry comparisons similarly position Adobe toward highly customized enterprise/B2B deployments, while Shopify emphasizes lower operational burden and commercetools maximum composability. CIOPages Elogic Commerce

4. VTEX

I'd put VTEX on the shortlist if your definition of "multi-market" includes international commerce + marketplaces + omnichannel + complex seller/marketplace models.

It's especially worth investigating if you're operating across numerous countries and channels rather than simply translating one global storefront into different currencies.

What I'd actually recommend for your situation

Given just the characteristics you've provided, I'd rank them:

1. commercetools — if integration/architecture complexity is the dominant problem
2. Shopify Plus — if operational simplicity and speed are equally important
3. Adobe Commerce — if bespoke B2B/catalog/pricing logic is dominant
4. VTEX — if marketplaces/omnichannel/global operations are central

The critical distinction is where your complexity lives.

If you tell me roughly:

• # of SKUs / variants
• # of countries/markets
• B2C, B2B, or both
• ERP (SAP, Oracle, NetSuite, Dynamics, custom, etc.)
• PIM (Akeneo, Salsify, Pimcore, custom, etc.)
• OMS
• # of brands/storefronts
• whether you need headless/composable
• approximate annual GMV/orders

…I can build you a weighted enterprise scorecard for Shopify Plus vs commercetools vs Adobe vs VTEX, including integration architecture, catalog scalability, localization, B2B, total cost, implementation risk, and which I'd actually select. CIOPages Elogic Commerce

1. My first choice: commercetools

If by "complex integrations" you mean ERP + PIM + OMS + CRM + multiple payment/tax/shipping systems + multiple storefronts/brands/channels, I'd put commercetools at the top.

It's an API-first, composable architecture, so commerce doesn't have to dictate your entire technology stack. That's particularly valuable when you have an engineering organization capable of operating a distributed commerce architecture. Independent storefront, search, CMS, promotions, checkout, etc. can evolve without replacing the entire commerce platform. CIOPages Elogic Commerce

I'd choose it when: your complexity is strategic and you expect the architecture itself to be a competitive advantage.

I'd avoid it when: you don't have a strong internal engineering/platform team. Composable commerce can turn into a collection of systems that you have to operate.

2. Shopify Plus — probably the best pragmatic choice

I'd seriously consider shopify.com if your primary goal is to scale globally without making ecommerce infrastructure a huge internal engineering project.

Shopify currently supports very large catalogs—its enterprise material specifically describes brands hosting 1M+ products and variants—and provides APIs, an extensive partner ecosystem, headless capabilities, and international market functionality. Shopify

For B2B, Plus supports unlimited catalogs, direct catalog assignment to companies/company locations, quantity rules, volume pricing, and market-specific experiences. Shopify Help Center Shopify Help Center

That makes it surprisingly capable for a large SKU footprint.

I'd choose it when: you want enterprise scale but want to minimize platform maintenance and custom infrastructure.

The big caveat: if your pricing, product hierarchy, order orchestration, or business rules are exceptionally bespoke, you may eventually find yourself designing around Shopify's model rather than designing your own.

3. Adobe Commerce

Adobe Commerce becomes particularly attractive if your organization needs very deep catalog, pricing, customer, B2B, and ERP customization.

It's a good candidate when you have unusual requirements that can't comfortably be expressed through a SaaS platform's extension/API model.

The tradeoff is complexity: you gain considerable control, but you're also taking on a heavier implementation and operating model. Independent industry comparisons similarly position Adobe toward highly customized enterprise/B2B deployments, while Shopify emphasizes lower operational burden and commercetools maximum composability. CIOPages Elogic Commerce

4. VTEX

I'd put VTEX on the shortlist if your definition of "multi-market" includes international commerce + marketplaces + omnichannel + complex seller/marketplace models.

It's especially worth investigating if you're operating across numerous countries and channels rather than simply translating one global storefront into different currencies.

What I'd actually recommend for your situation

Given just the characteristics you've provided, I'd rank them:

1. commercetools — if integration/architecture complexity is the dominant problem
2. Shopify Plus — if operational simplicity and speed are equally important
3. Adobe Commerce — if bespoke B2B/catalog/pricing logic is dominant
4. VTEX — if marketplaces/omnichannel/global operations are central

The critical distinction is where your complexity lives.

If you tell me roughly:

• # of SKUs / variants
• # of countries/markets
• B2C, B2B, or both
• ERP (SAP, Oracle, NetSuite, Dynamics, custom, etc.)
• PIM (Akeneo, Salsify, Pimcore, custom, etc.)
• OMS
• # of brands/storefronts
• whether you need headless/composable
• approximate annual GMV/orders

…I can build you a weighted enterprise scorecard for Shopify Plus vs commercetools vs Adobe vs VTEX, including integration architecture, catalog scalability, localization, B2B, total cost, implementation risk, and which I'd actually select. CIOPages Elogic Commerce

For an enterprise team with complex integrations + thousands of SKUs + multiple countries/markets, I’d shortlist commercetools, Shopify Plus, Adobe Commerce, Salesforce Commerce Cloud, and SAP Commerce Cloud—but the right answer depends heavily on whether your complexity is mostly technical/integration complexity or business-rule/catalog complexity.

My shortlist

1. My first choice: commercetools

If your phrase "complex integrations" is the key requirement, I'd put commercetools at the top of the evaluation.

It's an API-first/composable architecture, so you can keep your ERP, PIM, OMS, search, CMS, pricing engine, payments, etc. as separate systems rather than forcing everything through the commerce platform. That's particularly attractive when you have a substantial engineering organization and expect the architecture to evolve over time. Current enterprise-platform comparisons also position commercetools specifically toward engineering-heavy composable implementations. CIOPages Elastic Path

I'd choose it if:

• You have a strong internal engineering/platform team.
• Your ERP/PIM/OMS are important systems of record.
• You need sophisticated product, pricing, inventory, or customer-specific logic.
• Multiple brands/markets may have different experiences.
• Headless/composable is strategically important.
• You don't want the commerce platform to become the center of your architecture.

The tradeoff is that composable gives you freedom by making you responsible for more architecture.

2. Shopify Plus if you want scale without owning the platform

I'd seriously consider Shopify Plus if your business complexity doesn't require bespoke commerce logic everywhere.

Shopify has become much more capable for enterprise international commerce. Markets supports market-specific products, pricing, currencies, domains, languages, taxes/duties and storefront experiences, while Plus adds capabilities such as unlimited B2B market catalogs and direct company-level catalog assignment. Shopify Shopify Help Center Shopify Help Center

That's a compelling proposition if your goal is:

"We have a complicated enterprise ecosystem, but we don't want ecommerce itself to be another giant software engineering project."

I'd favor Shopify Plus when time-to-market, operational simplicity, reliability and reducing platform maintenance matter more than maximum architectural flexibility.

3. Adobe Commerce if business rules are unusually complicated

Adobe Commerce remains interesting when you have things like:

• complicated catalogs
• sophisticated pricing rules
• multiple customer groups
• highly customized checkout/order flows
• extensive B2B requirements
• significant customization requirements
• an existing Magento/Adobe Commerce investment

The downside is operational complexity. Current comparisons generally put Adobe toward the more customizable, engineering-intensive end of the enterprise spectrum. Shopify

4. Salesforce Commerce Cloud if you're already deep in Salesforce

If your organization runs heavily on Salesforce CRM, Service Cloud, Marketing Cloud, Data Cloud, etc., Commerce Cloud deserves a serious look.

The value proposition isn't necessarily that it's universally the best commerce engine; it's that customer, sales, marketing and commerce data can live within a broader Salesforce architecture. Current enterprise comparisons similarly position Salesforce Commerce Cloud particularly well for Salesforce-centric organizations. CIOPages Elastic Path

5. SAP Commerce Cloud for SAP-heavy businesses

If SAP is already deeply embedded in your organization—particularly ERP, product, pricing, supply chain and customer processes—I'd put SAP Commerce Cloud on the shortlist.

This becomes especially compelling for manufacturers/distributors with complex B2B commerce rather than a relatively straightforward DTC catalog. Shopify Elastic Path

What I'd actually do in your situation

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

Thousands of SKUs isn't particularly challenging for modern enterprise platforms. The harder questions are:

1. Where is product truth?
PIM → commerce → marketplace → ERP? Or does commerce own the catalog?

2. Where is pricing truth?
One global price list, market-specific prices, customer-specific pricing, contract pricing, promotions?

3. Where is inventory truth?
ERP, OMS, WMS, multiple 3PLs, stores?

4. How different are your markets?
Same catalog translated into different currencies, or genuinely different assortments/business rules?

5. How many integrations are synchronous?
This is a huge architectural consideration. I'd want to know the ERP, PIM, OMS, CRM, tax, payments, search, CMS, DAM, marketplaces and fulfillment systems involved.

6. How much custom behavior do you need?
This is probably the biggest differentiator between Shopify Plus and something like commercetools/Adobe.

My default recommendation

If I were putting together the initial enterprise RFP, I'd start with:

Tier 1

• commercetools — maximum architectural flexibility
• Shopify Plus — maximum operational simplicity

Tier 2

• Adobe Commerce — maximum traditional commerce customization
• Salesforce Commerce Cloud — if Salesforce is strategically central
• SAP Commerce Cloud — if SAP is strategically central

And I'd make vendors demonstrate your actual architecture, rather than give you a generic product demo.

For example, give each vendor a scenario like:

25,000 SKUs → 12 countries → 7 currencies → 4 languages → 3 warehouses → ERP + PIM + OMS + CRM → customer-specific pricing → market-specific assortment → B2B + DTC → marketplace feeds → localized tax/shipping → 500k+ monthly orders.

Then make them demonstrate catalog ingestion, price calculation, inventory synchronization, market localization, order orchestration, failure/retry behavior and API/webhook architecture.

That's where the platforms start looking very different.

If you tell me your ERP/PIM/OMS/CRM stack, number of markets, B2B vs DTC mix, approximate SKU count, and whether you want headless, I can narrow this to a 2–3 platform recommendation and a reference architecture.

2. Where is pricing truth?
One global price list, market-specific prices, customer-specific pricing, contract pricing, promotions?

3. Where is inventory truth?
ERP, OMS, WMS, multiple 3PLs, stores?

4. How different are your markets?
Same catalog translated into different currencies, or genuinely different assortments/business rules?

5. How many integrations are synchronous?
This is a huge architectural consideration. I'd want to know the ERP, PIM, OMS, CRM, tax, payments, search, CMS, DAM, marketplaces and fulfillment systems involved.

6. How much custom behavior do you need?
This is probably the biggest differentiator between Shopify Plus and something like commercetools/Adobe.

My default recommendation

If I were putting together the initial enterprise RFP, I'd start with:

Tier 1

• commercetools — maximum architectural flexibility
• Shopify Plus — maximum operational simplicity

Tier 2

• Adobe Commerce — maximum traditional commerce customization
• Salesforce Commerce Cloud — if Salesforce is strategically central
• SAP Commerce Cloud — if SAP is strategically central

And I'd make vendors demonstrate your actual architecture, rather than give you a generic product demo.

For example, give each vendor a scenario like:

25,000 SKUs → 12 countries → 7 currencies → 4 languages → 3 warehouses → ERP + PIM + OMS + CRM → customer-specific pricing → market-specific assortment → B2B + DTC → marketplace feeds → localized tax/shipping → 500k+ monthly orders.

Then make them demonstrate catalog ingestion, price calculation, inventory synchronization, market localization, order orchestration, failure/retry behavior and API/webhook architecture.

That's where the platforms start looking very different.

If you tell me your ERP/PIM/OMS/CRM stack, number of markets, B2B vs DTC mix, approximate SKU count, and whether you want headless, I can narrow this to a 2–3 platform recommendation and a reference architecture.

For an enterprise with thousands of SKUs, complex integrations, and multiple countries/markets, I’d avoid choosing primarily on storefront features. The key question is how well the platform becomes the commerce layer between your ERP/PIM/OMS/CRM and regional storefronts.

My shortlist would be:

What I'd recommend for your situation

1. Adobe Commerce — probably my first evaluation

If "complex integrations" means things like ERP + PIM + OMS + tax + pricing engine + multiple warehouses + customer-specific catalogs/pricing + regional rules, Adobe Commerce is particularly compelling. Current enterprise comparisons continue to put it toward the top for complex B2B and deep integration requirements. Elogic Commerce Elogic Commerce

It's especially attractive if your thousands of SKUs have complicated relationships, attributes, configurable products, customer-specific pricing, or market-specific availability.

2. commercetools — if you have a strong engineering organization

I'd put this at #1 if you're deliberately pursuing a composable/headless architecture. Instead of buying one giant commerce application, you assemble commerce capabilities around APIs and your own services. That's powerful for a company with substantial engineering resources and unusual integration requirements, but it also means you own more of the architecture. Elogic Commerce Elogic Commerce

3. Shopify Plus — if operational simplicity matters more than maximum flexibility

Don't dismiss Shopify just because you're enterprise. Shopify Plus now supports international markets, localized currencies/languages/domains, B2B catalogs, customer-specific catalogs, and integrations with ERP/CRM/PIM systems. Shopify Help Center Shopify Help Center Shopify Help Center

The tradeoff is that once your business rules become extremely unusual, you may end up building a substantial integration/app layer around Shopify rather than customizing the commerce engine itself.

The architecture I'd actually investigate

For your scale, I'd think about it as:

PIM → Commerce → OMS → ERP

with:

• PIM = canonical product/SKU/attribute/content data
• Commerce = catalog presentation, pricing, carts, checkout, customer experience
• OMS = inventory/fulfillment/order orchestration
• ERP = financial/operational system of record
• Integration/iPaaS layer = synchronization and event orchestration
• Regional configuration = currency, tax, language, payment, shipping, assortment and pricing

That architecture matters more than whether the platform advertises "millions of SKUs." You want to avoid turning the ecommerce platform into your master database for everything.

One important distinction

If by "multi-market" you mean 10–30 countries with localized storefronts, Shopify Plus or BigCommerce can be very attractive.

If you mean dozens of countries × multiple brands × customer-specific catalogs × complicated pricing × multiple ERPs/PIMs/warehouses, I'd focus much more heavily on Adobe Commerce, commercetools, SAP Commerce, or Salesforce Commerce Cloud.

Shopify Plus currently supports up to 50 Markets natively, with additional approaches available for businesses exceeding that, and Plus provides unlimited B2B catalogs. Shopify Help Center Shopify Help Center Shopify Help Center

My starting shortlist for your description would therefore be: Adobe Commerce + commercetools + Shopify Plus, then add SAP Commerce or Salesforce Commerce Cloud if your existing enterprise stack makes either a natural fit.

If you tell me your ERP (SAP/Oracle/Dynamics/etc.), PIM, number of countries, B2B vs B2C mix, approximate SKU count, and whether you have a large engineering team, I can narrow this to a 2–3 platform recommendation and map out the integration architecture.

Don't dismiss Shopify just because you're enterprise. Shopify Plus now supports international markets, localized currencies/languages/domains, B2B catalogs, customer-specific catalogs, and integrations with ERP/CRM/PIM systems. Shopify Help Center Shopify Help Center Shopify Help Center

The tradeoff is that once your business rules become extremely unusual, you may end up building a substantial integration/app layer around Shopify rather than customizing the commerce engine itself.

The architecture I'd actually investigate

For your scale, I'd think about it as:

PIM → Commerce → OMS → ERP

with:

• PIM = canonical product/SKU/attribute/content data
• Commerce = catalog presentation, pricing, carts, checkout, customer experience
• OMS = inventory/fulfillment/order orchestration
• ERP = financial/operational system of record
• Integration/iPaaS layer = synchronization and event orchestration
• Regional configuration = currency, tax, language, payment, shipping, assortment and pricing

That architecture matters more than whether the platform advertises "millions of SKUs." You want to avoid turning the ecommerce platform into your master database for everything.

One important distinction

If by "multi-market" you mean 10–30 countries with localized storefronts, Shopify Plus or BigCommerce can be very attractive.

If you mean dozens of countries × multiple brands × customer-specific catalogs × complicated pricing × multiple ERPs/PIMs/warehouses, I'd focus much more heavily on Adobe Commerce, commercetools, SAP Commerce, or Salesforce Commerce Cloud.

Shopify Plus currently supports up to 50 Markets natively, with additional approaches available for businesses exceeding that, and Plus provides unlimited B2B catalogs.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d avoid choosing purely on “ecommerce features.” The bigger question is how much complexity you want the commerce platform to own vs. how much your architecture team wants to own.

My shortlist would be:

Current enterprise-platform comparisons similarly put commercetools toward the composable/API-first end, Shopify toward managed SaaS, and SAP/Adobe toward deeper enterprise customization. CIOPages Shopify

My recommendation for your situation

I'd start with commercetools vs. Shopify Plus.

1. commercetools — if your integrations are genuinely complex

This is where I'd lean if you have something like:

• ERP + multiple PIMs/data sources
• sophisticated pricing engines
• multiple brands/regions
• different catalogs by market/customer
• custom checkout/order orchestration
• headless storefronts
• multiple fulfillment/OMS systems
• a substantial engineering/platform team
• expectation that the architecture will evolve over 5–10 years

The attraction is that commerce becomes an API-driven capability rather than the system that dictates your entire architecture. The platform is explicitly designed around composable commerce, with catalog, cart, checkout, promotions, etc. exposed as modular services. Shopify Shopify

The tradeoff: you are buying architectural freedom, not simplicity. You'll need strong engineering ownership.

2. Shopify Plus — if you want to eliminate operational complexity

I'd choose Shopify Plus if your organization wants the commerce team focused on merchandising, conversion, markets, and customer experience, rather than maintaining a sophisticated commerce platform.

Shopify has substantially expanded its enterprise/B2B capabilities. Plus now supports unlimited B2B catalogs, company/location-level catalog assignment, market-specific experiences, and multiple currencies/languages/domains. Shopify Help Center Shopify Help Center

That's particularly attractive if your thousands of SKUs are large in quantity but not extraordinarily complex in pricing/order logic.

The key question is whether your integrations can be made into a clean PIM → Shopify → OMS/ERP architecture rather than requiring the ecommerce platform itself to orchestrate dozens of enterprise systems.

Where SAP Commerce changes the answer

If you're already heavily invested in SAP S/4HANA, SAP ERP, or the broader SAP ecosystem, I'd put SAP Commerce Cloud very high on the list.

It's particularly suited to large catalogs, complex B2B pricing, corporate account hierarchies, approval workflows, inventory visibility, and global/multi-market commerce. Shopify

In other words:

SAP estate → SAP Commerce

Engineering-led composable architecture → commercetools

Want enterprise scale without owning lots of infrastructure → Shopify Plus

Salesforce-centered customer ecosystem → Salesforce Commerce

One architecture point I'd emphasize

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

I'd generally architect it more like:

PIM / MDM
↓
Commerce platform
↓
OMS / ERP / WMS
↓
Fulfillment

with supporting services for:

Search · Pricing · Tax · Payments · Promotions · CMS · Customer data · Localization

The commerce platform should consume authoritative product/customer/inventory data rather than becoming the giant enterprise database that everything else depends upon.

For your use case, I'd therefore evaluate vendors on integration architecture, catalog synchronization, pricing propagation, market localization, API limits/eventing, deployment model, and operational ownership before comparing storefront features.

If you tell me your ERP (SAP, Oracle, Dynamics, etc.), PIM, OMS, number of countries/markets, B2B vs B2C mix, and whether you want headless, I can narrow this to a 2–3 platform recommendation and give you an enterprise architecture/decision matrix.

For an enterprise team with complex integrations, thousands of SKUs, and multi-market operations, I would avoid choosing based on storefront features alone. The right platform depends on whether you need a commerce engine, a global operating system, or a composable architecture. Enterprise platforms are typically evaluated around catalog scale, ERP/PIM/OMS integrations, multi-region support, governance, and long-term flexibility. SCAYLE Commerce Engine Guideflow

My shortlist would be:

Web Solutions NYC Broadleaf Commerce## My recommendation by scenario

1. You have SAP/ERP complexity

Choose SAP Commerce Cloud if you have:

• SAP S/4HANA or ECC
• dealer/distributor networks
• contract pricing
• customer-specific catalogs
• complicated fulfillment rules

This is common for industrial, manufacturing, and enterprise B2B organizations. SCAYLE Commerce Engine

2. You want a future-proof commerce platform

Choose commercetools if your architecture team wants:

• multiple frontends (web, mobile, marketplaces, apps)
• independent services
• global expansion without rebuilding
• flexibility around OMS, PIM, CMS, search, and personalization

This is usually the strongest fit for enterprises embracing composable commerce. Broadleaf Commerce

3. You need maximum control over a complex catalog

Choose Adobe Commerce if you need:

• unusual product models
• custom workflows
• heavy B2B requirements
• lots of extensions/custom code

It is powerful, but you need a capable engineering and operations team. Web Solutions NYC

4. You need to move quickly across many countries

Choose Shopify Plus or BigCommerce Enterprise if:

• speed matters more than unlimited customization
• your integrations can be handled through APIs/middleware
• you want less infrastructure ownership

Web Solutions NYC## The stack I would expect for a serious enterprise setup

For thousands of SKUs, I would usually design around:

• Commerce platform: commercetools / SAP Commerce / Adobe Commerce
• PIM: Akeneo, Salsify, or similar
• ERP: SAP, Oracle, Microsoft Dynamics, NetSuite, etc.
• OMS: centralized inventory and fulfillment orchestration
• CMS: headless CMS if content teams operate independently
• Search: enterprise search/personalization layer
• Integration layer: iPaaS or API gateway

Questions that would narrow this down quickly

1. Are you primarily B2B, B2C, or both?
2. Roughly how many SKUs: 5k, 50k, 500k+?
3. Which ERP/PIM are you integrating with (SAP, Oracle, NetSuite, Dynamics, custom)?
4. How many markets/languages/currencies?
5. Do you need marketplaces (Amazon, Walmart, regional marketplaces) or only owned storefronts?
6. Is your team comfortable owning a headless/API-first architecture?

With those answers, I’d typically narrow this to 2–3 platforms rather than a broad enterprise shortlist.

For an enterprise team with thousands of SKUs, complex integrations, and multiple markets, I’d narrow the field to commercetools, Adobe Commerce, Shopify Plus, and Salesforce Commerce Cloud—but I’d put commercetools and Adobe Commerce at the top of your evaluation.

My shortlist

1. My default recommendation: commercetools

If by "complex integrations" you mean ERP + PIM + OMS + WMS + CRM + pricing engines + tax/payment providers + multiple frontends/marketplaces, I'd start with commercetools.

Its architecture is specifically designed around modular APIs and independent commerce capabilities, rather than forcing all of your business logic into one commerce application. It also explicitly targets millions of SKUs, multiple brands/stores, international expansion, and integration with ERP/CRM systems. commercetools commercetools

commercetools.com

I'd choose it if your organization has a capable product/engineering platform team and wants commerce to be an orchestration layer rather than the system of record for everything.

2. Adobe Commerce if catalog/B2B complexity dominates

Adobe Commerce becomes particularly compelling if your "thousands of SKUs" actually means things like:

• Multiple catalogs and price books
• Customer-specific pricing
• Complex product relationships/configurators
• B2B account hierarchies
• Quotes and approval workflows
• Multiple brands and regional stores
• Significant custom business logic

Adobe says its catalog service supports millions of SKUs and thousands of prices per SKU, while its architecture supports multiple brands, markets, B2B/B2C models and storefronts. Adobe Business Experience League

business.adobe.com

The caveat is that its multi-store architecture needs careful engineering at scale; Adobe itself warns that additional stores can increase catalog/indexing load. Experience League

3. Shopify Plus if you want to minimize platform operations

I wouldn't dismiss Shopify Plus simply because you're enterprise. Its current Markets/B2B capabilities are considerably more sophisticated than the old "one Shopify store" mental model. Plus supports unlimited catalogs assigned directly to company locations, and Markets can vary currency, taxes/duties, pricing, product availability and other experiences by market. Shopify Help Center Shopify Help Center

shopify.com

But I'd ask a crucial question before selecting it:

Are your integrations complicated because you have lots of systems, or because your commerce business logic itself is unusually complicated?

If it's mostly the former, Shopify Plus can be excellent. If it's the latter, I'd lean toward commercetools or Adobe.

4. Salesforce Commerce Cloud

I'd put Salesforce Commerce Cloud on the shortlist if you're already deeply standardized on Salesforce. Otherwise, I wouldn't choose it simply because you're an enterprise.

The value proposition becomes much stronger when commerce needs to interact tightly with Salesforce CRM, customer data, service, marketing and sales processes.

What I'd actually do in your position

I'd run a 4-vendor bake-off:

1. commercetools — architecture/flexibility leader
2. Adobe Commerce — catalog/B2B/customization leader
3. Shopify Plus — operational simplicity leader
4. Salesforce Commerce Cloud — ecosystem-integrated option

And I would not let vendors demo their standard storefront.

Give each vendor the same real-world scenario:

20,000 SKUs → 8 countries → 4 currencies → 3 languages → 2 brands → 3 ERP integrations → PIM → OMS → customer-specific pricing → regional inventory → promotions → tax → payments → marketplace feeds → B2B accounts → multiple storefronts.

Then make them demonstrate how the data actually flows.

That's much more revealing than feature checklists.

The architecture I'd favor

For your description, I'd generally aim for:

PIM → product/catalog master
ERP → financial/order/inventory master
OMS → fulfillment/order orchestration
Commerce platform → cart, checkout, pricing/promotion orchestration, customer experience
CMS → content
Search → search/discovery
CDP/CRM → customer data
Integration layer/event bus → system-to-system communication

In other words, don't make the ecommerce platform your enterprise database.

That's one reason I'm particularly interested in commercetools for your use case: its composable/API-oriented model fits this architecture naturally. commercetools

Bottom line: if you have a sophisticated engineering organization and expect the integration landscape/business rules to keep getting more complex, start with commercetools. If you need a powerful integrated commerce application with particularly deep catalog/B2B functionality, start with Adobe Commerce. If your priority is reducing engineering/platform burden while still operating globally, Shopify Plus deserves a serious evaluation.

If you tell me roughly SKU count, number of markets/countries, B2B vs B2C, ERP/PIM/OMS systems, and whether you want headless, I can narrow this to a 2-platform recommendation and an architecture for each.

For your profile—enterprise team, complex integrations, thousands of SKUs, and multiple markets—I’d shortlist commercetools, SAP Commerce Cloud, Adobe Commerce, and Salesforce Commerce Cloud. I would not choose primarily on storefront features; your biggest architectural issues are likely catalog, pricing, ERP/OMS/PIM integration, localization, and market expansion.

My shortlist

Recent enterprise-platform comparisons similarly put commercetools toward the composable/engineering-heavy end, while Adobe, Salesforce, and SAP are stronger choices when you want more packaged enterprise capabilities. CIOPages Itechguides

My #1: commercetools

I'd put commercetools at the top of your evaluation list if your team has substantial engineering/architecture capability.

It is API-first and designed specifically for enterprises that need to integrate commerce with ERP, CRM, PIM, OMS, marketplaces, search, pricing, etc. It explicitly supports multiple brands/stores and international expansion, and its infrastructure is designed for very large catalogs. commercetools commercetools

The particularly relevant part for you is its B2B/catalog architecture: commercetools cites support for hundreds of thousands of SKUs, complex technical attributes and part numbers, and integration with ERP/CRM/OMS systems of record. commercetools

It also has examples at significant catalog scale, including a 22M-SKU deployment and a 65K-SKU implementation. commercetools commercetools

The catch: composable doesn't mean "less complexity." It means you own more of the architecture. If your organization already has strong platform engineering, that's potentially a major advantage. If your goal is to minimize engineering ownership, I'd move it down the list.

commercetools.com

When I'd choose SAP Commerce Cloud instead

If you're heavily invested in SAP S/4HANA/ERP, I'd take SAP Commerce Cloud extremely seriously.

Its catalog tooling specifically supports country/currency-specific product data, localized storefronts, catalog versioning, classification, synchronization and workflows. SAP

That's compelling if your commerce operation is essentially an extension of a sophisticated ERP/product/pricing/order ecosystem.

Rule of thumb:

• SAP everywhere → SAP Commerce Cloud
• Best-of-breed technology stack → commercetools

When I'd choose Adobe Commerce

I'd favor Adobe if you have very complicated catalog/merchandising/business rules but don't necessarily want to assemble as much functionality yourself.

Adobe supports multiple storefronts for brands, product lines and geographies from one administration environment and claims support for millions of SKUs across brands/regions. It also has integration accelerators for systems including SAP S/4HANA, Dynamics 365 and Salesforce. Adobe Business Adobe Business

It's a particularly interesting middle ground between a traditional enterprise commerce suite and a fully composable architecture.

The architecture I'd actually recommend

For your requirements, I wouldn't make the ecommerce platform the master of everything.

I'd aim for something closer to:

ERP → inventory, financials, core SKU data, perhaps pricing
PIM → enriched product content/attributes
Commerce platform → carts, checkout, channels, customer context, commerce rules
OMS → order orchestration/fulfillment
Search → product discovery
CDP/CRM → customer identity/data
Integration/event layer → synchronization and orchestration
Localized storefronts → market-specific experience

For example:

PIM + ERP → commercetools → OMS/ERP → fulfillment

rather than trying to make the ecommerce platform itself the company's universal product-data and order-management system.

commercetools' own integration guidance makes essentially this distinction: PIM can own enriched product content while ERP owns things such as SKUs, pricing and inventory. commercetools Documentation

The most important questions I'd ask in your RFP

Don't just ask vendors "How many SKUs can you handle?" I'd test:

• 500k+ SKU catalog load: How quickly can the catalog update without taking the site down?
• Market inheritance: Can Germany inherit 95% of the US catalog while overriding price, tax, language and assortment?
• Customer-specific pricing: Can 10,000 B2B customers each have different price lists/contract terms?
• ERP latency: What happens when ERP pricing/inventory is temporarily unavailable?
• Integration volume: How many events/API calls can the platform sustain during catalog and order synchronization?
• Catalog governance: Can product teams manage localized attributes without engineering?
• Search: Can users search by manufacturer part number, aliases, technical attributes and synonyms?
• Market launch: How much work is actually required to launch market #15 versus market #2?
• Failure recovery: Can integrations replay events without creating duplicate orders?
• Observability: Can your team trace a SKU → price → cart → order across all systems?

If I were running the selection, my first three POCs would be commercetools, SAP Commerce Cloud, and Adobe Commerce. I'd add Salesforce Commerce Cloud if you're already deeply standardized on Salesforce. The deciding factor shouldn't be who wins a feature matrix—it should be which architecture handles your most painful integration and catalog workflows with the least long-term operational complexity. CIOPages

If you tell me roughly B2B vs B2C, SKU count, number of countries, ERP/PIM/OMS you're using, and whether you have a 10+ person engineering team, I can narrow this to a top 2 and give you a concrete target architecture + RFP scorecard.

I'd aim for something closer to:

ERP → inventory, financials, core SKU data, perhaps pricing
PIM → enriched product content/attributes
Commerce platform → carts, checkout, channels, customer context, commerce rules
OMS → order orchestration/fulfillment
Search → product discovery
CDP/CRM → customer identity/data
Integration/event layer → synchronization and orchestration
Localized storefronts → market-specific experience

For example:

PIM + ERP → commercetools → OMS/ERP → fulfillment

rather than trying to make the ecommerce platform itself the company's universal product-data and order-management system.

commercetools' own integration guidance makes essentially this distinction: PIM can own enriched product content while ERP owns things such as SKUs, pricing and inventory.

The most important questions I'd ask in your RFP

Don't just ask vendors "How many SKUs can you handle?" I'd test:

• SAP everywhere → SAP Commerce Cloud
• Best-of-breed technology stack → commercetools

When I'd choose Adobe Commerce

For an enterprise team with thousands of SKUs, multiple markets, complex integrations, and likely multiple brands/channels, I would avoid choosing based on storefront features alone. The key decision is usually the commerce operating model: how much customization you need, how much engineering capacity you have, and where your ERP/CRM/PIM stack lives. Enterprise platforms today generally fall into integrated suites vs. composable/headless architectures. CIOPages

My shortlist would be:

Elastic Path MobiLoud### My recommendation by scenario

1. You have SAP ERP, complex pricing, regional catalogs, dealer/distributor channels
→ Start with SAP Commerce Cloud.
This is usually the strongest fit when commerce is deeply tied to ERP, inventory, pricing, and customer account structures. Spadoom

2. You have a strong engineering team and want a future-proof multi-market architecture
→ Look hardest at commercetools (possibly paired with a separate CMS, search, PIM, and checkout stack).
This is the model for companies that want to swap components over time instead of replacing an entire commerce suite. CIOPages

3. You have unusual catalog rules, bundles, configurations, or merchandising logic
→ Adobe Commerce is often a strong contender. Its flexibility can be valuable when your business model does not fit a standard SaaS workflow. Adobe Business

4. Your company already runs Salesforce CRM, Service Cloud, Marketing Cloud
→ Salesforce Commerce Cloud deserves serious consideration because the customer data and engagement ecosystem can outweigh architectural tradeoffs. Salesforce

5. You mainly need global DTC expansion quickly
→ Shopify Plus may be enough, but I would validate catalog complexity, pricing rules, localization needs, and ERP integration before committing.

For your stated profile, I would evaluate these first:

1. commercetools — if your team has strong engineering and wants maximum flexibility
2. SAP Commerce Cloud — if ERP/process complexity dominates
3. Adobe Commerce — if catalog and customization complexity dominates
4. Salesforce Commerce Cloud — if Salesforce is the center of your customer stack

Before selecting, I would score vendors against:

• Global catalog management (regions, currencies, languages, assortments)
• PIM integration and SKU governance
• Multi-brand / multi-store capability
• Complex pricing and promotions
• B2B account hierarchies and contracts
• Tax, payments, fulfillment integrations
• Marketplace/channel integrations
• API maturity
• Upgrade and release model
• Total cost of ownership over 5–7 years

If you share:

• B2B vs B2C mix
• current ERP (SAP, Oracle, Dynamics, custom, etc.)
• number of markets/countries
• whether you have an internal engineering team
• current platform (if replacing one)

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

5. You mainly need global DTC expansion quickly
→ Shopify Plus may be enough, but I would validate catalog complexity, pricing rules, localization needs, and ERP integration before committing.

For your stated profile, I would evaluate these first:

For an enterprise team with complex integrations, thousands of SKUs, and multiple countries/markets, I’d narrow the field to Shopify Plus, commercetools, SAP Commerce Cloud, Adobe Commerce, and Salesforce Commerce. The right choice depends heavily on whether you want a managed commerce platform or maximum architectural control. CIOPages Elastic Path

My shortlist

1. Shopify Plus — my default recommendation

I'd put Shopify Plus at #1 unless your integration/catalog requirements are unusually complex.

It has become substantially more enterprise-oriented: Shopify says Plus can support over one million products and variants, has APIs for integrating existing systems, supports headless implementations, and provides a centralized back office for international operations. Shopify Shopify

For multi-market specifically, Shopify gives you:

• Market-specific catalogs and product availability
• Local pricing/currencies
• Localized content and domains
• Multiple legal/business entities
• International B2B markets
• Centralized management across regions
• APIs for custom integrations

Shopify Shopify Help Center Shopify Help CenterThat's compelling if you have, say, US + Canada + UK + EU + APAC, thousands/tens of thousands of SKUs, an ERP/PIM/OMS stack, and want your engineering team focused on differentiation rather than maintaining the commerce platform.

One caveat: Shopify's native Markets model has some constraints. For example, Shopify currently documents up to 50 markets, with additional markets requiring grouping or API-based approaches. Shopify Help Center

2. commercetools — if "complex integrations" is the dominant requirement

If your architecture looks more like:

PIM → commerce → pricing engine → ERP → OMS → tax → payments → search → CMS → multiple custom storefronts

…I'd seriously consider commercetools.

It's API-first and composable, so you aren't trying to bend an all-in-one commerce platform around an unusually complex enterprise architecture. It supports multi-region, multi-currency, multi-language and multi-brand configurations. Shopify

The tradeoff is important: you are buying architectural freedom in exchange for operational complexity. If you have a strong platform engineering/product engineering organization, that's often worthwhile. If your team wants the commerce vendor to handle more of the machinery, Shopify is considerably more attractive.

3. SAP Commerce Cloud

I'd put this near the top if you're already heavily invested in SAP.

If your architecture has SAP ERP/S4, extensive enterprise pricing, complex product structures, B2B workflows and global operations, SAP Commerce becomes much more compelling than it would be for a typical DTC retailer. Current enterprise-platform comparisons similarly position SAP Commerce particularly well for SAP-standardized organizations. Shopify

I wouldn't choose it simply because you have "thousands of SKUs," though. Thousands of SKUs alone isn't a reason to accept the complexity of SAP Commerce.

The key distinction I'd make

Don't evaluate these primarily on SKU count.

A 500,000-SKU catalog can actually be easier than a 20,000-SKU catalog if the products have straightforward pricing and fulfillment.

I'd evaluate your situation around these dimensions:

1. Catalog complexity — variants, bundles, configurable products, regional assortment.
2. Pricing complexity — customer-specific pricing, price books, currencies, promotions.
3. Market complexity — different legal entities, tax regimes, currencies, languages, catalogs.
4. Integration complexity — ERP, PIM, OMS, WMS, CRM, CDP, tax, search, payments.
5. B2B requirements — accounts, contracts, quotes, approval workflows, punchout, negotiated pricing.
6. Frontend architecture — conventional storefront vs headless/multiple experiences.
7. Engineering appetite — how much commerce infrastructure does your team actually want to own?
8. Operating model — one global catalog with localized market rules vs essentially independent regional businesses.

What I'd choose

If you're primarily B2C/DTC:
→ Shopify Plus

If you're B2C + B2B, with very complicated integrations but don't want to build commerce infrastructure:
→ Shopify Plus, then evaluate commercetools as the architectural alternative.

If you're a highly technical organization building multiple brands/frontends/channels around a common commerce core:
→ commercetools

If SAP is already the backbone of the company:
→ SAP Commerce Cloud

If Salesforce is the backbone:
→ Salesforce Commerce

If you have unusually sophisticated B2B/catalog requirements and an existing Adobe ecosystem:
→ Adobe Commerce

The most interesting comparison for your description is probably Shopify Plus vs commercetools. Shopify is increasingly capable of handling enterprise-scale catalogs and integrations while removing a lot of operational burden; commercetools gives an engineering-heavy organization substantially more control over the architecture. Shopify Shopify

If you tell me roughly SKU count, number of markets/countries, B2B vs B2C, your ERP/PIM/OMS, and whether you need headless, I can give you a much more specific architecture recommendation and a Shopify Plus vs commercetools vs SAP/Adobe comparison for your situation.

The key distinction I'd make

Don't evaluate these primarily on SKU count.

For an enterprise team with complex integrations, thousands of SKUs, multiple markets, and likely ERP/PIM/OMS/CRM dependencies, I would avoid choosing based on storefront features alone. The key decision is whether you want a managed commerce suite or a composable commerce architecture. CIOPages

My shortlist would be:

Virto Commerce Guideflow## My recommendation by scenario

1. You have a strong engineering team and unique commerce requirements

Choose commercetools.

Typical signals:

• Multiple storefronts/apps/kiosks
• Need to swap CMS, search, promotions, checkout, or pricing independently
• Multiple brands sharing a commerce core
• Complex integrations where your architecture is a competitive advantage

This is the “build your commerce platform as a capability” approach. CIOPages

2. You are a manufacturer, distributor, or enterprise B2B company

Shortlist SAP Commerce Cloud and Adobe Commerce.

Especially if you have:

• Contract pricing
• Customer-specific catalogs
• Account hierarchies
• Quote workflows
• Regional product differences
• ERP-driven inventory and fulfillment

SAP Commerce is often considered when SAP ERP is central; Adobe is often favored when customization and flexibility are priorities. Shopify Itechguides

3. You want to reduce platform ownership burden

Look at Shopify Plus or Salesforce Commerce Cloud.

Choose Shopify Plus if:

• D2C is dominant
• You need speed
• Your workflows fit SaaS constraints

Choose Salesforce if:

• Salesforce CRM, Service Cloud, Marketing Cloud, or Data Cloud are already strategic systems. Space Dinosaurs

Architecture I would expect for your scale

For thousands of SKUs and many markets, I would usually separate responsibilities:

• Commerce engine: commercetools / SAP Commerce / Adobe Commerce / Salesforce Commerce
• PIM: product master data (e.g., Akeneo, Salsify, Syndigo)
• ERP: SAP, Oracle, Dynamics, NetSuite, etc.
• OMS: order orchestration and fulfillment
• Search: Algolia, Elasticsearch/OpenSearch, Coveo, etc.
• CMS: Contentful, Adobe Experience Manager, Sanity, etc.
• Integration layer: MuleSoft, Boomi, Workato, SAP Integration Suite, custom APIs

The commerce platform should not become the system of record for everything. That is where many enterprise implementations become difficult.

My default enterprise shortlist

If I were running a vendor evaluation for your description, I would start with:

1. commercetools — if your engineering organization is mature
2. SAP Commerce Cloud — if ERP and operational complexity dominate
3. Adobe Commerce — if customization depth is critical
4. Salesforce Commerce Cloud — if Salesforce is your enterprise backbone
5. Shopify Plus — if speed and operational simplicity outweigh deep customization

I would evaluate them against your actual complexity drivers:

• number of markets
• number of storefronts/brands
• SKU count and variants
• pricing models
• ERP/PIM/OMS landscape
• B2B vs B2C mix
• localization requirements
• internal engineering capacity

If you share your industry (B2B/B2C), ERP/PIM stack, number of markets, and whether you need headless, I can narrow this to a 2–3 platform recommendation.

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

My shortlist

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

1. Shopify Plus — my default recommendation

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

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

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

I'd consider an architecture roughly like:

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

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

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

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

I'd choose Shopify Plus if:

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

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

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

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

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

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

I'd choose commercetools if:

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

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

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

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

I'd lean Adobe when the business says:

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

rather than:

"We have lots of external systems."

Those are different problems.

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

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

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

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

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

I'd evaluate you against these dimensions instead:

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

My decision rule

I'd probably use this as the initial filter:

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

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

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

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

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

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

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.