8 Best Enterprise eCommerce Platforms for 2026

Key Takeaways

• Elastic Path Composable Commerce. Best for complex B2B and B2B2C enterprises that need customer-specific pricing, deep catalogs and subscriptions natively, without a commercetools-scale build.
• commercetools. Best for enterprises with a standing in-house engineering team that wants full best-of-breed control and will fund the integration work.
• Adobe Commerce. Best for B2C-led merchants with an existing Magento codebase and an agency partner already on retainer.
• Salesforce Commerce Cloud. Best for organizations already standardized on Salesforce CRM and Service Cloud, where data-model gravity outweighs commerce flexibility.
• SAP Commerce Cloud. Best for ERP-led manufacturers running SAP S/4HANA where commerce must sit downstream of the ERP.
• The disqualifier: if annual revenue is under roughly $50M and the commerce model is straightforward D2C, an enterprise platform is the wrong purchase. A mid-market SaaS platform will serve you better and cost a fraction of the total.

Introduction

Most enterprises do not start searching for a new ecommerce platform because their current platform suddenly broke. They start because it stopped keeping up.

The homegrown build begins consuming the roadmap, developers spend more time patching than shipping, and the cost of that complexity starts showing up in conversion rates, order volume, and speed to market.

At that point, the question is no longer whether the platform works, but whether it can support where the business is going next.

This comparison evaluates the leading enterprise eCommerce platforms based on architecture, native B2B capabilities, catalog and pricing complexity, ERP integration requirements, real cost to go live, and the types of organizations each platform is best, and worst, suited for.

Coming off a Homegrown Platform: What Breaks First

The most common migration path into enterprise commerce is not platform-to-platform. It is homegrown-to-platform, and it follows a predictable sequence.

The custom build works, often for years. Then three things compound:

1. Security patching and dependency drift start consuming sprint capacity.
2. The integrations to ERP, tax, and shipping become brittle because each was built once by someone who has since left.
3. And, the framework version falls far enough behind that upgrading is a project, not a task.

The tell is not an outage. It is a roadmap where the ratio has inverted: the team spends most of its capacity keeping the current system alive and a minority shipping anything a customer would notice. Ask your engineering lead what percentage of the last two quarters went to maintenance versus new capability. Above 60% maintenance, the build is now the constraint.

The trigger point is when that reaches the bottom line. It usually shows up as one of three things:

1. Checkout conversion drifting down quarter over quarter with no campaign explanation,
2. Order volume flat while sales headcount grows,
3. Or a channel the business has committed to publicly and cannot launch.

That third one is what actually forces the budget. See our breakdown of commerce architecture decisions for B2B sellers for how to sequence the rebuild.

How the Eight Platforms Compare at a Glance

Architecture is the first fork in this decision, and native B2B depth is the second. Everything else is negotiable. The table below is the short version. Pricing models matter more than pricing tiers here, because only one of these eight vendors publishes a real entry number.

1. Elastic Path Composable Commerce: Best for Complex B2B and B2B2C Enterprises

Elastic Path Composable Commerce is an API-first, headless commerce platform built for B2B complexity, designed to sit behind whatever storefront a team has already built in Next.js, React, Contentful, or Builder.io. Named customers include Pella Windows and Doors, Orgill, T-Mobile, Comcast, The Pokemon Company International, and Johnstone Supply.

The lead differentiator is that it handles complex B2B natively rather than as an add-on, which places it between two failure modes: Shopify's simplicity ceiling and BigCommerce's bolt-on B2B module on one side, commercetools' build-everything-yourself development cost on the other.

Key Features

Three capabilities decide most Elastic Path deals: how it separates products from pricing, how it lets you add business logic without forking code, and how it handles the integration bill that sinks composable projects.

Product Experience Manager

Product Experience Manager decouples products, pricing, and catalogs into separate objects. You get unlimited catalogs, product hierarchies, and price books without duplicating the underlying product data.

