Consider following example:
Let’s assume we have customer action – “purchase” with a set of attributes: product, category,
price, amount, total sum, date of purchase, etc. A customer purchased two items:
- product – X, category – commodity goods, price – 100 dollars, quantity – 5 items, total sum – 500 dollars, purchase date – 1/1/2010 11:00.
- product Y, category – other goods, price – 200 dollars, quantity – 1 item, total sum – 200 dollars, purchase date – 1/1/2010 11:00.
I.e. for one purchase there are 2 records created in the system.
It is obvious how to create reward rules for buying product X, or for buying a product from category “other goods” or for a purchasing items with cost more then 150 dollars.
But sometimes it is required to assign bonus points if total purchase sum is larger then N dollars. In this case the product, its category and quantity will be ignored.
What to do in this case?
If you can simplify the processing rules – send only one record representing the total purchase with attributes: total sum, purchase date. In our case it will be following action:
- total sum – 700 dollars, date of purchase – 1/1/2010 11:00.
And create a reward rule depending on total purchase sum.
So, with some preliminary data processing it is possible to solve vast majority of such problems without changing the PointLoyalty Manager system.