A manufacturer we'll leave unnamed ran Odoo 10 for seven years. Eight custom modules, one of them an extended MRP module the whole plant depended on. Nobody planned to stay on version 10 that long. Each year the upgrade looked slightly more expensive than the year before, so each year it slipped, and by the time it became unavoidable the quote had roughly tripled. That is what upgrade debt looks like from the inside. It never arrives as one bad decision. It compounds quietly out of a dozen reasonable ones.
Manufacturing is where this happens most, and there's a structural reason for it. The MRP layer is where Odoo gets bent hardest to fit a real shop floor, and every bend is code somebody has to carry forward when the next version ships.
Why the Manufacturing Layer Attracts the Most Debt
Look at what a typical Odoo customization company gets asked to build for a manufacturer. Multi-level BoMs with revision control are usually first. Then work-order routing that mirrors the actual sequence on the floor rather than the default one. Finite-capacity scheduling comes up on almost every engagement. So do subcontracting flows for whatever operations get outsourced. Quality checkpoints pinned to specific work centers. Replenishment rules that match how your buyers really buy instead of how the demo assumed they would.
None of those requests is unreasonable. Most of them are the difference between an ERP the floor uses and one it routes around with spreadsheets. The problem is what they have in common: nearly all of them touch the core manufacturing models, which happen to be the ones Odoo keeps changing from one release to the next.
Odoo 19 reworked the ORM and the web framework underneath everything (the asset pipeline changed too). Modules that reach into those areas break on upgrade. Sometimes loudly. More often silently, which is worse, because a customization that overrides a core method instead of extending it simply stops doing its job the moment that method's signature changes, and nothing tells you. On a finance module that's an annoyance. On the module that releases work orders to the floor, it's a stopped line.
The Clock You’re Actually Running Against
Odoo ships a major version every year. Each one gets about three years of active support, with a couple more to finish migrating before the door closes. Since April 2026, anything more than three versions behind carries a 25% surcharge on the annual subscription.
Put numbers on that. A 50-user plant on a $30,000 subscription that's sitting on an old version pays $7,500 a year extra for the privilege of not upgrading. Three years of deferral is $22,500 in surcharge alone. The upgrade itself still has to happen at the end of it, now against a larger version gap, and emergency upgrades done under that kind of pressure cost two to three times what a planned one would have.
So the real cost of a customization isn't the build quote. It's the build quote plus what it will cost to carry that code across every upgrade for as long as you run Odoo. Most manufacturers never see that second number until it's already due.
What Cheap-to-Carry Customization Looks Like
Not all custom code ages the same way, and that distinction should be settled before you sign anything, because some of it upgrades in an afternoon while some of it needs a rewrite every single version.
The cheap kind extends rather than overrides. It adds a field or inherits a model. It hooks into an existing workflow at a point Odoo already defined for that purpose, so when the platform changes underneath, the extension usually still fits. The expensive kind reaches inside a core method and replaces the logic outright, or it duplicates a standard model with tweaks and hopes nobody notices. Every one of those needs a developer to re-examine it by hand, release after release.
Then there's the category most manufacturers overlook entirely. The Odoo ERP customization you never needed to write. The Odoo Community Association maintains a large library of manufacturing modules, peer-reviewed and migrated forward by the community with each version, and a surprising share of “custom” requests already exist there. A subcontracting variant or a BoM revision workflow that already exists as an OCA module costs you nothing to carry. A bespoke equivalent costs a developer-day per upgrade, indefinitely. Any Odoo customization company worth hiring checks OCA before opening an editor.
Questions That Surface the Debt Early
Vendor conversations about Odoo ERP customization tend to stay on features. Can you build it? How long will it take? Those matter, but they say nothing about what the work will cost in year three, so it's worth asking a different set of questions alongside them.
Start with whether a given module extends a core model or overrides it. If the answer involves the word “override,” ask what happens when that method changes in the next release.
Then ask whether anyone checked for an existing OCA module first. A vendor who hasn't looked is either unfamiliar with the ecosystem or would rather bill for a rebuild, and neither is a great sign.
Ask who owns the upgrade plan for this specific module. Not the platform upgrade in general. This module. If nobody has thought about it yet, you've just located where the debt will accumulate.
And one that sounds like a trick question but isn't: which of our requests would you talk us out of? Firms like BiztechCS (an Odoo Ready Partner with 25+ certified Odoo experts) tend to spend the first weeks of a manufacturing engagement arguing against roughly a third of the customization list, because the alternative is an upgrade bill the client didn't budget for two years later.
Where This Doesn’t Apply
Some manufacturing processes are genuinely unusual enough that no standard or OCA module covers them, and deep customization is the right call. A proprietary scheduling logic your whole competitive position rests on deserves custom code, and deserves a budget line for maintaining it. The mistake isn't customizing. It's customizable without a ledger, so the carrying cost surprises everyone at once instead of being paid down a little every year.
If you're a manufacturer scoping Odoo work right now, ask your prospective Odoo customization company for two quotes on every module: the build, and the estimated annual cost to carry it through upgrades. The second number is the one that decides whether you're still happy with the decision in 2029. At BiztechCS, we give both up front.
