Manufacturing in an ERP lives or dies by how well it handles bills of materials. The BOM defines what goes into a product, how much it costs, and whether the materials are actually available. For simple products with flat component lists, most systems handle this fine. But for anything with sub-assemblies — a table that requires a pre-manufactured table top, which itself requires wood panels and wear layers — understanding the full picture has always required clicking through multiple records and doing mental math.
Odoo 19.3 introduces a BOM Overview report that solves this by rendering the entire hierarchy in a single view, with cost calculations and availability forecasting baked in. Alongside it, work orders gain custom properties and the Shop Floor interface gets updated terminology that better reflects what operators actually do on the line.
The BOM Overview Report
The new report is accessible from a smart button on any bill of materials. Click it, and Odoo renders the complete product hierarchy as an expandable tree structure. A table product, for example, might show its table legs as direct components and its table top as a sub-assembly — which unfolds to reveal the wood panels, ply layers, and wear layers that make up that sub-assembly.
Each row displays the product name, required quantity, and total cost. For sub-assemblies, the cost appears in grey text to indicate it’s a rolled-up figure calculated from child components rather than a direct material cost. This visual distinction matters for cost engineers — it tells you immediately whether a line item is something you purchase or something you manufacture, without needing to open the record.
The Forecast toggle adds another layer. When enabled, it switches the view to show Free to Use and On Hand quantities, component status indicators, lead times, and procurement routes. This turns the BOM Overview from a static cost reference into an active planning tool — you can see at a glance whether you have enough material to start production or whether a component shortage will delay the order.
BOM References for When One Product Has Multiple Recipes
Not every product has a single way to be manufactured. A computer might normally use one GPU model, but during supply shortages, a substitute gets swapped in. Both configurations are valid, both need their own BOM, and both reference the same finished product.
The new Reference field on the BOM form addresses this directly. It gives each bill of materials a human-readable label that distinguishes it from alternatives. Instead of identifying BOMs by their internal sequence numbers, manufacturers can label them with meaningful names that reflect the actual configuration difference.
Work Orders Gain Custom Properties
Work orders have always been somewhat rigid in what data they capture. You get the operation, the workcenter, the expected duration, and the components to consume. But manufacturing floors deal with variables that don’t fit neatly into predefined fields — wood types, finish specifications, batch-specific temperature settings, or customer-specific packaging instructions.
The new work order properties feature lets operators and managers add custom fields to individual work orders through the Actions menu. These properties are flexible key-value pairs that attach directly to the work order record. A wood furniture manufacturer might add a “Wood Type” property to track whether a particular order uses oak, maple, or walnut — information that affects both the production process and quality expectations.
This isn’t about replacing structured data with freeform fields. It’s about handling the edge cases that every manufacturing operation generates — the details that don’t justify a custom module but still need to live somewhere accessible.
Processing Work Orders From Their Own Form
Previous versions funneled work order processing through the manufacturing order’s Work Orders tab. You’d open the MO, switch to the tab, and process each work order inline. This worked, but it meant constantly navigating back to the parent record.
Odoo 19.3 adds a direct processing path through the individual work order form. Navigate to Manufacturing → Operations → Work Orders, open a specific work order, and process it there — start the timer, work through quality check instructions, pause if needed, and mark it complete. The status changes, time tracking entries, and component consumption all happen from the same form.
For production managers overseeing multiple work centers, this is a meaningful workflow improvement. Instead of hunting through manufacturing orders to find a specific operation, they can filter the work order list by workcenter, status, or scheduled date and process orders directly.
Shop Floor Gets Clearer Terminology
The Shop Floor interface — the tablet-friendly view that operators use on the production line — has updated its registration language. The button previously labeled Register Production / Serial is now Register Quantity/Lot. The description changed too: instead of “Record lots of serial numbers for the units produced,” it now reads “Record the quantity produced and any lot or serial numbers for the manufactured products.”
This sounds minor, but terminology on a shop floor interface matters more than it does almost anywhere else in an ERP. These are screens used by operators who may not be deeply familiar with ERP conventions. The old phrasing implied serial numbers were always involved; the new phrasing correctly reflects that many manufacturing operations track by quantity and lot without individual serial numbers.
The Manufacturing Module’s Direction
These changes share a common theme: making the manufacturing module better at representing real-world complexity without adding structural weight. The BOM Overview report surfaces information that was always in the system but required manual navigation to assemble. Custom properties handle variability without schema changes. The work order form provides a direct processing path without removing the existing one.
For manufacturers running Odoo, the practical impact is incremental but meaningful: fewer clicks to answer common questions, better data capture at the point of production, and clearer interfaces for the people who spend their days on the shop floor rather than in the back office.