Short answer: An Odoo consultant analyses your business processes and shows how to solve them with standard Odoo features, while a developer turns a given task into code. An Odoo project needs both, but order matters: the consultant first defines what should be done, then the developer writes code only where it is truly needed. At Deep Vision, consulting, development and training work together on the same project.
Many companies treat an Odoo implementation as "finding a programmer". The client describes the process they are used to, the developer builds it, and the old mess ends up automated inside a new system. This article explains the difference between an Odoo consultant and a developer, when you need each one, and how to check the make-up of a provider's team yourself.
What does an Odoo consultant actually do?
An Odoo consultant is a specialist who designs business processes on standard Odoo modules and configures them. They start with questions: how does an order arrive, who approves it, how is stock counted, how is cost calculated, which report does the owner expect? Only then is the process mapped onto Odoo's logic.
A consultant's core tasks:
- study the current process and find weak points (double entry, manual calculations, unclear ownership);
- check whether Odoo already has a standard solution and demonstrate it;
- choose and configure modules such as Sales, Inventory, Purchase, Accounting and Manufacturing;
- write a requirements document and give the developer a clear task;
- train staff and verify results after go-live.
A good consultant sometimes says "no". If a client asks to reproduce a 40-column Excel sheet inside Odoo, the consultant asks which decision that sheet supports, and often shows that a standard report or filter does the job.
What does an Odoo developer do, and when do you really need one?
An Odoo developer is a specialist who writes new modules, integrations and features in Python on the Odoo framework when the standard product does not cover a need. That work is essential: integrations with tax services, unusual calculation logic, and connections to websites or hardware can only be done in code.
The problem is not the developer but where the developer is used. A developer executes the task; judging whether that task is right for the business is not part of the job. If the team has no consultant, every client wish turns into new code. The result:
- custom modules pile up, and each one needs its own maintenance;
- upgrading to a new Odoo version gets harder, because all custom code must be re-checked;
- timelines and budgets grow;
- a broken process starts running faster, but it is still broken.
Gartner expects that more than 70% of recently implemented ERP initiatives will fail to fully meet their original business goals by 2027 (Gartner). One reason is exactly this: technology copies old habits instead of improving the process.
Odoo consultant vs developer: what does the difference look like in practice?
An example. A wholesale company asks: "Customer discounts should not be typed in by hand; calculate them automatically."
A developers-only team: writes a new discount module with its own rules table. Two weeks of work, then re-testing at every upgrade.
A consultant-led team: first asks what the discount rules are (customer group, volume, season). Then it turns out most of them are covered by standard Odoo pricelists and customer categories with zero code. A small add-on is written only for the one genuinely unusual rule.
Both versions work, but the second is cheaper, faster and does not cause trouble at upgrade time. This is the basic rule of ERP projects: standard first, configuration second, code last. More on this: 7 mistakes in ERP implementation.
Does your provider have real consultants? How to check yourself
Ask these questions at the first meeting. The answers quickly reveal who will actually work on your project:
- Who analyses the processes, and does that person hold an Odoo functional certification?
- What document is produced in the first phase, before any development starts?
- Can you show in writing which requirements are covered by standard Odoo and which need code?
- In your last project, did you ever talk a client out of a customisation in favour of a standard feature?
- Who trains our staff, and will training materials be prepared?
- Is there someone on the team who understands accounting and inventory valuation?
Warning sign: the team consists only of programmers, the first meeting skips processes and goes straight to "send us a spec and we will quote", or the proposal has no analysis phase at all. That means you are expected to play the consultant yourself.
You can also check a partner in the official odoo.com partner directory, which lists certified experts and client references. A full list of questions for choosing an Odoo implementation partner: How to choose an Odoo partner in Uzbekistan.
When do you need a developer, and when a consultant?
A simple rule of thumb:
- New Odoo implementation, process redesign, merging several departments: start with a consultant.
- Integration with tax services, marketplaces, banks or hardware: the consultant defines requirements, the developer writes the code.
- A small technical bug in a running system: a developer is enough.
- "Odoo is live but staff are not using it": a consultant plus a trainer.
According to BCG, 70% of digital transformations fall short of their objectives, and high-caliber talent is one of six success factors; only one in four organisations cleared that bar (BCG). Team composition directly shapes the outcome.
How does Deep Vision combine consulting and development?
Deep Vision is an official Odoo Gold Partner based in Tashkent. Our odoo.com partner page shows 7 Odoo-certified experts (versions 17 to 19), 20+ client references and a customer retention rate of 89% (partner page). For Gold status, Odoo requires 300 new Enterprise users per year, 6 certified experts and at least 80% retention (Odoo partner tiers).
How we work:
- Diagnostics and process analysis: a consultant interviews each department and documents the current process.
- Standard first: every line in the requirements list is tagged "standard", "configuration" or "code".
- Development only where justified: for example, we have ready-made modules for Didox and Asl Belgisi, so those integrations are not built from scratch.
- Training: staff can work in an Uzbek-language interface; our team produced Odoo's Uzbek translation.
Our team includes not only programmers but also experienced specialists who know industries and finance. So the conversation starts not with "which button do you need" but with "which decision should be made faster". More about us: Why Deep Vision; service details: Odoo implementation.
If you would like to walk through your processes with a consultant, fill in a short brief.
Frequently asked questions
Isn't a consultant more expensive?
The hourly rate may be higher, but a consultant prevents unnecessary code. As a result, total project budget and future maintenance costs usually go down.
We have our own IT department. Do we still need a consultant?
An in-house IT team knows the technical side well, but deep knowledge of standard Odoo features and experience from other companies usually sit with an external consultant. The strongest results come when both work together.
How can I verify an Odoo consultant's certification?
The odoo.com partner directory shows each partner's number of certified experts and the versions they are certified on. At the meeting, also ask whether that specific person will work on your project.
Is any custom requirement a bad sign?
No. Some requirements reflect a real competitive advantage, and writing code for them is the right call. What matters is that the decision is made deliberately, after analysis.
Can a developer become a consultant?
Yes, many strong consultants started on the technical side. But it takes a separate effort to learn business processes, finance and industry specifics.
Sources
- Deep Vision, odoo.com partner page
- Odoo partner programme: Ready, Silver and Gold requirements
- Gartner: ERP initiatives and expected outcomes
- BCG: success factors in digital transformation
Start your Odoo project with a consultant: fill in the brief or call +998 77 093 00 07.