Skip to main content
Stores management is where you define the stores your store-level pricing runs against. Open Stores from the main navigation - four tabs cover the full setup: Stores, Zones, Channels, and Competitors. A store in Retailgrid is a location dimension, not just a physical shop. A store can represent:
  • A physical store
  • A country or market
  • A warehouse
  • An online shop or marketplace (Amazon, Zalando, etc.)
  • A B2B vs B2C channel
If prices, costs, tax rates, or stock differ across any of these, model them as separate stores and load a Product store data dataset.
Stores management - the Stores tab with name, external ID, country, currency, zone, and channel per store

​
Create a store

  1. Open Stores from the main navigation.
  2. Click Add store.
  3. Fill in the store’s attributes:
    • Name - must be unique. Use consistent, readable names.
    • External ID - the identifier your data uses for this store (e.g. NE-TOR). storeId values in your data loads match against this.
    • Country - drives tax and market context.
    • Currency - the currency this store prices in. Must be a valid currency code.
    • Zone - the pricing zone this store belongs to (see below).
    • Channel - the sales channel (e.g. Online, Offline, B2B).
  4. Save. The store appears in the list with its key attributes.
Retailgrid validates name and currency on save, and rejects a duplicate name or an invalid currency with a specific error.

​
Edit a store

Use Edit on any row to change a store’s attributes. Changes persist immediately and are reflected everywhere the store is used - the SKU-Store grid view, rule targeting in Dynamic Pricing, and store-level metrics.

​
Pricing zones

A pricing zone is a group of stores that share pricing logic - for example, all eurozone stores, or all urban locations.
  • Define zones on the Zones tab and assign stores to them.
  • In Dynamic Pricing, a rule can target a pricing zone, so one margin floor or parity rule covers every store in the zone without repeating the rule per store.
Zones keep rule sets small when you operate many stores with a handful of distinct pricing policies.
Stores management - the Zones tab grouping stores into pricing zones

​
Channels

The Channels tab groups your stores into sales channels - Online, Offline, B2B, marketplace, and so on. Like zones, channels are a targeting dimension: filter the grid by channel, or scope a Dynamic Pricing rule to just your online stores.
Stores management - the Channels tab grouping stores into sales channels

​
Competitors

The Competitors tab is where you scope which competitors apply to which stores, zones, and channels. Search your loaded competitors and assign each one to the locations where it actually competes, so pricing rules and competitor-gap metrics compare against the right set per location. See Assign competitors to stores, zones, and channels for the full workflow.
Stores management - the Competitors tab for scoping competitors to stores, zones, and channels

​
Find stores

The store list is searchable and filterable by country, zone, and channel - useful once the list grows past a screenful.

​
How store configuration is used

Everything defined here feeds the rest of the app:
  • Data loading - storeId values in your Product store data uploads (CSV or API) must match a store defined here.
  • Grid - the SKU-Store view shows one row per product-store combination, with the store’s country, currency, channel, and pricing zone as columns.
  • Pricing rules - Dynamic Pricing emits one recommended price per product-store combination and can scope rules by store attributes.
  • Competitors - assign competitors to stores, zones, or channels so each location’s pricing rules and gap metrics use the right competitor set. See Assign competitors to stores, zones, and channels.
  • Metrics - margin, price index, and competitor-gap metrics compute per store, using each store’s own price, cost, and competitor set.