Loyalty & Promotions

Card- based loyalty: Member Consent to Link Credit Card Token to Profile

What is it?
This new feature lets members give their approval (consent) to link their credit card token to their loyalty profile. Once linked, future transactions made with that card will automatically be recognized as theirs - bypassing the need for additional login steps like entering phone number or email.

How it works

• A new checkbox called "Allow card linking" is added to the member registration, profile update form, and a new consent preference in the member profile

   

  
   

• When members check this box, they agree to link their credit card(s) tokens to their loyalty profile.
   

  

• This consent is saved as a member preference and applies to all future cards used by that profile.
• Once enabled, transactions made with these cards will automatically link to the member’s profile.

Note: if a member doesn’t check the box, their card won’t be linked. 

Important details

• The card linking consent behaves similarly to other communication preferences like “Allow Email” or “Allow SMS”
• The consent field can be handled via APIs, so third-party apps or integrations can collect and update this preference too.

👉 For more details, check out the Knowledge Article.
 

Location group auto generation

What is it?

We’ve added a new “Generate” button in the Business Profile → Locations →  Location Groups section that makes it easy to create a location group for each individual location- automatically.

Why does it matter?

Previously, creating location groups for each location had to be done manually, which could be time-consuming and prone to errors. 
Now, with just one click, you can quickly create groups that are perfectly matched to each location, saving time and simplifying management.

How it works

• When users click the Generate button, a pop-up explains that one location group will be created per location.

• Users are asked to confirm whether to proceed or cancel.
• After confirmation, the system automatically creates a location group for every location.
• Each location group is named exactly like its location.
• Each group contains only the location it’s named after.
   

Important notes:

• The Generate button simplifies initial setup by automating group creation.
• You can still customize and edit groups after they are created.
• Be aware that deleting groups requires Access Groups to be enabled.

👉 For more details, check out the Knowledge Article.

Merge Flow: A New Way to Handle Duplicate Accounts

What is it?

We’ve significantly enhanced our Merge flow. When an updateMember request fails due to an existing member with the same identifier, the system now captures the event, allowing businesses to take action.

We’re introducing a new rule trigger: Member Already Exists, along with a new condition: Conflicting Identifier. With this rule, businesses can automatically prompt users to merge profiles when identifier conflicts are detected, streamlining data management and reducing duplicate accounts.

Why does it matter?

Until now, these situations would stop the customer journey - members were blocked, and staff had to manually step in.
This new flow reduces friction for members, gives merchants better control, and helps support teams track and resolve conflicts more easily.

What happens now?

• When a member tries to update his profile with an identifier that already exists in another account (for example, at a kiosk or online), the system detects it and logs a new action:Member Already Exists.
• This action can be used as a trigger in Hub rules, allowing you to:
  • Send the member a secure link to update their info (via Mention or direct link)
     
• The member is then redirected to update details from where they can review and update their information.
  If everything matches, the accounts are merged automatically after a quick verification (OTP).

👉 For more details, check out the Knowledge Article.

Additional enhancements:

• Legal age override support (BETA)
  • Businesses can now override the legal age restriction for members.
    Note: This feature is currently in BETA, and the UI support is expected to be released around September.
     

Bugs fixes:

• Better handling of null values in Member Merge
  • Fixed an issue where merging members could fail or display incorrect data if some fields were missing or empty.

Customer-Facing Tools

Multiple Branch IDs per Location 

We’ve added support for multiple branch IDs per location to handle cases where businesses use different systems (like POS and Online Ordering) that assign separate identifiers to the same physical site. This helps unify data, improve reporting, and simplify operations.

What is it?

Previously, each location had only one branch ID. When different systems used different IDs for the same place, data in dashboards and reports got split up, causing confusion and extra work.

Now, a location can have one main branch ID plus additional “sub” branch IDs linked to it. This means all data from different sources is grouped correctly under one location.

How it works

• Sub-branch IDs must be unique across the business to prevent reporting or syncing issues.
• The system prevents duplicate sub-branch IDs across different locations. If a sub-branch ID is already in use, trying to assign it elsewhere will trigger an error.

• The system handles location structure validations in the background, but it's important for teams to coordinate when making changes across multiple locations.

   

  

Challenges solved

• Inconsistent data: Different IDs for one location caused split reports and duplicated dashboard entries.
• POS migration issues: Switching POS systems meant creating new locations, breaking historical data.
• Billing discrepancies: A mismatch between branch IDs could cause incorrect billing.
   

👉 For more details, check out the Knowledge Article.

Hub 2.0 - Migrating Business Time Zone Settings from Hub1

What is it?
We migrated the business time zone setting from Hub 1 to Hub 2. To smoother and efficiency process and set up.
 

