---
id: ADR-COM-CAT-005
title: Stable Readable Configuration Keys
product_area: commerce
module: catalog
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Referenced configuration keeps readable keys established at creation, while transactional campaigns, uses
  and offers receive generated identities.
constrains:
  - DOM-COM-CAT-001
  - DOM-COM-CAT-002
  - DOM-COM-CAT-003
  - DOM-COM-CAT-004
  - DOM-COM-CAT-006
origin: Andrew's ordering-profile decision of 2026-10-18 (docs/decisions/ordering-profiles.md)
alternatives:
  - option: Use opaque keys for every configuration record
    why_not: Readable audience and period references already appear in migrated data and financial price rows.
consequences:
  - A period key is distinct within the workspace because price rows refer to the period directly.
  - Renaming changes display text while retaining the original configuration key.
supersedes: []
evidence:
  - >-
    services-commerce at c8b66a98: docs/decisions/ordering-profiles.md;
    modules/configuration/services/persistence/ordering-profiles.ts;
    modules/pricing/db/pricing-periods.table.ts.
---

# Stable Readable Configuration Keys

## Context

Readable keys make migrated configuration and cross-record references understandable. A later display-name change must not alter those references.

## Decision

Referenced configuration keeps readable keys established at creation, while transactional campaigns, uses and offers receive generated identities.

## Alternatives Considered

Use opaque keys for every configuration record. Readable audience and period references already appear in migrated data and financial price rows.

## Consequences

A period key is distinct within the workspace because price rows refer to the period directly. Renaming changes display text while retaining the original configuration key.