Assurance
Independent Odoo Assurance
Five fixed-scope, fixed-fee audits answering the questions nobody enjoys asking about their own work. You leave with a written finding, not a proposal.
See the five auditsAn integrator will not tell you their integration is brittle. A licence reseller will not tell you that you are paying for thirty seats too many. This is not dishonesty, it is incentive. You do not ask somebody to mark their own homework.
We also deliver Odoo projects, and we are not going to pretend otherwise. What we commit to is narrower and checkable: we do not audit our own delivery work, the audit price is fixed before we start, and it moves neither with what we find nor with who performs the remediation. If the report concludes that everything is fine, it costs the same.
Five audits
Each has a fixed scope, a fixed fee and a written deliverable. Take them separately or together.
Security and access audit
Who can see what, and what bypasses the ORM?
What forces itClient security questionnaires, insurer requirements, staff turnover.
See the detail →RPC integration migration audit
What breaks when the RPC endpoints go away?
What forces itOdoo documentation schedules removal of XML-RPC and JSON-RPC in Odoo 20, autumn 2026.
See the detail →Version and EOL exposure review
How long until you lose your upgrade path?
What forces itOdoo 17 leaves standard support in September 2026. Odoo maintains only the three most recent majors.
Quoted on requestData quality and migration assurance
Did the migration somebody else ran actually bring everything across?
What forces itIndependent verification of a migration performed by another firm.
Quoted on requestLicensing and spend audit
Are you paying for seats and modules nobody uses?
What forces itAnnual renewal, headcount growth, budget under pressure.
Quoted on requestThe most urgent of the five
Your RPC integrations have an end date
Odoo's documentation schedules the removal of the XML-RPC and JSON-RPC endpoints in Odoo 20, autumn 2026. Nearly every integration written in the last decade goes through them: Zapier, Make, n8n, your BI tooling, your warehouse scanners, the internal scripts nobody maintains any more.
The problem is not the migration itself. It is that almost nobody has inventoried their integration surface, and you cannot plan the replacement of something you have never listed. The audit produces that list: every caller, the user it authenticates as, what it reads or writes, and what it becomes after the cutover.
Scope the RPC auditHow an assurance engagement runs
The same shape for all five, so you know what you are buying before you sign.
Before you sign
Scope and fixed fee
A short call to bound the scope, then a firm price. It does not move afterwards, whatever we find.
Week 1
Read-only access
We work from a copy and read access. Nothing is written to your production system.
Weeks 1 to 3
The review
The analysis itself, run against a control set defined in advance rather than assembled as we go.
On delivery
Report and walkthrough
Prioritised findings, a remediation plan sized in effort, and a session with your team. What you do with it is yours.
What we commit to
Checkable commitments, not a claim of objectivity.
We do not audit our own work
If we delivered the system, we do not sell the audit that judges it. We point you at a third party.
The fee is fixed up front
It does not scale with the number of findings. A reassuring report costs the same as an alarming one.
No obligation to continue
The remediation plan can be run by your team, your current integrator, or us. The report does not lose its value if you pick somebody else.
The report is yours
Hand it to your insurer, your customer, your board or another supplier. Nothing in the engagement prevents that.
An audit says what needs to change. For it to stay true afterwards, see the fractional Odoo administrator.
Backed by real migrations
Numbers like yours, validated on real migrations
These are three engagements where the projection actually turned into operational reality on Odoo, and the full case studies live on the migration service page.
- ManufacturingV12 → V17
Industrial Manufacturer, Texas
12custom modules carried over, zero data lost
- DistributionV14 → V18
Wholesale Distributor, Quebec
30%faster page loads once the upgrade shipped
- Professional ServicesCE → Enterprise
Consulting Firm, Brussels
0hproduction downtime during cutover
Which one should you start with?
Tell us your Odoo version, user count and integrations. We will tell you which of the five matters for you, and if none of them does, we will say that too.
Frequently asked questions
01
You also deliver Odoo projects. How is the audit independent?
We are not claiming we do not implement. The independence is three specific, checkable things: we do not audit a system we delivered, the fee is fixed before we start and does not vary with the findings, and the remediation plan can be executed by anyone. If you want an auditor with no delivery arm at all, say so and we will point you at one.
02
Do we need all five audits?
No, and it would rarely make sense. Most companies have one or two that genuinely matter, depending on their Odoo version, their integrations and whatever prompted the question. We will tell you which before you pay for anything.
03
What if the audit finds nothing serious?
You get the same report at the same price, concluding that your configuration holds. That is a useful outcome: it is exactly what you hand to an insurer or a customer who asked the question.
04
Can you fix what you find?
Yes if you want us to, but the report is written to be executable by somebody else. The plan is sized in effort and describes the fixes precisely enough for your team or your current integrator to pick up.
05
How long does an audit take?
Depending on scope, one to four weeks from access to walkthrough. The timeline is fixed alongside the fee, before you commit.