# Content & catalog sources

Beyond live rates and inventory from channel managers and bedbank reselling, Adrasis receives **structured catalog feeds** — the rich, multilingual content that powers a property page and a search filter. These sources are content-heavy and rate-light: a curated dataset to seed and enrich your catalog, not a real-time sales channel.

A concrete picture: you onboard a new chain of 60 hotels. Instead of writing 60 property descriptions in 6 languages by hand (360 paragraphs), you import them from a content catalog source, then layer your own brand voice and translation overrides where you want to differentiate.

## What this kind of source contributes

A catalog source is fundamentally a **content reference** — the kind of data that does not change every minute but matters every time someone reads the property page or filters a search.

| What you get from a catalog source                                                                |
| ------------------------------------------------------------------------------------------------- |
| Hotel records — identifiers, names, addresses, descriptions, contact info                         |
| Multilingual property descriptions across many languages (EN, TR, AR, DE, FR, RU and beyond)      |
| Property images with captions, ordering, and per-language coverage                                |
| Hotel-level amenity codes and labels                                                              |
| Property classification taxonomies — luxury, family-friendly, all-inclusive, ski-resort and so on |
| Hotel-wide attributes — spa, pool, parking, accessibility                                         |
| What the hotel accepts at check-in (onsite payment types)                                         |
| Pet policy codes — allowed, weight limits, fees                                                   |
| Hotel-chain affiliations                                                                          |

Adrasis can connect to multiple sources of this kind in parallel. Each source brings its own slice; your product record absorbs them all.

## Where it fits

Catalog sources sit beside channel managers and bedbanks, but the role is different:

* **No live rates.** Catalog sources update on a slower cadence — content does not need to refresh every minute. Rates and inventory still flow through your channel-manager partners or your direct contracts.
* **Content-heavy.** The value is in language coverage, image quality, attribute precision — the things that make a property listing feel complete to a traveller.
* **Curation lives in Adrasis.** A catalog source is a starting point. You take what is there, layer your own translations, photographs, and overrides on top, and end up with a property page that reflects your brand and your contractual reality.

## What you do with a catalog source

A typical workflow:

1. **Discover properties** in the catalog through Adrasis's search.
2. **Onboard a property** into your catalog. Adrasis takes the source record as a starting point and creates the property and rooms.
3. **Map the content** — the source's amenity codes, category codes, and attribute codes resolve to your catalog through the regular mapping curation page (see [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md)).
4. **Layer your own content on top.** Translations, photographs, descriptions, attribute overrides — so the property page reflects you, not just the source baseline.
5. **Configure rates and contracts** through your own arrangement with the hotel; channel-manager partners or direct contracts handle live rates and inventory.

## Multilingual content as a first-class concern

Catalog sources typically ship content across many languages. Adrasis preserves that as multilingual content on the property and amenity records — a property's English description and Turkish description coexist as locale-tagged content, not as separate property records.

Traveller-facing channels can request the locale they want; the same property record serves any of them. Adding a new language to a property is a content task, not a structural one.

## How content from many sources stays consistent

When the same property comes from more than one source — a chain hotel that appears in two different catalog feeds and also through a channel manager — Adrasis mapping reconciles them into one property record. You do not end up with three almost-identical properties; you end up with one, with provenance on every field showing where the value came from.

For an operator, this means richer content without the cleanup work that usually comes with multi-source ingestion.

## Where to next

* **Channel manager partners (different shape — live rates and inventory)** → [Channel manager partners](/console/distribution/inbound/channel-managers.md)
* **The mapping system for amenities, categories, and attributes** → [Attribute mapping](/console/mapping-and-curation/attribute-mapping.md)
* **The place taxonomy properties resolve into** → [Location & geography](/console/catalog/location-geography.md)
* **The shared inbound model** → [Inbound overview](/console/distribution/inbound.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/distribution/inbound/content-catalogs.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.