> 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/sports-and-outdoor/terrain.md).
# Terrain
OVERVIEW
The Terrain field captures the surface type, environment, or geographic context a product is designed and optimised to perform on. For footwear, it describes the underfoot surface. For bikes, it describes the riding surface. For tents and sleeping bags, it describes the geographic environment. Terrain data connects a product's design specification to the real-world conditions it was built for.
Terrain is not the same as Activity. A trail runner and a hiker may use the same terrain. A road cyclist and a triathlete share road terrain but have different activity-specific requirements. Together, Activity and Terrain define the precise use-case context of an outdoor product — enabling search, filtering, and recommendation precision that neither field alone can provide.
BUSINESS VALUE
Why this field matters
* Terrain is a primary product specification for footwear, tyres, and surface-contact products — customers search 'trail running shoes', 'road bike tyres', 'sand tent pegs'
* Terrain mismatches cause product failures and safety incidents — a road shoe on technical mountain terrain lacks the grip and protection the user needs
* Structured terrain data enables activity + terrain filtered collections: 'Hiking shoes for rocky terrain', 'MTB kit for mud and roots'
* AI recommendation engines use terrain to surface the right product variant within a range (road vs trail vs mountain versions of the same product)
* Trade and professional buyers (outdoor centres, expedition outfitters) require terrain specification for equipment selection and client recommendations
* Terrain data supports safety liability documentation — confirming a product was specified for the terrain it was used on
ACF SETUP
How to configure this field in Accentuate Custom Fields
| Where | ACF dashboard → Templates tab → Product scope → Add new field |
| ----------- | ------------------------------------------------------------- |
| Label | Terrain |
| Name / Key | terrain |
| Namespace | accentuate (default) |
| Field type | Shopify >> Single-line text (List) |
| Multi-value | Yes — many products perform across multiple terrain types |
| Note: Be specific about terrain. 'Trail' and 'Technical off-trail' are meaningfully different — a shoe designed for groomed forest trails may be unsuitable for boulder fields and scree. Where the manufacturer makes this distinction, reflect it in the terrain data. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
STEP-BY-STEP IN ACF
* Open ACF, go to Templates tab and select the Product scope
* Click 'Add new field'
* Label: 'Terrain' — Key auto-fills as 'terrain'
* Namespace: leave as 'accentuate'
* Field type: Shopify >> Single-line text (List)
* Enable 'Allow multiple selections' — many outdoor products span multiple terrain types
* Click Done, then Save
* Assign terrain values based on manufacturer specifications and the product's design intent, not general outdoor applicability
REFERENCE VALUES
Example values — use terrain descriptions your customers recognise and search for
| Value | When to use |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------- |
| Road | Paved surfaces — road running, road cycling, urban commuting, pavement-specific footwear |
| Trail | Natural off-road paths and tracks — packed dirt, gravel, forest trails; the standard trail running and hiking terrain |
| Technical off-trail | Unmarked or rough terrain — scree, boulders, scrambling; requires high traction and ankle support |
| Mountain | High-altitude terrain combining multiple surface types — rocky, steep, exposed; alpine and mountaineering context |
| Mud / Wet terrain | Soft, wet, or boggy surfaces — cross-country running, fell running, winter trail conditions |
| Snow and ice | Winter surfaces requiring crampons, spikes, or specialised traction — ice axe and crampon-relevant products |
| Sand / Desert | Loose, dry surfaces — desert trekking, beach running, sandboarding; products requiring sand resistance |
| Rock / Climbing terrain | Vertical and near-vertical rock faces — climbing shoes, protection, ropes, technical alpine equipment |
| Water / Whitewater | River, lake, and open water environments — kayaking, paddleboarding, open water swimming |
| Groomed piste | Prepared ski runs — alpine skiing, snowboard carving on maintained resort terrain |
| Off-piste / Backcountry | Ungroomed snow terrain — ski touring, freeriding, backcountry skiing; avalanche risk awareness required |
| All terrain | Genuinely versatile terrain performance — assign only when manufacturer specifies cross-terrain capability |
BEST PRACTICES
* Assign terrain based on the product's underfoot or environmental design intent — not on the broadest possible terrain the product could be forced to work on
* Use 'All terrain' only when the product is genuinely engineered for cross-terrain versatility — not as a convenience default
* For footwear and tyres, terrain is one of the most important fields in the entire product data set — prioritise accuracy and completeness
* For tents and shelters, terrain describes the ground environment (mountain, desert, forest) and influences peg type, pole strength, and weather resistance requirements
* For bikes, distinguish 'Trail' (general MTB trail riding) from 'Technical off-trail' (enduro/downhill) and from 'Road' (tarmac)
COMMON MISTAKES
* Assigning 'Trail' to all outdoor products by default — many outdoor products are road-specific, piste-specific, or water-specific
* Not distinguishing 'Groomed piste' from 'Off-piste / Backcountry' for ski products — these require entirely different equipment specifications
* Using 'All terrain' as a catch-all for products that are actually road or trail specific
* Omitting terrain on footwear — for shoes and boots, terrain is as important as size
* Confusing terrain with environment: 'Mountain' is both a terrain type and an environment — be consistent about how you use it across your catalogue
IN CONTEXT
| Trail Running Shoe — Low Drop |
|
| ----------------------------- | --------------------------------------------- |
| Activity | Trail running, Hiking |
| Skill level | Intermediate, Advanced |
| Terrain | Trail, Technical off-trail, Mud / Wet terrain |
| Weather suitability | Rain / Wet conditions, Three-season |
DEVELOPER IMPLEMENTATION
| Liquid note: Shopify >> List — use .value for the array. Terrain tags link naturally to activity-terrain combination collections — one of the most powerful filtering mechanics in outdoor retail. |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Liquid — Storefront Rendering
\| {% comment %}
Terrain — Shopify >> Single-line text (List)
Namespace: accentuate | Key: terrain
Combine with activity for precise use-case collections
{% endcomment %}
{% assign terrains = product.metafields.accentuate.terrain.value %}
{% if terrains != blank %}
\
{% endif %}
|
\| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Pro tip: Create 'Mountain Running Gear' collections using activity = 'Trail running' AND terrain = 'Mountain' or 'Technical off-trail'. This precision filtering surfaces only the most relevant kit for technical alpine runners — a high-value, underserved customer segment. |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
SEE ALSO
* Activity — terrain and activity together define the full use-case context of an outdoor product
* Weather suitability — terrain environment and weather are closely related; mountain terrain implies mountain weather
* Material durability — terrain determines the abrasion, impact, and wear demands placed on a product
| Full ACF documentation: help.accentuate.io \| Metafield Definitions → Fields → Field data type → Shopify field types |
| -------------------------------------------------------------------------------------------------------------------- |
---
# 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:
```
GET https://help.accentuate.io/use-case-guides/sports-and-outdoor/terrain.md?ask=
```
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.