Customisation
Customisation, only when standard cannot.
Custom modules, Studio extensions, and bespoke UX, used sparingly and reversibly. Every customisation we ship is documented, version-controlled, automated-tested where it matters, and upgradeable to the next Odoo release without rewrites.
Right for you if
- Standard Odoo cannot model a process that genuinely is your differentiator.
- You are willing to live with a small number of carefully-built customisations rather than a sprawl of clever workarounds.
- You want to see a written impact assessment before any custom code lands.
Not right for you if
- You want to recreate the exact UI of a legacy system you are replacing. Configure to fit Odoo first; everyone is happier.
- You want a partner who will say yes to every customisation request. We will say no when it costs you future flexibility.
Methodology
How a Customisation engagement actually runs.
5 phases. Every artefact written down, every decision logged, every handover documented.
-
01
Audit
We confirm the standard product genuinely cannot do what you need. About a third of customisation requests stop here, replaced by a configuration change.
-
02
Design
A written design note with data model, UX, and migration plan. Reviewed with you before code is written.
-
03
Build
Implemented as a standalone module in a Git repo you own. Linted, type-hinted, automated-tested where the logic matters.
-
04
Test
Unit tests for logic, integration tests for the flow, manual UAT with your team in a sandbox.
-
05
Document
Module README in your repo, end-user notes in your runbook, upgrade caveats listed for every Odoo version we support.
What you receive
Deliverables.
Every artefact handed over to you. Code, configuration, documentation, training material. Yours to keep, yours to share with any successor.
- Custom module in your Git repository
- Design document and decision log
- Automated test suite covering the new logic
- End-user and administrator documentation
- Upgrade compatibility notes per Odoo version
Frequently asked
Questions about Customisation.
When is customisation the right call? +
When a process is a genuine differentiator and standard Odoo would force you to compromise on it. We refuse customisation when it solves a process problem better fixed by changing the process, or when the saving is smaller than the future maintenance cost.
Will customisations break when Odoo upgrades? +
Almost never, because we build them as standalone modules with explicit upgrade notes per Odoo version. We test against the next major release before it is published. Worst case is a few hours of upgrade work, never a rewrite.
Do we own the custom code? +
Yes. Code lives in your Git repository under your licence. We retain no rights to it. Hand it to any successor partner and they can read it.
Can you adapt a custom module written by a previous partner? +
Often yes. We audit it first, fix obvious issues, and either keep it or rewrite cleanly with your sign-off. See also our Rescue service.
Other services
Pair Customisation with one of these.
Tell us about your Customisation project.
A short note is enough. We answer in person, within one business day.