The practical version: a distributor running 50 catalog variations across regions, customer tiers, and contract accounts changes a product description once and it propagates to all 50. Where catalogs are effectively separate stores, that is 50 manual edits or a script somebody maintains. This is the merchandising problem "multi-store" features do not solve, because multi-store duplicates data rather than referencing it.

For a B2B buyer that structure maps onto three real requirements: pricing per customer segment, different assortments for distributors versus direct accounts, and regional pricing without a parallel catalog. Price books carry negotiated rates and volume-tiered discounts as first-class objects. Configurable products use product relationships rather than SKU explosion, which matters when the catalog is built from options rather than finished goods. Bulk changes go through PXM product import.

Commerce Extensions

Commerce Extensions works in two modes, and the distinction matters.

Extend a native resource. Add structured attributes and metadata to products, prices, hierarchies, orders, or accounts without altering the underlying platform logic. Example: attach a warranty expiry date and registered owner directly to the standard Order object, so warranty data travels with every purchase instead of living in a spreadsheet or a bolt-on system.

Create an entirely new resource. Define a schema for a concept the platform never shipped, fully addressable through REST APIs. Example: a Machine Registry recording which machines each customer owns, which then powers replacement-part reordering against that customer's actual equipment.

The strategic point is where business logic ends up living.

Custom resources here are first-class platform objects inheriting the platform's security, APIs, and performance characteristics. No database migrations, no forked code, no deployment work, which is precisely what keeps upgrades safe.

The honest contrast is Adobe Commerce, where custom modules and third-party extensions can conflict with core updates, and Magento upgrades are consequently planned as projects with rollback windows. Elastic Path documents the pattern for B2B customization work.

Composer, the Integrated iPaaS

Composer is the no-code and low-code integration and orchestration layer, described by Elastic Path as a commerce-intelligent iPaaS. Three parts: an Integrations Hub of instant-on connectors where you add credentials and go, a visual builder with thousands of pre-built components for anything not in the hub, and a unified monitoring dashboard with proactive alerting on the integrations themselves.

That last part is the one buyers underrate. Composable projects rarely overrun on the commerce engine. They overrun on integration, then keep costing money because nobody owns integration health after launch. Every vendor's flexibility pitch has an unpriced integration bill behind it, and the runtime, hosting, and monitoring is usually a separate line item or a separate vendor.

To be fair: commercetools, Spryker, and Adobe all integrate with anything, and mature iPaaS tools exist for each. The difference is that Composer's runtime is managed inside the same platform and contract rather than assembled and monitored separately.

See how Composer handles your ERP

Integration is the largest cost driver in an enterprise replatform. Watch Composer connect your ERP with prebuilt connectors, a managed runtime, and health monitoring on every integration.

See Composer in action

Pricing

Elastic Path is the only platform in this comparison that publishes an entry price. That is worth stating plainly, because six of the eight are quote-only.

All tiers include Search, Visual Builder and CMS, front-end hosting, Product Experience Manager, Promotions Builder, Composer, and Commerce Extensions. No per-user fees and no per-API metering. Subscriptions and Entitlements is a priced add-on at 0.5% of subscription revenue processed. Year one includes 40 expert services hours. Annual minimum term, better rates on multi-year. Full detail on the Elastic Path pricing page.

The license is not the number that decides your budget. See below.

What We Found Pricing All Eight Platforms

We priced all eight platforms against published vendor pages and third-party procurement data in August 2026. Two findings are worth publishing.

Elastic Path lists $49,500. Shopify Plus and BigCommerce publish floors. The other five publish packaging without a number: Adobe lists three deployment packages behind a "Get pricing" form, commercetools three editions, Salesforce two B2B editions marked "Contact for Pricing," SAP two editions at "price upon request," and Spryker no pricing page at all. Pricing keys off GMV, order volume, or negotiated tiers. SAP sells in blocks of 50,000 orders per year, and Salesforce confirms only that it takes a percentage of GMV based on functionality needed. Third-party estimates put Adobe Commerce on Cloud licenses between roughly $40,000/yr at entry and $190,000+/yr above $25M GMV, and commercetools between roughly $40,000/yr and $300,000/yr. Those same estimates put the Salesforce GMV share at roughly 1% to 3% for B2C and 1% to 2% for B2B.

