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)
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Organise outgoing deliveries into release channels so warehouse teams can control when and how many transfers are released, with a kanban dashboard showing workload per channel.
This module lets stock managers group outgoing transfers into named release channels (for example per warehouse, operation type, customer or a custom rule). Each channel has a sequence, an optional filter domain and optional Python code, and a transfer is automatically assigned to the first matching channel when it is created from a sales order, created as a backorder, or released.
A kanban dashboard shows, per channel, how many transfers are To Do, Release Ready, Released, Available, Waiting, Late, Priority and Done Today, plus related chained transfers and estimated move counts. Clicking a counter opens the matching transfers or moves.
Each channel has a lifecycle: Open, Locked and Asleep, with buttons to Lock, Unlock, Stop/Restart collecting and Sleep/Wake Up. A 'Release Next Batch' button releases the next transfers up to a configured maximum, taking already released but not shipped transfers into account. Releasing can be forbidden per channel, and a channel can be excluded from automatic assignment for manual use.
It also adds a Release Channels field on partners, a company setting to show the last done transfer on the dashboard, a scheduled job to re-assign channels, and multi-company access rules. It touches stock.picking, stock.move, res.partner, res.company and res.config.settings.
Depends on
Required by other modules
Menus it adds
Models and fields (6)
- stock.move · extends an existing model
- res.company · extends an existing modelrelease_channel_show_last_picking_done (Channels dashboard - Show last delivery done)
- res.partner · extends an existing modelstock_release_channel_ids (Release Channels)
- stock.picking · extends an existing modeldelivery_date, release_channel_id
- res.config.settings · extends an existing modelrelease_channel_show_last_picking_done
- stock.release.channel · new modelcode (Python Code), name, color, state, active, sequence, batch_mode, company_id (Company), partner_ids (Partners), picking_ids (Transfers), rule_domain (Domain), release_mode, warehouse_id (Warehouse), count_move_all (All Moves (Estimate)), max_batch_mode (Max Transfers to release), count_move_done (Moves Done Today (Estimate)), count_move_late (Late Moves (Estimate)), state_at_wakeup, collect_pickings, open_picking_ids (Open Transfers), picking_type_ids (Operation Types), count_picking_all (All Transfers), picking_chain_ids, release_forbidden (Forbid to release this channel), count_move_waiting (Waiting Moves (Estimate)), count_picking_done (Transfers Done Today), count_picking_late (Late Transfers), is_release_allowed, count_move_assigned (Available Moves (Estimate)), count_move_priority (Priority Moves (Estimate))
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/stock-logistics-release-channel.
terminal Installation and usage
OCA documentation · Odoo 18.0Configuration
Source · Odoo 18.0In Inventory \> Configuration \> Release Channels. Only Stock Managers have write permissions.
Usage
Source · Odoo 18.0Use 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 \ (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.
No verified information in OCA: Installation.
Installation 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.