ChatGPT answers, unedited

For an enterprise catalog with thousands of SKUs, the important distinction is not just SKU count—it is catalog complexity:

• Do products have deep variant structures (size/color/configuration)?
• Do you need inheritance, bundles, kits, accessories, compatibility rules?
• Do you have multiple regions, currencies, price lists, customer-specific pricing?
• Is it B2B (accounts, contracts, quotes) or B2C?
• Do you need ERP/PIM integration and multiple storefronts?

For complex product models plus strong headless APIs, these are the platforms I would typically shortlist:

My usual enterprise shortlist

1. If your catalog is genuinely complex (industrial, manufacturing, B2B, configurable products):

• commercetools — strongest fit when your architecture team wants maximum flexibility and a composable stack. Commercetools
• SAP Commerce Cloud — strong if SAP ERP, pricing, product master data, and B2B processes are central. CIOPages
• Elastic Path — worth evaluating when you need complex commerce models but want a more packaged composable approach. Elastic Path

2. If you have thousands of SKUs but mostly standard retail products:

• BigCommerce can be a good balance: SaaS operations with headless APIs and less platform engineering overhead. BigCommerce

Questions I would use to narrow it down:

1. How many SKUs are you expecting at peak (10k, 100k, 1M+)?
2. Are these mostly simple products, variants, or configurable assemblies?
3. Is this primarily B2B, B2C, or both?
4. What systems currently own product data (PIM, ERP, PLM)?
5. Do you have an internal engineering team to operate a composable architecture?

Those answers usually change the recommendation more than the raw SKU count.

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

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

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

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

My shortlist

Why I'd lean commercetools

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

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

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

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

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

When I'd choose something else

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

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

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

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

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

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

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

When I'd choose something else

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d put commercetools at the top of the shortlist—especially if you’re building a composable/headless architecture.

My ranking

1. commercetools — strongest overall

This is the one I'd evaluate first.

Its catalog model supports products, variants, typed attributes, assets, localized data, pricing, and complex assortments. More importantly for your situation, its 2026 Modular Product Catalog makes variants first-class resources, supporting up to 10,000 variants per product rather than forcing everything into a single giant product payload. commercetools Documentation commercetools Documentation

That's particularly interesting if your "thousands of SKUs" aren't simply color/size combinations but things like:

• configurable products
• multiple variant dimensions
• regional assortments
• B2B-specific products/pricing
• product relationships
• localized attributes
• bundles/kits
• channel-specific availability
• large variant counts

It also has both HTTP and GraphQL APIs, plus dedicated Product Search and Product Projection APIs for storefront use cases. commercetools Documentation commercetools Documentation

commercetools.com

Caveat: it's powerful precisely because it's composable. You'll generally have more architecture/integration work than with an all-in-one SaaS platform.

2. Saleor — excellent if your engineering team wants GraphQL

I'd put Saleor very high on the list if API quality and developer control are more important than having a highly mature enterprise commerce ecosystem.

Saleor is natively GraphQL and headless, with product types, attributes, variants, channels, metadata and extensibility built into its model. Its documentation specifically supports modeling/extending the commerce model and multi-channel catalogs. Saleor Documentation Saleor Commerce

docs.saleor.io

It's particularly attractive if you have a strong internal engineering organization and don't mind owning more of the platform architecture.

3. BigCommerce — good managed alternative

BigCommerce becomes attractive if you want SaaS operational simplicity while retaining good headless capabilities.

Its catalog API supports products, variants, modifiers, custom fields and metafields, and its GraphQL Storefront API can retrieve product/option/variation information efficiently. BigCommerce BigCommerce

BigCommerce also claims it can update 100,000 products in under a minute through its catalog API, which is relevant if your concern is bulk catalog operations rather than just storefront reads. BigCommerce

bigcommerce.com

The limitation is that I'd choose it less readily when the product model itself is the difficult part of the problem. commercetools and Saleor give you more architectural freedom.

What I'd choose for your situation

If your catalog is:

5,000–100,000+ SKUs, lots of attributes/variants, multiple markets/channels, B2B requirements, and a custom frontend → commercetools.

If it's:

Thousands of SKUs + highly custom domain model + strong engineering team + preference for GraphQL/open source → Saleor.

If it's:

Thousands of relatively conventional SKUs + you want managed SaaS + headless storefront → BigCommerce.

One particularly important question is what "complex product model" means in your catalog. If you tell me whether you're dealing with things like configurable products, variant matrices, bundles/kits, B2B customer-specific catalogs/pricing, product relationships, or PIM-driven attributes, I can narrow this down to a 2–3 platform shortlist and explain where each one will hit limits.

For an enterprise catalog with thousands of SKUs and genuinely complex product models, my first choice would be commercetools.

My shortlist

Why I'd lean commercetools

Its product model is unusually flexible: Product Types → Products → Variants/SKUs, with custom attributes, categories, product selections, localization, pricing, and search exposed through APIs. commercetools Documentation commercetools Documentation

More importantly for a very large SKU catalog, commercetools introduced its Modular Catalog model in 2026. Variants become first-class resources rather than being embedded inside the parent product, supporting up to 10,000 variants per product and allowing variant-level retrieval and publishing. commercetools Documentation commercetools Documentation

It also provides both REST and GraphQL APIs, which is useful when you're building custom storefronts or multiple consuming applications. commercetools Documentation

commercetools.com

When I'd pick Elastic Path instead

Elastic Path is particularly compelling if your catalog complexity is tied to B2B rules, contract pricing, price books, bundles, and customer-specific assortments. Its Product Experience Manager explicitly targets thousands of SKUs/catalogs and API-first, headless implementations. Elastic Path

elasticpath.com

When BigCommerce makes more sense

If you want less implementation overhead while retaining a good headless architecture, BigCommerce is worth serious consideration. Its catalog API handles products, variants, custom fields/metafields, bulk operations, categories, and pricing rules, while its GraphQL Storefront API supports catalog queries, filtering, sorting, carts, and checkout. BigCommerce BigCommerce

bigcommerce.com

Bottom line: If your requirement is “thousands of SKUs + complicated attributes/variants + multiple channels + API-first/headless + enterprise scale,” I'd put commercetools at #1, Elastic Path at #2, and BigCommerce at #3.

If you tell me whether your catalog is B2B, B2C, or both and roughly how many SKUs/variants, I can narrow this to 2–3 platforms and compare their product-modeling capabilities, APIs, pricing, and migration difficulty.

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

My shortlist

Why commercetools: its current catalog model is particularly interesting for your use case. Its modular product model supports up to 10,000 variants per product (with limits subject to project/performance review), and variants can be managed as standalone entities through its API. It also exposes dedicated Product Search and Product Projection APIs. commercetools Documentation Commercetools

That makes it a strong candidate if your catalog isn't just "product + color + size," but involves things like:

• Deep variant structures and thousands of SKU-level entities
• Multiple product types
• Bundles/kits
• Regional assortments and localization
• Customer/channel-specific pricing
• B2B catalogs
• Multiple brands or storefronts
• External PIM/ERP/OMS integrations
• Custom frontend applications consuming APIs directly

BigCommerce is the pragmatic alternative

BigCommerce is worth serious consideration if you want more of a managed SaaS platform rather than going all-in on composable architecture.

Its Catalog API supports products, variants, variant options, modifiers, custom fields, metafields, categories and bulk operations. Its GraphQL Storefront API can expose product options, variants, custom fields, pricing and customer/channel-specific availability to a headless frontend. BigCommerce BigCommerce

The important distinction is that BigCommerce's model is still more conventional. For example, variants correspond to SKU-level purchasable entities, while modifier combinations don't create separately inventory-tracked variants. BigCommerce BigCommerce

What I'd choose

If your catalog looks like:

10,000+ SKUs → many product types → complex attributes/relationships → multiple markets/channels → PIM/ERP integration → custom frontend

I'd evaluate commercetools first, then Saleor, then BigCommerce.

If instead it's:

Thousands of relatively conventional SKUs → need headless → want SaaS/managed operations → don't want to assemble as many composable pieces

I'd lean toward BigCommerce.

One particularly useful test during an RFP is to take 5–10 of your nastiest real products and ask each vendor to model them without flattening the data. That tends to expose platform limitations much faster than generic feature matrices.

For an enterprise catalog with thousands of SKUs, the deciding factors are usually not raw SKU count but product model flexibility, catalog inheritance, variant complexity, pricing rules, localization, channel support, and API maturity. The strongest candidates tend to be composable/headless platforms rather than traditional storefront-first systems. Netguru

A shortlist I would evaluate:

How I would choose based on your catalog complexity

Choose commercetools if you have:

• Thousands to millions of SKUs
• Many product families with different attributes
• Multiple storefronts/brands/countries
• A separate PIM, ERP, CMS, search, and frontend stack
• Developers who want full control over APIs and data models

Choose SAP Commerce Cloud if you have:

• SAP ERP as a core system
• Complex B2B pricing agreements
• Dealer/distributor workflows
• Product configuration or industrial catalogs
• Large operational teams managing commerce processes

Choose BigCommerce if you want:

