Build plans & add-ons

Once a product exists, you price it with plans — and can package extras as add-ons. Both live under the Catalog group.

Build a plan set

A plan is a named package — Basic, Pro, Enterprise — that sets each feature’s value for the customers on it. Plans live inside a plan set.

A plan set belongs to a suite — the group of products sold together — but you don’t have to create one to price a single product: the first plan set you build gets a suite holding just that product, created for you and named after it. Everything below works the same whether the suite holds one product or nine.

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 sync.
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, and publishing makes it the suite’s live set, retiring the one it replaces. Plans themselves aren’t versioned; publishing a new set is how their values change.

Sell several products together

When two products should be bought as one subscription, put them in the same suite and price them there. Under Catalog → Suites, a suite has three tabs: Suite details, Members and Plans.

Add the members

On Members, use Add member to pick the products this suite sells. The order is the sell order, and you can reorder or remove members later.

The dialog offers Merge existing plan(s) into this suite, on by default. Most products you add already have plans of their own: a company sells product A, sells product B, and later decides to bundle them. With the box ticked, the product’s existing plans come with it instead of you retyping them:

• A plan whose name already exists in the suite (Pro joining a suite that already has Pro): the product is merged into that plan.
• A plan with no match is added as a new plan, carrying just that product.

If the product’s plans are ambiguous — it already belongs to more than one other suite — the merge is skipped and the product is added, so nothing is guessed on your behalf.

Price the members together

On Plans, each plan is a column and each member gets its own block of feature rows with an Included switch per column. Switch a member off for a plan and the customer on that plan gets none of its features; switch it on and the plan’s values apply.

Saving works as it does for a single product: editing a published revision creates a draft copy and moves you onto it, so customers stay on the published one until you publish the draft.

Reduce the number of plans

To combine two plans, rename one to the other’s name. Renaming Basic to Home when Home already exists offers to merge them: confirm and everything Basic configured moves into Home, and the Basic column is removed.

Home — the plan you renamed into — is the one that survives, and it keeps its own values. Where both plans configured the same product, Home’s values are kept and Basic’s are dropped; where only Basic had a product configured, that product moves across. Decline the merge and the name reverts.

Package an add-on

An add-on is feature choices for one suite, granted on top of an entitlement’s existing plan — never a starting point.

Under Catalog → Add-ons:

1. Create an add-on and open the Editor to choose its suite scope and the features it includes.
2. Use the Report view to see how the add-on is being used.
3. Publish it. Add-ons have their own lifecycle — Draft → Published → Archived — with Move to Draft, Archive and Unarchive to manage it. Only a published add-on can be granted.

Plans vs. add-ons — which when?

• A plan sets values and limits for the features of everything its suite sells, and is what an entitlement is assigned when it’s created.
• An add-on is granted by Sales on top of an entitlement’s existing plan — a repeatable package instead of picking features one at a time.

If you only need plans, a plan set is enough. Use an add-on when you want a repeatable package to grant alongside a plan.

Next

• Sell it → Author & publish entitlements
• The model in depth → Suites, Plans & plan sets and Add-ons