An add-on a member is meant to hold several times can only be bought once #3

Open
opened 2026-09-21 07:18:02 +00:00 by cgalo5758 · 0 comments
Owner

What a person cannot do today

Buy the same add-on twice, or buy one with a quantity. Add-ons sit off the plan ladders and are meant to stack, unlike plan tiers, which are mutually exclusive per ladder. The member catalog already presents them as a stackable section; the mechanics behind that presentation were deferred, so checkout offers one purchase and the provisioning path for a second one does not exist.

What they should be able to do

Buy an add-on again, or several at once, and hold each purchase as its own provision whose entitlements add to what the member already holds.

Why it matters

An add-on that can be bought once is a plan tier with a different label, and the catalog says otherwise on the page where it is sold.

Where

internal/server, the checkout path; internal/fulfillment, provisioning from a purchase; internal/entitlements, the contributions that add up.

Done when

Checkout accepts a quantity and a repeat purchase of an add-on, each purchase creates its own provision recorded as sourced from a purchase, and materialization sums their contributions.

Migrated from status/issues.md at b7a0e15

## What a person cannot do today Buy the same add-on twice, or buy one with a quantity. Add-ons sit off the plan ladders and are meant to stack, unlike plan tiers, which are mutually exclusive per ladder. The member catalog already presents them as a stackable section; the mechanics behind that presentation were deferred, so checkout offers one purchase and the provisioning path for a second one does not exist. ## What they should be able to do Buy an add-on again, or several at once, and hold each purchase as its own provision whose entitlements add to what the member already holds. ## Why it matters An add-on that can be bought once is a plan tier with a different label, and the catalog says otherwise on the page where it is sold. ## Where [`internal/server`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server), the checkout path; [`internal/fulfillment`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/fulfillment), provisioning from a purchase; [`internal/entitlements`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/entitlements), the contributions that add up. ## Done when Checkout accepts a quantity and a repeat purchase of an add-on, each purchase creates its own provision recorded as sourced from a purchase, and materialization sums their contributions. Migrated from status/issues.md at b7a0e15
cgalo5758 added the
kind
enhancement
area/catalogarea/billingarea/member-ui
labels 2026-09-21 07:18:02 +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#3