The site does not have one price list, it has one per market. A Region is a market: one country, one currency, its own set of retailers and its own prices. Visitors are matched to a region by the country they are browsing from, and everything commercial they see, prices, buy links, store availability, flows from that match.
A region is three fields:
| Field | Meaning |
|---|---|
| Title | Internal name, e.g. Serbia |
| Country | The single country this region serves |
| Currency | Prices for this region are entered and displayed in it |
One country maps to exactly one region, the admin enforces it. There is no fallback region either: a visitor from a country with no region sees no prices and no buy links at all, the product pages simply omit the commercial parts. That is intentional, better nothing than the wrong market's offer.
The region's Retailers tab lists every retailer operating there, managed from the retailer side.
The visitor's country comes from network geolocation on every request, not from the language they picked. A visitor reading the Serbian site from Vienna gets Austrian prices and Austrian retailers. Language and market are deliberately independent axes: locale decides words, region decides money.
Prices live in their own collection, Where to Buy → Prices, not on the product. One price document says: this product, in this region, starts at this amount.
A product with no price document for a region still shows in that region, just without the price line. Prices and availability are independent: availability comes from retailers, the price is cosmetic on top.
When a new market launches, the checklist is short: create the region, assign the retailers to it, then add a price document per product that should show a price there. Products need no edits at all, which is the payoff of keeping prices out of the product document: launching or closing a market never touches the catalog.