![](\"https:\/\/cdn.opendims.com\/defaultdb\/assets\/OpenDIMS%20-%20Variants%20in%20integration.png\")
<\/p>\n","protected":false},"excerpt":{"rendered":"Variants, variations and main products can be difficult to keep track of – especially when they are in a flat file such as csv. Therefore, when importing variations into OpenDIMS, it must be done in a certain way. <\/p>\n
The start of the integration setup MUST look like this!<\/p>\n
The first merge MUST be SKU merge (e.g. ItemNumber) for the variants, with “Update on match” active.
The next MUST be the main product SKU generation and merge to recipient field type “Variation”, due to the first merge this will be saved in the same field as in the first merge.<\/p>\n
Then the variant fields MUST be merged (when creating a field in the integration’s setup, they are NOT correct, but must be corrected to the “One value” type).
Variant fields do not have to be the same columns as the main product sku, but can be color or different fields.<\/p>\n
Since the main products have no values in this run, you can set up a new integration that updates the main products and matches the same SKU generation.<\/p>\n
First merge lines MUST be SKU and match lines like this:<\/p>\n
Billede-VSN7W2.png<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Variants, variations and main products can be difficult to keep track of – especially when they are in a flat file such as csv. Therefore, when importing variations into OpenDIMS, it must be done in a certain way. The start of the integration setup MUST look like this! The first merge MUST be SKU merge […]<\/p>\n","protected":false},"author":0,"featured_media":502,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[54],"class_list":["post-501","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-products","tag-variants"],"yoast_head":"\n