# Outbound

Outbound is everything Adrasis publishes to the world: availability, rate and inventory updates, booking acknowledgements, content updates and partner-specific messages. Your curated supply reaches booking partners from one shared product record; Adrasis handles partner differences behind the scenes.

## In this section

* [Bedbank distribution (supplier feed)](/console/distribution/outbound/bedbank-distribution.md) — distributing your inventory through bedbank (B2B bed-supply network) partners that resell to their buyer networks.
* [Metasearch & B2B platforms](/console/distribution/outbound/metasearch.md) — the most well-known metasearch engines and B2B aggregators.
* [Partner API credentials](/console/distribution/outbound/partner-api-credentials.md) — issuing client\_id and client\_secret pairs for partners that consume the Distribution API directly.

## Channel families

| Family                       | What it is for                                                                                    |
| ---------------------------- | ------------------------------------------------------------------------------------------------- |
| **Bedbank distribution**     | Resell your inventory through B2B distribution networks (tour operators, agencies, smaller OTAs). |
| **Metasearch engines**       | Show your rates to travellers comparing across properties at search time.                         |
| **B2B aggregator platforms** | Connect to buyer networks through partner-specific connections.                                   |

For the list of channels available to your organization (your organisation account), open *Connectors → Integration*.

## What you decide as an operator

For any outbound channel, the questions you control:

1. **Which properties go through it.** A property's *Channels* tab is where you bind it to a channel.
2. **Which rate plans to expose.** You can keep a rate plan internal-only or surface it selectively to certain channels — the per-channel restriction overlay is what does this. See [Stop-sale & restrictions](/console/pricing-and-availability/stop-sale-restrictions.md).
3. **How rates and meal plans translate.** Mapping curation is where partner codes meet your catalog.
4. **Credentials and activation.** Once everything is in place, you flip the binding to active and the feed starts running.

The platform takes care of the rest — retries, partner-specific sign-in, format translation and delivery timing.

## Bookings come back

Several outbound channels are bidirectional in practice — you publish rates and inventory out, partners send bookings back in. When that happens:

* Bookings on **your own properties** land in your normal booking screens — same workflow as direct bookings.
* Bookings on **third-party inventory you resell** (the buyer flow with bedbanks) land in a separate buyer-side screen so they do not get confused with your native catalog.

[Bedbank distribution (supplier feed)](/console/distribution/outbound/bedbank-distribution.md) is the clearest example.

## You pick the partner; the platform does the rest

Behind the scenes the platform routes outbound traffic to fit each partner — credentials, retries, format translation and timing. You configure the channel from one place in the console; you do not pick the path.


---

# 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/outbound.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.