Frntkey blog
Long-form articles on headless commerce, frontend-as-a-service, and the frameworks that power composable storefronts.
Composable commerce
Composable commerce assembles best-of-breed services for every layer of the stack through APIs. The architecture is real and powerful. The cost is also real and often underplayed in vendor content.
Composable vs headless vs monolithic
The terms overlap in vendor marketing but mean different things in delivery. The choice shapes the team, the timeline, and the total cost over a three-year horizon.
Frontend as a Service
Every headless commerce project rebuilds the same storefront: catalogue, product detail, cart, checkout, account, search, content blocks. Frontend as a service treats that surface as a product instead of a from-scratch build.
Headless architecture
Headless decouples the storefront from the commerce engine. Most explainers stop there. This one covers the four layers, the honest tradeoffs, and when headless is actually the right call.
Headless frontend
A headless frontend is the storefront layer that runs independently of the commerce engine. It connects through APIs, deploys on its own cadence, and sets a higher ceiling for performance and customization than any platform theme.
Vue and Nuxt for headless commerce
A storefront has to render fast, hydrate cheaply, and stay maintainable across a multi-year lifecycle. Vue and Nuxt fit that brief in ways that are worth understanding before committing to a framework.
What is Norce Commerce
Norce is the API-first commerce engine behind a large share of Nordic B2B and D2C merchants. It owns the catalog, pricing, and orders. The storefront connects through the API and runs independently.