Shopfloor reception package dimension mobile
A glue module between shopfloor_reception and stock_quant_package_dimension.
It adds on the set_destination screen of the scenario.
- The height of the package and allows to change the value if needed, the new value is saved on the destination scan.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds a package height field to the mobile reception set-destination screen, shown only when the package type requires a height, and saves the entered value on the destination scan.
This module is a small add-on for the mobile shopfloor reception flow. It changes the mobile reception scenario so that, on the set-destination step, a "Package Height" input appears when the package type of the destination package is marked as requiring a height.
- The field is a number input, with the unit of measure taken from the destination package, so users can see and change the height directly on the mobile screen.
- The height is only shown when the package type requires it; otherwise the screen stays as before.
- When the user confirms the destination, the height value entered is included in the data sent with the destination scan, so the new value is saved on the destination package.
The module does not add any new menus, reports, or server-side models. It works by extending the existing mobile reception scenario and its templates, and it depends on the package dimension and mobile reception modules. No scheduled jobs, emails, or automatic checks beyond the "height required" condition are added by this code.
Text generated by AI (DeepSeek) from reading the Odoo 18.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 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/stock-logistics-shopfloor.
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.