Headless Solved Yesterday's Problems. But Is It Still the Right Investment?
Headless is a perfect example.
For a few years, headless was the answer every ambitious brand was supposed to give when asked about its tech stack. Performance. Flexibility. Creative freedom. Enterprise credibility.
The pitch was compelling. For many merchants, it delivered.
For others, it wasn’t appropriate. It introduced cost, complexity, and operational risk that simply wasn't justified by the business outcomes.
The decision was never really headless versus headed. It was always business requirements versus technology hype.
Our CRO, Richard "Stitch" Sandor, has had a front-row seat to both waves: the early enthusiasm for headless and the re-evaluation conversations happening today.
Back in 2020, iamota pitched against four other agencies for the same merchant. Every other agency recommended headless before they had fully understood the business.
iamota took a different approach.
Instead of starting with architecture, we started with the business. We looked at the merchant's growth objectives, GMV, internal technical capability, operating model, and budget before making a recommendation.
The answer was headed. iamota won the business. The merchant was successful.
As Stitch puts it:
"The decision was never really about headless or headed. It was always about requirements."
That same principle is even more relevant today.
Since then, Shopify has evolved dramatically.
Online Store 2.0 introduced modular customization without touching theme code. Metaobjects replaced many traditional CMS use cases. Shopify Markets simplified international commerce. Checkout Extensibility and Shopify Functions unlocked customization that previously required headless implementations.
The ecosystem evolved too.
A modern Shopify implementation in 2026 is fundamentally different from one several years ago.
Headless didn't stop working. Headed simply caught up.
Today, when merchants reassess headless, three themes consistently emerge:
Cost and complexity. Infrastructure, tooling, agencies, and specialist developers all introduce ongoing operational overhead.
Speed and agility. Routine merchandising changes often require developers, reducing experimentation and slowing teams down.
Business value. Many of the capabilities that once justified headless are now available natively within Shopify or through its app ecosystem.
There's another consideration that often gets overlooked: people.
Headless architectures frequently depend on a small number of highly specialized technical resources. As teams become leaner, the operational risk of maintaining those skills becomes just as important as the financial cost.
None of this suggests headless was the wrong decision. It simply reflects the reality that platforms evolve, and architecture should evolve with them.
Revisiting a headless decision isn't taking a step backwards. It's recognizing that what created the most value several years ago may not create the most value in 2026.
Which brings us back to Commerce Intelligence.
The question isn't: Should we be headless?
The better question is: Given where Shopify is today, where will our next commerce investment generate the greatest business return?
Sometimes the answer will still be headless. Sometimes it won't.
The important thing is that the decision starts with the business—not the technology.
Because technology changes, but business outcomes are what endure.
