Item volume (LxWxH) as a first class attribute

[labeneator]

Is your feature request related to a problem? Please describe. I think making an item volume as a first class citizen is important. Reasons are:

1. The total valuation of an item shipped via container/air is mostly dependent on the item volume. LCV can use this value as an additional optional field to distribute shipping costs
2. Shipping to customers via fedex/DHL/... is based on the max(mass, volumetric_weight), being able to store these values might help with computation of shipping sold items.
3. Estimating Storage use in warehouse.

In my case, I need item volume and mass to be stored per item. LCV can use item volume to allocate shipping cost while sales invoice may use item mass.

Quite a few people have bandied the issue on #4736, #3740, #3321,

Describe the solution you'd like I think we can add item volume directly to item. Currently we have in item.json

  "weight_per_unit",
  "weight_uom",

Might i suggest that we add

  "volume_per_unit",
  "volume_uom",

We would also need to handle storage of the actual dimensions of the item - Length, Width, Height since some packaging software might use such fields for optimal packing (and might be relevant for customer shipping). I don't know the best way do this :/

Describe alternatives you've considered I have researched the issue in the forums and github issues. It seems to be a thorny issue that if solved, would gainfully increase the utilty of the item class.

Additional context An additional work unit would follow this if approved. This would be the addition of

1. LCV calculation by volumetric weight
2. Have the applicable charges on an LCV have the option of being distributed differently. EX: Freight can be distributed by volume while taxes can be distributed by value.

[bastelfeak]

I think it is mandatory field and I'm wondering why this item attributes not exist?