Originally written by Will Miller, last updated Apr 25, 2024, on the Swan Retail knowledge base (SRS).
Part of: SRS 7.4
Version 7.4-52
23rd April 2024
- Fixes
SWAN-4083 - Standard Sales Invoice and Sales Order Print error - Notes area
Header notes have been moved under the list of items on the standard order prints (salesOrderPrint.jasper and salesOrderInvoice.jasper as set in Report Maintenance)
Sales order and sales order invoices using these standard layouts will no longer error when there are long external header notes on the order.
Support #: SUP-42177
SWAN-2704 - SRS Customer Order Enquiry - Purchase order details on 'View Detail'
From this patch onward, a GRN number will be stored for each customer order line when it is allocated to a purchase order prior to goods being received. This is not possible to add retrospectively, so this information is only for new goods received.
This means that, unless items are sold from stock, the purchase GRN details will now always reflect the actual purchase order and GRN detail.
There is still an element of assumption in this as there is no way to be certain that an item picked from a shared location is the one from that purchase order.
This is an important improvement for customer service teams as it provides greater certainty of purchase details when speaking to suppliers. The GRN number can also be referred to in report writing, making audit trails more straightforward and it will be the pre-cursor to further improvements to the supplier return process.
Support #: SUP-31293
- Added
SWAN-4436 - Stock Adjustment - Hide Empty Locations
A new tick box has been added to ‘Include Zero Quantity Location’ which will show past used locations for each item which no longer holds a physical stock quantity.
This is unticked by default so these empty locations are not shown, so make sure you tick this before loading items if you need to see them.
Support #: SUP-45028
- Changed
SWAN-4524 - SRS Schedule Delivery Button - Undo Fix
Change SWAN-2917 introduced in patch 7.4-49 has been reversed after some retailers found it had an impact on their workflows when scheduling goods when still on order or transfer. This will be revisited in a later patch.
SWAN-4483 - b/e COA Items lookup Endpoint - Include concatenated brand description in lookup
The Instore Brand Description of an item is now included as part of the item description when searching for items on the COA.
SWAN-4375 - Customer Order Creation - Stock Reservation error logging
Extra logging has been added so that cleared stock reservations are logged. This will then show the Swan support team what action has cleared the reservation and lead the team toward a solution.
Please continue to let the support team know if you experience a stock reservation error when saving creation of a customer order so these logs can be checked.
Support #: SUP-45217
SWAN-4373 - SRS Cygnus API - Stock Branch Levels Endpoint: Remove Offset
The way in which Cygnus retrieves price change details has been adjusted to avoid timing issues with updates.
SWAN-4341 - Stock Count Control Centre - Delete unexpected items from count
A ‘Delete’ button has been added to the unexpected items in count tab so that scans of items not needed in the count can be deleted for clarity.
It is not necessary to delete the items from this tab before completing the count as they are not included unless you use ‘Add to Count’. This new button is included as a way of housekeeping the scans during a count.
The button will delete highlighted lines with a confirmation prompt.
If scans are deleted in error, they will need to be re-added or scanned to the count. It is not possible to delete scans already added to the count, so countering entries should be made if that has happened.
Support #: SUP-45087
SWAN-1378 - Omnisend: Trigger an Omnisend update on delivery confirmation
Changes to the delivery confirmation programs: Customer Order Delivery Confirmation, Quick Delivery Confirmation, Direct Delivery Confirmation and Branch Collection Confirmation.
These will all now communicate to the Omnisend marketing automation platform to confirm fulfilment status when the whole order becomes delivered. This will then allow you to use this fulfilment status to market to customers who have a fulfilled order.
This will only impact systems which have an Omnisend integration enabled and only for orders confirmed after this update.
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