You can define conditions for earning points, redeeming points, expiry of points and returning points. ## Overview Earn conditions allow an org to create various conditions and define how a customer can earn points. You can have common points allocation across tiers or different allocations for each tier. ### **Note** - For **MLP enabled orgs**, allocation strategies created in a program are associated only with that program and cannot be used even in the org's default program. - Capillary does not support converting already allocated redeemable points to non-redeemable points. If you need to remove or suppress redeemable points after allocation (for example, due to double allocation or error), you can use the Manual Points Adjustment[UI](https://docs.capillarytech.com/docs/points-deductions#manual-points-adjustment)/[API](https://docs.capillarytech.com/reference/deduct-points-and-alternatecurrencies-from-user#/). ### Configure points delay accrual Delayed accrual allows issuing points to customer for an activity at a later date. For example, if you support item returns, say for a week from the purchase date, you can actually block customers from using those points before the return period. This avoids redundancy and fraud activities. In Delayed Accrual, points are first issued as promised points. These cannot be redeemed by the customer. After the configured period, these points are converted and credited to the main balance. In Delayed Accrual, the points allocation date is when points are actually issued to the customer. In the case of Delayed Accrual, the awarded date is when points get added to the current points (accrued date). Refer to the following examples for clarity. - If a transaction with bill date A is sent to Loyalty EMF on date B, the awarded date is date B. - If the transactionAdd activity of date A gets replayed on date B, the awarded date is date B. - If bill points with bill date A are imported on date B, the awarded date is date B. ### The 'delayed accrual points' are added to the 'current points' on the next morning of the delay period, i.e., (event date + the 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 28, Sep + 1 day). The awarded date is 30 Sep. You can create rules on the points that are redeemable, non-redeemable, or with the summation of both. Find the details of event, action, and limitations of Delayed Accrual below - 1. **Event name**: DelayedAccrual. You need to configure the DelayedAccrual activity to perform actions on Delayed Accrual. 2. **Action**: To enable converting promised points to current points, for the DelayedAccrual activity, you need to set **Delayed Accrual Action**. - **Other actions supported**: - Send Messages (SMS, Email, Mobile Push) - Upgrade To Tier - Issue Coupon - Delayed Accrual 3. **Limitations**: - For an activity, you cannot use both direct allocation and delayed accrual strategies. You cannot have strategies with different delay periods. For example, you cannot use one strategy with 4 days delay period and another strategy with 7 days delay period. - You cannot use **Delayed Accrual** strategies on Registration and Customer Update activities. ## Points unlock ability By now, it is very clear that brands can give delayed points to their customers from our Loyalty settings (delayed accrual strategy). However, some times brands might want to convert these delayed points also as redeemable points for their customers. The only way available to do this is via external triggers. Till now, we have this ability only for bill level. But now, we have the ability to do this even on line item levels. Merging customer accounts does not act as an external trigger. Promised points transferred during a merge remain in the promised state and still require the external trigger to be fired before they convert to redeemable points. **Some sample use cases:** 1. As a system integrator, I would like to be able to to configure fixed return windows for different line items, allocate promised points on each line item and convert them to redeemable points according to each line item’s return window, so that the users can get regular points on each line item, as and when the return window for the line items gets over and don't have to wait for the default return windows to get over. 2. As a Loyalty Program Manager, I would like to be able to give my customer an option to end the return window for any transaction or any line item in the transaction and immediately convert promised points to regular points. You can find more information on how to use this API at below link, please refer. [Points Unlock API](https://docs.capillarytech.com/reference/points-unlock-api) ## Configure points earn conditions There are three allocation types available. - **Fixed**: A fixed number of points is allocated irrespective of the transaction amount. - **Round Up**: Points are awarded for the gap amount within a defined range. This type can only be used inside Engage+. - **Prorated**: Points are issued as a percentage of the transaction amount or custom field value and through step function. Based on the chosen allocation type, you can have the following combinations of points allocation strategies. - Reward points as a percentage of a transaction amount with the same percentage across tiers. For example - Tier1: 15%, Tier2: 15%. - Reward points as a percentage of the transaction amount with different percentages for each tier. For example - Tier1: 15% of the transaction amount, Tier2: 20% of the transaction amount. - Reward a fixed number of points per transaction across tiers. For example - Tier1: 15 points per transaction, Tier2: 15 points per transaction. - Reward a fixed number of points per transaction with different values across tiers. For example - Tier1: 10 points per transaction, Tier2: 15 points per transaction. To configure earning conditions, do the following. - Reward a fixed number of points in equal step sizes or transaction intervals. For example, allocate 10 points on every spend of Rs.200. So a person doing a transaction of 450 will get 20 points, because his transaction amount lies between 400 - 600. 1. On **Intouch**, navigate to **Menu** > **Loyalty+** > **Programs**. 2. In **Programs**, select the program you want to edit. 3. Click **Edit Program**. 4. Click **Points**. 5. Click **Add Earn Conditions**.

