> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/housekeeping/housekeeping-module/masters/store-transaction-type.md).
# Store Transaction Type
The **Store Transaction Type** master in the House Keeping module is used to define and manage different types of store transactions. These transaction types help track stock movements such as stock issue, stock receipt, transfer, return, and adjustment activities within housekeeping stores.
## Steps to Create a Store Transaction Type
Step 1: Go to the **Housekeeping** module from the main menu.
1. Click on **Masters** and select **Store Transaction Type.**
* The **Store Transaction Type** screen will be displayed.
Step 2: Click on the **New** button.
1. Enter the required details in the respective fields.
* **Store -** select the required store from the list.
* **Transaction ID -** enter the unique identification code for the transaction type.
* **Transaction Name -** enter the name of the transaction type.
Step 3: After entering all required details, click on the **Save** button.
* The Store Transaction Type will be created successfully and added to the master list.
---
# 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://help.rbsgo.com/housekeeping/housekeeping-module/masters/store-transaction-type.md?ask=&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.
