Skip to Content
This question has been flagged
3 Replies
662 Views

Hey,


I have set up a product with a BOM that contains multiple subproducts produced by my company. I have noticed that when I change one of the subproducts, then my BOM always refers to the newest Version of the product. This is problem for our usecase since subproducts are sometimes used across multiple products and a change in the subproduct might affect the function and the certification of the other products. So in our workflow updating the version of a subproduct in the products BOM would always require a ECO with approval.


Does anyone have an idea how to fix this in odoo?


Best Regards

Malte

Avatar
Discard
Best Answer

A product can only have one valid version.  The same with BOM.

If a product is changed, so it must be separated from other you need to create a new product.  Else you will risk they are mixed and used where they should not be used.  

This is not only relevant for BOM and product revision.  All logistics in you company is related to this.  It is about product identification and traceabilty. 

https://www.iso9001help.co.uk/8.5.2%20Identification%20&%20Traceability.html

Avatar
Discard
Author

@Lars Aam

Thank you for the response. This is exactly what i am trying to solve. In the current setup of odoo, if I update one product I am automatically updating all the BOMs that include this product. This automatic update procedure without approval can change all Products that consume that one product without any risk assessment or documentation which is a huge issue for product conformity (also ISO9001: https://www.iso9001help.co.uk/8.6%20Release%20of%20Products%20&%20Services.html)

Do you have any approach on how get odoo to include the component version into the BOM version?

Author

@Lars Aam,
Do you have any approach on how to include this functions to traceability? We still have not found a suitable solution to roll out revisions in manufacturing without accidentally using old parts...

Hi Malte - based on what Lars has said, the logical approach is to rename the original product (e.g. to "This Component v1" COMP01-V1) and create a new product for the current version and change the BoMs to use it.

Best Answer

We're working on similar needs for one customer. Complex products with multiple levels of customization (width, length, color). We don't have the solution yet.

Avatar
Discard
Author

@Cyrille de Lambert
Is there any new update on your customers project?

Related Posts Replies Views Activity
0
Sep 23
472
2
Jul 23
900
0
Feb 22
1695
0
Mar 15
3116
2
Feb 24
1008