• Faster implementation
• A managed SaaS backend
• Headless storefronts without building as much infrastructure
• A catalog that is complex but not deeply configuration-driven

A few architecture questions matter more than SKU count

For your use case, I would ask:

1. Do products have wildly different schemas?

• Example: industrial equipment vs apparel vs spare parts.
• If yes, favor platforms with flexible product types and attributes.
• Do you need configurable products?

• Example: "choose motor → voltage → accessories → installation options."
• This pushes you toward SAP Commerce, commercetools, or specialized configuration services.
• Where does your product truth live?

• ERP?
• PIM?
• Commerce platform?
• Multiple sources?
• How complicated are pricing rules?

• Customer-specific pricing
• Contracts
• Regional pricing
• Volume tiers
• Promotions

For a large enterprise catalog with complex product models, my initial ranking would usually be:

1. commercetools — best pure headless/composable architecture
2. SAP Commerce Cloud — best for enterprise B2B complexity and ERP alignment
3. Elastic Path / Spryker — strong alternatives for highly customized commerce
4. BigCommerce Enterprise — best when you want more SaaS simplicity

If you describe your catalog (B2B vs B2C, number of attributes, variants/configurators, ERP/PIM systems, regions, and whether you need marketplace support), I can narrow this to a more realistic shortlist.

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

My shortlist

Why I'd favor commercetools

Its catalog model separates Product Types, Attributes, Products, and Product Variants, which gives you considerably more control than a simple product/variant/options model. Commercetools Documentation Commercetools Documentation

More importantly for your use case, its newer Modular Product Catalog Model can support up to 10,000 variants per product, with variants managed as standalone entities rather than being embedded in a huge product document. Commercetools Documentation Commercetools Documentation

It also exposes REST and GraphQL APIs, Product Search, Product Projection/Variant Projection APIs, pricing, categories, assortments, etc., making it particularly suitable when your frontend is completely decoupled. Commercetools Documentation Commercetools Documentation

docs.commercetools.com

Where BigCommerce is interesting

BigCommerce deserves serious consideration if you want less architectural complexity.

Its GraphQL Storefront API supports headless storefronts, while its REST Catalog APIs handle products, variants, categories, brands, custom fields, etc. BigCommerce BigCommerce BigCommerce also claims catalog API performance around updating 100,000 products in under a minute. BigCommerce

The catch is the product model is less expressive than commercetools for highly relational/heterogeneous catalogs. There is also a documented 600-SKU-per-product limit in its variant API. BigCommerce

The decision I'd make

If your catalog has things like:

• thousands or tens of thousands of SKUs
• many product types with different attributes
• configurable products
• bundles/kits
• B2B-specific assortments
• multiple brands/regions/channels
• customer-specific pricing
• ERP/PIM integration
• multiple frontends
• sophisticated search/filtering
• a desire to keep the commerce engine separate from presentation

→ commercetools is probably the strongest architectural fit.

If your catalog is large but relatively conventional—products → options → variants—and your priority is getting to market without operating a highly composable architecture, I'd look harder at BigCommerce.

If you're already heavily invested in SAP, SAP Commerce Cloud becomes much more compelling despite its greater implementation complexity.

If you tell me roughly how many SKUs you have, how many product types, whether you have bundles/configurators, B2B vs B2C, and what PIM/ERP you use, I can narrow this to a 2–3 platform recommendation and compare their actual catalog/API models.

docs.commercetools.com

Where BigCommerce is interesting

BigCommerce deserves serious consideration if you want less architectural complexity.

Its GraphQL Storefront API supports headless storefronts, while its REST Catalog APIs handle products, variants, categories, brands, custom fields, etc. docs.bigcommerce.com docs.bigcommerce.com BigCommerce also claims catalog API performance around updating 100,000 products in under a minute.

The catch is the product model is less expressive than commercetools for highly relational/heterogeneous catalogs. There is also a documented 600-SKU-per-product limit in its variant API.

The decision I'd make

If your catalog has things like:

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

My shortlist

Current industry comparisons similarly put commercetools toward the enterprise end for complex catalogs, multi-region architectures, and composable commerce, while Saleor and Medusa are stronger choices when you want more control over the underlying platform. Naturaily Netguru

Why I'd lean commercetools

If your SKU model looks like:

• Products → variants → configurable options
• Lots of attributes and product relationships
• Regional catalogs and localized data
• Multiple currencies and price lists
• Customer/account-specific pricing
• B2B catalogs
• Multiple sales channels
• ERP/PIM/OMS integration
• Independent frontend applications
• Thousands or potentially hundreds of thousands of SKUs

then commercetools' API-first/composable architecture is particularly compelling. It is designed more like a set of commerce services than a traditional monolithic ecommerce application. Naturaily Netguru

Saleor would be my second choice if your engineering organization strongly prefers GraphQL and open-source control. Its GraphQL-first API, multi-channel, multi-warehouse, and multi-currency capabilities make it unusually attractive for sophisticated catalogs without going all the way to commercetools' enterprise platform. Ribbsaeter Systems Guideflow

I'd consider SAP Commerce Cloud or Adobe Commerce instead if your complexity is heavily tied to an existing SAP/Adobe enterprise stack rather than primarily to the product model itself.

One important distinction: "thousands of SKUs" isn't actually the hard part. I'd evaluate how well each platform handles your product graph, variant inheritance, attribute schemas, pricing rules, catalog segmentation, localization, and PIM/ERP synchronization. That's where the platforms diverge significantly.

If you tell me roughly how your product model works (e.g. configurable products, bundles/kits, variants, compatibility relationships, customer-specific SKUs/pricing, regional catalogs), I can narrow this to 2–3 platforms and compare their actual catalog/API models.

For an enterprise catalog with thousands of SKUs, the right headless commerce platform depends less on raw SKU count and more on your catalog complexity: variants, configurable products, bundles, regional pricing, B2B contracts, customer-specific catalogs, workflows, and integrations.

The platforms I’d put on a shortlist:

My usual ranking for a complex SKU catalog

1. commercetools — if your catalog is truly complex
Choose it when you have:

• Many product families with different attributes
• Multiple storefronts/channels
• Complex pricing rules
• Heavy ERP/PIM integration
• A dedicated engineering team

Its catalog model supports structured product types, categories, variants, attributes, and API-driven product retrieval. commercetools Documentation

2. Elastic Path — if B2B complexity is the main challenge
Strong choice for:

• Customer-specific catalogs
• Contract pricing
• Account-based purchasing
• Configurable products
• Large enterprise catalogs

Elastic Path specifically positions itself around complex B2B commerce, advanced pricing, and large catalog scenarios. Elastic Path Elastic Path

3. Add a PIM alongside commerce
For thousands of SKUs, many enterprises avoid making commerce the source of truth for product data. A common architecture is:

ERP → PIM → Commerce platform → Search → Frontends

A PIM such as Akeneo can manage rich product attributes, variants, localization, and enrichment workflows before publishing to commerce APIs. Akeneo API Documentation

Questions that would change the recommendation:

1. Are these SKUs mostly simple products or complex variants/configurations (e.g., size × color × material × region)?
2. Is this primarily B2B, B2C, or both?
3. Do you need customer-specific pricing/catalogs?
4. What is your current source of truth: ERP, PIM, or the commerce platform itself?
5. Roughly how large: 10k SKUs, 100k, 1M+?

For a typical enterprise catalog with complex models, I’d start by evaluating commercetools vs Elastic Path, with a PIM layer if product data governance is important.

A PIM such as Akeneo can manage rich product attributes, variants, localization, and enrichment workflows before publishing to commerce APIs.

Questions that would change the recommendation:

For an enterprise catalog with thousands of SKUs, the deciding factors are usually not the number of products alone, but whether the platform can handle:

• complex product hierarchies (variants, bundles, kits, configurable products)
• multiple catalogs and price books
• customer-specific pricing
• regional/channel catalogs
• ERP/PIM synchronization
• rich product attributes and relationships
• high-volume APIs for storefronts, apps, marketplaces, and internal tools

The strongest candidates are typically these:

My shortlist for a "thousands of SKUs + complex models" scenario

1. commercetools

Best if your catalog is genuinely complex:

• industrial parts
• configurable products
• many attributes
• multiple sales channels
• custom pricing logic
• custom storefront experiences

Its strength is that you are not forced into a predefined catalog structure; your engineering team can model commerce domains around your business. The tradeoff is that it requires strong architecture and development capability. Digital Applied

2. Elastic Path

A strong fit if you want enterprise flexibility without building quite as much commerce infrastructure yourself. It is particularly positioned around B2B complexity, deep catalogs, and composable implementations. Elastic Path

3. SAP Commerce Cloud

If your SKU data originates in SAP ERP, this often becomes the practical choice. It handles enterprise product classification and integration scenarios well, but it is heavier operationally.

4. Spryker

Worth evaluating for:

• distributors
• manufacturers
• marketplaces
• multi-business-model companies

It emphasizes complex workflows and multiple commerce models rather than just storefront selling. Spryker

Things I would test in vendor demos

Do not just ask "how many SKUs can you support?" Ask them to demonstrate:

