SRS Patch notes for 7.4-34

Created by Migration Bot, Modified on Fri, 23 Oct at 11:31 AM by Migration Bot

Originally written by Will Miller, last updated Jun 07, 2023, on the Swan Retail knowledge base (SRS).

Part of: SRS 7.4 › Archive 2023


Version 7.4-34

7th June 2023

- Fixes

SWAN-3459 - Item Maintenance/Import - Cygnus item updates not always happening for each branch

When items were being updated in Item Maintenance or Item Import, they were not always triggering updates to the tills. This has been fixed and changes will now update all branches.

Minimum SRS Version 7.4

Support #: SUP-36192

SWAN-3401 - SRS Orders API - Ignore bad 'order status' for getNewOrders

Invalid web order status codes from third party web providers will no longer occasionally cause problems in processing web orders. SRS will now ignore these bad status codes, log them and continue to process the order as a new order.

For full operation of the web order interface, ideally only valid/supported status codes should be used.

Valid codes are:

cancelled
acknowledged
despatched
returned
awaiting despatch
abandoned
payment pending
partially despatched
completed
on hold
awaiting approval
on order
partially returned

Minimum SRS Version 7.4

Support #: SUP-33751

SWAN-3396 - Invoice Approval - GRN Cost Adjustment Issues

Cost adjustments in Invoice Approval will now update the GRN Audit in the nominal for use in Audit Enquiry of GRN Not Invoiced.

SWAN-3395 - Shipster - Remove 'CDATA' tags

The Shipster integration now handles text in a standard way which is accepted by the Shipster system.

Minimum SRS Version 7.4

SWAN-3282 - Shipster integration - UAT Snagging

Measurement dimensions output for Shipster are now in all caps as required by the integration.

Minimum SRS Version 7.4

Support #: SUP-15253

SWAN-3182 - Auto-suspended bespoke items

When bespoke items are generated they’re automatically suspended. This is phase 1 of a tidy-up operation being conducted across retailers to remove item clutter and tidy-up jobs users have typically had to do manually.

This ensures that if a bespoke item becomes free stock it cannot be used to re-order from supplier unless it has been un-suspended by stock administrators. However, it can still be sold from stock if available.

Items such as this replacement part will no longer need to be manually suspended to hide them once returned to supplier:

The ✔️ shown when adding items in order creation in the ‘BO’ (Back order) column for items like this will be a ❌ in future, showing the salesperson clearly that if they see it it cannot be ordered from the supplier.

This does not impact items generated from the catalog in purchase ordering as those items will be non-bespoke, so can continue to be used for re-ordering unless suspended manually.

The next phase of this tidy-up will be to suspend any existing items that are bespoke and to assist retailers on handling items that are no longer bespoke but should not be used for re-ordering from supplier (previously bespoke items), in particular those with 0 free stock. These next phases will either come in a patch or support will be in touch to run this ad-hoc for you.

Support #: SUP-34431

- Changed

SWAN-3391 - Discount & Price Override Reasons - 'Show in POS'

Reasons can be marked to ‘Show In POS’ this will hide them from use on the Cygnus tills if unticked. It allows for a subset of the discount reasons to be sent to the tills while still being able to use them in customer ordering on SRS back office, App or Web. This keeps it simple for till users while working directly in front of customers.

SWAN-3307 - Meal / Kit Items - Component item gross values incorrect

Components for kit and meal items no longer have the gross value apportioned and is now calculated by sell price multiplied by quantity. The net value will continue to have discount values apportioned over the components.

Previously, Gross values were incorrectly being discounted as well, making gross/net sales calculations needlessly more complex.

SWAN-1643 - Replace use of 'Salesman' with 'Salesperson' throughout SRS

The label ‘Salesman’ has been replaced throughout SRS with ‘Salesperson’.

This does not affect the database at this time and reports/prints will be unchanged. Systems outside of SRS back office have not had any changes.

However, a few import/exports have been updated to the new column header ‘SalespersonCode’, including:

  • Customer Export

  • Merchandise Budgets Export

Minimum SRS Version 7.4

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