I have a business where I sell both wholesale and retail and therefore I sell products at multiple pricing levels (retail, wholesale, designer pricing levels, etc) and I also have multiple product categories or departments (Home, Jewelry, Personal accessories, etc.). Certain "wholesale clients" may receive discounts on specific mdse categories, which they routinely buy from us, but not other categories for which they would need to pay retail, if they say walked into the store to buy a personal gift.
Therefore, I wanted to set up pricing rules where clients would be able to receive the appropriate discounts on specific categories of mdse that we relevant to them. LSR provides for this function. I set a pricing rule for an entire category of products (say "jewelry") and apply the rule to a certain customer category (say "wholesale jewelry" customers). That part makes perfect sense.
However, in the context of setting up the pricing rules, I was shocked to find out that when I apply a certain pricing rule to an entire category of mdse. (again, say "jewelry") so that all my wholesale jewelry customers will receive the appropriate discount, if tomorrow I then add some new jewelry items to stock, THE PRICING RULE WILL NOT APPLY TO THOSE ITEMS UNLESS I GO BACK AND MANUALLY ADD THOSE NEW ITEMS UNDER THE RULE! I thought that the whole point of categorizing merchandise is to be able to sort it and perform operations on whole sets of data. If you add a new item to that set tomorrow or the next day, the system should automatically apply any operations to that new data set. That's kind of the point of a database!! You shouldn't have to remember to go and manually add "new items" to a pricing rule that is supposed to apply to an entire category or class of products. If you have multiple people setting up products or doing data entry, each of them will have to know all the different pricing rules and how they are applied and remember that every time there's a new product. This seems like a very archaic and creating an opportunity for human error to occur every time a new product is created in the system.
Isn't there some way to fix this issue so that pricing rules that are applied "by category" continue to apply to that entire category not just for today, but into the future as new products are created?