Update to ASN update logic

Several issues have been caused by clients amending ASN’s at various stages so we took the step to restrict access to this.

However, we are increasingly seeing issues where new clients (who may have had access to Mintsoft with their previous 3PL) expect access and therefore, are making aforementioned changes.

Could access to making changes to an ASN be incorporated into ‘Customer Account Settings’ in much the same way as editing order status. Ideally this would be at client level.

This way, the 3PL control access to ASN changes at various stages. Currently cannot see a case for anything other than NEW and AWAITINGDELIVERY.

In addition to this (and in truth where this has spawned from) is the ability to edit ASN’s via the API up to a certain status.

Currently this is restricted to ‘NEW’ (there is no documentation to advise of this which has caused a real issue for us) but there are multiple business cases to expand this, as long as robust processes are in place. Allowing a client to amend an ASN at AWAITINGDELIVERY would be of great benefit as it would save hours of manual data corrections.

For example, a client places an order via the API, their supplier offers and additional or alternative product so currently, this has to be done manually but allowing the ASN to be amended at additional status removes this requirement.