Stock Location Bin Name
This module allows to compute automatically Bin location names based on locations attributes.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically builds bin location names in Odoo from a format you define on the parent area, using attributes like corridor, row, rack and level.
This module adds a new field called location name format on stock locations. You type a pattern there, for example '{area}-{corridor:0>2}.{rack:0>3}.{level:0>2}', and Odoo uses it to generate the actual name of bin locations.
The field is shown on the standard location form, right after the usage field, but it is hidden when the location is a bin. This means you normally set the format on the parent area location, not on each individual bin.
When you change the corridor, row, rack, level or the x/y/z position of a bin location, Odoo looks up the nearest parent location that has a format defined and rebuilds the bin name from it. The area name is inserted automatically where the pattern says {area}.
If a field used in the pattern is missing, a '~' is written instead, and if the formatting itself is wrong, a '!' appears. This makes it easy to spot incomplete or incorrect bin names.
The module works together with the zone and position location modules it depends on, and it only affects the stock.location model and its form view. It does not create new menus or reports.
Required by other modules
Models and fields (1)
- stock.location · extends an existing modellocation_name_format
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: 3 confirmed, 6 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.