Hi team,
We are observing behavior that appears similar to the previously reported issue regarding bundle line item properties propagating to child items.
For reference, here is the earlier thread where this was discussed and subsequently reverted:
In that thread, the change was acknowledged and later rolled back. However, we are now seeing similar behavior again in live stores.
Current Behavior
When a bundle has line item properties defined on the parent line item, those properties are now appearing on each expanded child item in the order.
This is creating unexpected order-level changes for merchants.
Merchant Impact
From a technical perspective, we can adapt to changing semantics if needed. The larger issue is the merchant experience.
This change appears sudden from the merchant’s point of view:
- Merchants are seeing additional properties on child items that were not previously visible.
- Orders now display significantly more metadata than before.
- It creates the perception of duplication or malfunction.
- Support teams receive tickets assuming something is broken.
When these changes occur without prior communication, they feel like regressions rather than intentional improvements, both to us and to merchants.
If This Behavior Is Intentional
If the propagation of parent properties to children is now intended and permanent behavior, a few UI improvements would significantly reduce confusion:
- Collapse child line item properties by default in the Admin UI
If these properties must be visible, having them collapsed by default (expandable when needed) would reduce visual noise and improve clarity. - Hide
_-prefixed properties by default
In the earlier thread, Michael mentioned the idea of hiding_properties (with an eye toggle to reveal them). That approach would be extremely helpful for apps that use_-prefixed properties for internal/system metadata.
Reference:
Bundle Line Item Properties Now Propagating to Children – Causing Merchant Issues - #14 by michael
These changes would meaningfully improve merchant QoL while preserving transparency when needed.
Request for Clarification
Could the team please clarify:
- Is this propagation intentional?
- If yes, is this now the defined and stable behavior for bundle line item properties?
- Are there planned Admin UI updates around property visibility?
- Was this rollout documented somewhere that we may have missed?
We are happy to adapt our implementation as needed. Our primary concern is ensuring predictable behavior and minimizing merchant confusion.
If changes like this can be communicated or discussed ahead of time, we can proactively inform merchants and train our support teams accordingly.
Thank you for the clarification.

