How to Audit Textile Data Across Shopify Variants
Variants of one product often carry different or missing material data, because data was added colour by colour or size by size. Group your export by product and compare variants, and any difference is either a real difference or an error.
For a catalog-wide method, see the general audit guide. This article covers variant conflicts only.
Why variants break data
- Shopify variants share one product description, so a single description cannot describe two fabrics.
- Variant-level fields get filled for some colours and forgotten for others.
- Imports overwrite some variants but not others.
- Contrast colours or trims use a different fabric, and nobody records that.
Typical conflict patterns
| Pattern | Example | Likely cause |
|---|---|---|
| Missing on some variants | Origin present for Black, blank for Navy | Partial import |
| Different values | Black: 100% cotton. Ecru: 95% cotton, 5% elastane | Real difference or typo |
| Product text vs variant field | Description says 100% cotton, variant says cotton blend | Edited in one place only |
| Different origin by size | Made in Turkey for S–M, Made in Portugal for L–XL | Split production not reflected in listing |
| Percentages not summing to 100 | 60 + 30 = 90 | Missing fiber |
The CSV method
- Export all products with variant and metafield columns.
- Sort by product handle, then variant.
- In a spreadsheet, add a helper column that concatenates fiber content, origin and care for each row.
- For each handle, count distinct values of the helper column (a pivot table or
COUNTIFSapproach works). - Filter handles with more than one distinct value or any blanks.
- For each hit, decide: real difference or error?
Deciding what is a real difference
Compare with the supplier specification or the physical label. If the colourways really use different fabrics, the page needs to say so clearly, or the listing should be split so each fabric has its own product. If they do not differ, correct the outlier.
Fixing at the right level
Put fiber content and origin at product level when they are the same for every variant. Use variant-level fields only for genuine differences. See the metafields guide.
Prevent it coming back
- Make the product-level field the only place for shared data.
- Run the helper-column check after every large import.
- Record the date of your last variant check in the matrix.
Frequently asked questions
Should different colours be separate products? If the fabric or origin differs, separate products often make the data cleaner. It is a merchandising decision as well as a data one.
Can I check this without a developer? Yes. A CSV export and a pivot table are enough.
Is a mismatch always a legal problem? Not necessarily, but information on a listing that does not match the label can mislead customers, so treat each as something to resolve.
Related guides
Sources: Shopify Help Center, Export and import products · FTC, Threading Your Way Through the Labeling Requirements
Not legal advice. Check requirements for your products and markets.