> 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/issue-register/issue-register-configuration/default-godowns.md).

# Default Godowns

**YouTube:** [How to Configure Default Godowns for the Stock Filter in the Issue Register?](https://www.youtube.com/watch?v=2tmvN21NYk8)

## How to Configure Default Godowns for the Stock Filter in the Issue Register?

In this tutorial, we will learn how to configure and use the **Default Godowns** feature in the Issue Register module of Logic ERP. This feature filters the Lot Search window to display lots only from the selected default godown, making item selection faster and more accurate.

***

### Objective of This Feature

* Filter lots based on a default Godown.
* Simplify lot selection during Issue Register entry.
* Reduce manual searching across multiple godowns.
* Improve inventory accuracy.
* Speed up issue transaction processing.

***

### Review the Default Behavior

* Open the **Issue Register** module.
* Initiate a new Issue Register entry.
* Transact an Item.

<figure><img src="/files/qeBar1SJhrRkOUObHW3n" alt=""><figcaption></figcaption></figure>

**Result**

* The **Lot Search** window displays available lots from **all Godowns**, as no default Godown has been configured.

***

### Let's Configure the Default Godown

* Open the **Configuration** window.
* Navigate to the **Other Settings** section.
* Locate the option labeled as:

> **"Default Godowns"**

<figure><img src="/files/drxIkqGoufiGXfS5vi44" alt=""><figcaption></figcaption></figure>

* Select the required Default Godown.
* Save the configuration.

**Observe the Functionality**

* Initiate a new Issue Register entry.
* Transact the same Item.

<figure><img src="/files/XuuL3Pn2gZto8WHMpyiz" alt=""><figcaption></figcaption></figure>

**Result**

The **Lot Search** window now displays **only the lots available in the configured Default Godown**.

This eliminates the display of lots from other Godowns and makes the selection process quicker and more accurate.

***

### Key Benefits

* Filters lots based on the selected Godown.
* Reduces manual searching during issue entry.
* Improves inventory accuracy.
* Speeds up transaction processing.
* Helps users work with the correct warehouse inventory.

***

### Best Practice Tips

* Configure the Default Godown according to your operational warehouse.
* Review the setting whenever warehouse assignments change.
* Verify lot availability before processing issue transactions.
* Use this feature to minimize selection errors in multi-godown environments.

***

### Final Outcome

After configuring the **Default Godowns** option, Logic ERP filters the **Lot Search** window to display only the lots available in the selected Godown during Issue Register entry. This improves efficiency, simplifies lot selection, and ensures transactions are processed using the correct warehouse inventory.


---

# 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/issue-register/issue-register-configuration/default-godowns.md?ask=<question>&goal=<endgoal>
```

`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.