What is a Magento Grouped Product?
Short answer A Magento Grouped Product is a product type that shows several simple products together on one product page, without bundling them. Each child keeps its own price, stock and quantity box, and the customer buys any mix of them. The parent has no price or stock of its own and never appears in the cart. I use it when items belong on one page but the customer should not be forced to buy them as a kit.
- Create the grouped parent (name, SKU, NO price) 01
- Link child simple products via "Products in Group" 02
- Set each child's default quantity 03
- PDP shows a table of children and one Add to Cart button 04
- Cart treats each child as its own simple-product line 05
Most common mistake Confusing Grouped with Bundle
Five steps to ship a Grouped Product end to end
The grouped parent is a page, not something you sell. These five steps show how Magento builds the product page and the cart lines from it.
-
01
Create the grouped parent (name, SKU, NO price)
In admin go to Catalog → Products → Add Product → Grouped Product. Fill in name, SKU, categories and SEO fields like any other product. There is no price field, because the parent has no price. What the parent controls is the page: URL key, meta tags, description, images and the order of the children. Price, stock, weight and tax class all sit on the children.
-
02
Link child simple products via "Products in Group"
Open the Grouped Products section on the edit page and click Add Products to Group. Tick each simple or virtual product you want on this page, then save. Each child gets a position on the link, and the storefront table is sorted by it, lowest first. When a client asks why the order on the page looks wrong, the position values are the first thing I check.
-
03
Set each child's default quantity
Default Quantity is the number already filled in next to each child when the page loads. The customer can change it before adding to cart. I leave it at 0 for optional extras, so people choose on purpose, and set it to 1 for the main item. The value is stored on the product link (
catalog_product_link_attribute_decimal), not on the child, so the same simple product can have a different default in each grouped parent. -
04
PDP shows a table of children and one Add to Cart button
On the storefront the page shows one table with a row per child: name, price and a qty field. One Add to Cart button sends all rows at once with the quantities the customer typed. Rows left at 0 are skipped, and out-of-stock children show as unavailable. If the customer leaves every row at 0, Magento asks them to pick a quantity for at least one product.
-
05
Cart treats each child as its own simple-product line
In the cart each chosen child is its own line with its own SKU, price, qty and stock check. The parent is not there. Cart price rules, tax, shipping, refunds and reports all work on the child SKUs, so you can refund one child and leave the rest, and stock comes off each child separately. Reorder from order history adds the child SKUs again, not the parent.
Four scenarios where Grouped beats Bundle and Configurable
Grouped fits when customers should see related items on one page and still pick only what they need. These are the four cases where I reach for it.
-
Cross-sell that customers configure themselves
An office chair, a footrest and a lumbar pillow on one page. The chair is the main item and the other two are optional. The customer sees everything that goes together and adds only what they want. It reads like a planned set rather than a “you may also like” block further down the page, which many shoppers scroll past.
-
Series or collection sold as separate volumes
A book series, an album discography, a course in several parts. Customers want to see the whole series on one URL and buy only the volumes they do not have yet. A grouped page lists every volume with its own price, stock and qty field. A bundle would push the whole set, and configurable does not fit because volumes are separate products, not variants of one.
-
Replacement parts and compatible spares
A “spares for Model X” page for a coffee machine: descaler, filter cartridge, replacement carafe and milk frother. Someone searching for a Model X filter lands on one page with every spare for that model and picks only what they need. Each spare stays a normal simple product, so it can still be sold and searched on its own.
-
Beauty / personal-care mix-and-match sets
Skincare routines, hair-care sets and scent samplers, where customers expect to pick their own mix. A “morning routine” page lists the cleanser, toner, serum and SPF as separate children, and the customer buys the ones they want. A bundle fixes the recipe. Grouped lets each customer build their own routine while the related items sit right at the top of the page instead of in a carousel below.
Three traps that turn a Grouped product into a support ticket
Most grouped-product problems come from one of these three mix-ups. Sort them out before you build the catalogue.
-
Confusing Grouped with Bundle
A grouped product is not a kit. Each child becomes its own cart line, with its own SKU, stock, and price, the customer can buy one, all, or any subset. A bundle product, by contrast, is a single composite SKU sold as one purchase with one cart line. If business requirements say "the gift box must always contain X, Y, and Z and ship as one unit," use Bundle. If they say "show these related items together but let the customer pick what they want," use Grouped. Picking the wrong type here means rebuilding the PDP later.
-
Expecting a price on the parent
The grouped parent has no price field, and that confuses admin users who expect one. On category pages Magento shows “Starting at” with the lowest child price, and on the product page each row shows its own child price. The cart only ever uses child prices. To change what the customer pays, change the child products, and tell the store team this before they go looking for a parent price.
-
Trying to link configurable products as children
Grouped product children must be simple or virtual product types. Configurable, bundle, and downloadable types cannot be linked, the admin product picker will not even show them. If you need "size variants of three related items on one PDP," the answer is not grouped-of-configurables; it is either three separate configurable PDPs cross-linked, or a single configurable product with extended attributes. Trying to force configurables into a grouped parent via direct DB inserts will break the PDP renderer.
Magento Grouped Product: frequently asked questions
-
Grouped vs bundle: what's the practical difference?
A bundle is a single composite SKU bought as one unit: one cart line, one price, one shipment. A grouped product is a presentation wrapper: each child becomes its own cart line with its own SKU, price, and stock. The customer can pick any subset (including just one) and the cart shows each pick separately. Bundle is the right call for gift sets, hampers, or fixed kits. Grouped is the right call for "buy together" UX where the customer should still be free to deselect any item. The clearest test: would you ever ship just one of the items independently? Yes = grouped. No = bundle. -
Why does my grouped product page show no price?
Grouped products have no parent-level price by design. The storefront renders each child's own price in the products-in-group table, not a single price at the top. If you want a "from $X" indicator at the top of the PDP, you need either a custom Block or theme override that loops the children, finds the minimum price, and renders it next to the title. Magento's default template will not do this for you. The same applies to category listings: without customization, grouped products appear with no price label in the category grid. -
Can I track stock at the parent grouped level?
No. Stock lives on each child simple/virtual product, and the grouped parent has no stock record of its own. The parent shows as "in stock" on the storefront as long as at least one child is in stock; out-of-stock children render disabled in the PDP table. If you need a parent-level stock concept (e.g. "only sell this set while all four items are in stock"), you need a custom plugin on the stock-status logic or a switch to a Bundle product (which does carry parent-level stock derived from its options). -
Can children be configurable products?
No. Grouped product children must be simple or virtual. Configurable, bundle, and downloadable are not allowed and the admin product picker will filter them out. If the requirement is "show three related configurable products on one PDP," the correct pattern is either three separate configurable PDPs with cross-sells, or a single configurable product with the variant axes you actually need. Magento intentionally restricts grouped children to simple/virtual to keep the cart-line model trivial: every line is a single concrete SKU. -
How does this affect promo rules and cart price rules?
Cart price rules apply to children, not to the grouped parent. A condition like "SKU equals GROUPED-001" will never match because GROUPED-001 never enters the cart, only the child SKUs do. Write rules against child SKUs, child attributes, or child categories instead. Catalog price rules behave the same way: they discount child products by SKU/attribute/category match, and that discount surfaces on both the grouped PDP price column and the cart line for that child. This is consistent with the underlying model where the parent is presentation, the children are commerce. -
Do grouped products work with Adobe Commerce B2B?
Yes. Grouped products work in Adobe Commerce (and Adobe Commerce B2B) on every supported version. Customer-segment pricing, shared catalogues, company-account quoting, and tiered prices all apply at the child level, which is exactly where you usually want them in B2B (different companies see different prices on each child item). The one thing to watch is requisition lists: customers add the child SKUs to lists, not the grouped parent, make sure your sales team and storefront copy reflect that the "set" is conceptual and the SKUs are still individual.
Not sure which product type fits your catalogue?
Send your store URL and a sample of the SKUs you're modelling, I'll reply with a product-type recommendation per SKU group, a migration plan if you're changing types, and a fixed-price quote. 24-business-hour turnaround.