wiki-cafe/member-console
0
0
Fork 0
Code Issues 140 Pull Requests Packages Projects 1 Releases Activity

The operator cannot see which payment-provider product a catalog product is mapped to #100

New Issue
Open
opened 2026-09-21 07:18:30 +00:00 by cgalo5758 · 0 comments
cgalo5758 commented 2026-09-21 07:18:30 +00:00
Owner
Copy Link
Copy Source

What a person cannot do today

See, from a product's operator page, which Stripe product and price it is mapped to and whether that mapping is in sync. Each catalog product is mapped one to one, and the mapping row carries the remote id and a sync status, but neither appears on the product list or the product detail page. A mapping that failed to sync is invisible until a purchase fails.

What they should be able to do

Read the mapped remote product and price, and the mapping's sync status, on the product's own page, and reach the provider's own record from there.

Why it matters

Retiring a product, changing a price and diagnosing a purchase that will not complete all turn on the state of that mapping. Stripe archives its products rather than deleting them, so the two sides drift in ways only the mapping row records, and today nothing shows the operator that row.

Where

internal/server/operator_products.go and the operator product templates; the product and price mapping tables in the Stripe integration's store.

Done when

The product list and the product detail page show each product's mapping and its sync status, a product with no mapping or a stale one is marked as such, and prices show the same.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today See, from a product's operator page, which Stripe product and price it is mapped to and whether that mapping is in sync. Each catalog product is mapped one to one, and the mapping row carries the remote id and a sync status, but neither appears on the product list or the product detail page. A mapping that failed to sync is invisible until a purchase fails. ## What they should be able to do Read the mapped remote product and price, and the mapping's sync status, on the product's own page, and reach the provider's own record from there. ## Why it matters Retiring a product, changing a price and diagnosing a purchase that will not complete all turn on the state of that mapping. Stripe archives its products rather than deleting them, so the two sides drift in ways only the mapping row records, and today nothing shows the operator that row. ## Where [`internal/server/operator_products.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/operator_products.go) and the operator product templates; the product and price mapping tables in the Stripe integration's store. ## Done when The product list and the product detail page show each product's mapping and its sync status, a product with no mapping or a stale one is marked as such, and prices show the same. Migrated from status/issues.md at b7a0e15
cgalo5758 added the
kind
enhancement
area/catalogarea/billingarea/operator-ui labels 2026-09-21 07:18:30 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
accessibility
A barrier for people using assistive technology or a keyboard alone.
 area/billing
The Stripe mirror, checkout, subscriptions, invoices, fulfillment.
 area/catalog
Products, prices, plan ladders, purchasability.
 area/discourse
The Discourse integration.
 area/domains
The domains registry, claims, placements, the certificate ask.
 area/entitlements
Entitlement sets, rules, grants, pools, provisioning.
 area/fedwiki
The Federated Wiki integration and farm sync.
 area/identity
Sign-in, sessions, persons, organizations, workspaces, roles.
 area/integrations
The provider registry, outbox and webhooks in general.
 area/licensing
Licenses, the contributor agreement, SPDX headers.
 area/member-ui
Member pages.
 area/meta
The repository itself, its contributing guide, CI, the tracker and the workflow.
 area/operator-ui
Operator pages, forms, lists, the design system.
 area/ops
Deployment, configuration, migrations, workflows, instance settings.
 area/testing
The test stack, screens, lint, walkthroughs.
 duplicate
Closed because another issue already covers it.
 good-first-issue
Small, self-contained, and explained enough to be a first contribution.
 invalid
Closed because it is not a ticket for this repository.
 privacy
Touches what a person's data reveals.
 security
Touches authentication, authorization, secrets or data exposure.
 upstream
Waits on another repository or project before it can move.
 wontfix
Closed because it will not be done, with the reason in the last comment.
kind
bug
The software does something other than what it promises; closed when it again does what it promises.
kind
debt
Code, tests or tooling to clean up with nothing visible changing; closed when they are cleaner.
kind
design
A question to settle before work can be defined; closed when the decision is written down.
kind
docs
Documentation that is wrong or missing; closed when it says the right thing.
kind
enhancement
Something the software does not do yet; closed when it does.
priority
critical
Blocks the active milestone or harms members now.
priority
high
Next in line inside the active milestone.
priority
low
Inside the active milestone, when nothing else is left.
priority
medium
Inside the active milestone, after the high ones.
No labels area/billing area/catalog area/operator-ui
kind
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
3wordchant Bortseb (Robert Best) cgalo5758 (Christian Galo) renovate-bot (Comrade Renovate Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#100