> 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/es/store-manager/configure-pos-and-store-manager/store-information-and-rules/setting-up-multiple-stores.md).

# ID de tienda (solo multitienda)

{% hint style="warning" %}
Solo necesita usar esta pestaña si ha implementado Store Manager y POS en varias tiendas de una cadena y está utilizando Central Manager para administrar las bases de datos de las tiendas.
{% endhint %}

1. Haga clic en **Archivo** | **Configuración**.
2. Haga clic en el **Multi-Store** .
3. La **ID de tienda** lo asigna el administrador de la tienda.
4. Seleccione **Habilitar el modo central** para administrar la tienda usando Central Manager.
5. En el **URL del servidor central**; introduzca la URL del Servidor Central. El Servidor Central se utiliza para intercambiar y sincronizar datos entre Store Manager y Central Manager.
6. Haga clic en **Probar** para probar la conexión con el Servidor Central.
7. Haga clic en **Guardar y cerrar**.


---

# 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/es/store-manager/configure-pos-and-store-manager/store-information-and-rules/setting-up-multiple-stores.md?ask=<question>&goal=<endgoal>
```

`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.