> 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/readme.md).

# Platform overview

Adrasis Console brings accommodation supply, pricing, contracts and distribution into one operating view. Hotel and supplier inventory stays in one place; your team reviews it, prices it and publishes it to the booking channels you work with.

This page explains where Adrasis fits, why agencies need a different operating model from hotel-only tools, and how supply moves from source to sale.

{% hint style="info" %}
**Reduce your operational overhead at a glance.** Adrasis starts from the agency workflow: many suppliers, many contracts, many selling channels, one team accountable for the outcome.
{% endhint %}

***

## The travel chain at a glance

| Part of the chain    | Role                                                                           | Examples                                                                       |
| -------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------ |
| **Supply sources**   | Own the rooms, rates, contracts or third-party inventory you sell.             | Independent properties, hotel chains, bedbank stock owners                     |
| **Channel managers** | Connect many properties to the wider travel market.                            | The most well-known channel managers in hospitality                            |
| **Agency hub**       | Collects supply for agencies, reviews it, prices it and distributes it onward. | Adrasis Console                                                                |
| **Booking channels** | Where travellers and partners search, compare and book.                        | Online travel agencies, metasearch engines, B2B partners, consumer travel apps |

The hotel side already has mature tools for sending rates and inventory from one property or chain to many booking channels. The agency side has a different job: collect supply from many sources, combine contracts and markups, review content, then sell the result through many channels.

Adrasis Console is the agency hub for that job.

***

## Why the agency angle is its own job

Hotel-side tools were built around one supply unit sending rates out to many channels. An agency works the other way around: it pulls supply *in* from many sources before sending it back out.

* **Multiple contracts at once.** A single Istanbul property might come to you through three sources — a direct contract for May–June, a bedbank for July–August, a regional supplier for the rest of the year. You sell *one* room; Adrasis tracks which contract is behind every cell.
* **Markups, packaging, and review** sit on top of raw supply. *Buy room-only at 80 EUR, sell breakfast-included at 95 EUR* is one operator action.
* **One shared catalog view** keeps supplier variations under control. *Deluxe Sea View* from one supplier and *Superior Sea-Facing Double* from another can resolve to the same room, so a traveller sees one clean listing instead of two near-duplicates.
* **Distribution is part of the agency job.** Your agency can sell approved supply onward to partners, not only resell what it receives.

Building these workflows on top of a hotel-only tool leaves the agency stitching the gaps. Adrasis assumes the agency workflow from the first screen.

***

## How supply flows through Adrasis

<figure><img src="/files/C4ZtxHJoaeWdG9cnLWR9" alt="Supply sources and channel managers feed Adrasis, which distributes approved inventory to booking channels"><figcaption><p>Supply comes from properties, suppliers and channel managers, lands in one shared operating view, gets checked and priced, then reaches the booking channels you choose.</p></figcaption></figure>

* **Supply intake** brings in property, room, rate and inventory data from direct contracts, suppliers and channel managers.
* **Mapping and review** reconcile supplier-specific rooms, attributes and meal plans into the catalog your operators work with.
* **Pricing, availability and contracts** are managed centrally, with the commercial terms behind each date and room kept visible.
* **Distribution** sends the approved catalog, rates and inventory to the channels you choose.

***

## Where to next

* **How Adragent runs operator work** → [Adragent Overview](/console/adragent/overview.md)
* **How supply and distribution channels work** → [Distribution overview](/console/distribution/overview.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/readme.md?ask=<question>&goal=<endgoal>
```

`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.