The license is the minority of the spend. Across 2026 replatforming cost analyses, the license accounts for only 20% to 40% of total replatform spend. Implementation, ERP integration, and data migration make up the rest, and integration complexity is consistently named the single largest cost driver. Reported ranges: mid-market replatforms at $150,000 to $300,000 over 5 to 10 months, enterprise or fully composable rebuilds from $500,000 upward, typically 6 to 12 months when multiple ERP integrations and multi-region deployment are in scope.

Practical use: multiply any license quote by 2.5 to 5 for a first-pass total cost to go live. If a vendor's answer to "what does implementation cost" spans wider than 3x, that is the number to negotiate, not the license.

Where Elastic Path Shines

• Native B2B complexity. Account hierarchies with scoped browsing and access control, unlimited price books for negotiated and volume-tiered rates, quoting with expiration logic and version history, and sales rep tooling including buy-on-behalf-of, invoice tracking, and bulk ordering. Platform objects, not a module bolted to a B2C core.
• Subscriptions and entitlements in the core. Physical subscription boxes, memberships, digital content entitlements, tiered access control, proration, and automated churn handling with payment retry. Most platforms here route this to a third-party app.
• Flexibility without a from-scratch build. Commerce Extensions and Composer deliver composable freedom with materially less development burden than a best-of-breed assembly, which is the core tradeoff against commercetools.
• Reliability at scale. Elastic Path publishes average API response times at or under 30ms, 95th percentile at or under 100ms, 10x capacity autoscaled in under five minutes, and zero breaking API changes.

Where Elastic Path Falls Short

• Wrong fit for straightforward D2C, at any revenue. The value is concentrated in complexity: multi-segment pricing, deep catalogs, account hierarchies, subscriptions. A single-catalog, single-price-list D2C business pays for architecture it never uses and should buy Shopify Plus or BigCommerce. Elastic Path publishes a $49,500 entry tier, so the honest disqualifier is complexity, not company size.
• No native POS. Retailers running physical stores on an existing POS stack will find a gap. That reflects a deliberate focus on digital B2B and B2B2C rather than omnichannel vretail, and it is a real constraint if store-and-online inventory unification is a requirement.
• Smaller review base than the incumbents. 27 G2 reviews against Adobe Commerce's 557 and SAP Commerce Cloud's 297. Fewer public data points, and fewer peers in your industry to reference-call.

Customer Reviews

On PeerSpot, Elastic Path holds 4.5 out of 5. Jorge Gil, a team lead at Nulogic, rated stability and scalability 9 out of 10 each and wrote that "the solution provided a flexible infrastructure with ease of use," calling technical support "excellent." The same review notes it "might not be suitable for minimum use cases," which matches the complexity threshold above. On G2 it averages 4.2 out of 5 across 27 reviews.

Lindsay Althouse, Director of Business Systems at Johnstone Supply, on the post-launch position: "The journey doesn't stop here. With Elastic Path, we can continue iterating, testing, and improving, without needing to replatform every few years."

Who Elastic Path Is Best For

• B2B and B2B2C enterprises: distributors, manufacturers and wholesalers selling through multiple channels. See B2B eCommerce solutions.
• Businesses coming off a homegrown platform: the most common migration path into this category.
• Multi-segment sellers: different pricing and assortments per customer type across direct, trade, and registered professionals. Relevant for distributor networks and multi-brand operations.
• Regulated and high-complexity catalogs: pharma, cannabis, configurable and related-product catalogs, and large SKU counts where options rather than finished goods define the assortment.
• Subscription and entitlement businesses: including multi-product SaaS catalogs across tiers and go-to-market motions.
• Multi-region sellers: per-market pricing, currency, and assortment via multi-geo support, or a blended model alongside D2C commerce.

