It's important to understand the concept behind loyaltycards. They are available in 3 different kinds:

 

1 - Points based loyaltycard

2 - Value based loyaltycard

3 - Identification based loyaltycard

The points based loyaltycards are available to save points earned by buyings. Within RetailVista users can define a percentage per sale value for example per salegroup, classification or articlecategory. That percentage is recalculated to a number of points which can also be defined. The big advantage on points in opposite to value based loyaltycards is that the value of points can be readjusted afterwards, while the value of a value-based card can never be adjusted anymore (customers would notice that immediately). The usage of point based loyaltycards is advised strongly!

As said, RetailVista also supported value based cards. These cards hold a value, based on a percentage of salue value per salegroup, classification or articlecategory.

The last feature is identification based cards. On these kind of loyaltycards, no point or value is being saved on each sale. These kind of cards are only used for customer identification. It is used commonly for debtor identification. Certain debtors can receive a card which makes it easy to recognise them within RetailVista POS.

To start using loyaltycards, a range of loyaltycards needs to be created within RetailVista. These cards are all generated without being assigned to a customer. Afterwards, customers can be assigned to cards, but it's not a requirement. There are a large number of settings around loyaltycards, for example settings so customers can't redraw a card value unless that card is registered for example.

To prevent the loyaltycard system from being abused from the public Internet, it's strongly advised to use a combination of the loyalty cardnumber and checksum when requesting data or even adjusting card information. RetailVista will support this: on the process of passing a card to a customer, RetailVista POS can ask for a checksum to the customer standing in front of the checkout. It's up to the RetailVista user to decide what kind of checksum to use. But in most circumstance, the zipcode of a customer is being asked. That checksum (zipcode) is then being save together with the card information and can be used later with a GetLoyaltyCards() webservice to request card information afterwards.