Headless commerce decouples the shop your customers see from the system that runs your business: a fast Next.js/React storefront in front, your ERP behind it, talking over a clean API. Our first choice for the engine room is Odoo — products, pricing, stock, orders and invoicing straight from the ERP — but we build the same architecture on top of any ERP, backend or commerce platform you already run. Your customers get a storefront that loads instantly; your team keeps the system of record they know.
Odoo · product.template
Oak Desk Lamp
Sales price
On hand
Oak Desk Lamp
SALEScope
Catalogue pages are prerendered and served from the CDN edge, with only the interactive parts — cart, variant picker, checkout — hydrating as small islands. LCP drops from seconds to under one; Core Web Vitals go green. Speed is not vanity: it shows up in Google rankings and in conversion rate.
The public internet only ever sees the storefront and a narrow, audited API. Odoo — or whatever ERP you run — lives on a private network or behind a VPN, with no login form, no RPC endpoints and no database manager reachable from outside. The attack surface shrinks to an API contract, not a monolith of storefront plugins to keep patched.
A campaign or Black Friday spike hits the CDN and the storefront — not your ERP workers. Product data is served from a read-through cache in single-digit milliseconds, so the backend only sees cart mutations and checkout. You never scale the ERP because marketing ran an ad.
Swap or upgrade the backend without rebuilding the shop, and redesign the shop without touching the backend. An Odoo major upgrade becomes an API-contract test instead of a theme rewrite — we've moved clients across major versions without changing the storefront beyond dependency bumps.
The same commerce API that powers the web shop feeds a mobile app, a B2B portal, in-store kiosks or digital signage. Add a second brand or a wholesale channel as a new deployment against the same engine room — not a copy of your shop to keep in sync.
No per-transaction platform fees, no theme system fighting your brand, no vendor deciding what your checkout can do. The storefront is your code in your repository — every change is a pull request with a preview URL, and a bad release is one revert away.
Process
TypeScript, React and Next.js on the front; Odoo — or your ERP — as the system of record; an in-memory cache between them. Everything ships in containers on our own Kubernetes clusters.
The storefront is the customer-facing tip of a connected system. Odoo-first, but every connection works the same against the backend you already have.
FAQ
Something else on your mind? Ask us directly — you'll talk to the people who do the work, not a sales layer.
Ask your questionNews
Decouple the storefront from Odoo and you get a faster, safer, upgrade-proof shop. DragonflyDB caching, island architecture, GitHub version control, PR previews, VPN-isolated ERP, PWA mobile UX — everything we ship on every headless e-commerce project.