ChatGPT answers, unedited

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.