Architecture
Headless commerce separates a custom web or mobile storefront from its commerce backend through APIs. It can deliver faster pages, unrestricted design and multiple channels on one data source, but it creates a second codebase and API contract to own. We use it when those benefits justify the added engineering.
Reviewed by Atul Makwana, CEO & Co-Founder, Heliconia Solutions · Odoo 16 Functional Certification · Odoo Partner · Updated
Businesses that run on what we built
Definition
Headless commerce separates the storefront (what customers see and use) from the commerce backend (catalog, cart, checkout, orders, inventory). The storefront is a standalone web or mobile application built with tools like Next.js or React Native. It talks to the backend (Shopify, WooCommerce, Odoo or a custom service) through APIs instead of using the platform's built-in theme layer.
The gains are concrete: page speed you control end to end, a design not constrained by the platform's theme system, and one backend serving web, mobile and any other channel. The cost is equally concrete: a second application to build, host and maintain, and an API contract between the two.
This page explains the pattern and helps you choose a backend. The deep dives live on their own pages: Headless Odoo, Headless Shopify and Headless WooCommerce.
Architecture
The backend changes. The storefront discipline doesn't.
Web storefront
Next.js / React: server rendering, edge caching
Mobile app
React Native / Flutter: same API
Content
Headless CMS (PayloadCMS) for pages and campaigns
Commerce API
Shopify Storefront API · WooCommerce REST/GraphQL · GraphQL on Odoo · custom
Commerce backend
Catalog, cart, checkout, orders, customers, inventory. Shopify, WooCommerce, Odoo or custom
Services
Payments · shipping · search (Meilisearch) · cache (Redis) · media (R2/S3)
Platform fit
Four options, three questions. Each has its own page for the detail.
| Odoo | Shopify | WooCommerce | Custom | |
|---|---|---|---|---|
| Content team size | Small to medium, content in a CMS alongside | Any, marketing-friendly admin | Large content teams at home in WordPress | Needs its own admin built |
| Catalog complexity | High: variants, lots, pricelists, B2B | Medium | Medium | Any |
| Existing backend investment | Already running the business on Odoo | Already on Shopify or want managed commerce | Already on WordPress/WooCommerce | Commerce is the product |
| Checkout control | Full | Limited: Shopify checkout stays | Full | Full |
| Deep dive | Headless Odoo | Headless Shopify | Headless WooCommerce | Custom application development |
If your operations (stock, pricing, orders) already live in an ERP, put the storefront on it. If they don't, choose the platform your team can run.
Deep dives
Odoo as the commerce and operations backend behind a Next.js storefront and mobile apps: our most-proven pattern.
Storefront API and Hydrogen, with Shopify checkout kept.
Decoupled storefronts that keep WordPress content and plugins.
When commerce is the product: your own catalog, cart and order services.
When not to
Most stores shouldn't go headless. These are the signs.
A well-built Shopify theme or Odoo eCommerce store already converts. Speed can be tuned without an architecture change.
The shared-API benefit disappears when there's only one storefront.
A headless storefront is an application. If there's no team or budget to evolve it after launch, don't build it.
A platform store launches in weeks. Headless adds a frontend build first.
The performance and flexibility gains don't pay back on a store that doesn't need them.
Fixing stock accuracy, fulfilment or pricing in the backend often lifts conversion more than a new storefront.
Evidence
A Next.js storefront and a Flutter catalog app, both on Odoo backends over GraphQL. The storefront discipline transfers to Shopify and WooCommerce. The deep dives explain how.
eCommerce, baby care
A direct-to-consumer baby care brand selling through a Next.js storefront, with Odoo behind it for ERP, inventory, orders and customers: connected over GraphQL, with Cashfree payments, Shiprocket shipping and a distributor onboarding portal.
Jewellery manufacturing
A bangle and fashion-jewellery manufacturer’s product catalog managed in Odoo and delivered to a cross-platform Flutter app over GraphQL, with media on Cloudflare R2 and production monitoring.
What clients say
Heliconia transformed our business with Odoo. They implemented a dynamic website with e-commerce capabilities, enhancing our online presence significantly.
Sandesh ThummarBusiness Owner, Ladder LogixHeliconia's Odoo Enterprise implementation, along with third-party system integration, has optimized our processes. Their expertise has been a game-changer.
Vladimir VukovicCEO, Mevalon ProdukteQuestions
With server/edge rendering, caching and an image pipeline under your control, headless storefronts typically reach Largest Contentful Paint well under 2.5 seconds on mobile where theme-based stores often sit at 3-5 seconds. The gain depends entirely on execution: a badly built headless storefront is slower than a good theme. We set Core Web Vitals budgets and measure against them.
Yes. You're building and hosting a second application and maintaining an API contract. It pays back when the storefront experience drives revenue, a mobile app is required, or several channels share one backend, and not otherwise.
The backend stays: products, orders, customers and (on Shopify) checkout are untouched. The storefront is rebuilt: that is what headless means. Content, URLs and SEO are migrated with redirects, and the switch can be done market by market.
Yes, and for businesses that run operations on Odoo it's usually the best backend: stock, pricing, B2B rules and orders are already there, so there's nothing to synchronise.
Next.js with React and TypeScript for web. React Native or Flutter for mobile. PayloadCMS for content. The same stack across every backend.
Yes, if it's planned: URL mapping and redirects, server-rendered pages, structured data and sitemaps are part of the build, not an afterthought.
Next step
Tell us your platform, catalog and channels. We'll tell you whether headless pays back, and which backend to put behind it.