Across the CPG and consumer goods industry, SAP S/4HANA migrations are in full swing. Roughly one-third of companies are currently transitioning to the new ERP environment. The trigger is IT-driven: simplify the landscape, reduce technical debt, and modernize infrastructure. But what many underestimate is that an ERP migration is not just a system change. It is a rare opportunity to fundamentally redesign the commercial backbone of the business.
When systems converge, complexity surfaces
As multiple legacy systems are consolidated into a single global template, inconsistencies inevitably become visible. Condition types that were created years ago for specific local agreements resurface. Pricing procedures differ widely by country. Trade term structures reflect historical negotiations rather than a coherent global logic. TPM and TPO tools are configured differently, preventing consistent cross-market reporting.
For years, local flexibility has enabled commercial teams to respond to customers. But over time, this flexibility has often turned into fragmentation. Trade spend definitions vary across markets. Net price levels are difficult to compare. Manual workarounds are embedded in pricing cascades. Central steering becomes limited, not because of strategy, but because of structural inconsistency.
If companies simply migrate these structures into S/4HANA, they do not solve the problem. Even more, they risk hard-coding legacy complexity into a new system for the next decade.
The risk of a “lift-and-shift” migration
Under timeline pressure, many organizations opt to replicate existing pricing logic in the new ERP environment. The objective is stability. They want to avoid invoice disruption, protect customer relationships, and minimize risk.
The consequence is predictable. Cascading pricing procedures remain overly complex. Unconditional discounts continue to dominate the gross-to-net waterfall. Local exceptions become part of the global template. Trade spend comparability remains limited.
Operationally, the burden persists. Order-to-cash processes remain manual and error-prone. Invoice corrections and price claims continue. Finance teams spend significant time reconciling accruals. Meanwhile, leadership still lacks transparency on true net price realization and investment effectiveness.
The infrastructure is modernized, but the commercial engine remains unchanged.
Why timing matters now
S/4HANA migration creates a unique external window. Because many suppliers are modernizing simultaneously, customers are generally more receptive to structural adjustments. Changes in nomenclature, trade term logic, or invoicing formats can be positioned as part of a broader system transition rather than unilateral commercial tightening.
This matters. Under normal circumstances, renegotiating trade term structures or standardizing discount logic can be politically sensitive. During a system transformation, the same changes can be framed as simplification and alignment.
Companies that recognize this dynamic can use the moment to align internal system design with external commercial agreements.
The tangible upside of commercial harmonization
When ERP migration is used as a trigger to redesign commercial structures, it unlocks several benefits:
IT system cost rationalization
This is the most obvious direct benefit of system harmonization. Harmonizing ERP, TPM, TPO, and RGM analytics systems into a centralized configuration reduces redundancy across markets. Standardizing country-by-country configurations into one global template can reduce operating expenses by 20–30%.
Simplified and centralized order-to-cash
A harmonized pricing procedure unlocks a centralized order-to-cash process. It can lead to savings up to 25% in order management and billing process costs. Improved invoice clarity reduces disputes and accelerates time-to-cash, strengthening working capital performance.
Margin leakage reduction
Organizations gain full transparency over trade spend. What was previously hidden in local agreements and system variations becomes visible at a consolidated level. Businesses can clearly identify and manage margin leakage driven by unconditional discounts rather than accepting them as a structural given.
In Europe, a harmonized trade term structure can expose and mitigate trade term risk across retailers within one buying group. The value at stake of reducing trade spend leakage is generally 1-3% of total trade spend.
Fewer price claims and back-office workload
Eliminating commercial exceptions that have accumulated over the years, harmonizing pricing procedures, and simplifying pricing cascades will reduce manual work (5-10% reduction in finance workload related to trade spend), reduce errors, minimize price claims up to 30% improvement, and reduce DSO with 1-3 days due to accrual accuracy and faster rebate settlement.
How to capture the opportunity: Five focused workstreams
To translate ERP migration into commercial value, organizations typically structure the effort around five focused workstreams:
1. Redesign the global price architecture
Before configuring SAP, define the future gross-to-net logic. Simplify discount layers, clarify rebate logic, standardize condition types, and remove historical workarounds.
2. Align trade term structures with system logic
Commercial policy must be consistently translated into system configuration. Governance mechanisms should define how conditions are introduced, approved, and monitored. Without alignment, ERP merely digitizes inconsistency.
3. Safeguard net neutrality and prevent invoice fallout
Protect margins during transition through invoice simulations, contract validation, and margin impact assessments. Maintaining invoice accuracy to the second decimal avoids price claims and protects customer relationships.
4. Execute in waves
Structured wave-based deployment reduces risk and improves learning. Early markets generate insights that strengthen later rollouts. This phased approach ensures high quality of execution and builds capabilities along the way.
5. Use the migration to reset external agreements
Leverage the transition to onboard customers onto harmonized trade terms, updated nomenclature, and standardized invoicing structures. This workstream converts internal harmonization into external commercial impact.
Where transformations often fall short
Many S/4HANA migration programs struggle not because of technical challenges, but because commercial decisions are postponed. Pricing leaders are insufficiently embedded in governance structures. Data clean-up starts too late. Local exceptions are preserved to avoid disruption. Change management is treated as communication rather than capability building.
The result is a modern platform running legacy complexity.
Once embedded into the new system, these structures are significantly harder to change. The next realistic window for structural redesign may not come for another decade.
The real strategic question
Every S/4HANA migration modernizes infrastructure. The strategic question is whether it also modernizes the commercial model.
Organizations that act deliberately can use this market-wide transformation moment to reset trade terms, standardize pricing procedures, and embed structural discipline into their revenue model.
Those who treat migration purely as a technical upgrade will stabilize infrastructure. Those who use it to redesign price architecture and commercial governance will unlock sustainable commercial improvement.
Please reach out if you’d like support in translating these insights into concrete next steps for commercialization.
