Attributes and attribute values

Attributes define structured catalog dimensions such as color, size, or material. An attribute is reusable across products; its values establish the choices that variants can select.

The four-part model

  1. An attribute defines the name and value type.
  2. An attribute value defines an allowed value, such as Blue or Large.
  3. An attribute assignment attaches that definition and its available values to a product.
  4. A variant selection chooses values from the product’s assignments.

For a shirt sold in blue and green, create one Color attribute and both values, assign them to the shirt, then select blue on SKU SHIRT-BLUE and green on SKU SHIRT-GREEN. The product owns shared copy; each variant owns the sellable selection and SKU.

Choose the correct catalog mechanism

Use an attribute when the value is structured, reusable, and participates in variant choice or product discovery. Use a tag for a lightweight product label. Use a category or collection for navigation and merchandising membership. Use a metafield for typed project-specific data that is not a variant option.

Changing definitions

Treat an attribute definition as a contract. Before removing a value, inspect products and variants that use it. Reorder values when presentation order changes; do not delete and recreate values merely to change display order. Product and variant mutations validate selected values against their assignments, so integrations should create definitions and assignments before variants.