Odoo Studio changes Odoo without code; custom modules add code. See what each can do, which edition and hosting allow them, what upgrades mean for both, and how to decide by need.
Odoo Studio is a toolbox for changing Odoo from the screen: you add fields, rearrange views, build simple automations, edit PDF reports and set up approvals without code. Custom development is the other route: a developer writes a module in Python and XML that extends Odoo's standard code. The choice between Odoo Studio and custom development depends on what the change must do, which edition and hosting you run, and who maintains it when Odoo upgrades. This guide follows the Odoo 19.0 documentation and the pricing page as read in October 2026.
In short
Odoo's documentation calls Studio a toolbox used to customise Odoo without coding knowledge. In any app you click the Toggle Studio icon, then add or change fields, views, models, automation rules, webhooks, PDF reports, approval rules and security rules.
Studio is an Enterprise tool. The pricing page lists it with the Custom plan, which can be hosted on Odoo Online, Odoo.sh or on-premise, and the documentation warns that installing it on the Standard plan triggers an upsell to Custom. It is not in the public Community source code, which matches Odoo Community vs Enterprise. Plans change, so confirm the terms on the pricing page.
The Studio documentation has a page for each area.
| Area | What it offers | Documented caution |
|---|---|---|
| Fields | Add fields (21 types), reuse existing ones, change properties | Stored as columns in your database. Custom field names keep the x_ prefix |
| Views | Form, list, kanban, calendar, Gantt, pivot, graph and more | Edits to standard or inherited views in the XML editor are lost at updates or upgrades |
| Models and apps | New models or apps with up to 14 suggested features, such as chatter, tags and pipeline stages | Most features can be added later |
| Automation rules | Triggers (updated values, email events, timing) and actions (update a record, create an activity, send email or SMS, send a webhook) | The Execute Code action is custom Python, and its maintenance is not included in plans |
| Webhooks | Receive events from, or send data to, other systems | Odoo recommends a developer: a bad setup can disrupt the database |
| PDF reports | Edit existing reports or create new ones | Duplicate the standard report first. XML edits can cause problems at upgrades |
| Approval rules | Approval on a button, by users or a group, in several steps | Approvals are tracked in the chatter |
Studio's changes are bundled in a studio_customization module in your database. You can export it as a ZIP and import it into another database, but only on the same Odoo version with the same apps.
The Studio pages do not list what it cannot do, so treat the features above as the boundary: if a need is not on the list, plan for code. Four limits follow from what the documentation says.
Odoo defines a custom module as any module that extends the standard code of Odoo and was not built with Studio. It is the right tool for real logic, such as a calculation, a new workflow or a new website feature; for an integration that needs its own code, such as a connector Odoo does not bundle; and for changes that must be reviewed, tested and deployed to several databases.
Odoo.sh suits that workflow. It is built around a GitHub repository with production, staging and development branches, and staging builds are neutralised copies of production data. On your own server you manage the add-ons path yourself. The cost is upkeep, because someone must maintain the module and port it at every major version.
| Odoo Online | Odoo.sh | On-premise | |
|---|---|---|---|
| Custom and Apps Store modules | No | Yes, in your repository | Yes |
| Studio | With the Custom plan | With the Custom plan | With the Custom plan, so Enterprise |
| Edition | Enterprise subscription | Enterprise subscription that includes Odoo.sh | Community or Enterprise |
Odoo says Odoo Online can serve long-term production, including customisations that need no custom code. The pricing page describes the Standard plan as hosted on Odoo Online for databases without custom modules, and lists Odoo.sh hosting for custom developments as not included in any plan. Odoo Online, Odoo.sh or on-premise compares them in full.
Odoo releases a major version every year. As of 2026, 19.0 is supported until September 2028 (planned) and 20.0 came out in September 2026. The upgrade documentation sets out who is responsible for what.
A module that someone else wrote and maintains sits between the two. From the upgrade point of view it is custom code, so Odoo's own upgrade terms do not cover it, but you gain a maintainer other than yourself if the listing says so. It only works where modules are allowed, so not on Odoo Online, and a module that depends on an Enterprise app will not install on Community. Check the supported Odoo versions, support period and update policy, as in how to choose an Odoo module, and browse Odoo modules when you know what you need.
| Need | Start with | Watch out for |
|---|---|---|
| An extra field on a form, list or report | Studio | Add it to the report too |
| Hide, move or group fields | Studio views | Edit Studio's inherited views, not standard ones |
| A small register of your own records | A Studio model or app | Pick its suggested features at the start |
| Notify or create an activity when a value changes | A Studio automation rule | Note its purpose in the rule, retest after upgrades |
| Approval before a button | Studio approval rules | Name the approvers or group |
| A changed quotation or invoice layout | A Studio PDF report, on a duplicate | Tax invoices have legal content: ask your accountant |
| Events to or from another system | A Studio webhook, or a custom module | Involve a developer |
| A calculation, workflow or screen Odoo lacks | A custom module | Needs Odoo.sh or on-premise, plus upkeep |
| A connector for a gateway or courier | A ready module, then a custom one | Version support and update policy |
| A need beyond Studio on Odoo Online | Change the process or the hosting | Online accepts no custom modules |
No. Odoo sells it with its paid plans, and the pricing page lists it under the Custom plan. Check the terms there, because plans change.
No. Studio belongs to Enterprise and is not in the Community source code.
Not for fields, views and simple rules. For webhooks and code actions, Odoo recommends involving a developer or another technical role.
Odoo's Enterprise upgrade terms cover Studio customisations while Studio is installed and the subscription is active. Still test on a copy, especially automations and reports.
Yes, but both can change the same screens, so test the combination on a copy.
List your change requests and sort them with the decision table, then check each against your hosting. For upgrades, read upgrading Odoo with third-party modules. If your needs are standard, browse Odoo modules, and if you write modules yourself you can sell them on DevMarket.
Compare the three Odoo hosting options from Odoo documentation: what each allows, who runs what, which editions fit, where data sits, what costs to expect and how to move between them.
9 min read
An Odoo implementation is a project, not an installation. Follow the phases from scope to go-live, see who does what, decide between a partner and doing it yourself, and use a go-live checklist.
9 min read
Odoo eCommerce is the shop app that runs on the Odoo Website app. See how it shares data with inventory, invoicing and CRM, how products, prices, payments and delivery work, and how to set up a first store.
9 min read
Every item on DevMarket has a human-reviewed release, an instant licence key and clear update and support terms.