Release Notes

Punchh Platform Release Notes - 12 November 2024 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.

Campaigns

Campaign Tags Field Removed From Business Profile

Campaign tags are managed from the Campaign Management tool under Campaigns > Campaigns. The legacy Campaigns page required users to update tags on the Business profile page and were limited to 10 tags. Access to adding/removing tags from the Business profile page has been removed completely. (CAM-4883, PDOC-2745) 

See the following article(s) for more details:

Loyalty

New Payments Tab for Notification Templates

The new Payments tab under Settings > Notification Templates contains a notification template for payment transaction notifications done via Single Scan Flow (SSF) and POS. (INT-1808, INT-1792, PDOC-2721) 

See the following article(s) for more details:

New Payment Tag for Notification Templates

A new dynamic tag called {{{payment_mode}}} has been added as a tag option for payments-related notification templates. (INT-1807, PDOC-2740) 

See the following article(s) for more details:

'Apple Passes' Changed to 'Passes' in Settings Navigation

The "Apple Passes" section under Settings has been renamed to Passes for a clearer, more generalized view. (INT2-1626, PDOC-2720) 

See the following article(s) for more details:

Resolved Issue With Xpient POS

Locations using the Xpient POS system were experiencing double earnings despite a previous fix having been applied via the Olo webhook. The root cause was identified as a mismatch between the transaction numbers received from Olo and the Xpient POS. Xpient appends a custom string to the POS transaction number when sending it to Olo, which led to the system treating valid POS transactions as fresh transactions, resulting in duplicate earnings. We have implemented a solution that addresses this issue specifically for Xpient POS systems. While ingesting the data from the Olo webhook, we will now split the transaction reference value provided by Xpient and only use the receipt number to process transactions. This will ensure the correct handling of duplicate transactions and prevent double earnings. This solution is designed as per the update from Olo regarding custom transaction number strings for Xpient. This fix will affect only businesses or locations using the Xpient POS system. There are no changes to other POS types, ensuring backward compatibility with existing configurations. (INT2-1685) 

Resolved Issue With Discount Applied to Ineligible Items

With multiple redemptions, if an offer was configured with a line item filter condition having excluded items and the "discount stacking" feature was disabled on the offer, then discounts were getting applied on the excluded items, which should not be happening. The discounting behavior for this issue has been fixed. If an offer has excluded items in a line item filter condition, then the discount will not be applied to the excluded line items. Businesses using multiple redemptions that have offers with the discount stacking feature and have excluded items in a filter condition will have a more accurate discount application as per the expected behavior. Offers will accurately discount the line items when the discount stacking feature is disabled. (EPS-9029) 

Segments

Sign-up Channel Renamed to ApplePass

We have updated the 'AppleVAS' onboarding channel to ApplePass to enhance clarity and consistency across the Punchh Platform. (SB-3227, PDOC-2717) 

See the following article(s) for more details:

Payment Type Attributes for Single Scan Flow Renamed

We have updated the labels for existing Single Scan Flow (SSF) payment types to enhance clarity and consistency across the platform. The 'Credit Card' and 'Recurring' payment types have been renamed to One-Time (Credit/Debit) and Recurring (Credit/Debit) to better align with segment evaluation and ensure accurate representation. (SB-3226, SB-3293, PDOC-2716) 

See the following article(s) for more details:

New Campaign Types for 'Guests Targeted From a Campaign'

We have expanded the Guests Targeted from a Campaign segment type with new campaign types, allowing you to engage guests based on their previous campaigns. The new types include Anniversary, Post-redemption Messages & Offers, and Post-Payment campaigns. (SB-3224, PDOC-2685) 

See the following article(s) for more details:

New Validation Check for Manually Entered Zip Codes

We have introduced a new validation check for manually entered zip codes during segment creation. Users will be notified if they exceed the 20,000 zip code limit in a single entry, ensuring smoother segment execution and improved system performance. (SB-3218, PDOC-2718) 