6. In **Name**, enter the condition name.

7. In **Description**, describe the condition.

8. In **Module Using this Condition**, select the module **Loyalty** or **Engage** where you want to use this condition.

### Note - If you select Engage+, three options are available: **Fixed**, **Round Up**, and **Prorate**. - Selecting Engage+ allows you to define the earn conditions when issuing points for campaigns and journeys. 9. In **Allocate Based On**, select your preferred option, based on which the points are allocated.

Option	Description
Tiers	This is the default option. Points are allocated to customers according to their tiers.
Loyalty Registration	Points are allocated to customers based on the information they provide during the registration. You can select any one of the custom fields. For example, if you select an age group of 25-30, points are allocated to customers belonging to this exact age group.
Loyalty Transaction	Points are allocated to customers on the basis of their Loyalty transaction. For example, if you select order\_channel, points are awarded only to customers who made a transaction through a particular channel(For example- Instore).

10. In **Allocation Type**, select your preferred allocation type to define the criteria for giving points to customers.

Type	Module	Description
Fixed	Loyalty & Engage	Reward a fixed number of points (irrespective of the transaction amount). For example: 10 to issue 10 points per transaction
Round up	Engage	Reward customers with points to round their balance up to the nearest multiple of a defined value within a specified range. For example, if the points range is from 0-1000 and the round upto value is 10, a customer with 643 points will recieve 7 points, bringing their total balance to 650.
Prorated- in terms of %	Loyalty	Reward points as a percentage of the transaction amount. For example: 10 to issue 50 points if the transaction amount is 500.
Points Multiplier- in terms of %	Loyalty	Reward extra points to the customers along with the existing points. This is used in promotion (run with a shorter period) along with the existing allocation strategy. For example: If an org issues 10 points to the customers in the lowest tier, during Diwali season the org can issue 10x points to attract more customers in the lowest tier to make more purchases with the org. The customers will receive 100 points (10 multiplied by 10) if they make a transaction with org during Diwali season.
Prorate - In terms of step function	Loyalty & Engage	Reward a fixed number of points for equal transaction intervals or steps. For example: Allocate 5 points on every transaction of $150. This way, a transaction amount lying between $0-150 gets 5 points, and transactions between 151-300 get 10 points and so on. Note: Step function proration based on line-item quantity is not currently supported. At runtime, the step calculation always uses the line-item amount, regardless of the "based on" value configured.

11. Enable **Same for all Tiers** and enter the point value. The point value will be the same for all the tiers in the program, If disabled, you can enter different point values for different tiers.

12. In **Enable Delayed Accrual**, enable the checkbox and enter the days after which the customer is able to redeem points. - **DELAYED ACCRUAL**: Points are reflected in the customer's account immediately after the transaction but are only redeemable after the prescribed number of days. For example, if an apparel store has a return policy of seven days, and a customer buys a shirt and gets 20 points on this purchase. The points are reflected in the customer's account right after the purchase, but if the customer decides to return the shirt on the third day, the points will disappear from the account and the customer is unable to use the acquired points. Delayed accrual prevents customers from misusing points.

