> 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/prix-par-participant-vs-prix-par-session.md).

# Price per Participant vs Price per Session

**Introduction :**

When configuring activities on Yoplanning, a crucial question arises: should we favor a price per participant or a price per session? This decision impacts not only the pricing structure, but also the management and organization of your activities. This article aims to shed light on the fundamental differences between these two approaches and help you choose the one best suited to your offering.

**1. Price per Participant:**

Pricing per participant is often used for activities where individuals or small groups can register independently. Each participant pays for their own place. This approach is ideal for:

* Regular activities or classes (yoga, workshops, group classes).
* Events where the number of participants varies.
* Encourage the inclusion of individual participants or small groups.

**Benefits :**

* Increased flexibility for customers.
* Allows you to fill sessions with a variable number of participants.
* Simplified management of individual payments.

**2. Price per Session:**

The price per session is suitable for activities booked as a complete unit, often by groups or for private events. Here, the price is set for the entire session, regardless of the number of participants. This method is perfect for:

* Group events or activities (team-building, private parties).
* Sessions that require full reservation of space or equipment.
* When the activity requires the exclusive attention of a supervisor.

**Note**: you can vary the price depending on the number of people anyway, see the dedicated article [by clicking here](/en/yoplanning-academy/yoplanning-parametrage/tarifs-gestion-et-parametrage/definir-un-tarif-par-session-pour-les-cours-prives-dans-yoplanning.pro.md)

**Benefits :**

* Simplifies planning and logistics for groups.
* Offers a more personalized and exclusive experience.

**3. Choosing the Right Strategy**

Your choice will depend on several factors:

* **Nature of the Activity**: Certain activities lend themselves better to one model than the other.
* **Target Customers**: Consider your customers' preferences and booking behavior.
* **Resource Management**: Evaluate how each option affects the management of your resources and staff.

**Conclusion :**

Yoplanning offers the flexibility to choose between a price per participant or per session, allowing you to optimize your offer according to your specific needs. Take the time to evaluate your activities, your target market and your operational capabilities to make the wisest choice.


---

# 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/prix-par-participant-vs-prix-par-session.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.