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 6th line in the products file for the master product. This product cant be purchased as it is a virtual product that is used for allowing the website user to select which version to purchase.
- Add ParentProductCode to the file – You would then add an extra column to the product file called “ParentProductCode”. For the example above, 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.
- Add Version Title to the TITLE – You would add extra words to the product title for each version – e.g. “ – Size Smal” or “ – S”.
- Example Products CSV File – The following is how this product with 5 versions would appear in the products csv file as 6 lines:
ProductCode |
ParentProductCode |
Title |
LookUp1Code |
P-A1234 |
|
Nike - Jumper |
|
A1234 |
P-A1234 |
Nike - Jumper – Size Extra Small |
XS |
A2345 |
P-A1234 |
Nike - Jumper – Size Small |
S |
A3456 |
P-A1234 |
Nike - Jumper – Size Medium |
M |
A4567 |
P-A1234 |
Nike - Jumper – Size Large |
L |
A5678 |
P-A1234 |
Nike - Jumper – Size Extra Large |
XL |
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.
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.
Field |
Used for Master Products |
Used for Versions |
ProductCode |
Y |
Y |
ParentProductCode |
|
Y |
Title |
Y |
Y |
PriceEURO |
|
Y |
PromotionPriceEURO |
|
Y |
PriceSTG |
|
Y |
PromotionPriceSTG |
|
Y |
ShortDescription |
Y |
|
LongDescription |
Y |
|
|
|
|
Rating |
Y |
|
|
|
|
Lookup1Code |
|
Y |
Lookup2Code Lookup3Code, etc |
|
Y |
|
|
|
Weight |
|
Y |
|
|
|
Is New Until Date |
Y |
|
Is New From Date |
Y |
|
|
|
|
Clearance Further Reduced Online Exclusive Best Seller |
Y |
|
|
|
|
DisablePurchase |
Y |
|
IsDiscontinued
|
Y |
|
|
|
|
StockControlLowStockQuantity StockControlOutOfStockQuantity
|
|
Y |
StockControlLeadTimeInStock StockControlLeadTimeOutOfStock |
|
Y |
StockControlNextAvailableDate |
|
Y |
DiscountsDisallowed |
Y |
|
SupplierCode |
Y |
Y |
Comments
0 comments
Please sign in to leave a comment.