Customer Rewards

there is currently no way to remove a customers email address from customer rewards. this should be in place to comply with GDPR regulations if a customer requests a right to forget. changing the email address in back office does not replicate to rewards.

Currently, points are only processed when an order is tendered through the system, rather than at the point of ordering. This creates a problem when running bonus point promtions, as the points will not be applied if the order is tendered after the promotion has finished. For example, running a 'double points weekend' would not work, as orders placed on the Sunday would not be tendered until the Monday and would then only be awarded standard points.

At the moment if we run a double points promotion the customer points multiplier will multiply the promotion. i.e if we run a triple points promotion and a customer has a double points multiplier against their account then they will receive a 6 x points multiplier. Could we suggest that there is a setting added to Customer Rewards where a retailer could set it so that the points generated from a transaction are based on the higher of either the customer or the promotion. This will avoid customers with multipliers receiving very high amounts of points. It would need to be set so that if the multiplier is below 1 then the points are calculated in the same way as they are now. i.e. if a customers points multiplier is 0 then if a 3 x points promotion is run the customer would still receive 0.

I can see there are plans to look into rewards / coupon usage with Apple Pay. In the interim could wording be added at the point of Rewards and Coupon redemption to explain the feature is not compatible with Apple Pay? We get a lot of customer service on this, a good number of poor Shopper Approved reviews and I dare say the odd dropped basket. Cheers ;-)

Its probably best to hide the customer login password, although they are generated by rewards, if a customer changes it to their own personel secret password we can see it, which is a GDPR issue.