Stock Picking: group by partner and carrier
This module can be used if your customers expect that several different orders they passed will be shipped in a single delivery order.
With this module installed, when a sale order is confirmed, the stock moves for the lines of the sale order can be placed in an existing delivery order that shares the same delivery address and carrier (or lack thereof).
Sale orders with a Shipping Policy set to ‘When all products are ready’ always get their own shipping.
When the delivery slip is printed, the list of pending quantities to deliver is shown at the end, grouped by order.
The grouping can also be applied in case of external resupply. Moves at the destination of the same delivery address defined on the resupply stock rule will be grouped in a same delivery order.
Note: The grouping is currently not propagated to the pulled internal moves if you don’t use the module stock_available_to_promise_release in the wms repository.
Table of contents
Usage
To use this module you need to enable grouping on the picking types for which you want grouping.
If you want to enable this for the shippings of a warehouse:
be sure that in the settings of the Inventory app, you checked “Manage Push and Pull inventory flows”
enable “debug mode”
go to the warehouse for which you want grouping and check the setting “Group Shippings”
You can also enable this for individual picking types by checking the setting “Group Pickings” on the picking type view.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Camptocamp: * Alexandre Fayolle <alexandre.fayolle@camptocamp.com> * Thierry Ducrest <thierry.ducrest@camptocamp.com>
BCIM: * Jacques-Etienne Baudoux <je@bcim.be>
Phuc Tran Thanh <phuc@trobz.com>
Other credits
The development of this module has been financially supported by:
Camptocamp
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/stock-logistics-workflow project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-stock-picking-group-by-partner-by-carrier 14.0.1.4.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo14_addon_stock_picking_group_by_partner_by_carrier-14.0.1.4.4-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_stock_picking_group_by_partner_by_carrier-14.0.1.4.4-py3-none-any.whl |
Release files / odoo14_addon_stock_picking_group_by_partner_by_carrier-14.0.1.4.4-py3-none-any.whl
| Download URL | odoo14_addon_stock_picking_group_by_partner_by_carrier-14.0.1.4.4-py3-none-any.whl |
|---|---|
| Size | 62.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e26bdcbef25f5657ea10b1b06b87ad3d21c0d4d16bd260e0269ee3cc52dffe53
|
|
BLAKE2b-256 checksum How to use checksums |
3b6711629462076f4faa8844d79b8c6f4dc9bc3765ab6d02b062db14bfc8e225
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo14-addon-stock-picking-group-by-partner-by-carrier 14.0.1.4.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
