WMS # Update After Shipment
under review
B
Brantley Armour
Would like the ability for a permission level to be set so that after an order is already shipped, someone with specific permission can still go in and update the WMS # in and then re-run the WMS update.
Case scenario, Ops deletes a box and therefore the WMS # is deleted and they just manually add a box back. This causes sync issues between systems forcing us to create tickets for Synapse, in my case, to update the order to shipped with tracking number etc. Would be more streamlined if I could add the WMS # in techShip then just re-run the WMS feature so that everything is in sync again.
Thank you!
Edward Aguiar
under review
B
Brantley Armour
Our issue with the restricting add/remove boxes is there are instances where we do need to add boxes due to the type of item shipping is only a single item number, but it goes out in two boxes. Current logic only allows me to restrict both add and remove. If those functionalities were split out into two separate settings, that would also help. If Ops added too many boxes and needed to delete, they would have to delete the batch and re-import, but keeps integrity of WMS carton info.
This would also be an acceptable alternative to our issue we are looking to solve.
If we proceed in this direction, only the portal admin will have permission to perform this function, as this functionality needs to be restricted.
--- I agree that if this is the approach, it is limited only to the portal admins to fix. I understand the concern regarding re-aligning the systems manually so maybe it is more than just allowing the update of WMS # to also allowing package content updates etc. which I understand is a bigger ask and scope, but would resolve the concern. We specifically would not encounter these international concerns as much, but understand we also have to look at it from a holistic viewpoint and ensure a fix would benefit everyone in all situations.
I do appreciate the update as we work together to figure out the best solution for all.
Edward Aguiar
The issue you are having is with ops deleting a package and then adding it again.
We could add the option to update the package ID on the web client. If we proceed in this direction, only the portal admin will have permission to perform this function, as this functionality needs to be restricted. The problem with this approach is the effort in getting the carton information updated manually. In the case of multiple packages, it may be hard to tell which package is associated with which WMS IDs since, from what we see, the user has deleted the package and, with it, is deleting the content. If you are shipping international orders or want to generate packaging documentation on the techSHIP side, you will also run into issues as the content of the package is destroyed when the package is deleted.
The alternative is preventing desktop client users from adding/deleting packages. Changing packages must then be performed in the WMS first, and the order must be reimported. This restriction will not be expanded to the web client at this time. The benefit will be consistency between techSHIP and WMS systems. The disadvantage is that it will be limited today to only desktop clients.
We will review both versions and look at adding it to the roadmap.
Edward Aguiar
Merged in a post:
Modify/add carton info after orders were processed.
B
Brantley Armour
We need to figure out a way to manually go back and update the WMS carton # after shipment so we can re-run WMS and the tracking info update our WMS (Made4Net/Zethcon/Synapse) to shipped status.
We have been dealing with for several months me having to submit tickets to Synapse in order to update orders to shipped status with tracking informatoin because for whatever reason the WMS number is missing when shipping from techShip desktop app and we have no visibility to know that.
I have been thinking that Ops is deleting the box and therefore the WMS number is being lost, but it is occruing way too much to be the case. I am thinking there is an issue with the API pull potentially. We need the ability to add boxes in techShip, but removing can be challenging if we have no way to see the WMS carton in techSHip desktop and add/change etc. Only option within techShip is to disable add/remove and we cannot do that either since we need to add.
In short what I would like to accomplish would be:
- To have a specific permission level or something to be able to go back on a shipped batch and re-add the WMS Carton # so we can then re-run the WMS. We should have a way to update the WMS # on the package after shipment to mitigate the need to submit tickets to have Synapse update orders.
- To have the ability within techShip Desktop to see the WMS#/edit if needed so we can ensure every order has at least one WMS# associated with it. (We do have scenarios where we will not have a WMS# associated with a box because it is one item but ships in two boxes in our WMS).