See the following article(s) for more details:

New Limit of 40 Rules When Creating Segments

To ensure optimal performance and smooth segment execution, we have implemented a limit of 40 rules when creating segments, whether in a single segment or nested segments. This update improves efficiency and ensures that segment execution remains uninterrupted. (SB-3169, PDOC-2719) 

See the following article(s) for more details:

Reporting & Analytics

Data Pipeline - New Columns for Mass Gifting and Segments

New columns have been added to the mass_giftings and segment_definitions tables. (CAM-5609, SB-3009, PDOC-2699) 

See the following article(s) for more details:

Deprecated the Daily Redemption Report

We are deprecating the 'Daily Redemption Report' and associated schedules from the platform due to limited usage. With this change, the 'Daily Redemption Report' will no longer be available on the platform. Users will not be able to enable or schedule the report through the platform UI or API. (DP1-1516, PDOC-2655, PDOC-2715) 

Recommended Action: All available redemption data can be found on the Redemption Report page (Reports > Redemption Report). Click the Export button on the top right of the page to export the report directly to your local machine.

See the following article(s) for more details:

Consumer Experience

Gift Card Configuration Value Added to Location Configuration for Mobile

When businesses have gift card payments enabled for Single Scan Flow, a new check box named "Hide gift card payment in SSF" will be available for each location under Settings > Location > Mobile App. This flag will be used by the Punchh Mobile Framework, and its value is also available for third-party developers via the v2 mobile API.  (CX-2534, PDOC-2725) 

See the following article(s) for more details:

Webhooks Manager

Webhooks Logs Easier to Close

You can now close a webhook log easily with a new sticky header tab, eliminating the need for multiple scrolls.  (INT-2722) 

See the following article(s) for more details:

Developers Corner

Deprecated the Daily Redemption Report

The enable_daily_redemption_report parameter has been removed from various location API endpoints (Get Locations List, Create Location, Update Location, and Get Location Details), as well as the api2/mobile/meta.json API endpoint, because the Daily Redemption Report will no longer be available in the Punchh platform. (DP1-1516, PDOC-2671) 

See the following article(s) for more details:

Gift Card Configuration Value Added to Mobile Program Meta

The hide_ssf_gift_card response parameter has been added to the api2/mobile/meta.json API endpoint to indicate whether paying using a gift card in the Single Scan Flow (SSF) is available or hidden for in-store transactions. (CX-2534, PDOC-2698) 

See the following article(s) for more details:

Gift Card Purchase and Reload Amounts Added to Mobile Program Meta

The gift_card_default_amounts object has been added to the response of the api2/mobile/meta.json API endpoint. For brands using the Punchh gift card module, the API has been updated to allow third-party app developers to ingest Punchh platform configurations for gift card purchase and reload default amounts. (CX-2547, PDOC-2723) 

See the following article(s) for more details:

Redemptions 2.0 APIs Return Details for Additional Offer Types

Redemptions 2.0 (multiple redemptions) APIs have a discount_details object that returns the meta_detail parameter. Previously, this parameter returned details only for the redemption_code (coupon) discount type. Now it also returns details for the reward, subscription, and redeemable discount types. This update applies to the Redemptions 2.0 API endpoints for POS, online ordering, and mobile. (OMM-1118, PDOC-2744) 

See the following article(s) for more details:

Previous
Punchh Platform Release Notes - 10 December 2024 Deployment
Next
Punchh Platform Release Notes - 15 October 2024 Deployment
Copyright © 2026 PAR Technology Corporation. All rights reserved.
PAR Technology Corporation 8383 Seneca Turnpike, Suite 3 New Hartford, New York 13413 (315) 738-0600 legal@partech.com. PAR Tech is a leading global provider of software, systems, and service solutions to the restaurant and retail industries. You may learn about its product offerings here.
Before using this application, please read the PAR Tech Terms of Use. In addition, the sample applications of PAR Technology are licensed under the terms of the O'Saasy License.