Skip to main content
Odoo // Support

Your Odoo, looked after. So you can stop refreshing it.

Predictable monthly plans covering bug fixes, security patches, performance work, and monitoring. Your team runs the business; we keep the ERP healthy.

Plans
Essential · Growth · Enterprise
Includes
Patching · fixes · monitoring
Reporting
Monthly health report

Written scope, defined response times, and monitoring that spots trouble first.

An ERP is never finished

After go-live, the work changes shape rather than stopping. Odoo ships fixes and security updates, operating systems need patches, data grows, people find new edge cases, and the business itself changes: a new warehouse, a new tax rule, a new product line.

Without a plan, that work happens in bursts: an urgent call when month-end breaks, a scramble before an audit, an upgrade postponed until it becomes a project of its own. A support plan turns it into a steady, predictable rhythm with a team that already knows your system.

Good support is mostly invisible: fewer surprises, faster fixes, and an upgrade path that stays open. You notice it mainly by what doesn't go wrong.

Three plans, clear scope

No ambiguous retainers. Every plan has written scope and a response target.

Essential

$500/ month

For stable instances that need a reliable backstop.

  • Bug fixes and configuration corrections
  • Email support
  • Critical issues handled immediately
  • Other requests answered within 12 business hours
  • Quarterly health check
  • Security patch notifications
Popular

Growth

$700/ month

For growing teams with custom modules.

  • Everything in Essential
  • Performance optimization
  • Priority queue
  • Security patches applied
  • Monthly health report
  • Slack or Teams channel

Enterprise

Custom

For mission-critical deployments.

  • Named engineer
  • Contractual response times
  • Proactive monitoring dashboards
  • Weekly check-in
  • Out-of-hours emergency cover
  • Priority development queue

How requests are prioritized

Severity decides the order of work. Response targets per plan are written into your agreement.

SeverityExampleHandling
CriticalOdoo is down, or invoicing or shipping is blockedImmediate triage and a workaround first, then the root-cause fix
HighA key workflow fails for some usersSame-day investigation within the plan's target
NormalA report is wrong or a screen errors in an edge caseScheduled into the next available hours
RequestA small change or new fieldEstimated, approved, then scheduled

Covered vs. not covered

Included in every plan

  • Security patches and Odoo point releases
  • Custom module bug fixes
  • Server monitoring and alerting
  • Automated database backups
  • Configuration corrections

Quoted separately

  • New feature development
  • Cloud hosting costs
  • Third-party subscriptions
  • Major version upgrades

How we spot problems before you do

Uptime & latency checks

External probes on login and key pages, with alerts on failure or slowdowns.

Database health

Slow-query logs, table bloat, disk growth, and backup verification.

Server metrics

CPU, memory, disk, and worker saturation dashboards with sensible thresholds.

Scheduled actions

Alerts when cron jobs fail, stall, or start running long.

Security updates

Odoo and operating-system patch tracking with scheduled application.

Monthly report

What happened, what we fixed, what's trending, and what we recommend next.

Onboarding an existing instance

Supporting a system someone else built starts with understanding it.

  1. Step 01

    Access & inventory

    Hosting, repositories, modules, integrations, and scheduled jobs documented in one place.

  2. Step 02

    Health audit

    Code review of custom modules, database health, backup tests, and security settings.

  3. Step 03

    Monitoring setup

    Probes, dashboards, and alert routing configured for your instance.

  4. Step 04

    Runbook

    Known issues, recovery procedures, and contacts written down so nothing depends on memory.

What's in the monthly health report

SectionWhat it tells you
AvailabilityUptime, incidents, and their root causes
PerformanceSlowest workflows and trends over the month
RequestsWhat was asked, fixed, and is still open
SecurityPatches applied and pending, with risk notes
BackupsBackup success and the latest restore test
RecommendationsImprovements worth scheduling next

How patches are applied

Updates are tested before they touch production, never applied blind.

  1. Step 01

    Track

    Watch Odoo releases and operating-system advisories for anything affecting your instance.

  2. Step 02

    Stage

    Apply the update to a staging copy and run your module tests and smoke checks.

  3. Step 03

    Schedule

    Agree a low-traffic window with your team, with a verified backup taken just before.

  4. Step 04

    Apply & verify

    Update production, re-run smoke checks, and confirm in the next health report.

