Why CPQ Should Be Considered Before S/4HANA Go-Live

Most S/4HANA transformation projects start with finance, logistics, and procurement. Sales operations, and particularly quoting, tend to get pushed to a later phase. The logic seems reasonable at first: stabilize the core, then layer on the commercial tools. But this sequencing creates real problems, and CPQ before S/4HANA go-live is a conversation that many organizations wish they had started earlier. When the quoting layer is treated as an afterthought, the cost of catching up later is almost always higher than the cost of planning it right from the beginning.

Why the Timing of CPQ Decisions Matters More Than Most Teams Realize

S/4HANA transformations are not just system upgrades. They are process redesign exercises. Every major workflow in the business gets revisited: how orders flow, how pricing is structured, how master data is maintained, and how different departments exchange information. The quoting process sits at the intersection of nearly all of these areas. It touches product configuration, pricing logic, customer data, contract terms, and order creation. Leaving CPQ out of the conversation during this redesign means making decisions that will later conflict with how quoting actually needs to work.

This is not a minor inconvenience. When teams discover after go-live that their pricing models do not translate cleanly into the new ERP structure, or that their quote-to-order handoff requires manual workarounds, they face a second implementation effort under the worst possible conditions, with a live system, active customers, and a sales team that is already frustrated. Understanding the SAP CPQ and S/4HANA integration architecture before go-live is one of the most effective ways to avoid this outcome.

Process Design Decisions That Cannot Be Undone Easily

During an S/4HANA implementation, foundational decisions are made about how pricing conditions are structured, how the product and material master is organized, and how sales documents flow through the system. These decisions are not easy to reverse once the system is live and operational. If CPQ is introduced afterward, the integration team is forced to work around choices that were made without CPQ in mind, often resulting in custom workarounds, data duplication, or compromised functionality on both sides.

Consider how pricing logic works across the two systems. SAP CPQ handles complex, rules-based pricing at the quoting stage. S/4HANA manages pricing conditions at the order and billing stage. For this to work cleanly, the pricing architecture needs to be designed with both systems in mind from the start. When that alignment happens during the S/4HANA design phase, the integration is cleaner, more maintainable, and far less likely to produce errors at the handoff point.

Sales Readiness Is a Go-Live Risk That Gets Underestimated

Go-live planning tends to focus heavily on data migration, system testing, and cutover logistics. Sales readiness, meaning whether the sales team can actually quote accurately and efficiently on day one, often receives far less attention. This is a significant gap. A sales team that cannot generate quotes confidently after go-live is a business risk, not just an operational inconvenience.

If the quoting process is still running on spreadsheets, legacy tools, or manual email chains at the time of go-live, the S/4HANA implementation may stabilize the back office while leaving the front of the revenue process unchanged. That creates an awkward split: modern ERP behind the scenes, outdated quoting at the customer-facing layer. Planning CPQ as part of the broader transformation avoids this split and ensures that sales operations are upgraded alongside everything else. For teams dealing with complex products, guided selling in SAP CPQ can dramatically reduce the time it takes for reps to produce accurate quotes, which matters even more during the transition period when teams are adjusting to new systems.

What CPQ Before S/4HANA Go-Live Actually Looks Like in Practice

Bringing CPQ into the S/4HANA conversation early does not necessarily mean implementing both systems at exactly the same time. It means making sure that CPQ requirements are understood, documented, and factored into the design decisions being made during the S/4HANA project. This can take several forms depending on the organization’s size, complexity, and timeline.

• Running a CPQ discovery workshop alongside the S/4HANA design phase to capture quoting requirements before ERP decisions are locked in
• Aligning the product and pricing master data strategy across both systems from the start
• Designing the quote-to-order handoff as part of the S/4HANA order management workstream, not as a separate afterthought
• Including CPQ in the data migration plan so that legacy product configurations and pricing structures are mapped correctly
• Ensuring that approval workflows and discount authorization structures are consistent between CPQ and the broader S/4HANA environment

This kind of early alignment reduces integration complexity significantly. It also means that when CPQ goes live, whether simultaneously with S/4HANA or in a planned subsequent phase, the foundation is already in place. The alternative is discovering during CPQ implementation that critical ERP decisions need to be revisited, which is expensive and disruptive for everyone involved.

Quoting Complexity and Why It Needs Its Own Design Attention

One of the reasons CPQ tends to get deprioritized in S/4HANA projects is that quoting complexity is easy to underestimate. On the surface, quoting looks like a straightforward process: a sales rep selects products, applies pricing, and sends a document to the customer. In reality, the quoting process in most mid-to-large B2B organizations involves a layered set of rules, dependencies, and approvals that are genuinely complex to configure and maintain.

Quoting complexity typically includes some or all of the following:

• Product configuration rules that determine which combinations are valid
• Multi-tier pricing logic based on customer segment, volume, region, or contract type
• Discount approval workflows tied to margin thresholds
• Contract terms that vary by customer, geography, or deal type
• Output formatting requirements for different markets or customer types
• Renewal and subscription logic for recurring revenue models

