Variant Import

Effortlessly manage and integrate variants with our comprehensive guide on Variant Import

Unlock the power of Variant Import to seamlessly create configurable product variants in your PIM system. Learn how to efficiently manage and integrate variants for a streamlined product management experience.

Required Headers

To successfully perform a Variant Import in your Product Information Management (PIM) system, ensure that your import file contains the following required headers with accurate values:

  1. variant_sku

The SKU for the variant or child products. Typically, a child product's SKU includes the parent SKU and the variant attribute value. This value must be unique in the PIM system. Import will validate and provide a message for any existing variant_skus.

  1. sku

The SKU of the parent product to which the variants belong.

  1. variant_attribute

This field should contain the variant attribute code. If a variant product has multiple variant combinations, use the "+ number of variant" prefix. For instance, with a single variant, the header would be "variant_attribute-1". For two variant combinations, use "variant_attribute-1" and "variant_attribute-2".

  1. attribute_code

This header contains the values of the variant attribute code. For example, if you're creating variants based on RAM, the attribute header would be "ram-en_US". This field is optional if the variant attribute already exists for the product, but mandatory for creating a new variant.

To ensure a successful import, please keep the following in mind:

  • Variant attributes must be select attributes in your PIM. If a variant attribute isn't a select attribute, the import will generate a validation error message in the import log.

  • Verify that the variant combination you're trying to create doesn't already exist. If you attempt to create a variant with an existing combination, an error message like "This combination of values variant is present" will be displayed.

  • Ensure that all child products have the same number of variant attributes. If a parent product has a Storage variant, any new child products must also include a Storage variant. To add new variant combinations, remove the existing variant products and start fresh. If the variant combination count doesn't match the parent product, you'll see an error message in the import log: "Please provide the same number of variant attributes as the parent."

  • Check that the newly created variant option values are available as attributes. If not, add the options under the corresponding attribute before performing the import.

The process of updating or adding new attribute values for variants is quite straightforward. Simply utilize the specific attribute code along with the appropriate locale code header, and you'll be able to smoothly update or create the desired information. 

Variant Import Sample Sheet

Last updated