Sale Product Pricelist Operating Unit
This module introduces the following features:
- On the sales order form excludes pricelists that are not associated with the same operating unit as the sales order
auto_awesome What this module does
AI-generated from the code · Odoo 17.0On the sales order form, the pricelist field only offers pricelists that belong to the same operating unit as the order (or pricelists with no operating unit).
This module adds a filter to the pricelist field on the sales order form so users can only pick pricelists that match the operating unit of the order.
- When a user opens a sales order and clicks the pricelist field, the list of available pricelists is limited to those linked to the same operating unit as the order, plus any pricelists that have no operating unit at all.
- Pricelists belonging to a different operating unit are no longer shown as choices, which prevents selecting a price list that does not apply to that part of the business.
- The change is a view-level restriction on the
sale.orderform (the standard sales order screen); it does not create new menus, reports, or automated actions. - It relies on the operating unit concept provided by the
product_pricelist_operating_unitandsale_operating_unitmodules, which must be installed for this filter to work.
No other business rules, computations, or scheduled jobs are added by this module.
Text generated by AI (DeepSeek) from reading the Odoo 17.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 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/operating-unit.
terminal Installation and usage
OCA documentation · Odoo 17.0Usage
Source · Odoo 17.0On the sales order form set pricelist that is associated with the same operating unit as the sales order
No verified information in OCA: Installation, Configuration.
Installation 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.