Your B2B complexity, handled natively

Account hierarchies, contract pricing, quoting, and rep ordering are platform objects here, not a module bolted to a B2C core. Bring your hardest requirement to the demo.

Request a Demo

2. commercetools: Best for Engineering-Heavy Composable Builds

commercetools is the reference implementation of MACH architecture: microservices-based, API-first, cloud-native, headless. It has been named a Leader in the Gartner Magic Quadrant for Digital Commerce for six consecutive years as of the 2025 report. It is the platform of choice when an enterprise wants to own every layer of its commerce stack.

Key Features

API-First Composable Core

Every capability is a discrete, independently scalable API service, with nothing coupled to a storefront and no opinionated front end to work around. For an organization with the engineering capacity to run it, that is genuine architectural freedom: swap search, CMS, payment orchestration, or the promotions engine each on its own schedule, without a platform upgrade. The tradeoff is that "assemble it yourself" is not a figure of speech. Capabilities that ship as configuration elsewhere arrive here as a build.

Frontend and Composability Tooling

commercetools has invested in reducing its own onboarding cost with pre-built frontend scaffolding and a component marketplace, which shortens time to first storefront against a bare-API start. G2 reviewers cite onboarding and support as strengths. It lowers the starting cost of a composable build without changing the staffing required to operate one.

Pricing

Where commercetools Shines

• True architectural independence: no vendor-owned front end, no coupled modules, and a real ability to replace any single component without a platform migration.
• Analyst-validated position: six consecutive years as a Magic Quadrant Leader is the strongest third-party signal in this category.
• Scale headroom: the microservices model handles very high catalog and traffic volumes without the ceilings monolithic platforms hit.

Where commercetools Falls Short

B2B arrives as assembly, not architecture: account hierarchies, contract pricing, quoting, and approval workflows are built or integrated rather than configured. That is the central difference against Elastic Path and the reason our commercetools comparison exists.

API-call pricing is hard to forecast: metering on API volume means cost scales with architectural decisions your developers make, not just revenue. Chatty front ends get expensive.

Staffing is the real cost: the platform assumes a standing engineering team. Reported total deployments run from roughly $250,000 into the millions, and the engineering line never goes away.

Customer Reviews

commercetools averages 4.6 out of 5 on G2 from a small base of 16 reviews. Across G2, Capterra, Trustpilot, and Gartner Peer Insights combined it holds roughly 4.2 out of 5 across 179 reviews. Reviewers consistently praise support responsiveness and onboarding.

Who commercetools Is Best For

• Enterprises with a funded, permanent commerce engineering team, not a project-based SI engagement.
• Organizations whose differentiation is the commerce experience itself, where owning every layer is a strategic choice.
• High-volume B2C and marketplace operators where scale headroom outweighs time to launch. See the side-by-side breakdown if you are evaluating both.

3. Adobe Commerce: Best for Existing Magento Estates

Adobe Commerce, formerly Magento Commerce, is the most widely deployed platform in this comparison and the one with the deepest partner ecosystem. It runs as a PaaS on Adobe Commerce Cloud or on-premise, with a headless option via API. Its real advantage is gravitational: the extension marketplace, the developer pool, and the agency bench are all larger than any competitor's.

Key Features

Extension Marketplace and Developer Supply

Thousands of commercial extensions cover most functional gaps, and the global Magento developer pool means you can staff a project almost anywhere. For a mid-complexity B2C merchant, the fastest route to a specific feature is often buying an extension rather than building. The cost of that convenience appears at upgrade time, below.

Adobe Experience Cloud Integration

