Variation families: parent and child ASINs, submissions, and family cases

A parent is a non-buyable ASIN that groups child ASINs on one detail page behind an option selector. The variation theme names what differs between children (size, color, flavor, pack count), and allowed themes depend on the product type.

For a vendor the purpose changes. Amazon Retail holds the retail offer on every child (sellers may hold their own), so the family has nothing to do with your price, stock or the sale. Its job is navigation and shared content: one page to compare options, bullets kept consistent across children. A+ Content is applied in A+ Content Manager, to a parent with its children or to chosen children, not through the family relationship; Retail readiness covers A+ itself.

Variation values are attributes you submit like any other, so the contribution ranking Retail readiness explains applies to them. Reviews and traffic generally consolidate at the family level, so a broken family costs every child, not just the one that fell out.

Families are normally created in the new item setup spreadsheet under Bulk product submissions. Labels shift between template versions, so read the instructions: parentage (parent or child), a parent identifier on each child row matching the parent row's own identifier (vendor SKU or external ID in most templates, not the ASIN unless the instructions say so), relationship type (variation), the variation theme, and the theme's attributes on each child (size, color, flavor).

The parent row carries brand, base title, product type, theme and its own identifier, but no GTIN and no cost: Amazon does not buy a parent. Each child row is a complete item (unit GTIN, case data, images) plus its theme values. Submit a new family's parent and children in one file so the identifier resolves to the parent row.

Then read the submission status view: a child can be accepted as an item while its relationship fails, so read the row's status detail, not just the item-level status; if it shows no relationship detail, the option selector is the check.

Adding a child to a live family is a submission when the parent is your own record (otherwise a case; see Common problems). The loop:

1. Confirm the live parent's theme and the existing children's values, so the new child matches their attribute and spelling.
2. Submit the child row alone with the live parent's own identifier, relationship type variation and matching theme values.
3. Check the submission status for the item and for the relationship.
4. Check the option selector and the child's own page.
5. Log the result against the child ASIN.

By submission you control the child side: attributes, images, theme values (the Content updates paths). Structure is a case: moving children between parents, merging families, changing a theme, repairing a flattened family (children come apart into standalone pages), through Support → Contact Us, parent-child relationships category (labels change), with the parent ASIN, every child ASIN, the intended structure, the theme and each child's values. A vendor has no parent-deletion step; a moved child keeps its ASIN and reviews.

Read the family as a shopper; Retail readiness covers the whole page, these checks are family-specific:

• Selector completeness — every child appears with its own option name. A missing child usually means its relationship was refused or broken, but it can also be one Amazon has no offer on or has suppressed, or whose brand or product type mismatches the family; open its page before deciding.
• Swatch and image match — the swatch and main image follow the child you select. A blue child with a green image is that child's image-mapping problem, not a relationship problem.
• No collisions, no near-duplicates — identical theme values cannot both show; one child disappears. Values differing only in spelling or casing show as separate options, hence step 1 of the loop above.
• Child titles — in most categories a child shows the title you submitted, so write the variation values into it yourself; in some (apparel, typically) Amazon appends size or color itself. Judge the page, not your title verbatim.

• Duplicate ASIN for one variant — often a seller created one from the UPC first (Vendor catalog explains adding over recreating); the fix is a merge by case with both ASINs and GTIN evidence.
• Child showing as standalone — read that row's status detail. Mismatched theme values, an unresolved parent identifier or a disallowed theme: correct and re-submit. A clean row that changed nothing means a contribution you do not control holds the relationship (Amazon Retail's, another vendor code's or a seller's parent, as Retail readiness describes): open the case, then Case management's ladder if it stalls, BIN check included.
• Parent that became buyable, or a child that became a parent — a structural error no submission repairs; case it with the intended structure.
• Two vendor codes or two marketplaces — children under different vendor codes can share a family (the relationship lives on the ASINs); each account submits only its own items. Each marketplace has its own family; amazon.com's does not exist on amazon.de until you build it there.