Error 8016: your parent and child don't agree on the variation theme

Amazon rejects the relationship, not the products. The rows upload fine — they just don't become a variation family. Here's what actually causes it and how to find it in your file.

What the error says

The processing report gives you something close to this, per SKU:

The message names the SKU but not the mismatch. If you have 200 children across 15 families, you get 200 lines that all say the same thing and none that says which column is wrong.

What it actually means

A variation family on Amazon needs three things to line up: a parent row, child rows pointing at that parent, and one shared variation theme that every row in the family declares identically. Error 8016 means at least one of those three broke.

The important part: your products may list perfectly well as standalone items. What failed is the relationship between them. That's why the error is confusing — Seller Central shows the SKUs live, just not grouped, and a customer sees six separate listings instead of one with a size picker.

The four causes, in the order you should check them

1. Parent and children declare different themes

The parent says Size, a child says SizeColor. Every row in the family must carry the exact same value in variation_theme — same spelling, same capitalisation, no trailing space.

This is the most common cause and the easiest to miss, because it usually comes from editing one family by hand after copying rows from another.

2. The theme is declared but its attribute columns are empty

If the theme is SizeColor, then every child needs both a size value and a colour value. A child with a size and a blank colour fails, even though the theme matches everywhere.

Amazon reads the theme as a contract: you told it which columns define the variation, so those columns can't be empty on any child.

3. The child points at a parent that isn't in the file

A typo in parent_sku, or a parent row you removed while cleaning up. The child references a parent SKU that the upload never sees, so there's no family to join.

4. The relationship type is wrong or missing

Children need relationship_type set to variation. Blank, or set to something else, and the row is treated as an unrelated product.

How to fix it

1. Sort by parent_sku. Every family becomes a contiguous block and mismatches become visible instead of scattered across hundreds of rows.
2. Check the theme column per block. One value per family, no exceptions. Watch for trailing spaces — they're invisible and they break the match.
3. Check the theme's own columns are filled on every child. If the theme names two attributes, both are mandatory.
4. Confirm every parent_sku referenced exists as a parent row in the same file.
5. Re-upload the whole family together — parent and all children in one file.

One trap worth knowing

Mixing manual edits in Seller Central with flat file uploads on the same family is a reliable way to end up with a relationship that looks correct in your spreadsheet and is broken in Amazon's catalog. If a family has been edited both ways, expect to have to resubmit it whole.

Catching it before the upload

Every cause above is visible in the file itself, before Amazon ever sees it. A theme mismatch, an empty attribute column, an orphaned parent_sku — all of it is checkable locally, in seconds, against the rows you already have.

The reason it usually isn't checked is that doing it by hand across a few hundred rows is tedious and easy to get wrong, and the alternative has historically meant uploading your catalog to someone else's service.