Productivity · Odoo Studio
Odoo Studio
Odoo Studio is the low-code layer on top of every Odoo module. Add fields, build screens, automate actions, and generate reports without Python. Best for business analysts and ops managers who want to ship small changes themselves and save dev capacity for the things only Python can do.
Book a free 30-min auditWho Odoo Studio is for
- ✓Business analysts maintaining Odoo configurations without dev resources
- ✓Ops managers automating repetitive admin work
- ✓Finance teams adding custom approval rules and report layouts
- ✓Teams that would otherwise pay for Mendix, OutSystems, or a low-code SaaS
See Odoo Studio in action
Official Odoo Studio walkthrough from the Odoo channel.
Top features
Field designer
Add fields to any Odoo model with point-and-click. Text, number, date, selection, many2one, computed, all available, with validation rules and conditional visibility.
View editor
Edit list, form, kanban, calendar, gantt, and graph views inline. Drag fields, group sections, add tabs, add buttons. Inheritance keeps your changes safe across Odoo upgrades.
Automated actions
Trigger actions on record events, on create, write, unlink, or on cron schedules. Send email, create records, run server actions, all without code.
Approval rules
Multi-step approval chains for any record. Configurable by amount thresholds, departments, or custom conditions. Email and Discuss notifications on each step.
PDF and Excel report builder
Visual report designer for invoices, quotes, picking lists, and custom statements. Generates QWeb templates that designers and developers can refine later if needed.
Custom application builder
Build a full Odoo application from scratch, models, views, menu entries, security groups, without touching the filesystem. Apps export as Odoo modules for staging then production.
Webhooks and external API hooks
Trigger external systems on Odoo events. Inbound webhooks accept payloads and create or update Odoo records. JSON-RPC and REST endpoints exposed for everything Studio creates.
Upgrade-safe by design
All Studio modifications use Odoo's inheritance and customization patterns under the hood. Upgrades preserve customizations; conflicts are surfaced explicitly rather than silently breaking.
Representative use cases
Finance approval workflow
Controller adds an approval rule, purchase orders above $5K route to the CFO, above $50K route to the CEO. Email notifications fire, the PO sits in a pending state until approved. Implemented in 30 minutes, no developer involved.
Service-business intake form
Ops manager builds a custom intake form for new client onboarding, fields for project type, scope, target dates, and budget tier. Submissions create a draft Project, an opportunity in CRM, and a task list for the AE.
Custom inventory location attribute
Warehouse manager adds a temperature-zone field to stock locations, with a validation rule preventing perishable products from being routed to ambient-zone bays. Built in Studio in an afternoon, blocked an entire class of picking errors.
Pricing
Odoo license
Studio requires the Odoo Custom tier ($37.40/user/mo). It is the headline feature that distinguishes Custom from Standard.
Octura implementation
Octura Studio enablement: $5K–$15K. Includes training a power-user, governance setup (who can edit what), and ten initial customization tickets. Typical timeline 3–6 weeks.
Common integrations
- Every Odoo module (Studio modifies any model)
- External APIs via outbound webhooks
- Inbound webhooks accept payloads from third-party tools
- Email (notification actions on automations)
- Odoo Knowledge (link automation runbooks to articles)
Related Odoo apps
Ready to scope an Odoo Studio deployment?
Book a free 30-minute audit. We'll walk through your current stack, identify the gaps Odoo Studio closes, and propose a fixed-fee implementation timeline.
Book a free 30-min auditOdoo Studio FAQ
01Do I need Studio if I already have a developer?
Probably yes. Studio handles the 80% of changes that don't need Python, freeing the developer for real lifts, integrations, complex algorithms, and custom modules. The split also keeps small changes from queuing behind big releases.
02Is Studio safe across Odoo version upgrades?
Yes, Studio uses Odoo's standard inheritance patterns under the hood. Upgrades preserve customizations and surface conflicts explicitly. Heavier custom-Python modules are a different conversation; Studio-only changes upgrade smoothly.
03Can a non-technical user actually build a working app in Studio?
For simple apps (intake forms, request trackers, internal tools), yes, with a few hours of guidance. For apps with computed fields, multi-step automations, or complex permissions, plan on partnering with a power-user or consultant for the first one.
04What is the difference between Studio and a full custom Odoo module?
Studio is configuration; custom modules are code. Studio is fastest and safest for fields, views, automations, and approval rules. Custom modules are needed for new business logic, heavy computed fields, integrations with native libraries, and performance-critical jobs.