Stock Picking Inter Warehouse
This module allows to set up an operation type dedicated to internal transfers between different warehouses in the same company, managing both delivery and receipt from each side of the transfer.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Configure warehouses to exchange stock through a dedicated inter-warehouse transfer operation, with automatic receipt pickings created at the destination warehouse.
This module lets you set up internal transfers between two warehouses of the same company as a proper two-step flow: a delivery from the source warehouse and a receipt at the destination warehouse.
On each warehouse (Warehouse form) you can enable 'Inter-Warehouse Transfers' and then choose the destination location, the incoming operation type and the partner used on the receiving picking. When enabled, the system automatically creates a dedicated route and a push rule so that, once the delivery is validated, a receipt picking is generated at the other warehouse.
On operation types you can flag an internal operation as 'Use for Inter-warehouse transfer' and optionally 'Disable Merge Picking Moves' to force one receipt per delivery. On transfer pickings, the partner field becomes required and is limited to the partners configured on the other warehouses.
Business rules: two warehouses cannot share the same receiving partner (validation error); the destination location of an inter-warehouse transfer is automatically set from the partner's default source location; a default source location can be stored on contacts. The module touches stock.picking, stock.move, stock.rule, stock.warehouse, stock.picking.type, stock.location, res.company and res.partner.
Depends on
Required by other modules
Models and fields (8)
- stock.move · extends an existing modelinter_warehouse_picking_id
- stock.rule · extends an existing modelinter_warehouse_src_id
- res.company · extends an existing modelinter_warehouse_route_id
- res.partner · extends an existing modeldefault_stock_location_src_id
- stock.picking · extends an existing modeltype_inter_warehouse_transfer, inter_warehouse_contact_domain_ids
- stock.location · extends an existing modelinter_warehouse_partner_id
- stock.warehouse · extends an existing modelreceipt_picking_type_id (Receipt Operation Type), inter_warehouse_transfers (Inter-Warehouse Transfers), receipt_picking_partner_id (Partner in Picking), receipt_destination_location_id (Receipt Destination Location)
- stock.picking.type · extends an existing modelinter_warehouse_transfer (Inter-Warehouse Transfer), disable_merge_picking_moves (Disable Merge Picking Moves), warehouse_inter_warehouse_transfers
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/stock-logistics-workflow.
terminal Installation and usage
OCA documentation · Odoo 14.0Configuration
Source · Odoo 14.0- Enable multi-step routes and location
- In warehouse, enable flag “Inter-warehouse transfers” and set:
- receipt destination location (eg: “WH2/Stock”)
- receipt operation type (eg: “WH2: Receipts”)
- partner in picking (eg: “My Company (San Francisco), WH2”)
- Note: this must be done for all warehouses sending or receiving internal transfers.
- Create or open an existing “internal” operation type; enable field “Use for Inter-warehouse transfer”.
- Boolean "Disable Merge Picking Moves" is also available if you wish to maintain a 1 to 1 relation between outgoing pickings and incoming ones.
Usage
Source · Odoo 14.0Create a transfer for “inter-warehouse” operation type:
- when selecting contact related to receiving warehouse, destination location is automatically selected
- on picking validation, a “receipt” picking is created in the destination warehouse.
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.