Replace sequence by priority in order to prioritize easily BoMs. Priority is used to bring up the most important BoMs, the others being classified as by default. This priority will be used to select the right BoM during manufacturing (thus replacing the sequence).
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a priority field (Low, Normal, High, Very High) to Bills of Materials so you can rank them and have Odoo pick the most important BoM first during manufacturing.
This module adds a priority selector to Bills of Materials (BoMs) in the Manufacturing app. On the BoM form you now see a priority widget next to the reference code, with four levels: Low, Normal, High and Very High. New BoMs default to Low.
In the BoM list view, the old sequence column is hidden and replaced by the priority column, and the list is sorted so that higher priorities appear first, then by product and code. This makes it easy to see at a glance which BoM is the most important.
Behind the scenes, when Odoo looks for the right BoM to use for a manufacturing order, it now searches with priority as the first sorting criterion (highest first), then sequence, product and record id. So the priority you set directly influences which BoM is selected during manufacturing, replacing the previous sequence-based ordering.
The module only touches the mrp.bom model and its existing form and list views. It does not add new menus or reports.
Depends on
Models and fields (1)
- mrp.bom · extends an existing modelpriority
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/manufacture.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.