Skip to Content

Continuous Improvement at Odoo — An Example

From custom to standard — how to capitalize on each version to create more value.
October 13, 2025 by
Continuous Improvement at Odoo — An Example
ANOR, Cyrille de LAMBERT

Auguria News

Odoo moves fast, and these are not empty words. With each version, needs once handled with custom development move into the standard. The result: less technical debt, calmer version upgrades, and energy reinvested in what matters — your processes, your data, your teams.

At Auguria, we know how to code… but we prefer not to code when the product already does the job. Our profession is naturally shifting toward consulting and coordination.

The general principle: when the standard catches up with custom

  • Virtuous circle: integrators and clients experiment, then the publisher generalizes what serves the greatest number. Everyone gains in robustness and simplicity.
  • Fewer overrides: fewer QWeb inheritances, fewer patches, fewer side effects.
  • Longevity: what is native benefits from fixes, official documentation and continuous improvements.
  • Better-spent budget: we shift effort from code to adoption, data quality and management.

Our concrete example Odoo 17 → Odoo 19

The business need. Present quotations “by sections” by hiding the line-by-line detail and showing only each section’s subtotal on the customer side.

Before Odoo 18.

We had developed a custom module sale_report_hide_price in Sales that:

  • hid the price of lines within a section
  • showed only the subtotal on the PDF and the portal

Today with Odoo 19.

The feature is native: on each section, you enable the option to hide details and display only the subtotal.

Result: our module becomes useless — excellent news.

Immediate benefits.

  • No template override to maintain
  • Cleaner version upgrades
  • Faster setup for sales teams

Mini migration checklist.

  1. Uninstall sale_report_hide_price in the v19 target environment
  2. Enable the “hide details” option on the sections of quotation templates and sales orders
  3. Test three scenarios: multi-section, taxes and discounts, PDF and portal rendering
  4. Inform the sales team with a short illustrated note
  5. Archive the module in the inventory of deprecated custom developments

Moral: what we wrote in code yesterday becomes a checkbox tomorrow. All the better.

What it really changes

  1. Less risk: fewer view inheritances, fewer side effects, fewer regressions
  2. More speed: configuration is faster than development
  3. Better budget allocation: priority to consulting with flow mapping, change management and data governance
  4. Clear return on investment: total costs fall within 12 to 24 months and the application becomes easier to update

Our method for “de-customizing” intelligently

  1. Map: list where there is “custom” work in each step (order → invoice, after-sales, purchasing, production)
  2. Check the standard: see what the new version already does well and how to use it
  3. Choose with common sense: remove, simplify or rewrite only if it brings a real business gain
  4. Test for real: try with concrete cases (taxes, discounts, multi-currency, portal)
  5. Train and document: create templates, checklists and notes directly in Odoo
  6. Measure, then repeat: look at the results and redo the pass at the next version

KPIs to track

  • Standardization rate: percentage of flows covered without custom development
  • Version upgrade time: preparation plus testing
  • Regression rate after migration
  • Adoption: time taken to get to grips with new features
  • Gains: development days avoided, technical debt reduced, TCO at 12 and 24 months

Quick FAQ

Conclusion

Odoo’s continuous improvement does not make integration disappear. It shifts the value. Less code to maintain and more attention paid to your processes, your data, your adoption.

Our promise is simple: make the most of the standard and develop only where it creates a competitive advantage. The rest, we lighten, document, and put you in a position to last.

in Blog
Continuous Improvement at Odoo — An Example
ANOR, Cyrille de LAMBERT October 13, 2025
Share this post
Tags
Our blogs

Updated on 04/01/2026

A question about your project? Talk to a consultant.

Book 30 minutes