Release Notes

Punchh Platform Release Notes - 09 September 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.

Consumer Experience

Password Reset Confirmation Screen

The Password Reset Confirmation screen has been updated to allow CSS styling. This screen is independent of the loyalty iFrame, such that it is still visible even when the loyalty iFrame is not in use. (CX-2856)

Offers Management

New Qualifying Conditions Added to Line Item Selectors

Marketers can add a qualifying condition (QC) at the line item selector (LIS) level to filter modifiers associated with a base on quantity and/or amount, allowing marketers to add an additional layer of qualifying condition in an LIS before being evaluated by the QC's Item qualifier condition. Two new modifier filter conditions are added:

  • Modifier Quantity
  • Modifier Amount

For example, if a marketer wants to run an offer on a sandwich with only two add-ons, then the marketer can define the qualifying conditions at the LIS level to qualify only the sandwiches on the receipt with 2 add-ons. Any sandwich with more or fewer than 2 add-ons will not qualify for an offer. (OMM-1373. PDOC-3265)

See the following article(s) for more details:

Platform Integrations

Update of Validation Login for PAR POS

We have introduced a new business setting to help prevent duplicate vendor transactions from PAR POS systems. When enabled, this feature will validate incoming transactions and block duplicates before processing. Full duplicate detection will be available in an upcoming release. (INT-3365)

POS Integrations

Toast: Leverage Multi-Location IDs

Customers using Toast can now create line item selectors using multi-location IDs instead of GUIDs. This update streamlines configuration for multi-location setups and improves overall usability. (PPCC-1647)

Action Required: Contact your Punchh representative to enable this feature for your business.

Developers Corner

Redemption API Update – Qualification Criteria in Failed Responses (Phase 1)

As part of Phase 1 of our Redemptions API improvements, the system now returns all qualification criteria (receipt-level and line-item) for submitted offers that fail in the responses of the POS Possible Redemptions 1.0 API and Create Redemption 1.0 APIs for Online Ordering and POS. This feature is available only when enabled for the brand in the Punchh platform. Brands must contact their Punchh representative to update this Punchh platform configuration. (CAM-6502, PDOC-3274)

  • Phase 1 includes the Redemptions 1.0 APIs.
  • Phase 2 (targeting September 30) will extend support to the Redemptions 2.0 APIs.

With this enhancement, when a redemption request fails, the response will now include all qualifiers for the offer (both receipt-level and line-item). While the overall status will remain “failed”, this enhancement enables loyalty marketers and digital teams to:

  • Build logic across online and in-store ordering to understand why an offer did not qualify.
  • Deliver custom messaging that helps improve order conversion after failed offer redemptions.

The responses of the Create Redemption 1.0 APIs for Online Ordering and POS now include a new response parameter, the qualifying_conditions object, which lists the failed qualification criteria for submitted offers.
See the following article(s) for more details:

Olo Promotions Spec (2.0) Support – Full Transactional Flow Implemented

Punchh now supports the full set of Olo transactional promotion APIs required for standard Olo ordering flows, including validation, redemption, accrual, and void operations. All endpoints comply with Olo Promotions Spec 2.0 and include request and schema validation as per the Olo documentation, ensuring real-time integration, robust error handling, and transactional integrity.

These enhancements enable seamless loyalty and promotion experiences for Olo-powered brands, with unified guest experiences and simplified partner onboarding. These APIs allow authenticated users to use both coupons and loyalty rewards when ordering through Olo. (OMM-1338)

Scope

  • Applies only to signed-in users with provisioned Punchh accounts.
  • Guest check-out and account creation flows are out of scope, as Redemptions 2.0 does not support guest redemptions.

Olo Promotions Spec 2.0 All-or-None Promotion Redemption

Punchh’s Olo Promotions API implementation fully supports Olo’s “all-or-none” redemption semantics. Per the Olo documentation and Promotions Spec 2.0 behavior, Redemptions 2.0 APIs are implemented with all-or-none redemption semantics. This means:

  • When multiple offers are submitted in a single check-out, the redemption succeeds only if all offers are valid.
  • If any offer is ineligible (e.g., conflicts, unmet criteria, expired, budget exhausted), the entire request is rejected with spec-compliant errors. Partial redemptions are not supported.

Enablement and Configuration in Punchh

  • Punchh must configure Redemptions 2.0 enablement at the brand level. To activate, Olo/brands should contact their Punchh representative to update this Punchh platform configuration.

Overview of Olo Promotions Spec 2.0 API Endpoints in Punchh

  1. POST /promotions/validate – Olo, via this API, sends the basket to Punchh to check which offers/rewards are valid before check-out.
  2. POST /promotions/redemptions – Olo calls this API to commit promo/loyalty redemptions at check-out.
  3. DELETE /promotions/redemptions/{id} – Olo calls this API to void or roll back a prior redemption if the order is changed or cancelled.
  4. POST /promotions/accruals – Olo calls this API to credit loyalty earnings after order completion.
  5. DELETE /promotions/accruals/{id} – Olo calls this API to roll back previously credited loyalty points if the order is refunded.
  6. GET /promotions/accounts/{accountId} – Olo calls this API to fetch the user's account details (User ID is used as Account ID).

These Olo APIs are implemented in Punchh. However, the API documentation for these APIs is maintained on the Olo website. Click here to view the Olo Promotions Spec 2.0 documentation (Olo login required).

Void Operations - Redemptions and Accruals via DELETE Endpoints

  • Both redemptions and accruals can be voided using the provided DELETE endpoints.

Compatibility and Security

  • Spec compliance: Request and response schemas, and error models, fully match Olo Promotions Spec 2.0.
  • Signatures: All incoming requests require valid signatures; invalid or missing signatures are rejected (per Olo rules).

Guest Events Now Published for Deactivated Users

As part of our event publishing improvements, the system now publishes guest events when users are deactivated in the Punchh system. In addition to deactivated, guest events are also sent for users with active or banned status. Events continue to be excluded for users with anonymized or archived status. (INT-3328, PDOC-3271)
See the following article(s) for more details:

Previous
Punchh Platform Release Notes - 30 September 2025 Deployment
Next
Punchh Platform Release Notes - 19 August 2025 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.