Skip to main content

Enriching a Style

A generated Style is sellable, but it becomes genuinely useful to a storefront and a merchandiser once it carries attributes, a completeness signal, images, certifications, and tags. This area covers all of that. This page starts with attributes, the richest piece.

Attributes: three scopes and how they resolve​

Every attribute is defined once (see Attribute Definitions) with a Scope of Style, Product, or SKU, and is then assigned a value at one, two, or all three of the following grids:

  • Attributes (Style), on the Style Card: one row per Style-scope attribute.
  • Attributes (Per Colour), on the Style Card: the same idea, scoped to Style plus Colour, for something like a colour-specific care note.
  • Cell Attributes (Overrides), on the Item Card or Item Variant Card: the one grid genuinely editable at the individual SKU level, for something like a fit note that only applies to the Medium and Large sizes.

All three grids show the human-readable Display Value rather than the raw stored code, for List and Multi-select attributes; typing a Display Value directly into the grid resolves it back to the underlying code automatically.

Entering a value at a deeper scope than the attribute's own Scope is only allowed if that attribute has Override Allowed turned on. If it does not, attempting a Colour- or SKU-level value is rejected outright: "Attribute X does not allow overrides; set its value at the style level instead."

Resolution order​

This is only relevant for an Override Allowed attribute:

  1. A non-blank SKU-level value, if one exists.
  2. Otherwise, a non-blank Colour-level value, if one exists.
  3. Otherwise, the Style-level value.
  4. If nothing at any scope has a value, the attribute's own configured Default Value.

An attribute that is not Override Allowed always shows its Style-level value, regardless of anything entered at a lower scope. If a value entered in Cell Attributes does not seem to be taking effect, check whether Override Allowed is actually turned on for that attribute.

Where the resolved view appears​

The Style Card has a read-only Attributes (Per SKU, read-only) roll-up across every SKU in the Style, showing each cell's own SKU Value alongside its Effective Value, so you can scan a whole size run at a glance. The standard Item Card and Item Variant Card each carry a Resolved Attributes view (also reachable as its own full page via the Resolved Attributes action) showing Attribute, Value, and Source (Per SKU, Per Colour, Style, or Default) for that one SKU. See Working from the item.

Translations are entered per attribute value through the Translations action (only available if the attribute is flagged Translatable), and are keyed to whichever Storefront Language you choose. See Web tags and translations.

Completeness score​

The Style Card shows a Completeness %, colour-coded red below 80%, amber 80 to 99%, and green at 100%, measuring how many required attributes (per the Style's Category Template) are actually filled in across all three scopes. It recalculates whenever the Style Card is opened, and again when the Style is released. Closing the Card while incomplete shows a non-blocking reminder; saving and releasing both work regardless of the score. Completeness is a merchandising quality signal, not a release gate.

More​