Consider the following example:

A program has two tiers - Base and Silver. Customers need to spend lifetime purchases of at least 100 to upgrade from a normal tier to the loyalty tier.

  • Tier Upgrade: 
    • Upgrade type: Upgrade tier first and then issue points according to the new tier.
    • Upgrade when lifetime purchases amount exceeds 1000.
  • Points Allocation
    • For transactions made in Mumbai stores, issue points of 
      • 2% the transaction amount only if they shop between 10 AM to 4 PM from Monday to Friday (non-peak hours) and 
      • 1% for the rest of the time (peak hours).
      • For transactions in stores other than Mumbai, issue  2% of the transaction amount as points.
  • Points Expiry: One year from the points issued date.

To configure the above loyalty program, do the following:

  1. On the Tiers, click Advanced settings.
  2. On the Tiers page, click +Create new tier and create the base tier. Similarly, add another tier with the name Silver.
  3. For the second tier set Eligibility criteria to Lifetime Purchases; Upgrade type to Upgrade to the next tier and then issue points; and if value to 1000.
  4. Navigate to Points > Earn Condition. Open the Add earn condition tab and create two different allocation strategies - one with 1% of the transaction amount and the other with 2% of the transaction amount.
  5. Then, navigate to the Expiry condition field and click Add expiry condition. create points expiry strategy and set the expiry to 12 months from the event date (points issued date) as shown below.
  6. Then navigate to workflows and configure rules accordingly.
    1. In Customer Activity, choose TransactionAdd to configure rules for transactions. 
    2. You need to create a separate set for each condition that you want to validate. 
    3. Set the action Forward to set for each satisfying condition and define the actual action to be performed in the last set. For example, in the screenshot below, the action to be performed for Set1 it is defined Set3 and for Set4 it is defined in Set4.
  7. Select the Customer Activity as TransactionAdd.
  8. In the following example, Set1 (a master set) is created which will check the conditions defined in Set3 (to check whether a transaction is made in Mumbai and visited during non-peak hours) and Set (to check whether the customer is not from Mumbai).
  9. Apply Store Level Scope to the set and select store(s) belonging to Mumbai. Tip: Set the button to Include and select the store(s) that are in Mumbai. You can also upload a CSV file with store codes using StoreCode CSV option.

    If you use both the options - select stores and also upload store codes - then the priority is given to the StoreCode CSV option.

  10. Now, set the condition to check whether the transaction is made during the non-peak hours, i.e., Monday - Thursday between 6 am - 4 pm. If yes, set the points allocation strategy that corresponds to 2% of the transaction amount; if false, set the points allocation strategy that corresponds to 1% of the transaction amount. Now same as above configurations, for Set 7, set a store level scope and select the stores that are not in Mumbai and click Save Scopes. Tip: Set the button to Exclude and select the store(s) that are in Mumbai.
  11. As no other condition needs to be verified, set Expression and Expression Equals as true as shown below and set the allocation strategy that issues points of 2% of the transaction amount

  1. Set the allocation strategy that issues points of 2% of the transaction amount.
  2. Click Save to save the recent changes made in the loyalty program.
  3. Then click Reconfigure to affect the changes made in the loyalty program.