Decide whether a product can set its own grace period after a failed payment, or whether one setting for the deployment is enough #334

Open
opened 2026-11-15 01:12:27 +00:00 by cgalo5758 · 0 comments
Owner

The question

#255 asks whether a plan should keep delivering for a grace period after a renewal payment fails. Suppose it does, and the length of that period is one setting for the whole deployment. Should a product be able to set its own length?

The reason to want it: what a member loses when the period ends differs by kind of thing. A wiki site that becomes read-only is a mild loss. A colleague whose seat is deactivated, or a storage account that turns read-only as a whole, is not. An operator may want a longer period for a plan that sells seats than for one that sells sites.

It may also be the wrong lever, which is why this is a question and not a request. Nothing here is needed before #255 is settled and built, and it may never be.

What depends on the answer

  • Whether the product's record and its form gain a field, and what a member's plan card says when two of their subscriptions wait for different lengths.
  • How operators are expected to shape a catalog. A period per product separates only the kinds of things that are sold as separate subscription products.
  • What happens for a product that holds tiers on several plan ladders at once. One subscription then pays for several kinds of things, and one period covers all of them.

Options known so far

  1. No override. One period for the deployment: one failed payment, one date, the same for every plan.
  2. A product may override the deployment's period. Different kinds of things then get different periods only where an operator sells them as separate subscription products. A product that bundles tiers of several ladders gets one period for everything it carries.
  3. Something finer than the product, such as a period per entitlement. One failed payment would start several clocks inside one plan, and the member could not be given one date. Set aside for that reason, and listed so it is not proposed again without an answer to it.

Decided when

The answer is written in the subscription management spec, beside the rule #255 settles. If the answer is no, this closes with that sentence.

### The question #255 asks whether a plan should keep delivering for a grace period after a renewal payment fails. Suppose it does, and the length of that period is one setting for the whole deployment. Should a product be able to set its own length? The reason to want it: what a member loses when the period ends differs by kind of thing. A wiki site that becomes read-only is a mild loss. A colleague whose seat is deactivated, or a storage account that turns read-only as a whole, is not. An operator may want a longer period for a plan that sells seats than for one that sells sites. It may also be the wrong lever, which is why this is a question and not a request. Nothing here is needed before #255 is settled and built, and it may never be. ### What depends on the answer - Whether the product's record and its form gain a field, and what a member's plan card says when two of their subscriptions wait for different lengths. - How operators are expected to shape a catalog. A period per product separates only the kinds of things that are sold as separate subscription products. - What happens for a product that holds tiers on several plan ladders at once. One subscription then pays for several kinds of things, and one period covers all of them. ### Options known so far 1. No override. One period for the deployment: one failed payment, one date, the same for every plan. 2. A product may override the deployment's period. Different kinds of things then get different periods only where an operator sells them as separate subscription products. A product that bundles tiers of several ladders gets one period for everything it carries. 3. Something finer than the product, such as a period per entitlement. One failed payment would start several clocks inside one plan, and the member could not be given one date. Set aside for that reason, and listed so it is not proposed again without an answer to it. ### Decided when The answer is written in the subscription management spec, beside the rule #255 settles. If the answer is no, this closes with that sentence.
cgalo5758 added the
kind
design
area/catalogarea/billing
labels 2026-11-15 01:12:27 +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#334