Thanks for the video, Kevin. I did the basic layout but expanded this for my warehouse. When I go to upload, is i get error code "The values for the fields 'company_id, barcode' already exist (they are probably 'Company, Barcode' in the current model). at multiple rows" I am not sure what is causing this as I used the same template as in this video. Thanks!
I really enjoy your videos as well, I think there will be huge expansion of views at certain point, but until that happens and my comments will get lost in an echo of your fans I'd like to also kindly ask for barcode and maybe rental and its' interconnection with inventory routes. I will have it cracked at the point of eventual publishing, yet I spent quite a lot of nerves that you can spare for others like me. Once again, really cool.
Hey Kevin, Im digging to find out what the workflow might be to have odoo automatically put away products respecting the weight limitations that are set. do you have any videos on that?
Nice, but your put away rule does not work when yu change to 2 steps incoming shipments. Because it goes to WH/INPUT and put away rule cannot be created from WH/INPUT to WH/STOCK/XXXXXX
The resulting bin names make perfect sense. However, not following the logic for creating the stacked layers, to get down to the bin. For example, creating "A" as a location. You would never actually store goods in WH/Stock/A, or in WH/Stock/A/01, so why create them as locations? They are not a necessity to creating the actual bin locations A-01-A, A-01-B, etc. to match your Barcodes for those location. What am I missing in regards to stacking these layers to get down to the actual bin? (Higher level put-away rules for sections, maybe?)
You can certainly simplify the hierarchy. There are a few reasons to created a more granular hierarchy. 1) You can easily see all of the stock in each location. For example if I wanted to know everything in Aisle 1 you can do that much easier. 2) If you wanted to create and use storage categories with specific capacities and put away rules you can apply settings to the higher level location as opposed to each individual one 3) If you want to rename or rearrange the categories you can do so without having to adjust every single location 4) Just for general future proofing - there may exist a reason in the future that will give us more functionality if our locations are more granular like more dynamic put away rules and overflow bins. It is unlikely that not having the hierarchy will provide more functionality in the future. All in all, if you don't see a reason to make it as granular as I did; I don't see any reason not to keep it simple as you suggested.
@@KZAKI - Thank you for the reply. I presumed you had some logic that I was missing. In a million to one coincidence, I mentioned this video in my meeting today, with Alana at Odoo. Seems she is aware of the creator. 😊
![[UNCUT]“ฅนตื่นธรรม”ปะทะ“หมอปลา-ปู่มหามุนี-อั๋นโอกิ”สะเทือนกระทรวงเวทมนตร์ Iคนดังนั่งเคลียร์I10 ตค.67](http://i.ytimg.com/vi/peMD_SAkwNc/mqdefault.jpg)
Thank you Kevin, it is clear. Right to the point.
Excellent video , straight to the point from start to finish. Everything a sales/wh person needs to know without the waffle!
I m an old warehouse supervisor, love, to watch the way u taught.
Clean and efficient, just the way I like it! Thanks for this vid!
Hi Kevin, can you make a video for Barcode setup & use? That can perform actions automaticly according to setting. That will be awesome!!
Thanks for the video, Kevin. I did the basic layout but expanded this for my warehouse. When I go to upload, is i get error code "The values for the fields 'company_id, barcode' already exist (they are probably 'Company, Barcode' in the current model). at multiple rows"
I am not sure what is causing this as I used the same template as in this video.
Thanks!
Great video! What is the combination of letters/numbers to create the barcode?
I really enjoy your videos as well, I think there will be huge expansion of views at certain point, but until that happens and my comments will get lost in an echo of your fans I'd like to also kindly ask for barcode and maybe rental and its' interconnection with inventory routes. I will have it cracked at the point of eventual publishing, yet I spent quite a lot of nerves that you can spare for others like me. Once again, really cool.
Great content I'm in the process of trying to set up a warehouse and this is the sort of stuff thats not readily available. Thanks
Hey Kevin, Im digging to find out what the workflow might be to have odoo automatically put away products respecting the weight limitations that are set. do you have any videos on that?
Utilizing storage categories might be your best bet. I do not currently have any videos on them.
Thanks for this valuable information ❤❤
Nice, but your put away rule does not work when yu change to 2 steps incoming shipments. Because it goes to WH/INPUT and put away rule cannot be created from WH/INPUT to WH/STOCK/XXXXXX
The resulting bin names make perfect sense. However, not following the logic for creating the stacked layers, to get down to the bin. For example, creating "A" as a location. You would never actually store goods in WH/Stock/A, or in WH/Stock/A/01, so why create them as locations? They are not a necessity to creating the actual bin locations A-01-A, A-01-B, etc. to match your Barcodes for those location. What am I missing in regards to stacking these layers to get down to the actual bin? (Higher level put-away rules for sections, maybe?)
You can certainly simplify the hierarchy.
There are a few reasons to created a more granular hierarchy.
1) You can easily see all of the stock in each location. For example if I wanted to know everything in Aisle 1 you can do that much easier.
2) If you wanted to create and use storage categories with specific capacities and put away rules you can apply settings to the higher level location as opposed to each individual one
3) If you want to rename or rearrange the categories you can do so without having to adjust every single location
4) Just for general future proofing - there may exist a reason in the future that will give us more functionality if our locations are more granular like more dynamic put away rules and overflow bins. It is unlikely that not having the hierarchy will provide more functionality in the future.
All in all, if you don't see a reason to make it as granular as I did; I don't see any reason not to keep it simple as you suggested.
@@KZAKI - Thank you for the reply. I presumed you had some logic that I was missing. In a million to one coincidence, I mentioned this video in my meeting today, with Alana at Odoo. Seems she is aware of the creator. 😊
Wow video❤
Getting errors on parent location. And I can't import from Excell. no info regarding this is in the video
🔥