Adrasis Console is airport transfer booking software for travel agencies and tour operators. Price private and shared routes on a contract, book them through the same search, prebook and book flow as a room, and sell them in packages or through the API.
Adrasis covers the commercial side of a transfer: the contract behind it, the price, the booking and the channels that sell it.
Scope. Adrasis is a transfer booking system for travel agencies and tour operators that sell transfers as a product: pricing, search, booking, packaging, and selling to partners through the API. Vehicle dispatch, driver assignment and fleet tracking are not part of Adrasis.
Airport transfer software often means vehicle and driver management, and that work belongs to whoever operates the vehicles. Adrasis serves the business that sells the ride: it holds the route on a contract, prices it, takes the booking and lets you sell the transfer together with the hotel, the tour and the flight.
In the Console, a transfer is point-to-point ground transport sold alongside a stay, such as Antalya airport to a resort, or the hotel back to the airport at the end of the stay. You author it as a contract and choose how it is priced.
If your team already works with hotel contracts, most of this will feel familiar. A contract backs every transfer, and children are priced by age, just as they are for rooms. The main difference is what the price is built on: a route and a direction instead of a room-night.
By route, direction and service class, not by the night. Every route runs as private or shared service, and each class follows its own pricing rule.
A private transfer has one price per vehicle, whatever the party size, so you price the vehicle rather than the seats. The system picks the smallest vehicle type that fits the party, using the minimum and maximum number of passengers set for each vehicle type on the contract.
A shared transfer is priced per person on an adult base, and children are priced by age bracket, the same way rooms price children. Two adults and a six-year-old pay two adult fares plus the price the contract sets for the bracket a six-year-old falls into.
Routes are directional. An arrival from the airport to the hotel and a return from the hotel to the airport are priced separately, so a round trip is two legs and costs the sum of both. The arrival and the return can carry different prices.
A route runs between pickup zones, and a zone is either an airport or an area. Antalya airport to a resort area is one route. The same two zones in the opposite direction make its return, with a price of their own.
As with a room, the sell price, cost, currency, validity and cancellation policy live on the contract, next to the fields only a transfer needs.
| Element | What it carries |
|---|---|
| Pickup zones | The airport or area each route runs between. |
| Vehicle types | Capacity as a minimum and maximum number of passengers, used to price private service. |
| Service class | Private, priced per vehicle, or shared, priced per person. |
| Child brackets | Age ranges, and how each one is priced on shared routes. |
| Cancellation policy | Date-based refund and penalty terms. |
| Booking cut-off | The minimum number of hours before pickup at which the transfer can still be booked. |
No nightly inventory to maintain. A transfer is bounded by vehicle capacity and its booking cut-off, not by a calendar of inventory cells, so there is nothing to top up each day.
The cancellation policy is date-based. How much is refunded and how much is kept as a penalty depends on when the cancellation happens, and the quote shows both figures before the cancel is confirmed.
In the same three steps as a room: search, prebook and book. The price is held at prebook and confirmed at book.
Choose the route, the direction, the date and the party. Search returns what can be sold to that party: private offers priced per vehicle and shared fares priced per person.
The chosen offer is priced again and held while the booking details are completed. A moved price or a withdrawn offer shows up here, before anything is confirmed.
The booking confirms, and a cancellation quote from the route's policy is attached to it.
The booking cut-off is enforced. If a route's cut-off is 24 hours and the pickup is 20 hours away, the transfer is not bookable, even when a vehicle is free. A last-minute request the contract does not allow never becomes a confirmed booking.
Canceling starts from a quote as well, and the same quote-first step applies when the transfer sits inside a package or a trip.
Yes, in two ways. A package sells several services at one inclusive price. A trip groups bookings that were made separately and keeps their prices apart.
A package sells two or more services, such as a hotel stay, a transfer, a tour or a flight, as one booking. Hotel Sunrise for five nights, an airport transfer and a return charter flight confirm as one total, with a per-item breakdown you can always open.
A package confirms only when every service in it is secured. If the last two charter seats sell out mid-booking, nothing is booked and nothing is charged. After confirmation each service is its own item: cancel the transfer and it is charged under the transfer's own policy, while the hotel and the flight keep the prices they were booked at.
Your team composes packages in the Console, and packages can also be put together and sold through your connected sales channels and the partner API. One package sells one provider's services in one currency.
When a traveler books a hotel, a transfer and a tour separately, the bookings can be linked into one trip. Each keeps its own price, policy and status. The trip lists them in date order with a combined total per currency, and gives one cancellation quote across all of them, for example a refundable hotel, a transfer with a 50% penalty and a non-refundable flight. Canceling the whole trip is one action, and each booking is canceled under its own policy.
Transfers use age brackets the same way rooms do. In a package booked through the API, each traveler's age is worked out on each service's own date, so a child who has a birthday during the stay counts at the new age for the return transfer.
Yes. The Distribution Partner API has its own transfer endpoints, and AI agents reach the same operations through the MCP (Model Context Protocol) server.
The Distribution Partner API is the REST/JSON contract your technical partners use to search and book your supply. Transfers follow the same search, prebook and book sequence as accommodation, on their own endpoints under /api/v1:
POST /transfer/search POST /transfer/prebook POST /transfer/book Idempotency-Key: <uuid>
distribution:booking scope. Search is included, so a read-only credential cannot search transfers.Idempotency-Key header. When a request times out and is sent again with the same key and the same body, the partner gets the original booking back, not a second one.cancellation-quote call on the booking shows the penalty without changing anything, and cancel then commits it.The MCP server wraps the same REST contract for AI agents, with the same authentication, scopes and pricing rules. Three tools cover transfers: search_transfers, prebook_transfer and book_transfer. The prebook tool returns a cancellation snapshot with its token, and the book tool requires an idempotency key, just like the REST call.
For how partners connect, read B2B distribution and API. For AI agents, read the MCP server page.
Try the Console free, or walk us through the routes you sell and the channels you sell them through, and we will show you where Adrasis fits. Plans are priced per organization, not per user.