# Distribution overview

Distribution in Adrasis Console is **bidirectional**. The same operating record receives supply coming in from suppliers and serves it back out to partners — one catalog view, two flows, one set of contracts.

This page explains the two directions, why one shared record serves both, and what an operator sets up to get distribution running.

{% hint style="info" %}
**One product record drives every channel.** You set rates and inventory once; Adrasis prepares the right version for each partner.
{% endhint %}

***

## The two directions

<figure><img src="/files/PDRsCWrRbDwGHSoaRUbC" alt="Suppliers feed Adrasis and booking partners receive curated supply from Adrasis"><figcaption><p>Suppliers feed Adrasis; outbound partners receive the curated catalog, rates and inventory. Booking traffic returns the other way at each end.</p></figcaption></figure>

| Flow         | Direction          | What you publish or receive                                                                              | Who you talk to                                   |
| ------------ | ------------------ | -------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| **Inbound**  | Supplier → Adrasis | Property catalog, rates, inventory, restrictions, bookings                                               | Hotels, channel managers, supply-side bedbanks    |
| **Outbound** | Adrasis → Partner  | Availability, rates and inventory updates, booking acknowledgements, content updates, visible rate plans | OTAs, metasearch engines, B2B partners, superapps |

The agency operating Adrasis can be on either side — sometimes both. A single organization can receive supply from a chain hotel through a channel manager, publish out through a bedbank distributor's B2B network, and show rates on a metasearch engine from the same product record.

***

## Why one record for both directions

Splitting supply intake and outbound distribution into separate tools creates drift. Adrasis keeps them together for three practical reasons.

### Rates do not change between directions

***

`single fact · no drift`

*EUR 120/night, refundable, breakfast included* is the same rate whether it came from a supplier or is going out to a partner. Storing it twice creates drift.

***

### Mapping reconciles in one place

***

`one room match`

A room called *Deluxe Sea View* by one supplier and *DSV Standard* by a partner must resolve to the same room once, not separately in each direction. See [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md).

***

### Contracts span both ends

***

`one rule per markup`

A markup applied to a supplier rate before publishing it to a partner is one pricing rule, not two parallel calculations that your team has to keep in sync.

***

Adrasis absorbs partner-specific differences internally; your operators work from the same product record.

***

## What you configure as an operator

In the console, distribution is set up per organization from a small set of pages.

| Page                                            | What you do                                                                                                                                                          |
| ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Channels** *(under Connectors → Integration)* | See available connectors and manage your organization's credentials.                                                                                                 |
| **Property → Channels tab**                     | Decide which channels each property publishes to or ingests from, and check mapping status.                                                                          |
| **Mapping curation**                            | Reconcile partner room codes, rate plans, attributes and meal plans with your catalog. See [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md). |
| **Outbound feeds**                              | Configure outbound channel feeds for the most well-known metasearch engines and B2B partners.                                                                        |

## Where to next

* **How channels are configured end to end** → [Channels](/console/distribution/channels.md)
* **What Adrasis publishes outward** → [Outbound overview](/console/distribution/outbound.md)
* **What flows in from suppliers** → [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/overview.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.