If you already run Adobe Experience Manager, Analytics, or Target, Commerce shares identity, content, and audience data across the suite with far less integration work than a third-party stack requires. For an organization standardized on Adobe for content and marketing, that is the most defensible reason to choose it.

Pricing

Not published by the vendor. Reported total cost of ownership commonly runs 2x to 3x the license once hosting, development, and extensions are included.

Where Adobe Commerce Shines

• Ecosystem depth: the largest extension marketplace and developer pool in enterprise commerce, which lowers staffing risk and time to a specific feature.
• B2C merchandising maturity: decades of accumulated capability in promotions, catalog merchandising, and content-led commerce.
• Deployment flexibility: one of the few enterprise options still supporting on-premise, which matters for specific compliance and data-residency requirements.

Where Adobe Commerce Falls Short

• Upgrades are projects, not tasks: custom code and third-party extensions can conflict with core updates, and reviewers consistently cite upgrade planning, compatibility testing, and downtime risk. That is the structural cost of extending a monolith by modifying it. Our Magento comparison covers the migration path.
• B2B is a module on a B2C core: functional for wholesale price lists and basic account management, thinner where real B2B lives, in account hierarchies, contract pricing logic, and quote-to-order workflows.
• Total cost of ownership is the recurring complaint: the 2x to 3x license multiplier reflects hosting, performance tuning, extension licensing, and specialist developers.

Customer Reviews

Adobe Commerce averages 4.0 out of 5 across 557 G2 reviews, the largest review base here. Positive themes center on flexibility and ecosystem. Critical themes cluster tightly on cost of ownership, upgrade friction, third-party plugin conflicts, and a steep learning curve for administrators and developers.

Who Adobe Commerce Is Best For

• Merchants with an existing Magento codebase where the cost of leaving exceeds the cost of staying.
• B2C-led brands already standardized on Adobe Experience Cloud.
• Organizations with an agency on retainer who can absorb upgrade cycles as planned work.

4. Salesforce Commerce Cloud: Best for Salesforce-Standardized Organizations

Salesforce Commerce Cloud, formerly Demandware, is a SaaS commerce platform sold as part of the wider Salesforce estate, with separate B2C and B2B products. Organizations almost never choose it for the commerce feature set in isolation. They choose it because customer, service, and order data already live in Salesforce, and keeping them there costs less than federating them.

Key Features

Unified Customer Data Across the Salesforce Estate

Commerce, Service Cloud, and Sales Cloud share the customer record natively. For a service-intensive business, an agent seeing order history, entitlements, and cases in one console without a middleware layer is a real operational advantage and expensive to replicate elsewhere.

Einstein Personalization and Merchandising

Product recommendations, search ranking, and predictive sorting ship with the platform rather than as a separate search and personalization vendor. Reviewers cite personalization tooling as its clearest strength, particularly for high-traffic B2C storefronts.

Pricing

Note the structural implication: your platform cost rises with revenue whether or not your cost to serve does. Model it against a fixed or order-banded license before signing a multi-year term. Our Salesforce Commerce Cloud comparison works through that math.

Where Salesforce Commerce Cloud Shines

• Data-model gravity: if the CRM is the system of record, native commerce inside it removes an entire integration layer and the team maintaining it.
• Personalization out of the box: Einstein merchandising and search reduce the need for separate search, recommendation, and personalization vendors.
• Operational maturity: proven at very high traffic volumes with an established global SI ecosystem.

Where Salesforce Commerce Cloud Falls Short

• GMV-based pricing penalizes growth: a percentage of revenue means a successful year raises platform cost proportionally, independent of order complexity or infrastructure use.
• B2C and B2B are separate products: organizations running both often buy and integrate two platforms rather than configuring one, which undercuts the unification argument that justified the purchase.
• Customization is bounded by the SaaS model: deep logic changes route through cartridges and middleware rather than a native extension layer, and reviewers cite implementation complexity and cost as leading concerns.

Customer Reviews

