Adding a brand-new child to a live variation family.

This is the most common variation edit on Amazon: an existing family ships a new colour, size or scent and you add it as a child of the live parent. The workflow is a single new row, attached to the existing parent — no need to re-touch the parent row, no need to re-upload the existing children.

When to use this workflow

• A new SKU in an existing colour-themed apparel family.
• A new pack size (10-pack added to an existing 1/2/4/6-pack family).
• A new scent in a fragranced product line.
• A new bundle option inside a quantity-themed family.

Use this workflow when the family structure itself isn't changing — the theme stays the same, the parent stays the same, only the child list grows by one.

The single-row upload — the exact columns

• item_sku = your new child SKU.
• parent_child = child.
• parent_sku = the SKU of the live parent — exact match.
• relationship_type = Variation.
• variation_theme = the theme already on the parent (do not change it; if the upload tries to change the parent's theme, the whole family can suppress).
• Attribute value for the theme (e.g. color_name = Sand) — must be in the category's Valid Values list and not already used by another child.
• external_product_id + external_product_id_type = the new child's GTIN. Distinct from every sibling's GTIN.
• Title, bullets, description — only the bits that need to override the parent for this specific child. Leave blank where the parent's value is correct.
• Child-level main image (main_image_url), additional images, child-level price and child-level stock.
• update_delete = Update or PartialUpdate — use PartialUpdate on subsequent child edits to avoid wiping fields you didn't specify.

What the new child inherits from the parent automatically

Brand, category / browse node, family-wide A+ content, brand story, the family-wide hero video, family-wide bullets where the child doesn't override, family-wide images where the child doesn't override, the title pattern where the child's title is blank. The cleaner the parent, the less the child needs to specify — a well-architected parent means a new child can ship with as few as 8 filled columns.

The pre-launch QA — five checks before shoppers see it

1. The new child appears in the family selector on the parent's detail page (colour swatch, size button, or pack pill depending on theme).
2. The thumbnail in the selector is the child's own main image — not the parent's, not a duplicate of a sibling's. If you see the parent's image in the selector, the child's main image hasn't propagated yet (allow 30–60 minutes).
3. The price, stock, and Prime eligibility show correctly when the child is selected.
4. The child has its own dedicated child URL (the canonical /dp/<child-ASIN>), even though the page rendered is the parent's page with the child selected.
5. The child's GTIN doesn't collide with any other child in the family or any other ASIN in your catalogue.

The most common surprise — and how to avoid it

If the new child's images aren't uploaded by the time the flat-file row processes, Amazon falls back to the parent's main image in the selector. The selector then shows the parent image in two slots — the original placement plus the new child's slot — and shoppers can't visually distinguish the new option. The fix is order-of-operations: upload images to Amazon's CDN first, wait for them to propagate (Image Manager → image URL shows live), then push the flat-file row with the image URL filled in.

The flat-file vs UI choice

For a single new child, either the Seller Central UI (Edit listing → Variations tab → Add a variation) or a single-row flat-file works. For more than one new child at a time, always use a flat-file — the UI processes them serially with its own race conditions, while the flat-file processes them as one batch with one consistency check.