Hi all,
Currently investigating to use fixed bundles for some products. It doesn’t look like it’s possible to revert a product from being a fixed bundle back to being a standard product. We have a client that sometimes switches a product between being a bundle and not. Anyone know if this is possible when using fixed bundles, or do we need to delete and recreate the product? If not possible to switch, does anyone from Shopify development teams know if this is a feature that is on the roadmap?
Hey @Mickey_Binder 
- there’s a bit more info in our docs here, but with fixed product bundles, the “parent” bundle product is composed of already existing product components.
It’s not possible to convert the parent product to a normal product, but its constituent parts would still technically be considered regular products.
Just to make sure I’m understanding things correctly on my end here though, would a flow where when they need to make the product “non-bundled”, they just unpublish the parent product from the storefront (keeping the components “live”)? Essentially, when unpublished, the bundle relationship should remain intact in the backend, so they can easily republish the parent bundle when needed again.
That might solve for their use case here, but let me know if I can clarify anything on my end - happy to help out further!
Hi Alan,
Thank you for you response. The use-case is that the client has products that are some of the time “prepacked” (meaning it’s still a bundle but is a single sku containing everything, so technically not a bundle) and other times it’s a real bundle. It depends on whether the prepacked product is in stock or not. I know this is a bit confusing, but that’s how the client likes to run things. So optimally it would be possible to just flick a switch on the product, and it would either sell as the single sku, or it would sell as the 6 bundle component skus.
But seems like it’s not possible. Do you think it’s something that will be supported as some point?
Thanks
Hey again @Mickey_Binder, no worries, happy to help - thanks for clarifying how they’re using bundles.
I have seen other merchants use bundles in a similar way before, so I don’t think this is a super uncommon use case, but you are correct that the only workaround at the moment would be to delete and recreate the product as needed.
I’ll speak with some folks internally to see if this is on the roadmap and loop back with you here, but at the very least I’m more than happy to put a feature request through for you as I can for sure see how a bundle toggle would be useful. Speak with you here again as soon as I have more info 
@Mickey_Binder :
Solution approach : Create a product as a bundle. your app should have a configuration that results in deduction or no deduction or simple product that resulted in bundle.
when its an actual bundle and you dont want the inventory of simple product to be deducted and only inventory of bundle to be deducted set a configuration value.When your client switches to individual product to be sold switch the config value to allow inventory deduction.
This approach should go provided you can use flow and handle inventory based on condition.
in the order the product will always have th same SKU thats of the bundle.
This approach just solves the inventory issue.
Hey @Mickey_Binder - I was able to speak with our product bundle team on this for you, and confirmed that we don’t currently have a feature like this on our roadmap (either through the native bundles app or the API) in the near term, but I’m going to set up a feature request for you.
I do think @Ankit_Shrivastava’s idea might be a good one to look into as well for a workaround.
Hope this helps, let me know if I can clarify anything on our end here.
Hi Ankit, thank you for your response. It’s a good idea, but will not work for the client. In the case where it’s a prepacked bundle they still want to use the same product, and it’s not possible to switch off getting the bundled products sent along, which is a problem at the WMS
Thanks, hope others are requesting it so it will be implemented relatively soon.