When Revlon’s ERP Makeover Turned into a Beauty Blunder
Introduction: A Makeover That Went Terribly Wrong
Revlon is a global icon in the beauty industry, known for elegance, legacy, and a vast product portfolio. But in 2018, it wasn’t a bold product launch or celebrity endorsement that made headlines.
It was a failed SAP ERP implementation that disrupted manufacturing, delayed shipments, triggered shareholder lawsuits, and caused brand damage across the board.
What was meant to be a strategic modernization quickly became a high-profile cautionary tale of how ERP missteps can unravel even the most glamorous operations.
What Happened in Revlon’s ERP Rollout?
In early 2018, Revlon went live with a new SAP ERP system at a major North Carolina manufacturing facility, part of an effort to unify systems across Revlon and its newly acquired brands (including Elizabeth Arden).
But soon after go-live, the company experienced:
- Production delays
- Order fulfillment issues
- Customer service breakdowns
- Disrupted manufacturing workflows
In a public SEC filing, Revlon disclosed that the ERP failure “caused the company to be unable to fulfill certain customer orders in a timely manner.”
“In ERP, poor execution isn’t just a technical failure... it’s a business failure.”
The Real-World Fallout
Supply Chain Disruption
Revlon struggled to manufacture, track, and ship products. Retail partners experienced stock-outs, missed deliveries, and inconsistent communication.
Financial Consequences
Operational inefficiencies led to higher costs, lost revenue, and shareholder frustration amplified by the company’s ongoing integration challenges.
Shareholder Lawsuits
Investors filed lawsuits, alleging Revlon misrepresented the risks involved in the ERP rollout and failed to disclose system vulnerabilities.
Brand and PR Damage
For a consumer brand built on perception and reliability, the ERP failure became a public embarrassment that undermined trust across the supply chain.
What Went Wrong?
1. Poor Change Management
Teams lacked the training and preparation needed to navigate a new system. Resistance and confusion slowed adoption at every level.
2. Inadequate Testing
The system was launched without comprehensive end-to-end validation. Core workflows weren’t stress-tested under real operational conditions.
3. Overly Aggressive Timelines
Facing pressure from stakeholders and post-acquisition integration challenges, Revlon moved too quickly because they were prioritizing speed over readiness.
4. Data and Process Misalignment
Legacy systems, acquired platforms, and inconsistent data structures led to conflicts and duplication, breaking critical workflows downstream.
Lessons for Every Business
✅ ERP Is Not Just an IT Project
Revlon’s experience reinforces the need to treat ERP as a cross-functional, enterprise-wide transformation. Every department is affected, especially supply chain and customer experience.
✅ Test in Real Conditions
Load-test the ERP system under full production volume before go-live. Simulations must reflect real-world complexity.
✅ Avoid Rushed Launches
Stakeholder pressure is real but a failed rollout will cost more than a delayed one. Readiness should dictate the timeline, not investor expectations.
✅ Data Hygiene Is Foundational
Clean, structured, and well-mapped data is the lifeblood of ERP. Integration across systems is only as good as the quality and consistency of the data.
Why This Story Still Matters
Revlon’s ERP failure is more than a system glitch, it’s a business continuity crisis. It reminds us that digital transformation in consumer industries, especially those with brand equity at stake, requires discipline, foresight, and execution maturity.
ERP systems are invisible to consumers, until they fail. And when they do, they impact everything from store shelves to stock price.
Planning a high-stakes ERP rollout?
→ Join The Community
Final Thought
ERP platforms are meant to enable scale, accuracy, and agility. Not introduce instability.
Revlon’s case proves that even iconic brands can falter when speed overtakes strategy, preparation is neglected, and systems go live before teams are ready.
For every business considering ERP transformation, this is the message:
Technology should enhance your promise. Not endanger it.
