A Dimecres, 25 de gener de 2012 14:17:35, Cédric Krier va escriure: > > I think it should. Of course, we can discuss on what's the best default > > behaviour of stock_lot module, but I'm sure that many companies will need > > to be sure that the current stock levels are ok and that includes the > > exact lots available. If you cannot rely on that, it has no sense to > > manage lots (at least, in many use cases). > > For me, I see it as a blocking stuffs that will be very annoying. > If the user pick a product with the wrong lot number, the next guys who > will need to pick the same product, the system will prevent him to do it > because it is the wrong number.
Take into account that in many cases it is the system that creates the lot number. You're probably thinking on a use case of a > For me, it should really be like a tag and even we should be able to > modify it after the move was done. And it makes no sense to have the > system telling to the user to pick the lot number X out of thousand of > same products from a location. I fully disagree. We've got installs in which it is the system that tells the users what lot they should use and it is a hard requirement. The lot can bring other information such as Expiry Date which may determine which lot is used. Also note that in many places which lot was used is very important. If the user did not put the correct lot when the product arrived, then it must be corrected. The same way you make an inventory when stock is not correct. -- Albert Cervera i Areny http://www.NaN-tic.com Tel: +34 93 553 18 03 http://twitter.com/albertnan http://www.nan-tic.com/blog -- [email protected] mailing list
