Adrasis Console is where a tour operator loads supplier contracts, holds allotments and charter seat blocks, and sells rooms, transfers, tours and charter seats one by one or as packages with one inclusive price. Your team, partner agencies and connected sales channels work from the same records.
The contract holds the terms, and your rate plans are the prices you publish from it. When a number on a booking looks wrong, the contract is where you look.
A hotel contract carries the counterparty, the properties and rooms it covers, validity, the pricing model (net rate plus markup, or commission on gross), currency, allotments and release period, cancellation and child policies, payment terms and the markets it may be sold in. Change the markup and the rate plans built on it follow; change the allotment and inventory follows.
Your Hotel Sunrise contract holds 10 Deluxe rooms per night for July, with a 7-day release period. By July 18 you have sold 4 of them for the night of July 25. On July 18, seven days before arrival, the 6 unsold rooms go back to the supplier, who can now sell them through other channels. Your 4 bookings stay on contract terms.
The contract page shows sold against held for every night, with the release date highlighted, so you see thin inventory before a channel does. Alongside the allotment, a contract can give you on-request rooms on the same date: rooms you ask the supplier for as bookings arrive, subject to their confirmation.
From the chat panel in the Console, email, WhatsApp or SMS, you can ask the AI Operator to “list the allotments whose release period expires this week” or to “flag every contract where the July allotment is more than 70% sold for any night.” Any change it prepares waits for your approval before it applies.
Season contracts are often priced only for bookers from a named group of countries. At upload you bind the sheet's market line to one of your source markets, and from go-live that rate plan is offered only to bookers inside the market. A plan without a market binding sells everywhere, and a supplier that prices each market differently gets one rate plan per market.
When a supplier changes rates, cancellation terms, allotments or markets mid-season, the amendment becomes a version with its own validity window. Bookings made earlier keep the old terms and new bookings take the current ones, so “which bookings does our June 1 policy change affect?” has an answer that holds up in a dispute.
Most contracts arrive as a supplier spreadsheet, and loading one takes four steps:
The import reads period bands, the rate grid, allotment and child pricing, and pulls free-text terms such as a no-show rule out for review.
Structure: do periods, occupancy and child brackets add up? Cross-read: does an independent reading match the grid? Math: does a recomputed price match the contract?
Period by room by occupancy, with the contract value beside the recomputed one and old against new for an amendment. You can stop here.
Prices, child rules, promotions, allotment and release periods go live after a final integrity check.
The math check is a hard gate. If the system computes 120 EUR where the contract says 115 EUR, the import stops until the source is corrected. The AI Operator also suggests how the supplier's room names map to your categories, such as Superior Garden View to Deluxe, and wherever its suggestion and your catalog differ, you decide.
A tour operator sells more than rooms. Each product line has its own contract, price and cancellation policy, and all four sell through the same search, prebook and book flow.
A quote is held at prebook and confirmed at book, and every product gives a cancellation quote before anything is canceled. What differs is what sets the price and what stops a sale.
| Product | Priced by | Availability is limited by |
|---|---|---|
| Rooms | Night, room and occupancy, under a rate plan | Inventory per date, allotments, stop-sale and stay rules |
| Transfers | Vehicle on private routes, person on shared routes, by route and direction | Vehicle capacity and a booking cut-off before pickup |
| Tours | Person on a shared departure, group on a private one | Operating days, seats per departure, release and cut-off |
| Charter flights | Passenger type (adult, child, infant), with base and tax | The seat block you hold and a ticketing deadline |
Routes run between pickup zones, such as Antalya airport and a resort. Private service has one price per vehicle whatever the party size, and the system picks the smallest vehicle type that fits. Shared service is priced per person, with children by age bracket. Arrival and return are separate legs. Inside the route's booking cut-off, for example under 24 hours before pickup, a transfer cannot be booked even with a vehicle free.
A single-day product is an excursion and a multi-day one is a tour. The traveler buys a departure option: a shared seat priced per person, or a private group priced per group and optionally tiered, such as 1 to 4 and then 5 to 8 people. The contract sets the operating days (for example Monday, Wednesday and Saturday), blackout dates, seats per departure date, when unsold capacity is released and the latest a booking is taken. Each booking draws down the departure's seats, and a full departure closes for that date.
A flight is a charter seat block you hold and resell, such as Istanbul to Tbilisi on Saturdays, 50 seats across the season. Fares are set per passenger type (adult, child, infant) and split into base and tax, and an infant takes no seat. Outbound and return are priced separately. Seats sell until the ticketing deadline, when unsold seats return, and the block is a hard limit with no overbooking past it.
Charter seats only. Flights in Adrasis are seat blocks you contract and hold. Scheduled airline ticketing is not part of the product.
A package sells two or more services as one booking at one inclusive price. A trip ties together bookings that were made separately. Adrasis keeps the two apart.
Five nights at Hotel Sunrise, an airport transfer and a return charter flight reach the traveler as one total with one confirmation, while you see each service as its own item with its own dates, policy and status. Building packages from live services this way is often called dynamic packaging.
A package confirms only when every service in it is secured: if the last two charter seats sell out mid-booking, nothing is booked. Prices are checked again at confirmation, and any movement, however small, stops the flow. The desk sees the old and the new total and chooses to take the new price, change the basket or discard it.
In the Console, Compose a package under Bookings takes a desk through four steps: party, services, combined offer and confirmation. The composition rules show as you build, and a basket in progress is saved for later. Connected sales channels and the partner API follow the same pattern: live services, one combined offer with an expiry, revalidation, confirmation. A package sells one provider's services in one currency.
Cancellation starts with a quote for the items you select. Each item is charged under its own policy, so a free-cancellation hotel and a non-refundable flight in the same package keep their own terms, and the remaining items keep their prices.
Before you sell into a market that regulates package travel, you complete the package compliance profile on your organization page:
At confirmation, the organizer's details, the services, the price and the disclosure are frozen into the booking. A later profile update applies to future sales only.
The legal wording stays yours. Adrasis records and freezes the evidence. The disclosure text, the applicable form and the decision that a sale is a regulated package remain the organizer's responsibility.
A trip groups a traveler's separate bookings into one itinerary in date order, with a total per currency and one cancellation quote across all of them. Each booking keeps its own price, policy and lifecycle. A trip is never a single price and never turns into a package, though a package booking can be linked into a trip.
For the rooms you contract, each layer answers one question: what the stay costs, what a cancellation costs and when the room can be booked.
One room can sell under several rate plans. A derived plan follows its parent by a percentage or fixed offset, and can also inherit the parent's restrictions, cancellation policy, open or closed status and minimum selling price. Raise the refundable Best Available Rate from 180 EUR to 200 EUR, and a non-refundable plan set 10% below it moves from 162 EUR to 180 EUR without a second edit.
A cancellation policy is tiered by how close to check-in the cancellation comes: free until a cut-off, a percentage penalty, a first-night charge, a fixed fee or non-refundable. A date-range exception overrides the tiers for a period, so a plan with free cancellation until 24 hours before check-in can be non-refundable from booking for stays between December 22 and January 5, without a second rate plan.
When several rules apply, the strictest wins, and the channel is told which rule blocked the booking.
Promotions change the price for a booking window and a stay window without rewriting the rate plan. An advance-purchase promotion rewards early booking, for example 15% off bookings made 60 or more days ahead, and a multi-night promotion such as stay 7, pay 6 makes the seventh night free. Stacking is set per promotion, and no promotion can reopen a stop-sale date or weaken a minimum stay.
Markets decide which bookers see which prices. Partnerships let other agencies sell your products under their own login, at the price you set.
A source market is a set of countries that says where a sale comes from. A destination is a set of places that says where your products are. Country groups such as CIS, Europe, MENA, Gulf and Balkans are commercial rather than geographic (whether Georgia belongs in CIS depends on the operator), so Adrasis ships them as templates. You clone one into your own markets and edit it, and your edits never touch the template or anyone else's markets.
Add an agency as a partner with the source market it sells from and the currency of the relationship, then activate the destinations it may sell. Access is closed by default. You can exclude single properties or rate plans, or include a product from outside the activated destinations.
For net-rate supply, pricing rules set what the partner pays: a market default such as CIS +12%, an override for one agency, or a rule pinned to a property, room or rate plan. A minimum selling price lifts an over-discounted price back to the floor instead of losing the sale. The partner sees one payable price, never your source amount, commission or markup, and its own retail markup stays private from you. Every booking it makes is recorded under your organization with the partnership attached.
The difference is who takes on the product and who sells it.
A tour operator contracts services and holds inventory: it takes allotments and seat blocks, builds packages and sets their price. A travel agency mostly sells products that others have contracted and priced. One company can play both roles, which is why contracts, packages and partner sales sit in the same Console.
Our guide to tour operators and travel agencies covers the difference in more detail.
Try the Console free, or walk us through your contracts, allotments and packages and we will show you where Adrasis fits. Plans are priced per organization, not per user.
