The default Odoo answer to "should we customize?" from most vendors is "yes, and here's a quote." That's often wrong. Here's how we actually decide.
Adapt your process when:
- The Odoo standard flow works, you just haven't seen it configured for your case yet.
- Your current process is idiosyncratic because of a previous system's limitations, not because your business genuinely requires it.
- The customization touches core accounting or inventory locking flows — the risk of breaking upgrades is real.
- The people who benefit from your current way of doing it are leaving in six months anyway.
Customize Odoo when:
- The customization is genuinely a competitive advantage — how you price, how you allocate stock, how you decide what to make.
- The standard flow adds three clicks per transaction and you do that transaction thousands of times a day.
- It's a regulatory requirement your industry has and Odoo's stock localization doesn't cover.
- It's a well-scoped, isolated change with clear boundaries.
A worked example
A client asked us to build a custom "sales team" hierarchy with five levels because that's how their org chart looked. We asked: does the hierarchy affect commission calculation? (No.) Does it affect access rights? (No.) Does it affect reporting? (Only visually.)
Answer: don't customize. Use Odoo's two-level sales team + tags to represent the middle levels. Save 40 hours of custom development and every future upgrade. Their org chart didn't change; how they modeled it in Odoo did.
The default should be adapt
Custom code is a permanent obligation: every future Odoo upgrade has to check compatibility, every future dev has to understand it, every future bug might involve it. That's not free. Customize when the payoff is worth the ongoing carrying cost.