Is there any way to support a base price for the cart transform merge operation?

Some users want to offer a base price for a bundle to cover the packing cost or a premium. However, the merge operation can only add the prices of the bundle components.

For example, the base price is $5. The customers can add any 5 variants to get a 10% off. The bundle price is $5 + (total variant prices x 90%) or ($5 + total variants prices) x 90%. I can apply a percentage decrease to the merge operation: MergeOperation

I believe the expand operation is not useful since the bundle parent price is used. But I don’t know the bundle parent price. It’s dynamic

In the merge operation, only a percentageDecrease can be supported. Can Shopify support a fixed amount increase or a percentage increase?

A user sells cookie boxes (e.g. cookie box of 3 or 6) and he wants to bump up the bundle price by $1 to cover the bundle box fee.

Hey @Benny_Chan :waving_hand:, you’re on point here, right now for Cart Transform Functions specifically, we do only support percentage decrease price adjustments.

One workaround I can think of would be to have a capped price for the parent bundle which you could then programmatically decrease to the desired amount. For example, set the parent bundle to $100, then calculate the percentage decrease needed to reach your target price (base + components). So for a $1 box fee + $24 of cookies, you’d decrease by 75% to get $25 total.

It’s definitely not the most ideal workaround though (and you’ll want to consider how the original price displays), so I’m happy to put through a feature request for you on my end. Fixed amount increases and percentage increases for merge operations would definitely make bundle pricing more flexible.

If you’d like to share any other specific use cases just let me know and I can pass your feedback on to our team here. :slight_smile:

The bundle price of the merge operation relies on the bundle components, but not the bundle parent. Therefore, I can’t set the parent bundle price.

Your case may be working for the expand operation. The bundle price relies on the bundle parent for expand. However, if the user can set a specific price for the bundle. There is no need to set up a base price because the bundle fixed price can include this extra packing cost.

Thanks for the follow-up and clarification @Benny_Chan! You’re correct here - merge operations work with component prices, not the parent bundle price. I had been thinking about fixed product bundles as a potential workaround in my earlier response, but that may not fit your use case, so I definitely understand where you’re coming from

Unfortunately, adding fixed amount increases to merge operations isn’t something we currently support. For now, the best recommendation would be including the base fee in your component prices as the most straightforward approach (but I do understand if this isn’t feasible because of the dynamic pricing).

Let me touch base with the team internally to confirm there aren’t any other workarounds I’m missing, and I’ll loop back with you on this thread. I’ll also make sure your use case is captured in the feature request I’ll set up for more flexible bundle pricing options.