Clean Odoo customisation is not a slogan about saying no to every useful change. It is a delivery discipline: keep the platform stable, make extensions deliberate, and give the business a clear path for improving daily workflows.
Start With The Operating Pressure
Automotive teams often customise because the pressure is immediate. A dealer cannot see the right stock position. A finance team cannot explain margin movement. A warehouse process needs an exception path that the original design never considered.
The customisation conversation should start there, not with an abstract architecture rule.
Separate Workflow From Platform Risk
Some changes belong in Odoo configuration. Some belong in extension services, portals, or integration layers. Some should be removed because they encode a workaround that no longer serves the business.
The practical work is deciding which is which, then documenting that decision well enough that future teams can support it.
Keep Governance Visible
An Odoo governance programme needs a small number of visible rules:
- what can be configured in the core
- what must be built as an extension
- how integration ownership is assigned
- how exceptions are reviewed before they become permanent
That level of discipline keeps the platform easier to upgrade while still letting the business move.