# Order History Report

### 🔎 Running the Report

To generate the Order History Report, the user only needs:

* **Document Number** – the unique identifier for the order.

No additional filters are required.

***

### 📋 Report Columns Explained

The report produces a **chronological list** of all steps taken on the document. The following fields are shown:

#### 📅 **Date**

* The exact date and time when the action occurred.

***

#### 🔖 **Sales Order Number**

* The internal OrderEazi sales order number.

***

#### 🌐 **External Order Number**

* The order reference provided by an external system or customer (if applicable).

***

#### 🏷️ **Reservation Number**

* The reservation number linked to the order, used for stock allocation.

***

#### 🧾 **Picking Slip Barcode**

* The barcode associated with the picking slip for the order.
* This can be scanned to track picking activity.

***

#### 📦 **Delivery Note Number**

* The delivery note linked to the order once it has been prepared for dispatch.

***

#### ⚡ **Action**

* The action that was performed on the order (e.g., order created, stock reserved, picking started, dispatched).

***

#### 👤 **Actioning User**

* The user who performed the action.
* Provides accountability and a clear audit trail.

***

### ✅ Why Use the Order History Report?

* **Audit Trail**: View every step of an order from creation to delivery.
* **Accountability**: See which users took which actions.
* **Customer Support**: Quickly answer customer questions about where an order is in the process.
* **Problem Solving**: Identify delays or errors by reviewing the history of actions.


---

# Agent Instructions: 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:

```
GET https://support.ordereazi.com/inventory-features/reports/order-history-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.