“Customization” and “configuration” get used interchangeably in conversations about Odoo, but they’re genuinely different things with very different cost, risk, and upgrade implications. Knowing which one you actually need before starting a project saves both time and money.
What configuration means
Configuration is working within Odoo’s existing settings and options — enabling or disabling features, setting up automated actions through the standard interface, defining pricelists, configuring approval workflows, adjusting field visibility through Studio. None of this touches Odoo’s underlying code. It’s the equivalent of adjusting settings versus rebuilding the software.
What customization means
Customization means changing Odoo’s actual code or data structure beyond what configuration options allow — building a new module, adding custom fields with logic Studio can’t express, modifying core views or workflows, or integrating with external systems that don’t have a built-in connector. This requires development work and, unlike configuration, has real implications for how upgrades work later.
Why this distinction actually matters
Configuration changes are generally safe across Odoo version upgrades — they’re stored as data, not code, so Odoo’s upgrade process handles them automatically. Customizations, especially ones that modify core behavior, need to be reviewed and often reworked during a major version upgrade, since the underlying code they were built against may have changed. This is one of the most common sources of unexpected upgrade cost we see, and it’s avoidable by knowing upfront which category a given change falls into.
How to tell which one you need
A useful test: if the change is possible by clicking through Odoo’s settings, technical menus, or Studio, it’s configuration. If it requires someone to write and deploy code — a new Python model, a modified view template, custom business logic beyond what Studio’s no-code tools support — it’s customization. When in doubt, it’s worth having a developer confirm before assuming a request requires custom code, since configuration options cover more ground than most people expect.
Frequently Asked Questions
Can Odoo Studio handle most customization needs without code?
Studio covers a meaningful range of customization — custom fields, views, and basic automation — without writing code, but it has real limits for complex business logic, which is where true development-based customization comes in.
Does configuration ever require a developer?
Not typically, though complex configuration (multi-company setups, advanced pricelists, intricate approval chains) benefits from someone experienced with Odoo’s data model, even without writing custom code.
Is it cheaper to configure around a limitation than to customize?
Usually yes, and it’s also lower-risk for future upgrades. We generally recommend exhausting configuration options before reaching for custom development, unless the configuration workaround creates more operational friction than the customization would cost.
Get the Right Approach for Your Requirement
Knowing whether you need configuration or customization before starting saves real time and avoids unnecessary development cost. Talk to Mediod Consulting about scoping your requirement correctly from the start.
