# 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

- Configuration
- Usage
- Bug Tracker
- Credits
  - Authors
  - Contributors
  - Other credits
  - Maintainers

# Configuration

1. To enable picking grouping:

> 1. Go to Inventory > Configuration > Warehouses
> 2. Select ‘Technical Information’ tab
> 3. Check the ‘Group pickings’ box

1. To disable picking grouping for some partners:

> 1. Go to the partner form you want
> 2. Go to ‘Sales & Purchase’ tab
> 3. Check the ‘Do not group deliveries’ box

# 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

## Authors

- Camptocamp
- BCIM

## 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>
- Denis Roussel <denis.roussel@acsone.eu>

## 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.