Stock Location Fill State Qty Picked
Glue module between move line qty picked and location fill state.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0This module automatically connects the quantity picked on stock move lines with the fill state of stock locations, so location fill state stays accurate when the picked quantity is used instead of the done quantity.
This is a technical glue module that installs itself automatically when both the location fill state and the move line quantity picked features are present. It does not add any new menu, screen, button or report.
What it changes is how Odoo decides the fill state of a stock location. The location fill state is normally based on the quantity done on outgoing move lines. With this module, the calculation is based on the quantity picked instead.
- It extends the
stock.locationmodel and overrides the fill state computation. - It declares a dependency on the
qty_pickedfield of pending outgoing move lines, so the fill state is recalculated whenever the picked quantity changes. - It exposes an internal property that tells the fill state logic which move line field holds the picked quantity.
As a result, when warehouse staff record a picked quantity on move lines, the fill state of the related locations is refreshed using that picked quantity. No new fields, menus or user actions are added; the module only keeps the two existing features consistent with each other.
Models and fields (1)
- stock.location · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 18.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 18.0
Confirmed on 2026-11-03 in branch 18.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.