Release Notes

Punchh Platform Release Notes - 23 July 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.

Loyalty

Removed Ability to Stop Recurring Rewards From the Guest Profile

Previously, if a recurring redeemable for a guest needed to be stopped, an admin could stop the recurrence through a 'Stop Recurrences' option available in the guest profile under the Rewards tab. Now, this feature for a recurring redeemable has been disabled. Admins will not be able to stop the recurrence for an offer from the guest profile but then should deactivate the redeemable (Settings > Redeemables) to stop all future recurrences. (EPS-8616, PDOC-2511)

See the following article(s) for more details:

Segment Type for Saved Payments (Punchh Wallet)

We have introduced a new segmentation capability based on the saved payment types in Punchh Wallet. A new segment type named 'Saved Payment' has been added to the Punchh platform. This feature is exclusively available to Punchh Wallet users. (SB-3081, SB-3111, PDOC-2531, PDOC-2532)

See the following article(s) for more details:

Campaigns

Increase in the Number of Campaign Tags

The number of campaign tags was increased from 10 to 50 with the release of the campaign management tool. This enhancement boosts that limit from 50 tags to 500 campaign tags, giving you more flexibility to get and stay organized with your campaigns. (CAM-4936, PDOC-2535)

See the following article(s) for more details:

Performance Enhancements for Recall and Anniversary Campaigns

To improve our campaigns' overall speed and efficiency, we have implemented some improvements for our Recall and Anniversary campaigns, allowing data to be transmitted in bulk. (CAM-4495, CAM-5258)

See the following article(s) to learn more about these campaign types:

Reporting & Analytics

Added referral_code to the Guest Data Export

We have added the 'Referral code' attribute as a field for selection on the Guest Data Export to allow users to pull the 'unique referral invite code' associated with every guest. (DP1-1348, PDOC-2518) 

See the following article(s) for more details:

Developers Corner

New Mobile API for Cancelling a Redemption

Developers can now cancel redemptions using the new /api2/mobile/redemptions API endpoint with Redemptions 1.0. This feature is supported across all loyalty structures. (LPE-835, CX-2448, PDOC-2469)

See the following article(s) for more details:

Card Type Response Parameter Added to POS Payments APIs

The new card_type response parameter has been added to the POS payments API endpoints: Create Payment, Update Payment, Void/Cancel Payment, Get Payment Status, and Refund Payment. (INT-2571, INT-2551, PDOC-2451)

See the following article(s) for more details:

Update Gift Card API Restricted to Gift Card Owner

The /api2/mobile/gift_cards/{uuid} API endpoint is restricted so that only the gift card owner may update the name, design, and preference of a gift card. This endpoint generates a 422 error response if a user who is not the gift card owner attempts to update the gift card. (INT-2604, PDOC-2509)

See the following article(s) for more details:

Remove Expired Rewards From Discount Basket

If a discount expires after being added to the discount basket, it is removed from the discount basket. When you make a call to the API, it validates the offers added to the discount basket. If one or more discounts are found to be honored, expired, perished, or archived, the API returns an error message indicating that these discounts cannot be honored. The new message response parameter has been added to some Redemptions 2.0 API endpoints to show the error message returned for an invalid discount. The applicable endpoints are: Auto Redemption (POS and Online Ordering), Add Selection to Discount Basket (POS), Remove Item From Discount Basket (POS), and Get Active Discount Basket (Mobile and Online Ordering). (OMM-944, PDOC-2523, PDOC-2524, PDOC-2527)

See the following article(s) for more details:

Receipt Qualifier Channel for Applicable Offers

If a channel is defined in the receipt qualifier condition of qualification criteria in the Punchh platform, then the list of offers applicable on a transaction should be filtered out as per the channel filter. However, the Applicable Offers API was not considering the channel filter and was returning all offers irrespective of the channel. The API evaluation has been corrected to validate the channel filter of the receipt qualifier. Only the applicable offers post the channel filter evaluation will be returned in the API response. Offers will be evaluated based on the value of the channel parameter provided in the request of the API. (OMM-935, PDOC-2528, PDOC-2529, PDOC-2530)

See the following article(s) for more details:

Facebook Limited Login Support With OIDC Tokens

The existing Punchh APIs now support Facebook's Limited Login with OIDC tokens. Brands will need to update their apps to switch to Facebook's Limited Login, and the Facebook App ID must be provided to Punchh and configured in the Punchh platform as part of that project. (CX-2437)

Previous
Punchh Platform Release Notes - 20 August 2024 Deployment
Next
Punchh Platform Release Notes - 25 June 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.