> For the complete documentation index, see [llms.txt](https://dev.ucommerce.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ucommerce.net/readme/search-and-indexing/indexing/facets.md).

# Facets

## Overview

When using Ucommerce, you can create a custom index definition that specifies which built-in or user-defined properties on your products should be generated as facets. Once you have completed this step, any queries against the index will return facets and their respective values, as shown in the image below.

<figure><img src="/files/5GSXp40pjQTJyX1tp2ca" alt=""><figcaption><p>Faceted search example</p></figcaption></figure>

## Creating a facet

When you want to enable faceted search for a field, your index definition needs to define the field to be part of the index as well as tell the system that this field should be faceted.

```csharp
this.Field(p => p["Coupons"], typeof(UserDefinedEnum))
    .Facet();
```

{% hint style="info" %}
The search API will automatically retrieve all possible values for facets.
{% endhint %}

### Price facets

Depending on the price indexing mode, prices can be different than most other fields. See [Indexing Prices](/readme/search-and-indexing/indexing/indexing-prices.md) for more details.


---

# 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://dev.ucommerce.net/readme/search-and-indexing/indexing/facets.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.