The practical answer
Preserve the source table, map identifiers and attributes, then run variation validation. Resolve missing parents before checking combinations and themes. A pass means the supplied file meets the checker’s structural rules. Verify marketplace-specific category eligibility, required attributes and the eventual Seller Central processing result separately.
Different SKUs can still describe one variation
A SKU identifies a record; color and size describe the customer’s choice. Appending BLUE-2 does not create a different color. Decide whether the rows are an accidental copy or genuinely different products before correcting, combining or moving them. Never invent an attribute merely to remove a warning.
The official Amazon relationship workflow describes a non-buyable parent and children that reference its SKU with a matching theme. Our six-column CSV is a simplified review input, not an official upload template or API payload.
Three separate questions
Record identity
Keep each SKU traceable to its original record; a display name or color is not an identifier.
Family membership
The child’s parent reference must resolve to a parent record in the supplied data.
Customer choice
Within one parent and theme, the relevant color or size values determine whether the checker reports a repeated combination.
Reproduce two errors with four fictional records
Save this example as UTF-8 CSV. It contains no real ASINs, accounts or orders. Color is an example input value, not evidence that your category accepts that theme. Include the whole family: a parent that exists in your store but is omitted from the file cannot be found by this local check.
These headers match the tool’s field keys, but review the mapping after import. If your source is JSON, follow the CSV and JSON conversion checks first. Preserve SKU strings, empty values and column names instead of allowing spreadsheet software to reinterpret identifiers.
sku,parent,parentage,theme,color,size
DEMO-MUG,,parent,Color,,
DEMO-MUG-BLUE,DEMO-MUG,child,Color,Blue,
DEMO-MUG-BLUE-2,DEMO-MUG,child,Color,Blue,
DEMO-MUG-RED,DEMO-MISSING,child,Color,Red,| Field | Meaning | Review |
|---|---|---|
| sku / parent | Record ID / parent reference | Leave parent blank for the parent; children need the complete parent SKU. |
| parentage | parent or child | Use these exact lowercase input values. |
| theme | Variation theme | Match parent and children; use approved values for a real submission. |
| color / size | Variation attributes | Fill attributes used by the theme; this Color example leaves size blank. |
Import, map and locate the findings
- Open Amazon Listings, choose Variation validation and upload variation-demo.csv, or paste it into the source data area.
- Review SKU → sku, parent SKU → parent, parentage → parentage, theme → theme, color → color and size → size. Confirm the source and required fields before running.
- Find DEMO-MUG-RED first. DEMO-MISSING is absent from this file. Check source evidence before correcting the reference or including a genuine parent record.
- Inspect DEMO-MUG-BLUE-2 next. It shares the same parent and Color/Blue values as the earlier blue child. Input order determines the earlier row referenced by the finding; identify records by SKU.
| Record | Status | Reason |
|---|---|---|
| DEMO-MUG | pass | Parent has no parent reference; structural checks pass. |
| DEMO-MUG-BLUE | pass | First Blue combination; no structural finding. |
| DEMO-MUG-BLUE-2 | review | Combination duplicates row 3, despite a different SKU. |
| DEMO-MUG-RED | review | Valid parent DEMO-MISSING is not found. |
Result row numbering includes the header as row 1. Row 3 is the first blue child here. Sorting changes row numbers, so retain stable SKUs.
Correct facts, then run the repaired file
For this demonstration, suppose source records confirm that the third item is actually green and the red item belongs to DEMO-MUG. Change the third SKU to DEMO-MUG-GREEN and its color to Green; change the red item’s parent to DEMO-MUG. Without that evidence in a real workflow, keep the findings unresolved instead of copying these changes.
Reimport, confirm mapping and run again. Expect four pass rows, each still stating that category eligibility needs review. Download CSV or XLSX and reopen it to inspect identifiers, statuses and messages. Use the report ZIP to retain source context and mapping. Editing inputs invalidates the previous result, requiring a new run.
An evidence-based correction
BLUE-2 = Blue; RED parent = DEMO-MISSING
GREEN = Green; RED parent = DEMO-MUG
What does a pass leave unchecked?
Amazon’s variation guidance ties eligibility to category support and the actual product differences. Check the current template or product type definition for your marketplace before submitting, then inspect the processing outcome and product page. A downloaded local report does not show platform acceptance.
The current checker recognizes color and size within the theme string; it does not retrieve Amazon product type definitions. Other attributes, including NumberOfItems, need separate validation. Even a compound theme containing Color may need fields absent from this simplified table. Parent and child theme strings are compared exactly, whereas combination values are normalized. Verify official spelling independently.
Duplicate SKUs, self-references, parents that reference another parent, invalid parentage and missing color or size values can produce review findings. The result cannot verify brand facts, genuine products, review relationships or live catalog membership. If AI previously merged your product tables, use the stable-identifier checks for merged lists to preserve record evidence first.
Before the actual submission
- Review a complete family and retain the original table plus evidence for changes.
- Reopen the export and compare all four demonstration SKUs and attributes with expected results.
- Check current marketplace and category requirements; assign unresolved items for review.
- Inspect the official processing report and live page after submission.
File limits and local records
Use this checker for supplied files before submission. Data runs allow up to 10 MB, 10,000 rows and 300 columns. Consider the combined size of multiple files and explicitly select a worksheet. Validate mappings on a small sample, then review complete families; splitting parents and children into separate batches can create misleading missing-parent findings.
This file check runs locally in your browser and does not connect to or modify Amazon stores. Drafts and project reports remain in that browser; clear unneeded local records on shared computers. Import only necessary product fields, excluding buyer details or account secrets. Keep downloaded report versions and access permissions under your team’s normal process.
Common questions
Why do different SKUs produce a duplicate warning?
The checker compares the parent, theme and corresponding color or size values separately from SKU identity. Two Color/Blue children of one parent repeat a combination; review actual product facts.
Can I submit immediately when every row passes?
A local structural pass is insufficient. Check the official template, required product type attributes, permitted themes and processing outcome. This tool does not publish listings.
Why is a parent missing when it exists in my store?
The checker sees only the current file. An omitted parent or mismatched reference, including identifier case, can prevent a match. Include genuine family records and verify the relationship without inventing a parent.
Further reading & sources
Put the guide into practice
Open the relevant tool, preview the result and check your exported file.
