> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/school-of-erp/sales-order-process.md).

# Sales Order Process

**Sales Order Lifecycle**

The sales order process involves the receipt and management of customer orders. This process starts when a customer places an order and ends with the successful delivery of goods or services. In an ERP system, sales orders are tracked from creation through to fulfillment, providing visibility over each stage of the process.

**Steps in the Sales Order Lifecycle:**

1. **Order Creation:** Sales orders are generated either through manual entry or an automated system like eCommerce.
2. **Order Validation:** The system checks that sufficient stock is available, prices are correct, and any discounts or promotions are applied.
3. **Order Confirmation:** Once validated, the sales order is confirmed and passed to fulfillment.

<figure><img src="/files/ucyCNFwEn6TJWJzFzd66" alt=""><figcaption><p>Sales Order creation in Pakk</p></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.pakk.io/school-of-erp/sales-order-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.