I think being able to add attributes at a variation level could be quite useful (as mentioned here - https://github.com/woothemes/woocommerce/issues/7944)
The guy doesn't seem to have posted the idea here (as suggested by you guys) so I thought I would add it.
This request is too broad and I think there are some misinterpretations to what this is or what this means.
Attributes are mapped TO variations. So variations do have attributes, they are just single attributes.
A few of the commenters here and on GitHub have mentioned EAN/GTN/MTN numbers and how attributes would solve this. These however are unique fields and whilst I can see some people could use attributes, they are unique data and could be better implemented with some kind of custom field, or dedicated EAN/MPIN fields for both products and variations.
EAN/MPN is a potential extension idea and would be better separate from this. With that in mind, rather than requesting attributes at variation level, maybe a better suggestion would be new fields for those (e.g. http://ideas.woocommerce.com/forums/133476-woocommerce/suggestions/16821466-field-for-product-serial-number and http://ideas.woocommerce.com/forums/133476-woocommerce/suggestions/19876414-set-gtin-as-a-field-like-next-to-sku)
http://ideas.woocommerce.com/forums/133476-woocommerce/suggestions/19876414-set-gtin-as-a-field-like-next-to-sku specifically already has a number of votes so backing things like that are more likely to be adopted than something abstract like this.
The ability to add attribute information about a product that displays in the further information section when a product configuration is chosen makes perfect sense to me. Why can't this be done?
Any News here ?
Hey, this feature is really important like rocketeer76 already said. Especially for marketing. For Example, u cant use Google Shopping if there is no unique EAN/GTIN for the variation. So i think individual attributes for variations are a must have.
Joseph L. Riviello commented
We've developed a plugin we are calling "WooCommerce Variation Addons". I believe it is what you are all interested in. With our plugin, you will be able to add conditional addons (with pricing adjustments) to each variation. Just about every type of field is supported. And we've even built in a swatch component to it.
Just because they dismissed it doesn't mean that its off the table. If we rally the troops to support this feature, I'm sure they will consider it. There are multiple posts here over the past 4 years asking for variation level attributes. Ill see if I can rally some support for this feature, I hope you all do the same :)
brent c. airey commented
I'm banging my head against the wall for issues caused by this not existing.
Specifically I need variations to have their own Category as an option. We sell product in various sizes, but if I want to create a Composite Product (or a coupon, or anything) with just the 3kg size I can't.
I guess having the framework accept Attributes as target terms outside the Variation itself would help a great deal here also.
But having the ability to treat variations as 'child' items would make marketing and broadening the offering on the site would be of enormous help.
Hey guys! I'm the guy who posted this! I'm not sure why mikejolley dismissed it :) It's a feature all my previous e-commerce systems have. I guess it's a bit complex to implement when it wasn't considered from the beginning. Hopefully it will be implemented in the future. I don't want another custom plugin for this.
Ryan Klatt commented
I could REALLY use this as well. That way variable products behave more like child products.
Anton Grant commented
Since this idea has been dismissed by Mike, I would assume there's a workaround that allows additional data applied to an attribute that doesn't involve the attribute being either an array for all attributes or having to use the attribute to set up a variable product?
Is it possible to set up custom taxonomy to handle variation level attributes perhaps? I've not found the answer yet but am willing to pay for development if necessary.