I dislike that i installed a bundle app and it turns out all the products created with that app are soft locked, if i uninstall the app the products are no longer usable, I break analytics history. And yet the underlying bundle information isn’t mysterious once you understand it, I could write a cart transform and take over these products pretty easily.
Anyway, this post is for hoping someone knows how to fix a product that has been “owned”. I want it for my own app, because I have worked out how to enhance my products with bundle variants, but they are then softlocked if they want to remove the variant they can’t revert the product to stand-alone. it’s demonstrated by the screenshot which is what happens when the app is removed.
Thanks for raising this Si! This is an architectural constraint with how bundle ownership works. Once an app assigns components to a product (or claims ownership via the claimOwnership field), that ownership is permanently locked to that app.
Unfortunately the only path forward right now is to recreate the bundle products under your own app. You can use productBundleCreate for fixed bundles, or productCreate paired with productVariantRelationshipBulkUpdate if you need more control over the variant-level component mapping. Your app will automatically become the bundle owner on the new products. You could then set up URL redirects from the old product handles to the new ones to preserve some of the SEO, though analytics history won’t carry over.
I’m raising this feedback internally as a feature request. The inability to transfer bundle ownership between apps is a real friction point for developers building in this space. If you have anything else to add about your use case, that context is helpful for informing the feedback.
1 Like
Thanks Donal! I look forward to seeing how it develops.
1 Like
