Contextual pricing for ExpandedItems is now critical for Markets and bundle apps

Wanted to bring attention to this open thread because this is a real gap, not an edge case:

Open thread: Contextual price for ExpandedItems in Expand Operation

For bundle apps, this becomes a serious blocker when trying to support merchants selling across Markets.

The core problem is simple:

  • Expand does not give a reliable way to access contextual pricing for component products
  • a single stored metafield price only represents the home price
  • presentmentCurrencyRate is not enough because it does not reflect actual market-specific pricing logic
  • this also becomes a problem for B2B / company pricing

Why this matters:

  • Shopify is going more global
  • Markets are becoming more important, not less
  • global brands need bundles to price correctly based on buyer context
  • without contextual component pricing, true dynamic bundling becomes very hard to support cleanly

Current workarounds are not great:

  • storing market price maps in metafields
  • syncing prices into parent products
  • maintaining custom infra just to approximate pricing
  • dealing with metafield size limits and function constraints

These approaches may work for small cases, but they do not scale well for:

  • large catalogs
  • many markets
  • complex bundle setups
  • B2B pricing scenarios

This is why this feels important.

It is not just a developer convenience request. It is a foundational requirement for building dynamic bundle experiences properly for global brands.

Would really love to see Shopify expose contextual pricing for expanded items directly inside Expand .

That would make it much more feasible to build:

  • market-aware dynamic bundles
  • localized pricing logic
  • B2B-aware bundle experiences
  • more native implementations without brittle workarounds

As Markets become more central, this gap becomes harder and harder to work around.

2 Likes

Hey @prakhar - thanks for reaching out. I can’t share too many details or a turnaround time on this, but this is a gap we’re aware of and have looked into this on our end. Really appreciate you sharing the above, I’ll pass along your thread here internally, thanks again!

1 Like

Appreciate you @Alan_G! Please keep us updated. This has been a huge blocker for a lot of our brands.