Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Lidl stopped its eLWIS merchandise-management programme in July 2018 after about seven years of development. Industry reporting estimated spending at roughly €500 million, although Lidl did not publish an audited loss figure. The retailer chose to keep developing its existing in-house Wawi platform instead. Lidl also said the decision was not a rejection of SAP generally and that it would continue using SAP in other areas.
What Lidl actually abandoned
eLWIS—short for “Elektronisches Lidl-Warenwirtschaftsinformationssystem”—was intended to replace Wawi, Lidl’s internally developed merchandise-management system. Reports described a solution based on SAP Retail powered by SAP HANA, with Software AG’s WebMethods middleware included in the wider architecture.
This was not a failed SAP finance deployment across every Lidl operation. It was a major retail programme covering merchandise, inventory and related processes. Computer Weekly reported a target environment spanning about 10,000 stores and more than 140 logistics hubs, but those figures describe planned scope, not completed deployment.
Contemporaneous accounts said Lidl’s original strategic objectives could no longer be achieved “with reasonable effort.” Lidl therefore decided that further development of Wawi offered a better cost-benefit outcome than completing eLWIS.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
Why Lidl wanted to replace Wawi
Wawi was closely aligned with Lidl’s established operating model, but reports identified growing constraints:
- limited capacity for innovation and enhancement;
- process breaks and integration gaps;
- duplicated master data;
- functional restrictions;
- a decentralised server structure; and
- rising maintenance and operational complexity.
The proposed replacement aimed to connect processes from suppliers through logistics and stores, reduce master-data duplication, and improve analysis and forecasting. That is a rational reason to modernise a legacy platform, but it also creates a difficult design question: which existing processes should be changed, and which are essential to Lidl’s business model?
Timeline: from development to cancellation
| Date | What happened | Qualification |
|---|---|---|
| 2011 | Lidl began developing a successor to Wawi. | Reports describe SAP Retail and HANA as the technology base. |
| May 2015 | The system reportedly went live in Austria. | This date was reported by Computer Weekly. |
| 2015–2016 | Lidl continued work on the wider transformation and global-template ambition. | A technical go-live did not establish that the programme was ready for the largest markets. |
| By 2018 | Reporting described only limited or smaller-market deployment, naming Austria, Northern Ireland and the United States. | Sources differ on the exact pilot and rollout footprint. |
| July 2018 | Lidl stopped eLWIS and planned further Wawi development. | The decision was reported contemporaneously by Netzwoche and others. |
| August 16, 2018 | Computer Weekly published its English-language account. | The report put the programme’s cost at approximately €500 million based on external estimates. |
The central mismatch: Lidl’s processes versus the standard design
Later analysis identifies inventory valuation and merchandise data as a major source of difficulty. Lidl’s established approach reportedly used purchase prices, while the standard retail design being implemented represented inventory and related values differently. Preserving Lidl’s required business semantics therefore demanded substantial adaptation.
That does not mean SAP categorically cannot support purchase-price valuation. The more accurate conclusion is that Lidl’s requirements did not align cleanly with the standard design and implementation assumptions chosen for eLWIS. The resulting customisation affected more than a screen or report: valuation rules flow into purchasing, stock, margins, finance, replenishment and management reporting. A change that appears local can therefore become a cross-functional redesign.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The most specific accounts of this conflict come from later secondary analysis, including ERP Perspective, rather than a published Lidl post-mortem. It is best treated as an important reported explanation, not a conclusively documented single root cause.
Why a pilot did not prove global readiness
A system can operate in a constrained market and still fail as a global retail backbone. The largest countries may have more stores, transactions, products, interfaces, legal variations and peak-period demands than a pilot environment. Lidl’s reported pattern illustrates several different milestones:
- Technical go-live: software is operating in a defined location.
- Operational acceptance: users and processes can run the business reliably.
- Scalable rollout: the template performs across the company’s hardest markets.
- Business-case achievement: expected benefits justify the remaining investment.
eLWIS may have reached limited deployment without meeting the latter objectives. A small-market pilot can generate useful learning, but it can also create false confidence if it does not exercise the scale and complexity of the largest operations.
What the €500 million figure means
Contemporaneous reporting put total programme spending at about €500 million. That was an estimate from industry sources or observers, not a publicly audited Lidl disclosure. It should not automatically be described as a confirmed €500 million write-off or loss.
The available reports do not provide a reliable itemised breakdown separating SAP licences, implementation partners, consultants, internal labour, integration, migration, infrastructure, sunk costs and accounting treatment. Later commentary sometimes rounds the amount toward €600 million, but that may reflect a different estimate or additional assumptions; it should not replace the 2018 figure without an explanation.
Was SAP itself the problem?
The public record does not support the blanket claim that SAP was technically incapable of serving a retailer. The outcome is better understood as an interaction among six factors:
- Product capability: SAP supplied a standard retail platform.
- Business-process fit: Lidl had a mature, highly specific operating model.
- Solution design: the programme had to translate Lidl’s data and valuation rules into the new model.
- Customisation: preserving legacy behaviour increased complexity and long-term maintenance risk.
- Governance and change: success depended on decisions about standardisation, ownership and user adoption.
- Stop/go discipline: executives eventually judged the remaining effort disproportionate to the expected benefit.
Lidl explicitly framed the decision as choosing its own system rather than rejecting SAP as a company. That qualification matters: abandoning one SAP-based merchandise programme is not the same as abandoning SAP everywhere.
Why returning to Wawi could make economic sense
Wawi was not necessarily an ideal or future-proof platform. It was, however, understood by Lidl, aligned with its established processes and under Lidl’s direct control. Continuing to evolve it offered a more predictable path than paying for further eLWIS redesign, migration and rollout risk.
The decision also limited additional exposure. Past expenditure could not be recovered, but it should not determine future spending. The relevant question was whether the next tranche of investment would produce enough benefit—not whether seven years of work justified continuing.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Lessons for companies planning an ERP transformation
Decide what must change before choosing the system
Separate genuinely differentiating or legally necessary processes from habits that survive only because the legacy system made them familiar. If the organisation will not change a process, prove that the selected platform can support it without altering core transaction logic.
Prove the data model early
Test products, suppliers, stores, prices, costs, inventory and valuation across merchandising, supply chain and finance before committing to a global template. A disagreement over “which price” can become a company-wide integrity problem.
Measure customisation debt
Maintain an exception register showing each deviation from standard functionality, its owner, upgrade impact, test burden and lifetime cost. Distinguish an isolated extension from a change to core inventory or financial logic.
Test the hardest market, not only the easiest pilot
Use representative transaction volumes, product counts, interfaces, legal requirements and peak-season loads. A pilot should be a learning environment, not evidence that global rollout is automatically safe.
Make benefits and exit gates explicit
Track the original business case with measurable targets for operating cost, data quality, process cycle time, service levels and forecast performance. Set thresholds that trigger redesign, pause or cancellation before sunk costs become the main argument for continuation.
Give assurance teams independence
An independent architecture, testing and benefits-review function should be able to report that the programme is not scalable or economically viable. Implementation partners and internal sponsors need incentives to surface bad news early.
What this episode does—and does not—prove
Lidl’s experience is not evidence that companies should never buy SAP, nor that a legacy platform is always superior. It shows the risk of selecting a standard ERP without agreeing which processes the business will standardise, which it must preserve, and what the difference will cost.
The lasting lesson is simple: evaluate process fit, data semantics, customisation, scale and governance together. A system can go live, function in a pilot and still fail the transformation’s strategic and economic objectives.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
