"Headless" gets marketed as if the word alone means independence. It doesn't. Plenty of headless storefronts sit on top of a fully hosted commerce platform, a custom Next.js front end calling a managed backend's API, and that's still renting, just with a nicer front door. Ownership lives in the backend, and it's worth being precise about what owning it actually buys you.
The fee that doesn't go away
A hosted platform's revenue share or transaction fee applies to orders processed through its backend, regardless of what front end sits in front of it. Rebuild the storefront in Next.js, keep the same hosted backend, and the fee structure is unchanged. You've improved the buyer experience and your SEO surface, not your margin. That's a legitimate and often correct move, but it isn't ownership, and conflating the two leads to a disappointing "why are we still paying this" conversation a year in.
Flexibility compounds the same way fees do
The fee argument is the easy one to quantify. The flexibility argument matters more over a longer horizon. A hosted platform's commerce logic is built for the median merchant, which is exactly why it's reliable, and exactly why unusual logic (tiered B2B pricing, split fulfilment across a marketplace, a subscription model the platform didn't anticipate) becomes a workaround, a third-party app, or a feature request with no committed timeline. On a self-hosted, modular engine, that same logic is a module you write, test, and ship on your own schedule.
Ownership has a real cost too, be honest about it
This isn't a free upgrade. Owning the backend means owning the operational burden: hosting, monitoring, security patches, and someone accountable when something breaks. That cost is real, and for a low-volume or engineering-light team, it can legitimately outweigh the fee and flexibility benefits, which is why we don't pitch self-hosting universally. We cover the actual crossover math in what headless commerce actually costs.
Weighing whether to own your backend?
We'll walk through your current platform fees, growth plan, and the commerce logic you can't express today, and tell you plainly whether owning the stack is worth it for your numbers.
Talk it through →The rule
Ask where your data, your commerce logic, and your fee structure actually live, not what your storefront is built in. If the answer to all three is "a platform we don't control," you have a headless front end, not an owned stack, and the fees and flexibility ceiling that come with that are permanent until the backend changes. For the architectural comparison this sits on top of, see Medusa vs. Shopify for headless commerce. This is the premise behind every headless commerce engagement we run.