Inside the SAP CX Suite: Sub-Solutions, Extensions, and Architecture

The five SAP CX products — Sales Cloud V2, Service Cloud V2, Commerce Cloud, Emarsys, and CDP — each contain multiple sub-solutions and extension points. Understanding this architecture helps you scope implementations accurately and avoid over-customisation.

This guide goes beneath the product-level overview into the sub-components, extension models, and integration architecture that define how SAP CX actually works.

TL;DR: Sixty-seven per cent of SAP’s Q4 2025 cloud orders included business AI, up over 20 points from Q3 (CX Today, 2026). Each SAP CX product contains multiple sub-solutions: Sales Cloud V2 includes pipeline management, intelligent forecasting, and Joule AI; Commerce Cloud includes the Composable Storefront, Intelligent Selling Services, and order management; Service Cloud V2 includes case management, knowledge base, and multi-channel routing. All extensions follow the Clean Core principle — built on BTP, connected through APIs.

What Sub-Solutions Does Sales Cloud V2 Include?

SAP Joule copilot adoption grew ninefold over 2025 (CX Today, 2026). AI capabilities are embedded throughout the Sales Cloud V2 sub-solutions.

Pipeline management. Leads, opportunities, and deals tracked through configurable stages. Each stage can have required fields, automatic notifications, and approval workflows. Weighted pipeline gives managers real-time revenue forecasting.

Intelligent forecasting. AI-assisted predictions that go beyond simple weighted pipeline. Joule analyses deal patterns, activity levels, and historical win rates to flag at-risk deals and surface opportunities likely to close.

Territory and account management. Hierarchical territory assignment with automatic account routing. Supports geographic, industry, and named-account territory models. Account 360 provides a complete view of every interaction.

Activity management and Joule AI. Calls, emails, meetings, and tasks linked to accounts and opportunities. Joule recommends next actions, summarises account interactions, and drafts follow-up communications.

Analytics and reporting. Embedded analytics dashboards for pipeline health, win rates, activity metrics, and forecast accuracy. Configurable without custom development.

What Sub-Solutions Does Service Cloud V2 Include?

Only 48% of digital initiatives meet their targets (Gartner, 2024). Service quality is one of the most controllable factors in customer retention.

Case management. The core module — create, categorise, route, escalate, and resolve cases. Supports custom case types, SLA timers, and automatic escalation rules. Cases can be created manually, via email, chat, or API.

Multi-channel communication. Unified inbox that combines email, phone, chat, and portal interactions into a single agent view. Agents switch between channels without losing context.

Knowledge base. Searchable article repository that serves both agents (internal knowledge) and customers (self-service portal). Articles can be linked to case categories for automatic suggestions.

Customer self-service portal. Web-based portal where customers create tickets, check status, browse knowledge articles, and manage their own account details. Reduces case volume by deflecting common questions.

Intelligent routing. Assign cases based on agent skills, workload, customer tier, or case category. Ensures the right agent handles each case without manual assignment.

What Sub-Solutions Does Commerce Cloud Include?

SAP Commerce Cloud delivered $17.8 billion GMV during Cyber Week 2025, a 40% year-over-year increase, with 100% uptime (SAP Community, 2025). The platform handles massive scale through specialised sub-solutions.

Composable Storefront. Angular-based decoupled frontend that replaces the legacy Accelerator approach. Enables modern web development practices — component-based architecture, lazy loading, and server-side rendering.

Product content management. Catalogue management for products, categories, variants, bundles, and configurable products. Supports multi-language, multi-currency, and customer-specific catalogues.

Intelligent Selling Services (ISS). AI-powered recommendations, adaptive search, and personalised merchandising. Analyses browsing behaviour and purchase history to surface relevant products.

Order management. Full order lifecycle — from cart to fulfilment to returns. Supports split orders, backorders, multiple fulfilment sources, and real-time inventory checks against ERP.

B2B accelerator. Pre-built functionality for B2B commerce: organisation hierarchies, buyer roles, approval workflows, requisition lists, and customer-specific pricing.

How Does the Extension Architecture Work?

BTP adoption reached 55% among ASUG members; 73% of BTP users use it for S/4HANA transformation (Precisely, 2026). The same extension model applies to CX products.

Every SAP CX product follows the Clean Core principle: keep the core product standard, build extensions next to it. This means:

Side-by-side extensions built with SAP CAP (Cloud Application Programming model) on BTP. Your custom business logic runs in a separate service that communicates with CX products through REST APIs and Event Mesh.

No code inside the core. SAP updates the core on their schedule. Your extensions keep working because they depend on stable API contracts, not internal implementation details.

Standard technology stack. Node.js or Java. OData and REST. CDS for data modelling. No proprietary lock-in beyond SAP’s API contracts.

This architecture means upgrades that used to take months (because custom code broke) now take days (because extensions are external). It also means you can build in any language that can call a REST API — though CAP is the recommended choice for SAP connectivity.

FAQ

Can I implement just one sub-solution within a product?

In most cases, the sub-solutions within a product are included together — you don’t license pipeline management separately from territory management in Sales Cloud V2. However, you can scope your implementation to configure only the sub-solutions you need and add others later.

How complex is the BTP extension model?

It depends on what you’re building. Simple extensions (adding fields, custom validation rules, notification triggers) take 1-2 weeks. Complex extensions (custom workflows, third-party integrations, custom UIs) take 4-8 weeks. The learning curve for SAP CAP is moderate — experienced Node.js or Java developers typically become productive within 2-3 weeks.

Do I need BTP for every SAP CX implementation?

Not every implementation needs custom BTP extensions. Standard Sales Cloud V2 or Service Cloud V2 implementations may work with configuration alone. But any project that requires custom business logic, non-standard integrations, or specialised workflows will need BTP. In practice, that’s most projects beyond the simplest scope.

What’s the difference between the Accelerator and Composable Storefront?

The Accelerator is Commerce Cloud’s legacy server-side-rendered frontend. The Composable Storefront (formerly Spartacus) is the modern Angular-based decoupled frontend. New implementations should use the Composable Storefront. Existing Accelerator-based storefronts should plan a migration — SAP’s investment is focused on the Composable approach.

How do Emarsys and CDP differ?

Emarsys is for execution — running campaigns, automating workflows, sending communications. CDP is for data — unifying profiles, managing consent, resolving identities. Emarsys uses CDP data to personalise campaigns, but CDP serves all five products (not just marketing).