Introduction

• Loyalty members earn points on every purchase they make, which can then be redeemed for a reward to encourage repeat purchases.
• Loyalty points are adjusted manually using Point Adjustment Categories. After performing certain actions, the points which are earned by the customer are viewed in terms of Lifetime Points, Earned Points, Redeemed Points, Returned Points, Debit Points, Expired Points, and Current Balance.
• The main purpose of Points Adjustment is to avail points benefits to the member if not assigned by the administrator.

Navigation : Products > Select Your Template > Select Template

Select the appropriate template, and click the View icon from the Action tab, as shown in the following image.

    Navigation: QA_temp_ 1 > Additional Loyalty Settings

Navigation: Additional Loyalty Settings > Point Adjustment Categories

Capabilities

This feature allows the administrator to make tier benefits available by performing actions such as purchase, etc.

Configuration Settings

1.Points Adjustment Categories

List By Points Reports / Moderation Reports : The user's account will be credited or debited by the manual points given in this field, depending on how the user points are manually adjusted. As an administrator, select the drop-down list to view the required report details.

Add New Reason: Administrator can add new reasons for assigning points to the member on the Annex Cloud site as per the requirement.

Add New Reason

After clicking on Add New Reason:

Reason Category: Select the category from the drop-down list as Points Report or Moderation Report.

Reason: Enter the reason which is to be added to the list and click on the Save button.

The added reason is viewed as shown in the above image. The newly added reason can be viewed in Reports > Points > Points Report > Give Points.

2.Points Deduction

Points Deduction Behavior: Points Deduction Behavior type can be selected as Do Not Allow Negative Points, Allow Negative Points, and Set Balance to Zero.

1. Do Not Allow Negative Points: This selection will not allow the member to deduct more points than are available in the account.
2. Allow Negative Points: Allows the member to deduct more points than are available. For example, if a member has 50 available points but wants to deduct 100 points from the account, the administrator can set a balance of -50 points for the member.
3. Set Balance to Zero: Allows the administrator to set balance points to zero. For example, if a member has 50 available points but wants to deduct 100 points from the account, the administrator can set a balance of zero rather than a negative quantity.

Issuance API: Supporting Multiple Points Deduction Configurations

The Issuance API provides flexibility in handling point deductions based on configured site settings. It supports three distinct options that govern how points are deducted when processing returns:

1. Do Not Allow Negative Points
   With this setting enabled, the API verifies the member’s available points balance before processing a return. If the member does not have enough points to cover the return amount, the transaction is rejected, ensuring that the points balance never goes below zero.
   Example:
   A member has 250 points available and attempts to return products that would require 400 points to be debited. Since the available points are insufficient, the API will reject the transaction and return an error message.
2. Allow Negative Points
   This configuration permits the return transaction to proceed regardless of the member’s available points balance. If the points required for the return exceed the member’s balance, the API allows the transaction and moves the balance into the negative.
   Example:
   A member has 300 points but returns products requiring 600 points. The return is approved, and their balance is updated to -300 points.
3. Set Balance to Zero
   Under this setting, the API deducts as many points as the member has available. If the return requires more points than the available balance, the transaction proceeds, but the member’s balance is simply reduced to zero instead of going negative.
   Example:
   A member with 150 points returns products requiring 500 points. The return is processed, and their new balance is set to 0.

Points Deduction Considerations

The API determines the appropriate behavior based on the points deduction configuration set in the site’s admin settings. This validation applies to both Purchase and Non-Purchase Actions.

When processing returns, the API should:

• Validate the member’s available points against the requested deduction.
• Return a meaningful validation message based on the outcome.
• Align the behavior with the configured points deduction settings, ensuring consistency across all transactions.

Additionally, for clients utilizing the advanced Hierarchy Management Group functionality, the system should check the group’s available points instead of individual balances if the settings indicate that all points belong to the group.

Use Case 1: Individual Member Return (Do Not Allow Negative Points)

Scenario:

• Points deduction setting: Do not allow negative points
• A member has 600 available points.
• They attempt to return an order valued at 1,200 points.
• Since they do not have enough points, the return request is denied.

Use Case 2: Group-Based Points Deduction

Scenario:

• Points deduction setting: Do not allow negative points
• Group B is configured so that members do not hold individual balances; all points are pooled at the group level.
• The group has 700 available points.
• A member of Group B attempts to return an order worth 1,500 points.
• Since the group’s available points are insufficient, the transaction is denied.

By ensuring that the Issuance API aligns with configured deduction settings, businesses can maintain control over how points are deducted while providing a seamless experience for members and groups alike.