- Mailing Lists
- Contributors
- Re: Stock valuation based on warehouse/location - food for thought ;-)
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
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 ;-)
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
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
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