Vouchers for rewards can be connected to Benefits and Actions. Typical examples include:
- Complete a purchase within 7 days and get a 10% discount voucher (Action).
- As long a user is a Gold member he gets a free shipping voucher (Benefit).
Pool settings
The first step for each voucher pool type is managing the general settings which includes:
- Pool Name: The internal name for you to use when connecting this pool to benefits and actions.
- Voucher Type: Here, you can select the recurrence of this pool (Single-Use / Multi-Use). Make sure to upload the right type and number of codes.
- Delete Voucher automatically after member has used it: This option is only available for Single-Use Vouchers. If you select this option, then Loyalty automatically deletes vouchers used for purchases by members.
Loyalty can only delete vouchers used for purchases if the sales data file includes the vouchers within the field s_coupon
.
- Voucher Name: The name that your Loyalty members will see in their Wallet for this voucher.
-
Icon: The icon that your Loyalty members will see in their Wallet for this voucher.
- You can either select icons from our library or upload your own icons.
- Icon requirements:
- Provide the icon in SVG or PNG formats
- The icon has to fit a square area of 200*200 px
- The image has to touch the border of the square area
- Icon requirements:
- You can either select icons from our library or upload your own icons.
- External URL: You can add a URL that links to a page directly from the Voucher in the Loyalty Wallet.
- URL Text: You enter a text to display for the URL that is shown to members in the Loyalty Wallet.
- Voucher Value: If you assign a value to this voucher, then it is used to calculate return on investment and track the monetary value members have in their Loyalty Wallets.
Upload file
When creating voucher pools, you have to upload CSV files containing the voucher codes to fill up the pool. It is your responsibility to produce, upload and resupply codes, as well as, support the code redemption. Loyalty's responsibility is to distribute the vouchers to customers in accordance with the pool settings you define. You can upload one-time or multi-use codes and set the validity of the vouchers as presented to your Loyalty members. When the pool is about to be empty of codes, or codes are about to expire, you will be notified via the notification center.
Upload code list - Only CSV files can be uploaded, maximum size per upload is 1 MB. Make sure to upload codes that support the voucher type you set (one-time use / multiple use, total number or redemptions). The codes' expiration date should be in sync with the pool validity you set later.
A sample CSV template:
Upload validation - Here, you can preview and check the uploaded codes before adding them to the pool.
Since all codes are managed in one bucket, once you add new codes, these will mix with the existing ones and cannot be separated. In the event of a mistake, you will need to deactivate the pool, delete all existing codes and upload new ones.
Codes status - a pool information table with which you can track your uploads and delete existing codes.
Refill reminder - Define the number of valid codes remaining in the pool that will trigger the refill reminder.
Validity
It is not possible for members to earn vouchers (with points or as a fixed benefit) when their validity would be longer than the remaining days from the pool validity. In such a case (towards the end of the pool validity period), the relevant vouchers do not appear as available.
- Voucher is valid for a predetermined date for all members. For this option, you have to select an expiry date.
Since the Loyalty Wallet is not connected to your checkout, the Wallet does not know if and when the voucher is actually redeemed after the voucher code is exposed. Therefore, the Loyalty add-on cannot automatically delete it after use. Members can manually delete a voucher after they redeem it in the Wallet.
Alternatively, you can use the API to delete a voucher. For more information, see Redeeming a voucher.