> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/sales-order-modification-history.md).
# Sales Order Modification History
**YouTube:** [How to Track Sales Order Modification History?](https://www.youtube.com/watch?v=VEu3xnL3drg)
## How to Track Sales Order Modification History?
In this tutorial, we’ll learn how to **track and review the complete modification history of a Sale Order** in **Logic ERP**.
***
### **Open Sale Order Modification History**
* Navigate to the **Sale Order Modification History** module.
* Select the **Sale Order** you want to review.
* Click **Refresh.**
* If **no data appears**, it means the selected Sale Order **has not been modified yet**.
***
### **Modify the Sale Order**
* Go to the **Sale Order Module**.
* Select and open the required **Sale Order** for editing.
#### Modify Header Details
* Change fields such as:
* **Party Order Number**
* **Customer Name**
* **Agent Name**
#### Modify Item Details
* Update:
* **Quantity and CD% of the first item**
* **Quantity of the second item**
* After making the changes, **Save the Sale Order**.
***
### **Review the Modification History**
* Return to the **Sale Order Modification History** module.
* Select the same Sale Order and click **Refresh**.
#### Header-Level Changes
* The **upper section** displays **header-level modifications**.
* It shows a **comparison between original and modified values**.
* Modified fields are **highlighted in pink** for easy identification.
#### Item-Level Changes
* The **lower section** displays **item-level changes**.
* Similar to the header section, it shows a **side-by-side comparison** of old and updated values.
***
### **Modify the Sale Order Again**
* Open the **Sale Order** once more.
* This time, change **only the quantity of the second item**.
* Save the document.
***
### **Verify Multiple Modification Records**
* Go back to the **Sale Order Modification History** window.
* Select the same Sale Order and click **Refresh**.
You will now see **two separate entries** in the modification history.
* Each entry represents **a different modification stage**.
* The **latest entry** reflects the most recent changes made to the Sale Order.
***
### **Conclusion**
The **Sale Order Modification History** module maintains a **complete audit trail of all changes** made to a Sale Order, helping users easily track revisions and identify modifications over time.
---
# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/sales-order-modification-history.md?ask=&goal=
```
`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.