Stock Location Position
This module adds position attributes on stock location such as:
- Corridor
- Row
- Rack
- Level
and renames position (XYZ) to box (XYZ).
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Adds storage position details (corridor, row, rack, level and box coordinates) to stock locations, so you can describe exactly where an item is stored and search locations by these details.
This module extends the stock location screen in Odoo with a new "Position" section. On any location record you can now fill in four text fields — corridor, row, rack and level — to describe the physical storage spot (for example, which aisle, which side of the aisle, which rack and which shelf).
It also renames the existing X, Y and Z position fields to "Box (X)", "Box (Y)" and "Box (Z)". These are optional whole numbers used when a location is divided into smaller compartments, such as drawers or storage trays.
Where it appears: - The stock location form gets a new "Position" group with all seven fields. - The stock location search view gains the same fields, so you can filter or group locations by corridor, row, rack, level or box coordinates.
The module only adds fields and screen elements; it does not add automatic checks, computations, emails or scheduled actions. It touches the stock.location model and the standard location form and search views.
Depends on
Required by other modules
Models and fields (1)
- stock.location · extends an existing modelrow, posx (Box (X)), posy (Box (Y)), posz (Box (Z)), rack, level, corridor
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: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.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.