Is the idea of warehouse locations to nest them down to bin level ? Why do products also have location fields (rack row case) ? Are 'rack' 'row' 'case' used as data by openerp or are they just static text values ?

We have setup our warehouse and sub locations in a nested format that represents warehouse/zone/rack/bay/shelf/bin in the format C1-A11-F5 (warehouse C1, zone A, rack 1, bay 1, shelf F and bin 5..... The top level is 'Physical Locations / ourcompany / Stock /' as per default and is an 'internal location' We have then nested all the other locations as views until the last sub location. The last sub location (the picking bin) is set as 'internal location'. This is how our bin locations look as a full path: Physical Locations / ourcompany / Stock / C1 / Zone A / Rack 1 / Bay 1 / Shelf A / C1-A11-A1

This seems very long and messy but we noticed only the bin location is printed on the packing note and not the full path. If we nested the above bin as just the value '1' then the pick/ dispatch note would only show the picking location as '1' (meaningless) It might have been better to shorten each sub location and have the full location path on the delivery note (bin location for picking purposes)

We then noticed the 'rack' 'row' 'case' fields in the product view and decided to ask the above questions !