When configuring Product Bundles, each component can only be recognized by the main SKU of that component product; the product aliases are not visible to the bundle configuration.
I understand this is the current intended design — bundles reference only the main SKU of each component. While that works during the initial setup, the problem arises later, when we need to switch the main SKU with one of its aliases. In those cases, all bundles that were previously configured with the old main SKU will silently lose that component, because the bundle does not recognize aliases.
This creates a serious operational issue: incoming orders for that bundle will not pull the component product, leading to fulfillment errors that are very difficult to detect in advance.
This scenario happens easily when we merge products and choose a new SKU to become the main SKU, while the original main SKU becomes an alias — something your interface currently allows without warning or any safeguarding.
It would be extremely helpful, actually absolutely necessary, if this behavior could be improved or safeguarded, so bundles remain intact even when SKU roles are switched.
