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

# Transfers

A **transfer** is point-to-point ground transport you sell alongside a stay — *Tbilisi airport to a city-centre hotel*, *Antalya airport to a resort*. You author it as a contract, choose how it is priced, and travellers book it through the same *search → prebook → book* flow as a room.

{% hint style="info" %}
**No nightly inventory to maintain.** A transfer is bounded by vehicle capacity and a booking cut-off, not by a calendar of inventory cells. There is nothing to top up each day.
{% endhint %}

## How a transfer is priced

A route runs in one of two service classes:

<table><thead><tr><th width="160">Service class</th><th>How it prices</th></tr></thead><tbody><tr><td><strong>Private</strong></td><td>One price per vehicle, whatever the party size. The system picks the smallest vehicle type that fits the party.</td></tr><tr><td><strong>Shared</strong></td><td>One price per person, on an adult base, with children priced by age bracket.</td></tr></tbody></table>

Routes are **directional**: an arrival (airport → hotel) and a return (hotel → airport) are priced separately, so a round trip is the sum of two legs.

## What a transfer contract carries

<table><thead><tr><th width="180">Element</th><th>What it carries</th></tr></thead><tbody><tr><td><strong>Pickup zones</strong></td><td>The airport or area a route runs between.</td></tr><tr><td><strong>Vehicle types</strong></td><td>Capacity — minimum and maximum passengers — used for private pricing.</td></tr><tr><td><strong>Service class</strong></td><td>Private (per vehicle) or shared (per person).</td></tr><tr><td><strong>Child brackets</strong></td><td>Age ranges and how each is priced on shared routes.</td></tr><tr><td><strong>Cancellation policy</strong></td><td>Date-based refund and penalty terms.</td></tr><tr><td><strong>Booking cut-off</strong></td><td>The minimum hours before pickup at which a transfer can still be booked.</td></tr></tbody></table>

## How a booking runs

{% stepper %}
{% step %}

### Search

The traveller picks a route, direction, date and party. The system returns a price for each available vehicle, or a per-person fare for shared service.
{% endstep %}

{% step %}

### Prebook

The chosen fare is held while details are completed.
{% endstep %}

{% step %}

### Book

The booking confirms, with a cancellation quote attached from the route's policy.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**The booking cut-off is enforced.** A transfer whose pickup is closer than the route's cut-off — for example *under 24 hours* — is not bookable, even when a vehicle is free.
{% endhint %}

## Where to next

* **Author the contract behind it** → [Contracts](/console/contracts-and-onboarding/contracts.md)
* **Guided activities and excursions** → [Tours](/console/tours-transfers-and-flights/tours.md)
* **Group it with a stay and a flight** → [Trips](/console/tours-transfers-and-flights/trips.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/tours-transfers-and-flights/transfers.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.