For most enterprises under $200M GMV, Shopify Plus is the right default in 2026: lower TCO, faster implementation, and a B2B product that has caught up. Adobe Commerce fits complex B2B above that threshold but is losing live stores fast. commercetools suits $200M to $500M GMV with genuine complexity and an engineering team. Salesforce Commerce Cloud makes sense mainly if you already run three or more Salesforce clouds.
- A platform choice once made each decade now sits in an unusually turbulent market.
- Forced migrations, cooling composable hype, and a reshuffling of winners drove the change.
- Start with the default, then stress-test against your specific profile.
For most enterprises under $200M GMV, Shopify Plus is the right default in 2026: lower TCO, faster implementation, and a B2B product that has caught up meaningfully. Adobe Commerce fits complex B2B above that threshold but is losing live stores fast. commercetools is the right answer for enterprises above $200M to $500M GMV with genuine architectural complexity and an engineering team to run it. Salesforce Commerce Cloud makes sense primarily if you already have three or more Salesforce clouds. Start there, then stress-test against your specific profile.
Choosing an enterprise ecommerce platform is normally a decision a company makes once a decade and tries very hard not to think about in between. In 2026 that calm is gone. Three forces arrived together: a forced mass migration off a legacy platform, a cooling of the composable hype that drove the last cycle, and a real reshuffling of which platforms are winning and losing. They make 2026 the most consequential year for enterprise platform decisions in a long time, and a buying committee in 2026 makes the call under unusual pressure.
I advise enterprise commerce teams on exactly these decisions, and I have watched the same mistakes repeat: choosing on a feature checklist instead of fit, underestimating total cost by a wide margin, and treating a platform decision as a technology choice when it is a strategy and operating-model choice. The stakes are high enough that getting it wrong sets a brand back years, which I argued in the platform bottleneck piece.
The sections that follow cover why 2026 is different and which platforms deserve a shortlist spot, with who each fits. After that come what the composable promise delivered, the full cost picture, and how to make the call without getting captured by a vendor's pitch.
The terms a buying
committee throws
around.
Enterprise commerce is thick with architecture jargon, much of it used loosely to sell a particular approach. This is what the terms mean in plain language.
| Term | What it means |
|---|---|
Monolith | An all-in-one platform where storefront, cart, checkout, and admin come bundled. Simpler to run, harder to customize deeply. Adobe Commerce, classic SAP. |
Composable / MACH | Architecture assembled from best-of-breed pieces connected by APIs. More flexible, more complex and expensive to build and run. commercetools is the headline example. |
Headless | Separating the storefront a customer sees from the commerce engine behind it, so each can change independently. Often part of composable, not always. |
GMV | Gross merchandise value. The total sales running through a platform. The number that determines which tier of platform you actually need. |
TCO | Total cost of ownership. License plus hosting plus development plus integration plus the team to run it. Always far more than the license quote. |
Replatform | Migrating from one platform to another. Expensive, slow, and risky, which is why brands stay on platforms they have outgrown. |
SAP Hybris EOL | The end-of-maintenance deadline for SAP's on-premise commerce platform, July 31, 2026. The trigger forcing thousands of enterprises to move this year. |
Keep the GMV-to-architecture link in mind: the single most common enterprise mistake is buying a composable architecture the business is too small to justify, which the composable section covers.
The largest forced
migration in
commerce history.
The reason 2026 is unusual comes down to a single date. SAP Commerce on-premise, the platform most people still call Hybris, reaches mainstream end-of-maintenance on July 31, 2026. More than 3,200 enterprise organizations have to migrate off it by then, which is the single largest forced enterprise replatforming event the industry has ever seen (Elogic). Early migration patterns show roughly 40% moving to SAP's own Commerce Cloud, about 18% to commercetools, and around 15% to Adobe Commerce.
Even if you are not on Hybris, the deadline affects you in two ways. First, it floods the market with enterprise migrations all at once, which strains implementation partners and pulls vendor attention toward the biggest deals, so timing and partner availability are tighter in 2026 than usual. Second, it is forcing a wave of architecture decisions in compressed time, which is when buying committees make rushed, checklist-driven choices they regret. If you are migrating under this deadline, resist the pressure to decide fast.
The platforms worth
your shortlist, and
who they fit.
Five platforms belong on most enterprise shortlists in 2026, and the right answer depends far more on your fit than on any feature ranking. The table gives my read on each, caveats included.
| Platform | Best fit | The caveat |
|---|---|---|
Shopify Plus | Speed to market, lower operational overhead, unified B2B and DTC on one store. Share leader in B2C above $50M GMV. | Less suited to the most deeply bespoke, highly complex catalogs that need total architectural control. |
Adobe Commerce | Complex B2B, deep customization, large catalogs. Still the share leader in B2B above $50M GMV. | Live stores fell 15% year-over-year in early 2026. Heavy to run, opaque pricing, momentum against it. |
commercetools | Large enterprises that genuinely need composable flexibility and have the team to run it. The MACH leader. | Real complexity and cost. Wrong choice below roughly $200M GMV, where the flexibility is not worth the overhead. |
Salesforce Commerce Cloud | Enterprises already deep in the Salesforce ecosystem, with three or more clouds and CRM-commerce unification as a priority. | A 2 to 3x cost premium that is hard to justify without that existing Salesforce footprint. |
SAP Commerce Cloud | Existing SAP Hybris shops staying in the SAP world, with SAP ERP at the core of operations. | Mostly a continuity choice. Worth pressure-testing against alternatives rather than defaulting to it. |
None of these is the answer for everyone. Buying committees that get this wrong start from "what is the best platform" and end up captured by whichever vendor ran the best demo. The ones that get it right start from "what is our profile" (GMV band, B2B versus B2C mix, catalog complexity, existing systems, and team capability) and let that narrow the field before a single demo. This is the same build-versus-buy-versus-partner discipline I laid out in the build, buy, partner piece.
Composable was
oversold to brands
too small for it.
The last platform cycle was dominated by the composable, or MACH, pitch: break apart the monolith, assemble best-of-breed pieces, gain total flexibility. For the right enterprise it is powerful; the problem is how far down-market it got sold. Composable architectures are now used by an estimated 34% of companies above $1 billion in GMV, up from 26% in 2024, but adoption falls off sharply below $200 million in GMV (Elogic). The cliff has a cause: below a certain scale, the flexibility of composable is not worth its complexity and cost.
I have watched mid-market brands buy composable architectures, spend two years and a fortune assembling and integrating the pieces, and end up with something slower to change than the monolith they left, because now every change touches five vendors instead of one.
Composable is a real answer for enterprises with the scale, the engineering team, and a clear need for architectural control, and a budget trap for the brand that bought the pitch without those prerequisites. The question to ask is whether you have the scale and the team to make composable pay off, and most brands under a few hundred million in GMV do not.
"Composable is a real answer for the enterprises that need it and a budget trap for the ones that bought the pitch without the scale or the team to use it. The architecture is not the strategy."
The license is the
small number.
Total cost of ownership is where enterprise platform decisions go wrong financially, because the license fee is a fraction of the real number once you add hosting, implementation, integration, customization, and the team to run it.
The platforms differ here by a lot. By Shopify's own analysis, its total cost of ownership runs about 33% lower than competitors on average and up to 36% lower at the high end, with Salesforce's overall TCO around 54% higher than Shopify's (Shopify Enterprise). Treat vendor-published comparisons like that as directional, since the vendor publishing them has an obvious interest. The broad pattern still holds up across independent analyses: operationally lighter platforms cost less to run over time.
Implementation speed is the other cost that hides on the timeline rather than the invoice. The same analyses put Shopify storefront launches roughly 28% faster than Salesforce, with some partners reporting 50% to 75% shorter implementation timelines versus Salesforce Commerce Cloud. For an enterprise, months of delay is real money in lost sales and carrying cost, so speed to launch belongs inside the TCO conversation. The platforms that are heavier to customize (Adobe Commerce especially) buy you control at the cost of a longer, more expensive build.
The market is
moving, and it
tells you something.
Platform momentum is a signal worth reading, because a platform losing customers is a platform whose ecosystem, talent pool, and roadmap investment are at risk. Adobe Commerce live stores fell about 15% year-over-year in early 2026, with over 1,700 stores leaving in a recent 90-day window, a meaningful share of them moving to Shopify and Salesforce (Elogic). The platform still powers an enormous base, an estimated $173 billion in annual GMV and a fifth of the top 1,000 US retailers, so the base is eroding rather than collapsing, and the direction is clear.
On the other side, commercetools crossed a $100 billion annualized GMV run-rate in early 2026, up from $75 billion months earlier, more than 60% year-over-year growth, with customers like Audi, Danone, Sephora, and Volkswagen Group. And Shopify Plus has moved decisively up-market, with Shopify B2B GMV growing 96% across 2025, which for the first time makes Plus a credible enterprise B2B platform as well as a DTC one, a shift I traced in what Shopify taught the enterprise. For a buyer, that means weighting momentum alongside fit, because you are betting on where a platform will be in five years as well as where it is today.
The questions that
narrow the field
before the demos.
I run this sequence with enterprise teams so the decision rests on fit instead of on whoever sells hardest. Answer the questions in order and the field narrows itself.
What is our GMV band? This alone eliminates most options. Below a few hundred million, composable is usually the wrong call and a strong monolith or Shopify Plus is the efficient answer. Above a billion with genuine complexity, composable earns its place.
B2B, B2C, or both? A unified B2B and DTC requirement now favors Shopify Plus in a way it did not two years ago, while the most complex B2B catalogs still pull toward Adobe Commerce.
What are we already locked into? A deep existing Salesforce or SAP footprint changes the math, because the integration value can justify a premium that would otherwise be indefensible.
What is our team actually capable of running? Composable demands real engineering capacity. If you do not have it and cannot hire it, a flexible architecture you cannot operate is worse than a simpler one you can.
How fast do we need to move? Under the Hybris deadline or any time pressure, speed to launch becomes a requirement, and the operationally lighter platforms win on it decisively.
The classic enterprise error is running the demos first and building the requirements around what impressed the committee, which means the vendor with the best demo team shapes the decision. Reverse the order: answer the fit questions above, narrow to two platforms on profile alone, and only then bring in demos to choose between finalists that both already fit. Brands that decide on a feature checklist and a slick demo end up on platforms that do not match their business, then live with the mismatch for a decade.
Choosing is half.
Migrating is the
hard half.
Everyone focuses on picking the platform, yet the migration is where the value is won or lost and where most of the pain lives. An enterprise replatform is a multi-quarter program with real risk: data migration, integration rebuilds, a period where the new system is not yet proven, and the organizational change of moving teams onto new tools. Even done well, it takes longer and costs more than the optimistic plan. The brands that survive it phased the work, ran old and new in parallel where they could, and refused to cut over everything at once under deadline pressure.
The Hybris deadline makes this harder, because a forced timeline tempts teams to rush the riskiest part. If the deadline cannot move and the migration cannot be done safely in time, a deliberate interim step is better than a rushed full cutover that fails in production. The board needs to see the replatform as a multi-year, high-stakes program instead of a procurement event, which is part of the conversation I laid out in the board conversation on commerce.
However loaded the 2026 decision gets, start from your own profile before the vendor's pitch. Know your GMV band, your B2B and B2C mix, your existing lock-ins, your team's real capability, and your timeline, and let those narrow the field before a demo ever runs.
Weight momentum alongside fit, judge cost on total ownership instead of the license quote, and treat the migration as the high-stakes program it is. If the shortlist lands on Shopify Plus, the next question is which of its capabilities you intend to use, which is a scoping problem rather than a licensing one. Choose for the business you run, whatever the vendor's slide says you should be, and you will not spend the next decade living with the wrong platform.
The questions
buying committees
ask most.
For most enterprises under $200M GMV, yes. Shopify Plus B2B GMV grew 96% across 2025, which is the clearest signal that the product has crossed from DTC-centric to enterprise-capable. The main limitation is highly bespoke catalog and checkout logic: if your B2B catalog requires custom pricing at thousands of account-specific tiers with complex approval workflows, Adobe Commerce or commercetools will handle that more cleanly. For everything else, Plus is faster to implement and cheaper to run than any serious alternative.
Plan for 9 to 18 months for a full replatform onto a modern platform, depending on integration complexity. The optimistic 6-month plans that vendors put in their sales decks rarely survive contact with legacy data migrations, ERP integrations, and the inevitable discovery that the old system had undocumented customizations. A phased approach, launching a new storefront while keeping back-office on the old system until it is stable, consistently reduces risk more than a big-bang cutover. If you are migrating under the Hybris deadline, this planning conversation needs to start no later than Q1 of your migration year.
License fees are the small number. Shopify Plus starts around $2,000 to $2,500 per month at the high end of volume pricing, but the real TCO including implementation, integrations, and ongoing development runs $500K to $2M+ for an enterprise launch. Adobe Commerce and commercetools licensing is negotiated and opaque, with enterprise contracts typically in the $200K to $800K per year range, then significant implementation costs on top. Salesforce Commerce Cloud adds a 2 to 3x premium on Shopify's TCO in most comparisons. Before evaluating any platform, build the full 3-year TCO instead of relying on the license quote.
At $200M GMV or above, with a dedicated in-house engineering team and a genuine architectural need that a monolith cannot serve. Below that, the flexibility of composable is rarely worth the complexity. Composable means assembling and integrating best-of-breed vendors for PIM, OMS, CMS, search, and checkout, each with their own contracts, APIs, and failure modes. That overhead makes sense for Danone or Volkswagen. It does not make sense for a $75M brand that wanted flexibility and ended up with a five-vendor integration project that takes months to change anything.
It depends on your B2B complexity and how much the existing customization would cost to rebuild. Adobe Commerce is strong for complex B2B, large catalogs, and heavily customized experiences. The concern is momentum: live stores fell 15% year-over-year in early 2026, which means the ecosystem, partner quality, and roadmap investment are under pressure. If you are on Adobe Commerce and it is working, the case for staying depends on whether your complexity would cost more to rebuild elsewhere than the platform's declining momentum costs you over the next five years. For mid-market or below, that math has shifted toward switching.
Making the platform call without getting captured by a vendor is exactly the kind of decision I work through with enterprise teams. It is part of the enterprise ecommerce consulting, and the form takes two minutes: start the conversation.
Facing a platform decision?
I advise enterprise commerce teams on exactly these calls, from the shortlist to the migration, without a vendor's thumb on the scale. If your organization is choosing or replatforming this year, the form takes two minutes.
Start a conversation Enterprise engagements →