Implementation ends. The system does not. Odoo support is what keeps an ERP working after go-live — fixing what breaks, configuring what changes, applying updates, watching the server, and answering the question the accountant has at month end.
We publish what is in scope, what is not, and how fast we respond, so you are not negotiating during an outage.
Businesses whose Odoo we keep running
An Odoo AMC is an annual maintenance contract covering ongoing support for your Odoo ERP. It typically includes regular system updates, bug fixes, functional help, technical fixes to custom modules, server maintenance and a defined response time. The contract matters more than the brochure: what counts as a bug, what counts as a new requirement, and how quickly someone actually answers.
Ask any support provider one question first: is a version upgrade included, or billed separately? That single line is usually the biggest number in year two.
Four areas, each with its own scope. A support contract that says only “support” is how disagreements start in month three.
The non-technical side of your implementation: configuring and adjusting modules, workflows, approval rules, pricelists, taxes, reports and dashboards as your business changes. Most tickets are this, not code.
Custom module fixes, failing cron jobs, integration errors, performance problems and database issues. We work on your custom code whether or not we originally wrote it.
Backup verification — not just backup scheduling — security patching, resource monitoring, log review and restore testing. A backup nobody has restored is not a backup.
For businesses without an AMC: a diagnosis, a quote and a fix on a per-issue basis. Useful if you inherited an Odoo nobody has looked after.
We do not quote a support contract on a system we have not looked at. This is what the free diagnosis covers, and you get the findings whether or not you sign.
We restore your latest dump into a scratch database. A surprising number of businesses discover here that their nightly backup has been failing for months.
How far behind the current release you are decides both your security exposure and what an upgrade will cost. Three versions behind is a project; one is a weekend.
Which modules are custom, who wrote them, whether they are in version control, and which ones patch core. Core patches are the ones that will hurt at upgrade.
Cron jobs that error silently are the most common cause of “the system stopped syncing and nobody noticed”. We list every one that is failing or disabled.
Table sizes, slow queries, log volume and whether the mail queue is backing up. Performance complaints usually have one specific cause, not a general one.
Who has admin, which accounts belong to people who have left, and whether the database can be downloaded by anyone who should not be able to.
Whether you are paying for Enterprise users who no longer log in, or using Enterprise features on a Community database that will break on update.
Being explicit about this up front is why our support relationships last. These are chargeable as separate scoped work, quoted before we start.
A new module, a new integration, a new report that did not exist before. Fixing what broke is support; building what did not exist is a project.
Moving to a new Odoo major version with your customisations carried forward is its own scope. We price it on request so it is never a surprise.
If a paid app from the Odoo store breaks, we will diagnose it, but the fix belongs to its author. We tell you which it is.
Correcting records your team entered wrongly is billable work. We will usually show you how to bulk-fix it yourself instead.
AMC is quoted after the health check, because a clean standard Odoo and a heavily customised one are completely different support loads. These are the factors.
We support Odoo systems we did not build, including ones whose original partner has disappeared. The health check tells you the truth about what you own before either of us commits to anything.
Platform behaviour described here is documented by Odoo. The health-check list comes from the systems we have taken over.
The health check restores your backup, lists your custom modules, finds the cron jobs that are failing silently and tells you how far behind the current version you are. The findings are yours whether or not you sign anything.
