> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/fr/go-to-market/details.md).

# Détails

La référence de ton opération commerciale : les champs, les états et les options de Devis, de Facturation des clients, de Tarifs et de ressources.

Ici, il n’y a pas d’étapes : vous découvrez ce qu’affiche chaque Écran, ce que signifient ses champs et quelles options possède chaque élément. Consultez-le lorsque vous avez besoin de la donnée exacte.

### Explorez les détails

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Paramètres des tarifs</strong></td><td>Les champs d’un Tarif : en-tête, niveaux de Marge et colonnes de chaque ligne de service.</td><td><a href="https://docs.plenit.com/fr/go-to-market/details/rate-card-parameters.md">Paramètres des Tarifs</a></td></tr><tr><td><strong>Détail de la Facturation</strong></td><td>Les colonnes de la liste des bons de livraison, le contenu du bon de livraison et les options de téléchargement.</td><td><a href="https://docs.plenit.com/fr/go-to-market/details/billing-detail.md">Détail de la Facturation</a></td></tr><tr><td><strong>Champs des Devis</strong></td><td>Les champs d’un Devis, ses états et les actions disponibles.</td><td><a href="https://docs.plenit.com/fr/go-to-market/details/quote-fields.md">Champs des Devis</a></td></tr><tr><td><strong>Catalogue de la documentation</strong></td><td>Les catégories disponibles, les types de matériel et le comportement de chaque carte.</td><td><a href="https://docs.plenit.com/fr/go-to-market/details/documentation-catalog.md">Catalogue de Documentation</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/fr/go-to-market/details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
