RESOLVED: Understanding Variants 3 - Alias Field

  • Posts: 76
  • Thank you received: 1
11 years 11 months ago #50959

Using Alias Field to reduce non-existant variants:

My first trial product ended up having over 2000 variants, most of which were variants that did not exist [no product matching that variant]. So I am working on understanding what I need to change in order to reduce this number of non-existing variants.

On Characteristics setup page, each characteristic has name and alias.... can I have more than one characteristic called 'Color' and then use the alias field to distinguish between products: eg. ballerina, sandal, dress, etc. to avoid excessive uneeded variants??

Example:
Name: Color, Alias: Ballerina Colors
Name: Color, Alias: Sandal Colors
Name: Color, Alias: Dress Colors

In this way each product page will have 'Color' as a characteristic while on admin side, I will be able to keep them separate. And doing it this way would avoid excessive variants that would exist if colors for all three products were entered into the same characteristic.

Is my thinking correct here? Do you recommend using alias fields in this way?

Thanks

Last edit: 11 years 11 months ago by scottshort. Reason: RESOLVED

Please Log in or Create an account to join the conversation.

  • Posts: 81604
  • Thank you received: 13082
  • MODERATOR
11 years 11 months ago #51094

Hi,

YES, the goal of the alias field is exactly for that: be able to distinguish it in the back end while keeping the same name on the front end.

The following user(s) said Thank You: scottshort

Please Log in or Create an account to join the conversation.

Time to create page: 0.056 seconds
Powered by Kunena Forum