Hi @Jeff96 ,
Thank you for your feedback. I would like to invite you to the Distribution Roundtable at Summit that will be seeking feedback and focused discussions about Acumatica WMS Pick, Pack and Ship. It is scheduled for Wednesday at 1PM.
Please let me know if you are able to attend. If not, i suggest that we do a OneonOne session with you post-Summit. If you are having difficulty registering for the session, please let me know.
-Dana
Hi @Jeff96 ,
Thank you for your feedback. I would like to invite you to the Distribution Roundtable at Summit that will be seeking feedback and focused discussions about Acumatica WMS Pick, Pack and Ship. It is scheduled for Wednesday at 1PM.
Please let me know if you are able to attend. If not, i suggest that we do a OneonOne session with you post-Summit. If you are having difficulty registering for the session, please let me know.
-Dana
Sorry, I will only be there on Monday.
Hi @Jeff96 ,
Suggest that we connect after Summit and have a OneonOne session to do a deep dive into your feedback - looks like you have valuable insights!
Thanks again,
Dana
@Dana Moffat Has there been any traction on this? I work with a retailer with a similar combination of issues/frustrations stemming from the rigidity and limitations of the Batch Picking workflows. Another user referenced these same issues in another more recent post, but it doesn’t seem (at least from the customer’s perspective) that this is on Acumatica’s radar.
Some of these issues (such as being unable to pull product from alternate, potentially better-in-context locations than the one specific location assigned) can be so disruptive as to cold-stop several team members and require managers to interact, while others tend to grow into a “Swarm of Gnats” situation, where no one issue is particularly bad, but the combination of them is continuously frustrating.
I for one am an open book. AMA. I’ll give any and all feedback!
Hi Dana and Acumatica team, #3 (Once a picker scans a picking sheet, there is no way to go back. If someone else wants to pick it instead, or if you want to cancel the picking sheet, it won’t let you) on this list is critical and carries a lot of business risk.
For instance, if someone needs to leave abruptly for an emergency, or is not finishing an order and sick/on vacation the next day, there is no way for us to continue the order without them or their credentials. In the end our customer is affected.
We are very close to fully implementing WMS but small issues like this are making us scratch our heads as it makes no sense why this limitation even exists.
Tagging @Mike Bradshaw our new PM for Acumatica WMS.
Thank you @NickSearle for reaching out and providing feedback.
For instance, if someone needs to leave abruptly for an emergency, or is not finishing an order and sick/on vacation the next day, there is no way for us to continue the order without them or their credentials. In the end our customer is affected.
I’ll also add other edge cases, which are frustrating:
- Users going home sick during a single day who neglected to close their pick lists create landmines for the shipping team downstream of them. This is an entirely realistic and common-at-scale scenario.
- What if, for some reason, the user was removed from the system or deactivated by an admin (ex an unexpected employee termination or departure). In these scenarios, you can’t even hijack the system to “Use as” the employee. While this wasn’t what I’d consider common within our org, it did happen more than a few times over the years and has been a cold-stopper when it occurs during our peak season.
- When some or all of the other shipments have been confirmed due to having been shipped, you effectively become trapped and are forced to “solve” the error in a way by brute forcing it all the way through, creating new problems along the way. This is also only if it’s possible to do so; We’ve experienced rare issues where a pick operation apparently didn’t register, but the picklist would be complete, creating scenarios where picklists are effectively blocked forever and require a database assist from support to resolve.