> For the complete documentation index, see [llms.txt](https://fredhopper.gitbook.io/product-discovery/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fredhopper.gitbook.io/product-discovery/sending-and-managing-product-data/what-is-the-items-api/working-with-items/category-tree/onboarding-on-xo.md).

# Category Tress in XO

### XO Enrichment

When a Category Tree is configured on a CIDP environment with an XO destination, we automatically create up to 5 attributes to reflect the category levels.

As an example, let’s say an item X has 2 category paths:

* Men > Clothing > Jacket
* Sales > Men > Clothing > Jacket

It would result in the following attributes automatically added to your items in XO:

`"enrichments_category_paths_level1": ["Men", "Sales"], "enrichments_category_paths_level2": ["Clothing", "Men"], "enrichments_category_paths_level3": ["Jacket", "Clothing"], "enrichments_category_paths_level4": ["Jacket"]`

### Important to know <a href="#important-to-know" id="important-to-know"></a>

* The category name values that are extracted from the Category Tree configuration are the values corresponding to the [default locale](/product-discovery/sending-and-managing-product-data/what-is-the-items-api/working-with-items/item-schema/defaultlocale-api.md) that is configured for the environment.
* If the customer has not set up a default locale (mandatory when using XO),
  * By default we try to retrieve the values matching the locale en\_GB
  * and if there is no matching value we retrieve the category id instead.
* It means every environment where a Category Tree is configured should have the additional item attributes populated on the items in XO.