Process flow examples¶

Scenario 1 – Customer receives loyalty and personal promotion vouchers¶

In the process flow below:

The first API call retrieves the customer details (after the customer search criteria are typed in) which include:
- CRM CustomerID (which is also the ID used in Treazure)
- Customer details and preferences
- Voucher attribute (EB) that is linked to a loyalty promotion to earn points.
- Voucher attribute (FF) to trigger a financial or extra article promotion if the basket conditions are met.
The second API call uses the CRM CustomerID to query Treazure to receive the:
- Loyalty program information and the point balance as well as the
- Vouchers issued to the customer (in this example the ‘LR’ voucher is issued because the customer has reached the point threshold). The voucher will trigger the promotion when the basket conditions are met.
The example below shows how the vouchers are displayed in the ‘Sale’ screen in rPos, i.e., the loyalty reward is displayed as a ‘Loyalty voucher’ and the friend of the family voucher attribute as a ‘Personal promotion’.

This scenario describes the process where the vouchers are issued in Treazure based on the request from the CRM system.

The CRM requests vouchers (with a specific voucher attribute) for a list of customers.
These vouchers are issued and linked to the customer in Treazure.
When the ‘GET’ call is done to Treazure, Treazure will return the vouchers linked to the customer(s) and track the voucher(s).
This voucher attribute originally sent by CRM (BR) should not be linked in CRM to the customer since it is tracked by Treazure.
In the ‘Sale’ screen example below, the ‘Loyalty reward’ voucher is already redeemed and therefore it is not shown anymore in the list of vouchers.
The new ‘birthday’ voucher requested by the CRM (in the issue demand call) is linked to the customer and can be selected.