# Bedbank distribution (supplier feed)

Some B2B distributors offer a **supplier-feed contract** for hotel chains and agencies that want to distribute their inventory through the distributor's buyer network — tour operators, agents, smaller OTAs. On this kind of contract, Adrasis acts as the supplier; the bedbank (B2B bed-supply network) distributor resells your inventory to its buyers.

A concrete picture: you operate 30 boutique hotels across the Aegean coast. Instead of selling each one to dozens of small tour operators yourself, you contract a B2B distributor as a supplier-feed partner: you publish availability, rates and inventory for all 30 hotels to the bedbank once, and its existing tour-operator buyers can resell them. Bookings come back to your usual booking screen.

## Direction at a glance

<figure><img src="/files/Q1ztOMEFR9TaZXVamP0v" alt="Adrasis publishes availability, rates and inventory to a bedbank; bookings come back to the regular booking screen"><figcaption><p>You publish availability, rates and inventory to the bedbank; bookings flow back to your regular booking screen.</p></figcaption></figure>

You push availability, rates, and restrictions *to* the bedbank. Bookings placed by the bedbank's buyers land back in Adrasis's regular booking surface — the same screens you already use.

## What you can do

For each property you publish through a bedbank distribution channel, you decide:

* **Whether it goes to that channel at all.** Bind it via the property's *Channels* tab; unbind it whenever you want.
* **Which rate plans go.** Use the per-channel restriction overlay to expose specific rate plans and keep others internal — the same mechanism you use for any other channel. See [Stop-sale & restrictions](/console/pricing-and-availability/stop-sale-restrictions.md).
* **How the partner sees your rooms and meal plans.** Mapping curation translates *your* rooms, rate plans and meal plans into the partner's vocabulary. See [Mapping & curation](/console/mapping-and-curation/canonical-mapping.md).
* **How net-rate vs. commission policy applies.** Bedbanks use net-rate pricing; the platform's pricing engine applies bedbank pricing rules automatically.

You configure all of this through the regular channel surface. There is no separate "bedbank dashboard" — the same screens you use for any outbound channel.

## Two flows, one connector

A bedbank that sells in both directions is connected once. The same partner can be both your **outbound supplier-feed target** (this page) and your **inbound supply source** (see [Bedbank supply](/console/distribution/inbound/bedbank-supply.md)) — the platform models that explicitly without merging the two:

* **One connector, one set of credentials.** Activate the bedbank once for your organization (your organisation account).
* **Two flows kept separate.** Bookings against your own properties (this flow) never get confused with bookings you place against the bedbank's third-party inventory (the buyer flow). Different surfaces, different reconciliation, different liability.

The reason for the separation is operational. A booking against *your* property has different reconciliation, cancellation, and settlement than a booking *against the bedbank's inventory* where you are reselling. Mixing them at the data layer creates confused defaults; keeping them separate makes the responsibility clear at every step.

## Bookings come back to your regular surface

When a bedbank buyer books one of your properties:

1. The bedbank sends the booking to Adrasis through the partner connection.
2. The platform prepares it and stores it as a regular booking in your organization.
3. The booking shows up in your usual booking inbox — the same one you use for direct bookings or other channel bookings.

There is no separate "bedbank bookings" view, no separate workflow. You handle a bedbank-sourced booking the same way you handle a direct one.

## Where to next

* **The buyer-side flow with the same kind of partner** → [Bedbank supply](/console/distribution/inbound/bedbank-supply.md)
* **How rate plan exposure works across all channels** → [Stop-sale & restrictions](/console/pricing-and-availability/stop-sale-restrictions.md)
* **The channel configuration model** → [Channels](/console/distribution/channels.md)
* **Other outbound channels** → [Outbound overview](/console/distribution/outbound.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/outbound/bedbank-distribution.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.