Glossary
Headless Commerce
Meaning and details
Headless commerce splits the shop in two: a commerce engine, catalog, cart, checkout, orders, inventory, exposed as APIs, and a separate frontend, a Next.js site, a mobile app, a kiosk, built with whatever renders best....
Headless Commerce meaning
An e-commerce architecture where the storefront frontend is decoupled from the commerce backend, communicating through APIs.
What is Headless Commerce?
Headless commerce splits the shop in two: a commerce engine, catalog, cart, checkout, orders, inventory, exposed as APIs, and a separate frontend, a Next.js site, a mobile app, a kiosk, built with whatever renders best. The classic bundled platform, theme-and-all like early Shopify or WooCommerce, couples them; headless trades turnkey simplicity for total control over the experience.
Why it matters to an indie builder: the decision is speed versus surface. Bundled gets a store live in a weekend with themes you did not write; headless lets the product page, the actual conversion surface, be engineered like an application, sub-second loads, custom configurators, content woven into commerce. The modern middle is comfortable: Shopify's storefront APIs and checkout let you own the frontend while renting the payments plumbing, which is the configuration most indie brands actually want.
A concrete example: a specialty coffee roaster on a standard theme converts 1.1 percent, and the product page cannot express what sells the beans, origin story, roast curve, brewing guides. A headless rebuild on the same commerce backend: editorial product pages with subscriptions as a first-class flow, 90ms page loads, and a bundle builder the theme could not host. Conversion reaches 1.9 percent and subscription share doubles. Same catalog, same checkout, the entire gain lives in the freed frontend, and it was bought with about six weeks of frontend work.
Common mistakes: going headless for the architecture credit rather than the experience, which buys complexity and pays for it in maintenance, rebuilding what the platform already gives away, the bundled checkout is a hardened, conversion-tuned artifact, replacing it is rarely wise, scattering commerce logic across the frontend (pricing and inventory truth must stay server-side in the engine), and skipping the operational readiness, headless means you own uptime, caching and edge cases the theme used to absorb. The cms and hosting blocks on IndieBoot are the usual companions to this pattern.