Hi, I have implemented in the food industry when the feature just came out and am a proponent of Catch Weight in the right circumstances, but it requires complex configuration (and decisions) and will affect several processes down the line so the effort has to be worth it. It will affect how formulas are constructed, how inventory adjustments are made, movements are made in the warehouse, raw material pick etc. More transactions will be required to capture the unique weight of a bag or pallet of bags (Catch Weight Tag) and to move that unique pack weight around, adjust it, consume it or sell it.
I would advise implementing catch weight if and only if the items are sold in an indivisive "Quantity" unit class (Pack, Bag, Head, Container) but invoiced in a "Mass" unit class. I often use the example of a rancher that has an inventory of 500 heads of cow, each with their unique weight. That rancher will sell 100 heads but will invoice the customer for the weight of each of these individual cows. The meat processor will build his formulas to consume whole heads, not lb or Kg.
I usually offer the customer a comparison between a <simple weight> option and a <catch weight> option with a demonstration of each. If they are not already using some form of catch weight, might be that the best option is to stay with simple weight.