1. Product inheritance

• Can a product family inherit attributes?
• Can child SKUs override values?
• Complex variants

• Example: a machine part with size, material, voltage, region, compatibility, and lifecycle status.
• Multiple catalogs

• Can different customers see different assortments and prices?
• Bulk catalog operations

• Import/update 50,000 products nightly.
• Partial updates through APIs.
• Search integration

• How does it connect to Algolia, Elastic, or similar search engines?
• ERP/PIM ownership

• Does commerce own product data, or is it just consuming it from a PIM/ERP?

A practical rule of thumb

• Complex B2B + strong engineering team → commercetools or Elastic Path
• SAP enterprise → SAP Commerce Cloud
• Industrial/manufacturing/distribution → Spryker or SAP Commerce
• Existing Magento investment → Adobe Commerce
• Salesforce ecosystem → Salesforce Commerce Cloud

If you describe your catalog type (B2B vs B2C, configurable products vs simple variants, ERP/PIM systems, and approximate SKU/attribute counts), I can narrow this to a 2–3 platform shortlist.

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

My shortlist

Why I'd favor commercetools

Its catalog model is unusually strong for complex enterprise data: Product Types → Attributes → Products → Variants, with custom fields, categories, product selections, tailoring, pricing and inventory. It exposes both REST and GraphQL APIs. commercetools Documentation commercetools Documentation

There is also an important recent development: commercetools now offers Product Catalog as a standalone module, explicitly aimed at enterprise catalogs and supporting millions of SKUs. Commercetools

One caveat: the traditional product model has a 100-variant-per-product limit, although commercetools now documents a modular variant model supporting up to 10,000 variants per product. That's something I'd investigate carefully if your "complex products" mean enormous variant matrices rather than simply thousands of independent SKUs. commercetools Documentation

BigCommerce is a good second choice if your models are mostly conventional products with variants, modifiers, custom fields and channel assignments. Its Catalog API supports batch operations and complex products, but I'd choose commercetools when the catalog itself is a major architectural concern. BigCommerce BigCommerce

If you tell me what makes your product model complex (e.g. configurable machinery, bundles/kits, B2B customer-specific assortments/pricing, 10k+ variants, localized catalogs, product relationships, subscriptions), I can narrow this down to the best 2–3 platforms and explain the tradeoffs.

For an enterprise catalog with thousands of SKUs, complex product relationships, lots of attributes, and a headless/API-first architecture, I’d put commercetools and Elastic Path at the top of the shortlist.

My first choice: commercetools

commercetools.com is particularly strong if your catalog is genuinely complicated rather than simply large.

Its model separates Products, SKUs/Variants, Product Types, Attributes, Categories, Product Selections, and Product Projections, with REST and GraphQL APIs. Its newer modular catalog model can support up to 10,000 variants on a product, versus 100 in the classic model. commercetools commercetools

It also lets you define typed custom attributes and custom fields, which is useful when you have things like:

• Different schemas for different product families
• Technical specifications
• Configurable products
• Regional/channel assortments
• Multiple catalogs and price structures
• Complex SKU/variant relationships
• Highly customized storefronts
• ERP/PIM/OMS integrations

The tradeoff is that commercetools expects a fairly capable engineering team. You get tremendous modeling freedom, but you'll be responsible for more of the architecture around it.

Strong alternative: Elastic Path

elasticpath.com is especially compelling if your catalog complexity is intertwined with B2B pricing, customer-specific catalogs, bundles, contracts, or multiple markets.

Its Product Experience Manager is explicitly designed around complex catalogs, bundles, variations, multiple catalogs, dynamic pricing and multi-market data. Elastic Path also describes its stack as API-first/headless and designed to integrate with PIM, ERP, CMS, OMS and other systems. Elastic Path Elastic Path

I'd lean Elastic Path over commercetools if your problem sounds more like:

"We have thousands of products, but the hard part is different customers seeing different products/prices/bundles."

I'd lean commercetools if it's more:

"Our product model itself is complicated and we need maximum control over how the catalog is represented and exposed through APIs."

Where BigCommerce fits

bigcommerce.com is worth considering if you want less implementation complexity and faster time to market. It has strong APIs and Enterprise capabilities, including localized product custom fields for multi-storefront scenarios. BigCommerce

But for a catalog with unusually deep product relationships or highly bespoke data modeling, I'd generally put it behind commercetools/Elastic Path.

Bottom line

Shortlist commercetools + Elastic Path first.

If you give me roughly (1) number of SKUs/variants, (2) B2B vs B2C, (3) how many product types, (4) whether you need configurable/bundled products, and (5) your PIM/ERP stack, I can give you a much more concrete platform recommendation and architecture comparison. commercetools Elastic Path

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

My shortlist

Why I'd lean commercetools

Its catalog model is unusually flexible: Product Types → Products → Variants → Attributes → Categories, with typed attributes, localization, constraints, references, pricing, and custom fields. commercetools Documentation commercetools Documentation commercetools Documentation

More importantly for your situation, commercetools now has a Modular Product Catalog model where variants are standalone resources and a product can have up to 10,000 variants—a significant improvement over the classic 100-variant model. commercetools Documentation commercetools Documentation

For headless implementations, it provides REST/HTTP APIs plus GraphQL, and its Product Search/Projection APIs are designed around storefront retrieval rather than forcing you to pull an enormous product object every time. commercetools Documentation commercetools Documentation

That makes it particularly attractive if your catalog looks something like:

• Products with hundreds/thousands of SKU variants
• Multiple dimensions such as size × color × configuration
• Different attributes by product family
• B2B-specific pricing/customer groups
• Regional/localized catalogs
• Multiple brands or storefronts
• Bundles/kits or related products
• External PIM/ERP/OMS integrations
• Several frontends consuming the same catalog API

One important caveat

I wouldn't choose based simply on "thousands of SKUs." Thousands of SKUs is easy for most enterprise platforms. The differentiator is whether you have complex relationships and rules between those SKUs.

If you tell me roughly how your catalog is structured—e.g. 50k products / 500k variants, configurable products, bundles, B2B pricing, multiple regions, PIM integration, etc.—I can give you a much more specific commercetools vs. Adobe vs. Salesforce vs. BigCommerce vs. Saleor recommendation and architecture.

For headless implementations, it provides REST/HTTP APIs plus GraphQL, and its Product Search/Projection APIs are designed around storefront retrieval rather than forcing you to pull an enormous product object every time.

That makes it particularly attractive if your catalog looks something like:

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

My shortlist

Why I'd favor commercetools

Its catalog model is unusually flexible: Product Types define attributes, products can have variant-specific attributes, and products can be assigned to multiple categories and product selections. commercetools commercetools

More importantly for a very large SKU catalog, commercetools introduced a Modular Product Catalog Model in 2026 where variants become first-class resources rather than being embedded inside the product. That supports up to 10,000 variants per product, versus 100 in the classic model. commercetools commercetools

It also gives you dedicated APIs for catalog management, product search, product projections, variants, pricing, etc., plus GraphQL when you need to avoid pulling enormous product documents. commercetools commercetools

That's a particularly good architecture if your catalog has things like:

• thousands/millions of SKUs
• configurable products
• many attributes with different schemas by product family
• regional/channel-specific assortments
• B2B-specific catalogs and pricing
• bundles and related products
• multiple brands or storefronts
• localized product data
• custom storefronts/mobile apps/marketplaces consuming the same APIs

docs.commercetools.com

When I'd choose the others

SAP Commerce Cloud — I'd strongly consider it if your organization already runs SAP ERP/S4HANA and the catalog, pricing, inventory, and order processes need deep SAP integration. Its enterprise capabilities can outweigh the architectural elegance of a pure composable platform.

Salesforce Commerce Cloud — a strong choice if Salesforce is already your enterprise customer/data ecosystem. Salesforce explicitly supports headless APIs and front-end framework freedom, with B2B and B2C capabilities. Salesforce

Elastic Path — worth evaluating if your primary requirement is an API-first architecture and highly customized product/commerce models, particularly if you don't want a traditional monolithic commerce suite.

My recommendation

If catalog complexity + API quality + architectural flexibility are the dominant criteria, I'd evaluate:

1. commercetools → 2. Elastic Path → 3. SAP Commerce Cloud → 4. Salesforce Commerce Cloud

But the ranking changes substantially if you're already standardized on SAP or Salesforce.

If you tell me roughly how many SKUs/variants you have, how many product types, B2B vs. B2C, number of regions/channels, and whether you need PIM functionality, I can give you a much more specific architecture recommendation—including which platform I'd pick and how I'd model the catalog.

For an enterprise catalog with thousands of SKUs, the key question is less “which platform is headless?” and more which platform has a product model flexible enough for your SKU complexity, variants, relationships, pricing rules, and integrations. The strongest candidates are usually:

My shortlist for a thousands-SKU enterprise catalog

1. commercetools — strongest pure headless choice

I would put this at the top if you have:

• Multiple storefronts or channels
• Multiple regions/languages
• Complex product attributes
• A dedicated engineering team
• A desire to compose your stack (PIM, CMS, search, ERP, OMS separately)

