> 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/tarifs-gestion-et-parametrage/module-marketing-dans-yoplanning/gestion-des-allotements-module-marketing.md).

# Allotment Management – ​​Marketing Module

#### What is the purpose of this feature?

Allotment management allows you to **limit the number of available slots for a given reseller** over a defined period. It's a useful sales management tool for strategically allocating your inventory between direct sales and resale.

> This feature is only accessible if you have activated the **marketing module** via Yoplanning support.

***

#### How do I access the feature?

1. Log in to Yoplanning.pro.
2. In the left menu, go to **Administration > Configuration**.
3. In the **Booking Module** section, open **Marketing Rules**.
4. Click on **Add a rule**.
5. Choose the type **Resale Stock**.

***

#### Configuration steps

**1. General Information**

* **Name**: Give your rule an explicit name (e.g., "Club Med reseller limit – winter 2025").
* **Type**: Select "Resale Stock".
* **Dates**: period during which the rule applies. These are **reservation** dates, not session dates.

**2. Relevant Reseller**

* **Reseller**: Choose a reseller previously created in your team.

**3. Change in Inventory**

* **Resale stock**: define the percentage of total capacity that the reseller will be able to see and sell.

  > **Example:** `-50%` on a session of 10 places → the reseller only sees 5 places available.

**4. Targeting (Sessions & Products)**

* **Session tag** *(optional)*: target specific periods via a tag (e.g., "high season").
* **Product** *(optional)*: select a specific product.
* **Product tag** *(optional)*: apply the rule to an entire product family (e.g., "Group ski lessons").

> ⚠️ If you combine a session tag **and** a product, the rule applies **only** to sessions of the product in question that carry this tag.

***

**5. Filling Conditions**\*\*\*(optional — advanced feature)\*\*\*

This section allows you to **automatically enable or disable the rule based on the session's fill rate**. It is optional: if you don't need it, leave these fields empty.

There are two typical use cases, and depending on your objective, you will use **only one of the two fields**.

***

**Case 1 — You want to open all remaining places when the session is not filling up properly**

\*Objective: to increase occupancy during the off-season, or for sessions with low sales.

When a session is approaching saturation from the bottom (there are still many places left), you want the reseller to be able to access **all available places** to help you sell.

→ Use the field **"Remaining seats — minimum (%)"**

This field defines the threshold **below which the rule no longer applies**. In other words: when there are too many places left (session not full), the restriction is lifted.

> **Concrete example:** You have a session with 10 places. You enter `80%` in the "minimum" field. As long as **more than 80% of the places** remain (i.e., more than 8 places available), the rule applies normally: the reseller only sees part of the available space. As soon as the session is more than 20% full (**fewer than 8 places** remain), the rule is deactivated: the reseller sees all the remaining places.
>
> *In practice: you've sold 2 tickets, the reseller only sees part of it. You've sold 3 tickets — the threshold has been crossed — the reseller sees everything that remains.*

***

**Case 2 — You want to reserve the last few seats for your own customers**

*Objective: to protect your stock during peak season, or during your most popular sessions.*

When a session is almost full, you no longer want the reseller to be able to sell the last few places — you prefer to keep them for your direct sale.

→ Use the field **"Remaining seats — maximum (%)"**

This field defines the threshold **above which the rule no longer applies**. In other words: when there are almost no spaces left, access to the reseller is closed.

> **Concrete example:** You have a session with 10 places. You enter `20%` in the "maximum" field. As long as **more than 20% of the places** remain (i.e., more than 2 places available), the rule applies normally. As soon as **only 2 places or fewer** remain, the rule is deactivated: the reseller no longer sees any availability.
>
> *In practice: you have sold 8 tickets — the limit has been reached — the reseller can no longer sell the last 2 tickets.*

***

**Summary of the two fields**

| Field                              | What he does                                                                    | Typical use case                                                    |
| ---------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Remaining places — minimum (%)** | Disable the rule when the session is not very full (too many places remaining). | Low season: open all seats to maximize occupancy                    |
| **Remaining places — maximum (%)** | Disable the rule when the session is almost full (few spaces remaining).        | High season: reserve the last remaining places through direct sales |

> 💡 In the vast majority of cases, you only use **one** of the two fields at a time. Use both only if you want a specific activation window (e.g., the rule only applies when the fill rate is between 20% and 80%).

***

#### Usage tips

* Use **session tags** to manage seasonality (high season, low season, school holidays…).
* If you are a beginner, **leave the "fill" fields empty**: the rule will apply uniformly over the entire duration of the session.
* Create a separate rule for each strategic reseller.

***

#### Common problems and solutions

| Issue                                         | Solution                                                                                                   |
| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| The reseller sees the full capacity           | Check that the rule is active and that the conditions (dates, product, tag) are met.                       |
| The rule does not apply                       | Check the "places remaining" fields: an incorrectly configured threshold can permanently disable the rule. |
| The rule does not target the correct sessions | Check the session and product tags.                                                                        |

***

To activate the marketing module, contact <support@yoplanning.com>.


---

# 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/tarifs-gestion-et-parametrage/module-marketing-dans-yoplanning/gestion-des-allotements-module-marketing.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.