Salesforce B2C Commerce carries 593 G2 reviews, the second largest base here. Reviewers credit personalization tooling and conversion impact. Critical reviews concentrate on price and implementation complexity, particularly for organizations without a dedicated Salesforce practice.

Who Salesforce Commerce Cloud Is Best For

• Organizations standardized on Salesforce CRM and Service Cloud with an internal Salesforce practice.
• Service-intensive B2C brands where agent-side order and case visibility drives retention.
• Enterprises with growth predictable enough to model GMV-based pricing over a multi-year term.

5. SAP Commerce Cloud: Best for ERP-Led SAP Manufacturers

SAP Commerce Cloud, built on the Hybris platform SAP acquired in 2013, is the enterprise commerce option for organizations where the ERP is the center of gravity. It carries the deepest native B2B feature set of any monolithic platform here, which is a genuine strength and the main reason it stays on shortlists.

Key Features

Native ERP and Product Master Alignment

For an organization running SAP S/4HANA, commerce inherits the ERP's product master, pricing conditions, inventory, and order management with far less transformation logic than a third-party platform requires. Where the ERP is the source of truth for price and availability, that shortens the integration project consuming most enterprise commerce budgets.

Mature B2B Commerce Model

Account structures, contract pricing, and complex order workflows are core architecture rather than a module, and 45.7% of its G2 reviews come from enterprise-segment users, the highest enterprise concentration of any platform here. For complex manufacturing and distribution, the functional coverage is real.

Pricing

Where SAP Commerce Cloud Shines

• Deepest native B2B of the monolithic platforms: account structures, contract pricing, and complex order workflows are architectural, not bolted on.
• ERP-native by design: the shortest path to commerce when SAP S/4HANA already owns product, price, and inventory master data.
• Proven at manufacturing complexity: the highest enterprise-segment review concentration here, and support quality is a consistently cited strength.

Where SAP Commerce Cloud Falls Short

• Complexity is the dominant review theme: reviewers repeatedly describe it as difficult to set up and maintain, requiring specialist expertise that is scarce and expensive to hire.
• Catalog and merchandising tooling shows its age: reviewers cite dated product catalog management and a less responsive admin interface, which lands hardest on merchandising teams making daily changes.
• Rigidity against changing requirements: users describe difficulty customizing and adapting the platform, the structural tradeoff of depth in a monolith. If you are evaluating because of the SAP Hybris end-of-life timeline, price migration effort rather than treating an upgrade as the default.

Customer Reviews

SAP Commerce Cloud averages 4.3 out of 5 across 297 G2 reviews. Positive reviews credit its handling of complex enterprise needs, support quality, and feature breadth, with roughly 30% reporting significant operational efficiency gains. Critical reviews cluster on complexity, total cost of ownership, catalog management, and interface responsiveness.

Who SAP Commerce Cloud Is Best For

• Manufacturers and distributors running SAP S/4HANA where commerce sits downstream of the ERP.
• Organizations with an in-house SAP practice or a funded long-term SAP SI relationship.
• Complex B2B sellers who value functional depth over speed of change.

Four More Platforms Worth a Shortlist Slot

6. BigCommerce Enterprise

BigCommerce Enterprise is a SaaS platform with open APIs and a headless option, positioned between mid-market SaaS and full enterprise. It rates 4.2 out of 5 across 568 G2 reviews, though 77.2% of those reviewers are small-business users, which is the clearest signal of where its center of gravity actually sits. B2B capability arrives as a module rather than core architecture, so account hierarchies and contract pricing work for moderate requirements and strain at real complexity. Best for D2C-led merchants outgrowing a mid-market platform who want SaaS operational simplicity and are not carrying deep B2B requirements. Our BigCommerce comparison covers where the module ceiling sits.

7. Shopify Plus

