> 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/gestion-des-revendeurs-et-apporteurs-daffaires/gestion-des-revendeurs-et-apporteurs-daffaires-pour-les-groupement.md). # Management of Resellers and Business Introducers for Groups This document is intended for groups to enable simplified collective management of their resellers and business providers in Yoplanning. The goal is to clearly organize processes according to legal structures and business needs, thus facilitating the management of orders and reservations within the group. {% content-ref url="" %} {% endcontent-ref %} *** ### 1. Resellers Resellers purchase services directly from producers and are therefore invoiced by the latter. There are two main cases: #### Case 1: Local Reseller (single-site) * The reseller wishes to resell **a single structure**. * Creation of a **single reseller** for this specific site. * The producer invites this reseller via his unique ID. * The reseller obtains a reservation module dedicated to his activity. * **Billing:** direct from the producer to this reseller. #### Benefits * Simplicity in management. * Clear for accounts and accounting. *** ### 2. Multi-site resellers (national or centralized reseller) When the reseller wishes to resell several structures within a single legal entity: * Create **a single reseller**. * All sites invite the same reseller ID. * The reseller will have two choices for its reservation modules: **Option A: Module per site** (in the reseller's team) * Create a booking module per site. * Simple and segmented management by establishment. **Option B: Multi-site module** * Create a single module including all products. * Enabled the filter by provider at the top of the module, allowing customers to easily select the site before booking. #### Benefits * Centralization of orders. * Simplified access to data for the national reseller. * Flexibility in business management. *** ### 3. Business introducers Business introducers do not pay directly for services, but bring clients in exchange for a commission. Management also depends on the number of organizations represented. #### Simple case: single-structure * The business provider wishes to book only with a single structure. * A specific reservation module is created in his name. * He receives a unique link allowing him to make his reservations. #### Benefits * Easy to manage. * Clear commissioning per site. #### Multi-site cases * A provider wishes to book services for several structures through a single module. * **Solution: Create a multi-site group.** * That is, a specific team named after the group that will bring together all the offers. This team will need to be a reseller for all the members of the group. **Mandatory conditions** * The group must be able to collect **on behalf of all member structures**. * The single module will have a filter by provider allowing you to choose the site before ordering. * Payment is centralized at the group level. #### Benefits * Simplicity for the business provider. * Centralization of reservation management. *** ### 4. Key criterion: legal structures * If the resellers have different legal structures, create one reseller per legal entity. * If it is a single centralized legal entity, create a single reseller for all the sites concerned. *** ### 5. Important reminder about modules * Reseller: module in the reseller's team (collects and will be billed). * Business developer: module in the producer or group team (the producer or group collects). *** This documentation clearly covers the essential cases for effectively managing resellers and business providers in Yoplanning. --- # 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/gestion-des-revendeurs-et-apporteurs-daffaires/gestion-des-revendeurs-et-apporteurs-daffaires-pour-les-groupement.md?ask=&goal= ``` `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.