# Inbound

Inbound is everything Adrasis receives from the outside world: catalog content, live availability, rate and inventory updates, restrictions, and bookings flowing **into** your product record. Supply reaches Adrasis from three kinds of source and lands in the same operator view.

## In this section

* [Channel manager partners](/console/distribution/inbound/channel-managers.md) — leading channel managers across the travel stack.
* [Bedbank supply (buyer feed)](/console/distribution/inbound/bedbank-supply.md) — third-party bedbank inventory consumed as supply.
* [Content & catalog sources](/console/distribution/inbound/content-catalogs.md) — structured rich content feeds: multilingual descriptions, images, attributes, categories, place references.

## Where supply comes from

Adrasis takes supply from three kinds of upstream:

| Source                        | What it is                                                                                   | What it brings                                                                            |
| ----------------------------- | -------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Channel managers**          | Partners that already connect to many hotels and publish their rates and inventory outward.  | Live rates and inventory.                                                                 |
| **Content & catalog sources** | Curated feeds that publish structured property content across many languages.                | Multilingual descriptions, images, attribute and category vocabularies, place references. |
| **Supply-side bedbanks**      | Third-party bedbanks (B2B bed-supply networks) that resell their hotel inventory to Adrasis. | Third-party catalog, rates and inventory for reselling.                                   |

Every source ends in the same place: the shared product record. Pricing, mapping, distribution and payments all see one view, regardless of where the data came from.

## What flows into the product record

A clean inbound flow updates exactly three things:

* **Rates** — the cell-level rate for a (property, room, rate plan, date, occupancy) tuple.
* **Inventory** — the cell-level count of bookable units.
* **Restrictions** — stop-sale, min/max stay, day-of-week constraints, advance-purchase rules.

Bookings that land alongside (some partners include them) go through their own paths — either your native booking surface (for bookings against your own properties) or a separate buyer-side surface (for bedbank reselling).

## How channels handle inbound

For each inbound channel:

1. The partner sends rates and inventory on its own schedule (or in real time).
2. Adrasis checks the connection, prepares the message, and queues it for processing.
3. The platform resolves *which* property and room each partner identifier refers to (mapping).
4. The change lands in the product record, with provenance — *which partner wrote this, when*.
5. If something fails, the message routes through a retry chain and then to a holding area you can replay or investigate. Nothing fails silently.

You see the result in the regular product views: rate calendars, inventory grids, and channel history. Nothing about being inbound makes the data different from data you typed in yourself.

## What you control as an operator

For each inbound source you operate:

* **Activate the connector** for your organization (your organisation account).
* **Add the partner-issued credentials.**
* **Bind the properties** that this connector populates.
* **Curate the mapping** — partner room codes, rate plans, meal plans and attributes, all matched to your catalog.
* **Watch the connector status** — recent message counts, success/failure rates, items that need replay.

If you can do all five, the data flow is yours; you control what comes in, when it comes in, and what it lands as.

## Provenance — every cell carries who touched it

This is what makes "multi-supplier" honest in the platform: every rate or inventory cell knows which partner last wrote to it. You can:

* Trace a cell back to the partner that wrote it.
* See per-source freshness on every cell.
* Override a partner-sourced cell from the console without losing the lineage.

The [cell history](/console/pricing-and-availability/cell-history.md) surface is where you see this.

## Where to next

* **Channel manager partners** → [Channel manager partners](/console/distribution/inbound/channel-managers.md)
* **Buyer flow with bedbank partners** → [Bedbank supply (buyer feed)](/console/distribution/inbound/bedbank-supply.md)
* **Rich multilingual content sources** → [Content & catalog sources](/console/distribution/inbound/content-catalogs.md)
* **The connector configuration model** → [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/distribution/inbound.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.