Skip to main content
odoocustomizationodoo-studiocustom-modulesodoo-19

Odoo Customization: Studio vs Custom Modules

A decision guide for Odoo customization: six questions that tell you whether a requirement belongs in Studio or a custom module, and when to move.

Odovation TeamNovember 10, 202611 min read

Planning an Odoo implementation?

Get a Free Consultation

Odoo customization comes down to two routes: Odoo Studio, the built-in no-code toolbox, and custom modules written in Python and XML. Use Studio when the change is a field, a view, a simple rule, an approval or a document layout that an administrator can own. Use a custom module when the change is business logic that must be tested, versioned and carried through upgrades by a developer. The choice is made per requirement, not per project, and three facts outside the requirement itself (your hosting, your pricing plan and who maintains the result) often decide it before design starts.

Odoo's behaviour below is taken from the Odoo 19 documentation pages linked in each section, checked on 10 November 2026.

What each route really is

Studio changes are stored as data inside your database. The Odoo 19 Studio documentation lists what it can add or modify in any app: fields, views, models, automation rules, webhooks, PDF reports, approval rules and security rules. The first time you customize anything, Odoo adds a module named studio_customization to the database to hold the result (Models, modules, and apps). Nobody writes files, and nothing is deployed.

A custom module is source code: Python classes that extend Odoo's models and XML that extends its views, kept in a Git repository and installed on the server. Odoo's developer tutorial shows the core technique, which is inheritance: a module extends an existing model's methods, adds its own logic, and calls the parent method so standard behaviour still runs (Server framework 101, chapter 12).

Odoo itself draws the line the same way. Its upgrade guide defines a custom module as "any module that extends the standard code of Odoo and that was not built with the Studio app" (Upgrade a customized database). That definition matters because Odoo treats the two sides differently at upgrade time, as question 3 below explains.

Two gates to check before you compare anything

Two facts can remove an option entirely. Check them first.

Gate 1: hosting. Odoo's documentation states that "Odoo Online is incompatible with custom modules or modules from the Odoo Apps Store" (Odoo Online). If your database is on Odoo Online, the custom-module route is closed unless you move to Odoo.sh or a self-hosted server. Odoo.sh is Odoo's own cloud platform for projects that carry code; its documentation lists continuous integration, a web shell, module dependencies and SSH access (Odoo.sh).

Gate 2: pricing plan. Studio is not free of consequences either. The Studio documentation warns that installing Studio on a database on the Standard pricing plan automatically triggers an upsell to the Custom plan. On a yearly or multi-year contract, an upsell order is created with a 30-day limit; on a monthly contract, the subscription switches to the Custom plan and the new rate applies at the next bill (Studio). Confirm the effect with Odoo or your account manager before anyone clicks the Studio icon.

If both routes are still open after these two gates, the six questions below decide.

Six questions that decide each requirement

Ask them in this order. The first clear answer usually settles it.

1. Does standard Odoo already do it?

Neither route is the right answer if a setting covers the need. Odoo's own upgrade guide tells teams to "challenge the developments as much as possible and find functional workarounds", because removing overlap with standard features makes upgrades easier and reduces technical debt (Upgrade a customized database). Apply the same test before building: ask for the standard screen that comes closest and what exactly it cannot do.

2. Is it structure or behaviour?

Structure is what a record holds and how it is shown: an extra field, a rearranged form, a new list column, a document layout, a button that needs sign-off. Studio is built for this. Behaviour is what the system does: calculations across several models, validations that must never be bypassed, changes to how a standard step such as confirming an order or posting an invoice works. Behaviour that alters a standard method belongs in a module, because inheritance is the mechanism designed for it.

3. Who will adapt it at the next upgrade?

This question separates the two routes most sharply. Odoo's upgrade service-level agreement covers "the upgrade of all customizations created with the Studio app, as long as Studio is still installed and the respective subscription is still active". It does not cover "the upgrade of additional modules not covered by a maintenance contract that are created in-house or by third parties, including Odoo partners". The same page warns that a database containing custom modules cannot be upgraded until a version of those modules exists for the target version (Upgrade).

