> 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/doc-pour-les-teams-producteurs-collaboration-avec-les-revendeurs-et-apporteurs-daffaires.md).

# Document for Producer teams: Collaboration with Resellers and Business Introducers

**1. Definition of Roles:**

* **Producer**: Team that provides the initial product or service. The producer is responsible for the creation, quality proposed activities
* **Reseller**: Commercial partner who purchases products or services from the producer to resell them directly to end customers. The reseller may use its own distribution channels and is responsible for collection.
* **Business introducer**: Contact person who recommends or directs potential customers to the producer without necessarily managing the sale or collection. The business referrer may receive a commission or other type of remuneration for their recommendation.

***

**2. Collaboration Modes:**

A partner can combine the roles of reseller and business provider. **The distinction is mainly made by the method of collection.**

* **Reseller Mode**:
  * If the partner collects directly from the end customer, he acts as a reseller.
  * For counter sales: The reseller must use a reservation module from their own team.
  * For online sales: The reseller must connect a payment solution to their own Team, such as Stripe. The costs associated with online sales (billing by Yoplanning and Stripe) are borne by the reseller.
  * If a reservation is made at the counter without going through online sales, no fees or commissions due to Yoplanning are applied.
* **Business Provider Mode**:
  * If the customer is a business provider, collection from the end customer is managed by the producer structure.
  * The producer can provide a reservation module for his own Team to the business provider.
  * The invoicing conditions for the Yoplanning service are identical to those applied for sales on the producer's site.

***

**3. Concrete example** :

A hotel can sell directly at its counter via its reservation module. For online sales, the hotel has two options:

* Connect a payment system to your own team to directly manage sales.
* Integrate the reservation module provided by the producer and delegate payment management.

***

**Note**: For structures collaborating with several producers, it is recommended to collect services directly to allow the creation of a common basket, thus facilitating the management of transactions.

***

**Conclusion**: Whether you are a producer, reseller or business provider, it is essential to understand and clearly define the terms of collaboration to ensure effective distribution of products or services. This documentation aims to clarify these roles and modalities for successful collaboration.


---

# 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/doc-pour-les-teams-producteurs-collaboration-avec-les-revendeurs-et-apporteurs-daffaires.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.