Plans & plan sets

A plan is a named package — Basic, Pro, Enterprise — that sets each feature’s value and limits for the customers on it. For every feature it can set a single value or a ladder of tiers, with an enforcement style:

• Single value — one flat value (e.g. seats = 5).
• Tiered (absolute) — limits by absolute usage (0–1,000 then 1,001–5,000…).
• Tiered (percentage) — limits by percentage of an allowance.

Plan sets

Plans live inside a plan set — a named collection (e.g. “Acme Plans”) scoped to one suite. A plan set moves through Draft → Published → Retired.

A suite is the group of products sold together, and most suites hold exactly one product: the first time you price a product, a suite holding just it is created for you and named after it. So “the plans for this product” and “the plans for this suite” are the same thing until the day you sell two products as one subscription.

Because a plan set belongs to one suite, what you sell and what you charge for it evolve together: publish a new product version and you give it its own plan set, leaving the previous version’s pricing untouched. A published set is never edited in place: an edit lands on a draft revision, created for you if needed, and publishing a set automatically retires the previously published set of the same suite — there’s exactly one live set per suite at a time. Plan sets can never be deleted, and a set holds at most 10 plans.

Every feature a plan configures must exist on the product, so plans and the product’s feature list stay in sync. Each feature entry needs what its style needs: single-value entries a value, percentage ladders a base. The value has to be readable as the feature’s declared type — "yes" on a Boolean is refused when you enter it, not at the customer’s application. Denied and Not included are how a plan withholds a feature, so they carry no value at all; an absolute ladder’s quota is the ladder itself.

A feature’s own value is what applies when no plan governs it — a plan-less entitlement, or a feature the plan does not list. Every plan that does list it overrides it, so the feature’s own value and the plan never both decide the same thing.

Plans across several products

When a suite sells more than one product, a plan lists each product in the suite separately: whether that product is included at all, and what its features are worth if it is. That is how one plan can carry a core product and leave a secondary product out, with the upgrade to a higher plan being an ordinary plan change. A product the plan does not list is treated as not included.

See suites for the whole picture.

How it relates

• Belongs to → one suite, which is one or more products sold together.
• Values → those products’ features, by code.
• Packaged by → an add-on, which picks a suite.
• Applied to → an entitlement, which carries the plan that’s in effect for that customer.