Web Widget One2Many Product Picker Sale Secondary Unit
Adds support for 'sale_order_secondary_unit' in the product picker
auto_awesome What this module does
AI-generated from the code · Odoo 13.0Lets the product picker widget on sales orders handle secondary units of measure, so users can pick a secondary UoM and quantity directly from the product cards.
This module extends the product picker widget used on sales orders so it works together with secondary units of measure.
When a product has secondary units configured, the picker card shows extra fields: a secondary unit of measure and a secondary quantity. These fields are only visible when the selected product actually has secondary units available, thanks to a computed flag on the sales order line.
- The picker card displays a badge showing the quantity and unit of measure, for example the main quantity multiplied by the unit name.
- The secondary unit and quantity are taken into account when comparing or refreshing the picker state, so the card stays consistent.
- The product search used by the picker also retrieves the default secondary unit configured on the product.
The module touches the sale.order.line model by adding a computed, non-stored boolean field that indicates whether the product has secondary units. It also injects the secondary unit and secondary quantity fields into the sales order line form used inside the picker widget.
No new menus or reports are added; the change appears inside the existing one2many product picker widget on sales orders.
Models and fields (1)
- sale.order.line · extends an existing modelhas_secondary_uom (Has Secondary UoM)
Text generated by AI (DeepSeek) from reading the Odoo 13.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 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/web.
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.