It is built around API-driven commerce primitives rather than a traditional storefront, which makes it a strong fit when the catalog is the core asset and you expect the model to evolve. commercetools

Typical product scenarios it handles well:

• Product variants (size/color/configuration)
• Custom attributes by product type
• Multiple catalogs
• Regional assortment differences
• B2B customer-specific pricing
• Multiple sales channels

2. SAP Commerce Cloud — strongest for industrial/B2B complexity

Consider it if your catalog has:

• Tens or hundreds of thousands of SKUs
• Manufacturer/distributor workflows
• Complex account pricing
• ERP-driven product data
• Configurable products

SAP tends to win where commerce is deeply tied to enterprise back-office processes.

3. Elastic Path — strong B2B composable alternative

Worth evaluating if you need:

• Complex B2B purchasing flows
• A headless-first architecture
• More packaged commerce capabilities than a pure platform toolkit

Capabilities I would test in a vendor bake-off

For your catalog, I would not start with SKU count alone. Test these:

1. Product modeling

• Can a product have different attributes by category?
• Can you model configurable products without custom code?
• Can you represent bundles/kits/substitutions?
• Catalog operations

• Can merchandisers manage thousands of changes safely?
• Can you bulk import/export?
• Are approval workflows available?
• Search integration

• How does it integrate with Algolia, Bloomreach, or Elastic?
• Can catalog data be indexed efficiently?
• Pricing

• Customer-specific price lists?
• Contract pricing?
• Regional currencies?
• Promotions?
• Integration model

• PIM integration (e.g., Akeneo, Salsify, inriver)
• ERP integration (SAP, Oracle, Dynamics)
• OMS/inventory synchronization

Practical recommendation

For a large enterprise with thousands of SKUs and a modern headless roadmap, I would usually narrow the first proof-of-concept to:

1. commercetools — if you want maximum flexibility and API-first architecture
2. SAP Commerce Cloud — if you are a manufacturing/distribution enterprise with heavy ERP dependency
3. Elastic Path — if B2B complexity is the dominant requirement

The deciding factor is usually not SKU volume; it is whether your catalog is simple retail inventory or a complex product information model with rules, configurations, customer-specific pricing, and multiple channels.

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

My ranking

1. commercetools — strongest overall fit

This is the one I'd investigate first.

Its product model separates Products from sellable Product Variants/SKUs, with typed Product Types and extensible attributes. Its newer Modular Product Catalog model supports up to 10,000 variants per product, subject to project limits/performance review. commercetools Documentation commercetools Documentation

It is also genuinely composable rather than merely offering a headless storefront API. You can integrate PIM, ERP, search, pricing, promotions, CMS, etc., independently. commercetools

commercetools.com

Particularly good if you have:

• Thousands or hundreds of thousands of SKUs
• Lots of attributes and product types
• Variant-heavy products
• B2B pricing/assortments
• Multiple brands, regions, currencies or channels
• PIM/ERP integrations
• Multiple frontend experiences
• A team comfortable owning a composable architecture

2. Saleor — excellent if GraphQL is a priority

Saleor is especially compelling if your engineering organization wants a GraphQL-native, API-only commerce backend.

Saleor explicitly supports rich product models, attributes, metadata, multi-channel catalogs, multi-region commerce, and extensibility through APIs/apps/webhooks. Saleor Documentation GitHub

saleor.io

I'd choose Saleor over commercetools when developer control, GraphQL, and open-source flexibility matter more than having the broadest enterprise commerce platform.

3. BigCommerce — easier operationally

BigCommerce is worth considering if you want strong APIs without taking on as much composable-commerce complexity.

It provides both REST and GraphQL APIs, and its GraphQL Storefront API exposes products, variants, options, pricing, and metafields. BigCommerce BigCommerce

bigcommerce.com

The tradeoff is that I'd generally favor commercetools or Saleor when the product model itself is one of your hardest architectural problems.

What I'd pick for your situation

If your catalog is something like:

Product → models → variants → configurations → regional assortments → customer-specific pricing → bundles/kits → channel-specific attributes

then my shortlist would be:

1. commercetools — best overall enterprise catalog/composable architecture
2. Saleor — best API/GraphQL-first alternative
3. BigCommerce — best if you want more out-of-the-box commerce operations

One important architectural point: don't use the commerce platform as your PIM just because it has a product model. For a large enterprise catalog, I'd usually make the PIM/MDM the system of record for rich product data and synchronize the commerce-specific subset into the commerce platform. commercetools' own integration guidance makes this distinction explicitly: PIM can own enriched content while ERP owns things such as SKUs, pricing, and inventory, with commerce receiving the data it actually needs. commercetools Documentation

If you tell me roughly how many SKUs/variants you have, how many product types, whether you need B2B pricing, and what PIM/ERP you're using, I can narrow this down to a commercetools vs. Saleor vs. BigCommerce architecture recommendation rather than just a platform ranking.

For an enterprise catalog with thousands of SKUs and complex product models, I would focus less on raw SKU count and more on whether the platform can handle:

• Deep product hierarchies and variant models
• Multiple catalogs/assortments by customer, region, channel, or brand
• Complex attributes (technical specs, compatibility, dimensions, certifications)
• B2B pricing rules and contract catalogs
• Bundles/configurable products/kits
• ERP/PIM integration patterns
• Strong APIs for custom storefronts and applications

The strongest candidates are usually:

Elastic Path commercetools## My shortlist for your scenario

1. commercetools — best if your team wants maximum modeling freedom

Choose this if you have a strong engineering organization and want to build a custom commerce ecosystem.

Strengths:

• Flexible product types and attributes
• Good fit for thousands to millions of SKUs
• Designed around APIs and composable architecture
• Works well when storefront, search, CMS, pricing, and inventory are separate services

Tradeoff:

• You are assembling more of the solution yourself. Complex B2B workflows often require additional services or custom development. commercetools

2. Elastic Path — best if catalog complexity is high but you want more packaged commerce capability

A strong fit when products are not simple "shirts with sizes," but things like:

• industrial parts
• configurable equipment
• subscriptions
• bundles
• customer-specific catalogs
• dealer/distributor channels

Elastic Path emphasizes custom objects/extensions and complex B2B use cases. Elastic Path

3. SAP Commerce Cloud — best for ERP-heavy organizations

If your catalog is mastered in SAP, with complex pricing, inventory, fulfillment, and product classification requirements, SAP Commerce is often shortlisted because it aligns well with SAP-centric enterprises.

Questions I would use to narrow it down

1. How many SKUs and variants?

• 10k SKUs is a very different problem than 5M configurable SKUs.
• Are products simple or configurable?

Examples:

• Simple: SKU + attributes + images
• Complex: "Choose motor → voltage → accessory package → warranty → installation option"
• Do you need customer-specific catalogs?

For example:

• Distributor A sees 30k products
• Distributor B sees 15k products
• Each has negotiated pricing
• Where is product truth today?

• ERP (SAP, Oracle, Dynamics)?
• PIM?
• Existing commerce platform?
• How much engineering capacity do you have?

• A 20-person commerce engineering team can thrive with commercetools.
• A smaller team may prefer more packaged capabilities.

If you are managing a large B2B catalog with complex SKUs, customer-specific pricing, and integrations, my initial ranking would usually be:

1. Elastic Path — complex catalog + B2B practicality
2. commercetools — maximum flexibility for engineering-heavy teams
3. SAP Commerce Cloud — SAP-centered enterprises
4. Spryker — complex B2B/marketplace scenarios
5. Adobe Commerce — when Magento heritage matters

The deciding factor is usually not "can it handle thousands of SKUs?" — most enterprise platforms can. It is how elegantly it models your product rules and how much custom code you need to maintain afterward.

1. Elastic Path — complex catalog + B2B practicality
2. commercetools — maximum flexibility for engineering-heavy teams
3. SAP Commerce Cloud — SAP-centered enterprises
4. Spryker — complex B2B/marketplace scenarios
5. Adobe Commerce — when Magento heritage matters

The deciding factor is usually not "can it handle thousands of SKUs?" — most enterprise platforms can. It is how elegantly it models your product rules and how much custom code you need to maintain afterward.

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d shortlist commercetools and Elastic Path first, with SAP Commerce Cloud worth considering if you’re deeply invested in SAP.

My ranking

1. commercetools.com — strongest overall for complex, API-first catalogs

• Very strong product modeling, custom attributes, variants, pricing, search, and multi-channel catalogs.
• Its APIs are genuinely central to the architecture rather than a headless layer added onto a traditional platform.
• A particularly relevant 2026 development: its new Modular Catalog makes variants first-class API resources and raises the model from 100 variants/product to up to 10,000 variants per product. commercetools Documentation commercetools Documentation
• Best fit if you have a strong engineering team and want maximum control over your commerce architecture.
• elasticpath.com — arguably easier for highly complex B2B/catalog scenarios

