> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/deployment-options/deployment-options-ms-cm.md).
# Multi-store deployments
In a multi-store deployment, you install Microsoft SQL Server and Central Manager on computers at a central administrative location, e.g., company headquarters. You then install Microsoft SQL Server, Store Manager, and POS in each store. Central Manager has its own database and each store has its own Store Manager database.
Key store operations, such as inventory management, merchandising, and purchasing, are controlled from the Central Manager app. Data is synchronized between Central database and the Store Manager databases using jobs, which are processed by services.
Server services, which are managed using the Central Server app, manage server-side communication between Central Manager and the Store Manager apps. Client services, which are managed using the Central Client app, manage store-side communication between the Store Manager apps and Central Manager.
**Example of a multi-store deployment with Central Manager**
**Example of Central Manager and Store Manager database communication**
The Flash Bridge app must be installed on any computer running an RMH app (such as Store Manager, POS, Central Manager, and Loyalty). The Flash Bridge app enables communication between the apps and acts as a vault where jobs are stored until they can be processed by Central Server and Central Client.
In multi-store deployments it is recommended that you install and run Microsoft SQL Server on standalone computers with sufficient memory and processing power to accommodate larger databases, worksheet processing, and more store transactions.
---
# 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://docs.rmhpos.com/installation/deployment-options/deployment-options-ms-cm.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.