Headless commerce is a real architectural option and an expensive default. Separating the storefront from the commerce engine buys flexibility and costs you the integration, the performance work and several capabilities that a packaged storefront provided without anyone noticing.
What you gain, stated precisely
Freedom to build any storefront experience without fighting a template system, the ability to serve several channels from one commerce engine, and independent deployment of the front end. Those are genuine and they matter most to businesses selling through more than a website, or whose storefront experience is a real differentiator rather than a preference about layout.
What you take on, which is usually understated
Search and merchandising, previously included, now yours to build or buy separately. Content and product data association. Preview for merchandisers, who otherwise cannot see changes before publishing. Performance, since a custom front end is only as fast as you make it. And the permanent obligation to keep the integration current as the commerce engine's interfaces change. Ask a bidder to price all five explicitly.
Performance is the argument, so contract for it
The usual justification for building a custom storefront is a faster, better experience, which makes it fair to hold the result to a measurement. Google documents what a well built page delivers: good Core Web Vitals, HTTPS, proper mobile display and no intrusive interstitials. Set targets on category and product templates, test on a real mid range phone at acceptance, and make payment depend on it. A slow headless storefront has lost its own argument.
Where a progressive web app fits
A progressive web app is a way of delivering the storefront, installable, capable of working offline and of receiving notifications, without an app store or its commission. For many retailers it is a better investment than a native app, since install friction is lower and updates are instant. The honest method is to list the capabilities you need and check each against current support on the platforms your customers actually use.
Questions people ask about headless commerce development
Is headless commerce worth it?
For businesses selling through several channels or whose storefront experience is a genuine differentiator, often yes. As a default it is expensive, because search, merchandising, preview, performance and integration maintenance all become yours.
What is most often understated in headless proposals?
Merchandiser preview and search and merchandising tooling, which the packaged storefront provided without anyone noticing, plus the permanent obligation to keep the integration current as the commerce engine changes.
Should we build a progressive web app instead of a native app?
Often yes for retail: lower install friction, instant updates, no store commission. List the capabilities you need and check each against current support on the platforms your customers actually use before deciding.