A few observations after years of watching enterprise commerce projects succeed, fail, and occasionally surprise everyone involved.
I sometimes think our industry is too quick to assume the answer is another technology decision.
Spend enough time at conferences, partner events, or executive roundtables and you’ll hear the same conversations repeated in slightly different forms. Someone asks whether they should migrate to a new platform. Someone else is convinced AI is about to redefine commerce. A debate starts over composable architecture, headless, MACH, or whichever acronym has captured everyone’s attention this quarter. Eventually the conversation becomes technical enough that we forget why we were having it in the first place.
How do we make our business easier to buy from?
For all the innovation we’ve seen over the past decade, I don’t think we’ve become much better at answering that question.
That’s interesting because enterprise commerce technology has never been stronger. Whether you’re looking at Adobe Commerce, Shopify, Shopware, commercetools, or any number of other mature platforms, we’re no longer constrained by capability. These ecosystems are remarkably sophisticated. APIs are richer than they’ve ever been, integrations are easier to build than they were even a few years ago, and AI is beginning to unlock possibilities that felt futuristic not long ago. If better technology alone produced better outcomes, we’d expect commerce projects to be more successful today than at any other point in our industry.
Yet many executive teams walk away from major digital initiatives with a lingering sense that something didn’t fundamentally change. The website is faster. The design looks more modern. Customers compliment the experience. Internal teams celebrate launch day. Six months later, sales representatives are still entering orders that should have happened online, customer service is answering questions that customers should have been able to answer themselves, and leadership is wondering why the return on investment feels smaller than expected.
After seeing this play out enough times, I’ve become convinced the technology usually isn’t the problem.
We’ve simply become very good at solving the wrong one.
The Storefront Gets the Blame for Problems It Didn’t Create
One of the biggest misconceptions in enterprise commerce is that the storefront is where the customer experience begins. It isn’t.
Long before a buyer lands on your website, they’ve already formed expectations based on every previous interaction they’ve had with your company. They expect negotiated pricing to be accurate because it’s always been accurate when they called their account manager. They expect inventory to reflect reality because inaccurate inventory creates real operational problems. They expect to reorder products quickly because they’ve been doing business with you for years. None of those expectations are unreasonable. In fact, they’re remarkably practical.
When those expectations aren’t met digitally, it’s tempting to conclude that the website needs work. Sometimes that’s true. More often, though, the website is simply exposing friction that already existed somewhere else in the business.
Pricing isn’t wrong because the commerce platform failed. It’s wrong because pricing logic lives in multiple systems that were never designed to stay synchronized.
Customers can’t see inventory because warehouse data isn’t flowing where it needs to.
Complex quotes still require email because the quoting process was never designed with digital self-service in mind.
Invoices are difficult to retrieve because finance systems evolved independently from customer-facing systems.
The storefront becomes the visible symptom of much deeper operational decisions. Replacing it without addressing those underlying challenges is a bit like repainting a building whose foundation is beginning to crack. It looks better for a while, but eventually the same problems find their way back to the surface.
That’s why I think we’ve spent too much of the last decade talking about digital experiences when we should have been talking about operational experiences.
The Best Commerce Projects Rarely Start with Commerce
One pattern has become impossible to ignore over the past few years.
The projects that create the most meaningful business impact often don’t begin with a discussion about commerce at all.
They begin with questions that sound surprisingly operational.
Why does customer service answer thousands of calls about order status every month?
Why does it take three different systems to produce a customer-specific quote?
Why does sales spend valuable time processing repeat orders instead of growing strategic accounts?
Why can’t customers access the same information internally that our employees can?
Those conversations almost always lead somewhere more interesting than feature comparisons ever could. They reveal where manual work has quietly become accepted as “just the way we do things.” They expose dependencies between departments that nobody intentionally created. They uncover years of incremental decisions that made sense individually but collectively introduced friction into nearly every customer interaction.
The organizations making the biggest strides today aren’t necessarily buying more software. They’re removing unnecessary complexity. That’s a subtle distinction, but it’s an important one.
Complexity has a habit of disguising itself as sophistication. Enterprise businesses often assume complicated processes exist because their business is unique. Sometimes that’s true. More often, complexity is simply accumulated history. Every workaround, customization, acquisition, spreadsheet, and manual approval adds another layer until nobody remembers why the process exists in its current form.
Modernization shouldn’t begin by asking what technology to buy next.
It should begin by asking which complexity is still creating value and which complexity has simply become expensive.
AI Isn’t Changing the Question. It’s Exposing the Answer.
It’s impossible to write about commerce today without acknowledging AI. Every board meeting, strategy session, and vendor roadmap seems to include it, and for good reason. The opportunities are real.
What I find interesting, though, is that AI has a way of exposing organizational maturity faster than almost any technology we’ve seen before.
Everyone wants AI to generate insights, recommend products, automate workflows, or help customers find answers faster. Those ambitions are entirely reasonable. But AI depends on something many organizations have quietly neglected for years: trustworthy operational data.
An intelligent system is only as useful as the information it’s given. If pricing differs across systems, inventory isn’t reliable, customer records are inconsistent, or product information lacks structure, AI doesn’t solve those problems. It simply responds with greater confidence using imperfect information.
We’ve reached a point where conversations about AI are increasingly conversations about data governance, integration, and operational discipline. That may sound less exciting than autonomous agents or conversational commerce, but it’s where lasting competitive advantage is being built.
Organizations that invested early in connecting ERP, commerce, CRM, and operational systems are finding themselves well positioned for what’s coming next. Those who didn’t are discovering that AI has a remarkable ability to expose everything that wasn’t working in the first place.
Maybe We’ve Outgrown the Idea of “Digital Transformation”
I’ve started wondering if the phrase itself has become part of the problem.
Digital transformation implies there’s a finish line. Complete the project, launch the platform, celebrate success, move on. But that’s not how healthy businesses operate.
Commerce isn’t something you transform every seven years. It’s a capability you improve continuously. Customer expectations evolve. Internal processes change. Markets shift. New technologies emerge. Your business acquires another company. AI creates new possibilities. None of those things happen according to the timeline of a replatforming initiative.
The organizations that adapt most successfully aren’t treating modernization as an occasional investment. They’re treating adaptability itself as the investment.
That’s a different mindset entirely.
Instead of asking whether the current platform will last another five years, they’re asking whether their business can respond to change without rebuilding everything from scratch.
That’s ultimately what modern commerce should enable.
Not a prettier storefront. Not another launch announcement. A business that’s easier to evolve.
A Different Way Forward
When we meet with leadership teams, platform discussions are certainly part of the conversation. They matter. Technology decisions always matter.
But the most valuable conversations usually happen before anyone starts comparing platforms.
We ask where customers experience friction that employees have learned to ignore. We ask which manual processes consume the most valuable people in the organization. We ask what information customers still need to call someone to obtain. We ask what would happen if AI suddenly became reliable enough to participate in daily operations.
Interestingly, those questions rarely produce technology answers. They produce business answers. Once those become clear, technology decisions become significantly easier.
That’s why I don’t believe commerce modernization is broken.
In many ways, we’ve never had more capable platforms, better tools, or more exciting opportunities than we do today. I simply think we’ve spent too long assuming the storefront was the business, when in reality it’s only ever been a reflection of it.
The companies that stand out over the next decade won’t necessarily be the ones with the newest technology. They’ll be the ones that build organizations where operations, customer experience, and technology reinforce one another instead of competing for attention.
And in my experience, that’s a much more interesting problem to solve.