You’re correct, this has been asked before (yet I’m struggling to find valuable content). You may want to expand your search with terms like “revision”, “version”, BOM, etc.
This is a complex issue and need planning and understanding of how your decisions now, impact worflows later.
From what I’ve seen so far I can’t think of any reason NOT to set revisions up as variants. You still have the problem of creating new BOMs manually all the time though. Could be pretty error prone if you use multi-level BOMs.
less related topics, but may have good info:
If quantities and performance differ, don’t force variants, you’ll regret it later lol. Variants work when items are basically interchangeable, same behavior, just different attributes like color or size. In your case 100g vs 90g already breaks that logic, BOMs, costing and MRP will get messy fast. Go with separate items per manufacturer, it keeps stock, pricing and planning clean. Then handle substitution via Item Alternative or in BOM with allowed substitutes, so you still keep flexibility wit…
Hi All
we are planning to create an app for PLM and are going ahead with the following use cases:
New item code creation process
Engineering change for Items, BOMs and Routings
Maintain versions
‘Where used’ report to assess the impact of the item being changed.
Allow impact of change on ‘where used’: certain items of user’s choice, all the items, do not allow the impact but disable them instead