Headless Commerce

In a traditional Shopify setup, themes render server-side using Liquid templates. The storefront and the commerce backend are tightly coupled: changing the look of a product page means editing theme code that runs inside Shopify. In a headless setup, the theme is replaced by a separate front-end application, often a Next.js or Hydrogen site, that calls Shopify's Storefront API to fetch products, manage carts, and create checkouts.

The commerce backend continues to handle inventory, payments, fulfilment, taxes, and admin. The headless front-end handles routing, rendering, search UX, and any custom interaction model. Because the front-end is a normal web app, the team can use any framework, deploy on any host, and ship features that would be hard or impossible inside a Liquid theme.

For example, a fashion brand running headless on Next.js builds a custom product page with side-by-side comparison and 360-degree product views, while still pushing every sale through Shopify's checkout. A second example: a multi-brand retailer uses one headless front-end that reads from two Shopify stores plus a custom CMS, presenting a unified storefront across all three sources.

For Shopify merchants, headless is rarely the right first move. It replaces a fast-out-of-the-box theme system with a custom application that needs developers, hosting, and ongoing maintenance. The conversion gain has to be worth that overhead.

That said, headless makes sense when the merchant has a strong reason to leave the theme system: complex product configurators, multi-region storefronts, deep CMS integration, or a need to ship native apps that share the same content. Apps like Shop Me work with both Liquid themes and headless storefronts because they integrate via APIs rather than theme files, which means the assistant follows the merchant whether they stay traditional or go headless later.