13. Click **Done**. ### Allocate points on custom field values You can also reward points to your customers based on the custom field values that are submitted on the customer registration and profile update screens of InStore. This works only for custom fields with integer values (for example: 20) and not for string values (for example: John). > Note: > When you set **Allocate Based On** to a custom field (such as a field collected during registration or transaction), you can only award points as a percentage of the transaction value. Conditions where points awarded equals the custom field value is not supported. For example, award 100 points when the custom field value is 100. To configure rewarding points based on custom fields, follow these steps: 1. In **Earn conditions**, click **Add earn condition** to create a new point earning condition, or to modify an existing condition, navigate to the earn condition and click the respective **edit** button. 2. In **Allocate based on**, choose either **Loyalty Registration** or **Loyalty Transaction** and select your desired custom field accordingly.

3. In the **Allocation type**, choose **Prorated** to allocate points as a percentage of the transaction amount. Fixed allocation is not supported when allocating based on a custom field value. 4. Click **Done**. ### Configure points round-up for campaigns Earn condition configuration for Campaigns has an additional Allocation type - Round up. This lets you round up points that are in a specific range for each tier. For example, when running campaigns, you can round up points that are between 30-100 to 100 for all customers in the base tier. ### If **Same for all Tiers** is disabled, Round up configuration will vary for each tier.

1. In **Allocation type**, choose _Roundup_. 2. In **Points range**, configure from, to, and round up to the range of points and the value that you want to have for the roundup. For example, if a customer has 40 points (current points) in his/her account and when the campaign is triggered, an additional 60 points will be added to his/her account making it 100 as configured. ### Configure rules for points allocation strategy Once you create a strategy, you need to configure the relevant activity and define rules based on which you want to execute specific points earning conditions. Allocation Points is an action that allows you to award points to customers based on certain activities (registration, transaction, profile update, coupon redemption, points redemption, tier upgrade). **To configure Rules for Points Allocation** : 1. In **Workflow**, go to Customer Activity and click TransactionAdd. 2. In **Select Customer Activity**, choose the activity for which you want to define earn condition rules. While defining actions, you can choose the desired allocation strategy in Earn Condition as shown.

3. You can also set up notifications to send to customers on the successful execution of the activity. Configure SMS, email, WeChat, and/or Mobile Push templates accordingly. ### Configure customer activity for points allocation at the transaction item level To allocate points at the transaction item level, you need to have a forward case in which the transaction item is enabled. To issue points on a transaction item based on the item price enable **Use proportions**. ### - Transaction item is available only for forward cases (Forward to set action). - **Use proportions** and **Maximize point allocation** options are visible only after you enable **Enable transaction item**.

1. **Enable transaction item**: Enable this option to issue points at the line-item level. 2. **Use proportions**: Enable this option to split points according to the price of transaction items. For example, consider a transaction with a bill amount of $300 consisting of two line items lineitem1 of $100, and lineitem2 of $200. If points allocation is 10% of the transaction amount, then 10 points will be issued for lineitem1 and 20 for lineitem2. 3. **Maximize point allocation**: Enable this option to set a cap on points allocated to customers. 4. **Enable tender unroller**: Enable this option to configure rules on payment modes. ### Limit points issual per customer for each set You can limit points issued to customers on transaction amount, line-item amount, and tracker value for each set and subset separately per customer. ### - After adding and deleting the capping value, click **Save**. The following are the different capping configurations supported. - Total Points capping: Limit the maximum amount of points allocated to a customer across all actions inside a set and all its subsets. This is applicable for all sets of the TransactionAdd customer activity. **Note:** When a transaction-level points cap (for example, 500 points) is reached, the system continues to calculate the source values for all tenders and line items in the transaction. However, for any entries that exceed the cap, the points awarded are set to zero. These zero-point entries are filtered out from reports and the user interface. As a result, the Earn Eligible Amount shown in reports or UI may differ from the total tender value, because only entries with non-zero points are displayed. To limit total points per customer for a condition in the TransactionAdd customer activity, do the following. - On Workflow, select TransactionAdd customer activity. Click +Add capping. ![](https://files.readme.io/d9ac5e4-earn1.png "earn1.png") - In Add capping page, click Total points. ![](https://files.readme.io/ee592fc-earn2.png "earn2.png") - In Total points, set the limit per customer. ![](https://files.readme.io/07282ab-earn3.png "earn3.png") - Click Save. 2. Source value capping Set a limit on the value based on which points are calculated and awarded to customers. For example, if there is x% discount on bill amount and source value is set as 5000, the customer receives x% on bill amount or x% on 5000 as points (whichever is lower). This is applicable for Set1 and its subsets of the TransactionAdd customer activity. To limit points per customer for a condition in the TransactionAdd customer activity. - On Workflow, select TransactionAdd customer activity. Click +Add capping. ![](https://files.readme.io/e32668c-earn4.png "earn4.png") - In Add capping page, click Source value. ![](https://files.readme.io/c0dc7c8-earn5.png "earn5.png") - In Source value, set the limit per customer. ![](https://files.readme.io/2d4f92a-earn6.png "earn6.png") - Click Save. Sum of tender amounts This option lets you limit points based on eligible payment methods. For example, issue points for the payments through ABC credit card up to 10000 of the cumulative transaction amount (from the configured time). ![](https://files.readme.io/67cd033-earn7.png "earn7.png") ![](https://files.readme.io/68888bf-earn8.png "earn8.png") ![](https://files.readme.io/1755562-earn9.png "earn9.png") This is applicable for Set1 and its sub-sets of the TransactionAdd customer activity. To limit points per customer on tracker values TransactionAdd customer activity. - On Workflow, select TransactionAdd customer activity. Click +Add capping. - In Add capping page, click Sum of tender amount. - In Sum of tender amount, enable/disable the toggle button to include/exclude the tender mode. Choose the tender mode from the drop-down options. - Click Save. Tracker source value This option is available for TrackerSet to limit issuing points on tracker value. For example, you can have a tracker condition to capture the quantity of petrol and limit points to issue per customer for up to 1000 liters of petrol. You can define multiple tracker conditions for a set. This is applicable only for the sub-sets of TrackerSet (TransactionAdd customer activity). ![](https://files.readme.io/29d0b0d-earnq1.png "earnq1.png") ![](https://files.readme.io/a0b0f34-earnq2.png "earnq2.png") ![](https://files.readme.io/91e63ed-earnq3.png "earnq3.png")

