> 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/stocks/regles-dentrees-sorties-de-stocks.md).

# regles-dentrees-sorties-de-stocks

Les entrées et sorties de stock sont soumises à des règles précises qui sont décrites ci-dessous.

Lors de vos contrôles sur les mouvements de stock et sur l'inventaire, vous pouvez vous référer à cette rubrique pour comprendre l'origine de chaque mouvement généré par le logiciel.

De manière générale, les mouvements de stock sont créés par :

1. Validation / dévalidation d'une pièce commerciale
2. Mouvement manuel à partir de la fiche article
3. Régularisation suite à un import en mise à jour du fichier article

{% hint style="info" %}
Seuls les articles gérés en stock sont soumis à ces règles.

Une pièce commerciale peut contenir à la fois des articles gérés en stock et non gérés en stock. (Les mouvements qui sont générés à la validation tiennent compte de ce paramètre pour chaque ligne)
{% 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/stocks/regles-dentrees-sorties-de-stocks.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.