ERP failure case studies
ERP failures are costly and often make headlines. By studying what went wrong – from Hershey's Halloween disaster to Nike's supply chain meltdown – we can learn to avoid similar pitfalls. This article analyzes famous ERP failures and extracts lessons for risk management, governance, and change management.
1. ERP failure statistics
Source: Standish Group CHAOS Report, Panorama Consulting
2. Hershey Foods (1999)
Hershey's Halloween Disaster
What happened: Hershey implemented a $112 million ERP system (SAP, Siebel, Manugistics) in 1999, going live just before Halloween – their peak season. Order processing failed, causing shipment delays. The company lost over $100 million in sales, and stock price dropped 19%.
Root causes:
- Big bang go‑live during peak season
- Inadequate testing (especially integrations)
- Poor change management
- Overly aggressive timeline
Lesson: Never go live during peak business cycles. Phase implementations and test thoroughly.
3. Nike (2000)
Nike's Supply Chain Meltdown
What happened: Nike implemented an i2 demand‑planning system that over-ordered some shoes and under-ordered others. The result: $100 million in lost sales, a 20% stock drop, and a class‑action lawsuit.
Root causes:
- Software configuration errors
- Lack of proper testing
- Over‑reliance on vendor promises
Lesson: Test every module with real data. Validate vendor claims. Plan for data migration carefully.
4. Lidl (2018)
Lidl's €500 Million Failure
What happened: German discount retailer Lidl spent 7 years and over €500 million developing a custom ERP. The project was abandoned because it couldn't handle the company's complex processes.
Root causes:
- Over‑customization (not using standard features)
- Lack of executive oversight
- Scope creep
Lesson: Avoid excessive customization. Use standard processes where possible. See SRS and governance.
5. City of Harrisburg (2004)
Harrisburg's ERP Lawsuit
What happened: The City of Harrisburg, Pennsylvania, sued SAP and implementation partner Deloitte, claiming the ERP project was a failure after spending over $12 million. The system never worked as intended.
Root causes:
- Poor requirements definition
- Vendor mismanagement
- Inadequate testing
Lesson: Define clear requirements and acceptance criteria. Maintain strong vendor governance.
6. Revlon (2018)
Revlon's Supply Chain Crisis
What happened: Revlon's ERP migration caused massive supply chain disruptions – inability to ship products, invoice customers, or pay suppliers. Sales plummeted, and shareholders sued.
Root causes:
- Underestimated complexity
- Inadequate data migration
- Poor contingency planning
Lesson: Plan for failure. Have rollback procedures and manual workarounds ready.
7. Common root causes
Across these failures, patterns emerge:
| Cause | Frequency | Related articles |
|---|---|---|
| Poor planning & governance | High | Governance |
| Inadequate testing | High | UAT |
| Data quality issues | High | Data migration |
| Scope creep / over‑customization | Medium | SRS |
| Change management failures | High | Change management |
| Vendor / partner issues | Medium | Vendor lock-in |
8. Lessons learned
- Invest in planning: Use a structured SRS and realistic timeline.
- Test, then test again: Multiple rounds of UAT with real data.
- Manage change: Involve users early, communicate, train.
- Govern rigorously: Strong steering committee with decision rights.
- Plan for the worst: Have rollback and contingency plans.
- Don't over‑customize: Embrace standard processes.
Key Takeaways
- ERP failures are common and expensive – but preventable.
- Common causes: poor planning, inadequate testing, data issues, change resistance.
- Learn from high‑profile cases: Hershey's (peak go‑live), Nike (data errors), Lidl (over‑customization).
- Apply lessons to governance, testing, change, and data migration.
- Remember: those who cannot remember the past are condemned to repeat it.
Are all ERP failures caused by software bugs? No – most are due to people, process, and project management issues, not software.
Can small companies learn from these big failures? Absolutely – the root causes (poor planning, lack of testing) apply to any size.
What is the most common single cause? Many studies point to inadequate change management – the human side.
Continue Reading in ERPEDIA
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.