To limit points per customer on tracker values: On Workflow, select TransactionAdd customer activity. Select sub-set of TrackerSet, click +Add capping. In the Add capping page, click Tracker source. Choose the Tracker for which you want to set the limit. After selecting the tracker a text box appears. Enter the capping value in the text box. ## Expiry conditions To configure expiry conditions, do the following. 1. On Intouch, navigate to **Menu > Loyalty+ > Programs**. 2. In Programs, select the program you want to edit. 3. Select **Edit Program**. 4. Select **Reward currency**. 5. Click **Add Expiry Conditions**. In Name, enter the condition name. In Description, describe the condition. In Select module for this condition, select the module (Loyalty+/Engage+) for which the condition is applicable. In Expire Pts. Based on, select your preferred option to define the criteria for points expiry.

Option	Description
Event Date	Points expire on the configured date based on the last activity (transaction/registration) done by the customer. For example, if a customer buys a shirt on June 10, 2021, then the validity period for points for this customer can be set on any day after this transaction was made.
Rolling Expiry from Event Date	The current date of points expiry is reset to a new date based on the recent transaction date. That is, if a customer earns points before the expiry of existing points, the validity of all points will reset to the new points expiry date. For example, if a customer who made a transaction on June 10, 2021, has their point expiring on July 10, 2021, but they again made a transaction on July 7, 2021, then customers’ existing points along with the newly acquired point will have a new validity period, based on the transaction made on July 7, 2021. Note: Only the points that were issued via rolling strategies are extended.
Membership Event Date	Points expire automatically when the membership expires. This is usually used for membership-based loyalty. For example, if a customer has subscribed to a Platinum membership with a Digital store, and has his/her membership expiring in January 2022, then the points earned by this customer also expire in January 2022.
Customer's registration date	Points will expire on the registration date of the customer. This registration date refers to the date on which customer got enrolled or registered into the loyalty program. This will be same for all tiers.
Fixed date	Points will expire on a fixed date. This fixed date will be selected here, and every year points will expire on this date. This will be same for all tiers.
Transaction extended field	Points expire based on the date provided by the selected transaction-extended field. This capability supports time units (days, months). The date in the selected extended field will have the specified time unit added to it, and that final date becomes the expiry date of the points. If the calculated expiry date is in the past, the system sets the expiry to 7 days from the event processing date instead of failing the event. - _Note:_\* As this is a transaction-extended field where the value of the field will be coming via a transaction this is available only for the loyalty module when creating the expiry strategy.
Customer extended field	Points expire based on the date in the selected customer-extended field. This capability supports time units (days, months). The date in the selected extended field will have the specified time unit added to it, and that final date becomes the expiry date of the points. If the calculated expiry date is in the past, the system sets the expiry to 7 days from the event processing date instead of failing the event. - _Note:_\* As this customer-extended field is independent of the transaction, it is available in both the loyalty and engage modules when creating the expiry strategy.

