Skip to content

Treazure Loyalty Vault

Definition of Terms and Abbreviations

The following is a list of acronyms and definitions used within this document.

Term Description
Voucher A Voucher is linked to a customer and when the customer card is added to the basket, all vouchers issued to the customer will be displayed automatically to choose from.
Coupon A coupon is ‘physical’ which could be a physical coupon or digital (coupon from an email). The difference is that this needs to be actioned by the customer/consumer, i.e., there is no ‘voucher’ list to choose from, you need to add it manually to the basket.

Voucher origin

A voucher can only have one origin, which is either in Treazure or in the CRM system.

Treazure

  • When a voucher is issued in Treazure, the voucher is issued (linked) to a specific customer with a unique ‘voucher serial number’.
  • In this document there are three (3) examples where the vouchers are issued in Treazure:
    • When the savings threshold is reached, a voucher is issued.
    • When the consumer buys a voucher when a saving goal is reached, a voucher is issued.
    • When the CRM requests vouchers to be issued for a specific customer (Post issue ondemand API call)
  • The voucher is tracked within Treazure and when the voucher is redeemed, the status changes from ‘issued’ to ‘redeemed’ and the voucher is removed from the customer.
  • Voucher attributes tracked in Treazure should not be linked to the customer card in the CRM system, i.e., the vouchers will be received via the Treazure GET call and not via the customer call to the CRM (e.g.Voyado). (See scenario 2).

CRM

  • When a voucher attribute is linked in the CRM system to the customer card for exclusive deals (personal promotions), the CRM is responsible for tracking the voucher attribute.
  • For example,
    • If it is the customer’s birthday, a voucher attribute is created in the CRM system (e.g., BR) and the attribute is linked to the customer card in the CRM. This attribute is sent with the customer details when the customer call is made to the CRM. The same attribute is also created in rCos to trigger the promotion when the attribute is linked to the customer card.
    • If the promotion (triggered by the voucher) was applied and the customer received the discount, the voucher attribute will not be removed by Treazure from the customer card, it must be removed in the CRM system.

AccountNumber

The account number parameter refers to the customer ‘CRM’ account number in the loyalty vault.

Expiration

There are two types of expiration:

  • Account expiration All available balance in the account will expire on a certain date. Points collected before the expiration moment will expire but points collected after the expiry moment will remain. Previously collected points will have their expiration bumped when collecting at a later time.
  • Balance expiration Collected points will expire, regardless of collected points in the future. This expiration moment is determined when points are received.

It is possible to setup an absolute (expire at x) or a relative expiration moment (x days after today).

All expiration types take into account spent balance. If you collect 100 points and spend 60, you have 40 points remaining. 40 points will be deducted on expiration.

Expiration in retrospective

Please note expiration for an account is determined when loading points. That means that if an account is not loaded after setting expiration on the program properties expiration date is not updated for that account. For setting expiration retrospectively for loaded points, entire account balances or received vouchers, contact Cow Hills.