Trilha 01 · Módulo 04 de 4
Parenting and variations: building, fixing, and merging families
How parent/child relationships work, how to pick a valid variation theme, and how to create, re-parent, merge, split, and repair families with flat files or a support case.
6 min de leitura
Neste módulo você aprenderá a
- ✓Explain what a parent ASIN is — and what it is not.
- ✓Pick a valid variation theme for the product type and map every child to complete attribute values.
- ✓Create a family, attach existing children, and re-parent or split with a PartialUpdate flat file.
- ✓Recognize a broken family and choose between a flat file fix and a support case.
- ✓Review the finished family the way a shopper sees it.
Connect products for the right reason.
A useful variation family helps shoppers choose between related versions of the same product. Confirm the relationship, check the category's current variation guidance, and only then change the family.
What a parent really is
A parent is a non-buyable container: no offer, no price, no inventory, no GTIN. Its only job is to group child ASINs on one detail page behind an option selector. Each child keeps its own ASIN, SKU, GTIN, images, and offer; reviews roll up to the family.
Because the parent is not a product, its flat-file row has parentage = parent, a variation_theme, and no product_id. Give a parent a GTIN and the upload fails.
Families are worth building: consolidated reviews, one page to rank, and shoppers who discover the other options. They are also policy-controlled — grouping unrelated products, or products that differ in something the theme does not describe, is variation abuse and can take the whole family down.
Variation themes
The theme names the attributes that vary between children: Size, Color, SizeColor, Flavor, Scent, Style, Pattern, Material, ItemPackageQuantity, and combinations of them. Which themes are allowed depends on the product type — the template's Valid Values tab lists them for that type.
Every child must carry a value for every attribute in the theme: a SizeColor family needs both size_name and color_name on every child. Values must also be consistent. Blue, blue, and Navy Blue become three separate options in the selector, and two children with identical values collide.
Building a family in a flat file
A family is three kinds of rows in one category template:
- The parent row —
sku, product type, brand, title,parentage = parent,variation_theme. Noproduct_id, price, quantity, or images required. - New child rows —
parentage = child,parent_sku,relationship_type = variation, the samevariation_theme, the theme attributes (size_name,color_name…), plus everything a normal listing needs:product_id, price, quantity, images. - Existing children you are attaching — a PartialUpdate row with only the relationship columns (
parent_sku,parentage,relationship_type,variation_theme) and the theme attributes. Leave the rest blank so nothing else is overwritten.
Upload, read the processing report, wait for the page to rebuild, then review the family.
Re-parent, merge, split
- Re-parent — PartialUpdate the child rows with the new
parent_sku. The child's ASIN, reviews, and sales history stay with it. - Merge two families — pick (or create) the surviving parent, PartialUpdate every child of the other family onto it, then delete the now-empty parent SKU.
- Split a family — upload the children you want standalone with the relationship columns (
parent_sku,parentage,relationship_type) left blank on a full Update, or delete the parent SKU. Deleting a parent removes the relationship, not the children's listings.
One caveat: these edits only take effect on relationships your contributions control. If a family was built by another seller or the brand owner, your flat file can process cleanly and change nothing — which is the cue for the next section.
Broken families and when to open a case
You know a family is broken when a child shows as a standalone page, the option selector is missing options, the parent has been "flattened", or a child displays another parent's data. The usual causes: a theme mismatch, a child with a missing or inconsistent theme attribute, a deleted parent, or a higher-ranked contribution that defined a different relationship.
Try a clean PartialUpdate first — all children, all theme attributes, one consistent theme. If the processing report succeeds and the page still does not change, open a Seller Support case (Help → Get Support → Products and inventory → variation relationship) and include the parent ASIN, every child ASIN, the theme, the attribute values per child, and the batch ID of the upload. Brand Registry authority makes these cases markedly faster.
Page review
After the change, read the family as a shopper:
- every child appears in the option selector with the right label and swatch,
- each child's title, images, and price change when you switch options,
- reviews roll up to the family,
- no child is orphaned and no option is duplicated.
If any of those fail, the family is not done — regardless of what the processing report said.
Lembre-se
Only group related versions of the same product under the allowed theme. Brand similarity or convenience is not a family.
Coloque em prática
Cenário
A fictional family should hold the AquaTrail 750 mL bottle in Blue and Green. The proposed child list also includes an AquaTrail 350 mL insulated mug. The product type's valid variation themes include Color, Size, and SizeColor.
Exercício
- Separate the bottle color options from the different product type.
- Choose the theme that fits the two bottles, and list the attribute value each child needs.
- Review each child's identifier, color value, and images for consistency before you upload.
Mostrar uma abordagem sugerida
Evaluate the blue and green bottles as a Color family: same product, one attribute varying. Investigate the mug separately — it is a different product type, and sharing a brand does not make it a variation. Confirm both bottle children carry exactly the same color_name spelling convention and their own GTINs, and that the parent row has no product_id.
Verifique seu entendimento
Ir à fonte
Documentação oficial do marketplace para este módulo.
Consistent copy across every child
Vendara's Bulk Listing tool generates titles, bullets, and search terms for a parent and all of its children in one run, so the family reads as one product with clean, consistent option names.