> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/use-case-guides/other-mixed-catalog/key-attributes.md).

# Key Attributes

Every product has one or two things that make it the right choice. Key Attributes surfaces those things — not in a paragraph of description copy, but as structured, filterable, badge-ready signals at the point of decision.

&#x20;&#x20;

OVERVIEW &#x20;

The Key Attributes field captures the two to five most purchase-decision-relevant characteristics of a product that are not already covered by other structured metafields. It is a flexible, cross-category field designed to highlight what makes a specific product stand out within its category — features, technologies, design decisions, or performance claims that directly drive conversion.

Key Attributes is not a description field. It is not a place for marketing language. It is a structured list of factual, verifiable product characteristics that answer the question: why should I choose this one over the alternatives? Each value should be a concrete, scannable claim — something a customer can read in under three seconds and immediately understand.

&#x20; BUSINESS VALUE &#x20;

Why this field matters

* Key attributes answer the 'why this one?' question at the moment of decision — they are the structured equivalent of a salesperson's three-sentence pitch
* Structured key attributes enable comparison-based filtering: 'show me all tents with a vestibule and a footprint' is only possible if these attributes are structured data
* AI recommendation systems use key attributes to match products to stated customer requirements — 'I need something lightweight and packable'
* Key attributes power badge strips on product cards in collection views — converting browsers to clicks before they reach the product page
* Editorial and content teams use key attributes to write product reviews, buying guides, and comparison tables without requiring full product expertise
* Trade and B2B buyers use attribute data to specify products against technical requirements — procurement without a sales conversation

&#x20; ACF SETUP &#x20;

How to configure this field in Accentuate Custom Fields

| Where       | ACF dashboard → Templates tab → Product scope → Add new field    |
| ----------- | ---------------------------------------------------------------- |
| Label       | Key Attributes                                                   |
| Name / Key  | key\_attributes                                                  |
| Namespace   | accentuate (default)                                             |
| Field type  | Shopify >> Single-line text (List)                               |
| Multi-value | Yes — 2 to 5 key attributes per product is the recommended range |

| Note: Key Attributes is a complement to, not a replacement for, specific structured fields. A product with 'Waterproof' as a key attribute should also have 'Waterproof' in its Weather Suitability field. Key Attributes surfaces the most important signals from across all fields in one scannable list — it is the headline summary of a product's structured data. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

<br>

STEP-BY-STEP IN ACF &#x20;

* Open ACF, go to Templates tab and select the Product scope
* Click 'Add new field'
* Label: 'Key Attributes' — Key auto-fills as 'key\_attributes'
* Namespace: leave as 'accentuate'
* Field type: Shopify >> Single-line text (List)
* Enable 'Allow multiple selections' — 2 to 5 values per product is the recommended range
* Click Done, then Save
* For each product, identify the two to five attributes that most directly drive purchase decisions for the target customer — these are not the only good things about the product, they are the deciding ones

| Discipline required: Key Attributes loses its value if every product has ten values. The power of this field comes from editorial restraint — 2 to 5 well-chosen attributes that signal the product's core proposition. More than five values is a sign that the field is being used as a description, not as a highlight list. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20;&#x20;

<br>

REFERENCE VALUES &#x20;

Example values — adapt to your category; these span Home & Living, Outdoor, and Children's products

| Value                   | When to use                                                                                                                |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Ultralight              | Product is significantly lighter than category average — a primary purchase driver for weight-conscious buyers             |
| Packable / Compressible | Product compresses to a significantly smaller size than its deployed volume — key for travel and adventure products        |
| Waterproof              | Product has a verified waterproof construction — surfaces this as a headline attribute for weather-dependent categories    |
| Handmade                | Product is made by hand — relevant for premium, artisan, and craft positioning                                             |
| Sustainably sourced     | Materials or production process meet a verified sustainability standard — relevant for eco-conscious segments              |
| Quick-dry               | Fabric or material dries significantly faster than standard — active wear, travel, outdoor textiles                        |
| Odour-resistant         | Fabric or material treated or engineered to resist bacterial odour build-up — base layers, activewear                      |
| Easy clean              | Product surface resists staining and can be wiped down or machine-washed — family, outdoor, and high-use products          |
| Adjustable fit          | Product features a fit adjustment system — harnesses, helmets, backpacks, children's items that grow with the user         |
| Foldable / Space-saving | Product folds or stacks to minimise storage footprint — furniture, outdoor gear, travel accessories                        |
| Award-winning design    | Product has received a recognised design or innovation award — Outdoor Industry Award, Red Dot, Which? Best Buy            |
| Made in \[Country]      | Country of manufacture is a meaningful purchase signal for this product — premium, provenance, or ethical sourcing context |

