Adrasis Console is where a travel agency brings its supply together, prices it and sells it. Direct hotel contracts, channel managers and bedbanks come in; your own team, partner agencies and online channels sell from the same record.
Hotel software sends one property's rates out to many channels. An agency does the reverse first: it pulls supply in from many sources, then sells the result through many channels.
That difference shapes the daily work. The same Istanbul hotel can reach you through three sources in one year: a direct contract for May and June, a bedbank for July and August, and a regional supplier for the rest of the season. You still sell one room, and Adrasis keeps track of which contract stands behind every date.
Markups (amounts or percentages added to the buying price), packaging and review sit on top of raw supply. Buying a room-only rate at 80 EUR and selling it with breakfast at 95 EUR is a single operator action, not a spreadsheet exercise.
Suppliers may name the same room differently. When the room type, capacity and features match, you review the source records and map them to the same room in your catalog. Approved mappings are used for subsequent rate and booking messages.
An agency does not only resell what it receives. It opens approved supply to its own partners and sales channels, which is why distribution sits in the same Console as contracts and pricing.
Adrasis brings supply from different sources into your catalog. Records for the same product are linked after their mappings are approved, and you can trace the source of rates and inventory.
A contract holds the counterparty, the properties and rooms it covers, validity, the net rate or commission model, currency, allotments and release period, cancellation and child policies, payment terms and the markets it may be sold in. Most contracts arrive as a supplier spreadsheet. Upload it and a guided import reads the rate grid, checks it three ways and shows you every cell before anything goes live. If a recomputed price does not match the contract, the import stops.
When a hotel already works with a supported channel manager, you connect to that source instead of re-keying rates. A property uses one source connection at a time for rates and availability. While that connection exists, source rates are read-only in the Console and price changes are made at the channel manager. Pausing the data flow does not change this rule.
Bedbank inventory comes in as third-party supply at net rates. You add your markup and decide which markets and channels see it. Those bookings are handled on their own buyer-side screens, because their cancellation and settlement terms follow the bedbank contract.
Structured content feeds bring multilingual descriptions, images and amenities for the properties you onboard, so working with a new hotel chain does not start with hundreds of hand-written paragraphs.
Prices are built in layers you can explain later: a base rate, the contract's markup or commission, promotions, audience rules and an optional floor price.
One room can sell under several rate plans at once, each with its own conditions and audience. A derived plan follows its parent: raise the public refundable rate to 200 EUR, and a non-refundable plan set 10% below it moves to 180 EUR without a second edit.
Every calendar cell keeps its history: what changed, when, and whether an operator, a connected partner or Adrasis AI Operator changed it.
Sales & Distribution lets another agency sell your products without a shared account or a second system.
Pick the agency or create its record, then choose the market it sells from and the currency of the relationship.
Access is closed by default. Activate the destinations the partner may sell and exclude anything you keep direct.
Use a market default, an agency override or a product rule. A floor price brings the amount calculated after discounts up to the minimum you set.
The agency searches and books from its own login, and every booking is recorded under your organization with the partnership attached.
A partner receives one payable price, never the source amount, commission or markup behind it, and its own retail markup stays private from you. Partners never see each other's terms. You can suspend a partnership and resume it later, or revoke it when the relationship ends.
If you want your team to work under your own brand, the settings for using your own brand put your name, logo and address on the Console they sign into.
You send instructions through the Console chat panel, email or WhatsApp. The AI Operator prepares the operation and brings it back for your approval before applying it. SMS is used for alerts and to approve or reject a specific prepared operation.
It is built for the work around a decision: reading a supplier email, finding the affected properties and dates, and setting up repetitive changes. A few instructions agencies send:
Requests that only read data are answered at once. Anything that changes data comes with a preview of what changes and where, and runs only after you confirm. A prepared operation waits up to 24 hours by default, then expires. The AI Operator works only inside your organization's data, and its usage is included in your plan within daily and monthly allowances.
Alongside accommodation, the Console carries transfers, tours and charter flight seat blocks, each with its own contract and cancellation policy.
Every product line is booked through the same search, prebook and book flow as a room. Two or more services can be sold as one package with one inclusive price, which confirms only when every service in it is secured. Bookings made separately can be grouped into one trip. Each booking keeps its own price, cancellation policy and status, and the trip provides one cancellation quote across all of them.
If tours and charter seats are the core of your business, the tour operator page goes deeper. If you sell airport and point-to-point transport, see transfers.
Apply for Console access, or walk us through your suppliers and channels and we will show you where Adrasis fits. Plans are priced per organization, not per user.
