What is a Magento Bundle Product ?

Configurable products are variants of one item — a t-shirt with size and colour options always resolves to one physical t-shirt. The variants share a parent product page but each combo (size M, colour red) is its own underlying simple product with its own SKU and stock. Bundle products are packages of several items — a PC build, a hamper, a meal kit. The customer ends up with multiple distinct items, each a separate simple product in your catalogue. Rule of thumb: if the cart contains one item at the end, use Configurable; if the cart contains several items grouped under one parent, use Bundle.

No. Magento restricts bundle children to <strong>simple</strong> or <strong>virtual</strong> product types only. You cannot attach a configurable, grouped, or another bundle as a child. The reason is dependency depth — if a child were configurable, the bundle picker would need to expose a nested configurable picker (size, colour) inside each option, and the cart line would need to track parent + bundle + configurable variant. Magento dodges that complexity by keeping bundle children flat. Workaround: create simple-product variants of your configurable, attach the variants directly as bundle children, and let the bundle option act as the size/colour picker.

<strong>Dynamic Pricing</strong>: bundle total is the sum of selected children's catalogue prices, multiplied by their selected quantities. The parent product has no price of its own. Use this for "pay for what you pick" builds like PC configurators or meal kits. <strong>Fixed Pricing</strong>: the parent has its own single price that overrides children. The children's catalogue prices are ignored at the parent level — Magento displays only the fixed parent price regardless of what is selected. Use this for fixed-price hampers, subscription boxes, or any kit where you want a consistent headline price (e.g. £75 gift box) regardless of which child variants the customer picks.

Yes. On the order, invoice, shipment, and credit memo, Magento displays the bundle parent as the main line item with the selected children as nested rows beneath it. Each child row shows its own name, SKU, quantity, and price (price column appears for Dynamic pricing; for Fixed pricing the children show qty + SKU but not price). This is important for warehouse picking — your fulfilment team sees the individual SKUs to pick from the shelf — and for tax reporting in jurisdictions that require per-item line detail. Some accounting integrations need extra configuration to round-trip the nested structure correctly.

Partly. At the child level you can set a default quantity and a "User Defined Quantity" toggle: if off, the customer is locked to that qty; if on, they can change it. Magento does not natively expose min-qty or max-qty per child inside an option — only the default and the on/off toggle. For per-child min/max enforcement you either: (1) add custom JavaScript validation to the PDP, (2) write a quote validator plugin that rejects out-of-range qtys at add-to-cart, or (3) use a paid extension like Amasty Bundle Options or Mageworx Bundle Options Pro that adds the missing fields to the admin UI.

<strong>Tax</strong>: by default, tax is calculated per child based on each child's tax class — not the parent's. So a hamper containing a 20%-VAT bottle of wine and a 0%-VAT food item taxes each child correctly. Override: set "Tax Class" on the parent and enable "Use Fixed Tax" on dynamic bundles only if you need uniform tax across all children. <strong>Shipping</strong>: controlled by the "Shipping" setting on the bundle parent — <em>Together</em> bundles the children into one parcel using the parent's weight (sum of child weights for dynamic, fixed weight for fixed-price), and <em>Separately</em> generates a shipping rate per child. Use Separately for kits where children ship from different warehouses or where multi-parcel rates are cheaper than a single oversized carton.