> For the complete documentation index, see [llms.txt](https://adrasis.gitbook.io/console/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adrasis.gitbook.io/console/distribution/inbound/channel-managers.md). # Channel manager partners A channel manager sends a hotel's prices and available room counts to connected sales channels. Adrasis can receive supply information from the hotel through this connection. ## Connection scope * **Supply information:** Hotel prices and room details are received from the channel manager. * **Updates:** Price and sales-condition changes sent by the hotel are transmitted through the relevant connection. * **Bookings:** Bookings received through the connection are linked to the relevant records using property, room and rate-plan mappings. You can review the information in the Console. Corrections to prices sent by the supplier must be made in the source system. ## 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. Adrasis manages connection authentication, retries and data-format conversion. It prevents a repeated message from applying the same change twice. ## One channel per property A property carries **one connected channel at a time** — the single source for its rates and availability. This keeps provenance unambiguous: two live channels writing the same rate and inventory cells would race, and you could not tell which one is authoritative. To move a property to a different channel, **disconnect the current one first**, then connect the new one. The Console blocks a second connection while one is already live and prompts you to disconnect first. ### External-supply connectors Some connectors run in **external-supply mode**: the partner addresses your rooms and rate plans by their Adrasis identifiers, so the room and rate-plan mapping step does not apply. For those, you manage rates and data flow from the *Supply* page rather than the mapping screen. ## Incoming price currency Agree one currency for the property with the supplier and set the property to that currency. If Hotel Sunrise sends TRY prices, its property currency is TRY and every incoming rate plan uses TRY. A received currency mismatch is rejected; it neither changes the property currency nor creates a foreign-currency plan. For independently authored EUR and TRY prices without an incoming channel-manager connection, use [static contract plans](/console/pricing-and-availability/rate-plans.md#choose-the-plan-currency). ## 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. * Inspect channel-supplied prices in read-only calendars. Correct a price at the supplying channel manager; manual Console and Adrasis AI Operator price edits are blocked while the source connection exists, including when transport is paused. 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 review 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 This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://adrasis.gitbook.io/console/distribution/inbound/channel-managers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.