SRS Patch notes for 7.4-59

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

Originally written by Will Miller, last updated Jul 30, 2024, on the Swan Retail knowledge base (SRS).

Part of: SRS 7.4


Version 7.4-59

30th July 2024

- Fixes

SWAN-2793 Purchase Order Sending - Supplier Purchase Orders not sending as Excel if the report has a logo

Excel format purchase orders will now strip out logos so that the spreadsheet can be emailed. Simply set a supplier as taking ‘Excel’ format purchase orders in Supplier Maintenance.

SWAN-4458 Customer Order Credits - No description of NON STOCK items for systems not concatenating brand descriptions

Item descriptions are always shown in customer order credits now, including where it was previously failing for non-stock items on some systems where brands were not being concatenated in the description.

SWAN-4742 SRS Swan Mobile - Pick Processing (Guided Picking)

A bug which was preventing the Guided Picking program on Swan Mobile from picking the same item from the same location for multiple orders has been fixed. This is an update to how SRS processes the data and not an update to the mobile software itself.

See if you’d like to know about the stock control and warehouse management functions available in Swan Mobile.

- New Features

SWAN-4682 COA V12 Finance Application - Include More Customer Details

More details are now sent up to V12 as part of finance application. This now includes name, address and ‘months at address’ details from SRS if you’re storing this. It will make it quicker and easier for customers to complete their finance application process on the V12 portal, which they get sent a link for.

At a high level, the process for a finance order through the integration (as at this patch 7.4-59) is:

  1. Create order on the Customer Ordering App

  2. At the end of the order creation, select ‘Apply For Finance’ on the payment screen. This will also set the customer with a ‘Finance Pending’ account type in SRS for their order.

  3. Customer receives an email with the V12 application link.

  4. Customer fills in remaining additional details for the application; Possibly on their phone while still in-store!

  5. Once complete, V12 will notify your team, at which point you can update their account in SRS with the agreement number and account type.

SWAN-4717 and SWAN-4753 SRS API to Cygnus - Add 'Receipt Print' option to Item Attributes

Added database storage to show attributes that should be printed to receipts, ready to be used by Cygnus.

Attribute maintenance in SRS now allows setting attributes so they can print on Cygnus receipts. The intention is that this can be used for customers to notify kitchen prep teams of allergies in a hospitality environment but could also be used for other attributes you’d like to show.

Please let our team know how you’re using this feature as we’re always interested in alternative uses for new features!

To use this on a till will require the new feature on Cygnus, which is coming soon!

- Other

  • BEHIND THE SCENES SwanPay - Additional logging for SwanPay (ClearAccept) payments to provide more detail to support for embedded payments in SRS.

  • API Deliverable days - the way dates and status changes are sent on the API has been improved ready for use by BalancePay v2 and COA.

  • API Deliverable days - The API has had some refactoring to make the available delivery dates easier to use and fit to our best-practice standards.

  • API Item settings for Cygnus - Measure and UoM are sent to Cygnus now so that the till can determine whether to use/allow decimal places.

  • DATABASE More User Settings - In preparation for future features for COA, a user can have permissions stored for creating quotes and amending orders. The setting controls and use of these will come in later patches.

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