For years, ecommerce technology has largely been a story of adding more.
More integrations, more specialist platforms, more custom development and more tools designed to solve individual problems. As digital commerce has evolved, businesses have invested heavily in building technology stacks capable of supporting increasingly sophisticated customer experiences and operational requirements.
But somewhere along the way, the technology itself has become a challenge for some retailers.
What happens when making a relatively straightforward change requires development support? When several systems need maintaining simply to keep the business running? Or when the cost of supporting an existing platform begins to compete with the budget available for improving the customer experience?
These are familiar challenges for many ecommerce teams, and they’re prompting a change in how businesses think about technology investment.
In a recent episode of The FODcast, I spoke with Anton Ekström, Co-Founder at Iggy Agency, about the hidden costs of commerce technology, the growing appeal of simpler platforms and why retailers may need to move away from technology-first thinking.
The conversation raised an interesting question: have we reached a point where the next phase of ecommerce innovation is as much about removing complexity as adding new capabilities?
When technology becomes a barrier to growth
Technology should help a business operate efficiently, respond to customers and pursue new commercial opportunities. Yet for some retailers, the systems originally introduced to support growth can eventually make those things harder.
Legacy platforms are a particularly obvious example.
A business may have invested heavily in a bespoke ecommerce environment several years ago, creating custom functionality and integrations around the way it operated at the time. That solution may have been entirely appropriate when it was first implemented.
But requirements change, platforms evolve and customer expectations move on.
Over time, even relatively small improvements can become expensive or time-consuming. The business may depend on specialist developers or external agencies to make changes that would be straightforward on a more modern platform.
There’s also the question of vendor lock-in. When important functionality relies on custom development or proprietary integrations, moving away from a particular supplier can become increasingly difficult.
The cost isn’t limited to maintenance fees or development hours. There’s also the commercial impact of being unable to respond quickly to opportunities.
For retailers, that makes the ability to change and adapt an important consideration when evaluating the long-term value of their technology.
Moving from tech first to commerce first
One of the central themes in our conversation with Anton was the idea of moving from a technology-first approach to what Iggy calls being “commerce first”.
It’s a useful distinction.
Historically, ecommerce projects have sometimes started with questions about architecture, functionality and what can be developed. Those questions remain important, but they don’t necessarily establish whether the proposed solution makes commercial sense.
A more commercially led approach starts by understanding what the business needs to achieve.
Will the technology support growth? Will it reduce operational costs? Can it help teams work more efficiently? Will it make the customer experience better, and is the expected benefit worth the investment?
These questions should help determine the technology, rather than being used to justify a decision that has already been made.
That doesn’t mean complex architecture or bespoke development should be avoided altogether. Some businesses have requirements that genuinely justify a more specialised approach.
The difference is having a clear reason for choosing it.
Is custom development always worth the cost?
There was a time when building something bespoke could feel like the natural answer to a business requirement that wasn’t immediately supported by an ecommerce platform.
And sometimes it still is.
However, the capabilities available within modern commerce platforms have expanded considerably. Functionality that once required significant custom development may now be available natively or through established applications and integrations.
This is particularly relevant to Shopify, where the platform’s expanding ecosystem is changing how merchants and their technology partners approach development.
Anton’s native-first philosophy is based on using the capabilities already available within Shopify wherever they meet the business requirement, rather than automatically creating something bespoke.
There are obvious potential benefits. Less custom code can mean fewer dependencies, reduced maintenance requirements and greater flexibility when the platform introduces new features.
But native first doesn’t mean no customisation.
Shopify still supports custom applications, integrations and more specialised functionality. The important distinction is between building within the platform’s intended architecture and creating solutions that work against it.
For businesses considering any new technology investment, the question is therefore not simply whether something can be built.
It’s whether building it creates enough value to justify the cost and ongoing responsibility.
Why total cost of ownership deserves more attention
The initial cost of an ecommerce project is only one part of the investment.
Licensing, hosting, integrations, support, development, maintenance and future upgrades can all contribute to the total cost of ownership, or TCO.
Some of those costs are obvious when a platform is selected. Others only become apparent as the business begins operating and developing the solution over time.
That’s why a platform evaluation needs to go beyond comparing features or implementation costs.
A solution that appears cheaper initially may carry greater ongoing costs. Equally, a more expensive implementation could potentially offer better long-term value if it reduces operational overhead or gives the business greater flexibility.
There is also a risk in approaching platform selection with a preferred answer already in mind.
Shopify may be an attractive option for many businesses, particularly those looking to simplify operations or reduce reliance on bespoke development. But it won’t necessarily be right for every retailer.
Complex omnichannel requirements, unusual sales environments or specific architectural constraints may point towards a different approach.
A proper evaluation should establish those requirements before committing to a platform.
It also needs to involve more than the technology team. Ecommerce leaders, finance, customer service and the people responsible for day-to-day operations may all have different perspectives on what the business actually needs.
Bringing those perspectives together helps prevent a technically impressive solution from becoming a commercially difficult one.
When did you last audit your technology stack?
Another practical point from the episode was the importance of regularly reviewing the technology a business already uses.
For many retailers, technology has been introduced gradually. An application is added to solve one problem, an integration is developed for another, and a new subscription is taken out to provide additional functionality.
Individually, those decisions may make sense.
Collectively, however, they can create a stack that is more expensive and complicated than necessary, particularly when functionality overlaps or tools are no longer being used to their full potential.
Anton recommends conducting a broader technology audit annually.
That means looking at the platforms and applications in use, their costs, performance and commercial contribution. It also means considering whether newer native functionality could replace something that previously required a separate solution.
The review doesn’t have to be limited to software licences. Website performance, accessibility, technical SEO, payment arrangements and the wider operational setup can all form part of the assessment.
An annual review also creates an opportunity to question assumptions that might otherwise go unchallenged.
Does the business still need this integration? Is this tool delivering enough value? Could a process now be handled more efficiently?
Those are useful questions regardless of which commerce platform a retailer uses.
AI is changing the economics of ecommerce operations
Of course, any discussion about technology efficiency in 2026 inevitably leads to AI.
What’s particularly interesting is how AI is influencing both sides of the ecommerce relationship.
For merchants, tools such as Shopify Sidekick and other AI-enabled applications are making it easier to access information, analyse data, automate tasks and manage parts of the business that previously required more manual effort.
There are also opportunities in customer-facing areas such as product search, merchandising, personalisation and sizing recommendations.
But the impact isn’t limited to what customers see.
AI is also changing the way ecommerce teams and agencies operate.
Tasks that once required significant manual input may be completed more quickly, while smaller teams can potentially take on responsibilities that previously required additional specialist resources.
That creates opportunities for more efficient operations, but it also changes expectations.
If technology allows a task to be completed in minutes rather than hours, how should the value of that work be measured?
Are businesses buying hours or outcomes?
One of the more thought-provoking parts of our conversation concerned the changing relationship between merchants and agencies.
Historically, many technology partnerships have been structured around projects, development hours and ongoing support retainers.
Those arrangements still have a place, but AI is challenging some of the assumptions behind them.
As merchants gain access to more capable tools, they may become less dependent on external partners for routine activities. At the same time, they will still need help with complex decisions, specialist requirements and longer-term strategy.
That could shift more of the value towards commercial guidance, platform expertise and the ability to identify opportunities for improvement.
Anton posed a particularly useful question: “Are you buying the outcome or the hour?”
It’s a distinction that matters for both agencies and retailers.
The time taken to complete a task doesn’t necessarily reflect its commercial value. Equally, businesses should be able to understand what they are getting from their technology partners beyond the number of hours delivered.
As AI continues to change how work is completed, those conversations are likely to become increasingly important.
Final thoughts
Ecommerce technology isn’t necessarily becoming less sophisticated. If anything, the capabilities available to businesses are expanding rapidly.
What may be changing is the amount of complexity retailers need to manage themselves to take advantage of those capabilities.
Modern platforms, native functionality and AI-enabled tools are creating opportunities to operate with leaner technology stacks and potentially smaller teams.
But simplification shouldn’t become another trend that businesses follow without understanding why.
The same principles still apply. Start with the commercial objectives, understand the requirements, evaluate the available options and consider the long-term implications of each decision.
For some businesses, that may mean migrating away from a legacy platform. For others, it could mean auditing existing applications, reducing custom development or making better use of functionality they already pay for.
The goal isn’t necessarily to have the simplest technology stack possible. It’s to have one that supports the business without creating unnecessary cost or complexity.
A big thank you to Anton Ekström for joining us on The FODcast and sharing his perspective on Shopify, native-first development, AI and the changing economics of ecommerce technology.
