Build plans & bundles

Once a product exists, you price it with plans and package it as a bundle. Both live under the Catalog group.

Build a plan set

A plan is a named package — Basic, Pro, Enterprise — that decides what each feature is worth for the customers on it. Plans live inside a plan set scoped to one product version.

On the product’s Usage Plans tab:

1. Create a plan set and add the plans you sell.
2. For each plan, set each feature’s value. Every feature you configure must exist on the product, so the plan and the product’s feature list stay in step.
3. Choose an enforcement style per feature:
   • 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.
4. Publish the plan set. A plan set moves through Draft → Published → Retired; only a published set is live. Plans themselves aren’t versioned — the set’s status governs whether they apply.

Package a bundle

A bundle is the named offering a customer actually buys — a plan set, an entitlement template and a set of feature choices, packaged so a whole offering can be granted in one step.

Under Catalog → Bundles:

1. Create a bundle and open the Editor to choose its plan set, its template scope and the features it includes.
2. Use the Report view to see how the bundle is being used.
3. Publish it. Bundles have their own lifecycle — Draft → Published → Archived — with Move to Draft, Archive and Unarchive to manage it. Only a published bundle is sellable.

Plans vs. bundles — which when?

• A plan sets values and limits for one product’s features.
• A bundle is the commercial offering — it picks a plan set and a template so Sales can grant the whole thing in one step.

If you only need tiers on a single product, a plan set is enough. Reach for a bundle when you want a repeatable, one-click offering.

Next

• Sell it → Author & publish entitlements
• The model in depth → Plans & plan sets and Bundles