Have this strange situation where the two parts to a customized bundle are in stock and show in checkout but the bundle itself is marked as sold out. To be clear it still gets to proceed to checkout. Is this a bug or am I missing some details?
Hey @DanielPatricio - thanks for reaching out!
This is likely tied to how customized bundles are handled versus fixed bundles. For fixed bundles, Shopify maintains sellable quantity on the parent bundle variant based on component inventory. For customized bundles using cart transforms, the parent bundle line can still have its own availability/display state, while the component lines are checked in cart/checkout if that makes sense.
So if the components are in stock and checkout can still proceed, this may be the cart UI reading the parent bundle variant as sold out, while checkout validation is correctly validating the components. I’d check that the parent variant is marked with requiresComponents: true, especially if this is in POS, since that’s required for complete cart transform support there.
Hope this helps, but let me know if I can clarify anything on our end here.
Thanks Alan but I believe requiresComponents is for fixed bundles, our customized bundles cannot use it
requiresComponents is on the variant object, we cannot just mark every variant.requiresComponents to true unfortunately. Almost all our merchants will let the customers buy a bundle component individually or as a bundle.
Are my assumptions correct here?
Hey @DanielPatricio - you’re right that this is a variant-level setting. The key distinction is which variant it’s applied to.
requiresComponents isn’t limited to fixed bundles, but you wouldn’t set it on every component variant. For a customized bundle, it should only be true on the dedicated parent bundle variant. The component variants remain unchanged, so customers can still purchase them individually.
Our customized bundle tutorial shows that setup here: Add a customized bundle function
If you’re also using an individually sold component as the parent variant, then your concern makes sense to me though. A separate bundle-only parent variant would usually be needed. Since checkout is succeeding,
Are you using a dedicated parent variant for the bundle? If you’re open to sharing a bit more info on your set up I can definitely take a look here. Let me know if you’d rather set up a DM to share and I can get that done on my end 
As we use it today we do not have a parent variant / product which is why we can’t adjust the setting.
Would really prefer not to have to add an additional product for the parent as it is one more thing to maintain for a merchant and our bundles tend to be quite ephemeral so would prefer not to clutter up a merchants product listing.
Ah, understood @DanielPatricio .I definitely get why creating and maintaining a product for every short-lived bundle wouldn’t be a good fit.
Also, just so I capture the right gap here: if POS stopped showing the “Sold out” status, would your current setup otherwise work as intended, or are you seeing other limitations from not having a parent variant? Just wanted to make sure I capture the feedback correctly.
Either way, I’m happy to pass along the catalog-maintenance concern and the misleading “Sold out” state. I can’t promise a timeline, but I want to make sure the gap is captured correctly.
Thanks! Yes if the POS just stopped showing the sold out status that would be fine.
It has been working very well for us so far on the online store, this issue is isolated to POS.
No worries @DanielPatricio - thanks for confirming. I’ve passed this along as a feature request.. I can’t guarantee whether or when this will change, but the feedback is captured on our end. Thanks again for flagging this!
Let me know if I can help with anything else on our end here.