Hi all. We are working with some customers that require GS1 standards and use of data sync. Some of the items we use are assortments so they require us to set them up as a parent/child relationship. The issue we are having is the parent item is all that we need to maintain the inventory on as we do not sell by the child number, parent only. The most ideal situation would be to have an inventory item for sale as the parent and create non-inventory items for sale as the child so they do not carry any inventory. However we cannot do this as there is no way to relate inventory and non-inventory items as parent/child. Any suggestions? Thanks!

At the end of the day - what do you need out of a parent child relationship? Is it just the naming convention of "Parent : Child" or is there some other function they need? You could emulate the naming structure with custom script - and then use a custom field with a type of list/record with the list type set to item. Then you could define your parent there. - You're right, this would result in a sublist on all items.

The real need for the children is to maintain the information of the products essentially. The parent is what we sell by and maintain the inventory on. But yes we agree the sublist would be sufficient, just not ideal since it would carry throughout the rest of the items. I appreciate the help!!