> 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-w-lm.md).
# Loyalty Manager deployments
This topic describes common Store Loyalty and Central Loyalty deployments for RMH. Deployments are also known as implementations.
In a single store deployment with Store Manager and POS (or multiple single store deployments), you need to install Store Loyalty Manager on the same computer as Store Manager. You also need to install the Store Loyalty Extension in every POS lane. The Store Loyalty Extension enables communication between POS and Store Loyalty Manager.
{% hint style="info" %}
The Store Loyalty Extension is installed using the same MSI file that you use to install Store Loyalty Manager. If the installation wizard detects that POS is installed on the computer, it will only install the Store Loyalty Extension.
{% endhint %}
**Example of a single store deployment of Store Loyalty**
In a multi-store deployment with Central Manager, you need to install Central Loyalty Manager on the same computer as Central Manager. You also need to install Store Loyalty Manager on the same computer as Store Manager and the Store Loyalty Extension in every POS lane. Loyalty programs can only be created in Central Loyalty Manager.
{% hint style="info" %}
The Store Loyalty Extension is installed using the same MSI file that you use to install Store Loyalty Manager. If the installation wizard detects that POS is installed on the computer, it will only install the Store Loyalty Extension.
{% endhint %}
**Example of a multi-store deployment of Central Loyalty**
---
# 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.rmhpos.com/installation/deployment-options/deployment-options-w-lm.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.
