Odoo services · Odoo Support & Maintenance
Support that knows your configuration.
Go-live is the middle of the project, not the end. Teams change, processes shift, Odoo releases a new version. Support is what keeps the system matching the business a year later instead of slowly drifting away from it.
—— Where it hurts
The problems this work actually solves.
Odoo rarely fails on day one; it drifts in year two, one slow report and one unnoticed failed backup at a time. These are the problems a support plan exists to catch early.
The partner who disappeared
The company that implemented your Odoo finished the project and moved on. Emails go unanswered, small fixes take weeks, and nobody on your side holds the passwords or the documentation. You are running a business on a system no one maintains.
How we handle itWe take over through an audit that documents everything before we accept responsibility. From then on, your requests reach a team with the record in front of them.
Slowdowns nobody can explain
Odoo that was fast at go-live takes ten seconds to open a sales order two years later. The database has grown, scheduled jobs have piled up, and the server settings were never revisited. Users start blaming the software and drifting back to spreadsheets.
How we handle itWe measure before we touch anything — slow query logs, worker configuration, scheduled job load. Then we fix the cause, which is rarely "buy a bigger server".
Errors users have learned to live with
Staff click past the same error message every morning and keep a side spreadsheet for the part that never worked. None of it reaches anyone who could fix it. The system loses trust one workaround at a time.
How we handle itThe baseline audit collects these known errors and we fix them in priority order. Staff get a direct channel in Thai or English, so the next problem gets reported instead of tolerated.
Upgrades postponed for years
You are three or four versions behind. Security fixes for your release have stopped, third-party modules no longer get updates, and every year of waiting makes the eventual jump bigger. Nobody wants to be the one who schedules it.
How we handle itThe quarterly review states plainly when an upgrade is worth scheduling and what it will involve. When it happens, it happens on a test copy first, with a written scope.
Everything lives in one admin's head
One person knows the server passwords, the customisation history, and why one scheduled job must never run before six in the morning. When they resign — and eventually they will — the company inherits a black box.
How we handle itWe document the configuration up front and log every resolution afterwards, so the knowledge lives in a record your company owns, not in anyone's memory.
—— Learn from other projects
Mistakes we see, and how to avoid them.
Waiting for something to break
Purely reactive support means the first sign of trouble is a user who cannot work. By then the failed backup is three weeks old and the disk has been full since Tuesday. We monitor uptime, backups, integrations and disk headroom so most problems are fixed before anyone has to report them.
Assuming the backup works
A backup job configured at go-live and never tested is a hope, not a plan. Companies discover the archive is empty or corrupt at the worst possible moment: during the restore. We test-restore your backups on a schedule and show you the result, so the first real restore is never the first attempt.
Handing out admin rights to end the conversation
Every time a permission error blocks someone, the quickest fix is to make them an administrator. Two years later half the company can delete journal entries and the audit trail means nothing. We review access rights during the baseline audit and fix the underlying permission instead of escalating around it.
Changing production directly
Quick fixes applied straight to the live database feel efficient until one of them takes down invoicing on the last day of the month. An untested change is the easiest way to turn a small bug into a company-wide outage. Every patch, module update and fix we make goes through a staging copy of your database first.
Buying hour blocks instead of responsibility
Prepaid hour bundles reward slow work: the harder the fix drags on, the more the vendor earns. They also make you hesitate to report small problems, which is exactly when problems are cheap to fix. Our plans are flat monthly with no per-ticket charges, so reporting early costs you nothing.
—— Ways to engage
Three ways to start with us.
System health audit
A fixed-scope review of an existing Odoo instance, priced in writing before we start. You get a report you own, whether or not you ever hire us again.
- Inventory of configuration, customisations and integrations
- Performance, security, access rights and backup check
- Prioritised fix list with an effort estimate for each item
Monthly support plan
Ongoing responsibility for keeping your Odoo healthy — fixes, monitoring, patches and upgrade planning under one flat monthly fee, in Thai and English.
- Bug fixes and user questions answered by people who know your setup
- Monitoring with alerts, and backups test-restored on schedule
- Quarterly review covering incidents, changes and upgrade timing
Takeover and stabilisation
For instances the original implementer abandoned or left unstable. We document what exists, stop the bleeding, and only then move you onto a standard plan.
- Documented baseline before we accept responsibility
- Stabilisation backlog worked in priority order, scoped in writing
- Handover into the monthly plan once the system is stable
Your implementation partner
A partner, not a licence reseller.
We are not chasing licence volume — we design, build and stay accountable for systems that companies run their operations on. The consultant who scopes your project stays through go-live and the support that follows, and everything we commit to is written into a fixed scope per phase.
—— What done looks like
Outcomes you can verify yourself.
A system someone else could take over
Your configuration, customisations and integrations are documented in a form any competent team could pick up — including one that is not us. That documentation is yours, and you can check it exists at any time.
Restores you have seen succeed
Backup restores are tested on a schedule and the results are reported to you, not just filed. Before a real incident ever happens, you already know recovery works and how long it takes.
A fix history your company owns
Every incident and its resolution is logged where you can read it. When staff change — yours or ours — the history stays.
Upgrades on a calendar, not in a crisis
Version decisions become a standing item in the quarterly review, with the trade-offs written down. You choose the timing with facts in front of you instead of being forced by an end-of-support date.
—— How we work
What the engagement looks like.
Documented baseline
We document your configuration, customisations and integrations before taking over, so nobody is guessing during an incident.
Monitoring and alerts
Uptime, backup success, integration health and disk headroom are watched. You hear from us before your customers do.
Quarterly review
What broke, what changed, what to plan for. Including whether a version upgrade is now worth scheduling.
—— Why us
What you get that you would not elsewhere.
Bilingual, in your hours
Thai-language support from the Thailand team; US and India offices cover the rest of the clock.
Backups you have restored
We test-restore your backup on a schedule. An untested backup is not a backup.
No ticket theatre
You reach a person who knows your setup, not a queue that asks you to describe it again.
Not sure where to start? A short call sorts it.
Talk to an Odoo specialist ➜—— Why us
What working with us is actually like.
The person who audits is the person who answers
We assign one consultant to your account, the same way our projects keep one consultant from first call through go-live. The person who documented your system is the person who answers when it breaks.
An Official Odoo Partner
We hold Official Odoo Partner status through the India programme. That means partner access to Odoo's releases and resources, and an accreditation we have to keep earning — not a logo bought once.
Thai and English, both native
Support requests are answered in the language they arrive in. Our Bangkok team writes Thai natively — your accountant does not have to compose an error report in English to be understood.
Three offices, one shared record
Bangkok, New York and Delhi NCR cover different hours of the same day. Every incident is logged in one shared system, so the office that wakes up next reads exactly where the last one stopped.
Out-of-plan work is scoped in writing
When a request goes beyond the plan — a new report, a new integration — you get a written scope and price before work starts. Support fees never quietly grow into project fees.
No margin on your licences
Odoo Community costs $0 and we say so. If Enterprise fits you better, Odoo bills you directly and we add nothing on top — so our advice about editions has no commission behind it.
We support systems we did not build
Support work often starts on someone else's implementation. We do not insist on rebuilding it our way first; we document what exists and improve it where the audit says it matters.
Boring on purpose
Patches go through staging, restores are rehearsed, changes are logged. None of this is exciting, and that is the point — the best support months are the ones where nothing surprising happens.
—— Partner tiers, explained
What an Odoo partner tier does and does not tell you.
Odoo ranks partners by certifications held and licence volume sold. A tier signals commitment to the programme — it does not tell you who will actually staff your project. Ask that question of any partner, including us.
Learning Partner
New to the programme, building their first certified consultants and reference projects. Not a red flag — everyone starts here — but ask for hands-on proof.
Official Partner
Certified consultants and active delivery. This is where we sit, enrolled through the India programme, delivering from Thailand, the USA and India.
Silver & Gold
Higher tiers earned mainly through licence sales volume and headcount of certified staff. A strong signal of scale — not automatically of fit for your project.
—— Who this is for
Built for your size, not resized for it.
Growing companies (5–100 people)
For companies of 5 to 100 people, a support plan does the job of the IT hire you cannot justify yet.
- You run Odoo without full-time IT staff, and every problem currently lands on the owner or the accountant.
- Your original implementer has gone quiet and small fixes wait for weeks.
- You are on Community edition and want support without pressure to buy licences you do not need.
- You want help in Thai, during Bangkok hours, with answers in writing you can keep.
Mid-market (100–500 people)
For companies of 100 to 500 people, support keeps your IT team on infrastructure and strategy instead of inside Odoo tracebacks.
- Your IT team is capable, but Odoo internals — the ORM, cron jobs, module conflicts — are not their day job.
- Downtime now has a measurable hourly cost across several departments at once.
- Auditors and key customers ask for evidence of backup tests, patch schedules and access control.
- You carry enough customisation that upgrades need a plan and a staging pass, not a weekend.
—— Risks
What usually goes wrong — and how we prevent it.
Tickets answered by strangers
Helpdesks that do not know your configuration relearn it on your time. Your requests go to people who already know your setup.
Patches that never land
An unpatched system accumulates risk quietly. Security patches are applied on a schedule and tested in staging first.
Fixes that live in one head
If the fix history lives in one person, staff change becomes an outage. Every resolution is logged so the history survives.
—— Pricing
What this costs.
Monthly plans scaled to user count and integration complexity. No per-ticket charges — that would penalise you for telling us something is wrong.
—— Editions & hosting
Community, Enterprise, and where it runs.
The licence and the hosting are separate decisions, and both are yours — we implement either edition and hand over whichever infrastructure you choose.
$0 licence
Odoo Community
Open source and free to license. Covers sales, purchasing, inventory, invoicing, manufacturing and more. You pay for implementation, not rent.
Per user, billed by Odoo
Odoo Enterprise
Adds studio, advanced accounting and localisations, mobile apps and official support. Billed by Odoo directly — never marked up by us.
Odoo.sh · VPS · on-premise
Your server or the cloud
Odoo.sh, a VPS we manage, or your own hardware. We recommend based on your compliance and budget, then document the choice so it stays portable.
—— The toolkit
What this service usually touches.
—— Related
Explore what else we do.
—— FAQ
Questions teams ask about this service.
Do you support Odoo you did not build?
Yes. It starts with an audit so we can document what exists. Occasionally that audit finds enough accumulated debt that repair is the honest first recommendation.
Are version upgrades included?
Standard upgrades are. Upgrades complicated by heavy third-party customisation are quoted separately, and we tell you which case you are in during the audit — not after.
How fast do you respond?
Response targets are agreed per plan and per severity, in writing. A production outage gets worked immediately by whichever office is on duty; a cosmetic report issue gets scheduled. We would rather set targets we can keep than advertise one impressive number that quietly measures only the first acknowledgement.
Do you support Odoo Community edition?
Yes, fully. The Community licence costs $0 and for many companies it is the right answer, so we will not use support as a lever to sell you Enterprise. If Enterprise genuinely fits better, Odoo bills you directly and we never mark it up.
Can our internal IT team stay involved?
Yes, and it usually works well. A common split is your team keeping servers and networks while we handle Odoo internals — code, configuration, upgrades. Everything we do is logged where your team can read it, so nothing becomes invisible to them.
Do we have to move to your hosting?
No. We support Odoo where it already runs — Odoo.sh, your own cloud account, or a server in your office. Managed hosting is a separate service you can add if it helps, not a condition of support.
What happens if we decide to leave?
You keep everything: the documentation, the fix history, and full access credentials. We hand over to your next team in an orderly way, with no exit fee and nothing held hostage — a client who can leave easily is the only kind we want to keep.
Let's find out whether Odoo actually fits your business.
A short call, an honest answer. If it isn't the right system for you, we'll say so.