Bill Points Promotion (Accrual)

This profile lets you add promotion points for existing transactions and line-items. You also need to choose the points expiry strategy for the points issued through this profile in Configure Template.

Note: You cannot import transaction level promotion points through transaction profiles.

• Mobile/Email/External ID*
• Loyalty Log ID
• TILL IUN or Store's External ID (Store Code)*
• User ID
• Transaction Number*
• Date of Transaction*
• Points*: Points to be issued
• Mobile/ Email/External id/ User id(Original User Identifier): Identifier of the actual customer who made the transaction. Required for group transaction.

CSV Sample:

Mobile,Til IUN,Transaction Number,Date Of Transaction,Points
9900111111,mal1,Trans122591,10/10/2015,100

Template Configuration
If you import multiple files using a specific template, all will have the same promotion identifier assigned to them.

The identifier is retained as long as no changes are made to the template.
When you make a change in the template and save, a new identifier is generated.

📘

More About Delayed Accrual

• You can add points only for existing transaction line items.
  • The issual date for the points will always be the current date.
  • The points allocation date is the date on which the points are actually added to the current points. For example:
    If a transaction with bill date A is sent to Loyalty EMF on date B, the awarded date will be date B.
    If a transaction/add on date A gets replayed on date B, the awarded date will be date B.
    * If bill points with bill date A are imported on date B, the awarded date will be date B.
  • The 'delayed accrual points' will be added to the 'current points' on the next morning of the (event date + number of days of delay) specified in the point allocation strategy
  • if a transaction is added on 28th Sep and the number of days of delay is 1, the delayed accrual points will get added to current points on the morning of 30th Sep (morning after 28th Sep + 1 day). The awarded date will be 30th Sep.
  • An event should have same type of points allocation strategies (either direct allocation or delayed accrual but not both).
  • An event cannot have allocation strategies with different delay accrual period.

Line Item Points Promotion

This profile lets you update line-item level promotion points for loyalty transactions. The transaction number, and transaction date are required to update promotion points. You can also use loyalty log id instead of transaction number and date.

Following are the supported fields for this import:

• Loyalty log Id * (If you want to use LOYALTY_LOG_ID to identify the transaction )
• Email /Mobile/ External id/ User id*
• Till IUN Or Store Ext Id(Store Code)
• Item id/ Item Code*
• Transaction Number(Bill Number)* (If Identification of Bill is chosen as STANDARD_FIELD)
• Date Of Transactions(Bill Date)* (If Identification of Bill is chosen as STANDARD_FIELD)
• Points*
• Mobile/ Email/External id/ User id(Original User Identifier): Identifier of the actual customer who made the transaction. Required for group transaction.

Note: You can get the loyalty_log_id in the user_management.loyalty_log table

Template Configuration
If you import multiple files using a specific template, all will have the same promotion identifier assigned to them.

• The identifier is retained as long as no changes are made to the template.
• When you make a change in the template and save, a new identifier is generated.

📘

Note:

• You cannot add a new transaction or line item through this import. You can just add or update promotion points of a transaction.
  • You can just add points to the existing transaction line-item but cannot override existing points.

This profile lets you redeem points of loyalty to customers against transactions.

This profile lets you redeem points of loyalty customers against transactions.

• Mobile/Email/External ID*
• Loyalty Log ID
• TILL IUN or Store's External ID (Store Code)
• User ID
• Transaction Number*
• Date of Transaction
• Points (points to be redeemed)
• Notes

CSV Sample:

LoyaltyLogId,Mobile,Til IUN,Transaction Number,Points

9900111111,mal1,Good122595,100

Template Configuration

Slab (tier)

You can use this profile to update the loyalty tiers of customers or groups. You can also use this profile to update only the expiry date of the tiers.

To import the loyalty slabs of registered customers or groups, perform the following:

1. Create a CSV file with the following fields:

   1. Customer identifier (email/mobile number/external ID/user ID). The mobile number is mandatory.
   2. Group identifier (group external ID, primary user ID, group ID, email/mobile number/external ID of the primary user)
   3. Store's External ID/ Store Terminal User Name
   4. Slab Name - This is a mandatory field.
   5. Notes
   6. Last Slab Change Date
   7. Custom Slab Expiry Date - You can use this option to change the expiry dates of customer tiers in bulk. For example, during the onboarding of new brands or can also be used to update customers' tier expiry date in bulk whenever required.
      This field becomes mandatory if the configuration Set custom slab expiry date for the users is selected.
      Notes:
      • The expiry date should be a future date and not beyond the year 2100.
      • The date should be in the YYYY-MM-DD HH:MM:SS format. If the expiry date is added in the YYYY-MM-DD format, the system will consider it as YYYY-MM-DD 00:00:00.

   Sample CSV file format:
   user_id,store_code,slab_name,notes,last_slab_change_date,new_slab_expiry_date 423771868,'124','GOLD','notes','2024-01-13 00:00:00','2028-01-13 08:06:00'

   

Template Configuration