> 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.md).

# Sale Return

- [Prompt in Sale Return if Lot/Item Sale is More Than Defined Months/Days](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/prompt-in-sale-return-if-lot-item-sale-is-more-than-defined-months-days.md)
- [Prompt for Bill Adjustment in Sale Return](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/prompt-for-bill-adjustment-in-sale-return.md)
- [Authorization in case of Sale Return Entry](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/authorization-in-case-of-sale-return-entry.md)
- [Do Not allow Blank Challan No. in case of Sale Return](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/do-not-allow-blank-challan-no.-in-case-of-sale-return.md)
- [Prompt Original Sale Details in case of Sale Return](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/prompt-original-sale-details-in-case-of-sale-return.md)
- [Do not filter for Customer in Sale Return History](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/do-not-filter-for-customer-in-sale-return-history.md)
- [Prompt Sale History for each Item in Sale Return](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)
- [Credit Note Validity (Days)](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/credit-note-validity-days.md)
- [Allow Sale Return after Lot Expiry Date(days)](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/allow-sale-return-after-lot-expiry-date-days.md)
- [Pick Rate From Last Sale Bill in case of Sale Return](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/pick-rate-from-last-sale-bill-in-case-of-sale-return.md)
- [Pick Taxes from Sale History in case of Sale Return](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/pick-taxes-from-sale-history-in-case-of-sale-return.md)
- [Do not Link Sale Return with Sale through Sale History](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/do-not-link-sale-return-with-sale-through-sale-history.md)
- [Allow Credit Note Redemption Across Branches](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return/allow-credit-note-redemption-across-branches.md)


---

# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/user-access/logic-global-admin/sale-return.md?ask=<question>&goal=<user_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.
