Stock Picking Show Linked
This module should allow a user to display, on smart buttons in a picking:
- Previous pickings: the pickings associated to origin moves indicated in the moves in this picking
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds a smart button on transfer (picking) forms that opens the previous transfers linked through the moves' origin moves, making chained routes easy to follow.
This module makes it easier to navigate chained warehouse routes. On a transfer form (stock.picking), a new smart button labelled "Previous Transfer" appears next to the existing transfer buttons.
- The button is only shown when there is at least one previous transfer, based on a computed counter (
origin_picking_count). - The counter is calculated automatically from the origin moves of the moves in the current transfer, so it reflects the real chain of documents.
- Clicking the button opens the related previous transfer(s): if there is exactly one, Odoo opens its form directly; if there are several, it opens the list of transfers filtered to those documents.
It touches the stock.picking model and the standard transfer form view. No new menus, reports, emails or scheduled jobs are added. The feature is purely a navigation aid for users who need to trace back the steps of a multi-step route (for example, from a delivery back to the internal transfers or receipts that fed it).
Depends on
Models and fields (1)
- stock.picking · extends an existing modelorigin_picking_count
Text generated by AI (DeepSeek) from reading the Odoo 19.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: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/stock-logistics-warehouse.
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.