Five industries worked hands on, so we arrive knowing where the gaps usually are.
All industries →Request a demoFour ERP platforms in house, and fifteen capability modules. The recommendation is never tied to a licence quota.
All solutions →Request a demoOne team from platform selection through to the reports on your desk.
All services →Request a demoGuides, how-tos, comparisons and a plain-English glossary, written by the consultants who deliver the projects. No form in front of any of it.
Nobody in UAE ERP publishes their tools or their pricing. We do both.
Free tools →Request a demoAn ERP and IT consultancy in Business Bay, Dubai, implementing Oracle, Microsoft, Odoo and SAP across the UAE and GCC.
Consultants in the UAE, technical team in South Asia. Cost stays sharp without cutting corners.
About QZ Infomatics →Request a demoOdoo systems rarely break. They drift — and by the time anyone notices,
nobody remembers how it was configured.
Odoo support covers user assistance, bug fixes, configuration changes, new reports, minor enhancements, module additions and version upgrades, under an annual maintenance contract with response times set by severity. QZ Infomatics supports deployments we built and deployments we did not.
Takeover
Stated plainly, because it is the reason most people land on this page: you do not need to have worked with us before. Taking over an existing Odoo deployment starts with a system audit.
The audit produces a realistic support price rather than a guess. It also almost always finds things nobody had flagged.
If you decide to stay with your current provider afterwards, you still have a documented picture of your own system — which most Odoo users do not have.
Scope
An annual maintenance contract is a yearly agreement covering support and upkeep for a fixed fee.
| Included in the AMC | Quoted separately |
|---|---|
| User support and issue resolution | New custom modules |
| Bug fixes and configuration corrections | Workflow redesign |
| New reports and views | Integrations |
| Minor enhancements within existing modules | Major data migration |
| Module additions and performance monitoring | Additional legal entities |
| Version upgrade support and refresher training | On-site training beyond the allowance |
Where that line sits should be agreed in writing before the contract starts. Arguments about whether something is “support” or “a project” are the most common friction in Odoo support relationships, and they are entirely avoidable.
Response
Ask any provider for these definitions in writing. A headline response time with no severity model behind it means very little, because everything becomes “high priority” at the point it matters.
System down, or payroll and statutory filing blocked. Everything else waits until it is cleared.
A functional error affecting a business process, with no workaround available to the users.
An error with a workaround available, scheduled rather than dropped into the middle of the day.
Enhancement and change requests, handled on a scheduled queue with a published order.
The response time committed against each severity, and the ticket or hours allowance at each contract tier, are written into your agreement before it is signed.
Upgrades
Odoo releases a major version each year, and the database moves to the new release before anything else is checked.
Annual release cycleEvery custom module and third-party module against the new release. Heavily customised deployments take longer, which is the recurring cost of over-customising.
And every third-party moduleBefore switching over, not after. Users test the processes they run daily rather than the ones the project remembers.
Users, not the project teamBusinesses that skip upgrades for three years do not save money. They accumulate a larger, riskier upgrade and lose access to fixes in the meantime. Odoo supports a limited number of prior versions.
Do not fall outside the windowCustomisation
Fields, workflows, approval rules, reports, views and full custom modules can all be built. That is a large part of why UAE businesses choose it.
Customisation is cheap to add and expensive to carry. The discipline is what keeps an upgrade from becoming a project.
Why it matters
And the new people are never trained properly, so the system is used the way the last person guessed it worked.
So finance rebuilds it in Excel, and the Excel version becomes the one the board sees.
Someone finds one for a broken workflow, and an upgrade gets skipped in case the customisations break. None of it appears on day one — it appears at year-end, when the auditor asks a question the system can no longer answer, and the business concludes that Odoo was the problem.
Support is priced annually on user count, number of modules and the amount of customisation in your deployment. Compare what is included rather than the headline figure: whether upgrade support, report changes and training days are covered makes a larger difference to the real cost than the rate does.
Odoo support FAQs
Odoo support covers user assistance, bug fixes, configuration changes, new reports and views, minor enhancements, module additions, performance monitoring and version upgrades. It is normally provided under an annual maintenance contract with response times agreed by issue severity rather than a single blanket target.
An Odoo AMC is an annual maintenance contract covering ongoing support and upkeep of your deployment for a fixed yearly fee. It typically includes an allowance of support hours or tickets, upgrade support and defined response times, with larger development work quoted separately as projects.
Because the system keeps changing after go-live: staff turnover brings new users, processes evolve, reports need adjusting and Odoo releases a new version each year. Deployments without support tend to drift — users work around problems, data quality degrades, and the system loses credibility within about a year.
Odoo releases a major version annually. Upgrading means migrating the database, retesting customisations and custom modules against the new version, fixing what broke, and validating with users before switching over. Heavily customised deployments take longer, which is the ongoing cost of over-customising in the first place.
Yes. It begins with an audit: how the system was configured, what was customised, which third-party modules are installed, what documentation exists and what condition the data is in. That audit sets a realistic support price and usually surfaces fixable issues the business had accepted as normal.
Support covers fixing what is broken plus small adjustments — a report column, a field, a permission. New modules, workflow redesign, integrations and custom development are projects and quoted separately. Agreeing where that line sits before signing prevents the most common friction in support relationships.
Response times should be defined by severity in the contract: a system-down or payroll-blocking issue as critical, functional errors as high priority, and enhancement requests on a scheduled queue. Ask for those definitions in writing, because a headline response time means little without them.
Support is priced annually on user count, number of modules and the amount of customisation in your deployment. Customised systems cost more to maintain because every upgrade requires retesting. Compare what is included — upgrade support, report changes, training days — rather than the headline figure alone.
Talk to a consultant
Book a free 30 minute call with QZ Infomatics in Dubai. You will leave it with a platform recommendation, the reasoning behind it, a realistic timeline and an indicative budget band — before you commit to anything.
