> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/commerce/catalog/reference/datasets-and-fields/enriched-fields.md).

# Enriched fields

Attributes added to the product catalog to make it richer than the original CMS/PIM feed. They are typically imported from external systems, connected services, or manually added by the merchant.

**Examples**:

* `eco_score` → imported from a sustainability API or custom attribute.
* `material` / `composition` → detailed product attributes from PIM.
* `lifecycle_stage` (e.g., “Spring collection”, “Back-to-School”) → defined by merchandising teams.
* `discount_flag` → imported from promotions system.
* `gender`, `age_group`, `style` → used for filtering or targeting.

Enriched fields allow finer control of merchandising rules. They let you tailor strategies to branding, campaign, or compliance needs (e.g., *boost eco-friendly products*, *exclude alcohol for under-18 users*).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/commerce/catalog/reference/datasets-and-fields/enriched-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.