Customer Loyalty

Need provision to store the reward expiry date provided by the client.

• The reward Expiry code flag will be used to set the expiration date to the codes from the codes uploaded on the Annex Cloud system.
• This expiration can have two types of expiration—Rolling Expiration and Calendar Expiration.
• It provides the ability to extend/update the reward code expiration dates if the code is not used also provides the ability to set the reward code expiration alert for the users.
• It provides the ability to set the reward code expiration alert for the client if the reward codes are not claimed yet and Validate the reward code at the time of redemption, if that code is claimed by the user or If the code is already redeemed or If the code is expired.

Rewards based on segment

• Rewards can now be provided to a specific set of users. A reward can be chosen to be provided for segments. Only the users belonging to the selected segment will be able to claim the reward.
• If a customer is part of the specified segment, then only eligible for that reward. This is the optional setting. If the Reward Eligibility Threshold type is selected, then the reward is visible to everyone.
• Navigation to set up the segment:
•  Products > Rewards > General Settings > Reward Eligibility Threshold
• ADR has the ‘Reward Eligibility Threshold’, functionality that handles the visibility of the reward on the loyalty dashboard and eligibility of the reward in the API.
  
• This reward will be visible on the loyalty dashboard only to the users belonging to the gold tier OR 2 Points Metric OR Product Purchase.

Multi-level earning rule

• It provides the ability to award points for purchases made by a loyalty member to other members influencing/enabling the sales. With the help of Add new earn rule we can add the user as Primary Buyer or as a Secondary Purchase influencer.
• By enabling the Secondary Purchase Influencer button the user will be added as Secondary Purchase Influencer and the user can get some points.
  

Secondary key in Advance purchase and order settings

This feature allows one to pass the secondaryKey parameter under the orderDetail array in the Order API.
When switched ON, productId and secondaryKey together will act as a composite key and in case of any product return we can differentiate between same product id.

Points adjustment and deduction

Points deduction allows us to deduct points based on 3 types of Points Deduction Behavior like:

• Do not allow negative points
• Allow negative points
• Set balance to Zero
  

Rewards section settings

Reward Denomination allows denominating points for a particular user. Based on the value of points the reward denominate. The denomination value should be multiple of the value given.

Advanced transaction types

This feature enables the addition of advanced transaction types. Under which we can define transaction types, ratios, and actions.

While adding new transaction type we have to define Transaction Type ,ratio and 2 type of points expiration like Rolling and Calendar.

Managing the Partial Returns for Orders Paid with Loyalty Points and Tender (Cash/Card)

• Ability to turn off the redemption credit to the user if the order is partially or fully canceled
  or returned. The redemption credit will happen manually using the Points API with Action
  ID 154.
• Order PATCH Method (updatedDiscountAmount)

If the discount is applied to the order, we update the discount amount at the time of partial return or cancellation. The point calculations will be based on the remaining order item * price - updated discount amount.

• Hold Points

The hold days will start counting from when the last item from the order is shipped. The release date will not display until the last item from the order is shipped.

Calculation method information (currency/quantity) in API Purchase Ratio

To override the buy points type we put up in the Product Catalog, we added the field to the purchase action

Member summary card

Added an option to search members based on their opt-in, opt-out dates

Enhanced dashboard summary export

• Unique member count will be shown separately as per the order status
• Members count with Full Return, Members count with Partial Return, Members count with Partial Cancel and Members count with Full Cancel

Campaign reporting

• Differentiate between Base [Purchase] Points and Campaign points
• Display percentage of participation as a total number of users that have participated in in the Campaign / Total number of users that the campaign was eligible to participate.

Provision to configure double points campaign for action id 100

• In the Campaign milestone under action and action series we have different types of custom actions and standard actions.
• For custom actions we have the options to select bonus as points ,ratio or both but in case of standard actions we have only points or ratio option. Previously we have ratio option only for Purchase action.
  

Manual spend adjustment

• Most of our clients have Tiers based on spending. This enhancement will enable our clients to adjust their customers' wrongly logged Spend manually which will further help the customers reach the right Tier and get the right benefits.
• An admin or Customer representative adjusts the spend for such customers and based on modification the purchase points are awarded. To achieve this, Annex Cloud created a standard action called “Manual Points Adjustment” and action id 164. 

Navigation: Products > Action Rules > Edit > Select Purchase Action name

