Odoo, implemented by people who have undone bad Odoo
Your Odoo works, but only because one developer keeps patching it, and nobody dares upgrade.
What you get
- Configuration before customisation — custom code only where the business genuinely differs
- Arabic and English side by side, with VAT and local compliance handled
- An upgrade path that does not require rewriting your customisations every release
- Your own team trained to run day two, not just day one
Your Odoo works because one person keeps patching it
The sentence we hear first is always the same: we cannot upgrade. Somewhere in the system there are custom modules that override core methods, fields added through the interface that nothing documents, and a report that is a copy of a standard report with three lines changed. Every one of those was a reasonable decision on the day it was made. Together they are why a version upgrade gets quoted as a second implementation.
The second symptom is the developer. Invoices cannot be posted on a day he is unreachable, because posting runs through something he wrote. Nobody else has read the code, there is no repository history worth the name, and the test for whether a change is safe is that it seemed fine yesterday.
Meanwhile you are three or four releases behind. Features you paid to have built have since shipped in standard Odoo, and you are still maintaining your own copy of them.
Odoo rescue: what an inventory of a bad implementation finds
Before recommending anything we read what is actually installed. Every custom module is sorted into three piles: delete, because standard Odoo now does it; keep, because the business genuinely differs; rewrite, because it works today and will not survive an upgrade in its current shape.
Then the data. Duplicate partners, entries posted directly against control accounts, stock that has been adjusted rather than corrected, and an access model where everyone is an administrator because that was faster than configuring groups. Access rights are where the audit findings come from later.
The output is a written position: what your Odoo is, what it costs to keep it as it is, and what an upgrade would actually involve. Some companies read that and decide to stay where they are for another year. That is a legitimate answer and we will say so in the report.
Who should call an Odoo implementation partner in the UAE, and who should not
Mid-sized manufacturers, contractors, trading companies and service firms across the UAE and the wider GCC — usually more than one company in the group, running in Arabic and English, needing VAT handled properly rather than bolted on afterwards. Companies whose first Odoo implementation was done cheaply and has become the constraint.
Also companies still choosing. Hanwha Group's UAE branch ran a selection against SAP before deciding; that is a fair comparison to make, and we would rather you make it with the real trade-offs in front of you than be talked out of it.
Who should not call: if you are five users on standard Odoo, invoicing and nothing else, and it works, you do not need an implementation partner. You need a bookkeeper who knows the product. And if what you want is Odoo rewritten until it is a bespoke application with an Odoo login screen, we are the wrong firm. That project has a known ending and we have been called in to clean it up more than once.
Configuration before customisation, and an upgrade path that survives
Every requirement goes through the same three questions. Does standard Odoo already do this. Does it do something close enough that the process should change instead. Or is this genuinely how your business differs from everyone else's. Only the third pile gets code, and it is always smaller than the first workshop suggests.
Where code is written it is a proper module with its own manifest, data files and tests, sitting alongside core rather than inside it. That is the difference between an upgrade being a project and an upgrade being a week of testing.
Your own team is trained to run day two. Silvertex uses close to the full application set across nine branches in five Gulf markets, and that works because the branches operate the system themselves — we run the software and its maintenance underneath, not the operation.
What determines the cost of an Odoo implementation
How many applications go live, how many companies and currencies, how much of the data is fit to migrate, how many integrations have to survive, and how much genuine customisation remains once the design is finished. Licence cost is the smallest and most predictable part of the total, and it is the only part most quotations discuss at length.
A rescue is priced differently. The first step is a fixed-price assessment of what you already have, because nobody can honestly quote an upgrade of a system they have not read. Only after that is there a scope worth putting a number against.
Either way you get a written diagnosis and then a fixed scope at a fixed price before any delivery commitment. No day-rate meter running against an open backlog.
How the engagement runs
- 01
Diagnose
Two weeks inside your operation. We map how the work is actually done, where two systems disagree, and what each gap costs you in a month.
- 02
Architect
A target design tied to operating decisions: which system holds which truth, who owns it, and what has to be true before go-live.
- 03
Implement
Delivery in phases you can stop after. We train your team to run it, because a system that only we can operate is a system you do not own.
- 04
Govern
The part everyone skips. Ownership, review cadence and metrics, so the system does not quietly decay back into chaos.
Questions
What people ask before they start this work
How much does an Odoo implementation cost?
It depends on scope, and we quote scope rather than hours. The drivers are the number of applications, the number of companies and currencies, the state of the data being migrated, the integrations that have to keep working, and how much genuine customisation is left after design. You get a written diagnosis and a fixed scope at a fixed price before committing to delivery. Licences are a separate and much smaller line.
How long does an Odoo project take?
The duration is set by how many applications go live together, how many legal entities are involved, and how quickly decisions get made on your side. Finance and inventory for one company is a different job from manufacturing, projects and payroll across a group. We phase it so the first phase is usable on its own, which matters more than the end date on a plan nobody will hold to.
Should we run Odoo Community or Enterprise?
It depends on which applications you actually need, not on principle. Some functions people assume are standard are only in Enterprise, and some companies pay for Enterprise and use nothing that requires it. We work out which features your processes genuinely depend on, then tell you which edition that implies. If Community covers you, we will say so even though it lowers the value of the deal.
We already have Odoo and it works. What would you change?
Possibly nothing. If your Odoo is on a supported version, your customisations are packaged properly and your team can run it without calling a developer, there is no work here worth buying. The reason companies call us is usually the opposite: an upgrade that has become impossible, or one person who is the only route into the system. We will tell you which of the two you are.
Who owns the code, the database and the hosting?
You do. Any module written for you is delivered as source in a repository you control, the database is yours, and hosting sits in your own accounts or in a provider you contract with directly. Documentation is written so a developer who has never met us can take the system on. If we are the only firm able to change it, we have sold you a dependency rather than a system.
Can you upgrade us without losing our customisations?
Usually, but not blindly. The assessment sorts your customisations into what standard Odoo now covers, what must be kept, and what has to be rewritten to survive future releases. Some of what exists should be deleted rather than carried forward, and deleting it is the cheapest part of the upgrade. We will not promise an outcome before reading the code.
Do you handle Arabic and UAE VAT properly?
Yes, and both are design decisions rather than a final-week task. Arabic and English run side by side for users, documents and reports. VAT is configured per entity and per transaction type, including the treatment that differs between free zone and mainland companies. We deliver in Arabic and English across the UAE, Saudi Arabia, Qatar and Oman, so the localisation questions are the ones we work on daily.
Odoo Implementation
Start with a diagnosis
Tell us the symptom in one line. We will come back with what we would look at first and what it would take.
Monday to Friday, 9:00 AM – 6:00 PM (GST)
Prefer we call you?
Leave your WhatsApp number and we will reach out.