Odoo Studio: Custom Models, Views, and Automation Without Code

Introduction

Odoo Studio amplifies the rest of the suite: dashboards, documents, Studio, and IoT only create value when sales, stock, and finance data is already trustworthy.

Teams adopt Odoo for transactions first, then ask for better insight and tailored screens, which is where platform apps and careful customization enter.

Studio helps leaders and power users shape how information is presented and accessed without breaking the core data model underneath.

COOs, product owners, and internal Odoo champions evaluating the next layer of maturity will see when to extend standard apps versus when to call for expert help.

Studio is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo Studio: Custom Models, Views, and Automation Without Code states the storyline for stakeholders approving.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo Studio.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo Studio is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Leadership opens a beautiful dashboard, then asks why the cash number does not match accounting. Someone built a view on incomplete data, and now every meeting starts with trust issues, not decisions.

Leaders want insight and tailored processes, but data and customization sprawl without governance. Dashboards and Studio changes only help when they sit on reliable transactional data.

Sound familiar? Teams usually hit these walls:

• KPIs that do not match operational reality
• Customization without sandbox discipline
• Integrations that break silently after upgrades

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo Studio, and measure what changes.

Top 10 Studio Use Cases

10 use cases for Odoo Studio, ranked from Level 1 (easy, do it this afternoon) to Level 10 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy daily win. The last level is intentionally over the top so you see how far the same app can scale when architecture and data stay clean.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Add a custom field to the customer form in two minutes Level 1 — Easy

Level 1 is the simplest possible Studio action: one admin, one missing field, no code, no schema migration. You drag a field onto the form and every user sees it the next time they refresh.

Here's how you'd do it in Odoo:

1. Open any customer record from Contacts and click the Studio icon in the top-right corner of the screen.
2. Drag a Char field from the toolbox into the form, just under the company name, and drop it there.
3. Rename the label to Account Manager Notes and add a tooltip explaining what your team should write inside.
4. Click Save; the field is now live for every user, on every customer record, in every view of that model.
5. Open a different customer to confirm the field exists, fill it once, and check the chatter logged the change.

What you get: Your team captures the missing information the same afternoon, without filing an IT ticket or waiting for a developer to ship a release.

2. Add a Compliance tab with grouped fields and conditional visibility Level 2 — Easy

Level 2 goes from one field to layout. You group related information into a dedicated tab so users find it without scrolling the entire customer form.

Here's how you'd do it in Odoo:

1. Open a customer record in Studio mode, click the plus icon next to the last tab, and name the new tab Compliance.
2. Inside the new tab drag a Section and add three fields: VAT Verified (boolean), NDA Signed (boolean), Last Audit Date (date).
3. Set the tab to display only when the customer is a company, not when it is an individual contact.
4. Enable Log Changes on each of the three fields so the chatter records who flipped what and when.
5. Save, reload the page, and confirm the Compliance tab now sits between Sales and Internal Notes for company records only.

What you get: Compliance data lives on the customer card itself instead of in a separate spreadsheet that nobody updates after the first month.

3. Build a custom Kanban view for the morning sales standup Level 3 — Easy

Level 3 introduces views. The same sales order data becomes a board grouped by sales team, color-coded by deadline, ready to drive a ten-minute standup.

Here's how you'd do it in Odoo:

1. Open Sales, Orders, click the Studio icon, select Views, and click Add a Kanban view to the model.
2. Drag the customer name, expected revenue, and salesperson onto the card, then set a color rule based on Date Deadline.
3. Group records by Sales Team and add a quick filter for Active equals True so closed deals stay hidden.
4. Pin the view as the default for the Sales Manager group via Studio's view access settings.
5. Run the next morning standup from one board, drag cards across columns, and watch updates propagate to all users.

What you get: Managers run a ten-minute visual standup from one screen instead of opening five reports and re-explaining the same pipeline every morning.

4. Customize the quotation PDF with branding and conditional blocks Level 4 — Medium

Level 4 leaves the screen and touches paper. Studio's report editor lets you redesign the quotation PDF with your branding, dynamic totals, and conditional sections.

Here's how you'd do it in Odoo:

1. Go to Settings, Studio, Reports, then pick the Quotation or Order report linked to the Sales Order model.
2. In the layout editor, drop the company logo into the header and reorder the columns: description, unit price, quantity, taxes, subtotal.
3. Insert a conditional block that only renders when state equals draft, showing a Valid 30 days banner in your brand color.
4. Add a footer with payment terms pulled dynamically from the customer record so each PDF matches contract reality.
5. Save, exit Studio, and send a test quotation by email to confirm the PDF matches the new layout end to end.

What you get: Sales sends branded, legally consistent quotations without asking design or finance to retouch a Word file before every customer email.

5. Spin up a brand-new no-code app for an internal workflow Level 5 — Medium

Level 5 leaves customization and enters creation. You build an entirely new app for a workflow Odoo does not ship out of the box, without writing one line of code.

Here's how you'd do it in Odoo:

1. Go to Studio, click New App, name it Equipment Loan, choose an icon and color, then confirm to generate the menu and database table.
2. On the new model add fields: Asset Name (char), Borrower (Many2one to res.users), Loan Date (date), Due Date (date), Status (selection).
3. Generate the default Kanban, List, and Form views, then tweak the form to show Status as a statusbar across the top.
4. Place the new menu under Inventory and grant Read or Write access to the Employee group so anyone can request a loan.
5. Test by creating two loan records and moving one through every status to confirm the workflow holds end to end.

What you get: A process that was previously untracked, equipment circulating between staff, now has a clean digital trail with owners, deadlines, and a manager view.

6. Automate overdue reminders with a no-code server action Level 6 — Medium

