> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/documentation-simax-anglais/functional/purchase/simple-purchasing-process.md).

# Simple purchasing process

## Context

As part of supply management, the company begins by creating the item entitled “Carton” and then registers the supplier CartonPACK in the system. A supplier order is then created and automatically appears in the list of unsent supplier orders.

After the information has been checked or modified, the order is registered and sent to the supplier by email. Once sent, it disappears from the list of unsent orders.

Upon receipt of the cartons, the order is retrieved, then received by selecting the receiving manager Barbier Bruno and validating it. The received items are added to the receiving slip. The order then appears in the list of Receiving Slips Awaiting Invoice, awaiting accounting processing.

## Implementation in SIMAX

### Prerequisite: creation of the item “Carton”

To create an article, go to **Files > Item > Items and click \[\[New]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2FyWcNrfNb4AiO9Rsvt3yE%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20183058.png?alt=media&amp;token=657d4d72-169b-4f37-832a-3bf4a69039f8" alt=""><figcaption></figcaption></figure>

### Supplier creation

To create the supplier **CartonPACK**, go to **Purchase > Supplier > Suppliers** and click on **\[\[New]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2Fh3lW8cL9LFno7sOJwak9%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20183727.png?alt=media&amp;token=b538ef39-53c6-4b54-abb9-a0702a2c4ca4" alt=""><figcaption></figcaption></figure>

and **Save.**

### Supplier order

We go directly to the list of unsent supplier orders. We can view the order details by double-clicking on the supplier order line. If there are any changes, they must be saved.

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2Fns30LA6u1XP2MxjTAJD7%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20184102.png?alt=media&amp;token=75871132-b321-4cd7-8753-ad260b0de77b" alt=""><figcaption></figcaption></figure>

Next, send the order by clicking on **\[\[Send supplier order by email]].**

When sending the order by email, it is sent directly to the email address entered in the supplier's file.

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2Fhs7rRvjSrFfbwHxx8akV%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20184248.png?alt=media&amp;token=9dd78e9b-13a3-4844-9420-4e847fee6407" alt=""><figcaption></figcaption></figure>

It will no longer be visible in the list of unsent supplier orders.

{% hint style="success" %}
You can send multiple orders by email in bulk by selecting them and then clicking **\[\[Send supplier order]].**
{% endhint %}

### Receipt of supplier order

The supplier order can be viewed in **Purchase > Orders > Supplier Orders.**

To receive the supplier order, select the relevant supplier order and click on **\[\[receive]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2F5C9LXryVcf4qGfrQkCKB%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20184503.png?alt=media&amp;token=49dfcb5a-df6a-4002-bc5d-8f3c0db01293" alt=""><figcaption></figcaption></figure>

Let's choose who will receive the order and **\[\[ok]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2FhkIF7EZm4H9LPOzMHZZH%2Fimage.png?alt=media&amp;token=f7948f68-96e6-4f3b-87c0-7014392615e0" alt=""><figcaption></figcaption></figure>

And let's finish by **\[\[Confirm reception]].**

<figure><img src="https://3774355255-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzEcRYDc0Yd5qgDsaJt5p%2Fuploads%2FlDCXJlHZBHTYpfYZbndf%2FCapture%20d%E2%80%99%C3%A9cran%202026-03-05%20184747.png?alt=media&amp;token=9c531b34-0729-4b94-93a7-3ab5098baca9" alt=""><figcaption></figcaption></figure>

On the receipt form, you must fill in the “Items received” list if it is not pre-filled. You can choose how to fill it in under **Settings > Plug-ins and options**, **\[\[logistics]]**, **\[Use of barcodes]**, **\[on receipt].**

The supplier order is currently visible in **Purchase > Supplier Invoice > Delivery receipt waiting for Invoice.**

#### Product Control

#### Quality control

#### Supplier Quality Control


---

# 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://doc.simax.fr/documentation-simax-anglais/functional/purchase/simple-purchasing-process.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.
