headless-shopifylisted

# Headless Shopify Own the Shopify-specific architecture and delivery contract for a decoupled storefront. Keep Shopify as the commerce authority: product publication, pricing, inventory, discounts, tax, shipping, payment, checkout, order, and the supported account/extension surfaces remain platform contracts. ## Enter with a decision, not a framework First establish the required experience, channels, content model, integrations, merchant operating model, team capacity, and measurable reason a theme/app cannot meet the need. Headless is justified by a concrete constraint, such as a bespoke interaction model, multi-surface delivery, or a real integration boundary. Faster pages or visual novelty alone are not sufficient evidence. If Shopify's hosted theme, app, Checkout Extension, Storefront Web Components, or a native Shopify capability meets the accepted need, recommend that smaller solution and do not create headless plumbing. Read [Architecture decisions](references/architecture-decisions.md) before selecting a stack or planning a migration. ## Inspect the actual contract Determine and record: - Shopify plan, enabled sales channels, published products, Markets, customer account model, delivery methods, subscriptions/B2B, discounts, and required checkout or post-purchase surfaces. - Runtime and rendering model, ownership of routes, redirects, domains, cookies, cache, content, search, cart, customer identity, consent, analytics, error reporting, and webhooks.