What is headless commerce?
Headless commerce separates the frontend presentation layer from the backend commerce engine. Instead of a monolithic platform rendering catalog, checkout, and storefront in one system, the backend exposes APIs that any frontend can consume — a custom React or Vue.js application, a mobile app, an in-store kiosk, or a marketplace integration.
In practice, this means the development team builds the storefront independently from the commerce logic. A product page fetches catalog data via API. The checkout calls the commerce engine's order API. Inventory checks happen in real time through the same interface. The frontend is deployed and scaled separately from the backend.
This is where Frntkey comes in — a plug-and-play headless ecommerce solution built on Nuxt.js, Vue.js, and Tailwind CSS. Unlike empty frameworks that require months of frontend development, Frntkey provides a complete storefront that works out of the box — product listing, search, checkout, account pages — yet is fully flexible to customize. It's the fastest way to go headless without starting from scratch.
Composable commerce and MACH
Composable commerce extends headless by assembling the entire stack from best-of-breed services connected through APIs. The MACH framework provides the architectural principles:
- Microservices: Each business capability (commerce, search, CMS, payments) runs as an independent service. Replace or upgrade one without touching the rest.
- API-first: Every service exposes a well-documented API. The frontend, integrations, and other services communicate exclusively through APIs.
- Cloud-native: Services run on modern cloud infrastructure (AWS, GCP, Vercel) with auto-scaling, CDN, and global distribution.
- Headless: No built-in frontend. The presentation layer is completely decoupled.
Junipeer acts as the API and integration layer in a composable stack — connecting the commerce engine to ERP, payment, shipping, CRM, and PIM services. Standard integrations to Fortnox, Visma.net, and Business Central can be live same-day — in as little as 30 minutes.
NWT's headless stack
Nordic Web Team delivers headless commerce through a proven stack of complementary services:
- Norce: The commerce engine. API-first from the ground up, designed to power any frontend. Handles complex catalogs, multi-brand, multi-market, and B2B pricing natively.
- Frntkey: Plug-and-play headless frontend. A complete storefront on Nuxt.js and Tailwind CSS that works immediately — but is fully customizable. Not a blank canvas; a production-ready starting point.
- Junipeer: iPaaS middleware. Connects the commerce engine to all backend systems — ERP, payment, shipping, CRM, PIM. Standard ERP integrations go live same-day.
- Storyblok: Headless CMS. Powers content pages, landing pages, and editorial content alongside the commerce frontend.
- Hyvä: For Magento-based headless. Replaces the legacy Luma frontend with a modern, performant alternative while keeping Magento's backend.
Headless with each platform
Norce + Frntkey: The native headless combination. Norce provides the commerce API — catalog, pricing, orders, inventory — while Frntkey delivers a plug-and-play storefront. No built-in frontend to fight against. The fastest path to enterprise headless with Nordic B2B capabilities, multi-brand support, and Junipeer integrations.
Shopify + Hydrogen/Frntkey: Shopify's Storefront API enables headless builds while keeping Shopify's checkout, app ecosystem, and operational simplicity. Hydrogen (React-based) is Shopify's own headless framework. Frntkey can also be connected to Shopify's API for teams preferring Vue.js. Best for D2C brands wanting headless UX without leaving the Shopify ecosystem.
Shopware Frontends: Shopware's Vue.js-based headless starter provides a solid foundation with comprehensive admin API coverage. The B2B suite works in headless mode. Best for mid-market businesses with strong content and B2B merchandising needs. NWT is an official Shopware Key Partner.
Magento + Hyvä: Hyvä replaces Magento's slow Luma frontend with a modern, lightweight alternative — dramatically improving performance without changing the backend. For fully headless Magento, Frntkey or custom frontends via GraphQL provide complete frontend freedom. Best for complex catalog and checkout requirements where open source flexibility matters.
Systems in a headless architecture
A headless storefront doesn't operate alone. It needs a constellation of backend services connected through APIs:
ERP: Fortnox, Business Central, Visma.net, SAP S/4HANA, NetSuite, Monitor, and Pyramid — for orders, invoicing, inventory, and accounting. You always need an ERP; Swedish accounting law requires it.
Payment: Klarna, Svea, Adyen, Nets, Walley, Avarda, Briqpay, and Qliro — checkout, invoicing, and B2B payment flows.
Shipping: Ingrid for delivery checkout and nShift for transport management and label printing.
CRM: Klaviyo, Dotdigital, Rule, Yotpo, and Nosto — email, SMS, loyalty, reviews, and personalization.
Search & discovery: Klevu — AI-powered product search and merchandising.
Cloud: Vercel, AWS, Cloudflare, Fastly — hosting, CDN, and edge computing for headless frontends.
Junipeer connects all of these — standard ERPs in as little as 30 minutes, with fully custom integrations supported too.
When does headless make sense?
Headless is the right choice when you need: multi-brand or multi-market storefronts from a single backend, extreme frontend performance and custom UX, unique buying experiences that the platform's built-in frontend can't deliver, or gradual migration from a legacy monolith.
When it doesn't make sense: simple single-market stores where a platform theme is sufficient, very small teams without frontend development capacity, or extremely tight timelines where a standard theme launches faster. That said, Frntkey dramatically lowers the barrier — a plug-and-play headless storefront means you don't need to build from scratch.
See also: Choosing the right ecommerce platform | ERP integration guide