SRS Patch notes for 7.4-90

Created by Migration Bot, Modified on Wed, 21 Oct at 1:02 PM by Migration Bot

Originally written by Will Miller, last updated Nov 11, 2025, on the Swan Retail knowledge base (SRS).


Version 7.4-90

4th November 2025

- Fixes

SWAN-6163 - TRIMS Integration - 'Loyalty Map' when multiple loyalty cards are used on one transaction

Changes to the TRIMS integration with Cygnus now mean that SRS will pass through all loyalty cards used on a transaction where it was previously only possible to use one.

Support #: SUP-59902, SUP-61091

- Changed

SWAN-6374 - SRS Web Orders - Logging Enhancements for Order Updates

Logging changes to adjust when data is taken for the log to ensure the log reflects exactly what is received by remote web services. Previously logs we populated before encryption, so small possibility of an impact from the encryption which will now become evident regardless of logs/information provided by third party web providers.

Support #: SUP-61338

SWAN-6154 - Cygnus Server API - Accept invoice matching details

The supplier invoice registration endpoint allows invoice approvals using purchase order goods received notes (GRNs) or Nominal details. This is adding to the existing invoice registration endpoint released in the last patch which will be utilised for the Swan invoice automation integration coming up.

SWAN-6153 - Cygnus Server API - GET GRNs endpoint

New Cygnus Server endpoints added to look up GRNs either by grn number or using query parameters:

  1. purchase-order-number

  2. supplier-number

  3. supplier-id

  4. received-from

  5. received-to

  6. include-matched

Note : When using GET /api/grns it will always return unmatched GRNs by default. If you want the response to include matched GRNs, the optional parameter ‘include-matched’ should be set to true.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article