POS Integration Engine • Release

Created 08 July 2025 • Updated 08 July 2025

1.57.0 - Production

The following information details this release of POS Integration Engine (Aztec).

Release Schedule

Production
4 February 2025

What's New

New Features

The following new features have been introduced in this version of POS Integration Engine (Aztec).

Feature Description

Loyalty REST API

REST API for Loyalty transactions has been implemented for Zonal Connect. This will support assigning account, balance enquiry, lite registration, redeem reward, reverse redemption, fetch earning code and upload ticket

Standard Loyalty APIs as REST Services

The Loyalty REST API is now supported in the Zonal Standard Loyalty plugin, which allows it to be supported in the FSA and available to Aztec+ and Zonal Connect.

Punchh Loyalty API as REST Services

The Loyalty REST API is now supported in the Punchh Loyalty plugin, supporting portable devices ability to perform loyalty related actions

Standard Loyalty enhancement - location data

The Standard Loyalty plugin has been enhanced provide the Aztec site reference location data during each call made to the 3rd party loyalty provider. This will support sites that want to apply location specific Loyalty campaigns

ZCF Head office Plugin

New plugin to retrieve order line items from head office via ZCF. ZCF data is transformed into till ready data format for display on a correction like page

CLM PMS - PosInt Log Improvements

To improve POS Integration Hotel postings, SQL will be removed from the logs to make them more legible and only display the required information

National Trust Plugin URL update

A new version of POS Int is required to make the resource URL configurable, allowing us to define different resources for Prod, Pre-prod SIT & UAT environments.

Additional Information

Voucher Manager TXD plugin installed on sites 1.51.0 and above will now utilise the Aztec CLM Site Discounts | No Discounts Assigned setting, administrators must manually enable what specific discounts should be applied to individual sites. Turning on all discounts will not impact other settings such as controlling discounts via prefixes