Shopify or headless commerce: how to choose

What headless actually means

A standard Shopify store does two jobs. It runs the commerce engine: products, stock, checkout, orders, payments. It also draws the storefront your customers see, through a theme.

A headless store splits those jobs. Shopify, or another commerce engine, still runs products and checkout. The storefront becomes a separate web application, often built with Next.js and React, that talks to the engine through an API.

Nothing about the split is visible to a shopper. What changes is who is responsible for the storefront: with a theme it is largely the platform, and with headless it is you.

What standard Shopify gives you

• A fast launch. A theme, your products and your payment setup can be enough to start selling.
• An app ecosystem. Reviews, subscriptions, loyalty and many other features install into a theme with little or no development.
• Less to maintain. Hosting, security updates and checkout are handled by the platform.
• Control for your team. Marketing can change pages and layouts in the theme editor without a developer.

For a store with a normal catalogue and a normal buying journey, this covers almost everything, and it keeps running costs low because there is no custom front end to look after.

When headless earns its cost

• The experience is the product. Complex configurators, heavily editorial layouts, or interactions a theme keeps fighting against.
• Several systems feed one storefront. An ERP, a product information system, more than one regional store, or stock held in different places.
• Content leads and commerce follows. A publication, community or brand site where the shop is one section and the content system matters as much as the catalogue.
• Speed has hit a ceiling. A theme carrying many app scripts can become slow, and a purpose-built front end gives you full control over what loads.

Notice that each of these is a specific limit you can point to. A general feeling that headless is more modern is not on the list.

What headless costs you

You are building and hosting a web application, and you will keep maintaining it. That is the main cost, and it does not end at launch.

• Many apps that plug into a theme will not work as they are. Their features have to be integrated by hand or replaced.
• Changes that marketing could make in a theme editor may now need a developer, unless a content system is set up to give that control back.
• Previews, drafts and scheduled changes do not come for free. They are part of what you build.
• There are two things to keep healthy, the storefront and the commerce platform, and two places a problem can come from.

Check payments and delivery first

Whichever route you take, confirm early that the payment methods your customers actually use are supported in the markets you sell in, and that your delivery partners can be connected. In some regions this narrows the options more than any technical preference does, and it is far cheaper to find out before the build than after.

A simple way to decide

Answer three questions honestly.

• Can you describe, in a sentence, the thing a Shopify theme cannot do that your store needs?
• Do you have, or are you prepared to pay for, developers to maintain a storefront after launch?
• Are several back-end systems involved, or will there be soon?

If the answers are no, start on standard Shopify. If you answered yes to the first and at least one of the others, headless is worth pricing properly.

You can change your mind later

This is the part that takes the pressure off. Your products, customers and order history live in the commerce platform, not in the storefront. A store that starts on a theme can move to a headless front end when it reaches a real limit, keeping its data and its checkout.

Starting simple and moving when there is a concrete reason is usually the cheaper path, and it means the headless build is designed around problems you have actually met.