&#x20;&#x20;

<br>

BEST PRACTICES &#x20;

* Choose key attributes from the customer's perspective, not the product manager's — what does the buyer need to know to choose this over a competitor?
* Keep values short and scannable — 'Ultralight' not 'Designed with an ultralight construction philosophy'
* Every key attribute should be verifiable — 'Handmade' requires a production process to substantiate it; 'Award-winning design' requires a specific award
* Review key attributes when a competitor launches a similar product — the attributes that differentiate may change as the competitive landscape shifts
* Align key attributes with the primary copy and hero images — if the product page leads with 'ultralight', that should be a key attribute

<br>

&#x20; COMMON MISTAKES &#x20;

* Using marketing language as attribute values: 'Premium quality', 'Best in class', 'Superior performance' — these are claims, not attributes
* Duplicating information already in other structured fields without adding value — if 'Waterproof' is in Weather Suitability and visible there, adding it as a key attribute is only useful if it is the product's single most important selling point
* Assigning more than five key attributes — at six or more, the field becomes a description and loses its signalling power
* Not updating key attributes when a product's competitive positioning changes
* Using identical key attributes on every product in a range — if all products have the same attributes, the field cannot differentiate within the range

&#x20; IN CONTEXT &#x20;

| Ultralight Down Sleeping Bag — 850 Fill | <p><br></p>                                                         |
| --------------------------------------- | ------------------------------------------------------------------- |
| Key attributes                          | Ultralight, Packable / Compressible, Sustainably sourced, Quick-dry |
| Activity                                | Hiking, Mountaineering, Camping                                     |
| Weight                                  | Packed weight: 680 g, Minimum weight: 610 g                         |
| Weather suitability                     | Cold conditions, Three-season                                       |

&#x20;

&#x20;DEVELOPER IMPLEMENTATION &#x20;

| Liquid note: Shopify >> List — use .value for the array. Render key attributes as a badge strip on both product cards (collection view) and the product page — they are the highest-density conversion signal in the product data set. |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

<br>

Liquid — Storefront Rendering

\| <p>{% comment %}</p><p>Key Attributes — Shopify >> Single-line text (List)</p><p>Namespace: accentuate | Key: key\_attributes</p><p>Render as badge strip on product cards and product page</p><p>{% endcomment %}</p><p>{% assign attrs = product.metafields.accentuate.key\_attributes.value %}</p><p>{% if attrs != blank %}</p><p>  \<div class="key-attributes"></p><p>    {% for attr in attrs %}</p><p>      \<span class="attribute-badge">{{ attr }}\</span></p><p>    {% endfor %}</p><p>  \</div></p><p>{% endif %}</p> |
\| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

<br>

| Pro tip: Surface key attributes on product cards in collection views — not just on the product page. A badge strip of 'Ultralight · Packable · Waterproof' on a collection card converts browsers to product page visits before they have read a single word of product copy. |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

&#x20;&#x20;

SEE ALSO &#x20;

* Tags (controlled) — key attributes can be mirrored as controlled tags for Shopify-native filtering
* Compatibility / context — for products where system compatibility is a key attribute, that detail belongs in the Compatibility field
* All category-specific fields — Key Attributes surfaces the most important values from across all structured fields

| Full ACF documentation: help.accentuate.io \| Metafield Definitions → Fields → Field data type → Shopify field types |
| -------------------------------------------------------------------------------------------------------------------- |

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.accentuate.io/use-case-guides/other-mixed-catalog/key-attributes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
