eCommerce : fields vs attributes? From the docs :


  Products variations can have attributes and other kinds of fields. Going back to our t-shirt analogy from above, if our t-shirts come in sizes and colors, perhaps the product variation should have an image field so you can upload a picture of a small red shirt. These kinds of non-attribute fields are loaded dynamically when variations are chosen.


What is the difference of purpose and meaning of "non-attribute fields" AND attributes ?
How are they different and similar ?
The way I think about it is in terms of sku numbers (or manufacturing part number/catalog number.) If a single product is available in multiple sizes (1 mg, 50 mg, 1 gm), each one will have its own unique sku. Those sizes are the variation attributes. But then I may also want to add on a non-attribute field like an image or a packaging/shipping surcharge (for a larger size). That data is specific to the product variation but isn't related to the sku.

Using the t-shirt analogy, if both size and color are attributes, then you might have the following unique variations:


TS_SM_01: small, blue t-shirt
TS_MD_01: medium, blue t-shirt
TS_LG_01: large, blue t-shirt
TS_SM_02: small, red t-shirt
TS_LG_02: large, red t-shirt 
TS_SM_03: small, green t-shirt 
TS_MD_03: medium, green t-shirt 
TS_LG_03: large, green t-shirt


If I add on a field for an image or a field for some sort of customization, those new "non-attribute" fields do not cause me to create a whole new set of product variation sku numbers.