> 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/user-access/logic-global-admin/sale-return/prompt-sale-history-for-each-item-in-sale-return.md).
# Prompt Sale History for each Item in Sale Return
**YouTube:** [How to Globally Enable Item wise Sale History Prompt in Sale Return?](https://www.youtube.com/watch?v=hsnJ4CfKHqA)
## How to Globally Enable Item wise Sale History Prompt in Sale Return?
This tutorial explains how to activate the feature that prompts the **original sale history** for each item during a **Sale Return**. This function helps ensure accurate return processing by referencing previous sales.
***
### **Enable the Feature in Logic Admin**
* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Go to the **Sale Return Settings** section.
* Locate and enable the option:\
\&#xNAN;**“Prompt Sale History for each Item in Sale Return”**.
* *Note: This setting must be applied via Logic Admin to enforce it across all billing series and branches.*
* Click **Save** to apply the changes.
* Restart the software to activate the feature.
***
**Optional: Enable at Series Level (If needed)**
* You can also enable this option individually in **Sale Voucher Configuration** for specific billing series if not applying globally.
***
### **Perform a Sale Return Entry**
* Open the **Sale Return Voucher** screen.
* Select an **item and its corresponding lot number**.
* A **Sale History** window will automatically appear.
* The window displays all **past sale bills** for the selected item.
* Select the specific bill against which the **return is to be processed**.
* This ensures the return is linked to the correct original transaction.
***
### **Benefits**
* Ensures **accuracy** in returns.
* Minimizes **manual errors**.
* Improves **traceability** of returned items.
---
# 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/user-access/logic-global-admin/sale-return/prompt-sale-history-for-each-item-in-sale-return.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.