Developer forum

Forum » Ecommerce - Standard features » VariantGroups
Michael Nielsen
Reply

Hi all

 

I need some feedback and/or suggestions to a specific issue we have.

 

We have a client with 36.000+ products including variants (they sell clothes).

 

They have a lot of different types of products, so they also have a lot of different types of sizes that valuebased are the same, but still is different. For example: A size 32 in shoes and pants is not the same.

 

The products are imported from a POS system. All products has a stylenumber and size information, so products that share stylenumbers are created as variants to each other.

 

Since there is not any information on what type of product it is (shoe, shirt, pants and so on) and the fact that variant types of the same product type (e.g. shirts) also vary depending on which brand it is, makes it impossible to assign an existing variantgroup containing relevant sizes. So it is done by creating a unique variantgroup for every stylenumber and the variantsizes found is created in this unique group, which is then assigned.

 

However the result of that is that there now are 20.000+ variant groups, which is giving some performance issues. 

 

So I'm looking for suggestions to do it otherwise.

 

The only other option I see is to have just 1 variantgroup containing all size variants in the shop. I am only showing variantoptions in stock, and even though a size 32 for shoes and pants aren't the same, it is in reality just a number.

 

But will this also give performance issues, having only 1 variantgroup, but with maybe 500+ variants in it?

 

Any feedback is welcome...


Replies

 
Lars Sørensen
Reply

I've worked on a similar case where we used the approach with one variant group for all sizes and one for colors. Assuming that each variant has its own unique product number, the variant option is merely a piece of information needed for the customer to make her choise on which variant to choose. In that case you can use the variant 32 for both shoes and dresses alike, so it's not necessary to import different variant groups. Listing the options in VariantAvailableOptions will ensure that you only display the variant options that are available for the product currently.

I'm not noticing any performance problems on that solution.

 

You must be logged in to post in the forum