An Odoo upgrade is not complete when the new database goes live. For Canadian manufacturers, the real work begins when teams return to daily planning, production, inventory, and customer service tasks. Odoo 20 should mark the start of an improvement cycle.
A successful technical migration does not automatically remove old spreadsheets, duplicate processes, or workarounds that slow down the plant and office. After upgrading to Odoo 20, manufacturers should review how the new version supports real production and planning workflows, including Manufacturing Orders, work order planning, replenishment, inventory visibility, and connected business processes. Labour availability, supply-chain changes, delivery expectations, and margin pressure make it even more important to turn the upgraded system into a reliable operational tool.
Turn Your Odoo 20 Go-Live Into Manufacturing Gains
After go-live, reserve time and budget for a focused review of how Odoo 20 performs in real manufacturing operations. The goalis to identify where Odoo 20 can improve production planning, material availability, work order execution, inventory visibility, and coordination between the plant and office.
Start by reviewing the workflows that have the greatest operational impact. Check how planners create and manage Manufacturing Orders, how replenishment responds to material shortages, how work orders are planned and executed, and how production changes affect inventory and delivery commitments. Odoo 20 introduces changes to Manufacturing Orders, backorder planning, and work order planning that should be assessed against the way your teams actually operate.
Then look beyond individual manufacturing transactions. In Odoo 20, Sales, Inventory, Manufacturing, and Purchase can work with connected records in the same database. For example, a confirmed sales order can trigger a Manufacturing Order for a product configured for replenishment, while the manufacturing process uses the same product and inventory records for component availability and stock movements. If additional materials are needed, Odoo can trigger replenishment through a purchase order or another manufacturing order, depending on the configured routes. This connected flow helps reduce duplicate data entry and gives teams visibility from customer demand through production and delivery.
The review should also identify opportunities to simplify the system after the upgrade. Some custom reports, fields, automated actions, or third-party applications may still exist because they solved a problem in an earlier version. If Odoo 20 now provides standard functionality for the same business need, the old customization may no longer be necessary.
Bring manufacturing, operations, inventory,
purchasing, sales, finance, IT, and your implementation partner into the review
where their processes overlap. This makes it easier to prioritize improvements
based on measurable outcomes such as fewer manual transactions, more reliable
production planning, better inventory accuracy, faster issue resolution, and
clearer production and cost reporting.
Set the Right Scope for Your Odoo Upgrade
Post-upgrade planning should cover more than system performance. Once users return to daily operations, businesses need to understand which Odoo 20 changes require attention, which processes should be reviewed, and which tasks remain the responsibility of the business or its implementation partner.
Manufacturing teams should start by reviewing Odoo 20 changes that may affect daily production and planning, including:
- Draft and confirmed Manufacturing Orders — the “Auto Confirm Production” setting on the Manufacturing operation type
- Backorder planning
- Work Order Planning, Gantt, and Kanban views
- Splitting ongoing Manufacturing Orders
- Resetting validated or canceled Manufacturing Orders to draft
These changes should be assessed against the way planners, production managers, and shop-floor teams actually work. A feature that is technically available in Odoo 20 still needs to fit the company’s production planning, replenishment, scheduling, and execution processes. Odoo 20 also changes Manufacturing Order cost reporting: the MO Cost field shows a provisional cost while the order is in progress and the real cost once the order is complete.
Your deployment also matters. Odoo Online is managed by Odoo and does not support custom modules. Odoo.sh supports custom modules and requires an Odoo Enterprise subscription that includes Odoo.sh. On-premise gives businesses control over their own infrastructure and supports custom modules, but infrastructure and maintenance remain the customer’s responsibility. Confirm the applicable Odoo edition and hosting setup before deciding which post-upgrade improvements belong in the roadmap.
For Enterprise databases, Odoo’s Upgrade Service handles the technical upgrade of standard Odoo applications and database data within its supported scope.
It can also cover Studio customizations as long as Studio is still installed and the respective subscription is still active, as well as additional modules covered by an applicable maintenance agreement. The service does not replace post-upgrade validation or automatically adapt custom code and third-party modules outside that scope.
Businesses using custom modules, third-party extensions, or other non-standard components should therefore identify who maintains them and who is responsible for adapting and validating them after the upgrade. This distinction should be established before post-upgrade work is planned and budgeted.
Validate Workflows Across the Plant and Office
Feature lists are useful, but workflows reveal where the friction lives. Follow an order from demand through completion and ask where staff still turn to email, spreadsheets, verbal handoffs, or duplicate data entry.
Start with sales order confirmation, material availability, Manufacturing Order creation, work order execution, quality checks, backorders, finished-goods receipt, and invoicing. A process may look efficient on the shop floor while still being held back by purchasing delays, unclear inventory status, or slow accounting updates.
For manufacturing teams, this review should also reflect Odoo 20-specific workflow changes. Check how Manufacturing Orders move between draft and confirmed states, how backorders are planned, and how work orders are scheduled and managed through the updated planning tools.
Connected functions deserve the same attention. Review replenishment rules, purchasing approvals, supplier lead times, sales commitments, landed costs, accounting entries, and reporting together. This prevents one department from improving its process while a bottleneck remains upstream or downstream.
Structured feedback helps turn complaints into useful priorities. Ask each team where delays, uncertainty, or repeat work appear most often:
- Planners may flag late status updates or poor visibility
- Warehouse teams may identify inaccurate stock information
- Buyers may see approval or supplier-data delays
- Finance teams may need clearer cost reporting
- Customer service teams may struggle with order-status questions
Recurring issues are usually more useful than one-off requests. If a report does not support timely decisions or a transaction takes too many steps, it deserves review.
Use Odoo 20 to Reduce Operational Friction
An Odoo upgrade can reduce operational friction when businesses make deliberate choices after migration. Carrying forward every legacy process may preserve unnecessary maintenance work, inconsistent user experiences, and avoidable operational risk.
Create an inventory of reports, approval flows, dashboards, spreadsheets, manual handoffs, and third-party applications used around Odoo. Rather than sorting them only by department, describe the business problem each item was meant to solve. That makes it easier for stakeholders to decide whether the need still exists.
Next, compare each process against standard Odoo 20 capabilities and current operating requirements. Review whether existing customizations, reports, automated actions, or third-party apps are still needed, or whether Odoo 20 now provides standard functionality that can support the same business need.
Classify every item into one of four outcomes:
- Retain
- Simplify
- Replace with standard functionality
- Retire
Duplicate fields, abandoned reports, outdated approval steps, and apps with overlapping features are common review candidates. Odoo’s Upgrade Service does not cover the upgrade of additional in-house or third-party modules that are not covered by a maintenance agreement, making unnecessary customizations and overlapping applications a practical consideration for future upgrades.
Removing them can make future Odoo upgrades easier to manage and give users a cleaner, more consistent system.
Strengthen Integrations, Performance, and Adoption
Some of the most disruptive post-upgrade issues happen outside a Manufacturing Order. Review integrations with e-commerce platforms, shipping carriers, customer portals, payroll systems, warehouse tools, supplier systems, business intelligence tools, and other business applications. Look for failed jobs, duplicated transactions, delayed updates, missing error alerts, and data exchanges that no longer need to run.
Review Scheduled Actions, Automation Rules, and Server Actions. Older processes can duplicate Odoo 20 functions, create unnecessary records, send conflicting notifications, or rely on business logic that no longer matches how your teams work. System performance and usability should be judged through daily tasks, including slow order processing, cumbersome screens, unclear permissions, and reports that create more questions than answers.
Turn these findings into a funded post-upgrade roadmap. Rank work by business value, operational risk, effort, dependencies, and expected payback. Separate quick wins, such as removing unused fields or simplifying reports, from larger work involving integrations, data governance, and advanced planning. Assign an owner and a measure for each priority, such as planner time saved, fewer manual transactions, better inventory accuracy, fewer production delays, or clearer cost reporting.
Make Post-Upgrade Decisions With Confidence
Kodershop helps manufacturers connect operational priorities to a practical Odoo upgrade strategy that supports measurable performance improvements. Our team can assess where your processes, data, and reporting need attention as production demands change. To discuss your next phase of planning, contact us for a focused consultation.