> 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/packages.md). # Packages A **package** sells two or more travel services — a hotel stay, a transfer, a tour, a flight — as one booking with one inclusive price. The traveller sees a single total and a single confirmation; you see every service as its own item, each with its own dates, policy and status. {% hint style="info" %} **A package is not a trip.** A trip links bookings that were made separately and keep their own prices. A package is one contract from the start: one price, one confirmation, one booking reference. [Trips](/console/tours-transfers-and-flights/trips.md) explains the grouping model. {% endhint %} ## What a package gives you * **One inclusive price.** *Hotel Sunrise, five nights + airport transfer + return charter flight* confirms as one total — with a per-item breakdown you can always inspect. * **All or nothing at confirmation.** A package only confirms when every service in it is secured. If one service cannot be committed — the last two charter seats sell out mid-booking — nothing is booked and nothing is charged. * **Item-level control after confirmation.** Each service inside the package is an item you can view, quote and cancel individually. ## How a package is sold Packages are composed and sold in three places: in the Console by your own team, through your connected sales channels, and through the partner API. The shape is the same everywhere — the seller picks live services, receives one combined offer with an expiry, revalidates it, and confirms. Every price in the offer is re-checked at confirmation; if anything changed, the seller sees the new total before any commitment is made. In the Console, **Bookings → Compose a package** walks a desk through it in four steps: the party, the services, the combined offer, and the confirmation. The screen shows the composition rules live — how many services, how many kinds, one currency, who is travelling on what — so the desk knows what a package still needs rather than finding out from a rejection. A basket in progress is saved as you work and can be picked up again later. The combined offer step shows the pre-contractual information in full, exactly as it will be frozen into the booking. Where the market requires the traveller to receive it on a durable medium, the desk sends or downloads it from that screen and the platform records the channel, the recipient and the moment — the evidence the confirmation then carries. {% hint style="warning" %} **A price movement always stops the flow.** However small the change, the desk is shown the old total and the new one and chooses: take the new price, change the basket, or discard. Nothing is confirmed on a price the seller has not seen. {% endhint %} In the Console, a package appears in **Bookings** like any other booking, marked as a package with its item count. The detail page shows the inclusive total, the current active total, and one card per item. ## Cancelling part of a package Cancellation is quote-led: select the items to cancel, review the cancellation quote, then confirm. * **Each item is charged by its own policy.** A free-cancellation hotel and a non-refundable flight in the same package keep their own terms; the quote sums them honestly. * **Remaining items keep their prices.** Cancelling the transfer never reprices the hotel or the flight. What survives stays exactly as booked. * **The booking reflects the outcome.** A partly cancelled package shows as partially cancelled with an updated active total; cancelling every item cancels the package. {% hint style="warning" %} **Nothing is cancelled without a quote.** The penalty and refund are computed and shown before the destructive step — there is no blind cancel for packages. {% endhint %} ## The organiser and the traveller Every package has an **organiser** — the organisation whose offer combined the services and who answers to the traveller for the whole package. Adrasis freezes the organiser's details, the service list, the price and the applicable disclosure into the booking at confirmation, so the evidence of what was sold, by whom, and under which terms is permanent. Before selling packages into a market that regulates package travel, complete your **package compliance profile** on the organisation page:
You configureThe platform freezes into every package
Jurisdiction and regimeWhich market's package rules the sale is classified under.
Standard information form versionThe approved disclosure form referenced by every offer and booking.
Complaint contactThe email — and optionally phone and web address — travellers use to reach you.
Insolvency protectionThe protection provider and reference, or an explicit record that none is configured.
Delivery requirementWhether confirmation requires evidence that the disclosure reached the traveller on a durable medium.
Updating the profile creates a new version for future sales; the evidence frozen into already-confirmed bookings never changes. {% hint style="warning" %} **The disclosure content is yours.** Adrasis records and freezes the evidence; the legal wording, the applicable form and the decision that a sale is a regulated package remain the organiser's responsibility. {% endhint %} ## What a package is not * **It is not a trip.** A trip groups independent bookings after the fact; a package is one contract from the first offer. A package booking can itself be linked into a trip. * **It is not repriced when it shrinks.** Partial cancellation never recalculates the surviving items. * **It does not mix currencies or suppliers.** One package sells one provider's services in one currency. ## Where to next * **Grouping independent bookings instead** → [Trips](/console/tours-transfers-and-flights/trips.md) * **The services a package can contain** → [Tours, transfers and flights](/console/tours-transfers-and-flights/tours-transfers-flights.md) * **Charter seat blocks a package can sell** → [Flights](/console/tours-transfers-and-flights/flights.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/packages.md?ask=&goal= ``` `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.