Originally written by Will Miller, last updated Jun 06, 2024, on the Swan Retail knowledge base (SRS).
Part of: SRS 7.4
Version 7.4-55
5th June 2024
Released with 7.4-54
- Fixes
SWAN-4607 (+ SWAN-4577) - Customer Order Enquiry - View details not showing assumed PO for stock lines
Assumed purchase order details are shown on the details tab when there is no PO or GR stored on the sales order line if the item sold is from stock or it’s sold from a PO and it’s a stock line (non-bespoke and not itemised).
There was also a niche case where an order line could cause the system to show an error if it had a GRN number but no PO number. This could only happen to service items if ‘quick received’ through Customer Order Control Centre. It’s resolved as well now though.
Support #: SUP-48181
- Added
SWAN-4559 - Quick Delivery Confirmation - Pick list for multiple orders
New “Pick List” available from quick delivery confirmation screen designed for use in branches dispatching goods via courier or post.
Highlight multiple orders using Shift+Click or Ctrl+Click and the pick will include all selected order lines that are available. Warnings will be shown for orders with undeliverable items and outstanding payments.
The pick list is not assigned a pick number and does not change the status of a customer order, but it makes it simple for branch teams to collate orders onto a single list to prepare for postage. This can then be paired with the integration to Shipster for a smooth but simple pick+despatch process requiring minimal administration.
See Shipster Courier Integration for more details on the Shipster courier integration.
Support #: SUP-45071
- Changed
SWAN-4492 - Cygnus Transactions - Use stock item code in transactions data
If barcode is missing from SRS, the item code will be used instead, ensuring deletions of barcodes from SRS do not cause transaction processing to fail.
Support #: SUP-45983, SUP-46027, SUP-46164, SUP-47087, SUP-47079
SWAN-4446 - SwanPay with SRS - Store Last used Device
When using SwanPay (ClearAccept) through the back office of SRS, the last used payment terminal is stored and will be shown as the default on all future payments that user processes at that branch. They’ll still have the option to change it if needed.
Example from the Customer Payments screen, but this works in Customer Order Creation, Customer Order Amendment and Sales Entry as well:
SWAN-4221 - Update Runner to Clear Till PAUTs and LAUTs
A maintenance routine has been introduced to automatically clear Payment Authorisations and Loyalty Point Redemption Authorisations (PAUT & LAUT) from customer accounts when there is not a transaction to match them to. This will ensure customer store cards and loyalty cards are able to use the full available balance.
The automated clear-down occurs for PAUT and LAUT entries older than 1hr.
Support #: SUP-45055
SWAN-3362 - Sales Entry - Take payments through ClearAccept
The SRS ‘Sales Entry’ program now has SwanPay (ClearAccept) integration and functions the same as order payments. This is the last order/POS entry program in SRS that needed integration, completing the initial phase of embedding SwanPay within SRS.
Sales Entry is a basic POS program, primarily used by retailers needing to process POS-like transactions when not near a Cygnus till.
Other
These changes are behind-the-scenes in SRS with no visible impact on users, on pre-release software currently being tested by users (User Acceptance Testing - UAT) or bespoke to a client:
-
UAT Customer Ordering App (COA) Warranty Lines → Sometimes warranties were not saving with the links, this is now resolved.
-
UAT Customer Ordering App (COA) Line Notes → Line notes were sometimes not being saved onto the order when processed by SRS, they are now.
-
BEHIND THE SCENES Patch Database Updates Adjusted → The handling of database constraints for new fields has been adjusted for reliability.
-
BESPOKE Delivery note fixes → Specialist handling to hide composite components and show a composite line instead.
-
BESPOKE Statement print changes → Adjustments to only print Brought Forward lines if non-zero and changes to column headers
-
BEHIND THE SCENES Cygnus Server Transactions API - Outputs customer details for loyalty transactions
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article