> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/features/warehouses-and-agencies.md). # Warehouses & Agencies **Warehouses** in PBMS represent the points from which goods, services, or cash are dispatched. For cash-based programs, sponsor banks holding program funds are treated as warehouses. Allocation of warehouses is determined by association rules based on geography and benefit codes, ensuring that distribution aligns with the geographical spread of beneficiaries. PBMS sends notifications to warehouses with detailed instructions, including the agencies responsible for collecting inventory and distributing it to beneficiaries. Warehouse allocation typically operates at the level of larger geographic entities such as states or districts, though this can be configured to suit specific implementations. **Agencies** function similarly to warehouses but operate on smaller geographic areas. Allocation of agencies is likewise based on association rules tied to geography and benefit codes, but while warehouses are mapped to large entities like districts or states, agencies are mapped to localities, postcodes, or neighborhoods. Once allocated, PBMS sends notifications to agencies containing details of beneficiaries and their entitlements, ensuring localized execution of benefit delivery. --- # 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://docs.openg2p.org/products/pbms/features/warehouses-and-agencies.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.