...
When using Charges to track a Service Feature, the feature will be directly visible on a Bill under the Service. This makes it clear to those reviewing the Bill what is related to their Service. However, when looking at the Service, it may not be intuitive for managing the Service's related features to look at the Charges Grid on the Service to see what features are currently on the Service. This also can make reviewing what features are available for a Service rather difficult because a User would need to know what Charge Catalogs are allowed to be on their Service. For Billable Service Features, which are available for all Services, when there is not a notably long list of Service Features that will be offered within your Organization, this can be a simple solution for tracking purposes. When not Billing for a Service Feature, using Charges to track the use of Service Features might look strange, since these would have to be represented by Charges of $0.00 on the Service for every Billing Cycle.
Using UDFs
When using UDFs to track a Service Feature, the feature can be directly requested within CustomerCenter, and makes identifying the presence of the feature quickly accessible from internal application records. However, this will not cause the feature to appear on the Bill, which may make the User of the Service confused when they review their Bill. When not Billing for use of a Service Feature, using UDFs is the recommended method for tracking Service Features. The use of UDFs makes it very clear internally what is available, and what is presently active for the Service via the UDF Tab.
Using a combination of UDFs and Charges
...