# Categories

A **category** is a classification you give a property — *Boutique hotel*, *All-inclusive resort*, *Family-friendly*, *Ski resort*, *Business hotel*. Categories drive how a property surfaces: in search filters, on partner channels, to specific audiences. Set them well and the right travellers find the right properties; set them poorly and good inventory disappears in noise.

## What categories cover

Categories are a typed taxonomy you maintain for your organization. Common axes:

| Axis                 | Examples                                                                     |
| -------------------- | ---------------------------------------------------------------------------- |
| **Property type**    | Boutique hotel, resort, vacation rental, villa, apartment, hostel, eco-lodge |
| **Audience**         | Family-friendly, adults-only, business, romantic, group                      |
| **Theme**            | All-inclusive, ski, beach, city break, wellness, golf                        |
| **Location flavour** | Beachfront, downtown, countryside, airport-adjacent                          |
| **Price tier**       | Luxury, premium, mid-range, budget                                           |

A property typically sits in several categories at once — *Boutique hotel + Adults-only + City break + Premium* tells a clearer story than any single axis would.

## Multilingual labels

Categories carry their own multilingual labels — *Boutique hotel* in English, *Boutique otel* in Turkish, and so on. When you publish to a partner channel that expects categories in a specific language, the platform sends your canonical label in the language the channel asks for. Your operator-side category list can be in any locale, and the traveller-facing screen picks up the matching label automatically.

## Setting categories on a property

For each property, you choose its category set from your canonical taxonomy. A few practical rules:

* **Don't over-tag.** 3 to 5 categories is usually enough. A property in 15 categories surfaces in too many irrelevant searches and dilutes its own positioning.
* **Don't under-tag.** A property with only *Hotel* on it is invisible to anyone searching for something more specific. *Boutique hotel + Adults-only + City break + Premium* tells a much clearer story.
* **Use the same category consistently across similar properties.** If two beachfront resorts in the same city have different category sets, your reporting falls apart.
* **Revisit when the property changes.** Adding all-inclusive packages? The category set should reflect that — and Adragent can sweep the gap for you.

Adragent can sweep through your organization for inconsistencies — *"Find every property in Antalya with all-inclusive rate plans but without the All-inclusive category."*

## Mapping partner categories to yours

Every source has its own category vocabulary. Mapping is what turns a partner's *Independent boutique* into your *Boutique hotel*, or a feed's *Family suite* into your *Family-friendly* tag. The curation surface flags partner categories that do not have a match yet; you decide whether to add a new category, map to an existing one, or ignore.

See [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md) — the same model applies to categories as to amenities.

## Per-channel exposure

A category does not have to surface on every outbound channel:

* An *Adults-only* property might surface on direct channels but be hidden from a family-focused B2B partner.
* A *Premium* tier classification might be reserved for retail and hidden from wholesale.
* A category that exists for internal reporting (e.g. *Pilot organization property*) never has to leave your organization.

Per-channel exposure is the same overlay used for rate plans and content — see [Stop-sale & restrictions](/console/pricing-and-availability/stop-sale-restrictions.md).

## Adragent and categories

Common phrases that map to Adragent category operations:

* *"Tag every property with a sea-front room as Beachfront."*
* *"Find canonical categories that are tagged on fewer than 5 properties — they may be misnamed."*
* *"Suggest category changes for the new properties from this source based on their descriptions."*
* *"Show me every property where the operator-side category set disagrees with what the partner sent."*

Read operations return immediately; writes preview before applying.

## Where to next

* **The bookable units carrying these categories** → [Rooms & attributes](/console/catalog/rooms-and-attributes.md)
* **Reconciling partner category vocabularies** → [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md)
* **The location dimension that pairs with categories** → [Location & geography](/console/catalog/location-geography.md)
* **Per-channel exposure for categories and other facets** → [Stop-sale & restrictions](/console/pricing-and-availability/stop-sale-restrictions.md)


---

# Agent Instructions: 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://adrasis.gitbook.io/console/catalog/categories.md?ask=<question>
```

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.