The bundle object and the allowed CRUD operations on the related resource endpoint

Bundles describe a set of specific products that are being sold. A unique code identifies each bundle. The bundle name, description, and image URL are best suited for internal usage (Commerce Layer is not a CMS). Bundles are linked to manual SKU lists, inheriting the SKUs from there.

A maximum of 10 SKU list items are permitted for each bundle. Once an SKU list is associated with a bundle, its items cannot be added, removed, or updated, unless you first destroy all of the linked bundles.

Bundles have price_amount_cents and compare_at_amount_cents attributes: the latter can be specified or computed as the sum of the SKUs, but is always guaranteed to be smaller than or equal to the former. Once a price is assigned to a bundle, the currency is inherited by the relationship with the associated active market. If that relationship is not specified, a currency must be assigned to the bundle.

When passing the _compute_price_amount and _compute_compare_at_amount trigger attributes the relationship with a specific market must be set, otherwise the API will return an error.

Data model

Check the related ER diagram and explore the flowchart that illustrates how the bundle resource relates to the other API entities.

Last updated