Add 'One or more' to 'number of leagues' discount
marked this post as
So you want to discount a "Product" if they've purchased a league?
The issue here is that leagues are seasonal whereas products are not. Do you have a concrete example I can refer to? I'm already
maybe thinkingthat we need another type of
thingthat can be sold based on other feedback. This could be related.
Dave Rapin: That's correct. I can already apply the '2+ league discount' to a 'Product', so it seems like there shouldn't be any architectural issue with applying discounts to products based on # of leagues. The only thing missing is that there's no '1+ league discount'. It seems like this should be simple to add, since it should be almost identical to the '2+ league discount'.
When I initially requested this, it was in conjunction with a separate request called 'Spare fees'. Historically my club has charged a fee for sparing, but that fee is waived for people who are registered in a league. I was hoping to set up a 'Product' called 'Sparing', and only allow people to sign up as a spare if they have already purchased this product (that's the content of my other 'Spare fees' request). I would then apply the '1+ league discount' to that product (that's this request).
Another example that would only require the '1+ league discount' is that we could offer a paid curling clinic and give a discount to people who are registered in a league at our club. We don't have an immediate need for this, I'm just thinking ahead.
Mark Leusink: The fact that you can apply a multi league discount to a product was most definitely an oversight (minor bug). It's interesting though.
As I understand it, you are no longer using this (hidden) feature?
Dave Rapin: I guess one person's bug is another person's feature. :)
I skimmed through our products and unless I overlooked something, it appears that we are not currently using the multi-league discount for any products. However, I don't see any harm in leaving it available, since it would take effort to remove it and it would decrease flexibility for your users.
Mark Leusink: I agree that it's a nice to have. It just needs to be properly documented, and I need to make sure it's being implemented properly (only applies to seasonal products).
marked this post as