Plans & plan sets

A plan is a named package — Basic, Pro, Enterprise — that decides what each feature is worth 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 a single product. A plan set moves through Draft → Published → Retired.

Because a plan set belongs to one product, a product and its plans evolve together: publish a new product version and you give it its own plan set, leaving the previous version’s pricing untouched. Plans themselves aren’t versioned — the plan set’s status is what governs whether they’re live.

Every feature a plan configures must exist on the product, so plans and the product’s feature list stay in step.

How it relates

• Belongs to → one product.
• Values → the product’s features, by code.
• Packaged by → a bundle, which picks a plan set.
• Applied to → an entitlement, which carries the plan that’s in effect for that customer.