Amazon Variations Not Showing on Your Listing? The Flat File Checklist
You uploaded a variation family, the feed status said successful, and yet the detail page shows no size dropdown, no color swatches — or only some of your child SKUs. This is one of the most misleading situations in Seller Central, because "upload successful" only means the file was processed, not that every row in it succeeded.
Work through these six causes in order. The first two account for most cases.
1. The relationship rows silently failed
Open the processing report for your upload: Catalog → Add Products via Upload → Spreadsheet Upload Status → Download your processing report. Feed status "successful with errors" (or even "successful") can hide row-level failures — a child that threw error 8016 or 8541 was simply skipped, and everything else went through. The family looks half-built because it is half-built.
If you find errors, fix those rows first — each error code page tells you which columns to repair — then re-upload.
2. A child has no active offer
Amazon only shows child variations that can actually be bought. A child row that was created but has no price or no stock is dropped from the selector without any error message. Check for each child:
| Column | Must be |
|---|---|
standard_price | Filled with a valid price — a child with no price never appears |
quantity | > 0 for merchant-fulfilled SKUs (FBA children show while in stock at a fulfillment center) |
The parent row is the opposite: it's a shell that holds the family together. It should carry no price and no quantity — a parent with its own offer is a classic cause of broken families.
3. A child is suppressed
A child SKU that gets suppressed — missing main image, missing required attribute — also vanishes from its parent's variation selector. Check Manage Inventory → Suppressed. If the missing children are listed there, fix the suppression and they'll rejoin the family; the variation structure itself is fine.
4. The parentage columns don't line up
The four structural columns must agree across the family — one inconsistent child breaks that child (or the whole family):
| Column | Parent row | Every child row |
|---|---|---|
parent_child | parent | child |
parent_sku | blank | The parent's exact SKU — watch for trailing spaces and case differences |
relationship_type | blank | variation |
variation_theme | A valid theme, e.g. SizeColor | Identical to the parent's value |
Also confirm each child actually fills the attribute columns its theme promises: theme SizeColor means every child needs both size_name and color_name. Two children with the same size and color values will also collide — each child must be a unique combination. For a full walkthrough of theme rules, see the error 8016 guide.
5. The family was edited in two different tools
Building the family by flat file, then touching one child in the web editor (or vice versa) is the classic way to detach children — the web editor can drop parentage fields the flat file set. Symptoms: the family worked for weeks, someone "just updated a price" in the browser, and a child fell out. Re-establish the relationship by re-uploading the structural columns above with update_delete = PartialUpdate, and pick one editing channel for structural work going forward.
6. You fixed it — Amazon just hasn't caught up
Variation changes propagate slowly: give a correct upload 24–72 hours before concluding it failed. Check the detail page in an incognito window (your cached session can show stale data). If it's still broken after 72 hours with a clean processing report, open a case with Seller Support and include your Feed ID.
Or skip the spreadsheet archaeology
Upload your flat file or processing report to FlatFileFix — it checks every family for broken parentage, missing offers, and theme mismatches, and gives you a corrected file. Diagnosis is free.
Fix my flat file →