Attribute Sets in Magento: What they are, why they matter, how to do them right

Attributes, attribute sets, attribute groups. How to structure your catalog so it scales to 10M SKUs.

Published 2026-09-24 • Category: Magento • Reading time: 8 min

What is an Attribute Set

An Attribute Set is a collection of attributes that defines what information is stored for a product of a given type. For example, a smartphone has display_size, ram, battery; a t-shirt has size, color, material; wine has vintage, grape, region.

Attribute vs Attribute Group vs Attribute Set

• Attribute — a single field: name, label, type (text, dropdown, multiselect, image, boolean, date, decimal).
• Attribute Group — an admin section that groups a handful of attributes together (e.g. “SEO” or “Shipping”).
• Attribute Set — the full bundle of attribute groups and attributes for a product of a given type.

When to create a new Attribute Set

Rule of thumb: if products have fundamentally different characteristics — new set. If the difference is just a few options — add an attribute to the existing one.

A fashion-store example

The store sells apparel and accessories. Create three sets:

1. Apparel: size, color, material, fit, season
2. Shoes: shoe_size, color, material, heel_height, closure_type
3. Accessories: color, material, weight, dimensions

All three share a common “SEO” group (meta_title, meta_description, url_key).

Working with Magmi

The Attribute Set Rewrite plugin picks up attribute_set_id automatically when the CSV has an attribute_set column:

sku,attribute_set,size,color,price
TSHIRT-01,Apparel,M,Red,29.99
SHOE-01,Shoes,42,Black,89.99

Migrating between Attribute Sets

If you decide a product should move to a different set, it’s not as simple as updating one column. Attributes that don’t exist in the new set are not deleted automatically. The right flow: export → clear values of orphaned attributes → import with the new attribute_set_id.

Conclusion

A sound attribute-set structure is the foundation of a catalog that scales. Spend one day planning before you create 100,000 products — and you’ll save weeks of refactoring at 1M.