An Odoo Team On Call, Not a Ticket Into the Void
Once Odoo runs your invoicing and dispatch, an unanswered issue costs real money. Our maintenance contracts give you named engineers, response times written into the agreement, monitored backups and version upgrades rehearsed before they reach your live database.
50+ ERP and software projects. Zero failed projects since 2021.
The cost of ERP downtime is not the fix, it is the wait
A blocked invoice on the last day of the month holds up dispatch, cash collection and the close behind it.
No explaining your business again on every ticket
You get the same small group of engineers month after month, with your apps, your custom modules and your integrations already in their heads. That is the difference between an issue resolved in an hour and one that spends the first day being understood.
- A named team, not a rotating queue.
- Your setup documented and kept current.
- Escalation path agreed before you need it.
Odoo covers the product, we cover your system
An Enterprise subscription pays Odoo for the licence and their own bug-fix support. It does not cover your configuration, your custom modules, your integrations or your hosting, which is where most real incidents start. Community customers have no vendor support at all, and this is what fills that gap.
- Cover for your configuration and custom modules.
- Your integrations and hosting included.
- Works alongside an Enterprise subscription or on its own.
Three levels of cover
Pick the one that matches how much of your operation depends on Odoo being available.
What happens when you raise an issue
What the contract covers every month
Ticketed help desk
Email and portal access with priorities and response targets written into the agreement.
Backups and restore tests
Daily backups that are verified, with a periodic restore proving they actually work.
Monitoring
Server resources, worker processes, scheduled actions and failing sync jobs.
Security patching
Odoo and operating system patches applied on a schedule, tested beforehand.
Version upgrades
Rehearsed on staging, checked against your modules, then scheduled with you.
Included change hours
A monthly block for small changes, new reports, access fixes and user questions.
What a real support contract gives you
Why teams choose TCB Infotech for Odoo support
Odoo support and AMC questions
What does an Odoo AMC actually cover?
Is this the same as an Odoo Enterprise subscription?
What response times do you commit to?
Do you support an Odoo database your team did not build?
Are Odoo version upgrades included?
What is not included in the contract?
Put Your Odoo on a Support Contract
Book a free consultation. Tell us which edition you run, how it is hosted and what has been going wrong, and we will recommend the plan that fits and what it should cost.
Book a Free Consultation →No commitment. An honest view of the cover you actually need.
What an Odoo Maintenance Contract Includes
A support agreement is only worth what is written into it. Here is exactly what we commit to, what we watch on your database, and what you receive each month.
Cover for the system, and time for the things you keep needing
Priorities and targets agreed before anything goes wrong
Issues are raised by email or portal and triaged against priorities you have already agreed, so nobody argues about severity during an incident. A named engineer who knows your setup picks it up, reproduces it on staging, and you can see the status at any point.
- Written response targets by priority level.
- A named team rather than a rotating queue.
- Diagnosis on staging, not experiments in production.
The work that stops incidents from reaching your users
We watch disk and memory, worker processes, the scheduled actions that quietly stop firing, and any failing sync jobs. Backups run daily, are verified, and are periodically restored to prove they work. Security patches go on in a tested, scheduled way rather than in a rush.
- Resource, worker and scheduled action monitoring.
- Daily backups with periodic restore tests.
- Odoo and operating system patching on a schedule.
Keeping up with the yearly release without a project each time
Version upgrades are rehearsed on a staging copy first, where your custom modules, QWeb layouts and integrations are tested against the new release. You get the report, then pick the window. Alongside that, a monthly block of hours covers the small requests that would otherwise queue for months.
- Upgrades rehearsed on staging with a rollback plan.
- Custom modules and integrations checked before you move.
- Included hours for reports, access rights and small changes.
Everything that comes with the contract
Written service agreement
Priorities, response targets, cover hours, escalation path and exclusions, all on paper.
Named engineers
A small assigned team, with a documented backup person so cover never rests on one individual.
Monthly report
Tickets raised and closed, response times met, changes released and any root cause findings.
Staging database
A maintained copy of production for reproducing issues and rehearsing every release.
Living documentation
Your apps, custom modules, integrations and runbooks kept current as the system changes.
Access you control
Your hosting, your repository, your credentials, with our access revocable at any time.