> For the complete documentation index, see [llms.txt](https://docs.dailybiz.com/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dailybiz.com/index/gestion-commerciale-bis/fichiers/clients/vision-360/utiliser-la-vision-360/menu-deroulant-360/historique-des-ventes-et-achats.md).
# historique-des-ventes-et-achats
1. Cliquez sur la ligne du client pour lequel vous voulez consulter l'historique des ventes et achats.
2. Cliquez sur 
ou sur le pictogramme .png?alt=media) situé en haut à droite de la fenêtre.
3. Cliquez sur l'option **Historique des ventes et achats**.
4. Choisissez les critères d'affichage : période et code article si vous le souhaitez.
{% hint style="info" %}
Dans la popup qui s'affiche, le filtre est par défaut positionné sur la période du mois en cours et "**tous**" comme code article.
{% endhint %}
5\. Cliquez sur .JPG?alt=media).
{% hint style="success" %}
Notez que vous pouvez personnaliser l'affichage des données en incluant ou excluant des données que vous souhaitez ou ne souhaitez pas visualiser. Pour cela cliquez sur .PNG?alt=media)
.
{% endhint %}
---
# 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.dailybiz.com/index/gestion-commerciale-bis/fichiers/clients/vision-360/utiliser-la-vision-360/menu-deroulant-360/historique-des-ventes-et-achats.md?ask=&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.