Including Versions / Variants in the Products File

If you would like to be able to group products into a single product when they have versions/variants (e.g. the same product but with different sizes), you can update the products file to include versions information as follows:

• Create a Master Product line in the Products File - If, for example, there is a product with 5 different sizes in it, you would create a 6^th line in the products file for the master/parent product. This product can't be purchased as it is a virtual product that is used on the product page for allowing the website user to select which version to purchase.
• Add ParentProductCode field in the file – You would then add an extra column to the product file called “ParentProductCode”. For the example below, the 5 versions would have the master product code in this field – and the master product would  have a blank in this field.
• Add LookUp1Code to the file – You would then add an extra column to the product file called “LookUp1Code” which would be the unique code for the version.  This is the EXTERNAL CODE recorded against the version under the VERSIONS TABLE on the website. 
  • These Lookups need to be added to the appropriate Versions Table on the website in advance of the upload of the products.
  • The title displayed on the website can be different to the Lookup Code used in file, eg you might use external code "S" in the file and display "Small" in the version title of a lookup on the product page or use "10" as the external code in the file and display "Size 10" on the product page.
• Add Version Title to the TITLE field  in the file – You would add extra words to the product title for each version – e.g. “ – Size Small” or “ – S”.  The version title is displayed in the basket, checkout, order confirmation email and order processing so it is important that it is clear to the customer and staff processing the order.

Example Products CSV File – The following is how this product with 5 versions would appear in the products csv file as 6 lines. You may also include other fields in the file eg PriceEURO.

Example Product CVS File with two sets of version buttons (eg Size and Leg Length)

• All Lookup Codes need to be unique across the website so if you had a waist 34 and a Leg Length 34.  The code "34" could not be used for both of these.  You might use "34W" and "34L" as the codes.
• LookUp1Code will appear above LookUp2Code on the product page
• The LookUp Codes in the spreadsheet are the "External Codes" that you set up for the version on the website.  The text displayed on the product page for this version can be different to the to the Lookup Code.

Should you use COLOUR as a variant / version?

Most fashion websites don’t use COLOUR as a version, as it can be better for selling online to have a separate master product for each colour of a product – and then just use SIZE as a version.  Products of different colour can be linked together by related products.

Fields to use for Versions / Variants

Remembering that the above example would appear as a single product on the website with the user being able to select from the 5 sizes before adding to the basket, some of the fields for products will appear blank for master products and some will appear blank for versions.  For example, you would not send a LONG DESCRIPTION for a version as it is only used for the master products – and you would not send a LOOKUP1 code for a master product as it is only used for the versions.