If you’ve set up inventory routing in Odoo before, you know the drill: open a product form, scroll to the Inventory tab, and check the appropriate route boxes — Buy, Manufacture, Make to Order, or some combination. It’s one of those configuration steps that trips up new users and occasionally catches experienced ones too, especially when a product needs both a purchase route and an MTO trigger.
Odoo 19 changes this entirely. The Buy and Manufacture routes no longer appear as checkboxes on product forms. They’re still there — the routing logic hasn’t changed — but the system now applies them automatically based on how the product is configured. If a product has a vendor set, Odoo knows it can be purchased. If it has a bill of materials, Odoo knows it can be manufactured. No manual route selection required.
Why the Checkboxes Were a Problem
The old route checkboxes were a classic case of configuration that duplicated information the system already had. A product with a vendor pricelist and no BOM was never going to be manufactured. A product with a BOM and no suppliers was never going to be purchased through the Buy route. Yet the system required users to explicitly tell it what was already obvious from the product’s own data.
This created a common failure mode: a product would be fully configured with vendors, lead times, and minimum order quantities, but replenishment would silently fail because someone forgot to check the Buy route box. The error wasn’t loud — nothing broke visibly. Reorder rules just didn’t trigger, purchase orders didn’t generate, and the warehouse team would eventually notice that stock wasn’t arriving.
Worse, because the route configuration lived on a tab that many users rarely visited, debugging the issue meant knowing to look in a non-obvious place. New Odoo users often spent hours in forums or support tickets before someone told them to check the Inventory tab for route settings.
How Automatic Routing Works Now
In Odoo 19, the system infers the appropriate supply route from the product’s configuration. The logic is straightforward:
A product with at least one vendor in its purchase configuration gets the Buy route applied automatically. A product with a bill of materials gets the Manufacture route. Products with both get both routes, and Odoo’s replenishment engine uses the same priority rules it always has to decide which route to take when stock needs refilling.
The Made-to-Order route remains as an explicit setting because it represents a genuinely different business decision. MTO means “don’t keep this in stock; only procure it when there’s confirmed demand.” That’s not something the system can infer from product data — it’s a strategic choice about how to manage inventory for that specific item.
The Documentation Gets a Full Rewrite
Alongside the routing changes, Odoo’s Made-to-Order documentation has been rewritten for version 19. The update goes beyond screenshot refreshes. New sections explain how MTO interacts with the automatic route system, clarify the workflow from sales order confirmation through to procurement, and walk through scenarios where MTO is combined with multi-step warehouse operations.
The documentation also addresses a point that confused users in earlier versions: the relationship between MTO and reorder rules. In versions prior to 19, some users set up both MTO routes and minimum stock rules on the same product, creating conflicting replenishment signals. The new docs explain when each approach is appropriate and why combining them usually means your inventory strategy needs rethinking rather than more rules.
What This Means for Existing Setups
For companies upgrading from Odoo 18 or earlier, the transition should be seamless. Products that already had Buy or Manufacture routes checked will continue working exactly as before — the routes are still applied, just through an automatic mechanism rather than a manual one. No data migration or reconfiguration is needed.
The real benefit shows up for new product creation. Implementation consultants who’ve spent years training users to “remember to check the Buy route” can drop that step from their onboarding scripts. One less gotcha, one less support ticket waiting to happen.
It’s a small change in terms of code — hiding two checkboxes and adding inference logic. But it eliminates one of those quiet configuration mistakes that could stall an entire supply chain without anyone immediately understanding why. The best features in an ERP aren’t always the ones that add capability. Sometimes they’re the ones that remove the opportunity to get something wrong.