Short answer: When staff are not using Odoo, the cause is usually gaps in the rollout rather than the software: people were not trained, Excel keeps running in parallel, the system does not match real processes, or the interface is in a language users struggle with. Prosci's research shows projects with excellent change management meet their objectives about seven times as often. Deep Vision, an Odoo Gold Partner from Tashkent and the team behind Odoo's Uzbek translation, handles these cases with an audit and a recovery plan.
Odoo went live, licences were paid and the launch report was signed. A few months later the picture is different: sales staff still write orders in a notebook, the warehouse keeps stock in Excel, and the owner does not trust the reports. This is a very common situation, and it can be fixed. This article covers why employees are not using Odoo, how to diagnose it and what a step-by-step recovery plan looks like.
What does it mean when Odoo is not being used?
Low Odoo adoption means the system is technically live, but employees do not do their daily work in it, data is entered only partly, and decisions rely on other sources.
The signs are simple: stock in Odoo does not match the warehouse, orders are entered late, staff complain that “the system takes too long,” and the owner asks the accountant for an Excel report again. The company pays in money and time for two systems and gets full value from neither.
This is not unique to Odoo. Gartner expects that by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals (Gartner). Most often the cause is people and processes, not technology.
Why are employees not using Odoo?
Excel stayed alive in parallel. If the old files were kept “just in case,” people drift back to what they know. The parallel run must end on a fixed date.
Training was not enough. One general presentation is not training. Each role needs to practise its own tasks on its own data: sales enters an order, the warehouse receives goods, accounting closes the period.
The system is configured wrong. If Odoo does not reflect how the company actually works, staff work around it. If discount rules or approval steps differ from real life, the work moves outside the system.
The interface is in an unfamiliar language. Menus in English or another unfamiliar language are a barrier for warehouse staff and cashiers. Every misunderstood button leads to a mistake, and every mistake erodes trust.
Management does not use it. If the owner asks for reports from Excel rather than Odoo, staff treat Odoo as secondary.
Dirty data. Duplicate products and wrong balances destroy trust in the first week.
For other common mistakes, see 7 ERP implementation mistakes.
How much does change management affect results?
Change management is the planned work of preparing people for a new way of working: training, support and preventing a slide back to old habits.
According to Prosci, 88% of projects with excellent change management met or exceeded their objectives, compared with 13% of projects with poor change management, roughly a sevenfold difference (Prosci). In other words, configuring Odoo correctly is half the job. The other half is working with people.
How can you check how much Odoo is really used?
Check your company against this list.
- What share of sales orders is created in Odoo?
- How closely does stock in Odoo match the last physical count?
- Are there Excel files maintained in parallel with Odoo?
- Which reports does management take from Odoo, and which from elsewhere?
- Is there a short guide or video for each role?
- Who trains new employees on Odoo, and how long does it take?
- Is the Odoo interface in a language staff understand, such as Uzbek or Russian?
- Where are staff questions and errors logged, and who answers them?
- Is there an internal person responsible for Odoo?
If several answers are “no” or “not sure,” the problem is not the software but an unfinished rollout. On moving fully off spreadsheets: moving from Excel to ERP.
What does an Uzbek-language interface change?
In many companies, warehouse, cashier and production staff prefer to work in Uzbek. None of the global ERPs we checked (SAP S/4HANA, Microsoft Dynamics 365, Oracle NetSuite) lists an Uzbek interface among its official languages. Odoo has one. In the Odoo 19 source code, 360 of 376 Uzbek translation files credit the Deepvision team (Amon Olimov, Jonibek Yorqulov), and about 97% of 60,618 strings are translated. Odoo 19 also includes an official accounting localization for Uzbekistan.
An interface in the native language speeds up training and reduces mistakes. More: Odoo in Uzbek.
How do you rescue an Odoo system nobody uses?
A recovery plan usually has five steps.
- Audit: which processes run in Odoo, which run outside it, and why.
- Fix the configuration: change what does not match the real process, remove unnecessary fields and steps.
- Clean the data: fix products, customers and stock balances once and properly.
- Role-based training: each position practises its own scenario and gets a short guide.
- Close Excel: after a fixed date, parallel files stop, and management takes reports only from Odoo.
A starting guide for users: how to use Odoo.
What should management do during the recovery?
Adoption starts at the top. In weekly meetings, discuss numbers only from Odoo reports. Appoint an internal person responsible for Odoo and give them time for it. Do not dismiss staff complaints about the system: each one points to a specific problem in configuration, training or data. In the first months, celebrate small wins, such as a smaller stock-count discrepancy or faster order processing. When employees see that management takes the system seriously, they do the same.
How does Deep Vision help in these cases?
Deep Vision is an official Odoo Gold Partner from Tashkent. Its Odoo partner directory page lists 7 certified experts, 20+ client references and 89% customer retention, against a Gold minimum of 80% (odoo.com). Retention is one of the signs that systems keep being used after go-live.
Our approach:
- Audit first, then a fix plan.
- Training in Uzbek and Russian; we translated Odoo's Uzbek interface ourselves.
- Experienced specialists who know industries and finance adjust settings to the real process.
- Ready modules for Didox and Asl Belgisi spare staff from juggling extra programs.
- Education track record: 4 hackathons, 3 seminars, an online Odoo course, and Odoo taught with Deep Vision at 3 universities to 300+ students a year.
If your Odoo is not being used, fill in the brief or see our Odoo implementation service.
Frequently asked questions
How can I tell that Odoo is not really being used?
If orders and stock are not fully kept in Odoo, Excel files run in parallel and management takes reports from elsewhere, adoption is incomplete.
Do we need to reimplement?
Usually not. An audit, configuration fixes, data cleanup and training are often enough.
How long does training take?
It depends on the number of roles. What matters is that training is practical and repeated for each role, not a one-off session.
Does an Uzbek interface really help?
Yes, especially for warehouse, cashier and production staff. Menus in the native language speed up learning and reduce errors.
Does Deep Vision work on Odoo systems set up by another partner?
Yes. We start with an audit of the existing system and then build a recovery plan.
Sources
- Prosci: the correlation between change management and project success
- Gartner: ERP initiatives and business expectations
- Odoo: partner tier requirements
- Odoo partner directory: Deep Vision
Make your Odoo work for real: fill in the brief or call +998 77 093 00 07.