Shopify Plus is the strongest platform in this comparison for high-volume, low-complexity commerce, and it is genuinely excellent at that job. It rates 4.4 out of 5 across 812 G2 reviews, with 68.8% from small-business reviewers. Checkout conversion, operational simplicity, and app ecosystem breadth are real advantages, and B2B on Shopify has closed part of the wholesale gap. The ceiling is catalog and pricing architecture: multiple catalogs mean multiple stores, and complex customer-specific pricing pushes into apps or custom work. Best for D2C brands at scale where the model stays straightforward. Elastic Path also offers a Shopify integration for teams keeping Shopify as a storefront, and a direct comparison for those evaluating a move.

8. Spryker

Spryker is a composable, B2B-oriented platform with particular strength in marketplace and multi-vendor models, recognized by Gartner, Forrester, and IDC for sophisticated B2B and enterprise marketplace commerce. It rates 4.4 out of 5 across 139 G2 reviews, with 48% from mid-market. Reviewers cite fast implementation and modular flexibility, and note it is less approachable for non-technical users. Best for B2B marketplace operators and European-headquartered enterprises where Spryker's partner density is highest.

9. Oracle Commerce

Oracle Commerce appears on most enterprise shortlists through Oracle estate relationships rather than on commerce merit, and it recurs across competing comparisons in this category. It is worth a slot only if Oracle ERP and CX are already the standard and procurement favors consolidation. For a broader architectural view, see our guide to headless commerce platforms.

How to Choose an Enterprise eCommerce Platform

Most comparison pages stop at feature lists. The decision is actually six questions, and the last one is the gate. Work through them in order, because each constrains the next.

1. Catalog and Pricing Complexity

The question is not SKU count. It is how many versions of the truth the business maintains: catalogs per segment, per region, per contract. A 200,000-SKU catalog with one price list is simpler than a 5,000-SKU catalog with 40 contract price books.

The warning sign is a merchandising team manually replicating the same change across storefronts, or a spreadsheet reconciling what should be in each catalog. That is not a process problem and it does not resolve with training.

Score high here and you need catalogs, hierarchies, and price books as separate referenced objects rather than duplicated stores, which is what Product Experience Manager is built for.

2. Requirement Complexity

Distinguish light B2B from real B2B. Light B2B is a wholesale price list and a login. Real B2B is account hierarchies, contract pricing, approval workflows, quoting, purchase orders, and sales reps ordering on behalf of customers.

What matters at renewal is whether the platform delivers this as a module or as core architecture. Modules version separately from the core, so upgrade compatibility is a question you re-ask every cycle, and capability gaps get filled with custom code that constrains the next upgrade. Core architecture has no such seam. Elastic Path's B2B model is native, as is SAP Commerce Cloud's. Adobe Commerce and BigCommerce deliver it as a module.

3. Customization Depth and Logic

Every enterprise has rules the platform never anticipated: eligibility logic for a regulated product, a compatibility matrix, an entitlement that depends on equipment the customer already owns.

The only question worth asking is where those rules will live. Three answers: forked platform code, which makes every upgrade a regression-test project; middleware, which works but puts business logic outside the system of record; or a supported extension layer, where custom objects are first-class and upgrades stay safe.

Commerce Extensions is the third option. Ask every vendor on your shortlist where custom logic lives and what happens to it at the next platform upgrade.

4. Integration Burden and ERP Dependency

Count the systems: ERP, OMS, PIM, DAM, CDP, tax, shipping, payments, analytics. Then ask two questions vendors rarely get. How many are pre-built connectors versus custom builds, and who monitors them after go-live?

The second is the expensive one. Integration is consistently the largest cost driver in enterprise replatforms, and post-launch integration failures are usually discovered by customers rather than by monitoring. Composer bundles the connector library, build tooling, managed runtime, and health monitoring into the platform contract. If your shortlisted vendor does not, price the iPaaS and the team to run it as a separate line.

5. Subscriptions, Entitlements, and Recurring Revenue

