AI-generated visual metaphor for checking a sales and stock path. It does not depict real Enersys documents, personnel, or workplace.
Consider one sales order. Sales confirms it, Inventory reserves the stock, the MES receives the manufacturing work, and Accounting issues the invoice under the agreed terms.
If an upgrade makes the screens look better but loses the reservation, breaks the manufacturing handoff, or applies the wrong tax to the invoice, the business has not gained a benefit. An upgrade should be judged by the work that must continue on an ordinary day, not by a feature list that looked good in a demo.
What Odoo announced, and what still needs proof
On September 24, 2026, Odoo launched Odoo 20 at Odoo Experience and published “Meet Odoo 20”. It presents natural-language AI process automation, prompt-based website creation, external AI connections that retain existing access rights, and CRM and Accounting improvements. Odoo Experience Odoo, Meet Odoo 20
Those are features Odoo describes. They are not evidence that every capability will be enabled automatically in every database, subscription, country, or configuration. The system owner must check the contract, edition, hosting model, installed modules, localization, and integrations before planning to use a new feature.
The recommendations below are Enersys guidance for upgrade preparation, not Odoo requirements. Start with the question “Which work must not stop?” Then decide whether a feature helps that work in this environment.
Start with the business path, not the menu
Map the important path from start to finish. A typical example is Sales creating an order, applying credit or discount rules, and passing the request to Inventory. Inventory reserves and ships the goods. Production data moves to the MES. When manufacturing is complete, stock is updated by lot or serial number, and Accounting creates an invoice with the correct tax and payment terms.
People from Sales, Inventory, manufacturing, Accounting, and integration ownership should review the path together. Each group sees a different failure. Sales may see the order status as confirmed while Inventory sees a split reservation or backorder. Accounting may discover that the tax line does not match the customer document.
Write expected outcomes as testable statements. For example: “When an in-stock order is confirmed, the system reserves the quantity under the existing rule and creates a delivery visible to the responsible user.” Or: “When a lot-based production order is completed, the invoice uses the approved quantity and tax data.” This separates a version-related regression from a process rule the team never agreed on.
Use a test database that is close enough to reality
Odoo’s documentation recommends an upgraded test database before production, requires compatible custom-module source code, and describes duplicating production into a neutralized on-premise test database. Odoo, Upgrade Odoo, On-premise
A test database may disable or redirect services such as scheduled actions, outgoing mail, and payments. Prepare sample data, test accounts, sandbox credentials, and a way to inspect each integration.
Check that the copy contains what the tests need: products with lots and serial numbers, replenishment rules, warehouse routes, bills of materials, role permissions, taxes, multi-country customers, and document templates. If the sample data does not resemble real work, a passing test can create false confidence.
Write regression cases that cross team boundaries
A useful case names the person who starts it, the starting data, the steps, the expected result, and the evidence to retain. Consider cases such as:
- An in-stock sales order must reserve stock, create a delivery, and close through the existing sequence.
- An order with insufficient stock must show the approved backorder or delivery date without overstating inventory.
- A manufacturing order using several lots must send work to the MES, receive the result, and preserve lot or serial traceability.
- A partial shipment, return, and credit note must keep quantities, statuses, and accounting entries aligned.
- An invoice with discounts, taxes, or foreign currency must produce the expected totals, reports, and downstream files.
- Each role must see and edit only the records it should, including when an external tool is connected.
- APIs, EDI, barcode scanners, printers, and automated actions must be tested for both successful responses and unavailable endpoints.
Odoo warns that adding or removing apps can affect other apps and subscription costs, and recommends testing on a duplicate database. Odoo, Apps and modules For a business team, every new feature needs three answers: which step does it improve, who owns it, and how will the team disable or reverse it if the result is not acceptable?
Decide from evidence, then enable new features
Before setting an upgrade date, have the process owners and system owner approve the test evidence together. Review at least these five points:
- Do the critical Sales, Inventory, manufacturing, and Accounting paths have comparable before-and-after results?
- Have custom modules and external integrations been tested against the target version?
- Do reports, documents, taxes, lots, serial numbers, permissions, and automated actions match the business rules?
- Who makes the go or no-go decision, and who coordinates remediation when a case fails?
- What cutover window, communication plan, and return path are possible in this hosting environment?
Passing the simplest screen test is not enough. A sound decision may be to enable some modules first, defer a feature without evidence, or adjust a process for the new version. That makes the benefit and the remaining uncertainty visible.
Odoo 20 may reduce repetitive work and connect more parts of the operation. The benefit appears when a sales order still travels correctly from Sales to Inventory, the MES, and the invoice in your own environment. Before asking “What is new?”, ask “Will the work we promised customers still run after the upgrade?”
References
