Classification of the feature
Shopify now also displays bundle components on the status page of draft orders in customer accounts. This means customers no longer just see a bundle as a single grouped item, but also the individual components it contains. That may sound like a small visual change, but in practice it affects transparency, support effort, and approval processes.
Especially with B2B, starter kits, gift sets, or more technically complex product bundles, the same question often comes up: What exactly is included? That’s exactly what this update addresses.
If previously only “Premium Care Set” was visible and now “Cleanser, Serum, Cream” appears, the risk of misunderstandings is immediately reduced.
What the feature is, and what it is not
The feature improves the visibility of existing bundle components within draft orders in the customer account.
- It is a presentation extension.
- It is not a new bundle architecture.
- It does not replace bundle management.
- It is not price control.
- It does not change any warehousing or fulfillment logic.
A simple example:
A retailer is selling a home office bundle.
Previously the customer saw:
Home Office Bundle
Now he sees:
Home Office Bundle
- Keyboard
- Mouse
- monitor arm
That helps with traceability.
But it’s also important to understand what the feature cannot do. Anyone who wants to specifically hide individual components on the thank-you page or order status page cannot easily achieve this with standard bundles according to the documentation as of today. Transparency is increased, not selectively controlled.
Requirements and data basis
The feature is only as good as the underlying data. If bundle components are not properly maintained, the visualization will merely reveal that something is wrong.
Poor data quality is often recognized by the following:
- cryptic component names
- duplicate components
- illogical variant names
- inconsistent bundle assignments
If X is called “KIT-02” in the bundle instead of “Vitamin C Serum”, then visibility doesn’t help the customer much.
A second point is channel compatibility.
According to Shopify’s documentation, bundles are tied to supported sales channels, in particular the Online Store and headless storefronts. Anyone selling across multiple channels should check whether their own setup is affected.
Important for B2B:
As of today, price locks are not supported for product bundles.
This is relevant.
If a B2B customer expects a draft order for price protection and the bundle is excluded from this, it can lead to conflicts.
This limitation should not be overlooked.
How to use it concretely in the Shopify admin
First step:
Check bundle structure.
Don’t start with the customer account, start with the data model.
Are components assigned correctly?
Are the prices reasonable?
Are variants named clearly?
Then create a draft order with a bundle.
Then test the customer view.
Don’t just check whether components are visible.
Also check:
- vote counts
- are the price relationships correct
- vote components
- is the representation consistent across different markets
An important additional test is often forgotten:
Change the product price of a bundle component.
Then check:
Does the bundle price change automatically?
As of today: no, bundle prices do not update automatically and have to be adjusted manually.
That is exactly what should be included in test cases.
Practice logic that determines costs and quality
The real potential doesn’t lie in the feature itself, but in its knock-on effects. If fewer customers make inquiries, support costs go down. If components are visible, follow-up questions such as these decrease:
“Is the accessory included?”
“Are both refill packs included?”
But visibility can also expose mistakes. If the ad promises three items and shipping delivers only two, the problem escalates more quickly.
That’s not a disadvantage.
This is quality control.
The more complex the bundle structures, the more important the splitting logic and test cases become.
A fixed two-item bundle is simple.
A bundle with country-specific components is not possible.
Typical practical applications
Starter sets in D2C
A first-time buyer can see exactly what’s included.
That reduces uncertainty.
B2B sample orders
A purchasing team inspects components before approval.
This is precisely where transparency helps.
But only if you know the price lock limits.
Gift or promotional bundles
Free components or bonus items are made transparently visible.
This reduces discussions after campaigns.
Text and template examples
Example:
Your set contains three individual products; you can find details here.
Link to the bundle overview
Example:
You can see all included components in your order overview.
Link to order details
Example:
If something is missing, please first compare it with this list of components.
Link to help and support
Keep it brief.
Often, 100 to 150 characters work better than long explanatory texts.
When it makes sense, when it doesn’t
Makes sense:
- When bundles have operational significance.
- When B2B approvals need a component view.
- If there are support questions about bundle contents.
- When multi-component sets are sold.
- Less useful:
- When bundles are just marketing packaging without any real component structure.
- When price hedging via a price lock is absolutely necessary.
- When bundles are to be combined with subscriptions.
Important point:
As of today, bundles are not compatible with purchase options such as subscriptions or pre-orders, and they are not compatible with the Shopify Subscriptions app.
Anyone who wants to combine both should look into it early.
Mistakes to avoid
Internally name bundle components.
Customers don’t understand internal codes.
Silently accept the price-lock capability.
Bundles don’t support that at the moment.
Change product prices without updating the bundle price.
Then the calculations no longer add up.
Want to combine subscriptions with bundles without checking compatibility.
This often doesn’t cause problems until late.
Moving Primates Perspective
In projects it often becomes clear that bundles look clean from a conversion perspective, but have operational breaks. A typical pattern is: pricing logic, ERP, and what the customer sees drift apart. The risk increases with market-specific bundles or when teams assume that bundle prices update automatically. A practical approach is usually simple: first check the bundle data, then simulate real draft-order test cases including price changes, and finally document B2B exceptions such as missing price locks separately. Often the problem is not the bundle itself, but incorrect assumptions about its boundaries.
Technical implications for larger shops
For larger shops, frontend validation alone is not enough.
It’s about data flows.
Bundle data.
ERP.
WHO.
Fulfillment.
Customer Accounts.
These layers must represent the same truth.
Mandatory test cases:
- Bundle with discount
- Bundle with variants
- Bundle after price change
- Bundle with market deviation
- Bundle with partial delivery
- Bundle in B2B draft order without price lock
- Bundle in combination with subscription scenario as a negative test
Governance question:
Who checks price changes?
Who documents bundle boundaries?
Who is responsible for channel compatibility?
Without responsibility, mistakes happen.
10-point checklist before go-live
- Bundle components created completely
- Component names suitable for customers
- Prices checked
- Bundle price tested after product changes
- Draft order test carried out
- Customer account verified
- Price lock relevance assessed
- Subscription conflicts checked
- Channel compatibility checked
- Support and Operations informed
Summary
- The update improves transparency for draft orders
- Individual bundle components become visible
- Relevant for D2C and B2B
- No substitute for bundle management
- Data quality determines usefulness
- Price locks for bundles are not supported
- Bundle prices do not update automatically
- Bundles cannot be combined with subscriptions
- Supported sales channels should be reviewed
- Test cases are more important than mere visual inspection.
- Large shops need clear governance
- Bad assumptions are often the real risk
FAQ
How much does that cost?
As of today, this is a platform feature and not an additional function priced separately. Availability is determined according to the Shopify documentation.
Which data do I need?
Clean bundle components, pricing logic, variant structure, and tested assignments.
Do Price Locks work with bundles?
As of today, no. Product bundles do not support price locks.
Can I combine bundles with subscriptions?
As of today, it does not work with Shopify Subscriptions or classic purchase options.
When is that unsuitable?
When price hedging is mandatory or bundle logic needs to be combined with subscriptions.
Do bundle prices update automatically?
No. Changes to component prices require manual adjustment of the bundle price.
Link list
Shopify changelog for the feature
https://changelog.shopify.com/posts/product-bundles-and-their-components-now-represented-on-draft-order-status-page-in-customer-accounts
Shopify Help Center on product bundles
https://help.shopify.com/en/manual/products/bundles
Shopify Customer Accounts Documentation
https://help.shopify.com/en/manual/customers/customer-accounts
