LOYALTY RELEASE 26.9.0

 

Offers: Bonus Offers for POS API Programs

Available to all CLIENTS

Background

Loyalty marketers are looking for more ways to motivate Member behavior beyond traditional discounts. Whether the goal is to encourage purchases in priority categories, increase spend, or reward specific products and activities, brands need greater flexibility to create incentives that align with their loyalty strategy.

For programs using the POS API, Bonus Offers expand the ways marketers can reward members and create more engaging earning experiences based on how Members shop and interact with the program.

Solution

Loyalty supports a new Bonus Offer type for programs using the Loyalty POS API, giving marketers three flexible ways to reward qualifying member activity:

• Fixed Metric Amount: Award a defined bonus amount when Offer criteria are met.

• Multiplier: Multiply the amount Members earn for qualifying activity.

• Percentage: Increase earned value by a specified percentage.

Bonus Offers can be configured using criteria such as categories, PLU/SKU values, Lookups, and spending thresholds, giving marketers greater control over the behaviors and purchases they want to incentivize.

The experience is built directly into the existing Offer builder, using familiar controls for qualification rules, Offer timing, response and usage periods, and advanced settings alongside new bonus-specific configuration options. Bonus Offers are also supported throughout the Offer activity and event lifecycle, helping ensure a consistent experience from setup through member engagement.

Key Benefits:

• Expand incentive strategy: Bonus Offers give brands a new way to reward Member behavior beyond discounts.

• Match the reward to the campaign goal: Fixed, Multiplier, and Percentage options let marketers choose the structure that fits the incentive.

• Target the behaviors that matter most: Categories, PLU/SKU values, Lookups, and spending thresholds help brands shape Offers around the activity they want to drive.

• Launch within a familiar workflow: Built-in Offer builder controls reduce setup friction for marketers and administrators.

• Create more engaging earning experiences: Flexible bonus structures help brands align rewards with how Members shop and interact.

For more information, see Configure an Offer - Bonus.

 

Offers: Flexible Bundle Sizes for Coupon Offer Bundle Deals

Available to all CLIENTS

Background

Brands need Coupon-type Offer bundle structures that better reflect the way they sell products in the real world, including meal deals, multi-item Offers, and quantity-based promotions that are not limited to a fixed pair of items.

Solution

Coupon Offer Bundle Deals now support variable bundle sizes through an Items per Bundle setting, which allows defining larger or more flexible bundle structures instead of being locked into a single fixed size. This setting opens the door to Offers such as 3-item combos, 5-for-$3 deals, and other multi-item bundle patterns while preserving support for existing configurations. The update also renames Quantity Limit to Redemption Limit across discount types, giving teams a clearer and more consistent way to manage Offer usage as they build and maintain promotions.

Key Benefits:

• Expand bundle design options: Variable bundle sizes let brands build promotions beyond fixed two-item deals.

• Support real-world promotions: Multi-item bundles make it easier to create combo meals, 3-item sets, and 5-for-$3 Offers.

• Simplify Offer management: Clearer redemption terminology helps teams understand and maintain bundle settings.

• Preserve existing configurations: Current bundle deal setups continue to work without disruption.

• Match Offer structure to merchandising strategy: Brands can align bundle mechanics more closely with how they sell products.

For more information, see Configure an Offer - Coupon.

 

Offers: Certificate Display Controls in Coupon Offer Details

Available to all CLIENTS

Background

Brands that issue Coupon-type Offer Certificates need the main Offer experience to make certificate settings easier to find and the display text easier to manage. Without that clarity, it is harder to keep certificate output consistent across activities and API responses.

Solution

The Certificates on Responses setting now appears in the main Coupon Offer Details area – moved from the Show More expander. Also, the Display Text field is restored so teams can control how certificate codes are presented. This design makes certificate configuration in Coupon Offers easier to manage during setup and gives connected experiences a more predictable value to render when certificates appear in activities or response payloads. The result is a cleaner setup flow and more consistent downstream display behavior.

Key Benefits:

• Make certificate settings easier to manage: Moving the control into Offer Details keeps setup more discoverable.

• Restore display control: The Display Text field gives teams a clearer way to define how certificate values appear to members.

• Support consistent downstream output: Connected experiences can rely on more predictable certificate presentation.

• Reduce setup friction: Certificate-based offers are easier to configure and maintain.

For more information, see Configure an Offer - Coupon.

 

Admin and Program: Metric Expiration Program Setting Configuration Visibility

Available to all CLIENTS

Background

