WolfSellers — Adobe Experience Cloud Partner en México

Architecture · Modern commerce

Composable Commerce — MACH architecture for enterprise eCommerce

Composable Commerce is the architectural model where the commerce stack is composed of best-of-breed services connected via APIs, instead of a vertical monolith. It follows MACH principles (Microservices + API-first + Cloud-native + Headless). WolfSellers implements composable architectures using Adobe Commerce as the catalog/order engine + decoupled frontend (PWA Studio, Next.js, Hyvä) + specialized services (Algolia, Talon.One, Contentful, Stripe).

Book a callSee all services

Definition

What is Composable Commerce?

Composable Commerce (also called MACH architecture or modular headless) is the approach where every layer of the eCommerce stack lives as an independent service — catalog, cart, checkout, search, payments, CMS, OMS — connected via APIs. This contrasts with monolithic platforms that integrate everything vertically (classic Salesforce Commerce Cloud, Shopify without apps, pre-headless Magento).

The advantage: you can swap a piece without re-architecting the rest. Is your search underperforming? Replace Elasticsearch with Algolia in a sprint without touching checkout. Want a better CMS for editors? Swap to Contentful or Sanity without rebuilding the storefront.

MACH

The 4 MACH principles

MACH Alliance (founded 2020 by commercetools, Contentstack, EPAM and Valtech) defined the 4 requirements for a truly composable architecture:

  • Microservices: each business function lives as an independently deployable service
  • API-first: everything communicates via well-designed APIs (REST, GraphQL, event-driven)
  • Cloud-native: built to run on managed cloud with elastic scaling
  • Headless: frontend decoupled from backend, total UI stack freedom

Adobe Commerce

Composable on Adobe Commerce

Adobe Commerce offers full GraphQL APIs since version 2.3 and Adobe Commerce Optimizer (2024+) for composable-first architectures. It's not monolithic in the classic sense: you can use it as the catalog/orders engine only and build the rest with best-of-breed services.

  • Adobe Commerce as the engine: catalog, orders, promotions, pricing, B2B
  • Headless frontend: PWA Studio (React), Hyvä (lightweight server-side), or custom Next.js against GraphQL
  • Search: Adobe Live Search native, Algolia, or custom Elasticsearch
  • CMS: Adobe Experience Manager Sites or Contentful / Sanity for content
  • Payments: Stripe, Mercado Pago, Conekta, Adyen as independent layer
  • OMS: integrated Walker OMS, Shopify OMS, or custom middleware
  • Personalization: Adobe Target + Real-Time CDP fueling the frontend

Decision

Composable vs monolithic — when to pick each

Not every client needs composable. The honest criteria:

  • Pick composable if: multiple channels (web + app + in-store), complex catalog that needs PIM integration, senior tech team, GMV >$5M/year, need to swap specific pieces for performance/cost
  • Pick monolithic if: single B2C storefront, small team, GMV <$5M, preference for fast time-to-market over future flexibility. Shopify Plus or monolithic Adobe Commerce with Hyvä theme are excellent
  • Hybrid: traditional Adobe Commerce (monolithic) with Hyvä frontend is a middle ground — speed without full-composable complexity

Delivery

What we do on a composable project

A new composable implementation takes 6-12 months depending on number of services. Our delivery includes:

  • Discovery: evaluate which best-of-breed services fit your case
  • Architecture: services diagram, APIs, data flows, event bus
  • Headless frontend: PWA Studio, Next.js or Hyvä per profile
  • Service integration: orchestration middleware with retries and idempotency
  • End-to-end observability: distributed tracing, logs-metrics-traces correlation
  • Per-service CI/CD with independent deploys (microservices deployability)
  • Contract strategy between services (Pact, OpenAPI)
  • Governance: ADRs, API docs, runbooks

Frequently asked questions

What is Composable Commerce?
Composable Commerce is an architectural model where the eCommerce stack is composed of best-of-breed services (catalog, checkout, search, CMS, OMS, payments) connected via APIs instead of a vertical monolith. Follows MACH: Microservices, API-first, Cloud-native, Headless. Lets you swap individual pieces without rebuilding everything.
Can Adobe Commerce be composable?
Yes. Adobe Commerce provides complete GraphQL APIs and Adobe Commerce Optimizer (2024+). You can use it only as the catalog/orders engine and combine it with a headless frontend (PWA Studio, Next.js, Hyvä), external search (Algolia), separate CMS (AEM, Contentful), and independent payments and OMS. It's a real composable architecture with Adobe Commerce at the center.
Composable Commerce vs Headless Commerce?
Headless is a subset of composable: separating frontend from backend. Composable goes further — every stack piece can be an independent service, not just frontend. All composable is headless, but not all headless is composable (you can have a headless frontend on a monolithic backend).
What are the downsides of composable?
High operational complexity: coordinating multiple services, API versioning, distributed observability, governance. Requires senior tech team. Higher initial cost: each service has its own license + operation. Slower initial time-to-market. That's why it doesn't make sense for small/mid stores.
What is the MACH Alliance?
MACH Alliance is the organization that formalized the Microservices + API-first + Cloud-native + Headless principles in 2020. Co-founded by commercetools, Contentstack, EPAM and Valtech. It evangelizes the composable model and certifies vendors that meet the 4 principles.

Related services

Adobe Experience Cloud

Pillar: Adobe's complete suite — Commerce, Experience Manager, Experience Platform, Target, Marketo, Journey Optimizer, Workfront. We're a Gold Partner implementing the entire stack.

Learn more →

Adobe Commerce

Adobe Commerce (formerly Magento) implementation with all native capabilities: catalog, checkout, payments, promotions, Page Builder and more.

Learn more →

Adobe Commerce B2B

B2B stores with purchase lists, quotes, approvals, customer-specific pricing and corporate account management.

Learn more →

Adobe Experience Manager (AEM)

AEM Sites + Assets + Forms and Adobe Target: enterprise CMS, DAM and personalization at scale for omnichannel experiences.

Learn more →

Want to discuss your project?

We'll assess your case at no cost and propose a concrete path forward.

Book a call