Five Key Questions That Reveal Odoo Readiness and Why Lidl’s €500M SAP Failure Is the Ultimate Warning
Do you think it’s possible to waste over €500 million in an ERP implementation?
Lidl, one of Europe’s largest retailers, did exactly that. After seven years of development, they abandoned their SAP ERP system and reverted to legacy systems. The main reason? They refused to adapt their business standards to SAP’s protocol, insisting instead on customizing everything to match their old way of working.
This failure wasn’t about the software—it was about readiness. Lidl entered the project with unrealistic expectations, inadequate alignment, and a determination to bend the system to their will.
Even though Odoo is more modular and often requires fewer customizations than SAP, the lesson is the same: if a business cannot adapt to Odoo’s standards or if the value of customization doesn’t outweigh the costs, you’re headed for trouble!
Experienced Odoo consultants know this. That’s why, before implementation even begins, they ask five key readiness questions, questions that separate successful rollouts from costly disasters.
1. Are the Business Processes Clearly Defined?
One of the first signs of readiness is whether a company can explain its core workflows. Odoo can automate and optimize processes, but it cannot design them from scratch.
Why Lidl failed:
Lidl’s processes were deeply tied to old systems and not clearly adapted for modern ERP design. This led to confusion, ongoing scope changes, and mounting costs.
Why it matters for Odoo:
- Clearly defined workflows determine which modules are needed and how they should be configured.
- They prevent costly delays caused by unclear requirements.
What Odoo experts look for:
- Written documentation (even high-level) of sales, procurement, inventory, finance, and other key processes.
- Consistency in how stakeholders describe workflows.
When processes are clear, Odoo projects move quickly into solution design, rather than revisiting basic operational questions repeatedly.
2. Is There a Dedicated Project Manager or Single Point of Contact (SPOC)?
Odoo methodology strongly recommends having a Single Point of Contact (SPOC) on the client side.
Why Lidl failed:
Lidl’s large-scale project lacked unified decision-making, leading to misalignment between technical teams and business users.
Why it matters for Odoo:
- The SPOC serves as the bridge between business and implementation teams.
- They manage timelines, track priorities, and ensure user training continues beyond go-live.
Key point:
Clients expecting their partner to “just set it up” without involvement often face low adoption rates and wasted potential.
3. Are They Willing to Adapt Processes to Odoo’s Standard Modules?
Even though Odoo is highly modular and often requires less customization than other ERP systems, the importance of adapting to its standard business practices cannot be overstated. One of the biggest mistakes organizations make Lidl’s SAP disaster is a prime example is insisting that the software replicate every detail of legacy systems.
Why it matters for Odoo:
- Adapting processes to Odoo’s standard modules ensures the system runs smoothly and efficiently.
- Excessive customization, even in Odoo, can increase costs, complicate future upgrades, and lengthen implementation timelines.
- The goal is to leverage Odoo’s built-in best practices rather than forcing it to mirror outdated workflows.
What Odoo experts look for:
- Openness to reviewing current workflows and identifying where standard modules can provide the same or better outcomes.
- Willingness to strike a balance between essential legacy requirements and the efficiencies offered by Odoo’s native capabilities.
Bottom line:
Even with Odoo, success depends on process adaptation rather than over-customization. Businesses that resist change risk wasting time, money, and the full potential of their ERP investment.
4. Has a Proper Business Analysis Been Completed?
Many ERP projects including Lidl’s fail because requirements emerge late, forcing costly rework.
Why it matters for Odoo:
- A structured business analysis clarifies needs, risks, and integrations before configuration begins.
It ensures a shared understanding of scope, technical requirements, and business objectives.
Best practice:
- Prepare a pre-analysis document to align expectations.
- Treat the analysis as a paid engagement its value is enormous in preventing costly missteps.
5. Are Decision-Makers and Stakeholders Engaged Early?
ERP implementation requires organizational alignment as much as technical capability.
Why Lidl failed:
Leadership was engaged but mostly to enforce existing methods instead of driving change. This resistance ultimately undermined adoption.
Why it matters for Odoo:
- Early involvement helps validate priorities, align departments, and secure commitment to timelines.
- Stakeholders must support process adaptation, not just sign off on budgets.
Readiness Checklist
Before starting an Odoo project, ensure you have:
- Documented core business processes.
- A Single Point of Contact for project coordination.
- Functional users available for workshops, training, and testing.
- A completed business analysis phase with clear deliverables.
- Early alignment of key decision-makers to support change.
Conclusion and Call to Action
ERP projects don’t fail because of the software they fail because of what happens before implementation. Lidl’s €500M SAP disaster proves it.
Odoo may be more flexible and modular, but success still depends on readiness, willingness to adapt, and structured planning.
Want to know if your organization is ready for Odoo? To explore best practices for building a strong foundation and avoiding costly pitfalls, contact us to schedule a consultation.
Perché l’utilizzo di un CRM è fondamentale per le aziende
