UOM - Q on UOM classes?

Summary:

We are currently working on cloud implementation - purchasing, inventory and finance. We have both inventory-stocked items and expense items with majority being expense items. We have defined SKUs for all items.

At this time, we plan to create one UOM class and include all UOMs in that particular single class. Some of the UOMs we plan to use are EA, BX, CA, TON, LBS, GAL, KM, MI etc. In short, UOMs which are typically spread across Quantity, Weight, Length, Volume etc. but we are thinking to create one huge class.

Advantages we see of this approach:

1. Almost all our expense items are procured across different traditional UOM classes. But, consolidating them into single class along with 1:1 standard conversion, reduces the work required to maintain item specific intra and inter class conversions.