This blog recently made the case that every mature software category eventually commoditizes, and that commerce platforms made the turn when Shopify arrived. Read “The Great Commoditization” here. The macro pattern holds. What it leaves unanswered is a specific question worth taking seriously: why is Shopify winning enterprise deals right now, in 2026, against platforms that were supposed to own the enterprise segment forever?
Shopify was supposed to be a DTC platform, and that was the running joke from incumbents for a decade. Shopify couldn’t handle enterprise complexity. Shopify didn’t do real B2B. Shopify wasn’t built for merchants above $500M in GMV. Then Estee Lauder picked Shopify as its platform, and the argument didn’t just end, it reversed. Enterprise merchants are actively moving to Shopify now, not in spite of the complexity argument, but because of it. The shift didn’t happen on the Shopify roadmap. It happened in the CFO’s office.
CFOs Are in the Room Now
Ten years ago, commerce platform decisions were run by the CIO, validated by IT architecture review, and negotiated by procurement, with the CFO seeing a line item after everything was already signed. That era has ended. Enterprise software purchases route through the CFO by default now, and every major SaaS buy, every replatforming decision, and every integration budget over a few hundred thousand dollars gets CFO scrutiny on the way through.
Three forces combined to make that happen. The rate environment that started in 2022 ended a decade of near-free capital and forced every enterprise to treat software as an operating expense rather than a growth bet. Post-ZIRP budget discipline produced vendor consolidation mandates inside the vast majority of Fortune 1000 IT shops, most of them carrying explicit targets on dollars saved and vendor count reduced. And the “Rule of 40” discipline that public markets now apply to every SaaS vendor rolled downhill into how enterprise buyers evaluate the vendors themselves, because a software company that can’t run efficiently can’t deliver efficiently to its customers either.
The practical result is that FP&A sits in deal reviews that used to be IT-only, five-year TCO models are table stakes, and payback period has replaced feature differentiation as the first gate a vendor has to clear. CIOs who once reported through the COO or directly to the CEO now report through the CFO at a growing number of large enterprises, and CIO compensation increasingly ties to dollars removed from the IT run rate at least as much as to the technical merit of any particular architecture decision.
CFOs ask fundamentally different questions than CIOs asked. CIOs asked what the platform could do. CFOs ask what it costs to own over five years, how many people it takes to run, what happens at renewal, and whether the vendor can prove the ROI on a quarterly basis. The last four questions are the ones that kill complexity.
Enterprise Never Actually Wanted Complexity
Enterprise buyers never wanted complexity for its own sake, they tolerated it because the platforms that handled their requirements also happened to be complex, and the two got bundled into a single category called “enterprise-grade.” No enterprise procurement team ever wrote a requirement that said “please make this expensive and hard to implement.” They wrote requirements for reliability, for scale, for compliance, for uptime, and complexity came along for the ride because that was the only way those requirements got met for the better part of two decades.
Strip the bundling apart, and what enterprise buyers actually want is reliability at scale without the tax. They want fulfillment across regions, B2B workflows, multi-currency, complex tax handling, and uptime during Cyber Week. None of those requirements inherently demand a multi-million dollar Hybris implementation, none of them inherently demand a Demandware-style GMV take rate of one to three percent (which works out to $5M to $15M annually on a $500M GMV business for essentially the same functionality the business had at $50M), and none of them inherently demand a team of twenty offshore consultants on retainer just to keep the platform running.
The old enterprise commerce math looked something like this: Hybris or Salesforce Commerce Cloud license in the seven figures annually, SI implementation at three to five times the license cost, ongoing maintenance at 20 to 30 percent of license annually, and a full replatforming cycle every five to seven years because the stack drifts out of support. Total five-year TCO routinely landed in the tens of millions for a top-500 online retailer before anyone counted the opportunity cost of 18-month delivery cycles during which the roadmap sat in PowerPoint rather than production.
Shopify delivers the capabilities that mattered (B2B, multi-currency, international, headless, POS, Markets for cross-border, Shop Pay for checkout conversion) at a fraction of the cost, without the SI retainer, without the 18-month implementation, and without a take rate that scales penalty with success. Shopify’s Commerce Components launch, which lets enterprises adopt pieces of the stack headlessly rather than committing to a full replatform, closed one of the last real objections enterprise buyers had about lock-in.
CFOs Are Telling Heads of Commerce to Accept Fewer Features
The old buying conversation started with a features checklist, where enterprise evaluators walked through hundreds of line items, scored each platform on coverage, and picked the one with the deepest functionality. Heads of commerce wrote requirements documents that protected every edge case the business had ever handled, and vendors competed to check every box. That’s how Hybris, Salesforce Commerce Cloud, and Manhattan won deals for fifteen years, by offering feature parity with the incumbent plus a few new things on top.
That conversation is over, and CFOs are now pushing back on the requirements doc itself. The new question isn’t whether Shopify POS has every feature that Oracle Retail POS has, because Oracle Retail POS does have more features and every head of retail in the market knows it. The question is whether the business can live with what Shopify POS actually does, and whether the 10 to 20 percent of edge cases it doesn’t cover can be recreated through a separate app, a workaround, or a process change that costs dramatically less than the feature delta on the incumbent platform.
The reframing runs deep. Instead of “which platform handles all our requirements out of the box,” the question becomes “which 80 percent of our current requirements are actually load-bearing for the business, and can the other 20 percent be recreated cheaply enough that total cost still lands 70 percent below the incumbent.” Heads of commerce don’t love this conversation because they’ve spent careers protecting feature depth, but CFOs don’t care, the mandate is savings, and the mandate comes from the board.
The brands winning this trade-off are deliberate about what they give up. They map the features they’ll lose, they identify which ones actually matter, they build or buy cheap replacements for the ones that do, and they retire the workflows that don’t. The total package ends up delivering roughly 90 percent of the business value at 20 percent of the cost, and the 10 percent that’s genuinely lost turns out to have been legacy complexity that essentially nobody was using. It’s the software equivalent of a brand cleaning out the warehouse before moving to a smaller building, where the stuff that looked essential for 20 years turns out to be mostly boxes nobody had opened since 2012.
This is exactly the calculus that drove Estee Lauder, Mattel, and Allbirds onto Shopify. None of them got there by pretending Shopify matched Hybris feature for feature, they got there by deciding the feature delta wasn’t worth what they were paying for it. The CFO runs the math in ten seconds, and the deal closes.
What the CFO Test Actually Looks Like
CFO-approved software has four specific properties that show up on every finance review.
Is it simple? One platform beats five stitched together, and operations teams have to be able to run it without a standing integration budget or a war room every time something changes upstream.
Is it easier to live with? Maintenance can’t require a dedicated offshore team on retainer, API changes from upstream vendors can’t turn into quarterly SI projects, and self-service configuration has to be the default rather than a premium tier that costs extra.
Is it quicker to stand up? Time to value has to land inside the current fiscal year, ideally the current quarter, because the CFO’s payback model runs on calendar time rather than project time, and any implementation timeline longer than 12 months now requires board-level justification and a plausible story for why a simpler alternative doesn’t exist.
Does it cost dramatically less to own? It needs to land orders of magnitude lower rather than 10 or 20 percent lower, because the cost structure has to be fundamentally different rather than discounted. CFO approval on a new category buy increasingly requires showing a 60 to 80 percent TCO reduction versus the incumbent, not a modest efficiency gain that could evaporate at the next renewal.
Every one of those is a CFO test, meaning the questions the finance function asks before approving anything, with the answers landing in the five-year model rather than the sales pitch. Shopify clears all four at the commerce platform layer, which is exactly why enterprise is moving.
The Same Tests Are Hitting OMS
Order management systems are next in line, and the Sterling and Manhattan installs that once defined enterprise commerce ops are showing up on CFO review lists now, failing all four tests.
Sterling, which traces its lineage back to Yantra in the early 2000s and was later rebranded through WebSphere Commerce Order Management before landing in IBM’s portfolio, routinely runs $500K to multi-millions of dollars and takes 12 to 18 months to deploy. Manhattan Active Omni, the cloud-native rebuild of Manhattan’s legacy OMS, still requires a dedicated team of SIs on permanent retainer and clocks in at seven figures of annual cost once license, hosting, and ongoing customization are added up. Both systems depend on separate middleware products, separate connectivity tools, and separate reporting layers, and the total footprint for an enterprise running either one is typically five or six products stitched together through custom code, which the CFO sees on five or six separate contracts with five or six separate renewal cycles.
Middle-tier alternatives including Fabric and Fluent cleaned up the UX and decomposed the architecture into more modern pieces, but they kept the same fundamental structure underneath. Integration still lives in a separate layer, orchestration logic still sits on top of that, and customer implementations still run several hundred thousand dollars and several quarters. They carry the same cost structure wearing newer paint.
Pipe17 is the only platform in the OMS category that clears all four CFO tests.
Simple. Connectivity and order management live in a single platform rather than two products stitched through middleware, with selling channels, 3PLs, ERPs, marketplaces, and fulfillment providers all plugging into one place through 84 pre-built managed connectors. Pipe17 is the first and only order operations platform with both a native Model Context Protocol (MCP) server and full implementation of the Order Network eXchange (onX) standard, which together make order operations data instantly accessible to any AI client including Claude, ChatGPT, and Gemini, and position the platform for the coming wave of agentic commerce. Pippen, the AI assistant built exclusively for commerce ops, configures pre-built proven flows from a chat interface rather than generating net-new code that could hallucinate its way through a double shipment. Connecting Shopify to a new 3PL takes minutes rather than a custom integration project measured in months.
Easier. Connectors are pre-built and actively managed by Pipe17 rather than built once and abandoned, so when Shopify ships an API change (which happens constantly) Pipe17 absorbs it and the customer’s engineering team doesn’t staff for it. Ops teams configure routing rules, returns logic, exception handling, and inventory sync through self-service tooling rather than through a three-month SI engagement and a change control board. The typical Pipe17 customer runs enterprise-grade order operations with zero to one dedicated developer rather than a team of five to ten, which works out to a seven-figure annual difference in fully loaded headcount cost that shows up directly on the CFO’s model and compounds every year the customer owns the platform.
Quicker. Implementations run three months now instead of eighteen, because the long pole in any OMS project is connectivity and Pipe17 owns the long pole directly. What used to consume most of a project plan at Sterling or Manhattan collapses to weeks at Pipe17, since the connectors are already built and the integration patterns are already proven. Pippen accelerates the other side of the house, with ops teams running flows on day one because the interface is conversational rather than a 400-page admin manual. Payback periods come in under two quarters rather than two years, which matters because the CFO’s approval threshold for anything longer than a two-year payback has climbed dramatically in the current environment.
Lower TCO. A joint Pipe17 and Shopify TCO study run by RMW Commerce Consulting documented up to 85% reductions in total cost of ownership versus legacy OMS, where implementations routinely run $500K+ all-in once software, integration builds, integration maintenance, developer headcount, and manual exception handling are added up. One enterprise customer cut its annual order operations spend from $590K on its legacy stack to $150K on Pipe17, a roughly 75% reduction with no degradation in the operations the business was already running. Other customers back the pattern up: one operations leader called Pipe17 10x less expensive than Sterling, another saved millions by eliminating a dedicated offshore team that had been maintaining legacy integrations, Wyze cut outbound costs by 13% year over year, and Form Factory’s merchants consistently see full ROI in under six months. Pipe17 processed a 163% year-over-year increase in order volume in 2025 with the same unit economics, which means the platform absorbs growth that would otherwise drive incremental cost at legacy alternatives.
The CFO Already Voted on Shopify
Any enterprise that has already moved to Shopify has run the math and decided simpler, faster, and cheaper beat complex, slow, and expensive at the platform layer, and that decision cleared a CFO signoff somewhere along the way, with a five-year TCO model attached and a payback period inside two years.
The same math applies one layer down. The CFO who approved the Shopify move won’t sign off on a $500K Sterling renewal or a seven-figure Manhattan install to manage the orders flowing through Shopify, because that inconsistency doesn’t survive a finance review, and the finance review is the review that matters now. Procurement sees the Shopify Plus contract at a modest annual spend and then sees a legacy OMS contract at ten times that amount handling a subset of what Shopify is already doing upstream. The question practically asks itself: why does operating the orders cost more than running the platform they come from?
Enterprise stopped paying for complexity, Shopify was the first big commerce answer, and Pipe17 is the next one. Buyers already know how to vote, and the CFO already approved the ballot.
