Odoo Standard vs Custom: When to Stay Standard, When to Customise Odoo, and When to Build Instead
What standard Odoo actually includes, the four levels of customisation from configuration to custom modules, what each level costs at every upgrade, and a simple way to decide how far to go before a custom build makes more sense.
Four levels of Odoo customisationFIG.01
Short answer
Standard Odoo is the set of modules Odoo ships and maintains; custom means anything added on top, from Studio fields to custom-coded modules. Stay standard wherever a process can bend to Odoo's way, customise only where the business genuinely differs, and move to a custom build when the custom parts outnumber the standard parts you still use.
Key takeaways
- Standard Odoo covers accounting, sales, purchase, inventory, CRM, HR and more; most companies use a fraction of it well.
- Customisation has four levels: configuration, Studio, custom modules and core changes. Cost and upgrade risk rise sharply at each step.
- Every custom module has to be re-tested or rewritten for each yearly Odoo version; that is the real long-term cost.
- Configure first, customise second, and treat a core change as a last resort.
- If the custom parts outnumber the standard parts you use, a custom system usually costs less over five years.
People search for 'Odoo standard vs custom' for two different reasons. Some are deciding between Odoo and a custom-built ERP; Odoo vs custom ERP answers that one. This article answers the other question: once you have chosen Odoo, how much of it should stay standard, and how far should you customise it before customising stops being the right answer?
What standard Odoo includes
Standard Odoo is the set of applications Odoo builds, tests and upgrades itself: accounting, invoicing, sales, CRM, purchase, inventory, manufacturing, HR, project, helpdesk, website, e-commerce and point of sale, plus country localisation packages for the chart of accounts and taxes. Community Edition is the open-source core; Enterprise adds applications such as Studio, full accounting reports, quality and field service, and is licensed per user.
Standard also means standard workflows. A sales order confirms into a delivery and an invoice in one particular way; stock moves follow Odoo's routes; approvals follow Odoo's model. A large part of a successful Odoo project is accepting those workflows where they are good enough, because everything that stays standard is upgraded for you.
The four levels of customisation
| Level | What it means | Upgrade impact |
|---|---|---|
| 1. Configuration | Settings, user roles, sequences, email templates, approval rules, report layouts and custom fields through the standard tools | Carried forward automatically |
| 2. Studio | Enterprise's no-code tool: new fields, views, simple automations and reports without code | Usually carried forward, but automations need checking after each version |
| 3. Custom modules | Code written for you that adds models, logic, integrations or screens on top of standard | Must be re-tested and often rewritten for every major version |
| 4. Core changes | Editing Odoo's own modules | Blocks upgrades until the change is redone; avoid |
Most of the cost difference between a cheap Odoo project and an expensive one is in rows three and four. Rows one and two are where a good implementer spends the first weeks, because a surprising number of 'we need this customised' requests turn out to be a setting nobody had found.
Where standard is the better choice
- Accounting and tax. The localisation packages are maintained for you; a customised ledger is a liability at audit time.
- Purchase, sales and basic inventory in a company that can follow a normal order-to-invoice flow.
- HR records, leave and expenses, where the process is not a competitive advantage.
- Anything a manager wants changed because it is unfamiliar rather than wrong. Three months of use settles most of those.
Where customisation earns its cost
- Your quotation or invoice format carries information customers rely on and Odoo's templates cannot show it.
- Pricing follows rules Odoo's price lists cannot express: tiers by customer group and season, or prices derived from a formula.
- An integration with a bank, a courier, a marketplace, a government portal or a machine on the shop floor.
- A workflow that is the business, such as a job card in a workshop, a consignment in freight forwarding or batch traceability in a food plant.
- Reports your bank, auditor or parent company require in a fixed layout.
The upgrade tax
Odoo releases a major version every year. Standard modules move with it. Custom modules do not: each one has to be migrated, re-tested and sometimes rewritten against the new version's models. Companies that customised freely in year one often find themselves two or three versions behind by year four, running on an unsupported release because the migration quote is larger than the original build. That is the hidden cost of custom, and it is why the number of custom modules matters more than their size. Software costs after launch explains where that money goes.
Hosting changes the answer
Odoo Online, the hosted edition, runs standard applications and Studio changes only; custom modules are not possible there. Odoo.sh and self-hosting allow custom modules, at the cost of managing the platform. So the hosting choice is also a customisation choice: if the plan is standard plus Studio, Odoo Online keeps things simple; if custom modules are certain, plan for Odoo.sh or a managed server from the start.
When to stop customising and build
There is a point where a company has customised so much of Odoo that it is paying Odoo licence fees, Odoo upgrade costs and custom development costs at once, while using a small part of the standard product. The usual signs: more than a handful of custom modules, core workflows replaced rather than extended, and every upgrade postponed. At that point a custom system built around the actual process, which imports the data from Odoo and keeps a standard accounting package, is often cheaper over five years and far easier to change. Custom ERP vs off the shelf sets out that comparison, and an ERP audit is the right first step if you are already in this position.
Keeping Odoo customisation under control
Map the process before choosing modules
Write down how orders, stock, purchasing and money move today. Most of it will fit standard Odoo once it is written down.
Configure everything first
Exhaust settings, roles, templates and Studio before anyone writes code. Keep a list of what was configured and why.
Give every custom module an owner and a reason
One sentence of business justification per module, so the next upgrade can decide whether it is still needed.
Keep custom code outside the core
Extend standard models; never edit Odoo's own modules.
Budget the next upgrade now
Ask the implementer to quote the migration of each custom module to the next version before you approve it.
We build custom ERP and CRM systems, with the Sea Keepers ERP as one example, and we review Odoo installations that have grown more custom than standard. If you are unsure which side of the line your company sits on, send us how your process works and we will say which parts belong in standard Odoo, which need a module, and which would be better built.
Frequently asked questions
Is Odoo Community enough, or do we need Enterprise?
Community covers accounting, sales, purchase, inventory, CRM and manufacturing for many small companies. Enterprise adds Studio, full accounting reports and several applications, plus support and upgrades, and is priced per user. Decide by listing the applications you will actually use, not by edition.
Can custom modules be added to Odoo Online?
No. Odoo Online runs standard applications and Studio customisations only. Custom modules need Odoo.sh or your own server.
How much does Odoo customisation cost?
It depends on the level. Configuration is part of a normal implementation; Studio changes are measured in hours; custom modules are quoted per module and should come with a migration estimate for the next version. Ask for the cost of the next upgrade alongside the cost of the build.
Does customising Odoo affect support?
Odoo supports the standard product. Problems in custom modules are the implementer's responsibility, which is why the contract should say who maintains them after launch.
/Services in this article
/ERP & CRM Systems by country
Keep reading
All articlesBespoke CRM Software in Saudi Arabia: What Riyadh, Jeddah and Dammam Businesses Should Specify
When a Saudi business needs bespoke CRM software rather than a packaged one, what to specify for Arabic, WhatsApp and SMS, PDPL data hosting and ZATCA invoicing links, how Riyadh, Jeddah and Dammam differ, and how to brief a developer inside or outside the Kingdom.
ERP Audit: How to Check Whether Your ERP Is Actually Working for Your Business
A practical ERP audit for business owners: whether people use the system, whether the data can be trusted, whether stock and accounts reconcile, who can change what, and whether to fix, extend or replace it.
Custom ERP Development for US Companies: What It Involves and How Offshore Teams Deliver It
What a custom ERP for a US business has to handle, from QuickBooks or NetSuite as the ledger to multi-state sales tax and state privacy laws, and how to work with an offshore development team without losing control.
ERP vs CRM: The Differences, What Each Costs and Which to Get First
An ERP runs the operation and a CRM runs the customer relationship. What each one does, where they overlap, what drives the cost of each, and how to decide which your business needs first.