Product application - is it a product or product variation

Posted by jamesnov on Pro Webmasters See other posts from Pro Webmasters or by jamesnov
Published on 2011-06-24T20:10:45Z Indexed on 2011/06/25 0:32 UTC
Read the original article Hit count: 351

I'm dealing with a lot of vehicle specific products, and I've been trying to determine whether to convert the variants/fit option into individual products. I currently put the vehicle specific items under a product:

Product: Widget Hood Deflectors Option1: 07-11 Silverado/Sierra, SKU1 Option2: 09-11 Ram, SKU2 etc.

Take a hood/bug deflector for example. They all share the same description, and specifications for the most part. They look very similar, but the shape/appearance could vary significantly depending on the vehicle it is going on.

Another example could be a suspension lift kit. Each one is engineered for a specific vehicle application. What would be the product "Widget Super Duper 4 inch lift kit", or "Widget Jeep 07-11 Super Duper 4 inch lift kit"?

If I converted the variants to a product, then I have a lot more products (some so called products or product lines have hundreds of applications), when no vehicle is selected, but if I require a vehicle to be selected, then the product results would be basically the same, and specific for that vehicle. The description would also be longer:

Product: Widget Silverado/Sierra 07-11 Hood Deflector

With the fit as a variants/option, then I have fewer products, but I could have a huge list of options.

Product: Widget Hood Deflectors Options: Fit/Vehicle

Am I doing things right by having product applications as variants, or am I treating a product line as a product?

© Pro Webmasters or respective owner

Related posts about website-design

Related posts about websites