On Jul 5, 2014, at 8:59 AM, Dale Scott <[email protected]> wrote:

> Hi, I've been attaching documents (e.g. datasheets, specifications, work 
> instructions, gerber files, schematics...) to all the product I have 
> imported. In the process, I found an attachment to a product is not the same 
> as an attachment to a product variant.
> 
> Can someone explain the basic concept of products and product variants? 
> Should I be attaching documents to the product, or to product variants? What 
> is the difference? How to the user cases differ? Fwiw, I find the product 
> variant grid convenient because it includes the product code for each product 
> in the kanban view.

Explanation by a live example:

**Variation on one attribute**

Varying Attribute: Platform
http://www.amazon.com/Call-Duty-Advanced-Warfare-Xbox-One/dp/B00K308KF4
Here the product is: Call of Duty: Advanced Warfare
And the variants are: for PS3, Xbox, PC, PS4 etc

**Variation on Two attributes**

Varying attributes: Size, Color
http://www.amazon.com/Cole-Haan-Lunargrand-Saddle-Oxford/dp/B00HB1PDTE
Here the product is: Cole Haan Men's Lunargrand Saddle Oxford
And the variants are: 12 sizes X 2 Colors = 24 variants


As for your question about attachments:

It depends on the nature of the products and variants.
For example if you were to use iPhone as a product and the three sizes of 16GB, 
32Gb and 64 GB
as variants, then the specifications would be different for each variant while 
the user guide would
the same since all of the user instructions for the series is same. Similarly, 
the images may vary by
the iPhone color, but not by the size. So this depends if those documents you 
attach change by
variant or change by product (template).

Thanks & Regards


Sharoon Thomas
CEO & Chief Software Architect
Openlabs Technologies & Consulting (P) Limited

w: http://www.openlabs.co.in
m: +1 813.793.6736 (OPEN) Extn. 200
t: @sharoonthomas 

- We win when our customers win

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to