A costly ERP project can fail in different ways. A system may prevent orders from being fulfilled, disrupt distribution, leave financial information unreliable, or consume far more money than planned. These six cases show why buyers need to define what the business requires, verify how a proposed system will meet those needs, and test the result before go-live.

The reported amounts are not directly comparable. Some are estimated lost sales; others are project spending, projected costs, or amounts claimed in a lawsuit. Each case identifies the measure used.

ERP and software failure cases over $100 million

Lamb Weston: Inventory problems disrupt customer orders

Reported impact: Approximately $135 million in reduced sales

Source: Lamb Weston’s fiscal 2024 results

Lamb Weston moved several North American functions, including order management and inventory management, to a new ERP system. During the transition, problems with inventory visibility affected its ability to fulfill customer orders. In its fiscal 2024 results, the company estimated that ERP-related disruption reduced sales by approximately $135 million. It separately reported an estimated $88 million in pretax losses and costs associated with lower order fulfillment and the transition. Those figures measure different effects and should not be added together. news.lambweston.com

What buyers should verify: Can the proposed ERP show dependable inventory availability and fulfill real customer orders across your locations? Test the complete process, including exceptions and peak volumes, before approving go-live.


SPAR Group: Distribution problems lead to lost sales

Reported impact: R2 billion in estimated lost sales, approximately $107 million

Source: SPAR Group’s 2024 annual report

SPAR Group introduced SAP at its KwaZulu-Natal distribution center in February 2023. Its 2024 annual report describes poor pricing visibility and inefficiencies with the new warehouse management system. SPAR estimated that the problems resulted in R2 billion in lost sales in its 2023 financial year. The approximate U.S. dollar figure comes from subsequent reporting; SPAR reported the amount in rand. thespargroup.com

What buyers should verify: Demonstrate the full flow from pricing and inventory through warehouse operations and delivery. Test the ERP and connected systems together, using the transaction volumes and exceptions your business actually encounters.


Birmingham City Council: Unresolved design leads to reimplementation

Reported amount: £108 million forecast project cost, approximately $137 million at the time

Sources: Council finance board minutes and independent auditor’s report (Both of these links download PDF files)

Birmingham City Council went live with Oracle Fusion in April 2022. The project had initially been budgeted at about £19 million. By September 2024, the council forecast £108 million in costs through 2025–26. A 2025 independent auditor’s report found that the solution design was not fully settled until two weeks before go-live. The team also lacked a sufficiently clear understanding of the business requirements and how the system would meet them. Problems with financial management and reporting led the council to undertake a reimplementation. www.birmingham.gov.uk

What buyers should verify: Define business requirements before selection, then establish how the chosen ERP will meet them before approving its detailed design. Require evidence for important gaps, financial controls, customizations, and acceptance tests. The client must be able to challenge the system integrator’s proposed solution.


Lidl: A costly mismatch with an established business practice

Reported amount: Approximately €500 million in estimated project spending

Sources: Le Monde Informatique and Henrico Dolfing’s case study

Lidl stopped its SAP-based merchandise management project in 2018 after roughly seven years. Contemporary reporting estimated that the company had spent €500 million, a figure attributed to external sources rather than confirmed by Lidl. Reporting identified a significant conflict between Lidl’s established approach to inventory valuation and the approach used by the proposed system. The project raised a question that needed to be answered much earlier: could the software support an important business practice at an acceptable cost, or should the business change that practice? www.lemondeinformatique.fr

What buyers should verify: Identify which processes protect a genuine competitive advantage. For each substantial gap, compare changing the process with configuration, an add-on, or customization. Prove that the chosen approach works in the most demanding parts of the business before committing to a broad rollout.


National Grid: Go-live problems drive a major cost increase

Reported amount: $945.1 million in projected total project cost

Source: InfoWorld report on the audit

National Grid’s SAP implementation went live in 2012. Problems followed in payroll, supply chain, and financial close. A 2014 audit projected that total project costs through fiscal 2015 would reach $945.1 million, compared with an original estimate of $383.8 million. The audit also raised concerns about design, training, accountability, vendor experience, and the decision to proceed despite questions about readiness. The projected total is project cost, not a measured financial loss caused solely by the go-live problems. www.infoworld.com

What buyers should verify: Test payroll, purchasing, reporting, and financial close with realistic data before go-live. Require clear readiness criteria and an independent way to raise unresolved problems, even when the implementation team is under pressure to meet a date.


Waste Management: A dispute over whether the software fit the requirements

Reported amount: More than $100 million spent on the project, according to Waste Management’s lawsuit

Source: Computerworld report on the dispute and settlement

Waste Management sued SAP after a disputed ERP implementation. Waste Management claimed it had spent more than $100 million on the project and alleged that the software did not meet its needs as represented. SAP disputed the claims and argued, among other things, that Waste Management had not defined its business requirements accurately or supplied enough knowledgeable, empowered users. The parties settled in 2010 for an undisclosed payment; the settlement did not establish which side’s account was correct. www.computerworld.com

What buyers should verify: Define and prioritize requirements before asking vendors to demonstrate their products. Have vendors show how they meet important requirements using your business scenarios, and record the gaps and commitments before signing.


Make your ERP decision with the risks in view

These cases do not mean every aging ERP should be replaced immediately. The first decision is whether replacement will advance your business goals, what the new system must do, and whether your company is ready to proceed.