Enable Same for all Tiers. In Time Unit, select your preferred option to set the validity period for points.

Option	Description
Days	Points expire after the configured number of days. For example, if a customer makes a transaction on July 1, 2021, and the Days for expiry is set as 10, points will expire on July 11, 2021.
Months	Points expire after the configured number of months. Points expire at the end of the last day of the calculated month, at 23:59:59 in the org's configured timezone — not on the exact same date the specified number of months later. For example, if a customer makes a transaction on July 10, 2021, and Months for expiry is set as 1, points expire on August 31, 2021 at 23:59:59 — not August 10, 2021.
Date	Points expire on the configured date. For example, if a customer makes a transaction on June 1, 2021, and the Date for expiry is set as August 10, 2021, then points will expire on this fixed date only.
Never	Points will never expire for the customer.

### **Note:** The points expiry job is a scheduled bulk process that runs in the early hours after the expiry date. As a result, the event timestamp visible in activity logs may show a time such as 04:51 rather than 23:59:59. This does not mean the points expired late — the system records the expiry date as the configured end-of-month date at 23:59:59. In Expire Pts. at the end of, enter the days or number of months for points to expire. For Date, you have to select a date on which points expire. For Never, there is no configuration required. Click Done. ## Create redeem conditions Redeem conditions allow you to configure points conversion ratio, eligibility criteria, and limit for points redemption. The eligibility criteria could be current points, lifetime points, or lifetime purchases. You can configure points redemption to do the following. - Set-point conversion ratio - Define the minimum points a customer should earn. - Limit the number of points redemption per transaction. - Redeem points in multiples of 'X'. ##### Example - Customers need at least 150-lifetime points to be eligible for redeeming points - Redemption is allowed only in multiples of 50, and - A maximum of 100 points can be redeemed per transaction - At least one redemption strategy should be created in a loyalty program. An error is shown if you run the loyalty program without any points redemption strategy. - For MLP, points redemption strategies created in a program cannot be used in other org programs, not even in the org's default program. ### Points consumption order When a customer redeems points, Capillary uses an **Expiry-First Out (EFO)** strategy — points closest to their expiry date are consumed first. This protects customers from losing points to expiry unnecessarily. For points sharing the same expiry date, the system falls back to **FIFO (First In, First Out)** — the oldest earned points are consumed first. **To configure redeem conditions, do the following** - 1. On **Intouch**, navigate to **Menu** > **Loyalty+** > **Programs**. 2. In **Programs**, select the program you want to edit. 3. Click **Edit Program** 4. Click **Points**. 5. In **How much is each point worth?**, specify the points conversion ratio (in terms of org's base currency). It is recommended to use a simple conversion ratio such as 0.1, 0.2, 0.5, 0.75,1.

6. Click **Add Redeem Conditions**.

7. In **Name**, enter the condition name. 8. In **Description**, describe the condition. 9. Enable **Same for all Tiers** The condition becomes relevant for all tiers. If disabled, the condition works only for the selected tier.

10. In **Minimum Points to redeem**, enter the minimum current points redeemable by customers. For example, if you set 50, a customer cannot redeem less than 50 points.

11. In the **Redemption limit**, enter the maximum current points redeemable by customers. For example, if you set 100, customers cannot redeem more than 100 points per transaction.

12. In the **Points balance required**, enter the minimum current points that a customer should have to allow redemption.

