An operator cannot retire a product; the only way out of the catalog is deleting it #97

New Issue

2026-09-21T07:18:29Z

cgalo5758 commented

2026-09-21 07:18:29 +00:00

What a person cannot do today

Move a product out of service from the operator panel. Every product carries a lifecycle status of draft, published or retired, and the products list filters and badges it, but no form writes it: the product edit form offers an Active checkbox and a Listed checkbox and nothing else. A product created through the console is published at creation and stays published, so an operator who wants to stop offering a product either unticks Active, which says nothing about the product's standing, or deletes the row, which takes its history with it.

What they should be able to do

Retire a published product, and publish a draft one, from the product's own page, with the transition named for what it does and a confirmation that states what retirement leaves untouched: existing grants keep delivering, and the payment-provider record is archived rather than deleted.

Why it matters

Retirement is the archive primitive the catalog was designed around: a retired product stops being offered while the grants, prices and invoices that reference it stay readable. Deletion is the only alternative the panel offers today, and it is the destructive one. An operator who cannot reach the safe path takes the unsafe one, or leaves a product in the catalog that should no longer be sold.

Where

internal/server/operator_product_forms.go and internal/server/operator_products.go; the product detail template under internal/embeds/templates/partials/; the lifecycle_status column and its domain check in the core product schema.

Done when

The product detail page offers the transitions its current status allows, a refused transition names why, the products list reflects the new status, and a test covers each allowed transition and at least one refused one.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Move a product out of service from the operator panel. Every product carries a lifecycle status of draft, published or retired, and the products list filters and badges it, but no form writes it: the product edit form offers an Active checkbox and a Listed checkbox and nothing else. A product created through the console is published at creation and stays published, so an operator who wants to stop offering a product either unticks Active, which says nothing about the product's standing, or deletes the row, which takes its history with it. ## What they should be able to do Retire a published product, and publish a draft one, from the product's own page, with the transition named for what it does and a confirmation that states what retirement leaves untouched: existing grants keep delivering, and the payment-provider record is archived rather than deleted. ## Why it matters Retirement is the archive primitive the catalog was designed around: a retired product stops being offered while the grants, prices and invoices that reference it stay readable. Deletion is the only alternative the panel offers today, and it is the destructive one. An operator who cannot reach the safe path takes the unsafe one, or leaves a product in the catalog that should no longer be sold. ## Where [`internal/server/operator_product_forms.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/operator_product_forms.go) and [`internal/server/operator_products.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/operator_products.go); the product detail template under `internal/embeds/templates/partials/`; the `lifecycle_status` column and its domain check in the core product schema. ## Done when The product detail page offers the transitions its current status allows, a refused transition names why, the products list reflects the new status, and a test covers each allowed transition and at least one refused one. Migrated from status/issues.md at b7a0e15

cgalo5758 added the

kind

enhancement

area/catalog area/operator-ui labels 2026-09-21 07:18:29 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#97