
Meet the Authors
Key Takeaways
-
Clorox has successfully transitioned to a cloud-based S/4HANA platform, replacing a legacy SAP system, which is crucial as it enables real-time data integration across finance, supply chain and sales.
-
The company is simultaneously managing significant operational pressures due to the acquisition of GOJO Industries while stabilizing post-S/4HANA implementation. This scenario underscores the importance of synchronizing ERP transformations with corporate growth strategies, impacting SAP practitioners and enterprise architects.
-
Clorox's experience highlights that organizations can expect a productivity lag of 12 to 18 months post-S/4HANA go-live before realizing operational improvements. This understanding is vital for SAP professionals as they plan for ongoing support and optimization during stabilization phases, emphasizing the need for careful change management and employee training.
Clorox completed a five-year SAP enterprise resource planning system rollout across the United States and Canada in January 2026, migrating from a 20-year-old legacy SAP environment to a cloud-based S/4HANA platform integrating finance, supply chain, sales and planning through real-time data. The implementation spanned 21 manufacturing plants, required training for more than 5,000 employees through 38,000 hours of instruction, and establishes a “digital backbone” enabling data-driven operational decision-making across the consumer packaged goods manufacturer.
For SAP practitioners managing large-scale S/4HANA migrations, Clorox’s experience demonstrates how modernization timing intersects with corporate strategy: The company announced their acquisition of GOJO Industries, maker of Purell, in January 2026 while still stabilizing operations following the ERP go-live, creating dual operational pressures that compressed margins and required careful sequencing of integration activities.
The S/4HANA transition initially disrupted Clorox’s supply chain performance due to lower shipments related to implementation challenges and inventory buffer strategies that left retailers understocked when procurement issues emerged. For their part, Clorox does not expect productivity gains from the S/4HANA system to materialize until fiscal 2027, signaling that large-scale migrations require 12 to 18 months post-go-live before operational improvements offset transition costs and stabilization efforts.
Explore related questions
Strategic Timing and SAP Integration Architecture
Clorox’s decision to acquire GOJO while completing S/4HANA stabilization creates compounding integration complexity as the company must simultaneously optimize newly deployed SAP workflows and absorb a business expansion into health and hygiene markets. The GOJO acquisition, expected to close before the end of Clorox’s fiscal 2026, adds Purell’s professional and institutional hygiene business to Clorox’s consumer retail portfolio, positioning the company for expansion into healthcare, corporate and educational sectors. SAP architects evaluating M&A timing relative to S/4HANA transformations should recognize that Clorox deliberately completed its technical rollout before initiating the acquisition, avoiding scenarios where legacy systems complicate post-merger integration or require parallel SAP instance maintenance during ownership transitions.
The S/4HANA platform standardizes master data and business processes across departments and locations, replacing fragmented manual workflows with integrated real-time information that improves demand forecasting through SAP Integrated Business Planning, production planning through SAP Manufacturing Execution, order fulfillment and supplier collaboration. Clorox’s prior SAP ECC environment, in place for two decades, had become increasingly manual and disconnected across business units, limiting real-time visibility and requiring reconciliation work between modules. Large-scale SAP replacements of this scope are uncommon in consumer packaged goods due to operational risk in migrating live manufacturing and distribution networks, but Clorox’s approach reflects a broader CPG shift toward cloud-based S/4HANA platforms supporting embedded analytics, intelligent automation and future SAP Business Technology Platform extensions.
What This Means for SAP Practitioners
Post-go-live hypercare periods extend 12 to 18 months before S/4HANA productivity gains materialize. Clorox does not expect supply chain improvements until fiscal 2027 despite completing technical deployment in January 2026, signaling that SAP optimization requires sustained basis team focus, user adoption support and process refinement beyond cutover. S/4HANA transformation leaders should structure business cases around delayed value realization and extended application management services engagements, recognizing that operational disruption persists through stabilization phases.
M&A timing relative to S/4HANA completion creates strategic windows for seamless acquisition integration. Clorox announced the GOJO acquisition after completing S/4HANA rollout, avoiding scenarios where legacy SAP ECC instances complicate post-merger carve-outs or require parallel AMS support. SAP enterprise architects should position S/4HANA modernization as prerequisite infrastructure for inorganic growth strategies, as cloud platforms enable faster acquisition absorption through standardized data models, unified Fiori workflows and consistent integration middleware that legacy environments cannot support efficiently.
Consumer packaged goods SAP customers accelerate cloud migrations despite manufacturing operational risk. Clorox replaced a 20-year-old SAP platform across 21 plants with cloud S/4HANA, joining industry transformations historically cautious about live production network migrations. SAP solution architects should emphasize S/4HANA’s embedded analytics through SAP Analytics Cloud, intelligent automation through SAP Build Process Automation, and real-time supply chain visibility through SAP IBP integration over transactional efficiency messaging, as CPG manufacturers prioritize predictive capabilities and supplier collaboration that SAP ECC cannot deliver.




