Overview
Dynamic Bundles in Nosto let you group products into meaningful sets and show them together in the right context. You can use them for “complete the look” sets, product + accessory combos, or curated sets.
You manage all of this in the Dynamic Bundles area of Nosto. There you create and edit Bundles, see how they perform, and decide which Bundle should show when several could apply. To actually appear on your site, each Bundle is then used through a Recommendation and Placement, which you set up separately.
Dynamic Bundles help you increase average order value (AOV), keep product suggestions relevant, and avoid gaps when items go out of stock, thanks to built-in fallbacks and prioritization.
What Dynamic Bundles Are and What You Can Use Them For
A Dynamic Bundle is a flexible group of products that Nosto shows together based on rules you define. Unlike a static “hard-coded” set, Bundles can react to shopper context and your catalog:
You can make Bundles trigger from a specific product (for example, “when this dress is viewed, show these shoes and a bag”).
You can use attributes like category, brand, or custom fields, so that your Bundles stay relevant and flexible.
You can define fallbacks so the Bundle keeps working even when some products are out of stock.
Typical use cases:
Product detail page “Complete the look”
Cart-based upsell (“Add these accessories to your camera”)
Fixed, curated sets in a specific slot (“Staff picks”, “Holiday gift set”)
If you are unsure which Bundle type to choose for a use case, see “Understanding Bundle Types and When to Use Them”.
Seeing Performance: Bundle Analytics
Every Bundle in Nosto comes with performance data so you can see what actually works.
In the Bundles Overview you see key metrics such as:
CTR (Click-through rate) – how many shoppers interact with the Bundle.
CVR (Conversion rate) – how often interactions with the Bundle lead to orders.
AOV (Average order value) – the average value of orders influenced by the Bundle.
& more
This lets you compare Bundles against each other, focus on the ones that move the needle, and decide which Bundles should get priority in overlapping situations. If a Bundle underperforms, you can adjust its products, triggers, or visibility settings and then watch its metrics over time.
Tip: Use Bundle analytics together with the Priority view to promote Bundles that drive higher AOV and de-emphasize those that do not. Find out more about Bundle-Priorities.
Before You Start
To get value from Dynamic Bundles, you should:
Have your product catalog and tracking already running in Nosto.
Know where in the journey you want Bundles to appear (for example PDP, cart, homepage).
Have at least a rough idea of the products or attributes you want to bundle together.
The high-level flow looks like this:
Create and configure a Bundle in the Bundles area.
Add fallbacks so the Bundle keeps working when products go out of stock.
Set visibility rules for more control.
Connect the Bundle to a Bundle recommendation and a Placement so it shows on your site.
More info about the connection to Recommendations and Placements is covered in “How to Deploy Dynamic Bundles Using Recommendations”.
Creating Your First Dynamic Bundle – Step by Step
Step 1 – Choose Bundle Type and Select Products
First, decide what kind of Bundle you want and which products it should contain.
When you create a new Bundle, you:
Pick the Bundle type
Use a Triggered Bundle when the Bundle should react to context (for example, a specific viewed product or a product in the cart).
Use a Generic Bundle when you want a fixed set of products or attributes in a specific slot, regardless of what the shopper is doing.
Define the context (if Triggered)
For Triggered Bundles, you choose whether the Bundle should trigger from the viewed product, from a product in the cart, or use Dynamic mode to handle both.
This defines when Nosto is even allowed to show the Bundle.
Select which products the Bundle will show
For the Bundle’s content (the products shown inside the Bundle), you can:Add specific products (“Product” selection).
Add products based on rules (“Attribute” selection) such as category, brand, or other attributes.
Or combine both, static products and attribute rules, in the same Bundle.
Select which products trigger the bundle
For triggered bundles to show on a page, you need to have at least one item set as a trigger or have one item selected under Advanced Visibility settings if you want to trigger a bundle based on an item that is not part of the bundle
When you combine static products and attribute-based items, you can control how the static products influence the dynamic ones:
On each static product card, there is a toggle at the bottom: “Use for relations”.
When you enable this, Nosto uses that specific product as the relation source to find the most relevant attribute-based products (for example, the most related items from a category).
Tip: Turn on “Use for relations” for the key product in the Bundle so attribute-based items stay relevant to that product, even if your attribute rules are broad. This is especially useful for “hero product + supporting items” Bundles.
Step 2 – Configure Fallbacks
Next, make sure your Bundle keeps working even when individual products become unavailable.
In the Fallbacks section of the Bundle editor, you see all products in your Bundle. For each eligible product, you can add fallback products that Nosto should use if the original product cannot be shown (for example, when it is out of stock or deactivated).
At a high level:
You can define up to three fallback products per Bundle product.
Fallbacks can be specific products or attribute-based alternatives (for example, same brand, similar price, same category).
Attribute-based items that entered the Bundle only via rules cannot have their own fallbacks.
When Nosto detects that a product in the Bundle is not eligible, it automatically replaces it with one of the defined fallbacks. This keeps the Bundle valid and helps you avoid empty or weak-looking Bundles for shoppers.
Important: Bundle fallbacks keep the Bundle valid. If no Bundle at all is eligible for a given slot, the Recommendation-level fallback decides what to show instead of the Bundle. For details, see “Understanding the Different Fallback-Types”.
Step 3 – Set Name, Headline, and Advanced Visibility
Finally, you control if the Bundle is active, how it is labeled for you internally, and in which situations it is allowed or prevented from showing.
Key settings in this step:
Bundle Status
Use status to activate or deactivate the Bundle.
An Enabled Bundle can show on-site (if it is assigned to a Recommendation and matches that Recommendation’s rules).
Disabled or Archived Bundles will not show at all.
For a full breakdown of all statuses and what they mean for visibility, see “Understanding the Different Bundle Statuses”.
Name
This is an internal name, visible only to you and your team.
Use clear, structured names so it is easy to recognize the Bundle later (for example, “PDP – Shoes – Complete the look”).
The Name is also used for alphabetical priority when working with attribute-triggered Bundles.
Headline
This is a text field you can use as a variable in your template (for example, “Complete the look”, “Bundle & save”).
The template used in your Recommendation decides where and how this headline appears to shoppers.
Advanced settings (Visibility rules)
In the Advanced settings, you can:Add additional triggers that further define when the Bundle is allowed to show.
e.g. Select a specific product that or attribute that is not part of the Bundle to trigger it from there regardless.
Add deactivators that explicitly prevent the Bundle from showing in certain contexts.
e.g. Exclude the Bundle to show on PDPs from a specific Brand.
These rules let you fine-tune where Bundles appear without editing every Recommendation or Placement it’s assigned to. For example, you may only want a Bundle to show for certain price ranges, or categories, or you may want to suppress it on specific products.
What Else You Need So Bundles Show On-Site
Creating a Bundle is only one part of the setup. For a Bundle to show on your storefront, it must:
Be assigned to a Bundle recommendation (Recommendation type = “Bundle recommendations”).
That Recommendation must be connected to a Placement on your site.
In the Recommendation, you also decide whether to use Triggered or Generic Bundles, whether to apply all relevant Bundles or manually select Bundles, and how to fall back if no Bundle is eligible.
All of this is covered step by step in “How to Deploy Dynamic Bundles Using Recommendations”.
Summary
Dynamic Bundles let you group products into flexible sets that react to context and keep working as your catalog changes.
Bundle Analytics gives you metrics like AOV, CTR, and CVR so you can see which Bundles perform and adjust your strategy.
In the Bundle editor, you move through three main steps: choose Bundle type and products, configure fallbacks, and set status, naming, and advanced visibility.
Fallbacks keep Bundles valid even when products go out of stock, while Recommendation fallbacks keep the overall slot filled.