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

Every overview of SAP CX stops at the product level. Five boxes, five labels. Done. But that’s not enough if you’re trying to scope an implementation or avoid over-customising things.

Each of those five products contains multiple sub-solutions and extension points. If you don’t know what’s inside each box, you’ll either build something that already exists or skip something you actually need. So let me break open the boxes.

TL;DR: 67% 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?

Joule copilot adoption grew ninefold over 2025 (CX Today, 2026). AI is embedded throughout these sub-solutions now. Here’s what’s actually inside Sales Cloud V2.

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

Intelligent forecasting. Goes beyond simple weighted pipeline. Joule analyses deal patterns, activity levels, historical win rates to flag at-risk deals and surface opportunities likely to close. I reckon this is where most sales teams have their first “wait, it can do that?” moment.

Territory and account management. Hierarchical territory assignment with automatic account routing. Geographic, industry, and named-account territory models. Account 360 shows every interaction in one place.

Activity management and Joule AI. Calls, emails, meetings, tasks linked to accounts and opportunities. Joule recommends next actions, summarises account interactions, drafts follow-up communications. The Activity Advisor is the most underestimated sub-solution in Sales Cloud V2. It doesn’t just track activities. It tells your reps what to do next based on deal patterns across the whole pipeline. That’s a different animal.

Analytics and reporting. Embedded dashboards for pipeline health, win rates, activity metrics, forecast accuracy. Configurable without custom development. Crisp and usable out of the box.

What Sub-Solutions Does Service Cloud V2 Include?

48% of digital initiatives meet their targets (Gartner, 2024). Service quality is one of the most controllable factors in keeping customers. Get it right, everything else follows.

Case management. The core module. Create, categorise, route, escalate, resolve cases. Custom case types, SLA timers, automatic escalation rules. Cases come in through email, chat, API, or manual creation.

Multi-channel communication. Unified inbox combining email, phone, chat, and portal interactions in a single agent view. Agents switch between channels without losing context. Sounds simple. Getting it right is harder than most vendors will admit.

Knowledge base. Searchable article repository for agents (internal knowledge) and customers (self-service portal). Articles link to case categories for automatic suggestions. Good knowledge base content deflects 20-30% of incoming cases.

Customer self-service portal. Web-based portal where customers create tickets, check status, browse articles, manage account details. Reduces case volume by deflecting common questions before they ever become tickets.

Intelligent routing. Cases assigned based on agent skills, workload, customer tier, or case category. Right agent, every time, without manual assignment. Proper routing alone can transform a service team’s throughput.

What Sub-Solutions Does Commerce Cloud Include?

$17.8 billion GMV during Cyber Week 2025. 40% year-over-year increase. 100% uptime (SAP Community, 2025). Numbers speak for themselves.

Composable Storefront. Angular-based decoupled frontend replacing the legacy Accelerator. Modern web development: component-based architecture, lazy loading, server-side rendering. If you’re still on the Accelerator, it’s time to plan the move. Seriously.

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

Intelligent Selling Services (ISS). AI-powered recommendations, adaptive search, personalised merchandising. Analyses browsing behaviour and purchase history to surface relevant products. Neat feature that pays for itself quickly in conversion rate improvements.

Order management. Full lifecycle from cart to fulfilment to returns. Split orders, backorders, multiple fulfilment sources, real-time inventory checks against ERP.

B2B accelerator. Pre-built B2B commerce functionality: organisation hierarchies, buyer roles, approval workflows, requisition lists, customer-specific pricing. This is where Commerce Cloud pulls away from the pack. Prima vista the B2B features look like nice-to-haves. In practice, they’re the whole reason B2B companies pick this platform.

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 standard, build extensions next to it. We’ve used SAP CAP on Cloud Foundry for every V2 project we’ve done. CDS data modelling, built-in authentication, Event Mesh integration. Fastest path to production-grade extensions we’ve found.

Side-by-side extensions built with SAP CAP on BTP. Your custom business logic runs in a separate service communicating with CX products through REST APIs and Event Mesh. Clean separation.

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. That’s the whole point of Clean Core and it actually works.

Standard technology stack. Node.js or Java. OData and REST. CDS for data modelling. No proprietary lock-in beyond SAP’s API contracts. De facto you can build in anything that calls a REST API, though CAP is the path of least resistance.

This architecture means upgrades that used to take months (because custom code broke) now take days (because extensions are external). That alone changes the economics of running SAP CX.

FAQ

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

The sub-solutions within a product come together. You don’t license pipeline management separately from territory management in Sales Cloud V2. But you can scope your implementation to configure only the pieces you need and add others later. We do this all the time. Start with pipeline and forecasting, add territory management in phase two.

How complex is the BTP extension model?

Depends what you’re building. Simple extensions (adding fields, custom validation, notification triggers): 1-2 weeks. Complex extensions (custom workflows, third-party integrations, custom UIs): 4-8 weeks. The SAP CAP learning curve is moderate. Experienced Node.js or Java developers typically get 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 can work with configuration alone. But anything requiring custom business logic, non-standard integrations, or specialised workflows will need BTP. In practice, that’s most projects beyond the simplest scope. I’d say 80% of what we deliver touches BTP.

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 Composable Storefront. Period. Existing Accelerator storefronts should plan a migration. SAP’s investment is going into the Composable approach. That’s where the momentum is.

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. Think of CDP as the foundation. Emarsys is one of the rooms built on top of it.