Odoo research · Updated October 2026
The most common Odoo customisations (and when to avoid them)
Every Odoo project faces the same question: change the software, or change the process? This guide maps the eight customisation types we see most, what Odoo Studio can handle without code, what needs a developer, and which changes cost you at every upgrade.
- Sources cited
- Updated October 2026
- Official Odoo Partner
- Configure-first guidance
Eight common Odoo customisations at a glance
Where each change is usually built, and how much it costs you at upgrade time
| Customisation | No-code route | Code needed? | Upgrade risk |
|---|---|---|---|
| Custom fields and views | Studio | Sometimes | Low |
| PDF reports and documents | Studio | Complex layouts | Low to medium |
| Approval rules | Studio | Rarely | Low |
| Automation rules | Studio | Python actions | Medium |
| Integrations | App Store connector | Often | High |
| Localisation and tax | Settings, tax rules | Gaps only | Medium |
| Website and eCommerce | Website builder | Themes, logic | Medium |
| Dashboards and KPIs | Reporting views | Rarely | Low |
Thoughtlogik assessment based on Odoo Studio docs and Odoo upgrade docs, Oct 2026.
Key takeaways
Key findings
- No survey ranks Odoo customisations. Odoo publishes no league table, so this list is built from what Odoo itself provides tools and training for, its App Store, and our project experience.
- Four of the eight types are point-and-click in Odoo Studio: fields and views, PDF reports, approval rules and automation rules all have dedicated Studio documentation and eLearning lessons.
- Studio needs the Custom plan. In the UK that is £32 per user per month for the first 12 months, then £41, against £18 then £22 for Standard (odoo.com, October 2026).
- Custom code is yours to maintain. Odoo's subscription does not cover maintenance of custom code, and its upgrade service does not port custom modules. They must be rewritten or ported for each new version.
- Odoo ships a major version every year, with three years of standard support each, so every customisation is a recurring cost, not a one-off.
- Configure first, customise last. Check standard settings, then Studio, then a maintained App Store module, and only then write code.
Methodology
How we built this list
There is no ranked, independent survey of Odoo customisations. Rather than invent one, we looked at where Odoo itself invests in tools and training, because a vendor builds no-code tools for the changes customers ask for most.
Odoo S.A. does not publish data on which customisations its customers make, and we found no independent survey that ranks them. Partner blogs that quote percentages rarely name a source. So this page uses observable evidence instead of a statistic:
- Odoo Studio documentation covers fields and widgets, views, models, automation rules, PDF reports and approval rules [1].
- Odoo's official eLearning has dedicated Studio lessons titled Approval rules, Customize reports and Customize views [2], and the developer onboarding course includes a nine-lesson report customisation use case and a module on automation triggers and scheduled actions [3].
- The Odoo App Store lists categories including Accounting, Localization, Manufacturing, Warehouse, Website and Extra Tools. On 18 October 2026 its most downloaded listings included an MCP Server, Accounting add-ons for Community and an AI dashboard and KPI builder [4].
- Odoo's pricing and upgrade documentation tells us who maintains each kind of change [5][6].
- Our own delivery experience as an Official Odoo Partner, which we label clearly as practitioner judgement.
The order below is therefore not a ranking by frequency. It groups the requests we see most often, starting with the ones Odoo makes easiest.
The evidence behind each customisation type
What Odoo itself documents, teaches or lists for each type
| Customisation type | Studio docs | Odoo eLearning | Related App Store category |
|---|---|---|---|
| Fields and views | ✓ | ✓ | n/a |
| PDF reports | ✓ | ✓ | n/a |
| Approval rules | ✓ | ✓ | n/a |
| Automation rules | ✓ | ✓ | n/a |
| Integrations | ✕ | n/a | Accounting, Sales, Warehouse |
| Localisation | ✕ | n/a | Localization |
| Website and eCommerce | ✕ | n/a | Website, eCommerce |
| Dashboards and KPIs | n/a | n/a | Most downloaded snapshot |
Sources: Odoo Studio docs (v19), Odoo eLearning, Odoo Apps Store (snapshot 18 Oct 2026).
The list
The eight most common Odoo customisations
For each type: what it is, when it earns its keep, and the standard feature to try first.
1. Custom fields and views
Adding a field to a form, a column to a list or a filter to a search is the most frequent request on any project. In Studio it takes minutes and survives upgrades well. Avoid adding fields nobody will fill in: every mandatory field slows data entry and every unused one clutters reports.
2. PDF reports and documents
Quotations, invoices, delivery slips and purchase orders are customer-facing, so businesses want their branding, terms and layout. Studio's report editor handles most changes; complex conditional layouts need QWeb templates in code. Try first: the standard document layout settings for logo, colours, fonts and footer.
3. Approval rules
Purchase approvals above a value, discount sign-off, or a manager check before a quotation is sent. Studio adds approval rules to buttons without code. Try first: standard settings such as the purchase order approval threshold, and access rights that limit who can confirm.
4. Automation rules
Send an email when a stage changes, assign an activity, update a field on a schedule. Automation rules are a Studio feature, but rules that run Python code are treated as custom code at upgrade time [6].
5. Integrations
Connecting Odoo to an existing payroll, carrier, marketplace, bank or legacy system. This is usually the largest and riskiest customisation because both ends change over time. Try first: Odoo's native connectors, for example its documented shipping integrations for DHL, UPS, FedEx, Sendcloud, EasyPost and others [7], then a maintained App Store connector, then the external API (Custom plan).
6. Localisation and tax
Odoo provides fiscal localisations for dozens of countries [8]. For the UK, Odoo documents modules for UK accounting, HMRC MTD VAT, BACS payment files and the Construction Industry Scheme [9]. Gaps remain, notably UK payroll, which Odoo does not provide natively. Fill gaps with connectors, not by rewriting tax logic.
7. Website and eCommerce
Themes, product page layouts, checkout steps and B2B pricing rules. Most layout work is done in the website builder; bespoke checkout logic needs code and careful testing at every upgrade.
8. Dashboards and KPIs
Management packs and operational dashboards. Standard graph and pivot views and spreadsheet dashboards cover most needs, which is why we build reporting before writing code. Demand is visible on the App Store, where an AI dashboard and KPI builder was among the most downloaded listings in October 2026 [4].
Configure first: what to try before you customise
Thoughtlogik guidance, ordered from least to most maintenance
| Request | Try first (standard) | Customise when |
|---|---|---|
| New data to capture | Existing fields, tags, notes | The data drives a report, rule or integration |
| Branded documents | Document layout settings | Legal or customer terms need conditional layouts |
| Sign-off before action | Standard approval settings | Rules depend on several values or teams |
| Repetitive follow-ups | Activities, email templates | A clear trigger and owner exist |
| Connect another system | Native connector or App Store module | No maintained connector exists |
| Management reporting | Pivot, graph, spreadsheet views | KPIs need data Odoo does not store |
Practitioner guidance from Thoughtlogik projects. Not a vendor statement.
The hidden cost
What happens to customisations at upgrade
Odoo releases a new major version every year and supports each one for three years. Whether a customisation moves with you, or has to be rebuilt, depends on how it was made.
Odoo's support policy gives each major version three years of standard support, covering helpdesk, bug fixes and security updates. Version 17.0 (November 2023) reached its end of standard support in September 2026, 18.0 (October 2024) runs to September 2027 and 19.0 (September 2025) to September 2028 [10]. So a business that stays supported will upgrade at least every three years.
Odoo's upgrade service converts standard apps and data. Its documentation is explicit about what is and is not included [6]:
What Odoo's upgrade service covers
Summarised from Odoo's upgrade documentation
| Item | Covered by Odoo upgrade? | What it means for you |
|---|---|---|
| Standard apps and data | ✓ | Converted by Odoo |
| Studio customisations | ✓ | Covered while Studio is installed and its subscription active |
| Code under a maintenance of customisations subscription | ✓ | Covered by that subscription |
| Custom modules (in-house or partner) | ✕ | Source must be ported to the new version first |
| Code added to standard modules | ✕ | Must be rewritten or removed |
| Python automated actions | ✕ | Must be checked and fixed |
| Migration from another ERP | ✕ | A separate migration project |
| Data clean-up and training | ✕ | Your team or partner |
Source: Odoo upgrade documentation and Odoo support policy, checked October 2026.
The practical rule: every custom module carries a porting and retesting cost at every version. Odoo also states on its pricing page that maintenance of custom code is not included in any subscription [5]. Budget for it, keep custom modules small and documented, and prefer Studio or maintained App Store modules where they do the job. Odoo's developer guide explains the steps for upgrading a customised database [14].
Licensing
Studio, apps or code: what each route costs
The route you choose for a customisation also decides which Odoo plan and hosting you need.
- Studio is included only in the Custom plan. Odoo's pricing page notes that installing Studio on the free plan moves you to Custom [5].
- Custom Python modules cannot run on Odoo Online. They need Odoo.sh (hosting charged extra) or on-premise, both on the Custom plan [5].
- The external API used by most bespoke integrations is also a Custom plan feature [5].
- App Store modules are built by third parties. With over 40,000 community apps listed [11], quality and upkeep vary, so check the publisher, version support and reviews before installing.
Odoo licence per user per month, UK
Studio, multi-company and the external API need the Custom plan
Source: odoo.com/pricing, yearly billing, ex VAT, checked from the UK on 18 Oct 2026. Prices change, so check the vendor page.
For a 20-user business, the gap between Standard and Custom is £14 per user per month in year one and £19 after that, before any development cost. That is often the real price of a customisation, so it belongs in the business case.
Quick check
Do you really need that customisation?
Before you approve a change request, tick every statement that is true.
0/6
Practical guidance
When to avoid customising Odoo
Customisation is not bad. Unplanned customisation is. These are the patterns we most often advise clients to drop.
Odoo's own guidance points the same way. Its original implementation methodology deploys apps in phases, each with onboarding, data import, training and go-live, rather than designing everything up front [15]. Odoo partner Captivea describes checking for an existing marketplace module before commissioning custom work [13]. The case for customisation is strongest where a process is a genuine source of competitive advantage. When FGY replaced SAP Business One with Odoo in 2017, the reason given was that SAP's design could not be adapted to its business [12]. Flexibility matters, but it should be spent where it pays back.
Red flags and better options
Thoughtlogik guidance from Odoo implementation and rescue projects
| Red flag | Why it hurts | Better option |
|---|---|---|
| Rebuilding the old system inside Odoo | Locks in old workarounds, adds code | Map outcomes, then adopt Odoo's flow |
| Changing core accounting or valuation logic | High audit and upgrade risk | Use standard costing methods and journals |
| One-off reports in code | Breaks at upgrade, few users | Pivot, graph or spreadsheet dashboards |
| Integrations without an owner | Silent failures, bad data | Maintained connector plus monitoring |
| Untested App Store modules | Unknown quality and upkeep | Check publisher, version and reviews |
| Studio changes nobody documented | Hard to support or undo | Keep a change log for every field and rule |
Practitioner guidance. Not a vendor statement.
Our approach: in the Scope and Craft phases of our SCALE method we run each request through the same ladder: standard setting, Studio, maintained App Store module, then custom module. Anything that reaches the last rung gets an owner, documentation and an upgrade estimate before it is built.
FAQs
Odoo customisation FAQs
Cannot see your question? Our UK consultants are happy to talk it through.
What is the most common Odoo customisation?
No vendor or survey publishes a ranking. Based on Odoo's own Studio documentation and training, and our project experience, the most frequent requests are custom fields and views, branded PDF documents such as quotes and invoices, approval rules and automation rules. Integrations are less frequent but usually the largest piece of work.
Do I need the Odoo Custom plan to customise?
For Studio, yes. Studio is only included in the Custom plan, as are the external API and the option to host custom Python modules on Odoo.sh or on-premise. On Standard you can still configure settings, use the website builder and install apps available on Odoo Online.
Are Studio customisations kept when Odoo upgrades?
Odoo's upgrade documentation says Studio customisations are covered while Studio is installed and its subscription is active. Python automated actions and custom code are not covered. Always test an upgrade on a copy of your database before switching.
Does Odoo support maintain my custom modules?
No. Odoo's pricing page states that maintenance of custom code is not included in the subscription. Custom modules from your team or a partner must be ported to each new version and tested before upgrading, unless they are covered by a separate maintenance agreement.
How often does Odoo release a new version?
Odoo releases a new major version roughly every year, and each gets three years of standard support. For example, 18.0 arrived in October 2024 and 19.0 in September 2025. Odoo Online customers also receive interim SaaS releases.
Is it better to use an App Store module or custom code?
A maintained App Store module is often quicker and cheaper, but quality varies across more than 40,000 community apps. Check the publisher, the supported versions and reviews, and test it. Custom code makes sense when no module fits and the process is genuinely distinctive.
How can I keep customisation under control?
Agree a configure-first rule, keep a change log of every Studio field and rule, give each custom module an owner, and cost every change across the next two upgrades. Our Odoo optimisation reviews start with exactly this audit.
Sources
- Odoo, Studio documentation (19.0) odoo.com/documentation/19.0/applications/studio.html
- Odoo eLearning, Studio lessons: Approval rules, Customize reports, Customize views odoo.com/fr_FR/slides/slide/customize-views-4614
- Odoo eLearning, developer onboarding course odoo.com/slides/onboarding-studio-68
- Odoo Apps Store, categories and most downloaded (snapshot 18 Oct 2026) apps.odoo.com/apps/modules
- Odoo, pricing (UK, checked 18 Oct 2026) odoo.com/pricing
- Odoo, upgrade documentation (19.0) odoo.com/documentation/19.0/administration/upgrade.html
- Odoo, third-party shipping connectors (19.0) odoo.com/documentation/19.0/applications/inventory_and_mrp/inventory/s
- Odoo, fiscal localisations (16.0) odoo.com/documentation/16.0/applications/finance/fiscal_localizations.
- Odoo, United Kingdom localisation (19.0) odoo.com/documentation/19.0/applications/finance/fiscal_localizations/
- Odoo, standard and extended support policy odoo.com/documentation/master/administration/standard_extended_support
- Odoo homepage (users and community apps, Oct 2026) odoo.com
- Odoo, FGY replaces SAP Business One with Odoo (2017) odoo.com/blog/6/post/310
- Captivea (Odoo partner), Odoo apps guide captivea.com/odoo/odoo-apps
- Odoo, upgrading a customised database (developer guide) odoo.com/documentation/19.0/developer/howtos/upgrade_custom_db.html
- Odoo, implementation methodology (9.0 documentation) odoo.com/documentation/user/9.0/getting_started/documentation.html
Sources checked 18 October 2026. Where we give guidance or risk ratings without a citation, it is Thoughtlogik practitioner judgement. Odoo publishes no ranked data on customisations.
Keep exploring
Related Odoo services and guides
Start your project
Planning Odoo changes? Get them right first time.
Tell us what you want Odoo to do differently. An Odoo consultant will review the request, suggest the standard route where one exists and estimate the upgrade impact of anything custom.
- Free, no-obligation review
- Configure-first recommendations
- Clear view of upgrade impact
Thinking about customising Odoo?Talk to a UK Odoo consultant first.
Book a free call