13. In **Allow redemption in multiples of**, enter the multiples in which the customer can redeem points. For example, if 10 is multiple, then the customer can redeem points only in multiples of 10 (10/20/30/40…).
**Note:** For the points awarded through the rewards catalog, if the conversion ratio results in a decimal point value, for example, 2,475 points × 0.005 ratio = 12.375 points, the Loyalty program must be configured to allow redemptions in multiples of 0.001. Without this setting, the reward issuance will fail. To configure this, set Allow redemption in multiples of to 0.001 in the Loyalty program's redeem conditions. See Points, Create redeem conditions for instructions.

14. In **Lifetime points required**, enter the total points that customers should earn to allow redemption.

15. In **Lifetime purchases required**, enter the total purchases that customers should make to allow redemption.

16. Click **Done**. ### Configure customer activity for points redemption condition Once you create a points redemption condition, you need to configure the PointsRedemption event on the Customer Activity page to define when to execute the redemption condition. 1. In **Customer Activity**, select Redeem points. 2. Create a ruleset, and inaction set the execute action as Redeem Points. 3. Click **Save & Continue**.

You can also configure notifications to be sent to the respective customer on the successful execution of the event. You can notify through SMS, email, or WeChat. ### Set points redemption threshold per customer You can limit the number of points to redeem per customer for the current day, last `x` days, calendar week, and calendar month. To limit points per customer, follow these steps. 1. In **Customer Activity**, select **Redeem points**. 2. In the Expression editor, define the condition using any of the following expressions. - Day limit: currentCustomer.pointsRedeemedToday - Weekly limit (Calendar week): currentCustomer.pointsRedeemedInCalendarWeek - Monthly Limit (Calendar month): currentCustomer.pointsRedeemedInCalendarMonth - In the last X days: currentCustomer.pointsRedeemedInPastDays(\) 3. Configure the actions to execute, click **Save & Continue**, and then Reconfigure the program. ## Create return conditions Return conditions allow an org to define conditions on the reissue of points after a customer returns a transaction or transaction line item. Points are returned in two ways as explained in the following. Reverse points Reissue Points Also see: Configure customer activity for points reversal Reverse points You can reverse the redeemed points, such that the points expiry for those points is restored to the original. There are some configurations for points reversal depending on the reference transaction number. Redemption without reference transaction number: If redemption is made without any transaction number then you can reverse points on the basis of redemption ID using the option Redemption reference captured in the bill. Points expiry for reversed points is restored to the original without altering the expiry date. Redemption with reference transaction number: If redemption is made with transaction number then you can reverse points on the basis of redemption ID using the option Redemption reference captured in the bill. Points expiry for reversed points is restored to the original without altering the expiry date. Prerequisites for points reversal support Enable Allow\_points\_redemption\_reversal config on EMF settings. Only the back-end team has access to this page. Please raise a ticket if you want this to enable. Enable V2 API as points reversal is supported only in V2.0. Enable Redemption reference captured in the bill on Points Return (Loyalty+)page. Reissue Points In a case where no transaction or redemption reference number is available, you can reissue points and set an expiry strategy. Hence, reissued points will have a new expiry date. To configure points return, follow these steps. On Intouch, navigate to Menu > Loyalty+ > Programs. In Programs, select the program you want to edit. Click Edit Program Click Points. Click Add Return Conditions. Enable Return Used Points. In Return used points based on, select any of the following options based on which points are returned. Points tender mode: To reissue redeemed points in form of currency relevant for the org. You need to set the expiry strategy for the reissued points in Select expiry strategy for reissued points. Redemption Reference in the Bill: To reverse redeemed points with the redemption reference number captured in the transaction. The expiry strategy will also be reversed to the original. Bill Number in Redemption API: When a customer returns a transaction for which certain points are redeemed, it is required to return those redeemed points. Hence, to reverse points, you need to configure the reference number to be considered for redemption. In Expiry condition for returned points., define how reissued points will expire for the chosen return method. Click Done. Configure customer activity for points reversal In Customer Activity, two actions are supported for points reversal - 1. Reverse points and 2. Send message. To configure events for points reversal, follow these steps. In Workflow, go to Customer Activity and click TransactionAdd. Select Redeemed points get reversed. In Condition, leave the Expression and Expression equals to default - true. No rules are applicable for points reversal. In Points redemption reversal action, leave Points Expiry to the default option. This will return the expiry of the reverse points to the original expiry. In Channels, set the message you want to send to customers for points reversal. For more details on channel configuration, see Communications. Click Save to save the changes. ### Return re-evaluation Return re-evaluation ensures that when a customer returns items, the points adjustment reflects the actual earn rules rather than a simple proportional deduction. This matters for loyalty programs that have [earning limits](https://docs.capillarytech.com/docs/advanced-capping). A pro-rata deduction would give the wrong result in these cases. For example, if a customer earns 500 bonus points for crossing a ₹5,000 spend threshold and returns an item that drops their total below ₹5,000, re-evaluation removes all 500 points — not just a fraction of them. This is default behaviour and no additional configuration or flag is required. Once you configure return conditions for your program steps above, return re-evaluation applies automatically to all return transactions. For [loyalty promotions](https://docs.capillarytech.com/docs/loyalty-promotions-introduction) you need to also define a `ReturnBill` ruleset on that promotion for its returns; without it, that promotion's returns just get a proportional deduction and a re-evaluation is not processed. When a return is processed, calculations are made on how many points the customer would have earned had they only purchased the remaining items. This uses the original purchase date, not the return date for the time reference. The difference between what was originally awarded and this recalculated amount is what gets deducted as part of the return. > **Note:** Return re-evaluation deducts the difference between originally earned points and the recalculated amount, regardless of whether the customer has already redeemed those points elsewhere. If the customer's available balance is lower than the deduction amount, this can result in a negative points balance. This applies even when no Return Condition/Strategy is configured for the program, since return re-evaluation runs by default. Gemini_Generated_Image_urdb70urdb70urdb

