> 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/configure-stores/best-practices-store-groups.md).

# Best practices for store groups

In Central Manager, you must assign stores to store groups to facilitate store setup and management. You should set up store groups according to natural divisions in your retail organization. Some examples of these natural divisions include:

* **Different types of retail operations.** You might create store groups to separate boutique stores from outlet stores, or general stores from specialty stores, or food trucks from brick-and-mortar restaurants.
* **Different store brands.** You might create store groups to separate your high end brand from your discount brand, or your quick stop brand from your full service brand.
* **Divisional or regional store management.** You might create store groups based on the management or sales hierarchies in your organization. For example your organization may have a divisional hierarchy or a regional hierarchy for store management.

It is acceptable to have only one store in a store group. There is also no limit to how many stores you add to a store group.

It can be difficult to change an established store group structure. You should consider your organization's current and future needs when you set up a store group structure. Ensure the store group structure can support growth.


---

# 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/central-manager/configure-stores/best-practices-store-groups.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.