> 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/inventory/receipt-register/receipt-register-configuration/prompt-for-godown-at-the-doc-end.md).
# Prompt for Godown at the Doc End
**YouTube:** [How to Prompt for Godown Selection Before Saving in the Receipt Register?](https://youtu.be/Pn7-4knwMrQ)
## How to Prompt for Godown Selection Before Saving in the Receipt Register?
In this tutorial, we will learn how to enable the **"Prompt for Godown at the Doc End"** feature in the Receipt Register Configuration. This option prompts users to select the destination Godown when saving a Receipt Register entry, ensuring that received stock is recorded in the correct warehouse.
***
### Objective of This Feature
* Prompt for Godown selection before saving the document.
* Ensure stock is received into the correct Godown.
* Improve inventory accuracy.
* Eliminate incorrect warehouse allocation.
* Maintain accurate stock records.
***
### Open Receipt Register Configuration
* Open the **Receipt Register Configuration** window.
* Navigate to the **Other Options** section.
* Locate and enable the option labeled as:
> **"Prompt for Godown at the Doc End"**
* After enabling the option, save the configuration.
***
### Create a Receipt Register Entry
* Initiate a **New Receipt Register** entry.
* Complete the transaction by entering the required details.
* Save the Voucher
* When you save the voucher, the software displays a prompt asking you to select the **Godown** where the received stock should be stored.
#### Select the Godown
* Choose the required Godown from the list.
* Confirm and save the entry.
**Result**
The stock is successfully received and recorded in the selected Godown.
***
### Verify the Transaction
To review the received stock:
* Open **Reports**.
* Navigate to **Stock Reports**.
* Open the **Receipt Register Report**.
**Result**
The report displays complete details of the stock received, including the Godown in which the inventory has been recorded.
***
### Key Benefits
* Ensures accurate Godown selection during stock receipt.
* Improves inventory tracking and warehouse management.
* Prevents stock from being posted to the wrong location.
* Provides greater flexibility when receiving inventory.
* Maintains accurate Godown-wise stock records.
***
### Best Practice Tips
* Verify the selected Godown before saving the voucher.
* Use this feature when stock may be received into different warehouses.
* Regularly review the Receipt Register Report to validate inventory postings.
* Ensure users are familiar with the available Godowns to avoid incorrect stock allocation.
***
### Final Outcome
When **"Prompt for Godown at the Doc End"** is enabled, Logic ERP prompts users to select the destination Godown while saving a Receipt Register entry. The received stock is then recorded in the selected Godown, ensuring accurate warehouse allocation and reliable inventory management.
---
# 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/inventory/receipt-register/receipt-register-configuration/prompt-for-godown-at-the-doc-end.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.