Archives
Contributors
Re: Stock valuation based on warehouse/location - food for thought ;-)
Re: Stock valuation based on warehouse/location - food for thought ;-)
Re: Stock valuation based on warehouse/location - food for thought ;-)
Hi Graeme,
you are right. I all to often forget that Odoos "Standard Price" valuation method, is "only" using the default standard price not the actual purchase price. (see https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html) Though i do agree that this is mostly a reporting issue and should be adjustable via specific journal items, i would still prefer a valuation based on cost price. Can't imaging that i would be all to hard to implement this. But it should definitly be done by Odoo S.A. themselves. Did anybody ever raise this feature request? I think if Odoo really wants to compete with say SAP it needs to implement this. It'll be hard to manually adjust that for million stock transaction multi warehouse case.
Best Frederik
Serialisation is neither a qualification nor disqualification. IAS2 is a simple standard largely unchanged since the 70s. Seperately identifiable refers mostly to wjether the organisation seperately identifies it e.g. for a particular customer. E.g a large order at special pricing or a custom manufacture item could qualify. But a bunch of serialised items for general sale that are easily exchanged do not.
Cost method won't do it because odoo does not support it. In cases where everything is custom or non fungible you basically have to use actual cost or serial track svls using fifo. Either is custom dev. I've done both, serial with fifo is easier but not without issues. More recently with v16 making Fifo a bit difficult for my use cases I've reimplemented actual over a small subset of non fungible items. It is manageable but at an entire company catalog scale i wouldn't trust it.
But in truth it is only a reporting issue. If your stock turn is high and you don't have a lot of it it is usually immaterial or easily adjusted for manually during report preparation.
On Thu, 21 Mar 2024, 8:36 pm Frederik Kramer, <notifications@odoo-community.org> wrote:
What does "separately identifiable" mean? Is a serial number enough? I generally don't see a reason why cost price method wouldn't do the job. It is valuing based on every single purchase transaction, isn't it?
Best Frederik
Am 21.03.24 um 01:42 schrieb Graeme Gellatly:
Under ias2 if it is seperately identifiable for a customer it should have its own valuation regardless of warehouse location. The usual 2 ways are actual cost with lot tracking not in odoo standard or a seperate product.
On Thu, 21 Mar 2024, 9:46 am Iryna Vyshnevska, <notifications@odoo-community.org> wrote:
Cost method can be set per product per company, so if warehouses A and B belong to different companies valuation can be different. I hardly can imagine a need to have a different valuation approach for one product in one company as this will create different approaches in valuation in accounting.
On Wed, Mar 20, 2024 at 10:00 PM Abdalrhman Hassan عبدالرحمن حس ن <notifications@odoo-community.org> wrote:
What a methdolgoy !🤔
First time hear about this scenario.
On Mar 20, 2024, at 9:02 PM, Radovan Skolnik <notifications@odoo-community.org> wrote:
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Вишневська Ірина
Vyshnevska Iryna
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 09:41 - 21 Mar 2024
Reference
-
Stock valuation based on warehouse/location - food for thought ;-)
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik
by Radovan Skolnik - 07:01 - 20 Mar 2024-
Re: Stock valuation based on warehouse/location - food for thought ;-)
Hi Graeme,
you are right. I all to often forget that Odoos "Standard Price" valuation method, is "only" using the default standard price not the actual purchase price. (see https://www.odoo.com/documentation/17.0/applications/inventory_and_mrp/inventory/warehouses_storage/inventory_valuation/inventory_valuation_config.html) Though i do agree that this is mostly a reporting issue and should be adjustable via specific journal items, i would still prefer a valuation based on cost price. Can't imaging that i would be all to hard to implement this. But it should definitly be done by Odoo S.A. themselves. Did anybody ever raise this feature request? I think if Odoo really wants to compete with say SAP it needs to implement this. It'll be hard to manually adjust that for million stock transaction multi warehouse case.
Best Frederik
Am 21.03.24 um 08:57 schrieb Graeme Gellatly:
Serialisation is neither a qualification nor disqualification. IAS2 is a simple standard largely unchanged since the 70s. Seperately identifiable refers mostly to wjether the organisation seperately identifies it e.g. for a particular customer. E.g a large order at special pricing or a custom manufacture item could qualify. But a bunch of serialised items for general sale that are easily exchanged do not.
Cost method won't do it because odoo does not support it. In cases where everything is custom or non fungible you basically have to use actual cost or serial track svls using fifo. Either is custom dev. I've done both, serial with fifo is easier but not without issues. More recently with v16 making Fifo a bit difficult for my use cases I've reimplemented actual over a small subset of non fungible items. It is manageable but at an entire company catalog scale i wouldn't trust it.
But in truth it is only a reporting issue. If your stock turn is high and you don't have a lot of it it is usually immaterial or easily adjusted for manually during report preparation.
On Thu, 21 Mar 2024, 8:36 pm Frederik Kramer, <notifications@odoo-community.org> wrote:
What does "separately identifiable" mean? Is a serial number enough? I generally don't see a reason why cost price method wouldn't do the job. It is valuing based on every single purchase transaction, isn't it?
Best Frederik
Am 21.03.24 um 01:42 schrieb Graeme Gellatly:
Under ias2 if it is seperately identifiable for a customer it should have its own valuation regardless of warehouse location. The usual 2 ways are actual cost with lot tracking not in odoo standard or a seperate product.
On Thu, 21 Mar 2024, 9:46 am Iryna Vyshnevska, <notifications@odoo-community.org> wrote:
Cost method can be set per product per company, so if warehouses A and B belong to different companies valuation can be different. I hardly can imagine a need to have a different valuation approach for one product in one company as this will create different approaches in valuation in accounting.
On Wed, Mar 20, 2024 at 10:00 PM Abdalrhman Hassan عبدالرحمن حس ن <notifications@odoo-community.org> wrote:
What a methdolgoy !🤔
First time hear about this scenario.
On Mar 20, 2024, at 9:02 PM, Radovan Skolnik <notifications@odoo-community.org> wrote:
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Вишневська Ірина
Vyshnevska Iryna
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
by Frederik Kramer - 09:41 - 21 Mar 2024 -
Re: Stock valuation based on warehouse/location - food for thought ;-)
Hello,
We actually have the same accounting practice in Macedonia. Long ago I wrote a design doc but never got to implement it.
This was concerning though only average price costing as this was the one most commonly used here. My conclusion was the same as what Radovan describes for FIFO. That is we would need to track cost price per warehouse and use it for the valuation entries.
Additionally also what is not part of Odoo and what comes naturally if you have different costing per warehouse, is the need to have inter-warehouse valuation entries created. In some sense this is like a separate company but at the end you would want to see that in one financial statement.
Kind Regards,
Kiril
On 21.3.24 08:36, Frederik Kramer wrote:
What does "separately identifiable" mean? Is a serial number enough? I generally don't see a reason why cost price method wouldn't do the job. It is valuing based on every single purchase transaction, isn't it?
Best Frederik
Am 21.03.24 um 01:42 schrieb Graeme Gellatly:
Under ias2 if it is seperately identifiable for a customer it should have its own valuation regardless of warehouse location. The usual 2 ways are actual cost with lot tracking not in odoo standard or a seperate product.
On Thu, 21 Mar 2024, 9:46 am Iryna Vyshnevska, <notifications@odoo-community.org> wrote:
Cost method can be set per product per company, so if warehouses A and B belong to different companies valuation can be different. I hardly can imagine a need to have a different valuation approach for one product in one company as this will create different approaches in valuation in accounting.
On Wed, Mar 20, 2024 at 10:00 PM Abdalrhman Hassan عبدالرحمن حس ن <notifications@odoo-community.org> wrote:
What a methdolgoy !🤔
First time hear about this scenario.
On Mar 20, 2024, at 9:02 PM, Radovan Skolnik <notifications@odoo-community.org> wrote:
Hi, today I have had an interesting conversation about Odoo's shortcoming regarding stock valuation. I was told it is common practice and in some cases part of the legislation in here to have a different stock valuation in different warehouses/locations. For example I commonly purchase a certain type of notebook which I store in a warehouse A from which I also sell it. Now I have won a big contract to supply 500 of such notebooks somewhere. I contact my supplier, arrange a big discount for the 500 notebooks and have them sent to warehouse B (a project warehouse). The requirement would be that the valuation of stock in warehouse B is different (based on that heavily discounted purchase) from the one in warehouse A and these 2 shouldn't mix. Have you ever encountered such requirement? Is this common situation? I do not really need to solve this but it just got me curious. I guess it should be possible to create such a thing but that would mean patching stock_account, purchase_stock, stock_landed_costs and mrp_subcontracting_[purchase|dropshipping] and we would have possible as many stock valuation layer entries for each product as warehouses/locations that we deal with separately. Any inputs/comments would be welcome. Best regards Radovan Skolnik
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Вишневська Ірина
Vyshnevska Iryna
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Lambda IS DOOEL - free/open-source information systems implementation & development Kiril Vangelovski - consultant/developer web: https://www.lambda-is.com tel: +38971753823
by Kiril Vangelovski - 08:56 - 21 Mar 2024