A product cannot be sold as a bundle covering several plan ladders at once #88
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: wiki-cafe/member-console#88
Reference in New Issue
Block a user
What a person cannot do today
Sell, or buy, one product that occupies a rung on more than one plan ladder at the same time, such as a hosting tier and a support tier together. A product can already be a tier on several ladders and the operator surfaces make that legible, but nothing treats the combination as an offer, and there is no operator-side configuration for one.
What they should be able to do
The operator: declare that one product is sold as a bundle covering named rungs on several ladders. The member: see what the bundle includes, read that taking it replaces the standalone tiers it covers, and find those standalone tiers disabled with that reason for as long as the bundle is held.
Why it matters
Without it an operator who wants to sell a combination has to price each part separately, and a member ends up holding several subscriptions where one offer was meant.
Where
The catalog's ladders and tiers; the member catalog and its controls.
Done when
The operator side lands first, because the member surface has nothing to present until a bundle can be configured; then the member catalog shows the bundle's contents, states the exclusivity it creates, and disables the tiers it covers with that reason.
Migrated from status/issues.md at
b7a0e15