> 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/default-godowns.md).
# Default Godowns
**YouTube:** [How to Configure Default Godowns in the Receipt Register?](https://youtu.be/h8SbD2hl0nU)
## How to Configure Default Godowns in the Receipt Register?
In this tutorial, we will learn how to define **Default Godowns** in the Receipt Register Configuration. This feature allows you to display stock only from selected godowns in the Lot Search window, making item selection faster and more relevant during Receipt Register entry.
***
### Objective of This Feature
* Display stock from selected godowns only.
* Simplify the Lot Search window.
* Improve stock visibility during Receipt Register entry.
* Reduce unnecessary lot selection.
* Speed up transaction processing.
***
### Review the Default Behavior
Before enabling the feature, let's understand the default behavior.
* Initiate a **New Receipt Register** entry.
* Select and transact an Item.
**Result**
The **Lot Search** window displays **all available lots** across **all godowns**.
This means the stock available for the selected item in every lot and every godown is displayed by default.
***
### Configure Default Godowns
* Open the **Receipt Register Configuration** window.
* Navigate to the **Other Options** section.
* Locate the option labeled as:
> **"Default Godowns"**
* Open the selection window.
* A list of all available Godowns will appear.
* Select the Godown or Godowns that you want to set as default.
* Save the configuration.
***
### Create a New Receipt Register Entry
* Close and reopen the **Receipt Register** window.
* Initiate a **New Receipt Register** entry.
* Select the same Item.
**Result**
The **Lot Search** window now displays stock only from the selected default Godown(s).
Lots belonging to other Godowns are no longer displayed, allowing you to work only with the relevant inventory locations.
***
### Key Benefits
* Displays stock from selected Godowns only.
* Simplifies the Lot Search window.
* Improves transaction speed.
* Reduces selection errors.
* Enhances warehouse-specific inventory management.
***
### Best Practice Tips
* Select only the Godowns that are relevant to your Receipt Register transactions.
* Review the default Godown settings whenever warehouse assignments change.
* Use this feature to minimize unnecessary lot selection and improve operational efficiency.
***
### Final Outcome
After configuring **Default Godowns**, Logic ERP filters the **Lot Search** window to display stock only from the selected Godown(s) during Receipt Register entry. This streamlines inventory selection, improves accuracy, and makes receipt processing more efficient.
---
# 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/default-godowns.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.