What is the reason that Webflow does not have nested components in ecommerce collections like it does in CMS collections, and should this feature be requested on the Webflow Wishlist?

TL;DR
  • Webflow eCommerce doesn't support nested CMS components due to rigid product data structures and lack of multi-reference fields.  
  • Use CMS collections as proxies, link via shared fields, or use custom code as a workaround, and consider requesting this feature on the Webflow Wishlist.

Webflow eCommerce currently does not support nested components like CMS collections due to architectural differences in how product data is handled. Here’s a breakdown of the likely reasons and how to proceed if you need this functionality.

1. Differences Between CMS and eCommerce Collections

  • CMS collections are more flexible and designed primarily for content (e.g., blog posts, team members), allowing collection nesting via Collection Lists and Reference fields.
  • eCommerce collections (Products, Categories) are structured to support shopping cart functionality, variants, and payment flows, making them more rigid than CMS collections.
  • Webflow has limited template-based support for eCommerce, and currently it doesn’t allow adding nested components like a CMS Collection List within a Product Template page.

2. Technical Limitations in eCommerce Collections

  • eCommerce Products don’t support multi-reference fields, a key requirement for outputting nested or relational collections.
  • Unlike CMS items, eCommerce Products are bound to variant structures, which complicates relational data nesting.
  • Webflow likely hasn't prioritized this due to the higher complexity in how Products are rendered and sold, as products need to be validated for pricing, inventory, and variants.

3. Workarounds and Alternatives

  • If you need to simulate nesting, consider:
  • Using a CMS collection as a proxy to structure extra eCommerce-related content.
  • Linking from eCommerce Product Pages to CMS collections using common identifiers like Slug or custom fields.
  • Embedding a static symbol or custom JavaScript embedding on product pages (with logic to pull related CMS entries), if needed.

4. Requesting the Feature on Webflow Wishlist

  • Yes, this feature should be requested. Nested components in eCommerce would enable advanced product presentation and relational design.
  • Other users have already requested similar features like multi-reference fields for ProductsCMS-style component architecture in eCommerce, and more dynamic content in Product templates.
  • Visit the Webflow Wishlist here: https://wishlist.webflow.com and either upvote an existing request or create a detailed new one.
  • Clearly describe your use case (e.g., “Show related products from a CMS collection inside a Product page”) to help the Webflow team understand the need.

Summary

Webflow’s eCommerce system lacks nested components due to structural limits and the complexity of product data. While workarounds exist, this is a valid feature to request via the Webflow Wishlist to improve eCommerce flexibility.

Rate this answer

Other Webflow Questions