Product variants let you sell one product in several sizes, colours or configurations without creating an unrelated record for each. SKULaunch can model products as a parent with variants, define which attributes vary between them, and publish the structure your ecommerce platform expects. How it is configured depends on your set-up and the platforms you publish to.
The problem
Supplier files list every SKU as a separate line. A t-shirt in five sizes and four colours arrives as twenty rows with nothing tying them together. Load that straight into a website and customers see twenty near-identical products, reviews are split twenty ways, and search results fill with duplicates.
Building the parent and variant structure by hand means grouping rows, deciding which attributes vary, and keeping shared content consistent across every variant. In a spreadsheet that usually ends with the description edited on one variant and not the other nineteen.
Before and after
An illustrative example from a workwear range.
Before: the supplier file
20 rows: SOFTSHELL-BLK-S, SOFTSHELL-BLK-M, SOFTSHELL-NVY-S and so on, each with its own title, description and image list.
After: modelled in SKULaunch
- Parent: Softshell work jacket, with shared description, material and care instructions
- Variation axes: Colour and Size
- 20 variants, each holding only its own SKU, EAN, colour, size and images
- Shared attributes set once at parent level
- Published as one product with options on the website
How it works in SKULaunch
- Define the product model. For each category, decide which attributes are variation axes, such as size, colour or length, and which are shared.
- Group SKUs into parents. Supplier rows are grouped into parent products using their codes, titles and attributes.
- Hold data at the right level. Shared content lives on the parent. Variant-specific values, such as size, colour, EAN and images, live on each variant.
- Publish the structure. Export to platforms that use options and variants, such as Shopify, or configurable products, such as Magento, with the relationships intact.
Parent level or variant level: where each attribute belongs
The test is simple to state and easy to get wrong: if the value is the same on every variant, it belongs on the parent. If it can differ between variants, it belongs on the variant. For the softshell jacket that splits like this:
- Parent level. Brand, product name, description, feature bullets, fabric, care instructions, category, size guide.
- Variant level. SKU, GTIN or EAN, colour, size, images, weight and stock-related codes.
Watch the attributes that look shared but are not. Weight often changes with size. Material can change with colour when a "heather grey" uses a different blend. Packaging dimensions change with pack quantity. If even one variant differs, hold the attribute at variant level, or the parent will publish a value that is wrong for some of the range.
Choosing variation axes for product variants
A variation axis should be something the customer chooses between on the page: size, colour, length, capacity, pack quantity. If the difference changes what the product is, such as a different voltage on a power tool or a different thread on a fitting, it is usually a separate product, not a variant, because the specifications, compliance and search terms differ.
Getting this right matters for search too. Variants consolidate signals into one page, while separate products let each rank for its own specification. A trade customer searching for an M10 fitting wants a page about M10, not an M8 page with a dropdown.
Axis values need the same discipline as any filter. If one supplier sends "Navy", another "NVY" and a third "Dark blue", the option selector shows three colours that are the same colour. Standardise axis values into controlled lists before you publish.
How platforms handle variants
Each platform names the same idea differently, and each has its own limits.
- Shopify. A product with options, such as Size and Colour, and a variant for each combination. Shopify limits how many options a product can have.
- Magento. A configurable product linked to simple products, with the configurable attributes acting as the axes.
- WooCommerce. A variable product with variations built from product attributes. See WooCommerce product import for the detail.
- Marketplaces. Parent and child listings tied together by a variation theme that has to match the marketplace's own list.
Model the variants once, at the right level, and map that model to each platform. Do not rebuild the structure separately for every channel.
Common variant modelling mistakes
- Colour and size held only in the title, so nothing can be grouped or filtered.
- Different products forced together as variants because they share a name.
- Shared descriptions copied onto every variant, then edited on some and not others.
- Mixed size systems on one axis, such as "M", "40" and "Medium".
- Too many axes, so most combinations do not exist and the selector fills with dead ends.
What changes
Supplier rows become proper products with options. Shared content is written once, variants stay consistent, and the website shows one product per item instead of a wall of near-duplicates.
Common questions
What is the difference between a product and a variant?
The product, or parent, is the item the customer thinks of. Variants are the versions they choose between, each with its own SKU and barcode.
What are variant attributes?
The attributes that change between variants. The ones the customer selects, such as size and colour, are the variation axes.
Can a product have more than two variation axes?
Yes, as long as your ecommerce platform supports it. Most ranges work best with one or two.
What if variants have different images?
Images are held per variant, so the navy jacket shows navy images.
Can we change the axes later?
Yes. The product model can be adjusted and products regrouped.
Does variant modelling work with our platform?
It depends on your set-up and where you publish. Confirm your platforms and variant structure with us and we will show how it maps.
More on the PIM platform, PIM for Shopify, category-specific attributes, and our guide to product attributes.

.avif)