So a Studio change is carried forward by Odoo, and a custom module is carried forward by you or the developer you pay. On Odoo Online a database on a major version must be upgraded every two years, and Odoo carries Studio changes through it. On Odoo.sh a major version is supported for three years and you then have two more years to upgrade; each of those upgrades waits for a new version of every custom module. A module is a recurring commitment.

4. Who needs to change it later?

A Studio change can be adjusted by a trained administrator on a Tuesday afternoon. A module change needs a developer, a test database and a deployment. If the business will keep tuning the rule (thresholds, approvers, which fields are required), Studio keeps the change in the hands of the people who own the process. If the rule must not be changed casually, the friction of a module is a feature.

5. Does it have to be tested and reviewed?

Studio has no code review and no automated tests. Module code can carry automated tests and sits in version control, so every change has an author, a date and a diff. Requirements where a silent error costs money or compliance (pricing logic, tax handling, stock valuation, commission calculation) deserve that discipline.

6. Does it talk to another system?

Studio can receive and send webhooks through automation rules, but Odoo's documentation is cautious about it: it says it is "highly recommended to consult with a developer, solution architect, or another technical role" when deciding to use webhooks, and that a misconfigured webhook may disrupt the database and take time to revert (Automation rules). A single inbound notification is reasonable in Studio. A two-way sync with retries and duplicate handling is integration work; our guide to Odoo integration options covers that choice.

Common requests and where they belong

RequirementRouteWhy
Extra field on a sales order, shown on the form and listStudioStructure only; an administrator can own it
Show the customer's email on the order without retyping itStudioA Related Field reads through an existing link
Manager sign-off before a button's action runsStudioApproval rules attach to buttons, with ordered steps and conditions
Reminder activity some days before a contract end dateStudioA timing-based automation rule on a date field
Reworded or rearranged quotation PDFStudioThe report editor edits existing PDF reports or creates new ones
A calculation that reads several models and must be exactModuleNeeds tests, review and a developer's ownership
Changing what happens when an order is confirmed or an invoice is postedModuleExtends a standard method through inheritance
Two-way sync with a shop, marketplace or warehouse systemModule or integrationFailure handling and duplicates need real code
The same customization rolled out to several databasesModuleVersioned code deploys the same way everywhere

Source: Odoo 19 documentation for fields and widgets, approval rules, automation rules and PDF reports for the Studio rows. The module rows are our scoping judgement, not an Odoo rule.

Two details from those pages are worth knowing before you promise anything. Approval steps can name individual approvers or a user group, can be ordered, and can be made exclusive so one person cannot approve two steps on the same record; approvals are tracked in the record's chatter. And timing-based rules are checked by a scheduled action that runs every 4 hours by default, with Odoo raising the frequency automatically when a rule uses a short delay. A reminder "three days before" is a good fit. An action that must fire within seconds of an event is not.

The grey zone: when a Studio build is turning into code

Studio is described as no-code, but two of its options accept Python. The Execute Code action runs Python on the triggering record, and the Update Record action has a Compute option that sets a field from Python code. One trigger, On UI change, works only with the Execute Code action (Automation rules).

Odoo attaches a notice to this. For automation rules that require the execution of custom code, the documentation says that maintenance of custom code is not included in the Standard or Custom pricing plans and incurs additional fees. In other words, the moment a Studio rule contains Python you have custom code to maintain, without the repository, tests or review that would normally come with it.

Signs that a Studio build has crossed the line:

  • Several automation rules fire on the same model and their order matters. Odoo runs the actions inside one rule in the order they were defined, so a rule that relies on a field another rule sets is fragile.
  • A rule has Python longer than a few lines, or the same snippet is pasted into more than one rule.
  • Nobody can say what a rule does without opening it. The documentation suggests using each rule's Notes tab to record its purpose; empty Notes tabs are a warning.
  • A time-based rule ran against old records. Odoo's setup steps include running the scheduled action manually once, and call that step critical to stop a new rule from acting retroactively on historical records.

