3.28.0 - Production

When receipt details are sent by Aztec to Punchh, Aztec should send the promotional price rather than the standard price when redemptions are done

This means that when Punchh returns a discount for a "free" item, then it should only tell POSInt/Aztec to discount by the value of the promotional price. This will be the selling price for each item and not the standard price

The print on the receipt currently shows expiry date in number of days (e.g 14 days). This feature allows the POS to calculate the actual expiry date of a promotion and print it on the receipt

A clear end date on the receipt for the promotion will make the customer aware of the 'use by' time they have to use that promotion.

Punchh sends POSInt the line items being discounted, but not the proportion of the discount value that applies to each item.

A change is made in Aztec to receive the information from POSInt about which line items have been discounted. This will result in POS and the receipt displaying the discount(s) applied to each item and by how much

When a Punchh redemption is performed, no barcode should be printed as the customer would already be earning on that transaction. And if a barcode is printed and the customer tries to scan it, they will get an error.

These voucher types will be able to be associated with an Aztec Promotion ID, that can be returned in an API response. This will allow POSInt to inject a promotion into an account when a Voucher Manager voucher is scanned

SQL 2012 is coming to the End of Life. Modern SQL versions are 64 bit whereas 2012 version was 32 bit. This feature delivered a test on the impact of upgrading to SQL 2022 with no issues found