I would like to inquire if there is a way to manually select the destination bin from existing ones, instead of having a new one generated automatically. Are there any configurations or alternative methods to achieve this?
As far as I know there is not a way to do this automatically for every shipment into a location (although maybe developers can weigh in on whether there is a configuration property for receiving). However, when you receive you can absolutely select a different destination bin, either by items or by shipment. On the receiving screen, there is an empty bin location field at the top of the list. This has a dropdown of all the bin locations in your current depot. If you select another bin in that field, it will update the receiving bin for all items in the shipment. Or you can click on the bin location dropdown for any individual item to choose a different bin.
Hope this helps! Let me know if this isnt what you were looking for.
First Thank you for your respond.
I don’t know if I did wrong settings, but I can’t find my list of bins in the current depot.
I did whath have you said, but I got only the generated receiving bin.
see pictures below
As shown in the screenshot, there is an active location called “EG - Receiving” with the “Receiving” Type (INTERNAL) and below there is the automatically generated bin. Same settings, however I cannot select EG as receiving bin. The other bins do show up for me though…
I wanted to provide an update regarding the issue. After following your suggestions, I checked the API endpoint responsible for populating the Bin Location dropdown. Unfortunately, I’m still encountering a problem as the data returned by the endpoint is empty.
Here is a screenshot of the response I received when accessing the endpoint:
Once we figure out what’s going on with the missing locations, you can disable the creation of these “dynamic” receiving locations (assuming you don’t want them) by adding the following line to openboxes-config.groovy.
On a side note, we have plans for improving the “receiving” and “putaway” features to support mobile workflows and implement automatic slotting algorithms so you don’t need to manually choose the “bin” or “receiving” location yourself.
In fact, we made a few improvements within a “fork” of OpenBoxes last summer (for a short-term implementation) that allows you to configure a slotting algorithm for each warehouse. In this instance, we implemented a very basic algorithm (“slot to the closest free space in the warehouse”). But, my thought was that we’d be able to expand this to include more complex criteria like weight, dimensions, classification, etc. We also built a proof-of-concept mobile application for this implementation that allows a user to receive one item (pallet) at a time using a barcode scanner like a Zebra device.
I’m very excited to migrate those changes from the fork to our core OpenBoxes repository. And we’d be very happy to solicit feedback and requirements for any improvements you’d like to see in current and/or future functionality.
I hope this message finds you well. First and foremost, I wanted to express my gratitude for your help. I wanted to let you know that the solution you provided worked perfectly for me as well! Thank you so much for your assistance!
On a related note, I noticed that you mentioned your work on the slotting algorithm, which has piqued my interest. I would be delighted if you could kindly direct me to the branch or location where I can find your work on this fascinating topic. I am eager to learn more and explore the insights you’ve gained through your research.
Once again, thank you for your invaluable assistance, and I look forward to hearing from you soon.