> 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/bill-passing/masters/applicable-stores.md).
# Applicable Stores
**Applicable Stores** are the specific stores, warehouses, or inventory locations where a particular master setting, transaction rule, or business process is applicable. This configuration helps organisations control and define the stores that can use a specific purchase type or related settings, ensuring accurate transaction processing and operational consistency.
## Steps to Configure Applicable Stores
Step 1: Navigate to the **Masters** menu in the **Bill Passing** module.
1. Click on **Applicable Stores**.
* The **Applicable Stores** screen will be displayed.
Step 2: Select the required **Purchase Type** from the available options.
1. Once the Purchase Type is selected, the system will display the list of available stores and the existing store configuration.
Step 3: Verify that all required stores have been selected.
Step 4: Click the **Save** button.
* The system will validate and save the selected store configuration.
---
# 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/bill-passing/masters/applicable-stores.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.