One or two of these is normal. Several together mean the logic should be rewritten as a module and the rules retired.

Moving between the routes

Studio first, module later is a sound path when requirements are still moving. Let users live with a Studio field and form for a few weeks, then freeze what survived. Three practical points make the later move easier:

  • Keep the field names. Studio prefixes new fields with x_studio_ by default, and Odoo requires at least the x_ prefix on any custom field (Fields and widgets). Data already lives in those columns, so a module that takes over the logic should keep using them, or include a migration step that copies the values.
  • Use the export for what it is. Studio's Export function downloads studio_customization as a ZIP that can be imported into another database. Odoo's warning applies: the destination must be on the same Odoo version and contain the same apps and modules, because Studio does not add the underlying modules as dependencies of the exported module (Models, modules, and apps). The export is a way to copy customizations and a useful specification for a developer. It is not a hand-written module with tests.
  • Decide before the upgrade, not during it. Odoo recommends a complete freeze of custom development when an upgrade starts, apart from bug fixes (Upgrade a customized database). Converting Studio logic to a module in the middle of an upgrade doubles the testing.

Most real systems are mixed. Fields, layouts and approvals sit in Studio where the business can adjust them, while the two or three rules that carry real risk sit in a tested module. A mix is fine as long as someone keeps one list of every customization, with its route and its owner. Our article on what Odoo development services include describes the layers a full engagement covers and the deliverables to expect for each.

What goes wrong, and how to spot it

A module built for Odoo Online. Symptom: a signed proposal for custom code, and a database that cannot install it. Check the hosting gate before any estimate.

Studio installed without checking the plan. Symptom: an unexpected upsell order or a higher next bill. The warning is on the first page of the Studio documentation.

Everything in Studio because nobody wanted a developer. Symptom: dozens of rules, Python in several of them, and a monthly "why did this field change" investigation.

Everything in a module because the developer prefers code. Symptom: you pay a developer to move a field on a form, and every upgrade includes work on changes Odoo would have carried for you.

How we scope customization work

When we scope Odoo customization, each requirement gets a route and a reason, using the gates and questions above: standard first, Studio where an administrator can own the change, a module where the logic needs tests and a developer, and a written note of who adapts each module at the next version. If you already have a Studio build that has grown past what you can maintain, or a quote you want checked against these questions, send it through our contact page.

Frequently Asked Questions

Is Odoo Studio enough for most Odoo customization?

For structural changes, usually yes: fields, views, PDF report layouts, approval rules, simple automation rules and small new models are all within Studio's documented scope. It stops being enough when the requirement changes how a standard process behaves, needs automated tests, or depends on Python inside automation rules. Odoo's documentation notes that maintenance of custom code in automation rules is not included in the Standard or Custom plans.

Can I use custom modules on Odoo Online?

No. Odoo's documentation states that Odoo Online is incompatible with custom modules and with modules from the Odoo Apps Store. On Odoo Online your customization options are configuration and Studio. Custom modules need Odoo.sh or a self-hosted installation, and changing hosting type is not part of a standard upgrade.

Do Studio customizations survive an Odoo upgrade?

Odoo's upgrade service-level agreement covers customizations created with the Studio app, as long as Studio is still installed and the subscription is still active. Custom modules are covered only under a maintenance of customizations subscription; otherwise adapting them is the responsibility of whoever maintains the code. You should still test Studio changes on an upgraded test database before upgrading production.

Can a Studio customization be converted into a custom module?

Partly. Studio's Export function produces a ZIP of the studio_customization module that can be imported into another database on the same Odoo version with the same apps installed. A developer can use that export as the starting point and specification for a hand-written module, but logic held in automation rules normally has to be rewritten as Python methods with tests. Keep the existing field names so the stored data stays attached.

Ready to plan your Odoo implementation?

Talk to an implementation specialist — get a realistic scope, timeline, and fixed quote for your project.