An often asked question is how saving on orders is being arranged, especially from webshops. Before that question can be answered, it's important to understand how saleorders should be implemented at a customer site.

When a saleorder (customer order) is being created for a certain customer, this doesn't do anything with loyaltycard savings. The order itself is nothing more than a registration of products which a customer would like to order. At the moment a saleorder is being procesed, reservations will be created from saleorders. The reservation is actually a representation of products which are set aside, and are reserved for that customer (order).

The next step in that process is 'selling' the reservation to the customer. By doing so, a sale will be created, resulting into profit, a lower stock and possibly purchase orders to refill that stock. This is also the moment where a customer will be rewarded for his buyings: RetailVista will calculate the number of saved points on a loyaltycard, and add those points to the loyaltycard.

The only downside of the current approach is that RetailVIsta POS will try to find a loyaltycard for the customer of the transaction, the customer of the imported reservation. When a loyaltycard is not registered, it would not find a loyaltycard!

This means it's not necessary (not wanted!) to calculate loyaltycard savings in an earlier stage, for example when creating a saleorder on a webshop. By doing so it would result in double savings at the end!