# Property

A **property** is the top-level catalog object — the hotel, vacation rental, villa, apartment, or any other accommodation you sell. Everything else (rooms, rate plans, mappings, channel bindings, bookings) hangs off it.

{% hint style="info" %}
**One property is one record, no matter how many sources fed it.** The same Istanbul hotel that arrives through a channel manager, a bedbank and a direct contract becomes one property with three sources of provenance — not three duplicate listings.
{% endhint %}

***

## What a property holds

| Element                | What it says                                                                                |
| ---------------------- | ------------------------------------------------------------------------------------------- |
| **Identity**           | Name, official identifiers, contact info.                                                   |
| **Address & location** | Country, region, city, district, neighborhood, coordinates.                                 |
| **Content**            | Multilingual descriptions, images, amenities, classifications.                              |
| **Lifecycle state**    | Draft, published, paused, archived.                                                         |
| **Rooms**              | The bookable units the property offers.                                                     |
| **Bindings**           | Which channels publish or ingest this property.                                             |
| **Mapping**            | How the property's rooms, rate plans and meal plans translate to each partner's vocabulary. |
| **Change history**     | Important changes to identity, content, lifecycle, and bindings.                            |

You see all of this from one place: the property page. Tabs split the work by concern (basic info, rooms, content, channels, mapping); the property as a whole stays one record.

***

## The lifecycle of a property

<figure><img src="/files/ibSNUEW5FfUmt1yy2gQ5" alt="Draft → In review → Published → Paused / Archived"><figcaption><p>The property moves through a small set of states. Each transition is recorded with the operator who made it.</p></figcaption></figure>

| State         | What it means                                                                                                           |
| ------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Draft**     | The property exists in your catalog but is not yet ready to publish. Content can be incomplete; channels are not bound. |
| **In review** | A reviewer is checking the content; the property is ready to publish once approved.                                     |
| **Published** | The property is live — bookable, distributed, indexed in search.                                                        |
| **Paused**    | Temporarily out of distribution; existing bookings stay valid; can be unpaused.                                         |
| **Archived**  | Permanently retired. Bookings and history are preserved; the property no longer surfaces in active operations.          |

You move properties through the lifecycle from the property page; each transition is recorded with the operator who made it.

***

## Adding a property

A typical onboarding pass:

1. **Create the property shell** — name, official identifiers, primary contact, address.
2. **Set the location** precisely — coordinates, place hierarchy, nearby landmarks. See [Location & geography](/console/catalog/location-geography.md).
3. **Add the rooms** — the room types, capacities, layouts you sell. See [Rooms & attributes](/console/catalog/rooms-and-attributes.md).
4. **Layer in content** — descriptions in the languages you operate in, images with captions, amenities, categories. See [Images & content](/console/catalog/images-and-content.md), [Categories](/console/catalog/categories.md).
5. **Map the meal plans** for the rate plans you offer. See [Meal plans](/console/catalog/meal-plans.md).
6. **Bind channels** — which outbound channels publish this property, which inbound channels feed it. See [Channels](/console/distribution/channels.md).
7. **Curate mapping** between your canonical entities and partner vocabularies. See [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md).
8. **Move to published** — the property goes live.

For a small property with 8 rooms across 2 room types, this is a couple of focused hours. For a 200-room resort with 6 room types and 4 meal-plan combinations, the work scales — but the steps stay the same, and Adragent can do most of the heavy lifting on confirmation.

***

## Updating a property

Once a property is published, updates flow through the same screens:

* **Content updates** — new images, refreshed descriptions, updated policies. The console preview shows the change before publishing; channel feeds update on the next refresh.
* **Room changes** — adding a new room type, retiring an old one, changing capacities. Lifecycle of rooms is its own concept; see [Rooms & attributes](/console/catalog/rooms-and-attributes.md).
* **Mapping adjustments** — when a partner changes their codes or you add a new partner, the mapping page shows what to update. See [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md).
* **Channel adjustments** — pausing a channel, opening a new one, rotating credentials. See [Channels](/console/distribution/channels.md).

Every update is recorded; you can trace any field on the property back to who set it and when.

***

## Multi-source properties

If the same property arrives in your catalog from more than one source — a channel manager, a content catalog, a direct contract — the canonical record reconciles them. Each value carries provenance (which source contributed it); your overrides win where you have set them. See [Canonical mapping](/console/mapping-and-curation/canonical-mapping.md) for the full model.

***

## Adragent and properties

Common phrases that map to Adragent property operations:

* *"Create a new property in Antalya called Hotel Sunrise with 30 rooms across three room types."*
* *"Find every property without a hero image and queue them for content review."*
* *"Pause the Marina property on all metasearch channels for the next two weeks."*
* *"Show me every property where the published descriptions are missing Turkish."*
* *"Apply our new cancellation policy template to every property in the Europe market."*

Read operations return immediately; writes preview before applying.

***

## Where to next

* **The bookable units the property offers** → [Rooms & attributes](/console/catalog/rooms-and-attributes.md)
* **Multilingual content beyond labels** → [Images & content](/console/catalog/images-and-content.md)
* **The place taxonomy the property sits in** → [Location & geography](/console/catalog/location-geography.md)
* **The channels it publishes to and ingests from** → [Channels](/console/distribution/channels.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/property.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.