Understand that commercetools does not have a native bundle product type; bundles are typically modeled using a custom product type with references to component products, or via product sets using Product Selections.
Create a custom product type for bundles with attributes such as bundleComponents (a set of product references or variant references) and bundleQuantities.
When adding a bundle to a cart, add the bundle product as a line item and then add each component as separate line items with custom attributes indicating they are bundle components (e.g., a custom lineItem field bundleParentId).
Use a Cart Extension (API Extension) to enforce bundle pricing and component line item consistency server-side on every cart update.
Alternatively, use Product Selections to group bundle-eligible products for catalog management, but implement bundle-in-cart logic separately in your application layer.
Consult current commercetools documentation for any native bundle or set product patterns that may have been introduced, as the platform evolves continuously.
Known gotchas
Without a native bundle type, bundle integrity (ensuring component items are not removed independently) must be enforced by a Cart Extension or application logic, adding implementation complexity.
Inventory tracking for bundle components must be handled at the component variant level; the bundle product itself typically does not track inventory independently.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp