--- title: Determine which fields are available for facets slug: ncc97453 canonical_url: https://docs.coveo.com/en/ncc97453/ collection: coveo-for-commerce source_format: adoc --- # Determine which fields are available for facets When your [catalog entity](https://docs.coveo.com/en/3143/) structure only contains items of the [product](https://docs.coveo.com/en/n8of5561#product) [catalog object](https://docs.coveo.com/en/ncig0154/), determining which fields are available for facets is straightforward. > **Note** > > To be used in a facet, a field must have [this option enabled](https://docs.coveo.com/en/1833#facet-and-multi-value-facet). However, if the structure of your catalog entity is more complex and contains products, variants, and/or [availability channels](https://docs.coveo.com/en/mc7e9096/), items of the different catalog objects can share the same fields. For example, the `collection` field can be defined for both items of the product and variant catalog objects. In such cases, don't create facets on fields that are defined for more than one catalog object. Refer to the [Facet Association tab](https://docs.coveo.com/en/3139#facet-association-tab) to view which facet-enabled fields are associated with the existing catalog objects in your catalog entity. **Example** The following capture shows the **Facet Association** tab for a catalog entity that contains items of the product and variant catalog objects: ![facet association tab for a catalog containing items of the product and variant catalog objects | Coveo](https://docs.coveo.com/en/assets/images/coveo-for-commerce/images/facet-association-tab.png) In this capture, you can see that: * The `cat_style` field is only defined for items of the product catalog object. * The `cat_thickness` field is only defined for items of the variant catalog object. * The `collection` field is defined for both items of the product and variant catalog objects. Therefore, you can create facets on the `cat_style` and `cat_thickness` fields. While you could also create facets on the `collection` field, we recommend that you don't do so because it's defined for more than one catalog object.