When building products, we sell in a single Unit of Measure using different package quantities. An example would be selling cans of soda; you can buy 1 soda can, a 6-pack of soda cans, a 12-pack of soda cans, etc, all with separate price points. Our unit of measure would be soda cans, but we'd want to track the unit/package quantity in a separate field for each of our charges. Today this requires a custom field that carries the package quantity with redundant information in the Unit of Measure text field, for example: Rate Plan Name - Charge Model - UOM - Custom Field Value Acme Soda Can - Per Unit - Cans (1) - 1 Acme Soda 6 Pack - Per Unit - Cans (6) - 6 Acme Soda 12 Pack - Per Unit - Cans (12) - 12 Instead of 3 units of measure ("Cans (1)", "Cans (6)", "Cans (12)") this could be 1 Unit of Measure ("Cans") with a numeric field that specifies the package quantity. The benefit is simplified Product Catalog management and fewer Units of Measure.
... View more