Restructuring a variation family — the day-to-day moves.

Most live variation families weren't designed in one sitting — they accreted over months as new products launched, ownership changed, and category mappings evolved. Eventually the structure stops fitting the catalogue and a restructure becomes the right move. Episode 09 covers the three day-to-day operations; Episode 10 sequences them into a playbook for big migrations.

Operation 1 — Moving a child to a different parent

Edit the child row in a flat-file. Change parent_sku to the new parent. Confirm the new parent's variation_theme matches the child's theme exactly (else the upload errors out). Submit with update_delete = PartialUpdate so unrelated fields aren't touched. The child keeps its own ASIN, its own reviews, its own BSR history — only the family it pools with changes. Visible to shoppers within minutes of processing.

When to use it: a child was attached to the wrong parent at creation (e.g. a Large was filed under the Color parent instead of the ColorSize parent), a new parent is now the better home for an existing standalone, or a family is being consolidated from many parents into one.

Operation 2 — Splitting one family into two

1. Create the new (empty) parent first — see Episode 04. Make sure its category, brand and variation theme are correct before any child attaches.
2. Rehome the children that should live under the new parent (one row each, new parent_sku). Move in batches of 2–3, not all at once, so you can validate each batch before the next.
3. Leave the rest under the original parent unchanged.
4. Confirm both parents now have at least one child — Amazon may suppress a parent that ends up with zero children, and the cleanest fix is to never let it happen.
5. Update family-wide content on the new parent (A+, brand story, hero image) — the new parent inherits nothing from the old one.

When to use it: a family has grown past 15–20 children and is hard to manage, the variation themes within the family have started to diverge (some colour-only, some colour-and-size), or shoppers' search intent has split (the original family covers both gift-pack buyers and refill buyers).

Operation 3 — Merging two families into one

1. Decide which parent survives — keep the one with the better review history, the correct category, and the cleaner family-wide content.
2. Rehome every child of the losing parent. New parent_sku = the surviving parent's SKU. Validate each move's variation theme compatibility before submitting.
3. Delete the now-empty losing parent (Episode 08), or leave it for Amazon's cleanup if you'd rather not press delete.
4. Re-check the family A+ and main image on the surviving parent — anything family-wide that lived on the losing parent is now gone.
5. Repoint any active ad campaigns from the losing parent's ASIN to the surviving parent.

When to use it: two adjacent families really sold the same product (the catalogue split was historical), an acquired brand's family duplicates an existing one, or pooled reviews would meaningfully help SERP positioning of both families.

The risk to budget for — what flickers during a restructure

• The pooled review count visible on the family page. The underlying review records survive on each child, but the count visible to shoppers can flicker for hours while Amazon re-indexes — a 5,000-review family can briefly show 4,200 before settling.
• The Buy Box on each child. A child briefly orphaned during a multi-step rehome can lose Buy Box for minutes to hours. Use PartialUpdate single-row uploads to minimise the orphan window.
• Active campaigns. A Sponsored Brands campaign pointed at a deleted parent ASIN serves nothing until repointed. A Sponsored Products auto campaign continues serving children even if the parent moves.
• External backlinks. Any URL pointing at a deleted parent ASIN breaks. Set up redirects in your own channels (brand site, email, social bios) before the delete.

The four-batch rule

Never restructure more than four children in one upload. Smaller batches give clearer processing reports, let you stop early if something breaks, and keep the pooled review flicker contained to a smaller subset of the family at any given moment.