Developer forum

Hey Scott

The reason is that the stock is managed for each item in the parts list and not the master product / bom container it self. Especially when you have a configurable product where you can change which of the other products you want, that comes in handy.

Enabling stock in the UI for the master would be simple, but would not work since stock is managed on the actual products instead. So it would require an option on the BOM container that specifies where stock should be managed - on the master or on the products in the BOM. (Could also be handy to specify on a product if stock should be managed or not)

One solution could be to create a 'virtual' product for the stock keeping part and let that be part of the BOM product - and somehow hide it during rendering and just use the stock information - something like this

• BOM container
  • SKU 'virtual' product (hidden in frontend)
  • Product 1
  • Product 2
  • etc.

I am not sure UOM will work on part list products though.

Let me hear if this could work.

An other alternative would be to just create a regular product, and create a related product group that contains the product references that the BOM product consist of. Then you have full stock keeping and UOM features on the main product.

BR Nicolai

Hi Nicolai,

Thanks for the detailed reply. Now that I know the reasoning, I think that we can create a workaround. So far, the purpose of the UoM stock value is for display purposes only, so we could even use a custom field called DefaultUoMText. And you're also right that the relationships between products and children is also mostly cosmetic, to display a parts list (the parts in the product) as information on the product detail page. So related products could be used, as you suggested. So that gives us two options. We'll run with one of those.

Thanks!

Scott