---
id: ADR-COM-CAT-017
title: Schedule Ownership and the Retained API
product_area: commerce
module: catalog
revision: 1
status: proposed
design_intent: open
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Ownerless schedule APIs remain implemented, but the later product ruling assigns schedules to selling owners
  and removes standalone administration.
constrains:
  - DOM-COM-CAT-004
  - SVC-COM-CAT-pricing
  - STATE-COM-CAT-005
  - WF-COM-CAT-012
origin: >-
  Andrew ruling R5, 2026-10-22 (services-commerce:docs/debt/pricing-schedules-owned-by-event.md);
  FND-COM-CAT-002
alternatives:
  - option: Retain permanent ownerless schedule administration
    why_not: This conflicts with the later owner-bound product direction.
  - option: Restore a standalone schedule screen
    why_not: The recorded ruling removes that surface in favour of owner setup.
consequences:
  - Existing ownerless schedules need an owner-aware migration path.
  - Staff currently have no standalone console preparation surface.
  - Unused schedule components can be reused by the owner setup or removed.
supersedes: []
evidence:
  - >-
    services-commerce at c8b66a98: modules/pricing/db/pricing-periods.table.ts;
    services/persistence/pricing-schedules.ts; docs/debt/pricing-schedules-owned-by-event.md.
  - >-
    services-commerce at c8b66a98: docs/milestones/COMM-M1-set-up-what-you-sell.md (Decisions);
    docs/milestones/plans/COMM-M1-plan.md.
  - 'services-commerce:docs/debt/pricing-schedules-owned-by-event.md#Decision'
---

# Schedule Ownership and the Retained API

## Context

The earlier independent-schedule direction was superseded by the walkthrough ownership ruling. Existing period pricing remains usable while the owner-aware write contract and setup are outstanding.

## Decision

Ownerless schedule APIs remain implemented, but the later product ruling assigns schedules to selling owners and removes standalone administration.

## Alternatives Considered

Retain permanent ownerless schedule administration. This conflicts with the later owner-bound product direction.

Restore a standalone schedule screen. The recorded ruling removes that surface in favour of owner setup.

## Consequences

Existing ownerless schedules need an owner-aware migration path. Staff currently have no standalone console preparation surface. Unused schedule components can be reused by the owner setup or removed.