> 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/tours-transfers-and-flights/tours-transfers-flights.md). # Overview Alongside accommodation, Adrasis carries three more product lines: **transfers** (point-to-point ground transport), **tours** (guided activities and excursions), and **flights** (charter seat blocks you resell). Each has its own contract, pricing, availability and cancellation policy, and each is searched, prebooked and booked through the same flow as a room. {% hint style="info" %} **If you know accommodation, you know most of this.** A transfer, a tour and a flight are authored as contracts and sold through the same *search → prebook → book* flow as a room. The differences are in what each product is priced *by*. {% endhint %} ## The three product lines ### Transfers *** `Operator-side · bookable` Point-to-point ground transport, airport to hotel, area to area. Priced per vehicle (private) or per person (shared), by route and direction. Open [Transfers](/console/tours-transfers-and-flights/transfers.md) [→](/console/tours-transfers-and-flights/transfers.md) *** ### Tours *** `Operator-side · bookable` Guided activities and day excursions. Each tour offers departure options, a shared seat or a private group, with its own operating calendar and seat capacity. Open [Tours](/console/tours-transfers-and-flights/tours.md) [→](/console/tours-transfers-and-flights/tours.md) *** ### Flights *** `Operator-side · bookable` Charter seat blocks you hold and resell. Priced per passenger type, adult, child, infant, against a held seat block with a ticketing deadline. Open [Flights](/console/tours-transfers-and-flights/flights.md) [→](/console/tours-transfers-and-flights/flights.md) *** ## What they share with accommodation * **Contracts back them.** Sell price, cost, currency, validity and cancellation policy live on a contract, exactly as for a room. * **Children price by age.** Transfers and tours use age brackets the same way rooms do. Flights are the exception, they price by passenger type. * **Search → prebook → book.** A quote is held at prebook and confirmed at book, with the same idempotency guarantees. * **Cancellation quotes.** Every product returns a refund-and-penalty quote before a cancel. ## What is different * **They price by route, departure or seat, not room-night.** A transfer prices by route and direction; a tour by departure option; a flight by passenger type. * **Availability is capacity, not a calendar of cells.** Tours and flights draw down a held seat pool; transfers check vehicle capacity and a booking cut-off. ## Where to next * **Point-to-point transport** → [Transfers](/console/tours-transfers-and-flights/transfers.md) * **Activities and excursions** → [Tours](/console/tours-transfers-and-flights/tours.md) * **Charter seat blocks** → [Flights](/console/tours-transfers-and-flights/flights.md) * **Group bookings into one itinerary** → [Trips](/console/tours-transfers-and-flights/trips.md) * **Sell several services at one inclusive price** → [Packages](/console/tours-transfers-and-flights/packages.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 following URL with the `ask` and `goal` query parameters: ``` GET https://adrasis.gitbook.io/console/tours-transfers-and-flights/tours-transfers-flights.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. 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.