• API-first and composable, with particular emphasis on complex catalogs, pricing, bundles, multi-brand, and B2B/B2B2C requirements. Elastic Path Elastic Path
• The big advantage versus commercetools is that it tries to provide more packaged commerce capabilities rather than making your team assemble everything from granular APIs.
• I'd favor it if your catalog complexity is accompanied by complex business rules, rather than simply lots of SKUs.
• SAP Commerce Cloud — strong if SAP is already your enterprise backbone

• Makes sense when product/catalog data is tightly connected to SAP ERP, pricing, inventory, or other SAP systems.
• Its downside is that it isn't as cleanly composable/API-native as the two above, so I wouldn't choose it just because you want headless.

For your specific situation

If by "complex product models" you mean something like:

Product → configurable variants → hundreds/thousands of attributes → multiple catalogs → regional assortments → customer-specific pricing → bundles/kits → multiple brands/channels → ERP/PIM synchronization

I'd put commercetools slightly ahead.

Its current catalog model is especially interesting for your use case: variants can be independently modeled, retrieved, published, and managed through APIs, rather than forcing a huge product object containing every SKU. commercetools Documentation commercetools Documentation

If the complexity is more like B2B contracts, account-specific catalogs, negotiated pricing, bundles, subscriptions, and sophisticated business rules, I'd give Elastic Path a very serious look.

One important distinction: "thousands of SKUs" itself isn't the hard part. Almost any enterprise platform can store thousands or millions. The questions I'd use to separate the platforms are how many variants per parent, attribute inheritance, catalog hierarchies, contextual pricing, bulk imports, API ergonomics, search, and how much custom orchestration your team has to build.

If you tell me roughly how your catalog is modeled (e.g. number of SKUs, variants per product, configurable products, B2B pricing, PIM/ERP, number of regions), I can give you a commercetools vs Elastic Path vs SAP comparison specifically against your architecture.

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

My ranking

Why I'd favor commercetools

commercetools is unusually strong at separating product definitions, attributes, products, variants/SKUs, categories, pricing, inventory, and channel-specific presentation. Its product model uses Product Types and configurable Attributes, with Products acting as parents to sellable Product Variants. commercetools Documentation commercetools Documentation

More importantly for your use case, commercetools now has a modular catalog model where variants can be standalone entities, supporting up to 10,000 variants per product rather than the 100-variant limit of its classic model. That's particularly relevant if your "thousands of SKUs" aren't simply flat products. commercetools Documentation commercetools Documentation

Its API architecture is also a major advantage: HTTP APIs for management, specialized Product Search/Projection APIs for storefront retrieval, and GraphQL when you need more selective product payloads. commercetools Documentation commercetools Documentation

docs.commercetools.com

When I'd choose the others

• Adobe Commerce — compelling if you have complicated configurable/bundle/grouped products, substantial B2B requirements, or already live deeply in Adobe. Its current architecture exposes commerce capabilities through GraphQL and includes a dedicated Catalog Service. Experience League Experience League
• Saleor — I'd seriously consider it if your organization is strongly engineering-led and wants a GraphQL-first platform with substantial control. It's particularly attractive when you want open-source flexibility without building as much of the commerce engine yourself. Ribbsaeter Systems
• BigCommerce — good if you want managed SaaS and headless flexibility without taking on as much infrastructure/platform ownership.
• Medusa — attractive when the catalog and checkout logic are highly bespoke and you have a strong TypeScript/Node engineering team. Its flexibility comes with more operational responsibility.

The important distinction

If by "complex product model" you mean something like:

Product family → configurable attributes → hundreds/thousands of variants → region/channel-specific assortments → customer-specific pricing → bundles/kits → localized content → multiple inventory sources

then I'd narrow the evaluation to commercetools vs. Adobe Commerce vs. Saleor.

If your catalog is more like 10,000–500,000 relatively straightforward SKUs, the catalog/search architecture becomes just as important as the commerce engine itself; you may want a dedicated PIM/search layer rather than forcing the commerce platform to be your entire product-information system.

My default enterprise choice: commercetools. Its product model and API architecture are particularly well aligned with a large, evolving catalog that needs to feed multiple frontends and channels. commercetools.com commercetools.com

If you tell me roughly how many SKUs, variants per product, B2B vs. B2C, number of countries/channels, and whether you already have a PIM, I can give you a much tighter commercetools vs. Adobe vs. Saleor recommendation.

For an enterprise catalog with thousands of SKUs, complex product relationships, and a strongly headless/API-driven architecture, my first choice would be commercetools.

My shortlist

Why I'd lean commercetools

Its architecture is particularly well suited to the problem you're describing. The platform exposes commerce capabilities through APIs, supports REST and GraphQL, and has dedicated product modeling around Product Types, attributes, variants, categories, pricing, and search. commercetools Documentation commercetools Documentation

More importantly, its Modular Catalog introduced first-class variants, removing the previous 100-variant-per-product constraint and allowing up to 10,000 variants per product in the modular model. That is a significant advantage if your "thousands of SKUs" eventually turns into highly variant-heavy products. commercetools Documentation

commercetools also announced a standalone Product Catalog offering in July 2026, explicitly targeting enterprise-scale product modeling, pricing, inventory, catalog management, and catalogs with millions of SKUs. commercetools

commercetools.com

When I'd choose SAP instead

If your organization is already deeply invested in SAP ERP/S/4HANA, SAP PIM, or SAP's broader ecosystem, SAP Commerce Cloud deserves very serious consideration. Its Product and Category API supports retrieving and searching products/categories, and SAP is designed for very large, complex enterprise commerce environments. SAP Help Portal

The tradeoff is generally more enterprise-suite complexity versus commercetools' more API-native/composable approach.

When BigCommerce makes more sense

BigCommerce is worth considering if you want headless APIs but don't want to build quite as much of the commerce architecture yourself. Its headless stack provides APIs/SDKs for product data, carts, checkout, customers and orders. BigCommerce

I'd put it ahead of commercetools when speed to implementation and conventional commerce functionality matter more than extremely sophisticated domain modeling.

Bottom line: if your catalog has things like product families → variants → configurable components → technical attributes → customer/market-specific assortments → multiple price lists → regional catalogs → B2B rules, I'd start the evaluation with commercetools, then benchmark it against SAP Commerce Cloud if you're a SAP shop.

If you tell me what makes your product model complex (e.g. configurable products, bundles/kits, variants, technical attributes, B2B pricing, regional catalogs), I can narrow this down to 2–3 platforms and compare their actual data models and APIs.

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

My first choice: commercetools

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

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

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

Elastic Path deserves a very close look

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

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

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

When I'd choose Saleor

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

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

What I'd actually shortlist

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

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

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

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

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

Elastic Path deserves a very close look

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

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

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

When I'd choose Saleor

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

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

What I'd actually shortlist

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

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

My pick: commercetools

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

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

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

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

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

rather than expecting the commerce platform to own everything.

Elastic Path is worth serious consideration

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

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

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

The important distinction

If you mean:

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

→ commercetools

If you mean:

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

→ Elastic Path

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

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

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

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

My ranking

1. commercetools — my first choice

commercetools is particularly strong if your catalog isn't just "products with a few options." Its model has Product Types, typed Attributes, Products, Variants, Categories, Product Selections, pricing and search, all exposed through APIs. commercetools Documentation commercetools Documentation

A particularly important development for your use case: in June 2026, commercetools introduced its Modular Catalog in public beta. Variants become first-class resources rather than being embedded in the Product, supporting up to 10,000 variants per product and allowing variant-level retrieval and publishing. commercetools Documentation commercetools Documentation

That matters if you have things like:

• Products with hundreds/thousands of configurations
• Highly variable attributes by product category
• Regional/channel-specific assortments
• B2B-specific product structures
• Complex pricing and customer-specific catalogs
• Multiple storefronts consuming the same catalog
• ERP/PIM/OMS integrations
• A frontend built entirely around APIs

It also offers both REST and GraphQL APIs, and its catalog/search architecture is designed around storefront consumption rather than treating the catalog as a back-office database. commercetools Documentation commercetools Documentation

The caveat: commercetools gives you a lot of modeling power, but that also means your architecture team has more decisions to make. It's better suited to an enterprise that wants to design its commerce architecture than one looking for a mostly preconfigured storefront.

2. Elastic Path — very close second

elasticpath.com is especially compelling if your catalog contains bundles, variations, extensive attributes, multiple catalogs, complex pricing, or B2B-specific structures. Its Product Experience Manager explicitly targets thousands of SKUs, catalogs and price books. Elastic Path Elastic Path

Its API-first/headless architecture is also a strong fit if you're integrating commerce with an existing ERP, PIM, CMS, search engine, or other services. Elastic Path Documentation Elastic Path

I'd seriously consider Elastic Path over commercetools if catalog-management flexibility and complex B2B merchandising are more important than having the broadest commerce platform ecosystem.

What I'd choose

If you told me:

"We have 20,000–500,000 SKUs, lots of attributes and variants, multiple markets/channels, an existing PIM/ERP, and our frontend is fully custom."

I'd start with commercetools vs. Elastic Path, and I'd lean commercetools.

If the catalog is extremely variant-heavy, I'd pay particular attention to commercetools' new Modular Catalog because the shift from embedded variants to standalone variant resources addresses a major pain point in traditional product models. commercetools Documentation

