> 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/sales-management/the-orders.md).
# The Orders
## Context:
Once the quote has been approved by AMB & ST, the order for the new manager is then placed with MASOCIETE.
In addition, another new order has been received for its new premises. It includes:
* A corner sofa
* 4 armchairs
* A wall-mounted TV stand
This order will also be prepared and shipped to AMB & ST.
## Implementation in Simax
### Creation of an order from a quote
Once AMB & ST has approved the quote. In the quote list, simply click on **\[\[create order]].**
The quote lines are included in the order and saved.
## Creation of an order
To create an order, click on **Sales > Order > Create order.**
Fill in the customer, contact, and order lines.
For the command line, click on **\[\[New]]** in **\[Amount]**, then choose the item name and quantity, and the rest will be filled in automatically.
And **\[\[Save]]**.
Both orders are visible in **Sales > Order > Orders**.
## Creation of branch order
Cf. Documentation ERP\_25\_Multi-company management
---
# 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/sales-management/the-orders.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.
