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

# Display groups & labels

> Organize properties into sections and tag product versions for tracking.

Two features help you organize the catalog: **display groups** arrange
properties into sections on the product page, and **labels** tag product versions
so you can track their state. This page covers both. For the shared vocabulary,
see [Core concepts](/getting-started/concepts).

## Display groups

A product can carry dozens of properties. Display groups arrange them into named
sections — "Basic Info", "SEO", "Materials" — and set the order those sections
appear in. Each [property definition](/catalog/product-types-properties) belongs
to a display group, and each group has a key, a display name, and a sort
position, all scoped to your organization.

<Note>
  Display groups only affect **presentation** — how properties are grouped and
  ordered on the page. They don't change a property's type, level, or validation.
</Note>

### Groups are created for you on import

When you import property definitions from a CSV, any display group referenced in
the file that doesn't yet exist is **created automatically** on import, so you
don't have to pre-create every section by hand.

<Warning>
  Editing and saving a property definition in the UI requires its display group to
  **already exist** in your organization. If you assign a property to a group name
  that has never been created, saving fails. Reference groups that exist, or add
  them (importing definitions that reference a new group creates it).
</Warning>

<Tip>
  Each organization starts with a set of default display groups, so a fresh catalog
  already has sensible sections to assign properties to.
</Tip>

## Labels

Labels tag product **versions** so you can mark and find their state — for
example `production`, `draft`, or `staging`. Labels are drawn from a shared list
for your organization: you can assign an existing label or create a new one.

<ResponseField name="production" type="reserved label">
  The `production` label is reserved and special-cased — only one version of a
  product may hold it at a time, marking the canonical version. It cannot be
  deleted. See [Versioning](/catalog/versioning) for how the production version
  is used.
</ResponseField>

<Note>
  Labels attach to a specific **version** of a product, not the product as a whole —
  which is what lets you keep, say, a production version and a draft version of the
  same product side by side.
</Note>

<CardGroup cols={2}>
  <Card title="Product types & properties" icon="sitemap" href="/catalog/product-types-properties">
    The property definitions that display groups organize.
  </Card>

  <Card title="Versioning" icon="code-branch" href="/catalog/versioning">
    How labels mark the production version and track version state.
  </Card>
</CardGroup>