> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/les-forfaits-prepayes-bons-cadeaux-cheques-cadeaux/creer-un-pass-multi-activites.md).

# Create a Multi-Activity Pass

A **Multi-Activity Pass** is a single product, sold at a fixed price, that grants access to several activities of the customer's choice. From the customer's perspective, it's a single purchase; from a configuration standpoint, the Pass relies on a system of **gift vouchers** automatically generated upon purchase.

### Operating principle

When a customer buys a Pass, the order creates **several separate gift vouchers**, one per **activity range**. Each range groups activities of a comparable price level and receives a dedicated value (for example: range 1 = €30, range 2 = €60, range 3 = €90).

Each gift voucher is valid only on the **list of products** associated with its range. The customer therefore consumes one activity per range, within the limits of eligible products.

#### Why gift vouchers rather than a balance to be deducted?

The gift voucher **decorates the value**: it entitles the holder to an activity from the range, regardless of the actual price of that activity at the time of booking.

|           | Gift voucher                                        | Balance/check to be deducted               |
| --------- | --------------------------------------------------- | ------------------------------------------ |
| Logic     | Right to one activity within the range, fixed price | Calculation of an amount in euros          |
| Remainder | None (single use per range)                         | Risk of unspent balance and refund request |

This mechanism avoids leftovers and guarantees a clear framework: one activity per range, without reimbursement for unconsumed items.

### Prerequisites

All Pass products must be in **the same team** — the one that will sell the Passes and collect payments. That's the only condition.

### Step-by-step configuration

#### 1. Define the ranges

Group the activities by price level. Each price range will correspond to a gift voucher, with:

* a **value** (the amount of the voucher),
* a **list of eligible products** (the activities in the range).

#### 2. Create the right gifts

Create **one gift voucher per product range**. For each voucher:

* Enter its value,
* Attach the list of eligible products from the range.

> This step only needs to be done once: the product list remains valid for all future sales (only to be updated if the catalogue changes).

#### 3. Build the "Pass" product

Create the fixed-price Pass product that your customers will see. Upon purchase, the order must send the **fixed gift vouchers** corresponding to the ranges (the same ones for each sale).

### For sale

When a customer buys the Pass:

* The order generates one gift voucher per product range.
* Each good product has a **code**.
* These codes are communicated to the customer (for example via a PDF summary reminding them how the Pass works and the codes to use).

### For consumption

When booking an activity, the customer enters the code corresponding to the product range. The validity of the code is automatically verified on the chosen product:

* If the product is part of the voucher's range, the reservation is confirmed.
* Otherwise, the code is rejected.

Each code is for **single use only**.

### Best practices

* **Clear framework for the customer.** Indicate in your terms of sale that this is an activity per range, without refund or carryover of unused items.
* **Test before launch.** Conduct a full-scale test on one or two product lines with a few real products before the commercial launch.
* **Keep the catalogue up to date.** If an activity changes price or range, update the products linked to the relevant gift vouchers.


---

# 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://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/les-forfaits-prepayes-bons-cadeaux-cheques-cadeaux/creer-un-pass-multi-activites.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.