Phoca Forum

Hi, yes, I understand. As I wrote for now it is based only on products, so yes thera are two possible ways to improve this feature in future:

1) to add it to attributes - but it is very problematic as what to do when two attributes work together (T-shirt XXL size, Blue color). What reward points to get when size and colors have different reward points

2) to extend current reward points system throug e.g. some total amount rule

Added into feature request list


Reward points class is here: administrator\components\com_phocacart\libraries\phocacart\reward\reward.php but the system is complex so in fact reward points will be handled in cart, etc.

Jan

Jan wrote: ↑31 Aug 2019, 17:02 1) to add it to attributes - but it is very problematic as what to do when two attributes work together (T-shirt XXL size, Blue color). What reward points to get when size and colors have different reward points

Jan

You could set the reward points based on primary attribute? For example, shirt size is primary attribute, and colour is a secondary attribute to shirt size - or if attributes don’t affect price of product, still have reward points for main product, or different price on attributes, set reward points only where prices differ. You could also do increments in points, one attribute is 15 points, but if adding a secondary attribute that adds to the price of the product, it adds 5 points to the reward points total giving you 20 points rewarded...

Hi, it is not so easy as if ther is only one attribute, e.g.:

Product A ... 10 points
Product A Option 1 ... 5 points
Product A Option 2 ... 7 points

Ordering product A ... 10 points ... OK
Ordering product A Option 1 .... 5 points or 15 points (10 + 5)
Ordering product A Option 1 and Option 2 ???? get 7 points or 5? get 17 points or 15 points? get 22 points? This will be always ambiguous and confusing and even you set some rules like only the first option is count then you will get questions why only first why not all, etc. etc.

Jan wrote: ↑02 Sep 2019, 12:31 Hi, it is not so easy as if ther is only one attribute, e.g.:

Product A ... 10 points
Product A Option 1 ... 5 points
Product A Option 2 ... 7 points

Ordering product A ... 10 points ... OK
Ordering product A Option 1 .... 5 points or 15 points (10 + 5)
Ordering product A Option 1 and Option 2 ???? get 7 points or 5? get 17 points or 15 points? get 22 points? This will be always ambiguous and confusing and even you set some rules like only the first option is count then you will get questions why only first why not all, etc. etc.

Maybe I'm explaining this wrong... Looking closer at the Attributes Tab, you have Add Attribute, and then you have Add Option to the Attribute... So you can have multiple Attributes with multiple Options... So, in my example, I have 1 Attribute, with 3 Options:
Attribute Title: Image Resolution - with 3 Options:
Option 1 Title: 1280x720
Option 2 Title: 2560x1440
Option 3 Title: 6240x3510

Okay, so just like attribute price adds to the product price. attribute points would add to the product points... as per your example above: (if Attribute 1 is size, and Attribute 2 is colour)
Product A $10 and 10 Points
Product A $10, 10 points, + Attribute 1 $5, 5 points = $15, 15 points
Product A $10, 10 points, + Attribute 1 $5, 5 points, + Attribute 2 $7, 7 points = $22, 22 points

Now, for my example: (if Attribute 1 (image dimension) has 3 options: Size 1 $10, 10 points, Size 2 $15, 15 points, Size 3 $25, 25 points)
Product A $0, 0 points (cant buy this, need to select Option 1 attribute)
Product A $0, + Attribute 1, Option 1 $10, 10 points = $10, 10 points
Product A $0, + Attribute 1, Option 2 $15, 15 points = $15, 15 points
Product A $0, + Attribute 1, Option 3 $25, 25 points = $25, 25 points
Since I can only select one option for Attribute 1, there is not price or points addition.

In most cases, even with T-Shirts that have size and colour, you can't select more than one size or more than one colour for one T-Shirt - you would only select size large, and colour black for example... you would NOT select Size large and medium, and colour black and colour white for one T-Shirt - you would add each T-Shirt individually.

How the attributes tab looks now:


Essentially, being able to add reward points to individual options on attributes, not just main product, would be a much more suitable method... and, if people understand the math of how points are calculated on products, I don't think it would be that confusing. Even with multiple Attributes, with multiple Options for each attribute, this would still work: So, some examples would look like this:
Product 1, Attribute 1, Option 2 = $15, 15 Points
Product 1, Attribute 2, Option 3 = $25, 25 Points
Product 1, Attribute 1, Option 2 + Product 1, Attribute 2, Option 3 = $15 + $25 ($40) and 15 points + 25 points (40 points)
Product 1, Attribute 1, Option 3 + Product 1, Attribute 2, Option 2 = $25 + $15 ($40) and 25 points + 15 points (40 points)

Now, with Product having 1 Attribute with 3 Options, your product admin page, Attributes Tab would look like this (adding in columns for Reward Points Given/Received, and Reward Points Needed):


and your Product Detail pages would look like this:


Product 1, Attribute 1, Option 1


Product 1, Attribute 1, Option 2


Product 1, Attribute 1, Option 3

I also think the Language file would need to be updated to have Reward Points Given/Received, Reward Points Needed, and Reward Points Used...

Does this explain it any better, or am I still not understanding the limitations of the system?

Regards,

Jeff

I should also add, in terms of help documentation, reward points on Attributes would be an "incremental" or addition calculation: Attribute 1, Option 1 + Attribute 2, Option 1 = Total Points Given/Received - points would only be given if there is a cost for an attribute option.

For a T-Shirt example (2 Attributes): Product 1: main product has a price of $10, with Reward Points Given/Received of 10 points and Reward Points Needed of 100 points.

Attribute 1 (Sizes): Attribute 2 (Colours): So, a customer selects a Large, Black T-Shirt, they would get 10 points, they would need 100 points to get it for free, and the shirt costs them $10 (main product has a price of $10, gives 10 points and needs 100 points + Attribute 1, Option 3: +$0 +0 Points +0 Points Needed, + Attribute 2, Option 1: +$0 +0 Points Received + 0 Points Needed = $10 10 Points Received 100 Points Needed)...

But if they select an XXL, Red T-Shirt, they would get 19 points, they would now need 190 points to get it for free, and the shirt now costs $19 (main product has price of $10, gives 10 Points and needs 100 points + Attribute 1, Option 5: +$4 +4 Points Received +40 Points Needed + Attribute 2, Option 3: +$5 +5 Points Received +50 Points Needed = $19 19 Points Received 190 Points Needed)

For a single Attribute (much simpler) example: Product 1: main product has a price of $0, with Reward Points Given/Received of 0 points and Reward Points Needed of 0 points.

Attribute 1 (Image Dimensions): Since they can only choose one Attribute Option, they would get either 10, 15 or 25 Points, and they would need 200, 300, or 500 points to get for free depending on which attribute option was selected.

Hi, thank you for the info, I have added it to the feature request list. The question still remains, if this way will be not so much complicated for the vendor that it is better to just add reward points feature based on final purchase amount (as an add-on to existing reward points system).

The problem of mixing points of different combinations of parameters is similar to advanced stock management, see here:
https://www.phoca.cz/documents/116-phoc ... management (but much more complicated through the points received vs. points needed). And not sure if such can be easily managed by vendors

Even it is much more complicated because there are select boxes and checkboxes, so you can:
1) select more attributes together
2) but even you can select more options of one attribute together (this is not a case for t-shirt example but e.g. for pizza example)

So your product can be Product A Attribute B and Attribute C and Option 1 and Option 2 from Attribute B and Option 1 and Option 2 and Option 3 from Attribute C.

Jan