Points & Slabs
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.
| OPTION | DESCRIPTION |
|---|---|
| Denote stores by external ids | Check if stores are denoted by store external ids |
| Replace invalid store names with | Choose the store that you want to replace with in place of invalid stores identified in the import |
| Append country code to the mobile number automatically | Check this box to prefix the base country code of the org's base country wherever mobile numbers without country code are identified |
| Identification of Bill(Transaction) | Choose whether the transaction is identified from the loyalty log or standard fields |
| Choose customers' unique identifier | Choose the unique identifier of the customer used at the organization |
| Do not add points if points already provided | Check this box to avoid accruing points in case of multiple imports for the same bill. If unchecked, the points that are imported every time will keep adding to the existing bill |
| Select the expiry strategy for points expiry | Choose the desired points expiry strategy for the current template |
| Promotion name | Enter the name of the promotion. Note: The name you specify will store in the backend directly. Hence, when you fetch details, the system no longer appends the timestamp to promotion name (as earlier), but retains the name that you specified. |
| Points allocation strategies(only delayed accrual) | Choose the delayed accrual strategy that you want to associate to the current points (only for delayed accrual points) |
| Import on group primary customer | Set this option to Yes for user group import and use the identifier of the primary member of the group to identify the group. |
| Set user defined promotion identifier | Check this if you want to use an external identifier for the promotion and enter the identifier in the text box that appears. When you provide a new identifier, a new promotion is created with the given identifier and name. When you provide an existing identifier, points will be awarded under the existing promotion. NOTE: Ensure you provide the same promotion name when using existing promotion identifier. If there is a mismatch, the system will throw an error. |
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.
| OPTION | DESCRIPTION |
|---|---|
| Denote stores by external id | Check this box if you are using (in the CSV file) store external ids to denote stores |
| Replace invalid store names with | Choose the store that you want to replace with in place of invalid stores identified in the import |
| Append country code to the mobile number automatically | Check this box to prefix the base country code of the org's base country if mobile numbers without country code are identified |
| Identification of bill (Transaction) | Choose the identifier used for transaction - standard fields or loyalty log id. Standard fields include transaction number, and transaction date where as the loyalty log id is the unique id for the transaction created in the log. You can get the loyalty log id from user_management.loyalty_log table in the db |
| Identification of line item (Transaction) | Choose the identifier used for line-item (item id or item code) |
| Choose customers' unique identifier | Choose the unique identifier used for customer registration |
| Do not add points if points are already provided | Check this box to disable adding points if the points are already added for the line-item. When unchecked, if you have imported 5 points for a line-item of a loyalty transaction who already has 10 line-item promotion points, the customer will have 15 (10+5) promotion points for the line-item |
| All programs of the org | Choose the loyalty program from which you want to issue points. |
| Select the strategy for points expiry | Choose the expiry strategy for the points issued through the current import. You will see all expiry strategies associated with the chosen program |
| Points allocation strategies(only delayed accrual) | Choose the delayed accrual strategy that you want to associate to the current points (only for delayed accrual points) |
| Promotion name | Specify the name of the promotion to which you want to associate the current points. If the name is not identified, then points are issued under a new promotion name that you specify here. |
| Import on group primary customer | Set this option to Yes for user group import and use the identifier of the primary member of the group to identify the group. |
| Set user-defined Promotion Identifier | Check this if you want to use an external identifier for the promotion and enter the identifier in the text box that appears. When you provide a new identifier, a new promotion is created with the given identifier and name. When you provide an existing identifier, points will be awarded under the existing promotion. NOTE: Ensure you provide the same promotion name when using existing promotion identifier. If there is a mismatch, the system will throw an error. |
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
| OPTION | DESCRIPTION |
|---|---|
| Denote stores by external ids | Denote stores by external ids |
| Denote stores by external ids | Choose the store that you want to replace with in place of invalid stores identified in the import |
| Append the country code to the mobile number automatically | Check this box to prefix the base country code of the org's base country wherever mobile numbers without country code are identified |
| Choose customers' unique identifier | Choose the unique identifier of the customer used at the organization |
Slab
You can update the loyalty tiers of customers or groups using this profile.
To import the loyalty slabs of registered customers or groups, create a CSV file with the following fields.
Customer identifier (mobile number/external ID/card number)
Group identifier (group external ID, primary user ID, group ID, email/mobile number/external ID/ card number of the primary user)
Store's External ID/ Store Terminal User Name
Slab Name
Last Slab Change Date
Notes
** At least one among these fields is mandatory.
A customer identifier is required to update customer slabs and a group identifier is required to update group slabs.
Template Configuration
| OPTION | DESCRIPTION |
|---|---|
| Denote stores by external ids | Check this box if the stores of the organization use store external ids as store codes |
| Replace invalid store names with | Choose the store that you want to replace within the place of invalid stores identified in the import |
| Append country code to the mobile number automatically | Check this box to prefix the base country code of the org's base country wherever mobile numbers without country code are identified |
| Choose customers' unique identifier | Choose the unique identifier of the customer used at the organization |
| Do not downgrade the slabs for users | Check this option to not allow downgrading loyalty tiers that you want to import |
| Renew slabs for users | Check this option to renew loyalty tiers that are downgraded based on the tier downgrade strategy configured for the org. For example, in membership-based loyalty programs |
| All programs for the org | Choose the loyalty program for which you want to update customer tiers. |
| User Group2 Enabled | Check this box if you want to update slabs of user groups. |
| User Group2 Identifier Type | Choose the unique identifier that you used in the CSV file to identify the user group. |
Updated 5 months ago