Composable commerce for retailers in 2026
Bring separate commerce services together without losing the shopping journey. Learn where a DXP fits and who owns catalogue, checkout and support data.
- Published
- Last updated
Composable commerce connects independently selected commerce services so a retailer can replace one capability while keeping the rest of the shopping journey working. You might change search while retaining your catalogue and checkout. The benefit depends on clear service boundaries and a team that can maintain the connections.
What makes commerce composable
Commerce is composable when its capabilities have defined interfaces and can change independently. An application programming interface (API) describes how another service requests information or performs an action. Shared product identifiers let separate services recognise the same item.
The MACH Alliance’s architecture principles describe composable capabilities as independently deployable units. In retail, that means assessing what you can release or replace without rebuilding unrelated services. A vendor’s modular product names alone don’t establish that independence.
Headless commerce separates the customer-facing storefront from the commerce backend. A headless store can still rely on one backend for every commerce function. Composable commerce extends the selection decision across capabilities such as search and checkout. Read about headless ecommerce when the main change you need is a separate storefront.
Consider these two cases. A retailer can replace its search service through a documented interface while keeping basket operations intact. That is a composable boundary. Another store adds several apps whose data remains tied to one platform’s private model. The number of apps alone doesn’t make those capabilities independently replaceable.
Where the DXP and product services fit
A digital experience platform (DXP) manages customer-facing experiences, often combining content delivery with personalisation and other experience tools. Its exact scope depends on the product. A DXP can arrange what shoppers see while separate commerce services decide what they can buy.
For a hypothetical retailer, assign each fact an owner before connecting the services. Product information management (PIM) holds approved product descriptions and attributes. Search holds an indexed copy for discovery. Neither a search result nor an editorial page can independently authorise a purchase.
| Retail fact or action | Authoritative owner in this example | What other services consume |
|---|---|---|
| Material and dimensions | PIM | Published attributes with product and variant identifiers |
| Buying guides and policy wording | Content service within the DXP | Approved content and its version |
| Search relevance | Search service | Indexed product records and filters |
| Customer-specific price | Commerce pricing service | Price for the customer, currency and channel |
| Available quantity | Inventory service | Availability for the fulfilment location |
| Basket and order | Commerce service | Accepted basket changes and confirmed order state |
These are design choices for the example, not mandatory product boundaries. One platform can own several rows. The team still needs to state which source wins when copies disagree.
For example, a DXP page that manually repeats a product’s dimensions becomes stale when the PIM changes. Store the product identifier in the page and retrieve the approved dimensions. Keep editorial advice separate from transactional facts such as the current selling price.
Follow one product from update to purchase
A product update must reach every service that uses that fact, while buying decisions still return to the owning service. Consider a hypothetical outdoor retailer using Adobe Experience Manager for content and commercetools for commerce, with a separate search service.
Adobe documents Content Fragments delivered through GraphQL, a query interface through which applications request selected content fields. That content interface lets the retailer change its presentation independently of commerce. Replacing the content service still requires mapping its content models and rebuilding affected connections.
The commercetools Product Projections API supplies customer-facing product data with store and locale context. The example uses that published representation to connect product records across the journey.
- A merchandiser corrects a tent’s packed weight in the PIM. The integration updates the commerce product and publishes the approved change. Search refreshes its indexed record. The content page retrieves the same product’s published attributes.
- A warehouse reports that the last tent has sold. The inventory owner updates availability for that fulfilment location. Search receives the change, but checkout still applies its configured inventory rules when the next customer tries to buy.
- A customer asks the assistant to compare that tent with a lighter model. Search finds candidates. The assistant retrieves their approved attributes and checks the relevant price and availability before proposing a basket change.
- The commerce service accepts the selected variant and quantity into the basket. Payment and order confirmation use that basket’s accepted state. A conversational recommendation alone is never proof that stock is reserved or an order exists.
Write a data contract for each connection. Specify identifiers, units and required fields. Define how deletions travel, which version wins and what a receiving service does with an unfamiliar field.
Set an acceptable update delay for each fact and measure it. The commercetools subscription interface can notify a message queue when resources change. Your integration must still process those notifications and recover missed or failed updates.
Give each connection only the permissions it needs. commercetools documents OAuth 2.0 authorisation with access scopes. Product-reading permissions must stay separate from privileged order-management access, and customer-specific requests need the correct customer context.
Agree on failure behaviour before launch. If content delivery fails, a product page can retain approved cached editorial text. If a current price or inventory check fails, show that the purchase can’t proceed yet. Don’t substitute an old conversational answer for the missing transaction check.
Keep shopping assistance aligned with checkout
Shopping assistance needs the same product identities and selling context as checkout, plus the retailer’s approved policies. A customer comparing two sizes must reach the exact variants discussed when they add one to their basket.
Supply the assistant with published catalogue attributes and approved delivery, returns and sizing documents. Identify which policy applies to the store or channel. Keep customer-specific prices and account permissions in authenticated commerce requests.
Ask the commerce service to validate the price and return the basket state after each accepted change. Validate availability under the store’s configured inventory rules. The commercetools cart documentation distinguishes retrieving a cart from recalculating its current prices and discounts. Its inventory behaviour also depends on the selected mode.
A useful acceptance case starts with a customer discussing a product, then changes its price before the customer buys. The basket must use the price accepted by commerce and explain any change before payment. A second case removes the selected variant from sale. The assistant must recover from the rejected action without claiming the item was purchased.
After payment, order support must retrieve the confirmed order through authorised access. A remembered order number or a previous chat message does not establish the customer’s right to view order details.
Account for the work between services
Composable commerce costs include the connections and their ongoing operation as well as the service subscriptions. Replacing a vendor changes both its fee and the work needed to keep the journey intact.
Budget for integration development, data mapping and test environments. Add monitoring for failed requests and delayed updates. Include incident response, security maintenance and release coordination across vendors. Assign a named team to each connection and one incident owner for the whole shopping journey.
During a checkout incident, that owner needs to distinguish a payment failure from a stale basket or unavailable inventory service. Separate vendor status pages won’t identify every broken connection between otherwise healthy services.
Choose a more integrated platform when its built-in functions meet your requirements and your team cannot justify maintaining separate services. Composable commerce gives you more selection control, with additional operating responsibility. Neither architecture automatically produces a faster site, lower costs or higher conversion.
Evaluate replacement difficulty before signing. Ask how you export product identifiers and customer-owned data, and which custom connections must change. A documented API reduces uncertainty about access. It doesn’t remove the work of migrating data and behaviour.
Introduce one replaceable capability at a time
Start with one capability whose replacement has a clear business reason, while retaining a working purchase path. A retailer struggling with product discovery can trial a new search service without also replacing checkout.
Keep the existing catalogue and commerce service authoritative. Feed published product records to the new search index, then route a controlled share of searches through it. Retain a way to return traffic to the previous search while you assess the results.
Before extending the architecture, complete these acceptance checks in an isolated test environment:
- Correct a product attribute and confirm that the product page, search results and assistant comparison use the approved value within the agreed delay.
- Remove a variant from sale and confirm that the basket rejects an unavailable purchase under the configured inventory rules.
- Complete a test payment and confirm that one accepted order appears with the correct products and totals. Replay a failed request to check that it doesn’t create a duplicate purchase.
- Sign in as the order’s customer and retrieve its status. Use a different customer account and confirm that the same private order details remain inaccessible.
- Interrupt the new search connection and confirm that shoppers can still reach the existing purchase path. Restore the connection and check that updates catch up.
Expand only after the retailer’s team can identify a failed connection and restore the journey. The next independently replaceable service must earn its operating cost by solving a specific retail requirement.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.