Originally written by Will Miller, last updated Jul 01, 2025, on the Swan Retail knowledge base (SRS).
Part of: SRS 7.4
Version 7.4-81
1st July 2025
- Fixes
SWAN-5631 - Swan Mobile - Processing Update Event Errors for Purchase Order Receiving
Update event errors are created for purchase orders received on mobile if part of the received goods are already invoiced.
Previously part of the receiving would complete and part would fail which made it unclear where there was missing data. Now it’ll be
Support #: SUP-53008
- Added
SWAN-5211 - Quick Delivery Confirmation - Full Picking process
Quick Delivery Confirmation (QDC) from branches, typically used to dispatch web orders, has an option to go through a picking routine. This provides additional status updates on the order so a line will go through Allocated → On Pick → Picked → Dispatched. It also lays the necessary groundwork to allow mobile picking of these goods later in 2025.
To enable QDC picking a parameter QDC_PICK_CONF needs to be set to ‘Y'. It’ll be 'N' by default to ensure existing notional-only picking remains the default where there is no pick number or process other than a print grouping the items required.
Once enabled, the ‘Print Pick List’ button (1) in QDC will produce a full pick when used, assigning the number to the orders (2) and lines (3) of the order that are highlighted when it is clicked. It will then be clear in Item Enquiry when looking at location detail when you have items on a pick.
This pick list can then be confirmed using the standard Customer Order Pick Confirmation program used for customer delivery schedules and the stock will be moved to TRANSIT once the pick is confirmed as well as showing the order as ‘Picked’ (4) in QDC.
Item lines cannot be picked again once picked but additional item lines or previously failed picks can be.
As all items in the branch are typically in the SELLING location, the intention for this picking method is to pick by order number, so the pick list will be sorted by order number.
It is possible to reprint and consolidate this picking lists as it is with delivery schedule picking using the existing programs (split pick list coming soon!). We’d recommend trying out any change in process to ensure success, but please contact us if you’re interested in adapting your existing workflows to make use of this new function.
Consolidated Picks If you want to consolidate these new prints there is a new report version to include non-warehouse picks - pickingListConsolidateQDC.jasper - which will need setting in Report Maintenance
Support #: SUP-49280
- Changed
SWAN-3749 - Report Spooler - Dated sub-folders
Report spool prints are now stored in a yyMMdd subfolder under report_spool_dir (see parameter for filepath) to prevent build up of files. This will ensure spool files stored outside of the database are easier to manage in the future.
Previously spool files were all stored in a single folder which would become difficult to support after extended use due to large volume of files.
Existing files will be moved into this structure on request to support. Most likely required for those retailers hosting their own systems locally.
Minimum SRS Version 7.4
- Other
[ API ] Customer creations have improved resiliency to configuration issues which could previously result in missing account types. Support #: SUP-58050
[ API ] SRS API - The field 'mandatory' is included for checklists picked up by the Cygnus tills
[ API ] Cygnus - Optimisation of receipt data retrieval on transaction lookup and transactions lookup since date time.
[ API ] Cygnus Server - a new POST endpoints for creating Departments designed for use with TRIMS integrations
[ API ] Cygnus server - New endpoint added to get standard notes from SRS. Initially intended to be used for line notes on Customer Ordering App.
[ API ] Cygnus server - Attributes updates are available through new endpoints so changes can be picked up in a reliable and efficient way by the tills.
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