Odoo Studio No-Code Customization Guide: Fields, Views, Automations, and Reports

Odoo Studio is the no-code customization platform built into Odoo Enterprise. It lets business users add fields, modify views, create automated actions, and build reports without writing a single line of Python or XML. For organizations that need customizations beyond Odoo's default configuration but want to avoid the cost and complexity of custom development, Studio is the bridge between out-of-the-box and fully custom. This guide covers every Studio capability with practical examples.

Key Takeaways

• Odoo Studio is included with Odoo Enterprise at no additional cost
• Custom fields, views, and automations created in Studio persist through Odoo upgrades
• Studio supports 15+ field types including computed fields, related fields, and HTML fields
• Automated actions can trigger on record creation, update, time conditions, or external webhooks
• Custom reports use QWeb templates with drag-and-drop layout editing

Accessing Odoo Studio

Studio is available to users with administrator access in Odoo Enterprise. Toggle Studio mode by clicking the wrench icon in the top menu bar. When enabled, every view in Odoo shows edit controls for customizing fields, layout, and behavior.

Studio modifications are global---changes apply to all users (not just the current user). Use access rights to control which user groups see custom fields and views.

Custom Fields

Adding Fields

With Studio mode active, click the + button next to any field group to add a new field:

Computed Fields

Create fields that calculate their value automatically:

1. Add a new field and select Computed in the properties
2. Write the computation expression using Odoo's domain syntax
3. Set dependencies (fields that trigger recalculation when changed)

Example: A "Total Weight" field on a sales order that sums the weight of all order lines. The computation references order_line.product_id.weight * order_line.product_uom_qty and recalculates whenever the order lines change.

Related Fields

Pull data from linked records without custom code:

1. Add a new field and select Related in the properties
2. Specify the path through relationships (e.g., partner_id.country_id.name)
3. The field displays data from the related record and updates automatically

Example: Display the customer's country on the sales order form by creating a related field that follows partner_id.country_id.name.

View Customization

Form View

Customize form layouts by:

• Adding fields: Drag fields from the field list to the desired position
• Creating groups: Organize related fields into labeled groups with optional column layout
• Adding notebooks: Create tabbed sections for organizing large forms
• Conditional visibility: Show or hide fields based on conditions (e.g., show "Reason" field only when status is "Rejected")
• Required fields: Make fields mandatory under specific conditions
• Read-only rules: Lock fields based on record state

List View

Customize list (tree) views by:

• Adding columns: Drag fields to add columns
• Reordering columns: Drag column headers to rearrange
• Column widths: Set fixed or proportional widths
• Conditional formatting: Color-code rows based on field values
• Default sorting: Set the default sort column and direction
• Grouping: Configure default group-by fields

Kanban View

Customize Kanban boards:

• Card fields: Choose which fields display on the card face
• Card colors: Color-code cards based on priority, status, or custom rules
• Progress bars: Show completion percentage on cards
• Quick create: Enable inline creation of new records from the Kanban column

Calendar, Pivot, and Graph Views

Studio also supports customizing:

• Calendar view: Map date fields to calendar events
• Pivot table: Configure default measures, rows, and columns for analysis
• Graph view: Set default chart type (bar, line, pie) and data dimensions

Automated Actions

Action Types

Navigate to Settings > Technical > Automated Actions (or use Studio's automation tab):

Action Outcomes

Each automation can perform one or more actions:

• Update record: Change field values on the current record
• Create record: Generate a new record in any model
• Send email: Use an email template with dynamic fields
• Send SMS: Send text messages to phone number fields
• Execute Python code: Run custom Python for complex logic (advanced)
• Add followers: Subscribe users to the record for notifications
• Create activity: Schedule a follow-up activity for a user

Practical Automation Examples

Auto-assign region manager: When a new lead is created, check the state/country field and assign the regional sales manager automatically.

Deadline reminder: Three days before a project task's deadline, send an email to the assignee and create a high-priority activity.

Approval notification: When a purchase order exceeds 10,000 USD, change the status to "Needs Approval" and notify the finance manager.

Customer onboarding: When a sales order is confirmed, create a project with onboarding tasks and assign the customer success manager.

Custom Reports

Report Builder

Studio includes a visual report designer:

1. Navigate to any list view and click Report in the Studio toolbar
2. Choose a report template (blank, table, or label)
3. Drag and drop fields onto the report layout
4. Configure headers, footers, and grouping
5. Preview the report with live data

Report Elements

PDF Output

Reports generate as PDF documents. Configure paper size, margins, and orientation in the report settings. Reports can be:

• Printed directly from the record
• Attached to emails
• Saved to the Documents module
• Generated in batch for multiple records

Approval Workflows

Building Approval Chains

Combine Studio's automated actions with custom fields to create approval workflows:

1. Add a status field: Selection field with values like "Draft," "Pending Approval," "Approved," "Rejected"
2. Add approver fields: Many2one fields linking to users for each approval level
3. Create automation: When status changes to "Pending Approval," send email to approver
4. Add approval buttons: Smart buttons that change status when clicked by the authorized approver
5. Add conditions: Make certain fields read-only when status is "Approved"

Multi-Level Approvals

For processes requiring multiple approval levels:

Studio Best Practices

When to Use Studio vs Custom Development

Upgrade Safety

Studio customizations are stored separately from core Odoo code. They persist through version upgrades, though some adjustments may be needed when underlying models change. Document all Studio customizations for review during upgrade planning.

Performance Considerations

• Computed fields recalculate on every record access---avoid complex computations on frequently accessed records
• Automated actions trigger on every matching event---use specific conditions to prevent unnecessary execution
• One2many fields on frequently loaded forms impact page load time

ECOSIRE Studio Services

While Studio handles many customization needs, organizations often benefit from expert guidance on what to customize and how. ECOSIRE's Odoo customization services include Studio-based customization for simple needs and custom module development for complex requirements. Our consultancy services help organizations determine the best approach for each customization need.

Related Reading

• Odoo Custom Module Development Guide
• Odoo API Integration Guide
• Odoo Security and Access Control
• Odoo Approvals Workflow
• Odoo Reports and Dashboards Guide

Is Odoo Studio available in Odoo Community Edition?

No. Odoo Studio is an Enterprise-only feature included at no additional cost with the Enterprise subscription. Community Edition users can achieve similar customizations through custom module development, but it requires Python and XML coding knowledge.

Can Studio customizations be exported and reused across Odoo instances?

Yes. Studio customizations are stored as a module that can be exported as a ZIP file. This module can be installed on another Odoo instance, making it possible to develop customizations in a staging environment and deploy to production, or replicate configurations across multiple databases.

Do Studio customizations affect system performance?

Minor customizations (extra fields, view changes) have negligible impact. Computed fields that reference large datasets, automated actions that trigger frequently, and complex report templates can affect performance. Monitor the effects of each customization and optimize or convert to custom code if performance degrades.