This is the requirement most often discovered in month three of an implementation, and a frequent cause of re-scoping. Physical subscriptions, digital entitlements, usage-based billing, and tiered access rarely ship natively.

If any part of the model is recurring, ask specifically about proration on mid-cycle changes, dunning and payment retry, and entitlement-based access control. Those three are where third-party subscription apps break against a commerce platform's order model. Elastic Path includes subscriptions and entitlements natively, at 0.5% of subscription revenue.

6. In-House Engineering Capacity

This is the gate, and where enterprise replatforms actually fail. The common failure mode is not the wrong feature set. It is choosing full composable without a standing team to operate it, then discovering the SI contract ended and nobody owns the stack.

Score the first five criteria for complexity, then score engineering capacity separately. Capacity is not a complexity multiplier. It is a constraint that overrides the others.

The Enterprise Readiness Scorecard

Score each of the first five criteria from 1 (simple) to 5 (highly complex). Total is your complexity score, from 5 to 25.

Then score criterion 6 separately, 1 to 5: engineering capacity. 1 means no in-house developers and an agency on call. 3 means a small permanent team that also owns other systems. 5 means a dedicated, funded commerce engineering team with no end date.

Read the two scores together:

The cell that catches most enterprises is high complexity with capacity of 1 to 2. The instinct is to buy the most flexible platform available. The correct move is to buy flexibility that someone else operates: a managed extension layer and a bundled integration runtime, rather than a set of APIs and an SI statement of work. That is the segment Elastic Path is built for, and it is why our architecture documentation leads with managed rather than assembled.

Fix Complex B2B Commerce With Elastic Path

Be honest about the segmentation, because the wrong purchase here is expensive in both directions. If the model is straightforward D2C at volume, Shopify Plus or BigCommerce will serve you better and cost less in total. If you have a deep SAP or Salesforce estate and the ERP or CRM is genuinely the system of record, their native platforms remove an integration layer that is hard to justify rebuilding.

If you are running complex B2B or B2B2C, with multi-segment pricing, deep catalogs, or subscriptions, and you do not have a standing engineering team to operate a from-scratch composable build, that is the specific problem Elastic Path is built for. Native B2B, a supported extension layer, and a managed integration runtime, on published pricing.

Request a demo and bring your readiness scorecard. Or work through the eCommerce software comparison guide first if you are still building the shortlist.

Complex B2B commerce, without a from-scratch build

Native B2B, a supported extension layer, and a managed integration runtime. On published pricing, starting at $49,500 a year.

Request a Demo

FAQs

• What counts as an enterprise eCommerce platform?

  An enterprise eCommerce platform supports multiple catalogs, complex pricing models, deep ERP integration, and high transaction volume under a negotiated contract with an SLA. The practical dividing line is architectural: enterprise platforms expose their data model through APIs so it can be extended, rather than only configured.

• How much does an enterprise eCommerce platform cost?

  Licenses commonly run $40,000 to $300,000+ per year, but the license is only 20% to 40% of first-year spend. Mid-market replatforms total $150,000 to $300,000 over 5 to 10 months. Fully composable enterprise rebuilds start around $500,000. Integration is the largest single cost driver.

• How long does an enterprise replatform take?

  Three to six months for a mid-market migration with limited integrations. Six to twelve months when multiple ERP integrations, multi-region deployment, and complex B2B workflows are in scope. Data quality in the legacy system is the most common cause of overrun, not platform capability.

• Is composable commerce always better than SaaS?

  No. Composable is better when complexity is high and you have a permanent engineering team to operate it. Without that team, composable moves cost from a vendor contract to a payroll line you may not have approved. Score complexity and engineering capacity separately before deciding.

• Can one platform handle both B2B and B2C?

  Yes, if B2B is core architecture rather than a bolt-on module. The failure mode is platforms that ship B2B and B2C as separate products, which means buying and integrating two systems. Ask whether account hierarchies and contract pricing exist in the same data model as the D2C storefront.