DeadlinesE-Invoicing by Dec 31, 20262026 Computerized Books in ORUS by Jan 30, 2027E-Invoicing Dec 31 · ORUS Jan 30

Check Readiness
TechNext

Standard first: when to customise Odoo, and when not to

Every customisation is paid for twice: once when it is built, and again at every upgrade. This is how TechNext decides what to configure, what to build in Studio, and what deserves custom code.

By TechNext · · Updated · 4 min readTechNext & Odoo

Key takeaways

  • There are three levels of change in Odoo: configuration, Studio and custom modules. Each costs more to build and to maintain than the one before.
  • Odoo releases a major version every year, and every customisation has to be tested, and often reworked, at each upgrade.
  • Customise for rules, differentiators and missing integrations. Don't customise to recreate an old system's screens.

"Can Odoo do it exactly the way we do it now?" is the question behind most customisation requests. Often the honest answer is: it could, but it shouldn't. Standard Odoo encodes how thousands of companies run sales, stock and accounting, and bending it to match an old habit usually costs more than changing the habit. That is why TechNext works standard first. It is not a refusal to customise. It is a rule about what earns the right to be customised.

The three levels of change

LevelWhat it isCost at upgrade
ConfigurationSettings, workflows, taxes, routes, approval rules, templates and access rightsLow: carried forward by Odoo
StudioNo-code fields, views, reports and automations (Custom plan)Medium: needs checking after each upgrade
Custom modulesPython code for new logic, integrations or apps (Odoo.sh or on-premise)High: must be ported and tested every version

Odoo ships a major version every year, and Odoo 20 has just arrived. Each custom module has to be ported to the new version and retested, and each Studio change checked, before a company can upgrade. A database with dozens of customisations can end up stuck on an old version because upgrading it has become a project of its own.

When customising is the right call

  • A legal or regulatory requirement that the country localisation does not cover.
  • A real differentiator: the part of the process that makes the business better than competitors, such as a unique pricing model or production method.
  • An integration with no connector: a bank, marketplace, machine or legacy system Odoo cannot reach through standard connectors.
  • A measured cost: a step that costs real hours every week, where configuration cannot help.

When it isn't

  • Recreating the old system. Old screens and old field names feel familiar, but familiarity fades in weeks, and the code stays.
  • One person's preference. A layout one user prefers is not worth a module every user maintains.
  • Rare edge cases. Something that happens twice a year is usually cheaper to handle by hand, with a note in the procedure.
  • Problems a report would solve. Many "we need a new screen" requests are really "we need to see this number", and a saved filter or spreadsheet view does it.

Five questions before approving any customisation

  1. Does standard Odoo do this, perhaps with a setting we haven't switched on?
  2. Could we change the process instead, and would anyone outside the company notice?
  3. Can Studio do it without code?
  4. What does it cost to maintain through the next three upgrades, not just to build?
  5. Who owns it: who will notice if it breaks, and who will fix it?

If a request survives all five, it is worth building, and worth building properly: as a clean module in version control, tested on staging and documented, rather than as a quick patch.

Should we build it?Five questions, three levels of change

Five questions before approving any customisation: does standard Odoo do it; could the process change instead; can Studio do it without code; what does it cost to maintain through the next three upgrades; and who owns it. Configuration costs least at upgrade, Studio needs checking after each upgrade, and custom modules must be ported and tested every version.

The questions, levels and upgrade costs are this article's; the example requests are its own "when it isn't" cases and its integration case.

How this plays out on a TechNext project

During discovery, every gap between your process and standard Odoo is written down with a proposed answer: configuration, Studio, a process change or a custom module. You see the trade-off before anything is built. Custom modules are built on staging, kept in version control and included in upgrade testing, which is part of our support plans. When a client asks for tailored modules and workflows, that work sits under our ERP customisation service, with the same rules.

The result is a system that fits the business and still upgrades cleanly. You can read how the whole project runs in How an Odoo implementation works.

Common questions

What is the difference between Odoo configuration and customisation?

Configuration uses the settings and options Odoo already has, such as taxes, workflows and approval rules. Customisation changes the software itself, either with Odoo Studio (no code) or with custom Python modules.

Do customisations make Odoo upgrades harder?

Yes. Odoo releases a major version every year, and custom modules must be ported and retested for each one. Studio changes need checking too. The fewer customisations, the easier each upgrade.

Does TechNext build custom Odoo modules?

Yes, when a requirement justifies it. TechNext builds custom modules on staging, keeps them in version control and includes them in upgrade testing, after checking that configuration or Studio can't do the job.

Odoo Ready Partner

About TechNext. TechNext Pte. Ltd. is a BIR compliance and integration partner for accounting firms and finance teams: an Odoo Ready Partner headquartered in Singapore, with its main development and consulting hub in Taguig City, Metro Manila. We plug Odoo into the system you already run, and our own experts implement it end to end (discovery, configuration, data migration, training and support), set up with the Philippine (BIR) and Singapore (GST) localisations, for clients in 25+ countries. We are not affiliated with, accredited by or acting for the BIR or any government agency, and we do not file or register on your behalf. About us · Get my custom blueprint

Talk to a compliance engineer How BIR CAS set-up works

More from the blog.

All articles

You don't need to hire your own team.

TechNext sets up your Odoo, can build your website and brand on it, and stays on after go-live, in Singapore and the Philippines. An adviser reviews your situation first.