# Channel manager partners

Channel managers sit between hotels and the wider travel market. They already connect to many hotels and distribute the hotels' rates and inventory to the outside world. Adrasis receives supply through them as one of its primary paths.

## What they are

A channel manager sits between a hotel and the rest of the demand market. The hotel publishes its catalog, rates and inventory once to its channel manager, and the channel manager fans the data out to OTAs (Online Travel Agencies), metasearch engines and other consumers — Adrasis included.

For an agency working with a property that already has a channel manager in place, the value is concrete:

* **You don't talk to dozens of OTAs separately.** The hotel is already connected to its OTA mix through the channel manager — you ingest from the channel manager, the rest follows.
* **Rate and inventory updates are real-time.** When the hotel changes a rate or closes a date, that change reaches your product record through the same connection.
* **Bookings round-trip cleanly.** A booking placed somewhere downstream lands in your booking screens with the right property, room and rate attached.

A concrete picture: Hotel Sunrise already publishes to four OTAs through its channel manager. You activate that channel manager for your organization, bind Hotel Sunrise once, map its rooms and rate plans — and from that point on, every rate edit the hotel makes lands in Adrasis in seconds. You did not call any of the four OTAs.

You see the result in the console. The channel manager is the conduit, not the place your operators work.

## Which channel managers are supported

Adrasis connects to **the most well-known channel managers** in the market — both global players and partners that lead in their regional markets. New partners are added through the same operator workflow.

For the list of partners available to your organization, open *Connectors → Integration*.

## What you do as an operator

For each channel manager you bring online:

1. **Activate the connector** for your organization.
2. **Bind a property** through the property's *Channels* tab. Enter the channel manager's identifier for the property.
3. **Map rooms, rate plans, meal plans, and attributes** between your catalog and the partner's vocabulary. The mapping page shows gaps and helps you close them.
4. **Watch the connector status** for the property — last successful message, error rates, anything in retry.

The platform takes care of the rest — partner sign-in, retries, format translation and duplicate-safe processing.

## What this means for your product record

Every inbound change from a channel-manager partner lands in the product record, tagged with the source. As an operator you can:

* Trace a rate or inventory cell back to the partner that wrote it.
* See, on the cell history, when the partner last touched it and what it was before.
* Override a partner-sourced cell from the console — manually or through Adragent — without losing the lineage record.

This is what makes "multi-supplier" honest in the platform: every cell carries provenance, you always know where the data came from.

## Adding a new channel manager

When a new channel manager partnership is available, you activate it for your organization, save the credentials, bind your properties and curate the mapping — the same workflow as any other channel.

## Where to next

* **The shared inbound model** → [Inbound overview](/console/distribution/inbound.md)
* **A buyer flow with a bedbank partner** → [Bedbank supply](/console/distribution/inbound/bedbank-supply.md)
* **Rich multilingual content sources** → [Content & catalog sources](/console/distribution/inbound/content-catalogs.md)
* **The cell history surface** → [Cell history](/console/pricing-and-availability/cell-history.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/channel-managers.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.