Three areas of the platform picked up meaningful changes this week: the warehouse routing engine now handles a decision that used to require manual intervention, the website builder rethinks how content blocks nest and resize, and HR teams get a cleaner path for something they do more often than most vendors assume — archiving former employees.
Inventory Routes Now Apply Themselves
Warehouse managers have long had to manually assign Buy and Manufacture routes to products — a pair of checkboxes that were easy to forget and tedious to audit at scale. That step is gone. Odoo now applies both routes automatically based on how a product is configured: if it has a vendor, the Buy route kicks in; if it has a bill of materials, the Manufacturing route activates. No checkbox required.
The bigger structural change sits underneath. Routes now follow a five-level priority system that determines which rule wins when multiple routes could apply to the same stock move. A route set directly on a product overrides everything. Below that, package type routes take precedence over operation type routes, which in turn override warehouse defaults, which override global fallback rules. The hierarchy is fixed and predictable — no more guessing which route the system picked or why a transfer followed an unexpected path.
As part of the same cleanup, the Dropship Subcontractor on Order route has been retired as a standalone option. The behavior still exists, but it’s now handled through the standard subcontracting workflow rather than a separate route that overlapped with existing functionality. Package type assignments also replace the old packaging-level route configuration, pushing shipping decisions up to where they belong — on the type of package, not the individual package record.
Website Building Blocks Get Nesting and Resize Handles
The Website Builder’s building blocks — the drag-and-drop content components that form the backbone of every Odoo website page — have been restructured around a concept that was conspicuously missing: nesting. Blocks can now contain inner content blocks, creating parent-child relationships that let designers build complex layouts without resorting to custom HTML. A hero section can hold a text block and a form block side by side, each independently editable, each aware of its container.
Form blocks in particular benefit from expanded action types. Beyond the standard contact form submission, blocks can now trigger newsletter subscriptions and project task creation directly from the form. Field labels are configurable, required-field marking is toggleable per input, and placeholder text can be set without touching code.
The most tactile improvement is the simplest: every block edge now sports a drag-to-resize handle. Where designers previously had to switch to a settings panel to adjust block dimensions, they can now grab an edge and pull. It sounds small. Anyone who has spent an afternoon nudging pixel values in a sidebar will disagree.
Employee Archiving Breaks Free From Offboarding
When an employee leaves a company, two things happen in the system: their offboarding process runs (exit interviews, equipment returns, access revocation), and eventually their record gets archived. These are related but distinct operations, and until now Odoo treated archiving as a subsection buried inside the offboarding instructions. That created a problem: anyone who just needed to archive a record — a contractor whose engagement ended, a seasonal worker returning next quarter, a duplicate entry from a data import — had to wade through offboarding steps that didn’t apply.
Archiving now has its own standalone guide. The separation reflects a practical reality: archiving is getting incremental updates as Odoo adds more controls around what happens to an archived employee’s data, their linked records, and their access permissions. Keeping those updates nested inside offboarding would have made both documents harder to maintain and harder to find.
POS Hardware Gets a Clearer Security Path
Separately, the Point of Sale team has tightened up how IoT devices connect to the POS terminal. The security certificate bridge — the layer that establishes trust between a physical device like a receipt printer or payment terminal and the Odoo POS application — now has clearer setup instructions and more explicit documentation around what happens when certificates expire or when devices move between networks.
This matters most for multi-location retailers running dozens of IoT boxes. A misconfigured certificate can silently break a terminal’s connection to its peripheral hardware, and the failure mode — the printer just stops printing, with no on-screen error — is exactly the kind of issue that eats hours of support time. The updated guidance makes the trust chain visible and debuggable.
The Pattern
None of these changes are headline features. They’re the kind of work that happens when a platform matures past feature checklists and starts paying down the small debts that accumulate in every module. Automatic route assignment removes a manual step that caused errors. Nested blocks remove a design limitation that forced workarounds. Standalone archiving removes a navigation detour that wasted time. The individual impact of each is modest. Taken together, they signal a team that’s listening to the friction reports, not just the feature requests.