> For the complete documentation index, see [llms.txt](https://manual.tourpaq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.tourpaq.com/booking/new-booking/circuit-bookings.md).

# Circuit Bookings

Create circuit bookings (multi-destination trips) in Tourpaq Office using multiple hotels and one-way transports. Includes prerequisites and example itinerary.

### Overview

Circuit bookings in **Tourpaq Office (BackOffice)** let you create a **multi-destination booking** (also called a **multi-hotel booking**) inside one booking.

Unlike a standard booking with one hotel and a return transport, a circuit booking can combine:

* Multiple hotels, potentially located in different resorts or even countries.
* Multiple transports, often **one-way flights**, to build a **multi-leg itinerary**.

***

### Purpose

* To provide greater flexibility in travel planning.
* To accommodate multi-destination trips under one booking record.
* To allow users to tailor customer journeys with varied hotels and transport legs.

***

### Preconditions (required setup)

* One-way transports must be enabled in the system.
* Custom hotel days must be enabled for hotels.
* Related price lists supporting custom hotel days and multiple one-way flights must be configured.
* Users should refer to:
  * [Price List Custom Hotel days Service](/price-list-custom-hotel-days-service.md) for hotel duration setup.
  * [Multiple one way flights bookings](/booking/new-booking/multiple-one-way-flights-bookings.md) for transport setup.

***

### How to create a circuit booking (workflow)

Use this flow when you need a **multi-leg itinerary** with **multiple hotel stays**.

{% stepper %}
{% step %}
**1. Create a new booking draft**

Start in [New Booking](/booking/new-booking/new-booking.md).

Set passengers first. Then build the itinerary.
{% endstep %}

{% step %}
**2. Add the first transport leg (one-way)**

Select the outbound **one-way transport** for the first destination.

Confirm dates and gateways. This sets the first leg of the route.
{% endstep %}

{% step %}
**3. Add the first hotel stay (custom hotel days)**

Select the hotel for destination 1.

Set the stay length using **custom hotel days**.
{% endstep %}

{% step %}
**4. Add the next transport leg + hotel stay (repeat)**

Add the “middle” one-way leg to the next destination.

Then add the next hotel stay with the correct nights.
{% endstep %}

{% step %}
**5. Add the final return leg and save**

Add the last one-way leg back to the home gateway.

Review the full itinerary. Then save the booking.
{% endstep %}
{% endstepper %}

### Best practices (avoid common mistakes)

* Build legs in **chronological order**.
* Check each leg’s **date and time** before you add the next.
* Confirm each hotel stay matches the intended **nights**.
* If you are rescheduling, copy passengers first. See [Copy Booking](/booking/new-booking/copy-booking.md).

***

### Key benefits

* Combine multiple hotels within a single booking.
* Manage hotels across different resorts or countries seamlessly.
* Use multiple one-way flights to match complex travel itineraries.

### Example itinerary (circuit booking)

<figure><img src="https://docs.tourpaq.com/assets/images/circuit-8d9b468c853f2ffb0e4a767d96942035.png" alt="Example circuit booking with two hotel stays and three one-way transport legs"><figcaption><p>Example: two hotels in different countries connected by one-way transports.</p></figcaption></figure>

* **Leg 1 (one-way transport):** Billund → Palma (Mallorca), 21.05.2020 09:15–11:15
* **Hotel stay 1 (custom hotel days):** 7 nights, 21–28 May
* **Leg 2 (one-way transport):** Palma (Mallorca) → Porto Santo, 28.05.2020 07:15–10:45
* **Hotel stay 2 (custom hotel days):** 7 nights, 28 May–4 June
* **Leg 3 (one-way transport):** Porto Santo → Billund, 04.06.2020 09:30–11:00

In this example, the booking includes two hotel stays in two countries.

The stays are connected by three one-way transports. Each transport leg must exist in Tourpaq.

### Ticket output (example)

<figure><img src="https://155167782-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4ho2ecpjkno5JvDRSja9%2Fuploads%2Fgit-blob-0a10b22c53d7c8da2aa1951dcadfa6fa1799219d%2Fimage%20(249).png?alt=media" alt="Example ticket layout for a circuit booking with multiple hotel stays and one-way transport legs"><figcaption><p>Example ticket for a circuit booking.</p></figcaption></figure>

### Related

* [New Booking](/booking/new-booking/new-booking.md)
* [Copy Booking](/booking/new-booking/copy-booking.md)
* [Moved Booking](/booking/new-booking/moved-booking.md)
* [Multiple one way flights bookings](/booking/new-booking/multiple-one-way-flights-bookings.md)
* [Booking for 2 One Ways](/booking/new-booking/booking-for-2-one-ways.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://manual.tourpaq.com/booking/new-booking/circuit-bookings.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.
