Lidl (Schwarz Group) · 2018 · cost index 5/5
Lidl walks away from SAP Retail
Estimated €500M+ over seven years before abandonment
What happened
Lidl bet that a standardized SAP Retail rollout would unify European operations. After years of customization wars, performance cliffs, and store-level reality colliding with vendor templates, the discounter killed the program and went back to the bespoke stack that actually understood €0.29 yogurt pricing.
Failure mode
Big-bang ERP with heavy customization disguised as "best practice." Regional legal, supplier, and pricing rules were forced into SAP's model until the project became a parallel company that never shipped to a single store on time.
Lesson
Packaged ERP is not a shortcut around domain knowledge. If your competitive edge is operational ruthlessness on thin margins, a generic retail suite plus SI army is a tax, not a strategy — especially when the fallback is the system you already had.
Sources
- Manager Magazin — Lidl SAP project halt
- Reuters — German retailers and ERP overruns
- Handelsblatt — Schwarz Group IT strategy coverage
Related tech
Practice · 1995–now
Heavy SAP customization
Customize the ERP until upgrades are impossible. The enterprise tax that keeps consultants in villas.
$ ABAP extensions and bespoke modules that made every upgrade a multi-year program. Millions spent aligning ERP to process instead of process to ERP.
Framework · 1999–now
J2EE / EE frameworks
EJB-heavy stacks taught a generation that XML config was architecture. Spring and lighter runtimes absorbed the survivors.
Practice · 1998–2014
XML-as-architecture
When every wiring decision lived in 4,000-line XML files. Configuration became a second programming language nobody wanted.
Architecture · 2003–2015
Enterprise SOA
Reuse via shared services — in theory. In practice: central buses and political ownership fights.
$ ESBs, governance boards, and "service portfolios" burned seven-figure programs. Many orgs got distributed monoliths with worse latency and a permanent integration team.
Language · 1995–now
Java
Write once, run everywhere — then enterprise forever. Still the backbone of serious backend estates.
Practice · 1990–now
Big Design Up Front
Spec first, code later. Agile didn't kill planning — it killed pretending the Gantt chart was reality.