+20 11 00 289 896|+966 53 646 4828|info@extramile-egy.com
← All articles

Odoo Customisation: When to Build a Custom Module and When to Configure

Odoo Customisation: When to Build a Custom Module and When to Configure

Short answer: Configure first, customise second. Odoo's settings, workflows, access rights and report layouts cover far more than most people expect. Build a custom module only when a requirement is genuinely specific to how your business makes money, when it is used often, and when changing the process would cost more than building the feature. Every customisation has a price after go-live: testing, maintenance and upgrades.

Customisation is a large part of what ExtraMile does, so this may sound surprising from us: the best projects we deliver are the ones where we wrote the least code that still did the job.

Three levels of change

Three levels of change
AspectExamplesUpgrade impact
ConfigurationSettings, taxes, price lists, approval rules, warehouses, access rights, email templatesVery low
Light customisationExtra fields, adjusted views, report layouts, automated actionsLow to medium
Custom modulesNew business logic, new documents, integrations, industry workflowsMedium to high; must be maintained and upgraded

A five-question test before building

  1. Is it a real business difference or just a habit? "Our old system did it this way" is a habit. "Our contracts require retention and advance recovery" is a business difference.
  2. How often is it used? A daily process deserves investment. A report needed once a year may be done in Excel.
  3. Can configuration get you 80% of the way? Often a small process change plus configuration is enough.
  4. What happens if you do not build it? Quantify the manual work or risk.
  5. Who will maintain it? Custom code needs an owner through future upgrades.

Customisations that usually pay off

  • Industry workflows: progress billing for contractors, pharmacy counter features, production steps specific to your factory.
  • Integrations: e-invoicing, banks, e-commerce platforms, logistics providers, devices.
  • Controls: approval rules and validations that prevent costly mistakes.
  • Documents your customers or authorities require in a specific format.

Customisations that usually do not

  • Recreating every screen of the old system.
  • Many slightly different reports that answer the same question.
  • Changing standard accounting logic to match old habits.
  • Features requested by one person and used by nobody else.

Rules we follow when we do customise

  • Build in separate modules; never modify Odoo's core code.
  • Keep custom code in a version-controlled repository that the client can access.
  • Document what each module does and why it exists.
  • Write the module so it can be upgraded with Odoo, and test it on each new version.

Frequently asked questions

Will customisation stop us from upgrading?

Not if it is done in separate modules and maintained. It does add work to each upgrade, which is why every customisation should earn its place.

Can our own developers customise Odoo?

Yes. Odoo is open source and uses Python and XML. Agree coding standards with your partner so both teams can work on the same system.

What about Odoo Studio?

Studio, available in Enterprise, handles simple fields, views and reports without code. Complex logic still needs development.

Get a second opinion on your customisation list

Send ExtraMile your requirements, and we will tell you which can be met by configuration and which really need development.

Review my requirements or message us on WhatsApp: Egypt · Gulf

This article was drafted with AI assistance and reviewed and edited by Mohamed El-Baddaly, Chairman of ExtraMile Business Solutions.