Packaged Business Capabilities (PBCs)

Packaged Business Capabilities (PBCs) are the modular building blocks of Composable Commerce. Coined by Gartner in 2020, a PBC is a software component that encapsulates a well-defined business function — such as Catalogue, Pricing, Checkout, or Search — bundling the APIs, services, data schemas, and event channels required to deliver that capability as an independently deployable unit. The key distinction from Microservices is that PBCs are scoped to be recognisable to a business user, not just an engineering team: a PBC is what a commercial stakeholder would call a "capability," not what a developer would call a "service."

Definition

Gartner introduced PBCs in the June 2020 report "Composable Commerce Must Be Adopted for the Future of Applications." Two Gartner phrasings of the definition circulate across vendor documentation:

Gartner PBC definition — two versions in circulation

Version 1 (shorter): "software components that represent a well-defined business capability, recognizable as such by a business user… [and] consists of a bounded collection comprising a data schema and a set of services, APIs and event channels." (Elastic Path, citing Gartner, 2020)
Version 2 (longer): "Independently deployable capabilities that include self-contained business data, logic and processes to perform a business function. These interact with other applications via APIs and event channels." (commercetools, citing Gartner, March 2026; Shopify, citing Gartner, February 2024) Both are attributed to Gartner. Without access to the original paywalled 2020 report, it cannot be confirmed whether these are from the same or different documents, or whether one has superseded the other.

Key terms

Term	Meaning
PBC	Packaged Business Capability — a business-recognisable, independently deployable software component
Composable Commerce	An architectural approach that assembles a commerce stack from interchangeable PBCs rather than a monolithic suite
MACH Architecture	Microservices-based, API-first, Cloud native SaaS, Headless — the certification framework that positions MACH-compliant services as the de-facto PBCs
Headless Commerce	Decoupling the frontend from the backend; composable extends this by also decoupling backend capabilities from each other
Monolith	A single-codebase commerce platform (e.g. Magento 1, SAP Hybris on-prem) where all capabilities are tightly coupled
Microservices	Fine-grained, single-responsibility services that may form the internal implementation of a PBC
Orchestration layer	Middleware (e.g. Atama Composer, GraphQL delivery API) that composes PBC outputs into a unified experience without custom integrations per vendor

PBCs vs microservices vs monoliths

Per commercetools (March 2026 blog) and Elastic Path (January 2026 blog), the three layers are:

Monolith: single codebase; updates affect the entire platform; vendor lock-in through proprietary extension models.
Microservices: granular, single-responsibility services — the "internal wiring." Each has its own SLA, deployment pipeline, and testing regime. High flexibility; high operational overhead.
PBCs: bounded collections of microservices that together deliver a business-named capability. Deployed as a unit. Business and engineering teams can share the same vocabulary.

Example (commercetools, March 2026): product variants + attributes + categories microservices, grouped together, form a Product Catalog PBC.

Example (Elastic Path, January 2026): a "Customer & Account Management" PBC bundles microservices for customer management, role-based access control, address book management, and account hierarchy configurations.

Elastic Path published a 2020 post ("What is the difference between PBCs and Microservices?") that is widely cited across the industry. The January 2026 Elastic Path post covers the same topic with updated language and supersedes the 2020 version for definitional purposes. The 2020 post is retained as a historical reference — it is the source for the Gartner 30%-by-2024 prediction cited in 2020.

PBCs in the MACH / composable architecture context

The MACH Architecture is the technical certification framework most closely associated with PBCs. Per the MACH Alliance MACH Maturity Whitepaper (July 2023):

"Businesses can integrate a collection of flexible cloud native technologies using an ecosystem of independent components that deliver packaged business capabilities."

In 2026, the MACH Alliance rebranded its guiding principles away from the M-A-C-H acronym toward three meta-principles — Open, Composable, Connected — with the "Composable" principle implicitly encompassing PBC-style independent deployability. (machalliance.org, 2026)

Gartner's 2025 Digital Experience Platform (DXP) Magic Quadrant added composability as a mandatory evaluation criterion for the first time, defining it as: "A composable architecture for modular and API-first approaches, with a set (or sets) of discrete, task-oriented and independently deployable packaged business capabilities (PBCs)." (MACH Alliance analysis of Gartner 2025 DXP MQ, February 2025)

Gartner also predicted: "By 2026, at least 70% of organisations will be mandated to acquire composable DXP technology, as opposed to monolithic DXP suites, compared to 50% in 2023." (as-of February 2025)

Benchmarks and adoption statistics

The following figures are from MACH Alliance survey data (2024 or earlier) and Gartner predictions made in 2020. Treat as directional only.

