> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enad.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Store groups and markets

> What store groups and markets are, and how they form a sales surface in Enad.

Products in Enad are not published to "the shop" as a single place. They are published to **surfaces**. A surface is one **store group** plus one **market**.

That is why a product can be live in B2B Sweden and off in B2C Finland at the same time. Pricing, availability, and [product and market status](/docs/catalog/product-status) are all scoped to that pair.

<CardGroup cols={2}>
  <Card title="Store group" icon="store">
    The **sales channel**. Typically B2B, B2C, or a similar store type, plus
    the markets that belong to it.
  </Card>

  <Card title="Market" icon="globe">
    The **locale**. A name, countries, language, and currency that a store
    group can sell into.
  </Card>
</CardGroup>

A simple way to remember it:

> The **store group** is who the catalog is for. The **market** is where it is sold.

## Store groups

A store group groups pricing and availability across one or more markets. Typical examples are a B2B channel and a B2C channel, each with its own set of markets.

When a store group is created it has:

| Field           | What it is                                                          |
| --------------- | ------------------------------------------------------------------- |
| Name and slug   | The label in Enad, and a stable identifier for the API              |
| Store type      | One of `b2c`, `b2b`, `d2c`, or `d2b`                                |
| Country of sale | Primary country, as an ISO 3166-1 alpha-2 code such as `SE` or `FI` |
| Markets         | Optional list of market slugs to attach                             |
| Description     | Optional note                                                       |

See [Create a store group](/api-reference/storegroups/create-a-store-group) in the Management API.

## Markets

A market is a selling locale: which countries it covers, which language it uses, and which currency prices are in. The same market can typically be attached to more than one store group.

When a market is created it has:

| Field         | What it is                                             |
| ------------- | ------------------------------------------------------ |
| Name and slug | The label in Enad, and a stable identifier for the API |
| Country codes | One or more ISO country codes, for example `SE`        |
| Locale        | Language and region, for example `sv-SE`               |
| Currency code | ISO currency, for example `SEK`                        |
| Active        | Whether the market itself is on                        |

A market being `active` is not the same as a product's **market status** on that surface. Market status is set on the product (or variant). See [Product and market status](/docs/catalog/product-status).

See [Create a new market](/api-reference/markets/create-a-new-market) in the Management API.

## How they fit together

```text theme={null}
Store group: B2B
├─ Market: Sweden
├─ Market: Denmark
└─ Market: Norway

Store group: B2C
├─ Market: Finland
└─ Market: United States
```

Each line is one surface. Product status is global. Market status, prices, and availability are typically per surface.