Auto Pick - Not taking stock from Bin Location Alpha Numerically causing stock quantities to be wrong

Chris

Hi Team,

The auto pick function is broken. When using FIFO-Batch and where the stock is split over various bin locations, the online platform IS NOT taking the stock from bin locations alpha numerically. This gives us issues when it comes to tracking stock quantities accurately within each bin location.

Unlike the WMS (which does display the stock by Bin Location Alpha Numerically whilst following FIFO rules), unfortunately the online platform with the Auto Pick function does not behave in the same manner. This gives us the following issues;

1. We cannot use the "Auto Pick" button on the Pick Tab of a Sale Order

  • Occasionally, we may want to complete a quick electronic fulfillment of the SO
  • However, because the system does not pick from the bin alpha-numerically it creates a headache
  • This is because in real life, we've taken the item from a location in Axx.xx.xx, whereas the system may have taken it from Fxx.xx.xx
  • In fact, even if we try to manually select the Axx location for the pick tab on the web platform, the system does not allow us to select it (the stock is all received on the same PO with the same received date)

2. BOM with Auto-Assembly

  • We use BOM with Auto-Assembly for bundle products
  • Auto-Assembly is required for Shopify to have the correct stock quantities
  • Our bundles are not “made in advance”, so on the WMS we use the Expand/Collapse function on the WMS, which works fine.
  • However, the problem is that the Auto-Assembly uses the “Auto Pick” function, which is not taking stock from the bin locations Alpha-Numerically whilst following FIFO rules.
  • So in real life, we have stock in Axx.xx.xx locations in which we pick from, but the system may have taken stock from a different location such as Fxx.xx.xx
  • The net result is that we're physically picking from Axx because we have stock there, but the system may take from Fxx, even though they are the same stock, received on the same PO.
  • This results in our stock quantities being incorrect in real life for each bin location.

3. Stock Quantities

  • The main net issue as a result, is that our bin locations will have the wrong quantities.
  • This gives us issues, as over time, the issue with each BOM keeps adding to the problem
  • Later on, when we go to complete a bin transfer in real life, as an example, you may see a carton of 10 units in Fxx, and we think you'll be able to transfer those 10 units to Axx, but the system only says there's 6 in Fxx but in real life there is 10. And in real life there is 0 in Axx, but electronically, there is 4. Do you guys see the issue now?

Summary

  • Can someone as Cin7 please please please - fix the Auto Pick function, where it picks from bins alpha-numerically whilst following FIFO rules
  • We need to be able to accurate track stock quantities in our bin locations
  • Many thanks.

Related to

4

Comments

3 comments

Date Votes
  • Comment author
    John K
    • Official comment

    In regards to point #2, would it be helpful if an auto-assembly was created in draft status, allowing manual picking from the true physical location?

  • Comment author
    Chris

    Hi John,
     

    In regards to point #2, would it be helpful if an auto-assembly was created in draft status, allowing manual picking from the true physical location?

    • When you say auto-assembly created in a draft status, if you're talking about the assembly job status, then no. 
    • This is because in a draft status, the individual stock quantities that make up the BOM sku, have not been allocated / consumed, and therefore this will not trigger any stock updates to Shopify, resulting in overselling of stock.

    --

    • However, I did go and run a little test here with a manual assembly.
    • I noted that if I authorised the "Assemby Order” tab, this consumes / allocates the listed items inside that BOM, so it will then update Shopify stock quantities accordingly, which is good as it stops the overselling problem.
    • I noted that this now sets the assembly job overall status as “Authorised” with the Pick Tab not completed.
    • Now I don't know how we would be able to use the WMS > Pick for a SO, and somehow have the system complete both the “Pick” tab in the Assembly Job and The Pick tab in the SO at the same time? If there was a way, then perhaps that could work?
    • Though I don't know if that's easier to program / provide a solution like that, compared to having the online platform for auto-pick follow fifo rules, and where the same stock is split over various bin locations, then simply have the auto-pick take stock from the bin locations alpha-numerically, like the WMS does.
    0
  • Comment author
    Simon (Sitech Industries)

    This is definitely a problem. Perhaps a more flexible way might be to define bin groups in order of picking, then we could put all our ground bins first. Or your A## bins before your B## bins.

    For a warehouse of the size which we're both dealing with, we'd also be happy with managing the assembly operation manually (as @John K suggests). But either way it is absolutely crucial as you mentioned to commit stock immediately so the components aren't sold in the meantime. I mentioned that on my thread here:

    https://help.core.cin7.com/hc/en-us/community/posts/12549757467279-Auto-Order-an-Assembly-rather-than-Auto-Complete-an-Assembly

    0

Please sign in to leave a comment.