> 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/bedbank-supply.md).
# Bedbank supply (buyer feed)
Adrasis can receive **third-party bedbank inventory** as supply: a bedbank (B2B bed-supply network) exposes its hotel catalog, rates and inventory; you consume it as a buyer and resell it through your own distribution channels. On this kind of contract, Adrasis acts as the buyer; the bedbank is the supplier.
A concrete picture: a B2B aggregator network gives you live access to several thousand hotels across Spain. You bind those hotels into your organization once, expose them on your own outbound channels (your website, the metasearch engines you publish to, your B2B partners), apply your own markup, and start selling — without contracting each hotel one by one.
## Direction at a glance
You receive catalog, rates and inventory inward; bookings flow back to the bedbank to be confirmed against their inventory.
You receive the bedbank's hotel catalog, rates and inventory inward; bookings placed by *your* customers (through your own outbound channels or direct sales) flow back to the bedbank to be confirmed against their inventory.
## Buyer-side boundary
Bedbank supply is a buyer-side flow. The platform keeps bookings placed against bedbank inventory separate from bookings on properties you operate directly:
* **Separate booking surface.** Bedbank bookings use the buyer-side workflow, not the native property booking inbox.
* **Separate reconciliation.** Settlement, cancellation and liability follow the bedbank contract, not your direct-property defaults.
The separation is operational. A booking against bedbank inventory has different reconciliation, cancellation and settlement rules from a booking on a directly managed property.
## What you can do
Bedbank supply is consumed differently from a directly-managed property — you are reselling third-party inventory, not maintaining your own catalog:
* **Search across the supply.** Adrasis search can include bedbank supply alongside your native catalog; results show you which is which so you can decide.
* **Apply markup and routing rules.** Decide how bedbank supply is exposed in your own outbound channels — priced, blended, routed to specific markets.
* **Manage bookings through the buyer-side surface.** Bookings you place against bedbank inventory go through their own settlement and cancellation workflow, separate from your native bookings.
You do not review the bedbank's catalog the way you review your native catalog — the bedbank is the system of record for those properties. Adrasis treats them as third-party supply you can resell.
## Pricing — net rate plus your markup
Bedbank pricing is **net-rate**: the bedbank gives you a net rate, you add your markup (the price gap or margin you decide), your customer sees the gross rate. The pricing engine knows the connector is a bedbank and applies the right policy automatically — you do not configure net-vs-commission per binding.
If the bedbank feed is in EUR and your organization operates in TRY, currency conversion is part of the same engine; exchange rates come from a configurable source, every conversion is recorded.
See [Pricing engine](/console/pricing-and-availability/pricing-engine.md) for the rate derivation model.
## Where to next
* **The shared inbound model** → [Inbound overview](/console/distribution/inbound.md)
* **How pricing handles bedbank net rates** → [Pricing engine](/console/pricing-and-availability/pricing-engine.md)
* **The channel configuration model** → [Channels](/console/distribution/channels.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/bedbank-supply.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.