Choosing a plan

Essential suits stable instances with few customizations, where support is mainly a safety net. Growth fits active teams with custom modules and a steady stream of small improvements. Enterprise is for deployments where downtime stops revenue, and you want a named engineer who knows the system as well as your own team does.

Support myths

Myth: If it's working, it doesn't need maintenance.

Reality: Unpatched systems and untested backups work fine right up until the day they don't. Maintenance is cheaper than recovery.

Myth: Support is just for emergencies.

Reality: Most of the value comes from small, steady improvements and catching problems early, not from the occasional fire drill.

Myth: Any developer can support any Odoo.

Reality: Custom modules, integrations, and data history make every instance unique. Context is what makes support fast.

Our backup policy

  • Daily database and filestore backups, kept together
  • Copies stored off the production server and account
  • Retention agreed with you, with older copies thinned out
  • Restore tests on a schedule, not just backup success checks

Who you'll work with

A consistent team

The same small group of engineers handles your requests, so context isn't lost between tickets.

A named lead

Your point of contact for priorities, the monthly report, and anything that needs a decision.

Senior reviewers

Every fix to custom code is reviewed before it reaches production.

On-call cover

For Enterprise plans, an engineer is reachable out of hours for critical incidents.

Why maintenance includes upgrades and restore tests

Odoo supports each major version for three years, and Odoo Online makes a major upgrade mandatory every two yearsSource [1]. Support that only fixes bugs leaves you facing a large, rushed upgrade later. We plan upgrades into the support calendar, review custom modules against each new release, and test the upgraded database before production.

Backups get the same treatment. PostgreSQL's own documentation advises setting up and testing the archiving procedure before relying on it, and keeping several backup sets to be certain you can recoverSource [2]. Our health checks include scheduled restores, so recovery is a rehearsed procedure rather than a hope.

Switching from another partner?

We'll handle the handover: collecting access, code, and documentation, auditing the instance, and setting up monitoring, so there's no gap in coverage while support moves over.

Frequently asked questions

Do you support the hosting too?
Yes, for self-hosted and cloud instances: server patches, monitoring, backups, and capacity. Hosting costs themselves are billed by the provider.
What if we need more hours one month?
Extra hours can be added for a busy month and billed separately, or we can schedule larger work as a small project.
Do you support custom modules you didn't write?
Yes, once they're reviewed during onboarding. High-risk modules may need fixes before we can support them within response targets.
Can support hours be used for small improvements?
Yes. Growth and Enterprise plans are designed for exactly that: steady, small changes alongside fixes.
Is there a minimum term?
Plans run month to month after onboarding. Some Enterprise arrangements use longer terms for dedicated capacity.
What happens to unused hours?
Plans are capacity reservations. Unused hours don't roll over by default; we review usage monthly and adjust your plan if it's consistently too big or small.
Can you support an instance another partner built?
Yes, after the onboarding audit described above, so we understand the custom code, hosting, and integrations before we're on the hook for them.
Are response targets guaranteed SLAs?
Targets and any contractual SLA terms, including remedies, are written into your support agreement.
Do you support Odoo.sh and Odoo Online?
Yes, with the access each platform allows. Self-hosted instances get the full monitoring setup.
Are major version upgrades included?
No. They're projects of their own with an audit, porting, and rehearsals. Support plans keep you ready for them, and we quote the upgrade separately.
Can we switch plans?
Yes, at the end of any monthly cycle.
How do we raise a request?
Through your plan's channel: email, a shared Slack or Teams channel, or your ticketing system. Every request gets a reference and a status.
Are Odoo version upgrades included in support?
Planning and reviewing upgrades is part of every plan; the upgrade project itself is scoped separately because its size depends on your custom modulesSource [1].
Do you test our backups?
Yes. Scheduled restore tests are part of our health checks, following PostgreSQL's advice to test the backup procedure itselfSource [2].