## Viewing conditions configured for points You can view the earn, expiry, redemption and return conditions that are configured for points earned through a loyalty program. You can also view and copy the configuration code for each condition. To view the conditions configured for points, follow these steps: 1. On Intouch, navigate to **Menu** > **Loyalty+** > **Programs**. 2. Select your program, then select the **Reward currency** tab. 3. Hover over the condition name to view the condition code. To copy a code to the clipboard, select the copy icon. These condition codes are used in the [Issue reward currency API](https://docs.capillarytech.com/reference/issue-reward-currency#/)

## Editing conditions configured for points You can edit the earn, expiry, redemption and return conditions that are configured for points earned through a loyalty program. To edit the conditions configured for points, follow these steps: 1. On Intouch, navigate to **Menu** > **Loyalty+** > **Programs**. 2. Select your program, then select the **Reward currency** tab. 3. Hover over the kebab menu (**⋮**) and select **Edit** to edit the configuration. ### Note You cannot edit the default configurations in a loyalty program. ## Advanced settings for points ### Points round off settings You can define the number of decimal points up to which points can be issued or withdrawn from a customer. This is applicable for [issued points](https://docs.capillarytech.com/docs/points), [returned points](https://docs.capillarytech.com/docs/points#create-return-conditions), [re-evaluated points](https://docs.capillarytech.com/docs/january-february-march23#re-evaluation-of-return-in-the-event-of-earn-capping), [delayed accrual points](https://docs.capillarytech.com/docs/points#configure-points-delayed-accrual), line-item allocation, issued and re-evaluated points on line items, [manual points adjustments](https://docs.capillarytech.com/reference/deduct-points-and-alternatecurrencies-from-user) and [points redemption](https://docs.capillarytech.com/reference/points-redemption). For example, 50.3458 points have to be issued to a customer. The following table highlights the points that will be issued based on the round off setting configured. The rounding strategy is round half-up (default). | Round Decimals value | 0 | 1 | 2 | 3 | | :------------------- | :- | :--- | :---- | :----- | | Points issued | 50 | 50.3 | 50.35 | 50.346 | To configure points round-of settings, follow these steps: 1. On **Intouch**, navigate to **Menu** > Loyalty+ > **Programs**. 2. In **Programs**, select the program for which you want to set the points round-off setting and click **Edit Program** > **Advanced settings**.

3. Navigate to the **Points** page. 4. Choose the decimal places using the drop-down list under **Round off decimal earnings by**. By default, the system stores the values up to 3 decimal places.

