Hosted builder vs. custom storefront

A hosted builder is the right choice for most merchants: the vendor runs hosting, checkout, security and updates, and you run the business. A custom or headless storefront, built in code on top of a commerce backend, is worth it only when you have a requirement a theme cannot meet and people to maintain the code.

Shopify’s own developer documentation says a headless storefront costs more to build and run than a theme. Take that at face value when you weigh the two.

The short version

• Default to hosted. If you are unsure, you do not need a custom storefront.
• Custom usually means headless, not from scratch: your front end, a vendor’s commerce backend and checkout.
• The cost is upkeep, not the first build. Budget for years of maintenance.
• Coding agents lower the build cost, and they do not remove the need for review.

What the terms mean

• Hosted builder: one product gives you the admin, the storefront theme, the checkout and the hosting. Shopify, Wix, Squarespace, Hostinger and BigCommerce work this way.
• Self-hosted platform: you install commerce software on hosting you choose. WooCommerce on WordPress is the common example, and it still uses themes, so it is self-hosted without being custom.
• Headless storefront: you write the front end in code and connect it by API to a commerce backend. In Shopify’s words from its headless documentation, you build the front end and its APIs handle the commerce underneath.

Side by side

What to compare	Hosted builder with a theme	Headless on a hosted backend	Fully self-hosted custom stack
Examples	Shopify, Wix, Squarespace, BigCommerce	Shopify with Hydrogen, BigCommerce with Catalyst	Medusa with its Next.js starter
Who builds the storefront	You, in a visual editor	Developers or coding agents, in a repository	Developers or coding agents, in a repository
Who runs checkout	The vendor	The vendor	You integrate a payment provider
Hosting	Included	Yours, or the vendor’s option for its own framework	Yours
Design freedom	Within the theme system	Whatever you can code	Whatever you can code
Ongoing work	Low	Framework and dependency upgrades, your own deploys	All of that, plus the server and database
Where the code lives	The vendor’s platform	Your Git repository	Your Git repository

When a hosted builder is right

For most merchants, which means almost every store that is new, small or run by a team without developers:

• You want to be selling in days or weeks.
• Your catalogue, checkout and shipping are ordinary. Most are.
• Nobody on the team wants to be responsible for uptime or security patches.
• The changes you want are covered by theme settings or an app.

A theme limitation is rarely a reason to leave. Shopify, for example, documents generating custom theme blocks from a prompt without writing code. Exhaust theme settings, apps and theme customisation first. How to choose an ecommerce AI builder covers picking between hosted platforms.

When a custom storefront is worth it

Look for a hard requirement, not a preference:

• An unusual buying experience, such as a product configurator or a guided flow that does not fit the product-page-and-cart pattern.
• The store lives inside something else, for example an existing web application or a content site with its own framework and design system.
• Strict front-end control, where you need to decide exactly what loads on each page.
• Several storefronts on one backend, each with a different design for a brand or region.

And a capability check: someone must own the code after launch. Framework releases, API version changes and dependency updates arrive whether or not you have time for them.

The starting points

On a hosted backend. Shopify’s toolkit is Hydrogen, and its documentation describes Oxygen as Shopify’s hosting for Hydrogen storefronts. You may also use another framework and host with the same APIs. BigCommerce’s Catalyst is an open-source storefront built with Next.js and React on its GraphQL Storefront API, and it requires a BigCommerce store behind it. In both cases the vendor still holds products, customers and checkout.

Fully self-hosted. Medusa describes itself as an open-source commerce platform with a built-in framework for customisation. Its core is MIT-licensed and it offers a Next.js storefront starter. This gives the most control and the most responsibility: the server, the database and the payment integration are yours.

Start from a vendor’s starter project. A storefront written from an empty folder repeats solved problems, and cart and checkout edge cases are a bad place to learn.

Who does the work

A custom storefront is ordinary web development: product listing and detail pages, search, cart, account pages, the hand-off to checkout, analytics events and tests. That is work AI coding agents handle well, because each piece can be written as a task with a checkable result (“the cart updates quantity without a page reload; add a test”).

Vendors now support this directly. Shopify’s AI Toolkit connects coding tools, including Claude Code, Codex and Cursor, to its developer documentation and API schemas so that agents look up the current API instead of guessing.

What agents do not do is decide what to build or accept the result. A person still reviews each diff, places test orders and checks tax, shipping and accessibility behaviour before launch. The ecommerce launch checklist applies to a custom storefront in full.

Our pick · we make it

If you do go custom: run the coding agents with Emdash

Emdash is our product. It is not an ecommerce platform, a website builder or a host, and most merchants reading this page do not need it. A hosted platform such as Shopify is the right answer for them.

For teams that are building a storefront in code, Emdash runs AI coding agents such as Claude Code and Codex in parallel, each task in its own isolated workspace, and gives you the diffs and pull requests to review. A storefront breaks down naturally into parallel tasks: product page, cart, search, tests. Emdash Classic is a free, open-source desktop app for macOS, Windows and Linux, and you bring your own agent subscription or API key. Emdash 2.0, which runs agents in the cloud for teams, is in early access.

See Emdash →

How to decide

1. Write down the requirement that a hosted theme cannot meet. If you cannot name one, stay hosted.
2. Ask whether an app, a theme code edit or a higher plan would meet it. If so, stay hosted.
3. Confirm who will maintain the storefront in two years. If nobody, stay hosted.
4. If you still need custom, go headless on a hosted backend before considering a fully self-hosted stack, so that checkout stays the vendor’s problem.

To see what the hosted platforms’ AI tools already cover before you decide, read what AI does in a store builder.

Frequently asked questions

What is a headless storefront?

A headless storefront is a shop front end that you build and host yourself, connected by APIs to a commerce backend that holds products, carts, customers and checkout. Shopify's developer documentation describes it as separating the storefront's front end from its back end.

Is a custom storefront better than Shopify?

Usually not, and the two are not opposites. Most custom storefronts still run on a hosted commerce backend such as Shopify or BigCommerce and replace only the theme. A custom front end gives you more control over design and performance, and costs more to build and maintain than a theme.

When is a custom or headless storefront worth it?

It is worth it when you have a specific requirement a hosted theme cannot meet, such as an unusual buying flow, a storefront embedded in an existing application or strict control of front-end performance, and you have people who can maintain code for years. Without both, stay on a hosted theme.

Can AI coding agents build a custom storefront?

They can do much of the work, particularly with a documented starter such as Hydrogen, Catalyst or the Medusa storefront template. Someone still has to specify the tasks, review each change and take responsibility for checkout, tax and accessibility behaviour.

Do I have to build my own checkout with a headless storefront?

Not on the hosted backends. Shopify's documentation says its Storefront API serves products, collections, search and the cart and then hands customers off to Shopify's checkout. A fully self-hosted platform leaves more of the payment integration to you.