# Style Tags

OVERVIEW

What is this field?

The Style Tags field captures the aesthetic, mood, and design language of a product. It answers the question: what visual or cultural category does this product belong to?

Style tags operate at a higher level than product attributes like material or fit. They describe the overall feeling and look of a product.

This is one of the most powerful fields for product discovery and recommendation.

BUSINESS VALUE

Why this field matters

* Customers increasingly shop by aesthetic and style rather than by product category
* AI recommendation engines use style data to learn customer preferences
* Style tags enable powerful cross-category collections
* Search engines use style descriptors for natural language query matching
* Style data helps visual merchandising teams create cohesive editorial content
* Influencer and social commerce marketing relies on style-based product grouping

TECHNICAL SETUP

Recommended setup

Field type: List of single-line text entries (multi-select)

Namespace: custom.product

Key: style\_tags

Multi-value: Yes — allow multiple entries where applicable

STEP-BY-STEP WALKTHROUGH

How to create the Style Tags field in Accentuate

Follow these steps to create and configure this metafield in your Accentuate dashboard.

Step 1: Navigate to metafield definitions

Open your Accentuate dashboard and go to the metafield definitions section. Select the "Product" resource type to add a new product-level metafield.

| Accentuate dashboard — navigate to Product metafield definitions |
| ---------------------------------------------------------------- |

Step 2: Create a new metafield

Click the "Add definition" or "Create metafield" button. Enter the namespace "custom.product" and the key "style\_tags". Set the display name to "Style Tags".

| Click “Add field” to create the “Style Tags” metafield |
| ------------------------------------------------------ |

Step 3: Select the field type

Set the field type to "List of single-line text entries (multi-select)". Enable the "List" or multi-value option so merchants can enter multiple values.

| Select the data type for “Style Tags” |
| ------------------------------------- |

Step 4: Configure validation and description

Add a helpful description for merchants: "The aesthetic, mood, and design language of this product (e.g., Minimal, Streetwear, Boho, Classic)." This will appear as helper text when merchants edit the field on a product.

| Description and validation settings for “Style Tags” |
| ---------------------------------------------------- |

Step 5: Save and verify

Save the metafield definition. Then navigate to any product and confirm that the "Style Tags" field appears in the metafields section, ready to accept values.

| The “Style Tags” field visible on a product editing page, empty and ready |
| ------------------------------------------------------------------------- |

STRUCTURING GUIDANCE

How to structure the values

Use established style vocabulary that your customers recognize.

Assign 1–4 style tags per product. Too few misses discovery; too many dilutes accuracy.

Style tags should describe the aesthetic, not the product type.

Consider having two tiers: primary style (dominant) and secondary style (complementary notes).

Review and refresh style tags periodically as fashion trends evolve.

USAGE CONTEXT

When to use this field

* All apparel products benefit from at least one style tag
* Accessories where aesthetic is a primary differentiator
* Footwear that belongs to a specific style category
* Any product you want to appear in style-based collections
* Products marketed through lifestyle or aesthetic-driven content

REFERENCE VALUES

Example values

The following values are recommended starting points. Adapt them to your product catalog as needed.

| Value                        | When to use                                                      |
| ---------------------------- | ---------------------------------------------------------------- |
| Minimal                      | Clean lines, neutral palette, unfussy details; Scandi-influenced |
| Streetwear                   | Urban culture-influenced; graphic prints, oversized silhouettes  |
| Classic / Timeless           | Enduring silhouettes; wardrobe staples, investment pieces        |
| Luxury                       | Premium materials, refined construction, elevated finishing      |
| Vintage-inspired / Retro     | Draws from past decades; nostalgic details, heritage             |
| Sporty / Athleisure          | Athletic influence worn casually; performance fabrics            |
| Boho / Bohemian              | Free-spirited, relaxed; prints, textures, artisanal details      |
| Scandinavian / Nordic        | Functional minimalism; clean design, muted palette               |
| Contemporary                 | Current and modern; trend-aware without being trend-dependent    |
| Edgy                         | Bold, non-conformist; darker palette, hardware, asymmetric cuts  |
| Feminine                     | Soft shapes, flowing fabrics, delicate details; florals, pastels |
| Monochrome                   | Single-color or tonal outfitting; black, white, or tonal         |
| Preppy                       | Collegiate-inspired; clean-cut, structured, polished casual      |
| Workwear / Utilitarian       | Functional design roots; sturdy fabrics, practical details       |
| Romantic                     | Soft and dreamy; ruffles, sheers, florals, flowing silhouettes   |
| Gorpcore / Outdoor aesthetic | Outdoor gear worn as fashion; technical fabrics, earthy tones    |

| The “Style Tags” field populated with example values |
| ---------------------------------------------------- |

RECOMMENDATIONS

Best practices

* Build a style tag vocabulary of 15–25 terms that covers your catalog range
* Assign style tags that genuinely reflect the product, not aspirational marketing
* Use style tags to power discovery pages, personalization, and email campaigns
* Monitor which style tags drive the most engagement and optimize accordingly
* Combine style tags with occasion for targeted merchandising
* Train your merchandising team on the vocabulary for consistent tagging

AVOID THESE

Common mistakes

* Using too many style tags per product, making every product appear in every collection
* Confusing style with occasion: “Casual” is an occasion, not a style
* Creating brand-specific style terms that customers do not understand
* Not evolving style tags as trends change
* Applying the same style tag to every product, making it meaningless
* Using style tags that describe physical attributes rather than aesthetic

IN CONTEXT

Example: How it appears on a product

| <p>Men’s Waxed Canvas Chore Jacket</p><p>Style tags: Workwear / Utilitarian, Classic / Timeless, Edgy</p><p>Occasion: Casual, Outdoor</p><p>Material: Waxed cotton canvas, Flannel lining</p><p>Season: Autumn, Winter</p> |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |

| Style Tags data displayed on the storefront via Custom Liquid |
| ------------------------------------------------------------- |

<br>


---

# Agent Instructions: 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:

```
GET https://help.accentuate.io/use-case-guides/fashion-and-apparel/style-tags.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.