S/4HANA
Clean Core
Fit-to-Standard
In almost every SAP S/4HANA scoping conversation, someone cites a different "rule of thumb" for how much should be standard versus custom: 80/20, 70/30, 60/40—pick your favorite. The disagreement is not surprising. "Custom" can mean anything from a few extra fields on a Fiori app to deep logic changes in the core. "Standard" can mean anything from adopting SAP Best Practices to "we kept our processes but implemented them in SAP."
What is clearer than the percentages is the direction of travel. In 2026, fit-to-standard is increasingly the default for the core, while customization is evolving into a more governed, decoupled form of extension. This shift is being driven by cloud operating models, faster release cycles, talent scarcity, and a growing consensus—supported by both SAP guidance and ERP research—that uncontrolled customization increases implementation effort and long-term maintenance risk.¹
The fit-to-standard vs custom debate persists because ERP value is a trade-off between two legitimate goals:
The problem is that ERP programs often treat customization as a design preference instead of an economic decision. Research consistently frames customization as a "double-edged sword": it can improve functional fit and user satisfaction, but it increases complexity, cost, and upgrade burden.² Moreover, the imperative for continuous innovation and rapid adaptation to market dynamics further amplifies the challenges associated with extensive customization.³
In 2026, those costs compound faster because the environment is less forgiving: more cloud adoption, tighter governance expectations, and less surplus capacity in skilled delivery teams.
SAP's own implementation doctrine has been pushing toward fit-to-standard for years. SAP Activate explicitly positions SAP Best Practices as the baseline, replacing traditional blueprinting with fit-to-standard analysis, where teams validate requirements against a working baseline and capture only the deltas in a backlog.
Separately, SAP's clean core strategy frames the end state many customers now optimize for: an ERP core that stays upgradeable and innovation-ready, with extensions governed so they do not destabilize the system—as SAP enforces by prohibiting customized extensions to the ERP core in cloud environments, requiring instead standardized interfaces for maintainability and continuous upgrades.³
In practice, this means:
A useful way to modernize the debate is to stop asking "standard or custom?" and instead ask: "Where does the custom logic live?"
Recent literature reviews show a shift away from classic on-premise code modification toward interface, integration, and UI-level customization in cloud ERP contexts.⁴
SAP's own extension guidance formalizes this as architectural domains and methods. The SAP Application Extension Methodology distinguishes:
So the "winner" in 2026 is not simply "standard." The winning pattern is:
Standardize the core; differentiate via governed extensions.
This strategy allows organizations to leverage best practices for core functionalities while retaining the flexibility to build unique capabilities where they provide a competitive edge.⁵
A practical way to decide is to classify each requirement into one of three buckets:
If the process does not create durable advantage (e.g., standard finance compliance, basic procurement flows), fit-to-standard typically dominates because it reduces delivery time and future friction.
Some deviations are unavoidable (regulatory, country-specific, industry constraints). The goal is not ideological purity; it is to make the delta small, explicit, testable, and owned.
If it truly differentiates (and leadership would fund it repeatedly), implement it as an extension in a way that protects upgradeability—preferably via released APIs and decoupled architecture, aligned with SAP's extension methodology and cloud extensibility models.
Most programs do not fail because teams choose the "wrong philosophy." They struggle because teams cannot reliably translate raw discovery into high-quality fit-to-standard and customization decisions—fast enough, consistently enough, and with enough evidence to align stakeholders.
The outcome is not "less customization at all costs." It is better customization choices: standard where it is sufficient, governed deltas where necessary, and deliberate extensions where differentiation truly pays.
Fit-to-standard is increasingly the default for SAP core processes in 2026, reinforced by SAP Activate and clean core thinking.
But custom development is not going away; it is being reshaped into a cleaner, more decoupled extension model supported by both SAP's extension methodology and ERP research showing that unmanaged customization inflates cost and risk.
The organizations that perform best are not those that "customize less" as a slogan. They are the ones that can decide faster, document deltas, and treat extensions as governed products—so their SAP core remains upgradeable while the business still gets differentiation where it genuinely pays.
