> 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/articles/creation-darticles-et-ses-particularites/creer-un-article/creer-un-article-de-type-compose.md).

# creer-un-article-de-type-compose

Quand l'article est de type composé, vous devez définir les différents articles qui le composent.

{% hint style="info" %}
Pour les articles de type composé, pack (ouvrage si gestion de chantiers), fabrication, assemblage, suite à la saisie des composants, le champ **Prix d'achat HT** est automatiquement mis à jour dans la fiche de l'article pour lequel vous avez défini les composants.

Vous devez indiquer le **prix de vente HT** de l'article de **type composé**. Les prix de ses composants seront alors ajustés pour arriver au prix de vente indiqué.

Vous pouvez cocher l'option de **mise à jour du prix de vente à partir du prix d'achat** pour un calcul automatique du prix de vente et vous pouvez également définir un coefficient. De la même façon, le prix des composants seront automatiquement ajustés pour arriver au prix de vente calculé.
{% endhint %}

{% hint style="warning" %}
Les composants d'un article de **type composé** ne s'affichent pas dans les pièces commerciales.

Si vous souhaitez que les composants soient affichés, vous devez créer un article de type "**Pack**".
{% 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/articles/creation-darticles-et-ses-particularites/creer-un-article/creer-un-article-de-type-compose.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.