Enterprise & product foundation
SAP S/4HANA
- Materials
- Business partners
- Characteristics & classes
- Condition records
- Availability & plant data
- Features > Integrations > SAP S/4HANA CPQ
Mercura CPQ + SAP S/4HANA
CPQ for SAP S/4HANA
Turn SAP product and variant data into a guided, visual buying journey — then return an approved, traceable configuration to your SAP sales process.
Mercura complements S/4HANA, including landscapes that use LO-VC or Advanced Variant Configuration, by adding the sales UX, quote automation and channel flexibility complex manufacturers need.
- Cloud or on-premise discovery
- Works with your configuration strategy
- SAP remains the operational backbone
SAP S/4HANA Example output
Sales quotation
- Customer
- Nordic Manufacturing
- Configured item
- Industrial system
- Status
- Validated
- Handoff
- Order-ready
The 30-second answer
What is CPQ for SAP S/4HANA?
It is the commercial layer between customer requirements and an executable SAP sales order. Mercura gives sellers, dealers and customers a guided interface for complex configuration, pricing and proposals while S/4HANA continues to manage the enterprise processes, master data and order execution.
System responsibility
Respect the SAP core. Design the experience around the buyer.
The target architecture depends on where configuration and pricing logic lives today. Mercura can orchestrate a sales experience around SAP-owned data, Mercura-owned rules or a deliberate hybrid.
→context
M
Configure · Price · Quote
Mercura
- Guided discovery
- Visual configuration
- Channel-specific UX
- Commercial calculations
- Proposal automation
→approved result
Quote-to-production execution
SAP S/4HANA
- Sales quotation / order
- Configured line items
- Characteristic values
- Pricing result
- BOM / routing outcome
SAP Sales Order API documentation →
Do we replace SAP variant configuration?
Not by default. Mercura can complement AVC or LO-VC, or own selected configuration logic when that is the better architecture.
Can SAP still calculate the final price?
Yes. Pricing can stay in SAP, be split by responsibility or be calculated in Mercura for configuration-specific logic.
Can this serve dealers and customers?
Yes. Mercura separates the sales experience from ERP screens while keeping the resulting order data governed.
Build vs. extend
SAP AVC, SAP CPQ or Mercura? Start with responsibility, not product names.
SAP Advanced Variant Configuration is a strong engine for configurable product models across sales, planning, production and engineering. Mercura focuses on turning that complexity into a high-conversion sales experience.
SAP S/4HANA + AVC / LO-VC
Strong at
- ✓Enterprise product and variant models
- ✓BOM and routing integration
- ✓Production-relevant configuration
- ✓SAP-native process consistency
Typical sales-experience gap
- —Bespoke dealer and customer journeys
- —Rich product visualization
- —Fast experimentation with sales UX
- —Cross-system quote and document experiences
M
S/4HANA + Mercura
Adds
- ◆Guided needs discovery
- ◆Role- and channel-specific interfaces
- ◆Real-time 2D/3D feedback
- ◆Commercial proposals built around the configuration
Use SAP for the responsibilities SAP should own. Use Mercura where the buying and selling experience must become simpler than the underlying product model.
Platform decision
Mercura, SAP CPQ or AVC: which responsibility belongs where?
These products overlap at the edges, but they solve different center-of-gravity problems. A defensible architecture makes that split explicit.
| Decision criterion | SAP AVC / LO-VC | SAP CPQ | Mercura |
|---|---|---|---|
| Production-relevant variant model | Primary fit | Consumes or complements | Consumes or complements |
| SAP-suite quote lifecycle | Not the focus | Primary fit | Integrates by design |
| Bespoke visual product journey | Not the focus | Possible | Primary fit |
| Dealer or customer self-service UX | Not the focus | Supported | Primary fit |
| Cross-system product logic | SAP-centered | SAP-suite centered | Flexible orchestration |
| 2D/3D configuration feedback | Requires experience layer | Project-dependent | Native experience focus |
Our view
Choose SAP CPQ when a standardized SAP-suite quote process is the dominant requirement. Choose Mercura when a differentiated, visual sales experience and flexible product logic are the dominant requirements. Keep AVC or LO-VC authoritative where the configuration drives production.
Mercura product experience
Give every buyer a configuration experience that feels purpose-built
Mercura can power an internal sales tool, dealer portal or customer-facing configurator. The interface carries your brand; the configuration model keeps every choice valid; SAP remains the operational system behind the sale.
- ✓Guided questions instead of ERP fields
- ✓Live 2D or 3D product feedback
- ✓Configuration-aware pricing and quote documents
- ✓One product model across direct, dealer and self-service sales
Shown: a live Mercura-powered configurator. This demonstrates the buyer experience, not a claim that this customer uses the SAP S/4HANA integration.
From configuration to commitment
A quote your customer can understand. Data your ERP can execute.
Use the same structured configuration to create branded proposal documents with product descriptions, options, technical values, quantities and commercial terms — then map the approved result to SAP S/4HANA.
Landscape qualification
What we validate in your SAP S/4HANA landscape
Edition, release and configuration strategy materially change what is possible. The workshop establishes these facts before anyone promises an interface.
- Edition & release
- Public cloud, private cloud or on-premise, plus the exact release and released API scope
- Configuration model
- AVC or LO-VC, single- or multi-level models, knowledge bases and ownership of constraints
- Pricing authority
- Condition technique, Variant Configuration and Pricing services, Mercura logic or a governed hybrid
- Integration layer
- SAP BTP Integration Suite, existing middleware, direct released APIs and event patterns
- Order handoff
- Quotation or sales order target, characteristic values, configurable materials and traceability
- Non-functional needs
- Identity, latency, availability, data residency, monitoring and exception ownership
Technical evaluation
A practical SAP S/4HANA CPQ data contract
The table below is a discovery framework, not a promise that every field belongs in every interface.
| Data | Direction | Typical integration | Decision to make |
|---|---|---|---|
| Materials | S/4HANA → Mercura | Released API / integration layer | Which products are sellable? |
| Customers | S/4HANA → Mercura | Business partner APIs | Which commercial context is needed? |
| Characteristics | S/4HANA ↔ Mercura | Variant configuration mapping | Which engine owns each rule? |
| Pricing inputs | S/4HANA → Mercura | Condition / simulation services | ERP price, CPQ price or hybrid? |
| Configuration | Mercura → S/4HANA | Order API + variant entities | How is traceability preserved? |
| Sales order | Mercura → S/4HANA | Sales Order A2X API | Synchronous or asynchronous handoff? |
| Documents | Mercura → customer / archive | Document service / agreed repository | Which output is commercially binding? |
| Status & errors | S/4HANA → Mercura | API response / integration monitoring | Who owns exception resolution? |
SAP publishes Sales Order A2X APIs for external integrations, including OData V4 operations and variant-configuration entities. Availability and scope vary by S/4HANA edition and release, so architecture validation is part of discovery.
Delivery path
Make the first scope narrow enough to prove, rich enough to matter
A successful SAP CPQ program aligns product modeling, commercial ownership, integration and user experience before it scales globally.
- 01
Choose a representative product family
Select a product complex enough to test rules, pricing, documents and SAP output without becoming a transformation program.
Output: measurable pilot scope
- 02
Decide configuration ownership
Map what stays in AVC or LO-VC, what belongs in Mercura and where validation must cross the boundary.
Output: responsibility architecture
- 03
Design the integration contract
Confirm APIs, communication arrangements, master-data cadence, identity, errors and order payloads.
Output: testable interface specification
- 04
Launch one complete quote-to-order path
Validate with sales, product owners, SAP architects and operations before expanding products and channels.
Output: governed scale plan
Where it pays off
Use cases with enough complexity to justify CPQ
Complex machinery
Translate capacity, environment, performance and option requirements into valid configurations.
Buying signal: Sales depends on specialists to interpret customer requirements.
Global dealer networks
Offer market-, role- and channel-aware experiences while preserving a shared product model.
Buying signal: Each region has built its own spreadsheets or local tools.
Visual engineer-to-order
Combine configurable foundations with project-specific dimensions, calculations and proposal content.
Buying signal: The customer cannot understand the product from SAP characteristics alone.
Decision support
SAP S/4HANA CPQ questions, answered
Does SAP S/4HANA include CPQ?+
S/4HANA includes sophisticated product and variant configuration capabilities, especially AVC and LO-VC. A separate CPQ layer becomes relevant when you need guided selling, visualization, multi-channel sales experiences, commercial workflows or document automation beyond the ERP interaction.
Does Mercura replace SAP Advanced Variant Configuration?+
It does not have to. Mercura can act as a sales-facing layer around SAP-owned models, own selected product logic, or use a hybrid split. The right pattern depends on model maturity, performance, channel needs and production ownership.
Read SAP's AVC overview →Can Mercura create sales orders with variant configuration data?+
SAP's Sales Order APIs include structures for sales orders and variant-configuration data in supported releases. The exact create and update path must be verified against your S/4HANA edition, release and configuration model.
Does this work with S/4HANA Cloud and on-premise?+
Both can be evaluated, but connectivity, released APIs, authentication and extensibility differ. Discovery confirms the available interfaces and the appropriate integration layer for your landscape.
Where should pricing run?+
SAP can remain the pricing authority, Mercura can calculate configuration-specific pricing, or the two can share responsibility. The architecture should preserve one explainable commercial result.
How do you avoid creating a second product master?+
By defining ownership field by field, synchronizing only what the sales experience needs and preserving SAP identifiers throughout configuration, documents and order handoff.
Official technical resources
Technical content last reviewed 14 August 2026. Validate assumptions against your SAP edition and release.
Explore the capability stack
Go deeper on the parts of CPQ that matter
See it on your process
Turn your SAP landscape into a clear CPQ decision.
Bring one product model, one representative quote and your current SAP architecture. We will map responsibilities, interfaces and the smallest credible pilot.