Season

OVERVIEW

What is this field?

The Season field indicates when a product is most appropriate to wear based on weather conditions, temperature, or seasonal fashion relevance.

Seasonal data powers some of the most impactful merchandising decisions in fashion retail: what to feature on the homepage, what to promote in email campaigns, and what to prioritize in search results at any given time of year.

This field should capture genuine seasonal suitability, not just the season in which the product was released or the collection it belongs to.

BUSINESS VALUE

Why this field matters

• Seasonal merchandising relies on accurate season tags to surface the right products at the right time

• AI assistants use season data to give contextually relevant recommendations

• Email marketing and ad targeting improve significantly when products are correctly tagged by season

• Customers shopping for upcoming trips or weather changes rely on seasonal filtering

• Search ranking algorithms can prioritize seasonally relevant products

• Inventory planning and markdown decisions benefit from clear seasonal classification

TECHNICAL SETUP

Recommended setup

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

Namespace: custom.product

Key: season

Multi-value: Yes — allow multiple entries where applicable

STEP-BY-STEP WALKTHROUGH

How to create the Season 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 "season". Set the display name to "Season".

Click “Add field” to create the “Season” 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 “Season”

Step 4: Configure validation and description

Add a helpful description for merchants: "When this product is most appropriate to wear based on weather or seasonal relevance (e.g., Summer, Winter, All-season)." This will appear as helper text when merchants edit the field on a product.

Description and validation settings for “Season”

Step 5: Save and verify

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

The “Season” field visible on a product editing page, empty and ready

STRUCTURING GUIDANCE

How to structure the values

Use standard season names as primary values: Spring, Summer, Autumn, Winter.

Allow multiple season values. A lightweight cardigan might be “Spring” and “Autumn.”

Include an “All-season” value for truly year-round basics.

Consider adding functional descriptors alongside seasons: “Cold weather,” “Warm weather,” and “Transitional weather.”

Do not use collection or drop names as season values. “Resort 2025” is a collection name, not a season tag.

USAGE CONTEXT

When to use this field

• All apparel products should have at least one season value

• Outerwear and layering pieces where temperature relevance is critical

• Footwear that is weather-dependent (sandals, boots, rain shoes)

• Accessories with seasonal relevance (wool scarves, sun hats, gloves)

• Any product where climate or time of year affects its usefulness

REFERENCE VALUES

Example values

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

Value	When to use
Spring	Mild temperatures; lighter layers, transitional outfits
Summer	Warm to hot weather; breathable fabrics, minimal layering
Autumn	Cooling temperatures; layering pieces, richer colors, medium weight
Winter	Cold weather; insulated, heavy fabrics, maximum warmth
All-season	Year-round basics; t-shirts, classic denim, versatile essentials
Resort / Pre-spring	Vacation and warm-climate wear; lighter than full summer
Transitional weather	In-between seasons; pieces for fluctuating temperatures
Cold weather	Designed for low temperatures regardless of specific season
Warm weather	Designed for heat; tropical or extended summer climates
Layering season	Designed to work as part of a layered outfit; mid-layers and versatile knits
Holiday	End-of-year holiday season; festive dressing, party pieces, gift items
Back-to-school	Late summer/early autumn; practical, youthful, campus-ready

The “Season” field populated with example values

RECOMMENDATIONS

Best practices

• Tag products based on when they are actually worn, not when they were designed

• Use “All-season” sparingly — most products have at least some seasonal bias

• Combine season data with occasion data for powerful curated collections

• Update season tags when products carry over between seasons

• Consider your customer base’s geography when assigning seasons

• Use season tags to automate homepage and collection sorting throughout the year

AVOID THESE

Common mistakes

• Tagging everything as “All-season” to avoid decision-making

• Using collection or campaign names instead of actual season values

• Not updating season tags on carryover or restocked products

• Ignoring that some products span seasons (a denim jacket is spring and autumn)

• Conflating season with weather intensity

• Using season to describe color palette rather than wearability

IN CONTEXT

Example: How it appears on a product

Men’s Quilted Puffer Vest Season: Autumn, Winter, Layering season Material: Recycled nylon shell, synthetic down fill Fit: Regular fit Occasion: Outdoor, Casual, Everyday