Program administrators need to confirm Metric expiration settings even when a setting is locked or not directly editable. When that visibility is missing, it can slow down configuration review and make the current state harder to understand.

Solution

Loyalty now shows the current Metric expiration values in the Program Setting and allows the modal to open even when the setting is read-only. This design gives administrators a clearer view of the active configuration without exposing underlying environment-state details in the interface. The result is a more transparent admin experience that still respects existing edit restrictions.

Key Benefits:

• Improve configuration visibility: Current Metric expiration values are easier for administrators to review in Program Settings.

• Support locked settings more clearly: Read-only access to the modal helps teams confirm the active configuration.

• Reduce uncertainty during setup: More visible settings make it easier to understand what is currently in effect.

For more information, see the Point Expiration User Guide.

 

Metrics and Tiers: Extended Windows for Pending Metrics

Available to all CLIENTS

Background

Some programs need more time before pending Metric value is activated so their loyalty rules can better align with return policies and other post-purchase adjustments. When the pending window is too short, teams may be forced into workarounds that do not reflect how the program handles returns or reversals.

Solution

Pending Metric expiration settings now support pending periods from 1 to 90 days instead of the previous 1 to 30 day range. This change gives brands more flexibility to align Metric timing with return policies, review windows, and other program rules that require additional time before a Metric is activated or earned. The broader range keeps the existing expiration workflow intact while making the timing better fit for program operations.

Key Benefits:

• Align Metric timing with return policies: Brands can keep pending windows open long enough to reflect their actual post-purchase rules.

• Support longer review periods: Programs that need more time before activating a Metric now have that flexibility.

• Reduce timing workarounds: Teams can configure the behavior they need without forcing a separate process.

• Keep expiration behavior consistent: The existing Metric expiration workflow still applies, with more flexible timing control.

For more information, see the Pending Metrics Setup Guide.

 

Earn Rules: Clearer Earn Rule Summaries

Available to all CLIENTS

Background

Earn Rules need to be easy to understand for marketers and program managers who are managing loyalty strategy, not reading script logic. When conditions and calculations are shown as technical expressions, it can be difficult to tell what a rule will actually do during setup or review. A clearer summary helps teams validate and manage rule behavior faster and with more confidence.

Solution

Loyalty now supports concise, human-readable summaries for Earn Rule conditions and calculations in the listing view. Marketers can quickly scan what each rule is doing without opening the full edit flow and reading through scripting logic, while the underlying Groovy or script logic remains available when deeper review is needed. If the system cannot generate a safe summary, Loyalty shows a clear fallback message instead of exposing raw technical output.

Key Benefits:

• Faster rule review: Marketers and program managers can understand rule intent at a glance.

• Better setup confidence: Business-friendly summaries make it easier to confirm the rule matches the intended earn behavior before launch.

• Less technical friction: The list view replaces script-heavy expressions with readable language.

• Safer fallback behavior: When a summary cannot be generated, the UI shows a clear message instead of technical output.

For more information, see View an Earn Rule.

 

Earn Rules: Unified Tabbed Earn Rule Editor

Available to all CLIENTS

Background

Earn Rules were previously edited across multiple sections and inline modals, which made the experience feel fragmented. For teams managing many rules, that meant more navigation, more context switching, and more room for inconsistent configuration.

Solution

Loyalty now supports editing Earn Rules in a single unified tabbed modal, giving brands one guided flow for Basic Information, Conditions & Expressions, Calculation & Settings, and Status & Effectivity, while keeping the underlying rule behavior unchanged. After a rule is created or cloned, the relevant group expands automatically; the new rule moves to the top, and it briefly highlights so teams can find it quickly.

For more information, see Configure Earn Rule Properties.

 

Triggered Actions and Activity Processing: Clearer Triggered Action Summaries

Available to all CLIENTS

Background

As Triggered Action rules become more complex, program teams need a faster way to understand what a rule is doing without opening the full editor every time and reading through groovy heavy scripting. That becomes especially valuable when teams are reviewing larger automation sets and need to scan behavior quickly.

Solution

Loyalty now shows readable summaries of Triggered Action conditions and actions directly in the listing view, making the list view easier to scan while keeping the full rule logic available in Edit. Summaries are regenerated when a rule is saved, so the listing stays current as teams update rules. If summary generation fails, the experience supports retrying the summary and falls back to a clear message that directs users back to Edit for complete logic. This gives teams a faster overview without losing access to the original rule structure.

Key Benefits:

• Scan rules faster: Readable summaries make it easier for teams to understand Triggered Actions at a glance.

• Review automation with less friction: Listing-level summaries help administrators assess behavior without opening every rule.

