Odoo Studio vs Custom Module – When to Use Which

The Core Trade-off

The fundamental tension is between speed and control:

• Studio gets you from idea to working customization in minutes — no development environment, no deployment, no code review needed. But it can only do what the Studio UI exposes.
• A custom module gives you the full power of Python, the Odoo ORM, JavaScript, XML, and CSS — but requires a development workflow: write code, test, deploy, install/upgrade the module.

The practical rule: start with Studio; graduate to a module when you hit a wall.

When to Use Studio

Studio is the right choice when:

• You need to add a few fields to an existing model (e.g., adding "Internal Reference" to Contacts).
• You want to rearrange or simplify a form view for end-user clarity.
• You need a simple automation (send email on state change, set a field on creation).
• You're building a lightweight data collection app with no complex business rules.
• You're prototyping — validating a workflow with users before committing to code.
• Your client has an Enterprise subscription and needs customizations delivered the same day.
• The person making changes is a business analyst or consultant, not a developer.

When to Write a Custom Module

A custom module becomes necessary when:

• You need Python business logic — calculations, validations, ORM constraints, wizards.
• The customization must work on Odoo Community (Studio is Enterprise only).
• You need version-controlled, CI/CD-compatible code deployed from git.
• The same customization needs to be installed on multiple Odoo instances.
• You need custom JavaScript widgets, OWL components, or client-side behavior.
• You're building an integration with an external API (REST, SOAP, EDI).
• Performance matters — stored computed fields with @api.depends vs formula fields.
• You need ORM inheritance (_inherit) or model delegation.

Feature Comparison Table

Migrating from Studio to Module

When your Studio customizations outgrow what Studio can do, you don't lose your work. Studio's Export button generates a ZIP file containing a complete Odoo module:

1. In Studio, click the Export button in the top toolbar.
2. Download the ZIP file.
3. Unzip it — you'll find a standard module structure: __manifest__.py, models/, views/, security/, data/.
4. Add the module to your Odoo addons path.
5. From this point, manage the module in git and add Python logic as needed.
6. Disable or uninstall the Studio customizations from the database to avoid conflicts.

The exported module looks like this:

{
    'name': 'studio_customization',
    'version': '19.0.1.0.0',
    'author': 'Odoo Studio',
    'depends': ['sale'],
    'data': [
        'security/ir.model.access.csv',
        'views/sale_order_views.xml',
        'data/ir_model_fields.xml',
    ],
    'installable': True,
    'auto_install': False,
}

Can You Mix Both?

Yes. Studio and custom modules coexist peacefully as long as they don't define the same things twice. Common mixing patterns:

Module references Studio fields

If Studio created a custom field (x_studio_approval_note) on sale.order, a custom module can reference it in Python:

class SaleOrder(models.Model):
    _inherit = 'sale.order'

    def action_confirm(self):
        # Access a Studio-created field by its technical name
        for order in self:
            if not order.x_studio_approval_note:
                raise UserError("Please add an approval note before confirming.")
        return super().action_confirm()

Studio extends a module's model

If your custom module created a model project.equipment, you can open Studio on that model and add extra fields or modify views without touching the module code. This is particularly useful for field additions that don't need Python logic.

Recommendation matrix