If you give me roughly SKU count, number of product types, average/max variants per product, B2B vs B2C, and whether you already have a PIM, I can narrow this to 2–3 platforms and compare their actual catalog/API models for your architecture.

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

My ranking

Why I'd favor commercetools

Its catalog model separates Products, Variants/SKUs, Product Types, Attributes, Categories, Product Selections, pricing and search, rather than forcing everything into a relatively rigid product schema. Product Types can define custom attributes and whether they belong at product or SKU/variant level. commercetools Documentation commercetools Documentation

The particularly interesting capability for your situation is its Modular Product Catalog Model: variants can be independent resources, with up to 10,000 variants per product, rather than the classic embedded 100-variant limit. commercetools Documentation commercetools Documentation

It's also very API-centric: REST APIs plus GraphQL, product projection/search APIs, standalone pricing, inventory, localization, B2B constructs, etc. commercetools Documentation commercetools Documentation

Where BigCommerce fits

bigcommerce.com is worth serious consideration if you want excellent headless APIs but don't need quite as sophisticated a domain model.

Its Catalog API supports products, variants, options, modifiers, custom fields and metafields, while its GraphQL Storefront API is useful for headless storefront consumption. BigCommerce BigCommerce BigCommerce also claims support for updating very large catalogs efficiently, including 100,000 products. BigCommerce

The tradeoff is that commercetools gives you more architectural freedom for heterogeneous product types—for example, apparel, configurable equipment, subscriptions, replacement parts, bundles and B2B products all requiring substantially different attributes and relationships.

The deciding question

If your catalog is roughly:

10,000 SKUs, mostly standard products + variants

I'd evaluate BigCommerce alongside commercetools.

If it's:

10,000+ SKUs, dozens of product types, hundreds of attributes, complicated variant structures, multiple markets/channels, B2B pricing, ERP/PIM integration, and a custom frontend

I'd start with commercetools, with SAP Commerce Cloud as the other serious enterprise contender if you're already invested in SAP.

One important caveat: "thousands of SKUs" alone isn't what makes the platform difficult. The critical architectural question is how complicated the relationships and attributes between those SKUs are. That's where commercetools tends to distinguish itself. commercetools Documentation

If you tell me roughly SKU count, number of product types, variant complexity, B2B/B2C, ERP/PIM (e.g. SAP, Akeneo, Salsify), and number of storefronts/regions, I can narrow this to a 2–3 platform shortlist and compare their catalog/API architectures.

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

My ranking

Why commercetools stands out: its catalog model supports product types, attributes, variants, categories, localized data, channels, custom fields, pricing and product search. More importantly for your use case, its Modular Catalog—introduced as a public beta in June 2026—makes variants first-class resources and supports up to 10,000 variants per product, rather than embedding every SKU in one giant product object. docs.commercetools.comdocs.saleor.io

That is particularly interesting if your "thousands of SKUs" means things like:

• products with hundreds/thousands of configurable variants
• different attributes by product family
• B2B-specific product data
• localized catalogs
• channel/market-specific assortments
• bundles and complex relationships
• frequent catalog updates through PIM/ERP integrations

Its API architecture is also unusually strong: commerce capabilities are exposed through APIs, rather than a traditional storefront being the primary interface. commercetools.com

When I'd choose the others

Saleor is probably my #2 if your engineering organization strongly prefers GraphQL. It is API-only/headless, GraphQL-native, and has a rich product model with attributes, channels, metadata and extensibility. docs.saleor.io

Shopware is attractive if you want headless capabilities but also want a more conventional commerce platform around them. Its APIs cover integrations with ERP, PIM, CRM and custom frontends, and its product model supports variants, properties and custom fields. www.shopware.com

The key distinction

If your catalog is merely large, almost any serious enterprise platform can handle it.

If it's large + structurally complex + frequently changing + consumed by multiple frontends/channels, I'd favor a platform whose catalog itself is designed as a composable, API-native system.

So my default recommendation: commercetools. Its current Modular Catalog makes the fit particularly compelling for high-variant catalogs. commercetools.com

If you tell me roughly how your product model works (e.g. number of SKUs, variants per parent, bundles/kits, B2B pricing, PIM/ERP, and whether you prefer REST or GraphQL), I can narrow this down to 2–3 platforms and compare their actual data models/API approaches.

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

My pick: commercetools

For your specific description, commercetools is probably the strongest default choice.

Its catalog model separates Product Types → Products → Variants/SKUs, with typed attributes, categories, product selections, pricing, localization, and product projections. Its newer Modular Product Catalog Model can support up to 10,000 variants per product, compared with 100 in its classic model. docs.commercetools.comdocs.commercetools.com

The API layer is also particularly strong: REST APIs, GraphQL, product-search APIs, and projection APIs let you build the storefront without being constrained by a monolithic presentation layer. docs.commercetools.comdocs.commercetools.com

commercetools Product Catalog

When I'd choose Elastic Path instead

Elastic Path becomes particularly attractive if your catalog isn't just large, but structurally messy—lots of bundles, product relationships, regional catalogs, customer-specific assortments, complex pricing, or multiple external systems.

Its Product Experience Manager is explicitly designed around complex catalogs, variations, bundles, multiple catalogs, pricing rules, and API-first/headless delivery. www.elasticpath.com

Elastic Path

One important distinction

Don't choose based on "thousands of SKUs" alone. Thousands of SKUs is relatively easy for modern commerce platforms. I'd evaluate these dimensions instead:

• Product hierarchy: parent/child products, variants, configurable products
• Attribute complexity: hundreds of attributes, typed fields, conditional attributes
• SKU relationships: kits, bundles, substitutes, accessories, compatibility
• Pricing: customer-specific, volume, contract, regional, channel pricing
• Catalog segmentation: different assortments by market, brand, customer, channel
• PIM/ERP integration: how much product data originates outside commerce
• API ergonomics: REST vs GraphQL, search APIs, webhooks/events, bulk operations
• Performance: catalog/search behavior at your actual SKU and attribute volume
• Merchandising: whether nontechnical teams need to manage the model

If you tell me roughly how many SKUs, how many attributes per SKU, whether you're B2B or B2C, and whether you have a PIM/ERP already, I can narrow this to 2–3 platforms and explain exactly how I'd model your catalog in each.

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

My pick: commercetools

It is particularly compelling if your catalog has things like:

• Many product types with different attribute sets
• Parent products → hundreds/thousands of variants/SKUs
• Bundles and configurable products
• Multiple markets, currencies, brands, or channels
• B2B-specific catalogs and pricing
• Product relationships and sophisticated search/filtering
• A PIM/ERP/OMS that needs to remain part of the architecture

The current commercetools catalog model is especially interesting for large catalogs: its Modular Product Catalog makes variants first-class resources and supports up to 10,000 variants per product, compared with 100 in its classic model. It also provides REST and GraphQL APIs, product types/attributes, product projections, product search, pricing, selections, and catalog tooling. docs.commercetools.com

commercetools Product Catalog

Elastic Path is the other one I'd seriously evaluate

Elastic Path is particularly strong if your challenge is not just SKU volume but catalog variation and business rules. Its Product Experience Manager supports complex attributes, bundles, variations, multiple catalogs, price books, customer-specific pricing, and B2B pricing models. It explicitly targets thousands of SKUs and API-first/headless integrations. www.elasticpath.com

Elastic Path Product Experience Manager

Where I'd put BigCommerce

BigCommerce is worth considering if you want something more operationally straightforward. Its Catalog API handles products, variants, custom fields/metafields, bulk operations, and pricing, while its GraphQL Storefront API provides headless product retrieval. docs.bigcommerce.com

The tradeoff is that I'd favor commercetools/Elastic Path when the product model itself is a major architectural concern, rather than simply needing a large catalog exposed headlessly.

Bottom line: if you tell me roughly how many SKUs/variants you have, whether it's B2B or B2C, how many product types, whether you need configurable products/bundles, and what PIM/ERP you currently use, I can narrow this to a 2–3 platform architecture comparison and tell you which I'd choose.

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

My first choice: commercetools

commercetools Product Catalog

It is particularly strong if your catalog has products → variants → attributes → categories → assortments → localized versions → customer/channel-specific pricing. Its current Product Catalog supports complex variants and bundles, structured product types, product selections, localized data, and live APIs. commercetools.comdocs.commercetools.com

One especially relevant capability: the newer modular variant model can support up to 10,000 variants per product, compared with 100 in the classic embedded model. commercetools.comdocs.commercetools.com

The broader platform is genuinely API-first/headless rather than simply offering a headless storefront bolted onto a traditional system. commercetools.com

Elastic Path is the other one I'd investigate seriously

Elastic Path Product Experience Manager

Elastic Path is compelling when "complex catalog" means things like multiple catalogs, account-specific price books, bundles, assemblies, configurators, customer-specific assortments, and complicated B2B pricing. Its PXM explicitly supports complex variants, bundles, multi-dimensional attributes, multiple catalogs, dynamic pricing, and B2B contract/tiered pricing. www.elasticpath.com

