> 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-juillet-2025.md).

# Mise à jour Yoplanning - Juillet 2025

July saw significant optimization of our online booking engine (VEL) and a series of usability improvements, particularly for mobile users. Here's what you need to know about the new features.

### 🚀 Online Sales & Reservations (VEL)

#### Real-time inventory optimization

We have refined the availability management algorithm. Now, the calculation of the number of available online slots takes into account the current stock of available resources, as well as the potential number of sessions generated by the virtual platform. This drastically reduces the risk of overbooking for complex activities.

#### Intelligent disaggregation management

For sessions with price aggregation, the system now handles disaggregation based on dates and prices more effectively. This ensures greater consistency between prices displayed online and marketing rules applied to the order.

#### Improvements to the Booking Engine (BE)

* **Availability Filters:** Fixed a bug in the search (P1) which could display inconsistent results due to removed availabilities.
* **Securing promo codes:** The system now systematically ignores deleted promo codes to prevent any fraudulent or erroneous use.

### 📅 Planning & Resources

#### Display and ergonomics

* **Unavailability:** Fixed a display bug on the schedule where some unavailability entries could hide sessions or be incorrectly positioned.
* **Conflict management:** Improved detection of overlaps when moving sessions or modifying anonymous staff.
* **Planning Notes:** Fixed a navigation bug that could occur when planning notes were displayed on homepage loading.

### 📱 Mobile Experience & Design

#### Redesign of mobile interfaces

We have made numerous visual improvements to the mobile and tablet versions:

* **Popup Design:** The list windows have been redesigned to be more readable on small screens.
* **Interactions:** Fixed the left/right swipe issue that could interfere with navigation on the schedule.
* **Social Login:** The login buttons via Google and Facebook have been fixed to ensure a smooth experience on iOS and Android apps.

#### Access rights

For increased security and clarity, we have restricted access to certain sensitive data. For example, exporting sessions and staff schedules is now only possible for team administrators.

### 📊 Administration & Exports

#### New export fields

To facilitate your accounting and operational tracking, we have added the **"Reservation Module"** column to the Excel export of orders. This allows you to identify at a glance the origin of each sale (Office, Online, API, etc.).

Do you have questions about these new features? Feel free to consult our [help center](https://www.google.com/search?q=https://docs.yoplanning.support) or contact our support team.


---

# 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-juillet-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.