> For the complete documentation index, see [llms.txt](https://support.barnetpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.barnetpos.com/pos-manager/product-maintenance/price-groups-and-sync-in-multi-store-portal.md).

# Price Groups and Sync in Multi Store Portal

**PRICE GROUPS**

A “Price Group” table is common for all stores across the portal, to allow centralized HO management. Store data cleanup is mandatory in preparation for the store being added to an existing multi-store portal. While each store in a multi-store portal can have the same product with different price groups, the price groups themselves in their table are shared across all stores. There can only be one Tier 25. Here is rationale to get an understanding on how to manage that area.

Price Groups are used in Categories, Customer Groups (for Cost types) and are common for all portal stores in multi-store portal and are also used in PBS.

For ease of manageability, Price Groups IDs in stores, targeted for multi-store portals, are usually set to Price Tier % value as seen below in PM:

![](/files/cR3wg42OCqP2XvTwRMDa)

Please note that on portal PM Tier (unique in PM) is called ‘PM Tier’:

![](/files/r9LmG5oTg5dAqJoYBKRI)

**Price Groups Synchronization Rules:**

\
-**Store to portal:**\
PriceTypes should be present in ‘Tables to sync’ on ‘Web Sync’ tab. (overnight, unless Fast Slow sync enabled in lower part of this tab)

-**Portal to store:**\
'Load Price Groups' should be checked on ‘Portal Sync with HO’ tab.\
To perform full portal to store sync, set ‘Price Groups Rev’ to 0 and save, otherwise sync is incremental - on Price Group saves.\
fast sync - usually within a minute\
this sync does not recalculate store product prices, it relies on portal Product prices update, and sync.

**In single store**, two-way full sync is executed if enabled as above.

\
**In multi-store**, portal to store sync is performed, if enabled in stores, and store to portal sync can work only for lead store, if enabled. Regular stores store to portal price groups sync is not performed, portal discards received data if percentages changed.

How to clean up store data before joining the portal:\
1\. In POS Manager, renumber Tiers in all Price Groups to be consistent across all stores.\
(I need to verify that PM renumbering updates PM Categories, Customer Groups (if used) and Products, and if necessary, release new PM build).\
2\. Update Price Groups on portal to have same ‘PM Tier’ as Tier in stores for same % levels.\
In single store portals, just execute web sync. In multi-store, either dedicate lead store and upload, or do that manually.


---

# 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://support.barnetpos.com/pos-manager/product-maintenance/price-groups-and-sync-in-multi-store-portal.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.