Creating parent and children together — the standard variation upload.

The standard workflow for a brand-new variation family is a single flat-file upload — one parent row and one row per child, submitted together. The three columns that decide whether it lands in one shot are parent_child, parent_sku and variation_theme. Everything else can be patched after the fact; these three cannot.

Picking the right template

Amazon ships a category-specific flat-file template (download from Catalogue → Add Products via Upload → Inventory Files for Non-Media Categories). Always download a fresh copy for the exact browse node — column sets drift between categories, and a Shoes template won't validate a Kitchen family. The template has three sheets that matter: Template (the rows you fill), Data Definitions (the spec for each column) and Valid Values (the controlled vocabularies — variation themes, colour names, size names).

The parent row

• item_sku = a unique SKU you assign to the parent (e.g. BRAND-FAM-PARENT).
• parent_child = parent
• parent_sku = blank (the parent doesn't have a parent of its own)
• variation_theme = the theme you picked (e.g. Color, Size, ColorSize). Must be a value from the Valid Values sheet for this category.
• relationship_type = Variation
• Brand, category (item_type or recommended_browse_nodes), title-template, family-wide bullets, family-wide A+, family-wide hero image — all filled.
• Every child-specific field (size, colour value, child SKU, child GTIN, child price) — blank.

The child rows

• item_sku = each child's own unique SKU (e.g. BRAND-FAM-RED, BRAND-FAM-BLUE).
• parent_child = child
• parent_sku = the SKU of the parent row above — exact match, including capitalisation and whitespace.
• variation_theme = the same theme as the parent. Different theme = the row is rejected as orphan.
• color_name / size_name / etc. = the attribute value that distinguishes this child. Must be in the Valid Values list (Amazon enforces a controlled vocabulary on colour names in some categories).
• The child's own GTIN (external_product_id + external_product_id_type).
• The child's own price, stock, child-level main image, and any per-child overrides for title, bullets or description.

The submission

Upload from Catalogue → Add Products via Upload → Upload your Inventory File. Pick the correct browse-node template and the file. Amazon queues it (usually minutes, sometimes hours during Q4) and returns a Processing Report. The report is the source of truth — read it row by row.

Validation — the eight checks that catch 90% of failures

1. Every child's parent_sku matches the parent row's item_sku exactly.
2. Every row has the same variation_theme.
3. Every row has the same relationship_type = Variation.
4. Every child has an attribute value for that theme (no blanks on color_name for a Color family).
5. No two children share the same combination of theme values (no two reds; for ColorSize, no two "Red / M" rows).
6. Every child has its own GTIN, distinct from siblings.
7. The parent row's category is one that allows the theme you picked.
8. Brand is identical across parent and every child.

Reading the processing report

Errors come back with a row reference and a code. The most common codes:

• 8541 / 5461 — variation theme mismatch between child and parent.
• 8542 — parent_sku on a child row doesn't match any item_sku in the file or the live catalogue.
• 5665 — duplicate attribute combination across two children (two "Red / M" rows).
• 8016 — category doesn't allow this variation theme; pick a different theme or different category.

The recovery pattern when only some rows succeed

Amazon processes each row independently. If the parent row succeeds but two children fail, you have a live parent with three children attached and two missing. Don't re-upload the whole file — that re-processes the live parent and risks contaminating its content. Instead, fix only the failed rows and re-upload as a single-row file per child. The fix is targeted and the live family stays intact.