> 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/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-septembre-2025.md).

# Mise à jour YoPlanning - Septembre 2025

September brings powerful tools for marketing and managing your sessions. The focus has been on upselling and ensuring the reliability of your email campaigns.

### 🛍️ Marketing & Sales

#### Shopping cart rules (Upselling)

You can now create smart cart rules to encourage your customers to book more.

* **The concept:** "If the user has a Surf lesson in their basket, then they benefit from 50% off wetsuit rental."
* **Objective:** Increase the average order value by offering automatic discounts based on the content of the reservation.

#### Initial billing history

To strengthen confidence in the resale system and order modifications, YoPlanning now stores the PDF of the **original invoice** for each online order.

* In case of dispute or subsequent modification, you can view the exact status of the order at the time of purchase in the history.

### 📅 Session & Staff Management

#### Session view improvement

* **Number of participants:** The participant counter is now visible directly in the session details, saving you from having to navigate through lists to see the fill level.
* **Automatic cleaning:** To keep your schedule light and efficient, the system now automatically deletes "empty" sessions (without orders, participants or fees) older than 6 months.

#### Fees & Bylaws

* **Advanced Filters:** Added a filter by "Staff Status" in the member list, particularly useful for teams managing instructors with different types of contracts or fees.
* **Guided configuration:** The fee configuration interface has been simplified with numbered icons to indicate the order of steps to follow.

### 🚀 Performance & Reliability

#### Ultra-reliable email sending

We migrated the email sending system to "Google Tasks".

* **In practice:** If a sending server encounters a temporary error, the email is automatically queued and resent later. This ensures that your customers always receive their confirmations and reminders.

#### Mapping & Location

* **Google Maps:** Migration to the latest Google Maps APIs for better display performance and removal of warnings in the console.

### 📱 Ergonomics & Interface

* **Tag Filters:** In your product lists (BE and resellers), you can now filter by **Product Tag**, making it easier to manage large catalogs.
* **Wording:** For clarity, the term "Repeat Type: Individual" simply becomes "Repeat: No" in session addition.
* **Participant Interface:** The participant list has been revised to display the order status on the left and the product on the right, improving quick reading in the field.


---

# 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/information-de-mise-a-jour/rapport-de-maj-2025/mise-a-jour-yoplanning-septembre-2025.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.