Every bundle has a default selection of components. Default components are what customers receive when a bundle is added to the cart without any selection information. This commonly occurs through quick add buttons, or when other sales channels create carts on your store, such as shared links, draft orders, or the API.
Defaults also set the bundle product's displayed price. To keep price transparency for customers, the default selections are used to calculate the initial price that displays on the bundle product, in your store currency and in every market.
[screenshot - the Defaults list in the bundle editor's pricing summary]
When you create a bundle, the app picks the lowest priced components that satisfy your step rules as the defaults. You can adjust them at any time; you do not have to keep the lowest priced selection.
Two rules shape what the app picks:
Required items always come first. A required variant, or the cheapest available variant of a required product, is always part of the defaults. This includes required items on optional steps.
Optional steps stay empty unless they contain a required item, or you add defaults to them yourself.
Open the bundle in the app and select Edit defaults in the pricing summary, or Review default components from the banner if one is showing. The Default selection window lists each step with its current defaults.
[screenshot - the Default selection window with steps and selected defaults]
Add or remove items per step, and set a quantity for each.
The selection must satisfy the same step rules your customers see: step minimums and maximums, single select steps allow one option, quantity rules and increments apply, and no line can exceed a quantity of 2,000.
Required items are locked and cannot be removed.
The running total shows the price of the current selection after discounts.
Reset to lowest price returns the whole selection to the cheapest valid choice.
Select Save defaults, then save the bundle. A bundle cannot be saved without a complete, valid default selection.
The bundle product's price in Shopify is the total of the default components, after your discount. The subtotal (used for the compare-at price) is the total before discounts.
If "Update prices automatically" is on, the app keeps the bundle product's price in line with the default components as their prices change. Price changes can take a moment to apply, and up to 24 hours for catalog prices on localised bundles. See Localised pricing for Shopify Markets for how this works per market.
Because the defaults set the displayed price, changing your defaults changes the price customers see on the bundle product before they make choices.
Sold out. If a default component sells out, the app flags it in the bundle editor and in the Default selection window. Replace it so bare adds and the displayed price stay accurate.
Deleted. If a default component is deleted from your store, the app resets the bundle's defaults to the lowest priced items available. You will see a warning in the bundle editor when this happens; review the new selection and adjust it if needed.
[screenshot - a sold out default flagged in the Default selection window]
On localised bundles, the bundle's price in each market is built from the default components. Give every default component a fixed price in each market's catalog: that lets the app calculate an accurate display price for the bundle in that catalog and keep it up to date, instead of relying on Shopify's exchange rate conversion and rounding, where prices can drift. See Localised pricing for Shopify Markets.
Every default must also be available everywhere the bundle is sold:
Default components must be published in every market the bundle itself is published in. Only product level publishing counts; variant publishing settings are ignored.
Items that are missing from a market appear greyed out in the Default selection window, with a note listing the markets. To use one anyway, publish it to those markets in Shopify admin first, or unpublish the bundle from those markets.
If a required item is not available in a market, the save is blocked with a message naming the item. Publish it there, remove the requirement, or unpublish the bundle from those markets.
They look similar but do different jobs:
Preselected products are ticked for the customer when the bundle page loads. The customer can still change them, and they only affect the storefront form.
Required products are always part of the bundle and cannot be removed by the customer. Required items are automatically part of the defaults, and are locked there too.
Default components are what a bare add contains and what the displayed price is built from. They do not change what is selected on the bundle page.
See Preselect and Required Products for the storefront side.
Defaults are edited in the default price context and default language. Switch the country and language selectors back to Default to edit them on a localised bundle.
A customer who adds the bundle from your bundle page always pays for what they actually selected. Defaults only apply when no selection information reaches the cart.
