Custom headless commerce platform development for brands that truly want control of their e-commerce
We build headless commerce platforms for brands that want to go beyond standard Shopify or WooCommerce: a custom frontend with blazing-fast performance, a commerce engine of your choice, and integrations with PIM, OMS, ERP and CRM. MACH architecture where it makes sense: not as a hype, but as a pragmatic choice.
When headless commerce really makes sense, and when it doesn't
Headless commerce is not a holy grail. For some brands, a good Shopify theme is faster, cheaper and just as effective. For others, headless is the only route to the customer experience and operational scale they want. Honest triage is the first question.
Headless fits when
We often advise against headless when
Our approach: from platform choice to production launch
We work in clearly defined phases with measurable deliverables. At the end of each phase, you know exactly what has been built, what it cost and what the next step involves.
Discovery & platform choice
2-4 weeks: business goals, channels, integrations and KPIs are defined. We assess 2-3 commerce engines (Shopify Plus + Hydrogen, commercetools, Saleor, BigCommerce, Medusa) against your requirements and give you a well-founded recommendation with a TCO comparison.
Architecture & integration design
3-5 weeks: the data model, integration flows (PIM, OMS, ERP, CRM, payment, shipping), event architecture, identity & access, performance budget and observability are documented. Only then do we start building.
MVP storefront on the core catalogue
2-4 months: a first storefront with the product categories that carry 80% of your traffic. End to end: product detail, listing, search, basket, checkout, order confirmation, account. Performance is part of the pipeline from day 1.
Integrations go live
In parallel: PIM feed, stock sync, price sync, order sync to OMS/ERP, CRM events. Each with dual-write or compare mode between old and new, so data integrity can be validated before cutover.
Soft launch and gradual rollout
5-10% of traffic goes to the new platform via feature flags or CDN routing. We monitor KPIs: conversion, AOV, page speed, error rate. We scale up in stages to 100%, but only once the thresholds are met.
Decommissioning the old platform
Only once all SKUs, customers, orders and integrations have been migrated do we switch off the old platform. A stable parallel run of 6-12 months is normal at enterprise level.
Commerce engines we regularly recommend — and why
No religious wars. We recommend what fits your scale, team DNA and growth path. Here's what we choose most often.
Shopify Plus + Hydrogen / Remix
For brands that want to keep the mature Shopify checkout but need a storefront that is significantly faster than the standard themes. Stock, orders and payments stay in Shopify; the storefront is custom. Pragmatic, quick to launch, lower TCO than full headless.
commercetools
For enterprise B2B and brands with complex pricing, multi-tenant or multi-brand setups. Fully API-first, strong catalogue modelling, B2B features out of the box. High flexibility comes with higher licence costs and a steep learning curve.
Saleor
Open source, GraphQL-first, Python backend. A strong option for brands that want to self-host or keep licence costs under control. Its community and development pace have grown considerably in recent years.
Medusa
Open source, Node.js, modular. Strong for brands that want to fork their commerce engine or extend it extensively. At Appfront, a popular choice for niche products with unusual business rules.
BigCommerce + Catalyst
The middle path: the SaaS reliability of BigCommerce with a modern storefront (Catalyst, GraphQL, Next.js). For brands with mid-to-high volume that don't want the full commercetools investment.
What we choose less often
Magento (Adobe Commerce) remains powerful but is operationally heavy; we rarely choose it for new greenfield projects. Salesforce Commerce Cloud usually only makes sense where the whole Salesforce suite is already in use.
Tech stack for headless commerce
Pragmatic choices with strong vendor neutrality. We don't want you locked into a supplier who doubles their prices in two years' time.
Storefront frameworks
Next.js (App Router), Remix, Astro for content-heavy brand pages, Hydrogen for the Shopify stack. Always TypeScript.
CMS / content
Sanity, Storyblok, Contentful for brand content. Directus or Strapi where self-hosting matters.
Search & discovery
Algolia, Typesense, Meilisearch for product search. Klevu or Constructor for merchandiser tooling on larger catalogues.
Payment & fraud
Mollie, Stripe, Adyen, Klarna. Riskified or Signifyd for fraud screening in B2B scenarios. PSP-independent abstraction so you can switch.
OMS / fulfilment
Shopify order management, fluentcommerce, custom middleware to your ERP, Sendcloud for logistics routing, Shipstation for shipping labels.
Analytics & CRO
GA4, Matomo (privacy-first), Heap, Mixpanel for product analytics. VWO or Optimizely for A/B testing at storefront level.
Performance is a feature, not an afterthought
Storefront speed drives conversion. We build with a performance budget from day one, monitored in CI/CD.
Edge rendering & caching
Static pages prerendered at the CDN edge (Vercel, Cloudflare, Netlify). Dynamic data via SWR patterns and targeted invalidations. ISR/PPR where it makes sense.
Image optimisation
Responsive images with AVIF/WebP, lazy loading, correct dimensions and blur placeholders. CDN image services (Imgix, Cloudinary, Vercel Image) for on-the-fly transforms.
Lighthouse budget in CI
Pull requests that worsen LCP, CLS or TBT are blocked. Performance is not a post-launch project; it's a release criterion.
Streaming SSR
Above-the-fold content reaches the browser quickly, with long queries streaming in behind it. Perceived speed is higher than the technical TTFB suggests.
Prefetch & predictive routing
Next pages are preloaded on intent (hover, focus, viewport). Applied correctly, site navigation feels like a native app.
Real-user monitoring
Not just synthetic Lighthouse tests, but also RUM via SpeedCurve, Vercel Speed Insights or Datadog RUM. Real users on real networks are the truth.
Frequently asked questions about headless commerce platforms
What exactly is headless commerce?
Headless commerce decouples the storefront (the frontend, what the customer sees) from the commerce engine (the backend, where products, orders and checkout run). The frontend communicates with the backend via APIs, so you can use the same commerce data for web, mobile, kiosks and marketplaces, and build the frontend in whichever modern stack you like.
What is the difference between headless and MACH architecture?
MACH stands for Microservices, API-first, Cloud-native, Headless. Headless commerce is part of a broader MACH approach in which every component (commerce, CMS, search, payments, OMS) is a specialised, best-of-breed service with APIs. Not every headless project is fully MACH; sometimes a hybrid approach with a single commerce engine is the pragmatic choice.
Is headless commerce more expensive than a Shopify theme?
Initially, yes. The storefront has to be developed rather than bought, and integrations are custom. In the longer term (2-3 years), headless can work out cheaper thanks to better conversion, lower CRO friction and the ability to build across channels. So only go headless if the business case stands up, not "because it's modern".
How long does a headless commerce project take?
An MVP storefront on a core catalogue typically takes 4-6 months. A full migration from a legacy commerce platform, including integrations, takes 9-18 months depending on complexity. We work in phases with visible results along the way — no big-bang projects.
Which commerce engine should we choose?
It depends on scale, team capabilities and business model. Shopify Plus + Hydrogen for brands that want speed and pragmatism. commercetools for enterprise B2B with complex pricing. Saleor or Medusa for open source and cost control. We run a vendor-independent comparison for your context.What about SEO with headless?
Better than many template-based platforms, provided it's done well. Server-side rendering or static generation, structured data (Product, BreadcrumbList, Offer), canonical tags, hreflang for multi-locale and a correct sitemap are a standard part of our approach. Edge rendering often delivers better Core Web Vitals than traditional SaaS platforms.
Can you replace an existing platform without downtime?
Yes. We use gradual traffic routing (CDN rules or feature flags), parallel integrations with dual-write during the migration, and extensive validation before we commit. A typical cutover happens in phases, per category or per locale.
What if we want to hand maintenance over to our in-house IT team?
That's a standard part of the engagement. We work in mixed teams, record architecture decisions in ADRs, write runbooks and run knowledge transfer. By the end of an engagement, your team should be able to run the platform, with our remote support for anything that still needs it.
Ready to take your e-commerce from templates to custom?
We start with a platform strategy session. You get an honest assessment of whether headless suits your situation, a well-founded platform choice and a realistic view of scope, cost and lead time. No sales pitch.
Looking for a more concrete picture of the possibilities? On applatenmaken.com you'll find Custom commerce platform development.
If you want your product data to appear as schema markup in Google, read about implementing structured data.