Create or update sizes, colours and other choices from a file without confusing the parent product and variant.
This guide covers product import and customer choices in Go, Plus and Pro. Choice import templates differ from Plus/Pro product templates. You need unique, stable article numbers and a checked import file. First export a safety reference and try a small intended selection. Import changes actual product data.
1. Distinguish new products from updates
A new parent product needs an article number and name in the shop's base language plus intended prices in the correct base currency and VAT basis. Each sellable variant requiring its own data needs a unique article number. The parent number identifies the product; the variant number identifies the choice or combination.
Keep the parent and its variants together in consecutive file rows. Repeat the parent number on variant rows. Put the name and parent details on the intended parent row, followed by choice values and correct variant numbers. The example below has three sizes and two colours: one number per combination rather than one number for every size.
To update existing variant data only, preserve both identifiers and map only the properties being changed. A new or changed identifier can create another product or variant. Do not treat ordinary import as a general renaming function for numbers used by other systems.
2. Create an import template for each choice
Open Catalogue → Import and Customer choice import templates in the import information. Choose Add new, enter Size for example and create a separate Colour template if needed.
Price effect: enable when choices should affect product prices.
Price effect before numeric quantity multiplication: use only when those measurement/quantity fields are involved. It determines whether the adjustment is included before multiplication. Check the calculation for your actual example; it does not itself create a complete square-metre setup.
Weight effect: enable when choices should affect product weight.
Own properties: needed for individual variant information such as article number, stock and image. A simple text choice without individual stock records is a different arrangement.
Save each template. Check whether existing products and choices already use another structure before creating nearly identically named templates.
3. Load the file and check columns
Select the file under Catalogue → Import. Choose Update information when intending to update existing records rather than Ignore.
Use automatic delimiter and encoding as a starting point but check the preview. Correct broken columns or characters before importing.
Choose Continue and select First row contains column headings if applicable.
Map the parent number, article number under Customer choices and each choice column to the correct import template. Then map only intended price, weight, stock, GTIN/EAN or other columns. Ignore the rest.
File headings do not automatically make mapping correct. Scroll sideways and review every column. An empty mapped cell can differ from an ignored column; do not include unintended empty price or identification fields in a large update.
You can save column order for repeated imports. Reuse it only when columns, languages and choice templates really match; it cannot safely identify a reordered supplier file.
4. Start a controlled import and read results
Check the selection once more and choose Start import. Wait for the final result and read imported, ignored and failed rows. A completed percentage does not mean every row is correct. Do not repeat a large file before knowing the outcome.
5. Enter the variant's total price and weight
When importing price or weight effects, enter the variant's full price and weight. The difference from the parent is calculated for the choice. If the parent weighs 100 grams and the variant weighs 110, enter 110 rather than the adjustment 10. A variant price of 125 against a base price of 100 represents an adjustment of 25 when the correct price effect is used.
Check the pricing basis, currency, any special-offer list and that combined choices do not add the same difference repeatedly. Verify the displayed final variant price and shipping weight after import. Product templates and variants with individual pricing can require separate assessment.
6. Update GTIN/EAN and stock on the correct row
Export existing products with customer choices with own properties as separate rows for a per-variant reference. Preserve parent and variant numbers and enter the actual GTIN/EAN for each sellable variant. Keep leading zeros as text. Do not invent a number or copy another size's GTIN onto the parent merely to fill a field.
Import stock only if Abicart owns that stock value or the change is coordinated with the warehouse system. Another integration can otherwise overwrite it. Check which products an external feed actually exports; a successful EAN import does not prove every variant reaches Google Shopping.
Check and troubleshoot
Open an affected product and compare combinations, numbers, GTIN, stock, prices and weights with the file. Also check the visible shop page. For duplicates or the wrong parent, stop further imports and review identifiers, consecutive rows, column mapping and the log. Do not delete old products or change integration identifiers by guesswork.
The preserved video is an older Swedish walkthrough. Images and video can have older labels; the text's checks apply even where examples differ.
Quick start
Export a reference and preserve stable parent and variant numbers.
Create the correct choice templates and a small file for a controlled test.
Review every column and import only intended properties.
Read results and check actual variant price, weight, GTIN and stock.
Subscription and variant model
Product import and customer choices are available in Go, Plus and Pro. Plus/Pro product templates are separate. Follow the actual model of the affected product rather than assuming identical mapping suits every older and newer variant arrangement.
