> 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/central-manager/manage-customers/customers-synchronizing.md).
# Synchronize customer records between stores
This topic explains how customer records are synchronized between centrally managed stores and the Central database.
In centrally managed stores, when a customer record is added to a store's database, it is automatically synchronized to the Central database. However, the customer record is not automatically synchronized from the Central database to other store databases. The other stores must use the **Lookup Online** function in POS to synchronize the customer record to their own store databases.
{% hint style="success" %}
If your store wants to prevent other centrally managed stores from synchronizing your store's customer records to their store databases, open Store Manager and go to **File** | **Configuration** | **Store rules** | **Customer Options** and enable the store rule **Do not allow customer lookup in RMH Central**.
{% endhint %}
1. In **POS**, tap **Customers** | **Lookup Customer**.
2. Type all or part of the customer's name in the lookup field.
3. Tap **Lookup Online**.
4. To select the customer, do one of the following:
* Tap the customer record once and tap **Select**.
* Tap the customer record twice.
The customer record is synchronized from the Central database to the store's database.
{% hint style="info" %}
The **Lookup Online** function in POS does not synchronize the customer's purchase history from other stores. Stores can only look up the customer's purchase history in their own store.
{% endhint %}
---
# 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/central-manager/manage-customers/customers-synchronizing.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.
