Stock Warehouse Flow Product Packaging
Integrate the Stock Warehouse Flow module with Product Packaging Type, so the applied flows are limited to ones which has the a same packaging type referenced as the move product has configured
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets warehouse managers restrict stock routing flows to specific product packaging types and split stock moves by product packaging.
This module extends the warehouse flow configuration so that a routing flow can be linked to one or more product packaging types.
- On the flow form (Warehouse Flow), a new "Packaging types" field appears. It is only visible and required when the flow's split method is set to "By Product Packaging".
- A new split method option, "By Product Packaging", is added to the flow's split method selection.
- When a stock move is processed, the system only applies flows whose packaging types match the packaging types configured on the product being moved. Flows with no packaging types set are also considered.
- If the split method is "By Product Packaging", the move is split according to the product's packaging quantities, but only for packagings whose packaging type is allowed by the flow.
- The module adds a uniqueness constraint check on packaging types to avoid duplicate flow configurations.
It touches the stock.warehouse.flow model and its form view, and works together with the stock warehouse flow and product packaging type modules.
Models and fields (1)
- stock.warehouse.flow · extends an existing modelsplit_method, packaging_type_ids (Packaging types)
Text generated by AI (DeepSeek) from reading the Odoo 14.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 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/wms.
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.