• Keep the full logic available: The edit experience still preserves the underlying rule details when deeper changes are needed.

• Reduce review overhead: Faster rule comprehension helps teams manage larger automation sets more efficiently.

For more information, see View a Triggered Action.

 

API Connectors and Integrations: Named Punch IDs in Punch Card API Responses

Available to all CLIENTS

Background

Brands using Named Punches need those identifiers returned consistently in API responses so connected experiences can identify the correct punch detail without extra mapping or custom handling.

Solution

The GET /api/punchcards response now includes the Named Punch ID in punch_details. This change makes the API output more useful for connected experiences, front-end displays, and integrations that need to render or match named punches accurately. The change keeps the response more descriptive and reduces ambiguity when multiple punch definitions are in use.

Key Benefits:

• Improve API clarity: Named Punch IDs in punch_details make Punch Card responses easier to interpret.

• Support connected experiences: Downstream systems can identify the right punch detail more accurately.

• Reduce custom mapping work: More descriptive response data lowers integration effort.

• Render punches more consistently: Front-end and API consumers can match Named Punches with less ambiguity.

 

Punch Cards: Punch Card Lifecycle Continuation

Available to all CLIENTS

Background

Brands often want Punch Card experiences that continue past a completed or expired card, but they also need direct control over when that behavior is allowed. This is especially important when Punch Card campaigns are tied to response limits and planned Member journeys, where the continuation rules need to be both configurable and reliable at runtime.

Solution

Loyalty now supports Punch Card continuation, so program administrators can independently control whether a Member may receive a new Punch Card after completion and after expiration. The setup makes those lifecycle rules explicit inside the configuration experience and keeps existing Punch Cards unchanged unless the continuation setting is enabled. Once configured, Loyalty processes continuation on the next qualifying activity after completion or expiration, while respecting response limits and handling simultaneous qualifying events safely to help prevent duplicate issuance. This gives brands a consistent way to define the rule and rely on the platform to apply it correctly.

Key Benefits:

• Gives brands more control over Punch Card campaigns: Teams can decide when continuation should apply after completion or expiration.

• Supports more flexible lifecycle behavior: Configuration and runtime processing work together to handle both setup and execution consistently.

• Helps protect campaign limits: Response controls still cap the total number of Punch Cards issued.

• Reduces manual intervention: The platform applies continuation automatically once it is enabled.

• Keeps the Member experience predictable: Continuation behavior stays consistent even when qualifying activity happens close together.

For more information, see Getting Started with Punch Cards.

 

Member Profiles and Data: External Segments Available in Loyalty Objects

Available to all CLIENTS

Background

For brands that manage Segments outside of the Loyalty product and create an External Segment in Loyalty, there was previously no way to use those External Segments directly inside Loyalty Objects such as Offers, Rewards, Punch Cards, and any other object that supports Segment-based eligibility. When External Segments could not be used in these workflows, teams had to create extra steps or duplicate audience logic to activate the same audience across the program.

Solution

External Segments can now be used directly in Loyalty Objects wherever Segment-based eligibility is supported. This design allows brands to apply an External Segment inside Offers, Rewards, Punch Cards, and any other object that accepts Segment targeting, without rebuilding the same audience in another format. The enhancement extends where External Segments can be used across the platform while keeping the existing Segment type and targeting model intact.

Key Benefits:

• Extend existing Segment logic into Loyalty Objects: Brands can use the External Segments they already manage in more parts of the platform.

• Reduce duplicate audience setup: Teams no longer need to recreate the same audience logic for each object.

• Support more activation workflows: Offers, Rewards, Punch Cards, and other eligible objects can now use External Segments for eligibility.

• Keep targeting consistent across the program: Brands can apply the same audience source across more loyalty experiences.

• Simplify campaign execution: Program teams can activate the same Segment more efficiently across multiple objects.

For more information, see Getting Started with Segments.

 

Member Profiles and Data: Upcoming Expiration Details by Metric

Available to all CLIENTS

Background

Brands need Metric expiration information that is easy to interpret at a glance, especially in Member Profile and CSR-facing views. In the current experience, the next expiration watermark can appear without clearly showing which Metric it belongs to, and it can also surface entries that would expire zero points. That design makes it harder for teams to read the balance context quickly and explain what Members should expect.

Solution

Loyalty now supports a clearer upcoming expiration display that identifies the Metric tied to the next expiration, excludes zero-point expirations, and shows the amount scheduled to expire. This design gives brands and customer-facing teams a more complete view of the next balance change directly in the Member Profile and CSR metrics experience.

