Studio sprawl
Duplicate fields, abandoned views and overlapping automations accumulate because changes were made without a shared plan.
Odoo ERP · Studio
Odoo Studio services that keep no-code changes tidy and upgrade-friendly
Studio lets you change Odoo Enterprise without writing code. Used with a plan, it is fast and safe. Used without one, it leaves dozens of unexplained fields and views behind. We help you get the first outcome.
What is Odoo Studio?
Odoo Studio services help businesses use Odoo Studio, the no-code customization tool included with Odoo Enterprise, to add fields, adjust forms and lists, edit report layouts, set up automation rules and approvals, and build simple custom apps without writing Python. The service covers designing and making those changes, cleaning up existing Studio work, and deciding which requirements are better handled by a custom module. Studio is not available in Odoo Community.
Studio is easy to start with, which is both its strength and its risk. Several people add fields with similar names, views get edited repeatedly, automation rules overlap, and a year later nobody remembers why a form behaves the way it does. Studio also has limits: complex calculations, heavy integrations and logic that needs testing don't belong there. Knowing where that line sits is what keeps Studio a productivity tool rather than a source of confusion.
Where Studio goes wrong
Requirements that outgrow Studio
Complex pricing logic, multi-step integrations or performance-sensitive computations are forced into Studio and become fragile.
Uncertainty at upgrade time
No one knows which Studio changes still matter or how they will behave on the next Odoo version.
Studio and code in conflict
Studio edits made on top of views that custom modules also change produce unexpected results when either side is updated.
Our Odoo Studio service
Studio suitability review
Each requested change assessed for whether Studio handles it cleanly or whether a custom module would be more reliable.
Fields, forms and lists
New fields, tabs, conditional visibility, required rules and list or kanban changes designed consistently across apps.
Reports and documents
Quotation, invoice and delivery slip layouts adjusted in Studio's report editor to show the information your customers need.
Automations and approvals
Automation rules, scheduled reminders and approval rules on buttons, configured so they don't overlap or contradict each other.
Simple custom apps
Lightweight apps for registers, checklists or request tracking built with Studio, with menus, views and access rights.
Studio cleanup and conversion
Audit of existing Studio customizations, removal of unused elements, documentation of what remains, and conversion to code where Studio has been stretched too far.
Included capabilities
- Custom fields with clear naming
- Form, list, kanban and calendar views
- Conditional visibility and required rules
- Studio report editor changes
- Automation rules
- Approval rules on actions
- Simple custom apps and menus
- Studio change documentation
- Export of Studio customizations
What Odoo Studio changes for your business
Quick changes without developers
Many day-to-day adjustments can be made in Studio without a development cycle.
Works on Odoo Online
Studio is the main way to tailor Odoo Online, where custom Python modules aren't allowed.
Lower upgrade risk
A planned, documented set of Studio changes is easier to review during version upgrades.
Right tool per requirement
Studio handles what it does well, and code is reserved for what genuinely needs it.
Where it makes the biggest difference
Extra data on sales orders
Delivery windows, customer PO numbers and site contacts added to orders and shown on the printed quotation.
Purchase approval
Purchase orders above a set amount require a manager's approval before confirmation, configured without code.
Internal request tracker
A simple Studio app for equipment or IT requests, with stages, assignees and reminders.
Tidying years of Studio edits
Dozens of unused fields and duplicated views are removed, leaving a documented set of changes that still matter.
How we make Studio changes
Every request is checked against Studio's strengths before it is built, and every change is tested first.
Gather requests
Collect the changes users want and the reason behind each.
Studio or code
Decide which items suit Studio and which belong in a custom module.
Design consistently
Agree field names, placements and automation logic across apps before building.
Build on a test database
Make Studio changes on a staging or duplicate database first.
Review with users
Confirm each change solves the original request in real use.
Apply and document
Move the changes to production and record what was changed and why.
What it connects to
Odoo Studio
- Odoo Sales and CRM
- Odoo Inventory
- Odoo Accounting
- Odoo Project and Helpdesk
- Odoo HR
- Odoo Online, Odoo.sh and on-premise Enterprise
Built with
When to use Studio and when to write code
| Criterion | Odoo Studio | Custom module |
|---|---|---|
| Add fields and adjust views | Well suited | Possible, often unnecessary |
| Simple approvals and automations | Well suited | Possible |
| Complex calculations and business rules | Limited | Well suited |
| API integrations with other systems | Limited | Well suited |
| Automated tests and code review | Not available | Standard practice |
| Available on Odoo Online | Yes | No |
| Available on Community | No | Yes |
Security, quality and scale
Access rights on new apps
Studio-built apps and fields are given appropriate group access, not left open to every user.
Test before production
Studio changes are made and checked on a duplicate database before being applied live.
Automation guardrails
Automation rules are scoped with filters so they don't run on more records than intended.
Performance awareness
Changes that would slow large lists or reports are flagged and handled in code instead.
What working with us looks like
We'll tell you when Studio is enough
Many requests don't need a developer, and we won't turn them into development projects.
We'll tell you when it isn't
When a requirement needs tested logic or integration, we explain why and propose a module.
Studio and code under one roof
Because we build custom modules too, Studio changes and code are designed not to collide.
Documentation as standard
Every Studio change we make is recorded, so your team understands its own system.
What it costs
Fixed-price packages with the scope written down, paid stage by stage. Your project goes live once it's fully paid.
Related services, technologies and industries
Sources and further reading
Official documentation and guidance if you want to read more about this topic.
Odoo Studio: questions we hear most
Is Odoo Studio available in Odoo Community?
No, Odoo Studio is part of Odoo Enterprise and is not included in Odoo Community. Community users make equivalent changes through custom modules.
What can't Odoo Studio do?
Studio is not well suited to complex business logic, integrations with external systems, performance-critical calculations or anything that needs automated tests. Those requirements are better handled in a custom Python module.
Do Studio customizations survive Odoo upgrades?
Studio changes are upgraded along with the database and generally carry over, but they should be reviewed after each upgrade because the views they modify may have changed. A documented, tidy set of Studio changes makes that review straightforward.
Can Studio changes be moved to another database?
Yes, Studio can export its customizations as a module that can be imported into another Enterprise database. This is useful for moving changes from a test database to production.
Should we use Studio or hire a developer?
Use Studio for fields, view changes, simple automations and lightweight apps; use a developer for complex logic, integrations and anything that needs tests. Many businesses use both, with a clear rule about which tool handles what.
Next step
Check what Studio can do for you
Send us the changes you're considering. We'll tell you which ones Studio can handle and which deserve a custom module.