An Odoo upgrade is not a routine technical task when your manufacturing setup contains custom workflows. One small change to production logic can affect planning, warehouse work, operators, traceability and finance at the same time.
When we assess an upgrade, we look beyond whether the database can be migrated. The real question is whether the upgraded system still supports how you plan, make, move and trace products on a normal working day.
An upgrade tests every manufacturing shortcut
Custom manufacturing processes usually grow over time. A planning rule for scarce materials, an extra approval before production starts, a barcode screen built around one warehouse routine. Useful changes, but each one leans on how Odoo behaves in the version you are leaving behind.
An upgrade can alter screens, field behaviour, workflows and the way standard modules work together. That matters as soon as custom logic touches:
Where custom logic touches production
- Production order steps and work orders
- Component reservations and automated replenishment
- Quality checks and subcontracting flows
- Serial number tracking and traceability
- Stock movements, backorders and financial postings
Problems usually surface at the handover points between teams. A planner releases an order, while the warehouse team sees unexpected reservations. Operators complete a work order, but traceability records no longer follow the expected path. Finance then finds that stock valuation or invoicing behaves differently.
The goal is not to assume every customisation will fail. It is to know, before go-live, where a change could interrupt production.
Map custom logic before the upgrade
Start with a proper inventory of everything that changes standard behaviour. That is more than the modules a developer wrote. Studio changes, automated actions, tailored reports, dashboards, approval flows, security rules and modified screens all belong in the review.
Not every change deserves the same attention. A renamed field is easy to recreate or remove. A rule that decides whether a component can be reserved for a production order needs a much deeper check. Sort by operational impact, not by who originally requested it.
Three questions per customisation
- What problem does this solve today?
- Who depends on it during daily work?
- What happens if it behaves differently after the upgrade?
The newer version sometimes covers part of the requirement with standard functionality. Removing unnecessary custom code reduces maintenance and makes later upgrades easier. Still, standard is not automatically a better fit. Before you replace working logic, the new process has to work for the people on the shop floor, in the warehouse and in planning.
Recheck production flows that standard Odoo now covers
A manufacturing review follows the complete order flow, not just the Manufacturing app. Sales demand triggers purchasing, stock moves, production orders, quality checks, deliveries and invoices. If a change affects one link, the effect may only show several steps later.
We start with the flows that carry the greatest operational risk: bills of materials, multi-level production, work centres, capacity planning, component availability, scrap, backorders and traceability.
Generic demo data rarely shows the problems that actually matter.
Test with scenarios your team recognises: an urgent order, a missing component, a partial production run, a product with serial numbers and a late supplier. Each scenario shows what users see, which records are created and whether the next team can continue without a manual workaround.
Pay close attention to the exceptions. Normal production is easy to test. The pressure comes when stock is short, an order changes halfway through, quality puts goods on hold, or an operator has to record scrap. If custom logic was built for those situations, it deserves a test case of its own.
Protect data, integrations and shop-floor devices
Data quality belongs in the scope. Incorrect bills of materials, old routings, duplicate products, inconsistent units of measure and incomplete serial numbers cause failures that look like upgrade issues. Often the migration simply exposes data that was already unreliable.
Check the records that drive production decisions up front: active product data, bills of materials, work centre settings, supplier details, stock locations and traceability records. Cleaning up does not mean every historical record has to be perfect. It means the operational data can be trusted after go-live.
External connections need the same discipline. List every system or device that exchanges data with Odoo: barcode scanners, label printers, shipping platforms, accounting tools, planning software, machine connections and custom APIs. Give each connection a named owner and a test case.
Technical testing alone is not enough. Operators need to know whether tablet screens, barcode actions, work-order instructions or quality forms have changed. A migration can succeed while production still slows down, because familiar tasks take longer or appear somewhere else.
Plan testing around real production dates
The best go-live date follows your operating calendar, not an arbitrary IT deadline. Production peaks, major deliveries, stock counts, supplier lead times and the finance close all decide how much room you have.
Autumn is a good moment to review that calendar and decide whether an upgrade fits before year-end, in a quieter period, or after the peak. There is no universal quiet window. The choice depends on your actual production load and on what disruption costs.
Phases with an owner for each
- Technical migration and initial checks
- Functional testing of the configured processes
- User acceptance testing with real scenarios
- Training for the affected teams
- Go-live checks and issue management
Every phase has named decision-makers. Testers know what a pass looks like, how to log an issue and who decides whether it blocks go-live. That keeps teams from reporting concerns nobody owns.
Training sits close enough to go-live that people remember the changes, and early enough to surface unclear steps. The warehouse and shop floor are not the last audience after planning and finance have already signed off.
Turn your findings into a safer go-live
An upgrade is easier to steer when you know what is custom, what is business-critical and what can be simplified. The aim is not to preserve every historical modification. It is to protect the processes that keep materials available, production moving and products traceable.
A focused upgrade assessment gives you a usable scope before migration work begins. Review custom modules, manufacturing workflows, data quality, integrations, devices and timing together. That creates a clearer basis for testing, training and go-live decisions, with fewer surprises under real production pressure.
Make your upgrade plan practical
We turn the technical decisions into a migration plan that fits your production reality. Our work on Odoo upgrades and migrations covers the custom development review, the test preparation and the go-live checks.
Schedule a conversation