Stock Release Channels

Release channels are:

• Release channels are created by stock managers (only pallets, only parcels, ...)
• A release channel has a sequence, a domain + possibility to use python code
• When a delivery is: created from a sales order / created as backorder / released, each release channel is evaluated against it (domain + python code), the delivery is assigned to the first channel that matches
• A release channel can change over time: for instance the evaluation of a domain or rule can change if a delivery is only partially released
• A kanban board allows tracking how many [To Do Today, Released, Done Today, Waiting, Late, Priority] Transfers are in each channel, plus quick access to all the pick/pack transfers for released deliveries
• A button on each channel allows to release the next X (configured on the channel) transfers (max X at a time, it releases X - currently released and not done)

Table of contents

Configuration

In Inventory > Configuration > Release Channels. Only Stock Managers have write permissions.

Usage

Use Inventory > Operations > Release Channels to access to the dashboard.

Each channel has a dashboard with statistics about the number of transfers to release and of the progress of the released transfers.

When clicking on the "box" button, transfers are released automatically, to reach a total of <Max Transfers to release> (option configured in the channel settings).

The availability of a release channel depends on its state. A release channel can be in one of the following states:

> - Open: the channel is available and can be used to release > transfers. New transfer are assigned automatically to this > channel. > - Locked: the channel is available but the release of transfers from > the channel is no more possible. New transfers are still > automatically assigned to this > - Asleep: the channel is not available and cannot be used to release > transfers. It is also no more possible to assign transfers to this > channel.

New release channels are by default "Open". You can change its state by using the "Lock" and "Sleep" buttons. When the "Sleep" button is used, in addition to the state change, not completed transfers assigned to the channel are unassigned from the channel. When the "Lock" button is used, only the state change is changed. A locked channel can be unlocked by using the "Unlock" button. A asleep channel can be waken up by using the "Wake up" button. When the "Wake up" button is used, in addition to the state change, the system looks for pending transfers requiring a release and try to assign them to a channel in the "Open" or "Locked" state.

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
• ACSONE SA/NV

Contributors

• Guewen Baconnier <>
• Matthieu Méquignon <>
• Sébastien Alix <>
• Jacques-Etienne Baudoux <>
• Laurent Mignon <>
• Michael Tietz (MT Software) <>

Design

• Joël Grand-Guillaume <>
• Jacques-Etienne Baudoux <>

Other credits

Financial support

• Cosanum
• Camptocamp R&D

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.

Current maintainers:

This module is part of the OCA/wms project on GitHub.

You are welcome to contribute. To learn how please visit .