92% of US brands have adopted some form of composable commerce, with an additional 21% planning implementation. (as-of 2024 — MACH Alliance survey; source date may be 2023 survey published in 2024)
80% of ecommerce leaders plan to move toward composable architecture, but only 42% have achieved full implementation. (as-of 2024)
Gartner predicted 30% of digital commerce organisations would use PBCs to construct application experiences by 2024. (as-of 2020 — prediction now past; actual outcome not confirmed)
Organisations using composable architecture are 6x more likely to achieve clear AI ROI (78% vs 13%). (as-of 2026 — MACH Alliance Enterprise Technology Report 2026, n=600 decision-makers, 7 global markets)
94% of composable-mature organisations say composable architecture increases the speed of AI deployment. (as-of 2026 — MACH Alliance ETR 2026)
98% of composable-mature organisations can support AI at scale. (as-of 2026 — MACH Alliance ETR 2026)
Klizer / Gartner (via secondary source): organisations using a composable approach can launch new features approximately 80% faster than competitors. (as-of mid-2025; original Gartner source date unclear — treat as directional)

Adoption speed claims

Klizer/Gartner (secondary): composable organisations launch features ~80% faster than competitors.
CMS Critic / Umbraco CTO Filip Bech-Larsen (November 2025): in many composable implementations, engineering backlogs multiplied and marketing teams waited weeks for content changes. The speed claim appears to be a theoretical ceiling for mature implementations; actual outcomes vary significantly by implementation maturity and team capacity.

Vendor landscape

Vendor	PBC positioning	Notes
Elastic Path	PBC-first; modular catalogue, pricing, promotions, subscriptions	Jan 2026 blog is current authoritative statement
Spryker	PBC-first; B2B/enterprise focus	Explicit about PBC grouping model
commercetools	Microservices/MACH foundation; PBC framing applied to grouped capabilities	Dirk Hoerig coined "headless commerce"; Kelly Goetsch key PBC architect
VTEX	Full-platform SaaS with built-in OMS and marketplace; "pragmatic composability"	MACH member but founder publicly critical of pure-MACH in 2023–2025; exited MACH Alliance March 2025
SAP Commerce Cloud	Uses "PBC" narrowly for its own released SaaS components	e.g. SAP Open Payment Framework, SAP Search Service — proprietary label, not vendor-neutral
Shopify	Composable as option for large digitally-mature enterprises only	Recommends "blended approach" (composable front end + full-stack back end)
HCL Commerce	PBC-defined catalogue, inventory, pricing, promotions, search	Positions each as independently scalable
Contentful / Contentstack / Storyblok	CMS/DXP vendors positioned as PBCs within a broader composable stack	Contentful does not use "PBC" terminology explicitly in its docs
Umbraco	Open-source CMS; building SaaS GraphQL orchestration layer to reduce PBC integration overhead	Addresses "composable regret" directly

SAP's use of "PBC" vs the broader industry Gartner, commercetools, Elastic Path, and Shopify use "PBC" as a vendor-neutral architectural pattern for any modular business capability. SAP applies "PBC" specifically to label its own discrete cloud SaaS service releases (Open Payment Framework, Search Service) — a narrower, product-catalogue sense rather than a general design concept. (SAP Community blog, December 2024; Gartner 2020; commercetools March 2026)

Retailer and brand adoption examples

Bang & Olufsen — composable stack (Contentful + commercetools): +60% conversion rate, +27% average order value. (as-of November 2024 — Contentful case study)
Ace & Tate — composable stack: launched 30+ campaigns in eight months across 11 markets and 5 locales. (as-of November 2024 — Contentful case study)
ALDO Group (1,500+ stores, 100+ countries) — composable best-of-breed: unified content, orders, delivery, and in-store functions; real-time inventory, demand forecasting, personalised marketing. (as-of undated — SAP case study)
PetSmart — commercetools composable: boosted conversions. (September 2025 — commercetools YouTube)
The Vitamin Shoppe — commercetools composable: accelerated speed to market. (August 2025 — commercetools YouTube)
Viridor (UK waste management) — composable Umbraco platform: saved £80,000/year in licence costs, +18% engagement, +3% conversions, 40% lower CO₂ than average. Delivered in 3 months. (as-of November 2025 — CMS Critic / Umbraco CTO article)
Moncler, Sweaty Betty, Iceland — composable on Salesforce Commerce Cloud (not MACH-certified): positive reported outcomes. (as-of November 2025 — 64labs agency article)
Whirlpool — VTEX "pragmatic composability." (date unknown — VTEX YouTube)
Jollyes (UK pet supply) — composable platform with advanced inventory management and CRM integration. (September 2025 — Klizer, updated March 2026)
Ted Baker — composable with multi-currency/multi-lingual support. (September 2025 — Klizer, updated March 2026)

What practitioners report: the composable regret debate

From 2023 onwards, a significant practitioner counter-narrative has emerged around the operational costs of pure best-of-breed PBC stacks. Key themes:

