Default BoM Order is weird : sequence and id. This module changes it and change order in BoM tree view with :Product template name, then product variant name, then their code. It hides sequence as it is not used anymore.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Changes the default sorting of Bills of Materials (BoM) in Manufacturing so they are listed by product name, then variant, then reference, and hides the sequence column.
This module only affects how the list of Bills of Materials is displayed in Odoo Manufacturing. Instead of the previous ordering based on an internal sequence number and record ID, the BoM list is now sorted by the product template name, then the product variant, and finally the BoM reference code.
Where it appears:
- In the Manufacturing area, on the Bills of Materials list screen (mrp.bom), the default sort order changes automatically when you open the list.
- The "Sequence" column is hidden from that list, because it is no longer used for ordering and could be confusing.
Business rules and behaviours:
- The underlying default order of the mrp.bom model is set to the reference code, so records are consistently ordered by code when no other sort is chosen.
- The list view applies the order product template, product variant, then code, making it easier to find all BoMs for a given product grouped together.
- No new fields, menus, buttons, reports, emails or scheduled actions are added.
Areas touched: - Manufacturing / Bills of Materials list view only. No other Odoo screens or documents are modified.
Depends on
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.