How it works
The business time zone is copied from Hub 1 into the Loyalty server whenever a business is created or updated. This happens automatically behind the scenes.
 

Hub 2:
Business profile → POS & Connectivity → General 

👉 For more details, check out the Knowledge Article.

Additional enhancements:

• Collapsible Campaigns in Campaign Center (Hub 2.0)
  • Users can now collapse and expand individual campaign sections using a small arrow at the top left of each campaign box. This makes it easier to manage long lists of campaigns.

• New Success Pages After Registration/Profile Update
  • When customers complete registration or update their profile through the Customer Portal:
    • They’ll be shown a branded confirmation page featuring your business logo, name, and relevant details, creating a more polished and consistent experience.
    • If your business has an app, the page will also display a “Download App” button, powered by OneLink, directing users to the correct app store for their device.
      
      
       

Bugs fixes:

• Style fixes in Member Profile
  • Minor visual issues in the layout were corrected to improve readability and consistency.
     

Multi-channel Communication

Email Templates Organization 

What is it?
Merchants often have many email templates stored in one place, which can get messy and hard to manage. To make this easier, we’re improving the email template system. 

We added group templates into containers (like folders or categories). You can also move templates between these containers. This makes finding and organizing templates much simpler.

Why it matters
Right now, templates are all in one flat list. This makes it difficult to:

• Quickly find the template you need
• Keep things organized as the number of templates grows
• Manage templates efficiently

With containers, merchants can easily group related templates, improving workflow and saving time.

How it works

• Users create and name containers (called Category Groups).
• Every new template is created inside a container.
• Existing templates can be placed into a default “untitled” container if needed.
• Templates can be moved between containers.
• You can search and filter templates by container names.
• The interface clearly shows which templates belong to which container.
   

👉 For more details, check out the Knowledge Article.

Additional enhancements:

• Email Mentions
  • We’ve introduced new mentions in our email builder:  member detail mentions. Now, each email can be personalized with dynamic member information, improving relevance and engagement.

• Web Push Inbox in the Customer Portal

A new Web Push Inbox was added to the Customer Portal:

• It allows users to view previously sent web push notifications.
• The inbox is accessible from both the homepage and the main navigation bar.
• Each message includes its title, description, and image, if provided.
• This inbox is separate from app push notifications – it only includes web messages sent via browser.

• Helps users keep track of messages they may have missed or closed.

   

  
  
  
  
   

Bugs fixes:

• Illegal characters removed from SMS messages
  • Non-supported characters that could prevent message delivery are now automatically cleaned before sending.
    
     

Connectivity

App Deep Link Support - Phase 1

What is a deep link?

A deep link is a URL that directs a user straight to a specific web view page  within a mobile app, rather than just opening the homepage or app’s main screen. It allows for more precise navigation, improving user experience by taking them exactly where they need to go.

 Our current deep link setup works as follows:

• If the app is already installed on the device, tapping the link will open the app directly.
• If the app is not installed, the link will open a fallback webpage instead (rather than redirecting to the App Store or Google Play).

It ensures users can still access content when the app isn’t installed, but does not yet support automatic redirection to the app store for download.

👉 For more details, check out the Knowledge Article.

Bugs fixes:

• Improved support for large payloads in Action Log (Shopify integration)
  • Previously, when opening a purchase activity involving multiple members, the extended activity table overflowed or appeared misaligned.
  • The layout now handles large activity data correctly without breaking.

Data & BI

Looker - Support Multiple Branch IDs per Location - Data Explorer & Como Projects Update

The Data team has enhanced the system by adding support for sub-branch IDs per location within Data Explorer and Como projects.

This includes:

• New mapping tables that link sub-branch IDs from different sources to a main branch ID that is mapped in HUB.
• Improved accuracy in tracking purchases and general information across these IDs, avoiding data confusion .

These updates provide more reliable and comprehensive data reporting for locations with  sub-branch IDs.

There have been changes to the following reports: 

• Points/credit
• Benefits
• Punch Cards

• Promo Codes

   

Additional enhancements:

• POS Transaction ID Added to Points/Credit Explore

The data team enhanced the Points/Credit Explore by adding a new field for POS-related transaction IDs.
This improvement allows better tracking and analysis of transactions linked to POS systems within the existing data reports.

Bugs fixes:

• Promo Codes Linked to General Membership in Reports
• Punch Card Expiration Date Missing in Explore Results

App Release

Phoenix Version: 3.0.49
iOS / Android Version: 3.0.21 (Minimum: iOS 13 / Android 7)

Bugs fixes:

• Cookie Consent Modal – Scroll Issue Fixed (Android)

We resolved a UI issue that prevented proper scrolling in the cookie preference banner on Android devices.

The fix is now live in production and available in Phoenix version 3.0.49.

• Fixed the webview where some items were not clickable on iOS