Overview
Shopify Bundles does not automatically update a bundle’s price when one of its products changes price. You can update it manually, or use automatic pricing in Biscuits Bundles. This guide explains both options and how to check that your bundle prices are correct.
Contents
Does Shopify Bundles update prices when a component price changes?
No. Shopify says that a price change to a bundled product, whether entered manually or through a price import, does not update the Shopify Bundles product’s price. You must change the bundle price separately in Shopify admin. Inventory and component relationships can still be tied to the underlying products, but that does not make the parent selling price a live sum.
Why does the bundle keep its old price?
The Shopify Bundles product has a price of its own. That can be intentional: a merchant may want a gift set to remain at a round fixed price even if one item’s individual price changes. It can also cause a missed update when the intended rule is “charge exactly what the components cost.” Shopify cannot infer which of those two intentions applies from a component edit.
In this example, Product A goes from €19.90 to €24.90 and Product B stays at €30. The component total becomes €54.90. A native bundle parent set to €49.90 continues to sell for €49.90 until a merchant changes it. That is only a problem if the merchant intended a component sum or a particular saving, rather than a fixed €49.90 offer.
Does a component sale price update the native bundle price?
No. A sale created by editing a product’s Price and Compare-at price changes that component’s selling price, but does not recalculate the Shopify Bundles parent price. A discount code or automatic discount is a different mechanism: Shopify can apply eligible discounts to a bundle parent, yet that does not turn the parent’s underlying price into a live component sum. Check which kind of promotion you are running before changing bundle prices.
How do you update affected Shopify bundle prices?
Start with the component that changed. Identify each bundle and variant that contains it, write down the current parent price, then calculate the intended replacement using a consistent rule. Shopify lets you manage bundle product details in Products and edit its included products through the Bundles app; you do not need to remove and recreate the bundle just to change its product price.
How do you find bundles that contain the changed product?
For a small catalog, review your bundle products in Shopify admin or maintain a simple component-to-bundle list so one product edit prompts all related checks. A product can occur in more than one bundle or bundle variant, so checking only the first match is not enough. If your catalog is large, a developer can query the Admin API’s ProductVariant.productParents connection to find parent products containing a component variant. Confirm the returned relationships on a test bundle before relying on a bulk update.
Record the bundle’s existing price, the component prices and the intended rule before saving. That gives you a reviewable before-and-after list and helps catch a bundle that is meant to remain fixed.
How do you calculate the new bundle price?
If the rule is sum of components, multiply each component’s current price by its quantity and add the results for every bundle variant. In the illustration above, €24.90 + €30.00 = €54.90. Update the native bundle product or variant price to that amount and check every affected variant. If the offer promises a fixed euro saving or percentage saving, calculate that from the new component total instead. If the offer promises a fixed total, you may deliberately leave it at €49.90, but review the resulting margin and the savings claim.
Check the parent product’s Compare-at price separately. It is a display reference, not a formula that makes the Price field follow components. If the crossed-out number no longer represents an honest comparison, adjust or remove it before presenting the changed offer.
Can Shopify bundle prices update automatically?
Shopify Bundles does not provide an automatic component-price-to-parent-price update. Automation needs an explicit rule: should the price equal the component sum, keep a fixed amount off, keep a percentage off, or stay at a fixed total? Choosing that rule first prevents an automation from silently changing an intentionally fixed offer.
Can the bundle follow the sum of its component prices?
Yes, with a component-priced bundle approach or a separate process that updates the native parent price. In Biscuits, Sum of Products totals the selected items with no additional bundle discount. With the app-wide Use compare at price setting off, this follows their current selling prices; turning that setting on can use higher valid compare-at prices instead. Sum of Products with that setting off directly matches a merchant who groups stock but wants the selling price to equal the current component total. The bundle product’s displayed starting price is built from its default components; a customer’s actual selection can have a different total.
What if the bundle must keep a fixed price or discount?
These are different promises. A fixed total stays the same until you choose a new one. A fixed amount off moves with the component total but keeps the same money saving. A percentage off moves with the component total while keeping the percentage. Biscuits documents Sum of Products, Fixed Total Price, Percentage Discount and Amount Discount as separate types; its fixed total is merchant controlled. For broader pricing tradeoffs, see our Shopify bundle pricing guide.
Can you automate price changes without switching bundle apps?
A developer could keep Shopify Bundles and build a separate job: detect a component price edit, find the parents that use its variant, calculate the price from your chosen rule, and update each affected parent variant. Shopify’s Admin API exposes the parent relationship, but the pricing rule, safeguards and update process are your own implementation. Test one bundle first, handle multi-variant bundles and market-specific prices, and keep a review trail before letting a job write many prices. For an occasional change, a manual checklist may be simpler.
How does Biscuits update bundle prices when product prices change?
Biscuits calculates component-priced offers from the selected products and the bundle discount type. Its Update prices automatically control also maintains the bundle product’s base display price from the default components when it is on. On localised bundles, it maintains supported pinned market catalog prices. A Fixed Total Price remains a price you control; do not select it if you expect the selling total to track component changes.
Which Biscuits pricing types follow component prices?
Sum of Products follows the combined item prices with no extra saving. A percentage or amount discount calculates a saving from those items. Volume pricing can depend on how many items are selected. The bundle’s initial product price reflects its default components, while selections made on the bundle page can change the final total. A fixed total is the deliberate exception.
What does Update prices automatically change?
With this bundle-level control on, Biscuits maintains the bundle product’s base price and supported pinned catalog prices from the default components. The app’s localised pricing guide says ordinary component price changes apply within minutes, while catalog edits can take up to a day. For a localised bundle with the control off, those product and market display prices belong to you; shoppers building the bundle on the supported storefront path still pay the current local component prices minus the chosen discount. Check the bundle page after an edit rather than assuming every display surface has refreshed at once.
How does Use compare at price affect sale-priced components?
This separate app-wide Biscuits setting changes the price used as the reference for a component in bundle calculations. When a component’s Compare-at price is higher than its Price, Biscuits uses the higher value if the setting is on. If Compare-at is missing, equal or lower, it uses Price. This can prevent an individual sale markdown from being compounded with the bundle discount. It also means the resulting bundle price may be higher than a shopper expects from the current individual sale prices, so compare the final offer with buying the items separately before enabling it across your store.
Changing this setting refreshes existing bundles in the background, usually within minutes; newly added cart items reflect the update while items already in carts retain their prior pricing. It does not control the bundle product’s own Compare-at price field. That separate field can be preserved using Don’t update compare-at price on an existing bundle. Neither setting determines whether a separate Shopify discount code may combine at checkout.
How do you check the bundle price after a component changes?
Use one changed component to test the complete path before applying the rule more widely. Note its old and new price, compare-at price and market catalog prices. Check every bundle variant containing it, then verify the product page, cart and checkout with a newly added bundle. Repeat for a temporary component sale and for a permanent price increase if both occur in your store.
Do the product page, cart and checkout show the expected price?
For a native Shopify Bundles product, compare the parent’s saved variant price with the new component sum and the rule you chose. For Biscuits, select the actual components on the bundle page and compare the displayed total with a fresh cart and checkout. Do not rely on an item that was already in a cart before changing the app-wide compare-at setting. If a promotion is involved, test it with and without the discount code so a checkout combination is not mistaken for a component-price update.
Do Markets prices and compare-at prices still match your offer?
If the bundle is localised, test the markets where you have fixed component catalog prices. Biscuits can maintain the corresponding pinned bundle product prices when automatic updates are on, but catalog price edits can take longer to propagate. Markets using conversion and rounding may show small differences on the product page even when the checkout total follows the selected components. Fixed Total Price bundles have their own merchant-set market totals. Check the market’s Compare-at visibility and avoid claiming a saving where its display reference is missing or out of date.
Keep the outcome simple: if the intended rule is a component sum, the saved or calculated bundle total should equal the current eligible component prices. If it is a discount, verify both the final price and the saving. If it is a fixed campaign price, confirm that the unchanged number is still profitable and accurately presented.
View on app store