5. Navigate to the Points page. ### Reward currency rounding strategy You can define the strategy for rounding off reward currencies. Based on the number of decimals configured, the rounding is considered up to those decimal places. For example, if the round-off is set to two decimal places, the rounding would be for the nearest hundredths. The types of strategies for rounding are as follows: 1. **Ceiling**: Rounds numbers towards positive infinity. Positive numbers round-up, while negative numbers round down (towards zero). 2. **Floor**: Rounds numbers towards negative infinity. Positive numbers round down, while negative numbers round down. 3. **Round Half Up**: Rounds to the nearest value, rounding up when the next digit is five or more. If the decimal is 5 (midway), then it is rounded up. 4. **Round Half Down**: Rounds to the nearest value, rounding up when the next digit is five or more. If the decimal is 5 (midway), then it is rounded down. 5. **Round Half Even**: Rounds to the nearest value, rounding to the nearest even number when the next digit is exactly five. For example, 25.8751 points are to be allocated to a customer and the round-off is set to two decimal places, The following table highlights the value of points that will be issued based on the round off strategy: | Round Strategy | Ceiling | Floor | Half Up (Default) | Half Down | Half Even | | :------------------------ | :------ | :---- | :---------------- | :-------- | :-------- | | Points round-up (25.8751) | 25.88 | 25.87 | 25.88 | 25.87 | 25.88 | To configure the points round-of strategy, follow these steps: 1. On **Intouch**, navigate to **Menu** > Loyalty+ > **Programs**. 2. In **Programs**, select the program for which you want to set the points round-off setting and click **Edit Program** > **Advanced settings**.

3. Navigate to the **Points** page. 4. Choose the points rounding strategy using the drop-down list under **Currency rounding strategy for decimal conversion**. that appears on the earn conditions. By default, the system rounds half up.

5. Select **Done** to save the changes. ### Rolling points expiry when no points are issued Points rolling expiry is a feature that resets or extends the expiry date of loyalty points when a customer performs certain actions, such as making a transaction or redeeming points. Refer to the documentation for more information on [points rolling expiry](https://docs.capillarytech.com/docs/points-rolling-expiry). By default, the rolling expiry process only considers points with a value greater than zero. If a customer performs a rolling event and receives no points for it, the system will not consider the rolling event even if it is valid, and the expiry window is not extended. To consider rolling when no points are earned, you can enable **Roll the expiry even when 0 points are given** to ensure that it is considered for extending the expiry. For example: A retail loyalty program configures points earned to expire after 12 months unless they engage in a rolling event to extend the expiry. A customer earns 100 points in January 2024, with a 12-month rolling expiry (set to expire in January 2025). Now, in December 2024, the customer purchases as part of a special promotion. However, this promotion does not award any new points (zero points are awarded). **When disabled:** - Since the promotion awards zero points, it is ignored by the rolling expiry. - The customer’s **100 points still expire in January 2025**. **When enabled:** - The system recognizes the **zero-point award purchase as a valid rolling event**. - The **expiry date of the 100 points is extended to December 2025**.

To enable rolling points expiry when no points are issued, follow these steps: 1. On Intouch, navigate to **Menu** > **Loyalty+** > **Programs**. 2. Select your program, then choose **Edit Program** > **Advanced settings**.

3. Navigate to the **Points** page. 4. Turn on the **Roll expiry even when 0 points are given** toggle.

5. Select **Done** to save the changes. ## FAQs

Can I limit the number of times my customer can earn points?

You can limit the number of points a customer can earn in the points earning condition. However, there is no option to limit the number of times the points are issued for a customer.

Why does the Earn Eligible Amount sometimes not match the total tender value in reports or the UI?

When a transaction-level points cap is reached, the system continues to calculate source values for all tenders and line items. However, any entries that exceed the cap are assigned zero points. These zero-point entries are filtered out from reports and the user interface. As a result, the Earn Eligible Amount shown may be less than the total tender value, because only entries with non-zero points are displayed.

What is the use of proportion and max point allocation?

Use Proportion lets you issue points based on the line item amount. The Maximum points allocation is to set a threshold value for the number of points a customer can earn.

How is the Transaction Points Allocation action different from Allocate Points?

**Transactional Points** - Points you earn as per the configured ruleset for making a transaction. **Allocate Points** - Points you can assign on the transaction amount and custom field values based on the configured ruleset.