|Number of votes:||5|
Episerver Catalog Packages vs Bundles
This is a short blog to clarify a catalog concept that is often unclear for folks new to Episerver : the difference between bundles and packages.
Bundles and packages are catalog item-types that have distinct features and different use cases.
A bundle is a collection of SKUs that are simply grouped together for catalog-browse and add-to-cart purposes. There is no bundle-specific pricing or inventory. The pricing for a bundle is simply the total of the prices for the SKUs in the bundle. Inventory is tracked on the SKU level. A common scenario for using bundles is when an item usually needs to be bought in conjunction with other items in the catalog, like a phone and its charger.
When a bundle is added to the cart, your “add to cart” functionality needs to retrieve the SKUs in the bundle from the system and add each one to the cart. Once in the cart, the SKUs from the bundle are not identifiable as part of a bundle; they’re simple SKUs (as lineitems) in the cart. Therefore, a) you can’t attribute promotions to them as a bundle, b) you can change the quantity of each SKU/lineitem independently, and c) you can delete the individual lineitems that were associated with the bundle SKUs. Given the lack of pricing on a bundle and that promotions can’t be applied to them, you can’t provide discount pricing to incentivize buying bundles (at least not without significant additional development).
Conversely, packages contain SKUs but have their own pricing and inventory. When you add a package to the cart, its a single lineitem, like a SKU. SKUs can’t be removed from the package lineitem in the cart. You can only update the quantity of the package in the cart (or remove it). You can think of a package as a group of SKUs that are physically stored together and inventory is managed on the package level. Packages allow you to provide discounted pricing for a group of SKUs. You can also create promotions for packages. Note, however, that promotions which apply to SKUs contained in the package will not apply to the package lineitem.
These catalog types and their behavior are flexible with some minor customization. You could do things like:
* Create a “dynamic package”, where a user can select which items in a package or bundle is ultimately purchased in their cart.
* Use packages but still maintain inventory on the SKU level
* Add a package as multiple lineitems in the cart
These customizations may require additional effort to a) ensure your pricing logic reflects this logic, b) modify the way carts are processed to validate the content of the carts, update prices, etc , and/or c) change the way your add to cart functionality works.
Documentation on how to work with packages and bundles programmatically is here:
[Edited to incorporate comments below from Khurram and Per from 6/9/17]
Please login to comment.