Has anyone found a reliable solution for when cart transformation bundles break after a update.js or change.js call that updates line item properties?
We’re running into this issue mostly with pickup/delivery apps that add delivery-related properties. When they do, the bundle gets split into individual cart items, which not only breaks the grouping but also removes the applied discounts.
We’ve tried reaching out to popular apps our merchants rely on such as Zapiet and other 3rd party apps but so far the conversations haven’t been very productive. It’s a bit frustrating, especially since functions and cart transformations are becoming more widely adopted, and these conflicts are turning into major blockers for merchants.
Has anyone here found a workaround, or a way to better coordinate between apps to avoid this?
Thanks for reaching out in the Dev Forums about your Cart Transform bundles breaking after updates to line item properties!
I’ll need to replicate the issue in order to look into potential solutions. Can you share the following information:
Video showing the issue if possible (not required if you wish to protect store privacy)
Request ID listed on the response header for a update.js or change.js request that caused the issue
Which operation is used to create the affected bundles with the Cart Transform API - merge or expand?
Any information on the intention of the apps when they add these line item properties if possible - purpose of using line item properties, are the changes targeting variants or lines, etc.