Level 6 brings logic. Studio's Automations builder triggers actions on field change, time interval, or record creation, without ever opening a Python file.

Here's how you'd do it in Odoo:

1. Open the Equipment Loan app, go to Studio, Automations, and click New to create your first no-code rule.
2. Set the trigger to On Update of Status, where the new value equals Overdue, on the Equipment Loan model.
3. Add two actions: send an email template to Borrower including the asset name and due date, then post a red note in the chatter.
4. Create a second rule on a time interval: every morning at 9:00, scan loans whose Due Date is past today and flip Status to Overdue.
5. Test by setting a loan's due date in the past and verifying the next run flips the record and emails the borrower automatically.

What you get: Reminders happen automatically every morning, so nobody chases overdue equipment by hand and managers stop asking 'did we ever get that back'.

7. Build a multi-step approval workflow with conditional buttons Level 7 — Hard

Level 7 turns Studio into a workflow engine. You model purchase requests with a statusbar, role-based buttons, and conditional logic that enforces who can move what.

Here's how you'd do it in Odoo:

1. Create a Purchase Request model with fields Requester, Amount, Justification, Approver, and a Status statusbar (Draft, To Approve, Approved, Refused).
2. Add three form buttons: Submit (visible in Draft), Approve and Refuse (visible in To Approve and only to users in the Manager group).
3. Configure each button to move the record to the next stage and to auto-assign an Approver when Submit is clicked.
4. Build a Studio automation: when the record reaches Approved with Amount above five thousand, send an email to the CFO for second-level sign-off.
5. Save a My Pending Approvals filter so managers see only the requests waiting on them, pinned to their dashboard.

What you get: Spend control runs inside Odoo with a full audit trail instead of email threads where every approval gets lost the moment someone reorganizes their inbox.

8. Lock down a custom model with record rules and group access Level 8 — Hard

Level 8 is security. The same Equipment Loan app needs different permissions per role; Studio's security layer enforces who reads, writes, and sees which records.

Here's how you'd do it in Odoo:

1. Go to Settings, Users and Companies, Groups, and create Equipment Manager and Equipment Employee with descriptive names.
2. In Studio on the Equipment Loan model, set Read, Write, Create, and Delete per group: Employee can create or read own loans, Manager edits everything.
3. Add a record rule: Equipment Employee sees only loans where Borrower equals the current user, while Manager sees all records across the company.
4. Hide sensitive fields (Approval Notes, Acquisition Cost) from the Employee group via Studio's field visibility rules.
5. Log in as a test employee to confirm they cannot see other people's loans, then switch to a manager account and verify full access.

What you get: One app serves everyone, but each role sees only what they should , no separate database, no manual exports, no risk of leaking confidential data.

9. Connect the custom model to CRM, Inventory and Project via smart buttons Level 9 — Hard

Level 9 is integration. The Equipment Loan model stops being an island and starts feeding the rest of Odoo: customers, projects, inventory, and CRM all see the same record.

Here's how you'd do it in Odoo:

1. Add a Many2one from Equipment Loan to res.partner so each loan can be linked to a customer or partner record.
2. On the customer form, use Studio to add a smart button Open Loans that filters Equipment Loan by partner and shows a live count.
3. Add a related field on the loan showing the customer's outstanding invoice balance, so finance sees risk before approving a new loan.
4. Build a Studio automation: when a loan is marked Returned, create an Inventory activity assigned to the warehouse team to verify the asset.
5. Add the loan record as a smart button on the Project form when the project's customer matches, linking the two timelines in one click.

What you get: Equipment, customers, inventory, and projects share one timeline; nobody retypes data and warehouse, sales, and project teams act on the same record.

Wiring related fields, smart buttons, automations, and security rules across four standard apps and one custom model is exactly the kind of cross-app architecture Dasolo runs as a partner-led Studio engagement.

10. Run a full no-code Customer Health mini-app with AI, dashboards and BI sync Level 10 — Expert

Level 10 is the ceiling. Studio orchestrates a Customer Health mini-app that pulls signals from every app, scores risk, calls Odoo AI for chatter summaries, and pushes dashboards to leadership in real time.

Here's how you'd do it in Odoo:

1. Build a Customer Health model with fields Score, Last NPS, Open Tickets, Overdue Invoices, Last Order Date, and AI Summary, populated by Studio related fields from CRM, Helpdesk, Sales, and Accounting.
2. Create a nightly Studio automation that recomputes Score from a weighted formula and flips Status between Healthy, Watch, At Risk, and Churn Imminent.
3. Add an Odoo AI action that reads the last thirty days of customer chatter every Monday and writes a one-paragraph risk summary into AI Summary.
4. Configure record rules so account managers see only their assigned customers and executives see the full portfolio with redacted personal notes.
5. Embed the Customer Health record as a smart button on every CRM Opportunity, surfacing the score and AI summary inside the deal review screen.
6. Build a Spreadsheet dashboard Customer Risk Live that ranks customers by score, refreshes in real time, and pipes the top ten at-risk into a Discuss channel by webhook.
7. Sync the dataset to your external BI tool (Looker, Power BI) through a Studio webhook automation so leadership reads the same numbers as the CRM team.

What you get: One mini-app, zero code, gives the whole company the same view on customer risk, with AI doing the reading and Studio doing the wiring , humans focus on saving accounts.

Designing the model graph, the AI prompts, the security rules, the real-time dashboards, and the external sync is the architecture Dasolo assembles in a partner-led Studio program. Most teams need an outside team to get the cross-app glue right the first time.

When Expert Help Makes Sense

If levels 1 to 6 fit your world, you can often succeed with standard Odoo Studio, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 7 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for Studio includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo