ERP transformation won’t improve commercial decision-making
CPG leaders shape commercial architecture during ERP transformation, whether they realise it or not.
Key Takeaways:
ERP is not the commercial decision layer
Modernising the transactional backbone does not, by itself, improve trade, pricing, or promotion decisions.
Architecture decisions cannot wait
ERP programmes shape data, integration, planning, and ownership, so commercial capabilities should be designed alongside the ERP.
The core misconception: ERP as a commercial performance solution
ERP transformation is one of the largest technology investments a CPG organisation will make. Across the industry, organisations are replacing legacy ERP platforms, modernising core business processes and redesigning enterprise operating models.
As organisations modernize their ERP landscape—including large-scale migrations to SAP S/4HANA—they are making architectural decisions about data, integration and planning processes that will shape how the business operates for years to come.
However, a persistent misconception surrounds these programs: that modernising the transactional backbone will, by extension, improve commercial performance.
In reality, it won’t.
ERP systems record transactions, manage financial processes and provide operational control. They are not designed to improve commercial decision-making. The quality of decisions made before transactions occur determines trade ROI, promotion effectiveness, and pricing performance —not the systems that record them. In other words, these are fundamentally different problems.
The gap between the two surfaces in consistent, observable patterns across CPG organisations mid-transformation:
- Teams continue to manage pricing decisions in spreadsheets, even during active promotional periods
- Trade promotion planning continues to rely on prior-year actuals with no upfront view of incremental volume or margin impact
- Trade ROI measurement remains a post-event activity — static reports produced weeks or months after execution closes, with limited ability to drive forward-looking action
The result is an uncomfortable realization: operational efficiency has improved, but commercial performance remains constrained by the same processes, assumptions and planning methods that existed before the transformation began.
Why sequencing is a false choice
The most common planning assumption encountered in CPG ERP programs is that revenue management modernization can follow ERP stabilization. It appears to reduce risk. It appears to simplify scope. In practice, it often does neither.
By the time ERP programs reach completion, foundational commercial architecture decisions have already been embedded:
- Data structures — how trade, pricing, and volume data are modelled and stored
- Integration patterns — how commercial planning tools connect to financial systems
- Planning processes — how cycles are designed around system capabilities
- Organisational ownership — how accountability is distributed across Sales, Finance, and RGM
Revisiting these decisions post-implementation is significantly more complex and expensive than designing them correctly from the outset. Organisations that defer commercial modernization do not avoid the decision. They make it by default, under worse conditions.
This is particularly relevant for organisations currently planning or executing large-scale ERP modernization programs, including migrations to SAP S/4HANA, where foundational architecture decisions are being made.
Three architectural paths and their trade-offs
CPG organisations navigating ERP transformation typically evaluate one of three approaches to commercial capability. Each carries distinct implications.
Path 1: Rebuild commercial capabilities within the ERP
Objective: Extend the ERP platform to cover trade promotion management, pricing, and planning.
Strengths: Tight financial integration, reduced vendor complexity, unified data model.
Trade-offs:
- Scenario modelling and optimisation capabilities remain constrained by ERP architecture
- Commercial innovation slows — changes require IT involvement and release cycles
- Complexity re-accumulates within a system that ERP programs were designed to simplify
Net outcome: Improved transaction recording. Limited improvement in decision quality.
Path 2: Replace with a standalone commercial platform
Objective: Implement a best-of-breed revenue management platform independently of the ERP.
Strengths: Stronger commercial capabilities; purpose-built for optimisation and planning.
Trade-offs:
- Integration overhead and ongoing data consistency management
- Reconciliation burden between commercial and financial systems
- Significant transformation risk introduced at the precise moment organisational capacity is most constrained
Net outcome: Capability uplift potential, often eroded by integration complexity and delayed time to value.
Path 3: Extend the ERP with a dedicated commercial decision layer
Objective: Retain the ERP as the financial system of record while running advanced planning, simulation, and optimisation in a purpose-built layer alongside it.
Design principles:
- Financial control and auditability remain within the ERP
- Commercial intelligence — scenario modelling, trade optimisation, promotion planning — operates in a connected but architecturally separate layer
- Integration is designed to be upgrade-safe, reducing long-term maintenance risk
Net outcome: No compromise on financial governance. Material improvement in decision quality. Lower transformation risk than full replacement.
This third path represents the most consistent pattern among CPG organisations achieving measurable commercial performance improvement during ERP programs.
It is not a compromise between the other two — it is a different design principle:
Rather than extending the ERP or replacing it, organisations keep the ERP as the transactional system of record while introducing a dedicated commercial decision layer alongside it. For many organisations, this represents a pragmatic balance between governance, flexibility and long-term maintainability.
What this looks like in practice
This is the architectural philosophy XTEL is built around. Rather than replacing the ERP or extending it with trade capabilities it was not designed to support, XTEL sits alongside the ERP as a dedicated commercial decision layer, covering Trade Promotion Management, Trade Promotion Optimisation, and Revenue Growth Management.
Organisations retain their ERP as the financial system of record while modernising commercial planning, scenario modelling, AI-driven decision support, recommendations and optimisation within a dedicated commercial platform.
The result is a commercial landscape that can evolve independently while remaining fully connected to the ERP foundation.
For organisations running SAP environments, this approach aligns with SAP’s Clean Core strategy by extending commercial capabilities without introducing unnecessary ERP customization. XTEL integrates with SAP ECC, SAP S/4HANA, SAP Condition Contract Management and SAP Business Technology Platform (SAP BTP), and is available on the SAP Store.
Commercial modernisation is no longer simply a technology decision. It is an architectural one — and it is being made inside every ERP programme, whether or not it is on the agenda.
If your organisation is evaluating how Trade Promotion Management, Trade Promotion Optimisation or Revenue Growth Management should evolve alongside ERP transformation, these resources provide a useful next step.
The strategic extension model
Explore the three architectural approaches in greater depth, including integration considerations, architectural principles and what leading CPG organisations are doing differently.
Commercial Excellence Benchmark
Assess the maturity of your commercial planning capabilities across strategy, planning, execution and data, and identify where the greatest opportunities for improvement exist.