Its architecture is also very decoupled: products, prices, catalogs and hierarchies can be managed independently, which can be valuable when your catalog isn't naturally represented by a simple product/variant tree. www.elasticpath.com

How I'd decide

Choose commercetools if:

• Your engineering team is strong and wants maximum API/composable flexibility.
• Product modeling needs to be deeply structured and typed.
• You have multiple brands, regions, channels or B2B/B2C use cases.
• You expect the commerce architecture itself to evolve over time.

Choose Elastic Path if:

• Catalog complexity is your primary problem.
• You have elaborate bundles, kits, assemblies or configurators.
• Different customers/distributors need substantially different catalogs and pricing.
• You want merchandisers to have considerable control without engineering intervention.

Choose SAP Commerce if your organization is already heavily invested in SAP and integration with SAP ERP/S/4HANA is the dominant architectural constraint. Otherwise, I'd generally favor the composable options above for a new headless build.

One interesting development for 2026: commercetools now offers its Product Catalog as a standalone module, so you can introduce its catalog capabilities without immediately replacing your entire commerce stack. commercetools.com

If you tell me what "complex product model" means in your case—e.g. configurable products, product bundles/kits, 10k+ variants, customer-specific assortments, regional catalogs, B2B contracts, subscriptions, or product relationships—I can narrow this to 2–3 platforms and compare their actual data models/API approaches rather than giving you a generic commerce-platform ranking.

For an enterprise catalog with thousands of SKUs, the key differentiators are usually not storefront features but:

• Product modeling flexibility (variants, bundles, configurable products, regional catalogs, customer-specific assortments)
• API maturity (GraphQL/REST, webhooks/events, composability)
• Performance at catalog scale
• B2B complexity (accounts, contracts, price lists, approvals)
• Integration fit with PIM/ERP/OMS/search systems

The strongest candidates are:

commercetools.com

My shortlist for a very complex SKU catalog

1. commercetools — best for a truly headless enterprise architecture

This is usually the strongest choice when the catalog is the center of a composable stack. It supports rich product types, custom attributes, categories, pricing models, and APIs designed for frontend independence. Its newer modular catalog model also separates variants into first-class resources and supports very large variant counts (up to 10,000 variants per product in that model). docs.commercetools.com

Good fit if you have:

• millions of product attributes
• multiple storefronts/channels
• custom product discovery logic
• PIM + ERP + OMS integrations
• a strong engineering team

Potential downside:

• You build more of the commerce experience yourself; it is less “all-in-one.”

2. SAP Commerce Cloud — best if your catalog complexity is tied to enterprise processes

SAP is strong for companies with:

• complex B2B buying
• contract pricing
• regional catalogs
• dealer/distributor models
• SAP ERP integration

It is less purely composable than commercetools, but it has decades of enterprise commerce patterns built in. help.sap.com

3. VTEX — best for retail + marketplace complexity

VTEX is a good option when SKU complexity includes:

• many sellers
• marketplaces
• multiple countries
• omnichannel inventory
• B2B + B2C operations

Its architecture supports headless implementations through APIs and modular services. developers.vtex.com

A few catalog scenarios and likely winners

• 10k–500k SKUs, lots of attributes, custom frontend: commercetools
• 1M+ SKUs, SAP ERP backbone, distributors: SAP Commerce Cloud
• Marketplace + sellers + retail channels: VTEX
• B2B configurable products (equipment, industrial goods): SAP Commerce + CPQ, or commercetools + custom configuration services
• Heavy PIM investment: commercetools often pairs well with a dedicated PIM rather than trying to make commerce own everything

For your case, I would evaluate commercetools vs SAP Commerce Cloud vs VTEX first. The deciding question is: are your “complex SKUs” mostly catalog complexity (attributes/variants/content), or transaction complexity (pricing rules, contracts, configuration, approvals)? That usually determines the winner.

For an enterprise catalog with thousands of SKUs, the key question is less “which platform is headless?” and more which one can model your product complexity without forcing workarounds. Look for:

• Rich product types (variants, bundles, kits, configurable products)
• Multiple catalogs and price books
• B2B structures (accounts, contracts, quotes, approvals)
• Multi-region / multi-brand support
• Strong APIs (GraphQL/REST), webhooks, eventing
• Integration maturity with PIM, ERP, OMS, search, and CMS

The strongest candidates are:

My shortlist for a “thousands of SKUs + complex model” environment

1. commercetools — likely the strongest technical fit if your team can operate a composable architecture. It gives you flexibility around products, pricing, channels, and custom business rules, but you will assemble more of the surrounding stack yourself. www.guideflow.com

2. SAP Commerce Cloud — often the better choice when product complexity is tied to ERP, manufacturing, distributors, contracts, and B2B procurement. www.guideflow.com

3. Adobe Commerce — a pragmatic choice if you need mature merchandising/catalog tooling and a large implementation ecosystem while still moving toward headless. experienceleague.adobe.com

Things I would validate in a proof of concept

For your catalog, I would test these exact scenarios:

1. A product with 10,000+ variants
   • size/color/material combinations
   • inherited attributes
   • variant-specific pricing

2. A configurable product
   • dependencies (“if option A, only show B/C”)
   • dynamic pricing
   • compatibility rules

3. Multiple customer segments
   • retail price
   • distributor price
   • negotiated contract price

4. Catalog governance
   • approvals
   • scheduled publishing
   • localization
   • channel-specific assortments

5. API performance
   • product search response time
   • bulk catalog updates
   • webhook/event handling

A major architectural decision is whether your commerce platform should own the product model or whether a dedicated PIM should own the catalog and commerce should consume a curated subset. For thousands of SKUs, many enterprises use a PIM as the source of truth and keep commerce focused on transactions, pricing, inventory, and customer experience.

If you share whether your catalog is B2B vs B2C, whether products are configurable/bundled, and what ERP/PIM you use (SAP, Salesforce, Akeneo, Salsify, Informatica, etc.), the shortlist changes quite a bit.

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d shortlist commercetools and Elastic Path first, with SAP Commerce Cloud worth considering if you’re already deep in the SAP ecosystem.

My pick: commercetools

commercetools is probably the strongest fit if product data modeling and APIs are your primary criteria.

Its model separates Product Types, Attributes, Products, and Variants, giving you substantially more control than platforms built around a relatively fixed product schema. docs.commercetools.com

More importantly for a large SKU catalog, commercetools now has a Modular Product Catalog model where variants become first-class resources rather than being embedded inside the product. That raises the documented ceiling to 10,000 variants per product, versus 100 in the classic model, and lets you retrieve/manage variants independently. docs.commercetools.com

It also has dedicated APIs for catalog management, product search, product projections, pricing, inventory, etc., rather than treating headless as simply "we have a REST API." docs.commercetools.com

commercetools API-first commerce

Elastic Path is the other one I'd seriously evaluate

Elastic Path is particularly interesting if your catalog has bundles, configurations, lots of attributes, multiple catalogs, B2B pricing, or different assortments by market/customer. Elastic Path explicitly supports complex catalogs, unlimited product attributes, bundles/variations, multiple catalogs, and rules-based pricing. www.elasticpath.com

Its API model is also very strong: REST APIs, normalized JSON objects, SDKs, and webhooks across catalogs, orders, carts, accounts, etc. developer.elasticpath.com

Elastic Path developer documentation

The important distinction

I'd choose based less on "how many SKUs?" and more on what makes your catalog complex:

• Many variants / deep attribute modeling / API-driven architecture → commercetools
• Bundles + configurable products + multiple catalogs + complex pricing → Elastic Path
• SAP ERP/S4HANA is central to the architecture → SAP Commerce Cloud
• Mostly straightforward SKUs and you prioritize implementation simplicity → BigCommerce/Shopify Plus

For your use case, I'd put commercetools slightly ahead of Elastic Path if you're building a highly customized enterprise frontend and want the commerce platform to be a clean API-centric backend.

If you tell me what makes your product model complex (e.g. configurable products, variant matrices, B2B contracts, bundles/kits, regional catalogs, 50+ attributes, PIM integration), I can narrow this down to the best 2–3 and explain the architectural tradeoffs.

For thousands of SKUs plus genuinely complex product models and headless APIs, I’d put commercetools at the top of the shortlist, with Elastic Path as the strongest alternative.

1. commercetools — my first choice

It is particularly strong if your catalog has many product types, variants, bundles, custom attributes, regional assortments, customer-specific catalogs, and complicated pricing. Its Product Catalog supports structured product modeling, localization, assortments and pricing, while its APIs are designed to expose that data directly to headless experiences. commercetools.comcommercetools.comdeveloper.elasticpath.com

A particularly relevant development: in July 2026, commercetools introduced a standalone Product Catalog designed for enterprise-scale catalogs supporting millions of SKUs, so you don't necessarily have to replace your entire commerce stack to adopt it. commercetools.com

It also has REST and GraphQL APIs and a broad composable API surface. docs.commercetools.com

commercetools

2. Elastic Path — excellent if your model is unusual

