Skip to content
ERP Builders
ERP Development

Odoo Studio vs Custom Code: Where to Draw the Line

What Odoo Studio does well, where it creates trouble, and when to switch to custom module development. A practical decision guide with examples.

By ERP Builders Team2 min read

Odoo Studio lets non-developers add fields, change views, build simple apps and set up automations, all through the browser. It's genuinely useful. It's also easy to overuse.

What Studio is good at

  • Adding fields to forms and lists, such as a "Customer PO reference" on sales orders
  • Rearranging views: moving fields, hiding ones nobody uses, adding tabs
  • Simple reports: tweaking document layouts
  • Simple automations: send an email, set a field, create an activity when a condition is met
  • Small standalone apps, like an equipment register or a request log

For these, Studio is faster and cheaper than a developer, and the business can make the changes itself.

Where Studio gets risky

  • Complex logic. Multi-step calculations, validations across several models, conditional behaviour. Automated actions with Python code work, but they're hard to test and review.
  • Many interdependent automations. Five automations firing on the same record update, in an order nobody can quite explain.
  • Performance-sensitive changes, like computed fields on large tables.
  • Integrations. Anything talking to external systems belongs in code with proper error handling.
  • Changes nobody documented. Studio makes changes easy to make and easy to forget.

A simple decision guide

RequirementUse
Add a field, show it on a form or reportStudio
Hide or rearrange fieldsStudio
Simple notification or activityStudio automation
Validation involving one or two fieldsStudio, carefully
Logic spanning several modelsCustom module
Anything financial or stock-affectingCustom module, with tests
Integration with another systemCustom module
Changes that need code review and version controlCustom module

Govern Studio use

If you allow Studio, set a few rules:

  1. Only named people use it, and changes are logged somewhere
  2. Test in staging first, especially before an upgrade
  3. Review quarterly: remove fields nobody uses
  4. Name fields clearly so they make sense in exports and reports

Upgrades

Studio customisations are generally carried through upgrades by Odoo's upgrade service, but they still need testing. Python code in automated actions is the part most likely to break.

Our approach

We use Studio for the light stuff and custom modules for anything with business logic. We also teach key users to use Studio safely, so they're not waiting on a developer for every small change.

See Odoo custom module development for the coding side, or our Odoo customization service.

Frequently asked questions

Is Odoo Studio available in Community?

No. Studio is part of Odoo Enterprise.

Can Studio changes be moved to a custom module later?

Yes. Studio customisations can be exported as a module, and a developer can rewrite them cleanly. It's easier when Studio use has been modest.

ERP Builders Team

Articles written and reviewed by the ERP Builders delivery team — functional consultants, solution architects and developers who implement, integrate and support ERP systems.

Related articles

ERP Development3 min read

Odoo 20 Access Rights: Migrating to ir.access

Odoo 20 removes record rules and merges them into access rights with domains. What changed, how to migrate ir.model.access.csv and ir.rule, and what to test.

Next step

Turn the plan into a working system.

Book a consultation with an ERP consultant. No sales script — just an honest look at your situation.