Delivery Package Default Shipping Weight
This module allows to define a Default shipping weight on Delivery packages (product.packaging) in order to set automatically the Shipping weight on the packages (stock.quant.package) using this Package type.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you set a default shipping weight on each Package Type, so that weight is filled in automatically on packages that use it.
This module adds a new field, "Default shipping weight", to Package Types (the packaging records used for delivery). You can enter it on the Package Type form and see it in the Package Type list, right after the maximum weight field.
When you create or edit a Package and choose a Package Type that has a default shipping weight, Odoo automatically fills the package's Shipping weight with that value. This happens both when you pick the Package Type on screen and when packages are created or updated by other processes, as long as no shipping weight was already provided.
A check prevents saving a negative default shipping weight: the value must be zero or positive, using the company's weight unit and rounding.
The module touches the Package Type model (product.packaging) and the Package model (stock.quant.package). It does not add new menus; the new field appears inside the existing delivery-related Package Type views.
Depends on
Models and fields (2)
- product.packaging · extends an existing modelpackage_default_shipping_weight (Default shipping weight)
- stock.quant.package · extends an existing model
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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/stock-logistics-workflow.
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.