On 25 January 2012 22:22, Bertrand Chenal <[email protected]> wrote:
> Le Wed, 25 Jan 2012 19:54:14 +0100, > Albert Cervera i Areny <[email protected]> a écrit : > > > > > Or update stock module to take care of lot with a default lot NULL. > > > > Now that you mention it, I think that lots are so common that it > > would probably make sense to put them in the default 'stock' module... > > Lot is common, but behaviours are diverse. So maybe we should define > lot in stock but without any important constraints or behaviours. > > But to be sure that we do not forget anything we need to gather > all/most of the possible use cases and enrich the blueprint. > > In the ERP of my employer we operate an FIFO system to track cost prices for a given product, it sounds similar to Lots. Goods received details such as quantity, cost, order ref, received date are all tracked against stock records for a given branch, then when the items are sold the quantity at the top of the stack is reduced, when it reaches 0 the next "lot" is then at the top and it's associated cost is recorded against sales. I haven't looked at the Tryton stock / product / invoice way of doing things so do not know if this scenario would be handled differently in tryton. HTH Craig -- () ascii ribbon campaign - against html mail /\ -- [email protected] mailing list