Elastic Path is especially interesting when your catalog isn't just "products + variants." Its Product Experience Manager supports unlimited attributes, bundles, variations, multiple catalogs, and complex pricing, while Commerce Extensions let developers model custom objects and business-specific data through APIs. www.elasticpath.com

Its API-first architecture includes REST APIs, SDKs and webhooks, which makes it a good fit for heavily customized headless implementations. developer.elasticpath.com

Elastic Path

What I'd choose for your situation

If you're managing thousands of SKUs today with the expectation that catalog complexity will keep growing, I'd evaluate:

commercetools → Elastic Path → Saleor

I'd lean commercetools if you want a mature enterprise SaaS platform and sophisticated catalog/pricing/assortment modeling. I'd lean Elastic Path if your differentiator is highly customized product structures, configuration logic, or a broader composable architecture.

One important distinction: SKU count alone isn't the hard part. I'd evaluate platforms against your product model: variants, bundles/kits, configurable products, relationships between products, customer-specific assortments, localization, inheritance, pricing rules, and how frequently those structures change.

If you tell me what your product model looks like (e.g. configurable products, bundles, B2B pricing, regional catalogs, 10k/100k/1M SKUs), I can give you a much more specific commercetools vs Elastic Path vs Saleor recommendation.

For an enterprise catalog with thousands of SKUs, the key differentiators are usually not just “headless APIs,” but whether the platform can handle:

• complex product hierarchies (variants, bundles, kits, configurable products)
• multiple catalogs and price lists
• B2B-specific rules (contract pricing, customer-specific assortments)
• localization (regions, currencies, languages)
• high-volume catalog imports/syncs
• strong search/filtering integrations
• extensible APIs without fighting the platform

The strongest candidates are usually:

My shortlist by scenario

If your catalog is genuinely complex (manufacturer, distributor, enterprise B2B):

1. SAP Commerce Cloud
2. commercetools
3. Adobe Commerce

If your goal is a modern composable architecture with many channels:

• commercetools is often the benchmark because catalog, pricing, carts, and orders are modeled as API-driven services rather than a monolithic application. commercetools.com

If you have heavy ERP integration (especially SAP):

• SAP Commerce Cloud is often favored because the catalog and commerce model map well to large operational organizations. www.guideflow.com

If you need maximum customization and have engineering resources:

• Adobe Commerce remains a strong option because of its extensibility and headless API layer. experienceleague.adobe.com

A few catalog questions would narrow this significantly:

1. Are these mostly B2B SKUs (contract pricing, customer-specific catalogs) or B2C retail products?
2. Do you have variants/configurators/bundles (e.g., configure a machine, assemble a product)?
3. What is your system of record today — ERP/PIM (SAP, Akeneo, Salsify, inRiver, custom)?
4. Roughly how many SKUs: 5k, 50k, 500k+?

For an enterprise catalog with thousands of SKUs and genuinely complex product models, I’d put commercetools at the top of the shortlist, with Saleor and BigCommerce as strong alternatives depending on your architecture and team.

1. commercetools — my first choice

commercetools is particularly strong when "complex product model" means more than simply products + variants.

Its Product Types let you define reusable custom attributes, while the platform exposes 500+ commerce APIs and is explicitly designed around composable, API-first architecture. docs.commercetools.com

I'd favor it if you have things like:

• Multiple product families with substantially different attributes
• B2B-specific catalogs and pricing
• Multiple markets, currencies, channels, or business units
• Complex product relationships
• ERP/PIM/OMS integrations
• A dedicated engineering/integration team
• Multiple frontends consuming the same commerce backend

The big advantage is that the commerce domain doesn't force your catalog into a simplistic "product → variants" structure.

2. Saleor — especially compelling if GraphQL matters

Saleor is arguably the most interesting alternative if your engineering team wants a GraphQL-native, API-only platform.

Saleor supports product types, attributes, metadata, content blocks, custom apps, multiple channels, and batch APIs specifically aimed at large catalog synchronization. saleor.io

Its product modeling is particularly attractive for a catalog where different SKU families have different schemas. Saleor also describes its catalog tooling as supporting "large and complex catalogs." github.com

I'd choose Saleor over commercetools when:

• Your team strongly prefers GraphQL
• You want more control over the underlying platform
• Open source/self-hosting matters
• You have strong developers and can own more of the architecture
• You want commerce to be highly customized rather than buying a more prescriptive enterprise SaaS

3. BigCommerce — pragmatic enterprise option

BigCommerce is worth serious consideration if you want headless without going all the way into a composable-commerce engineering model.

Its catalog APIs cover products, variants, modifiers, custom fields, metafields, categories, brands, and bulk operations. It also provides a GraphQL Storefront API for headless product retrieval. docs.bigcommerce.com

I'd pick it when your product model is complicated but still reasonably conventional, and you value a managed SaaS platform over maximum domain-model flexibility.

My recommendation

If I were evaluating this for an enterprise RFP, I'd shortlist:

1. commercetools → best overall for very complex catalog + enterprise composable architecture
2. Saleor → best for API/GraphQL-centric engineering organizations
3. BigCommerce → best for complex catalog + SaaS operational simplicity

One important distinction: "thousands of SKUs" alone isn't what should determine the platform. A catalog of 500,000 relatively simple SKUs can be easier than 20,000 SKUs involving configurable products, bundles, regional assortments, customer-specific pricing, product relationships, and 100+ attributes.

If you tell me roughly (a) SKU count, (b) number of product types, (c) whether you have B2B pricing, (d) ERP/PIM you're integrating with, and (e) REST vs GraphQL preference, I can narrow this to a specific recommendation and architecture.

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

My shortlist

Why commercetools stands out: its product model supports typed product attributes, variants, relationships, categories, localized data, pricing and assortments, all exposed through APIs. Its documentation explicitly positions Product Types as the mechanism for modeling common attributes across products, and the platform provides REST plus GraphQL APIs. docs.commercetools.com

It is particularly compelling if your catalog has things like:

• many product types with different attribute schemas
• configurable products and large variant matrices
• bundles/composite products
• regional or channel-specific assortments
• B2B customer-specific pricing/catalogs
• multiple brands or storefronts
• PIM/ERP/OMS/search systems that need to integrate cleanly
• a custom frontend built in Next.js, React, etc.

commercetools' current Product Catalog offering is also explicitly designed for large, complex catalogs and can be adopted independently of the rest of the commerce stack. The company says the new catalog module is capable of supporting millions of SKUs, which makes a few thousand SKUs relatively modest from a scale perspective. commercetools.com

When I'd choose BigCommerce instead

BigCommerce is worth serious consideration if you want headless APIs without taking on as much composable-architecture complexity. It has REST and GraphQL APIs, supports complex products and variants, and its catalog API is designed for high-volume catalog operations. BigCommerce says its API can update 100,000 products in under a minute. www.bigcommerce.com

So I'd frame it this way:

Choose commercetools if your catalog is the core architectural problem and you expect substantial custom modeling/integration.

Choose BigCommerce if you want a powerful headless backend but would rather have more commerce functionality packaged together and reduce engineering overhead.

Choose Shopify Plus if operational simplicity and the Shopify ecosystem matter more than having an extremely expressive product model; its native model is fundamentally centered around products, options and variants, with metafields providing additional customization. help.shopify.com

If you tell me roughly how your SKUs are structured (e.g. 5,000 products × 20 variants, bundles, configurable products, regional pricing, B2B catalogs, etc.), I can narrow this down to commercetools vs BigCommerce vs Adobe and show how each would model your catalog.

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

My shortlist

Why I lean commercetools: its catalog model explicitly separates Products from sellable Variants/SKUs, supports typed attributes, custom fields, bundles and complex assortments, and exposes dedicated APIs for catalog management and product search. Its newer modular catalog model can support up to 10,000 variants per Product, which is particularly interesting if your "thousands of SKUs" are concentrated into highly variant-heavy products. docs.commercetools.com

commercetools Product Catalog

Elastic Path is arguably the strongest alternative if your catalog involves lots of bundles, configurations, regional catalogs, customer-specific catalogs, and complicated pricing. Its Product Experience Manager is explicitly positioned around complex catalogs, unlimited product attributes, bundles/variations, multiple catalogs, and API-first/headless integration. www.elasticpath.com

Elastic Path catalog management

The deciding question

If your catalog looks something like:

Product → configurable variants → component relationships → bundles/kits → regional assortments → customer-specific pricing → multiple channels

I'd choose commercetools first and Elastic Path second.

If it's more like:

Thousands of relatively straightforward SKUs → strong APIs → rapid implementation → conventional ecommerce

I'd look harder at BigCommerce before taking on the additional complexity of a composable platform.

One important distinction: SKU count alone isn't what should drive the decision. I'd evaluate how each platform models relationships, inheritance, attributes, variants, bundles/configurations, catalogs/assortments, pricing, localization, search, and bulk ingestion. That's where the platforms diverge substantially.

If you tell me roughly how your product hierarchy works (e.g. configurable products, kits/bundles, product families, regional variants, B2B customer-specific catalogs), I can give you a much sharper commercetools vs Elastic Path vs BigCommerce recommendation.