Product variants: how to organize sizes and colors in a feed
A beginner-friendly guide to avoid duplicates, wrong grouping, and unnecessary ID changes when you sell the same product in multiple options.
Julia Villegas

Product variants are the different versions of the same item: for example, one T-shirt sold in several sizes and colors. If you organize them poorly in your product feed, you can create duplicates, break ad history, or send inconsistent product data to each channel. The fix starts with separating parent product, variant, SKU, and attributes.
What product variants are in a feed
In an online store, a product is not always one single item. Very often, it is a family of options. A sneaker may come in several sizes; a sofa may come in different fabrics; a suitcase may come in multiple colors. Each option that can be purchased separately is a product variant.
In a product feed, that distinction matters because advertising and commerce platforms need to understand two things at the same time:
- Which items belong to the same base product.
- What makes each purchasable option unique.
Here is the simplest way to think about it:
| Concept | What it means | Example |
|---|---|---|
| Parent product | The shared product that groups options | Basic cotton T-shirt |
| Variant | A purchasable version of that product | Basic T-shirt, blue, size M |
| SKU | Your internal code for the variant | TSH-BASIC-BLU-M |
| Product ID | The identifier sent to the channel | 12345-BLU-M |
| Variant attribute | The difference between options | Color, size, material, capacity |
A common mistake is using the same individual identifier for every variant. The opposite mistake is treating every size and color as a completely unrelated product when they should be grouped. Both can create problems: duplicate listings, products competing with each other, rejected items, or lost learning if you change IDs without a real reason.
Google’s product data specification explains that product data should accurately describe the product and match the landing page. It also notes that required attributes can vary depending on the product type, country, and program. Pinterest’s documentation on getting started with catalogs also emphasizes preparing a coherent commercial data source before sending products.
This guide is not about memorizing every attribute required by every channel. It is about building a clean foundation so you can adapt your feed without improvising every time.
Why product variants matter for catalog ads
When you run catalog ads, Shopping campaigns, or dynamic product ads, your feed is not just a list of items. It is the raw material for the campaign: titles, images, prices, availability, URLs, categories, and variants all affect what the platform can show.
If your variants are poorly structured, you may see issues such as:
- Visible duplicates: the same T-shirt appears several times and users cannot tell the difference.
- Wrong grouping: one size is mixed with another color, fabric, or old version.
- Lost history: you change product IDs and the channel treats existing products as new.
- Warnings or disapprovals: price, availability, or URL does not match the landing page.
- Unclear creatives: the image shows one color, but the title or attribute says another.
For an ecommerce manager, this means more manual work and less control. For an agency, the problem multiplies across clients and channels. For a performance marketer, it makes reporting harder: you cannot tell whether a variant is underperforming because of demand, price, image, stock, or a feed structure problem.
The practical rule is simple: every purchasable variant needs its own stable identifier and its own data; every family of variants needs a clear way to be grouped.
SKU, parent ID, and variant attribute: the minimum structure
Before you edit your feed, it helps to understand three pieces that should not be mixed together.
SKU: your internal inventory code
The SKU is usually the code your store, ERP, or operations team uses to identify a sellable unit. It does not need to be pretty or customer-friendly, but it should be unique and stable inside your own system.
Fictitious example:
- Product: Essential organic T-shirt
- Color: Green
- Size: M
- SKU:
ESS-TSH-GRN-M
The SKU helps connect your catalog, inventory, orders, and logistics. If you change it without a strong operational reason, you can make internal tracking harder.
Variant ID: the identifier the channel sees
The feed ID is the identifier you send to the advertising or commerce platform. It may be the same as the SKU, but it does not have to be. What matters is stability. If a variant is still the same real-world item, do not change its ID just because you improved the title, replaced the image, or updated the price.
Changing historical IDs unnecessarily can make a channel treat existing products as new items. During a feed cleanup or migration, the safer approach is to keep IDs when they still represent the same real variant.
Parent ID: the group the variant belongs to
The parent ID, often called item group ID in some feed environments, groups the variants of the same product. All Essential T-shirts, across sizes and colors, may share the same parent ID. Each variant still keeps its own individual ID.
Fictitious example:
| Parent ID | Variant ID | SKU | Color | Size |
|---|---|---|---|---|
| ESS-TSH | ESS-TSH-GRN-S | ESS-TSH-GRN-S | Green | S |
| ESS-TSH | ESS-TSH-GRN-M | ESS-TSH-GRN-M | Green | M |
| ESS-TSH | ESS-TSH-BLK-S | ESS-TSH-BLK-S | Black | S |
| ESS-TSH | ESS-TSH-BLK-M | ESS-TSH-BLK-M | Black | M |
This allows the channel to understand that these are options of the same product, while each row remains a distinct item that can be bought, measured, and advertised.
How to prepare product variants without creating duplicates
The safest way to organize variants is to work from the inside out: first your store data, then your master feed, then the version required by each channel.
1. Audit the fields you already have
Start by reviewing your current data. Do not try to fix everything at once. Look for these columns, or their equivalents:
- Product or variant ID.
- SKU.
- Title.
- Product URL.
- Image URL.
- Price and sale price, if applicable.
- Stock or availability.
- Color, size, material, capacity, or another variant attribute.
- Category.
- Brand.
- Parent ID or grouping field.
If key attributes are hidden in the title, for example “Essential T-shirt Green M”, make a note of it. You may need to extract color and size into separate fields.
2. Decide what each feed row represents
For catalog ads and commerce feeds, each row usually represents a purchasable variant, not only the parent product. If you sell a T-shirt in three sizes and two colors, you will usually have six rows.
Each row should carry its own specific data:
- Stock should match that size and color.
- Price should match the variant if there are differences.
- The image should represent the right option, especially when color changes.
- The link should open the correct product and, where possible, make variant selection easy.
Not every channel asks for exactly the same attributes, and requirements may vary by market, product category, and program. That is why it is useful to keep a complete master feed and then export channel-specific versions from it.
3. Keep historical IDs when the variant has not changed
A feed cleanup should not become a full renumbering project. If “Essential T-shirt Green M” already exists and is still the same item, keep its ID.
You can improve:
- Title.
- Description.
- Image.
- Category.
- Color or size attributes.
- Internal labels or segments.
But avoid changing the identifier just to make it look neater. If you truly need a new ID convention, document the relationship between old and new IDs carefully. In many cases, it is better to keep the external ID stable and organize the rest of the fields around it.
4. Separate variant attributes into their own columns
Titles help users understand the product, but they should not be the only place where important variant information appears. “Blue linen dress size 38” can be a useful title, but your feed should also have structured fields such as:
color: Blue.size: 38.material: Linen.genderor audience, if relevant and required by the channel.age_group, when relevant.
This reduces ambiguity and makes it easier to build product sets. For example, you can create sets for “women’s sandals in stock”, “black products with high margin”, or “available extended sizes” only if those attributes exist in structured fields.
5. Check consistency between product, URL, price, and stock
A variant can have the right ID and still fail if the data does not match your store. Pay special attention to:
| Check | Practical question |
|---|---|
| Link | Does the URL open the correct product? |
| Price | Does the feed price match the landing page? |
| Stock | Does availability reflect the real variant? |
| Image | Does the photo match the advertised color or model? |
| Title | Does it distinguish the variant without keyword stuffing? |
| Parent ID | Does it group only true variants of the same product? |
This matters because platforms do not evaluate feed data in isolation. They also compare it with the landing page and with the account’s business and commerce requirements.
Fictitious example: a sneaker store
Imagine a store selling the “Runner City” sneaker in two colors and three sizes. At first, its feed has this problem:
| ID | Title | Color | Size | Stock |
|---|---|---|---|---|
| runner-city | Runner City | In stock | ||
| runner-city | Runner City | In stock | ||
| runner-city | Runner City | In stock |
The three rows look like the same product. The channel cannot tell which variant each row represents. Also, if stock changes for one size only, there is no clean way to show that.
A more organized version would be:
| Parent ID | Variant ID | Title | Color | Size | Stock |
|---|---|---|---|---|---|
| runner-city | runner-city-black-40 | Runner City black size 40 | Black | 40 | In stock |
| runner-city | runner-city-black-41 | Runner City black size 41 | Black | 41 | Out of stock |
| runner-city | runner-city-sand-40 | Runner City sand size 40 | Sand | 40 | In stock |
The difference is not cosmetic. Now every row describes a real option. You can exclude out-of-stock variants, group by parent product, and build product sets for specific campaigns.
How to organize product variants with AdMotion
If you manage many SKUs, reviewing variants manually in a spreadsheet becomes fragile. With AdMotion Feed Manager, you can connect a store or import a product file, map fields, normalize data with rules, filter sets, and generate feed URLs for your channels.
A practical workflow would look like this:
- Connect the product source. Start from a supported store or from a product file/feed. The source should contain coherent product, URL, price, stock, and variant data.
- Map your fields. Match your catalog fields to the data you need to work with: ID, SKU, title, price, availability, image, color, size, and parent ID if it already exists.
- Normalize values with rules. If your colors appear as “Black”, “black”, and “Jet black”, you can use rules to standardize them. You can also clean titles or complete derived fields when the data supports it.
- Create variant sets. Filter useful groups such as in-stock products, discounted variants, seasonal categories, or complete product families with all required attributes.
- Generate the output feed. Publish the feed with a URL generated on each download and use it in the relevant channel. Remember that your feed import frequency and the channel’s processing frequency are separate; do not assume instant synchronization inside the channel.
- Review ingestion errors. Check channel warnings, territorial availability, and feed analyzer feedback before scaling campaigns.
AdMotion can also use catalog fields to create product-level creatives with the Templates Editor, showing elements such as image, brand, price, or offer in 1:1, 4:5, 9:16, and 16:9 formats. For this guide, however, the priority is feed structure: creative automation works better when size, color, price, stock, and product identity are clean.
If you manage several destinations, Export Channels can help prepare feeds for Meta, Google Shopping and Dynamic Feed, TikTok, Pinterest, Snapchat, Criteo, Microsoft Advertising, Thribee, ChatGPT, or a custom channel, with each feed checked against the relevant specification.
Common mistakes when working with variants
Even stores with strong catalogs can run into avoidable issues. These are the ones to watch first.
Using the same ID for several variants
If multiple rows share the same individual ID, the channel may overwrite data or fail to distinguish products. Use one unique ID per purchasable variant, and use a parent ID for grouping.
Changing IDs for seasonal campaigns
Do not create new IDs just because Black Friday, Christmas, or a sale period is coming. Change price, labels, titles, product sets, or creative fields, but keep the identifier if the product is the same.
Grouping products that are not true variants
A dress and a jacket from the same collection are not variants of each other. They may share a campaign, label, or merchandising theme, but they should not share the same parent ID. Reserve the parent ID for versions of the same base product.
Hiding the variant only in the title
If color or size appears only in the title, it becomes harder to filter, create rules, and troubleshoot errors. Whenever possible, use dedicated columns.
Forgetting the landing page
Your feed may say “in stock”, but if the page shows the item as unavailable, you have a consistency problem. The relationship between feed and website is just as important as the file format.
What to do this week
- Export a sample of your current feed. Choose products with variants and check whether each row represents a purchasable option.
- Identify three critical columns. Find the individual ID, SKU, and parent ID. If there is no parent ID, define how you could create one without deleting historical IDs.
- Check variant attributes. Review whether size, color, material, or capacity are in their own fields or hidden in the title.
- Look for real duplicates. Filter repeated IDs, identical titles, and variants with the same URL, price, and stock. Not every duplicate-looking row is wrong, but every one deserves review.
- Validate one channel before scaling. Send a corrected feed to one priority destination and review ingestion errors, territorial availability, and consistency with your store.
Start with the channel that matters most to your current investment: Google Shopping, Meta, Pinterest, or another catalog destination. If you want to clean the catalog before exporting it, you can centralize the work in Feed Manager and use sets to separate ready variants, out-of-stock variants, and items that still need review.
A solid variant structure does not guarantee ad results by itself, but it removes a lot of noise: every size, color, and version is identified, grouped, and ready to be adapted to the channel that needs it.
Frequently asked questions
What is the difference between a SKU and a product ID?
A SKU is usually the internal code your store uses for inventory, orders, and operations. A product or variant ID is the identifier you send to an advertising or commerce channel. They can be the same, but they do not have to be. What matters is that every purchasable variant has a unique, stable ID.
Should I create one row for every size and color?
For most catalog ad and commerce feeds, yes: each purchasable combination should have its own row. That lets you send specific price, stock, image, and URL data for that variant. A parent ID can then group those rows as versions of the same base product.
Can I change product IDs when cleaning up my feed?
It is better to avoid changing IDs if the variant is still the same real item. You can improve titles, attributes, images, categories, and labels without changing historical IDs. If you change identifiers unnecessarily, some channels may treat existing products as new, making catalog review and tracking harder.
Sources
- Especificación de datos de producto de Google — Google
- Primeros pasos con catálogos de Pinterest — Pinterest
- Feed Manager de AdMotion — AdMotion
Related posts

Product feed format: CSV, XML or Google Sheets?
Choosing between CSV, XML and Google Sheets is not just a technical preference. It depends on catalog size, update frequency, team workflow and the ad channels you need to feed.

Feed rules: how to clean titles, prices and descriptions without editing products one by one
Feed rules help you fix repetitive catalog data issues without editing every product manually. Learn how to remove HTML, normalize prices and improve titles with a safe, reviewable workflow.

Product titles: how to clarify variants without stuffing your feed
Product titles help Google Shopping, Meta and other channels understand what each catalog item is. Learn a simple brand/type/attribute pattern to describe variants clearly without artificial keyword stuffing.