Integration tax Each new PBC vendor added to a stack creates UI re-integration work, data duplication risk, SLA negotiation overhead, and organisational knowledge fragility. Practical Ecommerce (October 2020) named this the "UI tax" — a recurring cost that most PBC marketing glosses over.

Composable Regret CMS Critic / Umbraco CTO Filip Bech-Larsen (November 2025) documented the pattern: organisations became de facto system integrators, stitching APIs together and debugging data flows. Engineering backlogs multiplied; marketing teams waited weeks for content changes. Root causes: IT teams led the composable conversation without CFO/marketing buy-in; misaligned expectations followed.

VTEX MACH Alliance exit (March 2025) VTEX co-CEO Mariano Gomide de Faria suspended MACH Alliance support, calling the movement a path "paved with hidden costs, operational nightmares, unfulfilled promises, and financial ruin." Specific critique: integration complexity, surging licencing and maintenance costs, fragmented multi-vendor UIs, data duplication creating security/compliance risk. (Retail Tech Innovation Hub, March 2025)

API-first as a requirement for composability

MACH Alliance: "Connected" (API-first, real-time, interoperable) is one of the three non-negotiable principles of composable architecture.
VTEX (2020): "If your solution isn't API-first, that does not necessarily mean you can't compose." VTEX offers a CMS composable without a fully API-first backend. Sources: MACH Alliance principles page (2026); VTEX blog post (October 2020).

Forrester data (2023) A third of digital businesses would abandon or restructure composable commerce projects due to complexity or maintenance. (Forrester 2023 Predictions, cited in VTEX TechCrunch op-ed November 2023)

Forrester 2023 Predictions (cited via VTEX TechCrunch op-ed, November 2023). The 1/3 abandonment figure is 2+ years old. No updated Forrester figure available without paywall access. The trend of composable regret continued into 2025 per multiple sources but the exact proportion is unconfirmed.

Pragmatic composability The working answer that has emerged in the practitioner community (2023–2026): use platform-native (pre-integrated) PBCs as the base layer; compose best-of-breed PBCs only where they provide clear competitive differentiation and where the team has the capacity to maintain them.

VTEX TechCrunch op-ed (November 2023) claims a VTEX-commissioned Forrester TEI study found enterprise companies can save up to $5.8M by mixing native/pre-integrated PBCs with selective best-of-breed extensions versus full best-of-breed stacks. (as-of 2023; vendor-commissioned study — treat with caution)
Shopify (February 2024): 45% of 1,000+ surveyed enterprises (IDC study) use a composable front end with a full-stack back end — Shopify calls this optimal.

Who composable is appropriate for

SAP (undated): composable is better suited to "larger organisations aiming for high growth" — not SMEs.
Shopify (February 2024): not right for most businesses unless "digitally mature with experienced engineering teams and complex delivery requirements."
MACH Alliance: frames composable as broadly desirable strategic direction for enterprise, calling it "recession-resilient IT." These reflect vendor positioning differences as much as factual disagreement.

PBC sizing guidelines

From Elastic Path (January 2026):

"A PBC should be recognizable to a business user as a standalone capability (e.g., 'Catalog' or 'Pricing'), large enough to provide meaningful value, small enough to be independently replaced or enhanced. If a PBC is too small, it becomes meaningless to the business. If it's too large, it risks unnecessary complexity."

On monolith-as-PBC: "Can a Monolith Be a PBC? Yes, if the monolith offers a focused, complete capability that is always consumed as a whole. For example, a standalone payment gateway with APIs can qualify as a PBC." (Elastic Path, January 2026)

Risk of over-scoping: PBCs can become "little monoliths" if scoped too broadly — e.g. baking tax logic inside a Payments PBC creates future lock-in. (Elastic Path, citing the Gartner original, September 2020)

Key people

Dirk Hoerig — commercetools CEO; coined the term "headless commerce" in the early 2010s; architect of the broader composable/MACH movement.
Kelly Goetsch — CSO at commercetools; widely cited as a primary populariser of PBCs as an architectural concept; YouTube interview available (April 2024).
Mariano Gomide de Faria — VTEX Co-CEO; authored "pragmatic composability" as a counter-framework; led VTEX's exit from the MACH Alliance (March 2025).
Filip Bech-Larsen — CTO at Umbraco; authored the "combatting composable regret" analysis (November 2025).
Casper Aagaard Rasmussen — MACH Alliance President; defended MACH principles in response to VTEX exit (March 2025).

Next frontier concepts (dangling links)

Composable Regret — 11 inbound refs; no dedicated page; the practitioner backlash pattern documented from 2023–2025
VTEX — 9 inbound refs; no entity page; critical voice in the composable debate; exited MACH Alliance March 2025
Strangler Pattern — migration methodology for moving from monolith to composable/PBC; referenced across vault
Digital Experience Platform (DXP) — Gartner 2025 MQ context; composability now mandatory criterion
Atama — orchestration layer vendor; Atama Composer manages PBCs for business users without developer involvement