Can you add a liquid field to distinguish if a product is a bundle parent product?

Online Store and Theme Development
1

Short description of issue

Many themes don’t recognize these virtual bundle parent products

Reproduction steps

Try a theme that activates the Quick Add button on the collection, and have the store sell bundles.

Additional info

As a result, these themes show a quick add button on the product cards of the collection pages. Some themes may add a quick add-to-cart footer on the product pages.

When customers click the quick add-to-cart buttons, they don’t work. Customers think that the products are not working and leave. They don’t enter the PDP, which lowers the bundle conversion rate.

At the same time, I want Shopify to enforce theme developers to offer a better support for virtual bundle products. Most themes don’t handle these products as non-purchasable. My app offers custom bundles. This issue happens almost every week.

What type of topic is this

Feature request

2

Big +1 on this — we run into it almost weekly too, and the failure is silent, which is the worst part: the shopper doesn’t see an error, they just decide the product is broken and bounce.

A few workarounds that have held up for us until (hopefully) a real flag exists:

  • Tag the bundle parent (e.g. bundle-parent) from the app or a Flow automation, then guard the quick-add snippet with an “unless product.tags contains” check and render a “Choose options” link straight to the PDP instead.
    • If you control the app side, write a boolean product metafield on the parent and check that instead of tags — merchants edit tags, they rarely touch metafields.
      • Rough fallback for themes you don’t control: parents that break quick add almost always have a single default variant with no independent inventory, so combining product.has_only_default_variant with an inventory check catches most of them.
    • That said, none of these should be necessary. The Storefront API already exposes requiresComponents on the variant, so the platform clearly knows what a bundle parent is — surfacing the equivalent in Liquid, and having the reference themes respect it in the quick-add block, would close a real conversion gap rather than leaving every bundle app to patch themes one at a time.
  • One CRO note from building on this: the most reliable fix we’ve found is to stop relying on the theme’s native add-to-cart path for bundles entirely. Rendering the bundle builder in its own theme app extension block that posts to /cart/add itself means quick add never touches the parent product, and you keep the AOV upsell in the cart drawer where a theme update can’t break it. That’s the approach we took with Sleek Bundles, and it removed this whole class of bug for us.

Happy to share the tag-guard snippet if it’s useful to anyone.

4

Hey @Benny_Chan and @Mubashir_Hassan :waving_hand: thanks for raising this and sharing the impact it has.

You’re right that theme Liquid currently doesn’t expose whether a variant requires bundle components. This leaves theme developers without a generic way to replace quick add with a product-page or app-picker flow, which can result in non-working add-to-cart controls. Thanks for sharing the workarounds as well. That context may help other developers encountering this.

I’ve submitted a feature request covering both a Liquid signal for bundle parent variants and guidance for bundle-aware theme behaviour. We’ve received similar reports before, and this additional context helps show the recurring impact. I don’t have a guarantee or timeline to share, but your report has been documented and shared internally for review.

Hope this helps!