Punchh Platform Release Notes - 11 February 2025 Deployment

The updates described in these release notes and the affected/linked documentation will not be available in the Punchh platform until the target deployment date.

Loyalty

Validation Check for Associations on Location Edit Page

A validation has been added to the location edit page to ensure that if a location group is to be attached, it must not already be linked to an existing reward. (LPE-1038, PDOC-2861)

See the following article(s) for more details:

• Store Locations (Support Portal)
• Location Groups (Support Portal)

Fuel Discount for Auto-Redemption

Businesses with a manual business type can enable fuel discounts for auto-redemption strategy. Once a fuel discount is selected for auto-redemption, it will be applied to transactions without any guest intervention. (OMM-565)

Currency and Points Expiry Event Notifications

We have removed the dependency on System Messages (formerly Notification Templates) for currency and points expiry notifications. Customers using third-party systems are no longer required to configure templates for these events. Webhooks will now trigger automatically, ensuring seamless functionality without additional setup. Going forward, if you want guests to receive these two notification events (currency and points expiry), there is no prerequisite to enable their notification templates within the Punchh platform. It was identified recently that there was a dependency to enable their templates via a toggle button under Notification Templates (now System Messages). However, we do not expect webhook functionality to be behind any notification template flag to be enabled for any customers. (INT-2978)

Segments

New Attributes for Receipt Tag Segmentation

We have introduced a new segmentation capability for the Contains Receipt Tag(s) segment that enables easy filtering of guests based on the number of times they are tagged with a specific receipt tag or by their overall tagging activity. (SB-3349, PDOC-2859) 

See the following article(s) for more details:

• Segment Types, Attributes, and Timeframe Definitions (Support Portal)

Reporting & Analytics

Data Pipeline - New Column for Storing Location Group Status

A new column 'archived_at' has been added to the tags table. (LPE-1052, PDOC-2821) 

See the following article(s) for more details:

• Data Pipeline - Announcements (Support Portal)

Enhanced Redemption Data Export

A new field 'Reward Origin' has been added under the 'Available Fields' section of the Redemption Data Export selection screen. When selected, it will appear in the 'Selected Fields' section and be included as the last column in the exported CSV file with the same column header and values: 'Loyalty', 'Deals', and 'Campaigns and others'. By default, this field remains unselected, ensuring the existing exports function as designed. (DP1-1586, PDOC-2837) 

See the following article(s) for more details:

• Data Export (Support Portal)

Developers Corner

Multiple Redemptions Business Logic Added to Program Meta API

The responses of the Program Meta API endpoints for POS and Mobile include a new object named multiple_redemptions, providing visibility around business-level configuration for Redemptions 2.0, such as auto-redemption, number of discounts allowed, etc. Also, the multiple_redemptions_enabled parameter has been added to the response of the Program Meta API endpoints for POS and Mobile, and the multiple_redemptions_on_location parameter has been added to the response of the POS Location Configuration API endpoint and the response of the Mobile Program Meta API endpoint. (OMM-1182, PDOC-2865)

See the following article(s) for more details:

• Program Meta (POS) (Developer Portal)
• Program Meta (Mobile) (Developer Portal)
• Location Configuration (POS) (Developer Portal)

Fixed Webhook Mapping for Adapters

The receipt_date attribute, previously missing from check-in event payloads with event mapping enabled, is now included for Braze, mParticle, and Salesforce Marketing Cloud (SFMC). Admins can now choose to include or exclude this attribute when using event mapping. This update ensures consistent functionality across all integrations. This allows displaying the receipt_date field when someone selects the event mapping feature for the check-in event and would like to modify/remove the field from the list of attributes if required, ensuring consistency among attributes with or without event mapping across all adapters (Braze, mParticle, and SFMC). (INT-2981)