Shopfloor Single Product Transfer Force Select Package
Force the user to select a package if they scan a location which already contains packages.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0In the Shopfloor single product transfer screen, when a user scans a destination location that is configured to require packages, the system now blocks the transfer until a package is selected.
This module adds a control to the Shopfloor single product transfer workflow. When a user scans a destination location during a transfer, the system checks whether that location is flagged as requiring packages.
- If the location requires packages and neither a package has been selected nor the move line already has a result package, the transfer is stopped.
- The user sees a message telling them that the location requires a package, and the screen asks them to select one before continuing.
- If a package is already selected or the move line already has a result package, the normal transfer flow continues as before.
The check is applied through the shopfloor.single.product.transfer component, which is part of the Shopfloor barcode interface. The module depends on shopfloor, shopfloor_single_product_transfer and stock_location_package_restriction, so the package restriction setting on the location comes from the latter module.
No new menus, models, reports or scheduled jobs are added by this module. It only changes the behaviour of the existing single product transfer screen by adding a validation step before the quantity can be set.
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.