Odoo 19 Studio: Decide Cost, Data Structure and Access Before Customizing

Applicability

For Odoo 19, subject to the plan, hosting, apps, permissions and provider eligibility described below; not every database has these enabled.

Research method

Research based on Odoo 19 and applicable official policies; no new Odoo operation, payment or messaging tests.

Check standard apps before customizing. Studio can add fields, views and explicit workflow rules; it cannot turn an undefined process into a safe app automatically. The service-request design below is fictional and was not implemented or tested.

Contents

• Price the plan change before the build
• Define one service request before a new model
• Model access and own-record access differ
• Specify automation triggers and duplicates
• Make handover and reversal explicit

Price the plan change before the build

Odoo 19 explicitly states that installing Studio on Standard triggers an upsell to Custom. Annual or multi-year contracts generate an upsell order with a 30-day limit; monthly contracts switch rate on the next bill. Do not treat installing it on a production database as a free experiment.

Compare user count, contract period, the Custom-plan difference and ongoing maintenance. Obtain the actual regional quotation from Odoo; no invented Hong Kong monthly price is given here. If CRM or Project already fits, evaluate configuration before creating a parallel data structure.

Define one service request before a new model

A fictional Hong Kong repair company needs request number, customer, assignee, due date, state and budget. First ask whether these are fields on an existing ticket. A genuinely separate lifecycle may justify a new model.

Link Customer to a contact rather than typing inconsistent names. Pair monetary values with currency. A budget is management information, not an invoice or proof of payment. Sequence numbers, attachments and a pipeline are design choices, not completed accounting integrations.

Model access and own-record access differ

Group/model permissions determine whether users can read, create, write or delete that class of data. Record rules restrict which records within it they may access. Adding someone to a sales group does not prove they can see only their customers; hiding a field in a view does not replace data access control.

Write a permission matrix first: an operator works assigned requests, a supervisor works the team's requests and an administrator maintains configuration. That is a requirement, not an installed rule. Later verify lists, direct record links, search and export under each role. Multi-company and portal access need separate analysis; an administrator screenshot cannot validate ordinary-user restrictions.

Specify automation triggers and duplicates

Design example: when a request first changes to Awaiting quotation and has an assignee, create a quotation-preparation activity for that person. Odoo automation rules provide triggers, conditions and activity creation, but define which changes trigger the rule, missing-assignee handling, repeated saves and reopening before configuring it.

Acceptance cases should cover first transition, repeated save, returning to the state and a missing assignee. Without observed results, do not claim working automation or saved hours. Sending a notification does not complete a business transaction.

Make handover and reversal explicit

Keep a field inventory, permission matrix, rule purposes and a named maintainer. Studio customization export is not automatically a full database backup or a risk-free cross-version migration. Before removing a field, inspect existing data and dependencies; deleting it to restore the old screen can lose information.

Next express one unmet standard-process requirement as a role, a record and an expected outcome. Use that to decide whether Studio is justified.

Sources

• Odoo 19 Studio

  Studio capabilities and Standard-to-Custom subscription effects.

  Source checked Oct 21, 2026

• Odoo 19 Models, modules, and apps

  Model features and customization export boundary.

  Source checked Oct 21, 2026

• Odoo 19 Access rights

  Groups, model permissions and record rules.

  Source checked Oct 21, 2026

• Odoo 19 Automation rules

  Triggers, conditions and create-activity actions.

  Source checked Oct 21, 2026