ES Loyalty 4.7.1-HF.A Release Notes
These release notes cover features introduced or completed since ES Loyalty 4.7.1.
What's in this release
- Realtime Redemption Lock (new feature)
- Fraud Plus Enhancements (enhancement)
- Automation of Annual Unredeemable Balance / Points Expiry Report (enhancement)
- Default Reporting Margin (enhancement)
- Fix for Incorrect Reporting License Assignment (bug fix)
- Fix for Missing Store Details in Multi-Brand Transactions (bug fix)
- Fix for New User Permissions Not Reflected for Single Sign-On Users (bug fix)
- Fix for Data Feed Failure Due to Empty Value Handling (bug fix)
- Fix for Missing Transactions in Promotion Reporting (bug fix)
- Fix for Unnecessary Data Queries for Disabled Feature (investigation — no fix required)
New features and enhancements
Realtime Redemption Lock
Account takeover and fraudulent redemptions cost loyalty programs millions annually, eroding member trust and complicating program liability management.
What it does
Redemption Lock gives agents and dashboard operators instant control to freeze all point redemptions for a member in real time, while allowing points to continue accruing normally from purchases and other earning activities.
How you benefit
Agents and dashboard operators gain self-service fraud prevention that reduces fraud-related losses and support costs without disrupting the earning experience that drives member engagement.
Key details
- Agents can enable or disable Redemption Lock for a member with a single toggle.
- Members receive an email notification when an agent enables or disables Redemption Lock on their account.
- The feature delivers improved security, member control, and operational efficiency for enterprise loyalty programs.
Fraud Plus Enhancements
Unusual patterns of Redemption Lock changes by console users can signal potential insider threats or compromised administrator accounts that put your entire loyalty program at risk.
What it does
This enhancement automatically monitors and logs when console users modify Redemption Lock settings beyond defined thresholds within specified time periods, then instantly triggers email alerts to program administrators.
How you benefit
You gain an early warning system that detects suspicious internal activity before it escalates, enabling rapid response to potential security breaches while maintaining a complete audit trail for compliance and investigation.
Key details
- Sends an email alert when a specified number of Redemption Lock edits are made via the console — either on a single member or across multiple members.
- Adds new detection rules that improve fraud coverage and case management.
- Works with existing fraud controls to deliver a complete fraud management solution.
- Gives fraud teams, customer service reps, and marketing managers clearer visibility into fraud patterns with flexible control over enforcement.
Automation of Annual Unredeemable Balance / Points Expiry Report
Accurate liability forecasting is critical for financial planning, yet manually tracking point expiry trends across millions of member accounts is time-consuming and error-prone — and errors can affect balance sheet accuracy.
What it does
This automated report breaks down total outstanding liability by months to expiry, based on account inactivity periods. It updates annually and preserves historical data for trend analysis.
How you benefit
Your finance team gains effortless visibility into expiry patterns and future liability projections, enabling more accurate financial forecasting and strategic decisions about program economics — without manual reporting overhead.
Key details
- Programs can now set different expiration rules for registered versus unregistered members (for example, a 30-day rule for unregistered members and a 2-year inactivity rule for registered members).
- The definition of member activity is now broader: beyond earning and redeeming points, the system recognizes profile updates, account status changes, partner linking, and card replacements as valid activity. This keeps engaged members active longer while identifying truly dormant accounts.
- Programs can trigger automatic account closure actions when inactivity thresholds are reached, including zeroing points, anonymizing profiles, and canceling cards.
- Built-in reporting tracks expiry by member type.
- The enhancement integrates with existing console controls and data flows.
Default Reporting Margin
Accurate profitability tracking and margin-based member segmentation can be difficult when detailed item-level cost data isn't available.
What it does
The system automatically assigns margin values to products using a smart hierarchy: it first checks transaction costs, then product costs, then applies category-based defaults to ensure complete profitability data across all purchases.
How you benefit
You gain full visibility into purchase profitability and can build margin-based audience segments without needing granular cost data for every SKU.
Key details
- Supports default margin assignment by product sub-category (for example, one rate for snacks, another for beverages).
- Applies the correct category default for accurate profitability analysis across all transactions, including historical purchases through data patching.
- Benefits marketing managers and analysts who need complete margin visibility without item-level cost data for every product.
- Integrates with existing targeting and reporting tools, making margin-based segmentation accessible for all programs.
Bug fixes
Fix for Incorrect Reporting License Assignment
Issue
A bug caused the system to automatically assign reporting licenses to all users upon login, even when they hadn't been granted reporting access permissions. When a large number of customer service agent accounts were created for console access without reporting permissions, the system incorrectly consumed reporting licenses for these users — exhausting the total license pool and blocking legitimate reporting users from accessing dashboards and analytics. The problem was particularly severe during periods of rapid user account creation, where license capacity could be consumed within days.
Fix
The system now checks for specific reporting permissions before claiming a license. Only users with view or manage reporting access receive a license upon login. Additionally, licenses are automatically released when users log out or after periods of inactivity, preventing licenses from being held unnecessarily.
Who benefits
- Administrators can create console accounts for support staff without worrying about exhausting reporting licenses.
- Marketing managers and analysts regain reliable access to dashboards and analytics tools.
- All users benefit from improved license availability across the organization.
Fix for Missing Store Details in Multi-Brand Transactions
Issue
A bug affected loyalty programs operating multiple retail brands under one program. When members made purchases at non-primary brands, critical transaction details — including store name, location, and staff information — weren't recorded. Transactions from the primary brand worked correctly. This created visibility problems for program managers, customer service teams, and fraud investigators.
Fix
The system now correctly identifies which brand processed each transaction and captures complete store information — store name, location, employee information, and brand — regardless of location or format.
Who benefits
- Program managers have complete reporting across all retail formats for accurate performance tracking.
- Customer service teams see full transaction context for better member support.
- Fraud teams gain the location and employee data needed to identify suspicious activity at non-primary brand stores.
Fix for New User Permissions Not Reflected for Single Sign-On Users
Issue
A bug prevented new user permissions from being recognized for users logging in through single sign-on (SSO) authentication. When new accounts were created or existing users were granted additional permissions, the changes weren't reflected in the console upon login. New users could only access help documentation, while existing users couldn't access newly granted features such as reporting, promotions, or member management — even when permissions had been properly assigned. The issue stemmed from a broken authentication component that failed to correctly process identity provider information during the login flow.
Fix
The system now correctly processes identity provider information during SSO authentication. User permissions are recognized upon login for both new users and existing users with newly granted access. Changes made by managers are immediately reflected when users log in.
Who benefits
- Program managers can grant access to new team members or expand permissions for existing users, knowing changes take effect immediately.
- Marketing managers, customer service teams, and analysts gain reliable access to their assigned tools — reporting dashboards, promotion management, member lookup, and more — as soon as permissions are granted.
Fix for Data Feed Failure Due to Empty Value Handling
Issue
A bug in the data warehouse feed caused failures when processing member account information. A change in the underlying data platform altered how blank or missing values were read during data import, causing the account data feed to break. This stopped critical member information — including registration dates, contact details, and point balances — from flowing into reporting and analytics systems. Analytics teams lost access to current member data, and business intelligence reports became outdated or incomplete until the feed was restored.
Fix
The system now properly processes blank fields without errors, allowing complete member account information to flow into the data warehouse on schedule. All account attributes — registration dates, balances, contact information, and activity timestamps — load correctly regardless of whether individual fields contain values.
Who benefits
- Analytics teams regain consistent access to current member data for reporting and analysis.
- Marketing managers can track registration activity, account growth, and member engagement without interruption.
- Business intelligence users have reliable data pipelines that support daily operations, campaign measurement, and strategic decisions.
Fix for Missing Transactions in Promotion Reporting
Issue
A bug in promotion reporting caused certain transaction rows to be excluded from performance reports. Transactions with adjustments or missing tier information weren't counted in promotion metrics, making reports for promotion completions, sales totals, margin calculations, and member participation incomplete and inaccurate. Marketing managers couldn't accurately assess which promotions were driving sales, analysts saw incomplete participation numbers, and finance teams received incorrect margin calculations.
Fix
The system now correctly handles transactions with adjustments or missing tier names, ensuring all transaction rows are included when calculating promotion performance. All promotion metrics — member participation, transaction counts, sales totals, margin calculations, and rewards issued — now reflect full promotional activity.
Who benefits
- Marketing managers have reliable data to measure campaign performance and ROI.
- Analysts can accurately track member participation.
- Finance teams receive correct margin calculations for confident budget allocation and future campaign planning.
Fix for Unnecessary Data Queries for Disabled Feature
Issue
A suspected bug appeared to cause the member scoring feature to continue running data queries even when the feature was disabled. This was flagged while investigating high data processing costs for a client who wasn't using the member scoring module.
Investigation outcome — no fix required
Upon investigation, the system was already working as expected. The configuration switch properly controls the member scoring feature: when disabled, the system returns an empty response without executing any data queries. No fix was needed.
What this means for you
Program operators can confidently disable unused features knowing the system respects those settings and avoids unnecessary processing costs. Configuration controls work correctly, allowing programs to optimize costs by enabling only the features they actively use.