This complexity does not disappear during an S/4HANA transformation, it needs to be mapped and designed carefully. Understanding the difference between variant configuration and CPQ rules is an important part of this design work, because the two approaches handle product complexity differently and the choice between them has downstream implications for how quoting and ordering interact within the SAP ecosystem.

The Hidden Costs of Delaying the CPQ Conversation

Organizations that defer CPQ planning until after S/4HANA go-live consistently encounter a predictable set of problems. These are not edge cases. They are the natural result of designing a system without accounting for how one of its most critical inputs, the sales quote, will actually be generated and managed.

The most common issues include:

• Integration rework, The quote-to-order connection requires changes to S/4HANA configuration that was not designed with CPQ in mind
• Pricing misalignment, Pricing logic in CPQ does not map cleanly to the condition structures in S/4HANA, requiring manual reconciliation
• Data migration complexity, Legacy quote and product data was not included in the original migration scope, creating a separate and often painful catch-up effort
• Sales disruption, The sales team continues using outdated tools while the CPQ implementation catches up, creating a dual-process environment that is difficult to manage
• Compliance gaps, Approval workflows and audit trails are not aligned between CPQ and the ERP, which creates risk in regulated industries

Each of these problems is solvable, but solving them after go-live is significantly more expensive than preventing them through early planning. The total cost of ownership of SAP CPQ over a multi-year horizon looks very different when the integration foundation is built correctly from the start versus when it is retrofitted after the fact.

Compliance and Audit Trail Alignment Across Systems

In many industries, the quoting process is subject to compliance requirements. Discount approvals need to be documented. Pricing decisions need to be traceable. Contract terms need to be auditable. When CPQ and S/4HANA are planned together, these requirements can be addressed coherently across both systems. When CPQ is added later, there is often a gap between what the ERP records and what the quoting system captures, which creates compliance risk that is difficult to resolve cleanly. Organizations operating in regulated environments should pay particular attention to how SAP CPQ handles compliance, audit trails, and regulatory requirements as part of their overall S/4HANA go-live planning.

How to Build CPQ Into Your S/4HANA Go-Live Planning

The practical question for most organizations is not whether to include CPQ in their S/4HANA planning, but how to do it without overcomplicating an already demanding transformation program. The answer is usually not to run a full CPQ implementation in parallel with S/4HANA from day one, but rather to ensure that CPQ is represented in the right conversations at the right time.

A structured approach to S/4HANA go-live planning that includes CPQ typically looks like this:

1. Include quoting process owners in the S/4HANA design workshops, Sales operations and commercial teams should be present when pricing, order management, and customer master decisions are being made
2. Document CPQ requirements before ERP design is finalized, Capture the quoting rules, pricing logic, and integration needs that CPQ will need to support
3. Align the data model across both systems, Product master data, pricing structures, and customer data should be designed to work in both CPQ and S/4HANA
4. Define the quote-to-order handoff clearly, Decide how quotes become orders, what data flows between systems, and where approval authority sits
5. Plan the CPQ implementation timeline relative to S/4HANA go-live, Whether CPQ goes live simultaneously or in a subsequent phase, the timeline should be intentional, not accidental

For organizations that are also dealing with legacy quoting data, the migration planning deserves its own workstream. Data migration to SAP CPQ, including products, attributes, and mappings, is a significant effort that benefits enormously from being scoped and planned alongside the broader S/4HANA data migration rather than treated as a separate project afterward.

It is also worth considering the sales team’s experience during and after the transition. The sales bottlenecks that CPQ is designed to eliminate are most effectively addressed when the tool is ready and aligned with the rest of the system landscape from go-live onward. A sales team that is already navigating a new ERP environment does not benefit from also having to manage an interim quoting process that will be replaced again in six months.

What This Means for Your Transformation Strategy

S/4HANA go-live planning is inherently complex, and no organization can prioritize everything at once. But CPQ is not a nice-to-have addition to an S/4HANA project, it is a core part of the commercial process that the ERP is meant to support. Treating it as optional during the design phase creates structural gaps that are expensive and disruptive to close after the fact.

The organizations that get this right are the ones that bring quoting into the conversation early, align their CPQ and ERP design decisions deliberately, and plan the integration as a first-class workstream rather than an afterthought. This does not require a larger budget or a longer timeline. It requires the right framing from the start, one that recognizes the quote-to-cash process as a unified flow, not a series of disconnected systems.

If your organization is currently in the planning or early design phase of an S/4HANA transformation, now is the right moment to bring CPQ into scope. The earlier that conversation happens, the more options you have, and the fewer expensive corrections you will need to make later. Solvetect’s SAP CPQ services are designed to support exactly this kind of early-stage alignment, helping organizations design their quoting process in a way that works with their S/4HANA environment from day one rather than against it.