A Product Group facilitates the organisation and structure of similar product versions together.
In some cases, you will have multiple versions of the same product in your product catalogue, e.g. a dress that is available in 5 different sizes. Even though the dress comes in 5 different sizes, it is essentially the same product. Each version of the dress will have its own unique product code and entry in the product database.
So rather than leaving the product versions standalone which would mean having to upload an individual product image and product descriptions for each one, you can group the product versions together under one product name (i.e. a parent product group).
From your customers perspective, they will look at the product on the website, see that it comes in different sizes. They will then choose the version that they would like to purchase:
If you wish to leave your products as standalone products then you will not be required to create a product group.
When should you use versions?
Using versions is not necessarily a good way to merchandise your products and should be avoided if possible. Fashion websites should use versions for sizes as they will have products with many different sizes and they will pollute the website if they gave each size their own product – but if the website only has a few products that could be grouped into versions, then it would probably be easier just to set each of these products as their own product and not use versions.
- Version cannot be used as add-on products to upsell a product.
- Promotions and promotion codes are assigned at a product level not a version level.
Best Practice for Colours
When you have products with different colours, you can either group them into one product – or have each colour as it’s own product. The best practice is to have each colour as a separate product and not use versions for colours.