Key Benefits:

• Clarify balance context: Showing the Metric name helps teams understand exactly which points balance is expiring.

• Reduce noise in the profile view: Filtering out zero-point expirations keeps the expiration display focused on meaningful activity.

• Set clearer expectations: Surfacing the expiring amount alongside the date helps brands communicate upcoming balance changes with confidence.

• Improve service conversations: Customer-facing teams can answer expiration questions faster with more complete information in one place.

• Support more readable Member records: The updated presentation makes expiration details easier to scan in both Member and CSR workflows.

For more information, see either View Member Profile or View Member Details.

 

Platform Updates: Updated Phone Validation Support

Available to all CLIENTS

Background

Phone validation rules change over time, and brands need the platform to stay current so member contact data can be checked reliably across markets. When validation libraries lag behind, otherwise valid numbers can be rejected or handled inconsistently.

Solution

Loyalty updates its phone validation library to keep validation behavior current and more reliable across regions. That update helps maintain consistency when brands collect or validate Member phone numbers and reduces the chance of mismatches caused by outdated regional rules. The change supports more dependable member data validation without changing the overall experience for program teams.

Key Benefits:

• Keep validation behavior current: Updated phone validation helps brands rely on more up-to-date rules.

• Improve contact-data quality: More reliable validation supports cleaner Member sign-up flows and records across markets.

• Reduce validation mismatches: Updated library behavior helps avoid issues caused by outdated rules.

• Support global programs more consistently: Brands can validate Member phone numbers with greater confidence.

 

Resolved Issues

Bug Fixes

• Resolved a mismatch where the Segment count shown in the UI did not match the rows exported to CSV, giving teams a clearer and more reliable audience total.

• Resolved an issue where expiration-based Member events could miss the expected follow-up action, keeping Triggered Actions aligned with program rules.

• Resolved an issue where reprocessing a return could apply the returned amount more than once, helping keep Member balances accurate.

• Resolved a mismatch where the Offer List response count did not align with the downloaded import results, making Offer totals more consistent.

• Resolved an issue where some admin logging pages could fail to load or time out, so support teams can review activity more reliably.

• Resolved an issue where a Member record could fail to load in the CSR People view, improving lookup reliability for service teams.

• Resolved an issue where Member imports could allow duplicate mobile phone values in some cases, helping protect Member data accuracy.

• Resolved an issue where recurring exports could intermittently fail to connect to an SFTP destination, improving export reliability.

• Resolved an issue where Bonus Earn Rules could apply outside the intended Member Segment, keeping promotional rewards aligned to the right audience.

• Resolved an intermittent file import failure that could stop processing before completion, so import jobs finish more consistently.

• Resolved an issue where certain triggered email actions could fail after personalization settings changed, helping Loyalty Messages send as intended.

• Resolved an issue where creating a Place could return a server error when location details were invalid, making Place setup more dependable.

• Resolved an issue where reapplying a buy-one-get-one Offer to a closed transaction could fail when item matching was incomplete, keeping Offer recalculations stable.

• Resolved an issue that could block Member sign-in through OAuth, restoring access to the mobile login flow.

• Resolved an issue where Calculated Attribute processing could fail during daily sync, helping profile updates complete consistently.

• Resolved an issue where an Earn Rule could fail during Activity processing when a required Metric value was missing, helping Earn Rules run more reliably.

• Resolved an issue where some return requests could fail instead of completing, improving return processing reliability.

• Resolved an issue where scheduled Dashboard emails could send a placeholder CSV without warning, making report deliveries clearer for recipients.

• Resolved an issue where import error counts could differ between the UI and the downloaded file totals, so teams see matching results in both places.

• Resolved an issue where welcome Offer Triggered Actions could skip some Members during high-volume imports, helping Offers reach every eligible Member.

• Resolved an issue where Wallet Pass installs could be missing from Member activity history, so Wallet status stays accurate.

• Resolved an issue where Redemption activity could leave Member balances incorrect after redemption or cancellation, keeping points totals accurate.

• Resolved an issue where Scheduled Jobs using Segment-based eligibility could complete without processing qualifying Members, ensuring eligible Members are included when Scheduled Jobs run.

See Loyalty Upcoming Releases for the platform release schedule.

See System Maintenance for details on the next system maintenance window, per region.

The status page provides you with regular updates regarding the status of the Loyaltyplatform in the event of a major system incident in your region. In this article we’ll explain the information you will see and how to subscribe to the Loyalty notification system to receive regular updates on the platform status, which we highly recommend to all users.

See Platform Status for more details.