Hide Actions under POST API

• To provide functionality that allows the admin user to hide activities in the POST/actions response.
• When these actions are also sent in the response, the mobile team will no longer have to deal with pagination. This will aid clients who only utilize our APIs in hiding such operations from their dashboards.

Navigation: Products > Action Rules > Edit > UI Settings

Points expiry in next 30 days

Created a new API to show the user points with expiration dates. One endpoint shows all the data, and another endpoint allows filtering data within a selected date range.

Points should expire after the end of calendar year + 2 years

• We can set the point expiration date from 1 to 10 calendar years.
• In the points expiration option, the Week, Month, and Year (1 Year) options are available. Points expiration options are available in Action Rules, Action Series, Ties, and Campaigns.
  

Reward Eligibility Threshold: Fixed and Recurring

Rewards can now have a threshold. The users will have to achieve the threshold set to be eligible for the reward. The threshold can be fixed or recurring.

A fixed threshold needs to be achieved once whereas a recurring threshold can be attained multiple times to increase the claim limit of the reward.

Fixed limit:

We have 3 options under fixed limit:

1. Lifetime Points
2. Purchase Amount
3. Segment
   

Recurring limit:

We have added a new type 'Recurring Eligibility' and ‘Earned Points in Calendar Year’ as a threshold option under it.

Added profanity/word filter functionality in Incentive engine product setting

• This functionality will predominantly be used as a profanity filter to ensure codes with questionable meaning are not issued to members.
• The new “Exclude Words” feature helps to exclude profane words being used in coupons. You have to create a list of profane or unwanted words. This feature is provided in the “Additional settings” of the Incentive Engine.
• To create a new list of exclude words, click on the “Exclude Words” button, which is displayed in the Incentive Engine window under Additional Settings.
  

Looking Ahead

Annex hosted Loyalty Micro-Site

Customers have requested that Annex Cloud host a lightweight Loyalty program experience for their end consumers. The idea is that Annex would provide a framework that would allow our customers or AC internal CIs to configure landing page to promote the program, account registration for members, member profile management, and loyalty dashboard.

Integration product management

1. Loyalty certification for SAP/Hybris Commerce Cloud
2. Enhancement of order level use cases in SAP Cloud for customers
3. Integration security and code clean as mentioned in the technical code audit
4. Migration of SAP commerce cloud to their latest version 2105
5. MSD365 marketing application enhancements
   • Implementing the filtering criteria to only sync updated records from MSD365 Marketing
   • Implemented the bulk / batch import of contacts from Annex Cloud to MSD365 marketing to improve the efficiency
   • Enhanced Application to include Account level mapping with the contacts
6. Netsuite: Submission of BFN 2022
7.  Carlton One(GRS):Integration of loyalty program
8.  Responsys: ESP integration with Responsys
9.  Bloomreach: User Sync implementation
10.  Attentive Enhancement: Integration of Webhook for saving the status

Refer a friend(RAF)

1. Friend Link to Reward Code
   • Added a Flag which will skip the email form to unlock the Coupon Code.
   • According to the client's request, the user wishes to claim the reward code without having to provide the friend's email address.
   • The promo code is displayed by the site administrator without unlocking the page.
   • AC has introduced this feature by adding the flag in the Super Admin. This feature will work when the Super Admin flag is enabled. The flag is available in the EDIT section.

Flag Name: Enable Landing Coupon Code Without Popup

Ratings & review (R&R)

No product development.

Looking Ahead

Ability for end-user to update star rating

• There are times when an end-user is unhappy with something and leaves a poor review and low start count.
• After a satisfactory resolution, the client would like the end-user to be able to adjust the star count to reflect their new level of satisfaction. Please consider not just the functionality of being able to adjust the stars, but the user experience.
• There will probably be something inside the Admin portal where the client is able to re-retrigger an email for the same purchase and the same product, where a user can change the rating.
• This may also be a good time to review the Commenting functionality within a posted review and if we acknowledge on the front end if the star rating has been changed/updated.

2. Trigger edit review email to update the ratings

• The end-user should be able to edit the ratings provided. In order to achieve this -
• The admin user should be able to set up the edit review email
• The admin user should be able to trigger an edit rating email
• The admin user should be able to view all the reviews provided by the user

Visual commerce (VC)

No product development.

Incentive Engine

No product development.