Composable Commerce: Every Component, Best-of-Breed
commercetools · Medusa · Shopify Hydrogen · MACH
Leading e-commerce companies are migrating to headless architecture for greater agility. Composable commerce takes the concept further: every component (payments, catalog, search, CMS) is best-of-breed, connected via APIs.
- 5.0 Clutch rating
- 01 · Catalogue Products and prices in sync
- 02 · Experience Search, product page and cart
- 03 · Payment Gateways and anti-fraud
- 04 · Order ERP, stock and logistics
- 05 · Measurement Conversion and margin
- 06 · Operation Your team sells, the system scales
- Every sale refines the catalogue
In numbers
Kiwop Composable Commerce Results
Real data from our projects.
- 80+ E-commerce Projects E-commerce projects delivered with headless and composable architectures
- 5+ Years Headless Years of experience building headless frontends with Shopify Hydrogen, Astro and Next.js
- +35% Performance Improvement Average page speed gain in Kiwop projects with headless frontend vs monolithic
What's included
Service Deliverables
From strategy to full implementation.
- Architecture Design
- Platform Selection
- Frontend Development
- API Integration
- Migration Strategy
- Performance Optimization
Why
Monolithic vs Composable
Why modular commerce wins.
A monolithic e-commerce platform (Magento, PrestaShop, WooCommerce) is a single block where everything is coupled: frontend, backend, payments, catalog, search. Changing any piece means touching the rest. Composable commerce decouples every component: you use the best search engine, the best payment gateway, the best CMS, connected via APIs. The result: faster teams, better performance, and the ability to evolve each piece independently.
- Best-of-breed Components
- Zero Coupling
- +35% Speed
Definition
What Is Composable Commerce?
Composable commerce is an e-commerce architecture where every capability (catalog, payments, search, CMS, logistics) is an independent service, selected as best-of-breed, and connected via APIs. It follows MACH principles: Microservices, API-first, Cloud-native, Headless.
Summary
Executive Summary
For CEOs and e-commerce directors.
Leading e-commerce companies are migrating to headless and composable architectures for greater agility, performance and innovation capacity. This isn't a passing trend: it's the natural evolution of digital commerce toward modular stacks where every component is best-of-breed.
In our projects, clients get teams that ship changes in hours (not weeks), 35% better performance across Kiwop projects, and the ability to adopt new technologies without rewriting the entire stack.
Kiwop already builds headless with Shopify Hydrogen and WordPress headless. Composable commerce is the next step: the umbrella architecture that connects all our e-commerce development services into a cohesive offering.
- 80+ E-commerce Projects
- 5.0 Clutch rating
- +35% Performance Gain
For the CTO
Summary for CTO / Technical Team
Stack, platforms and architecture decisions.
Commerce engines: commercetools (enterprise, pure API-first, GMV-based pricing), Medusa (open-source, Node.js, ideal for startups and mid-market), Saleor (open-source, Python/GraphQL), Shopify Hydrogen (when you're already on Shopify), BigCommerce (SaaS with headless API).
Frontend: Astro (SSG/SSR, zero JS by default, ideal for content-rich catalogs), Next.js (React, ISR, Vercel-native), Nuxt (Vue, SSR/SSG), Remix (React, loader-based). Selection depends on team stack and interactivity requirements.
Typical integrations: Stripe + Adyen (payments), Algolia + Typesense (search), Payload CMS + Contentful (content), Segment + GA4 (analytics), Klaviyo (email), and ERPs via middleware (MuleSoft, n8n).
Technologies
- commercetools
- Medusa
- Saleor
- Shopify Hydrogen
- BigCommerce
- Next.js
- Astro
- Nuxt
- GraphQL
- REST API
- Stripe
- Adyen
- MACH: Microservices, API-first, Cloud-native, Headless
- Strangler fig pattern for gradual migrations
- Edge rendering (Cloudflare Workers / Vercel Edge)
- Event-driven: webhooks + message queues between services
Who it is for
Is It Right for You?
Composable commerce isn't for everyone. It's the right architecture when your scale and complexity justify it.
Who it's for
- E-commerce businesses with revenue >€500K/year that need to scale without rewriting.
- Teams frustrated by the sluggishness of their current monolithic platform.
- Businesses selling across multiple channels (web, app, marketplaces) that need a unified backend.
- CTOs who want to adopt new technologies without a full-stack migration.
- Companies with specific search, personalization or internationalization requirements their current platform can't handle.
Who it's not for
- E-commerce stores with <100 products and low traffic (standard Shopify is sufficient).
- Companies without a technical team to maintain a distributed architecture.
- If your budget is below €50K for the initial build.
- Businesses where standard WooCommerce or PrestaShop covers all needs.
- Very early-stage startups where product validation is the priority (not architecture).
Key points
Composable Commerce Services
Verticals for every phase of your project.
- 01
MACH Architecture Consulting
Assessment of your current stack, mapping components to replace, platform selection with PoC. ADRs (Architecture Decision Records) documented for every decision.
- 02
Commerce Engine Implementation
Setup of commercetools, Medusa or Saleor. Catalog, pricing, inventory, and tax configuration. Integration with your ERP and existing systems.
- 03
Headless Frontend
Storefront development with Next.js, Astro or Nuxt. Conversion-optimized design. Core Web Vitals passing, technical SEO, and mobile performance.
- 04
Integrations and Middleware
Connecting payments (Stripe, Adyen), search (Algolia), CMS, email marketing (Klaviyo), and ERPs. Event-driven with webhooks and queues.
- 05
Migration From Monolith
Gradual migration from Magento, PrestaShop or WooCommerce using the strangler fig pattern. Zero downtime. Catalog, orders and historical data migrated.
- 06
Optimization and Scaling
Edge rendering, image optimization, multi-layer caching. Traffic-based auto-scaling for peak periods (Black Friday, campaigns).
How we work
Implementation Process
From monolithic platform to composable commerce.
- 01
Discovery and Architecture
Analysis of your current stack, business requirements, volume and complexity. MACH architecture design with component selection. PoC with candidate platforms.
- 02
Commerce Engine + Integrations
Setup of the selected commerce engine. Catalog, pricing and inventory configuration. Payment gateway and ERP integration. API Gateway for orchestration.
- 03
Headless Frontend
Storefront development: product pages, category pages, checkout, user account. Performance and SEO optimization. Conversion testing.
- 04
Data Migration
Migrating catalog, customers, orders and history. Data integrity validation. 301 redirects for SEO. Planned cutover with rollback strategy.
- 05
Launch and Optimization
Go-live with intensive monitoring. Post-launch performance optimization. Checkout A/B testing. Business team training.
Risks and how we cover them
Risks and Mitigation
The real risks of migrating to composable commerce.
- 01
Operational complexity
MitigationComprehensive documentation (ADRs, runbooks), unified monitoring, and team training. Complexity is managed with processes, not ignored.
- 02
High upfront cost
MitigationTypical build: €68K–€128K. But ROI is recovered in 12–18 months through faster team velocity, better performance, and lower switching costs. Gradual migration to spread investment.
- 03
SEO loss during migration
MitigationComplete 301 redirects, URL preservation where possible, daily GSC monitoring. Planned cutover outside traffic peaks.
- 04
Multi-vendor dependency
MitigationEvery component is replaceable by design. Abstraction layer in middleware. If a vendor raises prices or shuts down, you swap it out without rewriting.
- 05
Composable talent shortage
MitigationKiwop already operates headless with Shopify Hydrogen and WordPress headless. We train your team on the new architecture with documentation and hands-on sessions.
Technologies
Composable Ecosystem
Platforms and tools we integrate.
- commercetools
- Medusa
- Saleor
- Shopify Hydrogen
- BigCommerce
- Next.js
- Astro
- Nuxt
- Remix
- React
- Vue.js
- Stripe
- Adyen
- Algolia
- Typesense
- Payload CMS
- Contentful
- Klaviyo
- Segment
- GraphQL
- REST API
The proof
Headless Commerce Experience
Kiwop has been building headless e-commerce with Shopify Hydrogen, WordPress headless, and custom frontends for years. Composable commerce is the natural evolution: the umbrella architecture that connects our expertise in frontend development, API integration, and performance optimization.
- 80+ E-commerce projects delivered
- 5+ Years of headless experience
- 5.0 Clutch rating
Why
Composable ≠ Expensive
Open-source makes composable accessible.
Composable commerce doesn't require commercetools at €200K/year. Medusa (open-source, Node.js) offers the same MACH pattern without license fees. Saleor (Python/GraphQL) is another solid alternative. The real cost is building the frontend and integrations, not the platform itself. For mid-market, a complete build with Medusa + Astro + Stripe starts from €50K.
- €0 Medusa/Saleor License
- From €50K Mid-Market Build
FAQ
Frequently Asked Questions About Composable Commerce
What e-commerce directors and CTOs ask.
What is composable commerce?
Composable commerce is an architecture where every e-commerce component (catalog, payments, search, CMS, logistics) is an independent service, selected as best-of-breed, and connected via APIs. It follows MACH principles: Microservices, API-first, Cloud-native, Headless.
How is it different from headless?
Headless only separates frontend from backend. Composable breaks apart the ENTIRE stack: every capability is an independent, replaceable service. You can have a headless commerce engine without being composable, but composable is always headless.
How long does a migration take?
New build from scratch: 12–16 weeks. Migration from a monolith (Magento, PrestaShop): 16–24 weeks with the strangler fig pattern. Includes data migration, SEO redirects, testing and training.
How much does a composable project cost?
Standard build (mid-market): €68K–€128K. Enterprise with complex integrations: €100K–€500K+. With Medusa (open-source): from €50K. Ongoing maintenance costs are similar to monolithic, but with greater agility.
Which commerce engine should I choose?
commercetools: enterprise, pure API-first, ideal for +€10M GMV. Medusa: open-source, Node.js, perfect for mid-market. Saleor: open-source, Python/GraphQL. Shopify Hydrogen: if you're already on Shopify. We evaluate based on use case, team and budget.
Will I lose SEO when migrating to headless?
No, if done properly. With SSR/SSG the frontend renders complete HTML for Google. 301 redirects for all migrated URLs. Intensive GSC monitoring during and after cutover. Our migrations maintain or improve organic traffic.
Can I keep my current tools?
Yes. That's the whole point of composable: you integrate what works and replace what doesn't. If your current ERP, payment gateway or email marketing platform works well, we connect it to the new stack via API.
What performance improvement can I expect?
In Kiwop projects, headless frontends with SSG/SSR and edge rendering are 35% faster than monolithic platforms. On PageSpeed: from 40–60 to 90+ on mobile. On conversion: +15–25% from the page speed improvement alone.
Next step
Is Your Monolithic E-commerce Holding You Back?
Free assessment of your current stack. We'll tell you if composable commerce makes sense for your case, which platforms fit, and what migration would cost.
- No commitment
- Response in 24h
- Custom proposal
Let's talk.
Initial technical consultation
AI, security and performance. Diagnosis with phased proposal.
- NDA available
- Response <24h
- Phased proposal
Your first meeting is with a Solutions Architect, not a salesperson.
Talk to an architect