Cart Transform API bug - customized bundles #378
Replies: 14 comments 10 replies
-
I experience a very similar issue when using the same parentVariant for multiple customized bundles, except I only use merge operations. I could see a possible solution where not only the parentVariantId but also the title gets taken into consideration before merging effectively different bundles together and keep them separate cart items instead. |
Beta Was this translation helpful? Give feedback.
-
@horst7000 I've tested using only merge operations targeting the same parent variant with different child component variants and I'm also experiencing bugs. I'm wondering if the only way around this problem is to create a new parent variant for each bundle possibility. This is not ideal though because when bundling products that have several options/variants we will need to create lots of variants. The ideal scenario for us would be having a single parent variant and being able to select the child component variants from a product selector to attach to that parent dynamically. |
Beta Was this translation helpful? Give feedback.
-
Any update regarding this one? I'm experiencing the same issues with the merge operation. |
Beta Was this translation helpful? Give feedback.
-
Confirming we're experiencing the same issue. I flagged this in a recent AMA on Discord and didn't get a response beyond the initial saying its supposed to work (ie, create two bundles, not a single combined bundle) |
Beta Was this translation helpful? Give feedback.
-
Any update on this? This is the biggest blocker for us that prevents us from using native bundles. |
Beta Was this translation helpful? Give feedback.
-
Converted to a discussion as this appears to be a feature request. |
Beta Was this translation helpful? Give feedback.
-
Running into the same problem trying to create custom bundles by merging multiple items into a parent. Works fine until you add more than one bundle with different child products because in the cart it's seen as the same parent item and groups them under the same cart line item. Make's it basically unusable for custom bundles unfortunately. Would love to hear any potential solutions or any plans to address this, feels like an incomplete feature right now. |
Beta Was this translation helpful? Give feedback.
-
Update - Sorry for the delayed response but we have identified the issue and are working on a fix. I'll keep you posted here once the fix is merged. |
Beta Was this translation helpful? Give feedback.
-
We made some changes, can folks here confirm if they are still facing this issue? If so can you share the steps to replicate, along with your development store url? |
Beta Was this translation helpful? Give feedback.
-
We have the same issue when multiple number of the same bundle exists in cart. After navigating to checkout the price update modal is shown and child components are added back to cart. Example output: |
Beta Was this translation helpful? Give feedback.
-
Facing the same issues as Saeed mentioned, Once we add more than one quantity of bundles in cart, then shopify adds all other items to the cart as individual products and it messes up everything.. |
Beta Was this translation helpful? Give feedback.
-
We are having an issue that is quite similar: When I add products (= one bundle) into cart, the cart transform is applied correctly. But if I go back to the cart page, remove that bundle, then create a new one with different products (but the same ParentVariant), it's fine on the cart page, but in the checkout I still see the old bundle. It's like the checkout page is cached but shouldn't be. Also it breaks when I change the "bundle" product quantity on cart page. It will split it into individual products instead of showing it as a bundle. @siddhantbajaj Are you guys aware of these issues? Any ETA when it might be fixed? We have already launched "native bundles" live to the merchants and now we're getting bad reviews because of issues like that what we're not in control of. |
Beta Was this translation helpful? Give feedback.
-
I'm experiencing the same issue as @stevekaran. I have a working merge function, but after increasing quantity in the cart it'll increase component quantities while the parent always remains at 1. I'd rather have the opposite of this, where only the parent qty is changing. Though when I define a specific item count for the merge, increasing quantity greater than 1 breaks the components out into their own lines again. Do I need to return multiple identical merge operations to get the correct quantity? |
Beta Was this translation helpful? Give feedback.
-
Having same issue. 79fc7f04a49582c720b33e6fc20c68ec.mp4Also, the merge operation doesn't show discounted price. It's very important. because we offer discount when customer bundle products. |
Beta Was this translation helpful? Give feedback.
-
I've been experimenting with Cart Transform functions and came across some unusual behaviour when using different combinations of Merge and Expand operations and switching between cart and checkout.
Let's say I have 2 bundle configurations:
an Expand bundle with the following configuration
Parent ID:
gid://shopify/ProductVariant/111
Child Component ID:
gid://shopify/ProductVariant/211
(caramel)Child Component ID:
gid://shopify/ProductVariant/211
(caramel)a Merge bundle
Parent variant ID:
gid://shopify/ProductVariant/111
Child Component ID:
gid://shopify/ProductVariant/212
(chocolate)Child Component ID:
gid://shopify/ProductVariant/212
(chocolate)Things to note:
Behaviour:
If you add 2 x
gid://shopify/ProductVariant/211
(caramel) to the cart, it shows 1 xgid://shopify/ProductVariant/111
(parent) in the cart. Upon navigation to checkout it shows the 2 x caramel variants nested, which is correct.Navigate back to the store and add 2 x
gid://shopify/ProductVariant/212
(chocolate) and it shows 2 xgid://shopify/ProductVariant/111
(parent) in the cart. Upon navigation to checkout it shows 4 xgid://shopify/ProductVariant/212
(chocolate) nested beneath the parent.Expected Checkout:
gid://shopify/ProductVariant/212
(chocolate)gid://shopify/ProductVariant/211
(caramel)I can assume from this behaviour that there is either a bug or there is some kind of limitation where you can't associate multiple bundle configurations with a single variant.
Beta Was this translation helpful? Give feedback.
All reactions