Suites

A suite is what you sell. A product is what you build. Most of the time those are the same thing, and you never have to think about the difference — but once you sell two products as one subscription, they are no longer the same thing, and the suite is the piece that lets you price them together.

A suite is a group of products sold together, and it owns the plan sets that price them.

Selling several products as one subscription

Say you sell a design tool, a publishing tool and an analytics module. You want three plans — Home, Pro, Enterprise — where every plan includes the first two, and only Enterprise includes analytics. Upgrading to Enterprise should unlock analytics without anyone touching the customer’s grant by hand.

Put the three products in one suite, and its plan set does that. A plan decides, product by product, whether that product is included and what its features are worth:

Plan	Design tool	Publishing tool	Analytics
Home	5 seats	5 seats	not included
Pro	25 seats	25 seats	not included
Enterprise	Unlimited	Unlimited	Included

The upgrade from Home to Enterprise is an ordinary plan change. Nothing about analytics is treated specially — it is included in one plan and left out of the others.

Every product already has one

You do not have to create a suite to price a single product, or to build an offer for one. The first time a product gets a plan set — or the first time you create an offer for it — a suite holding just that product is created for you, named after it. So pricing one product is unchanged, and nothing asks you to make a suite first.

Those suites stay out of the way. The Suites page lists the offerings you built, not one row per product you priced — so a vendor selling nine products separately sees an empty page until it assembles something. Turn on Show product suites in the page’s filters when you want to see them anyway.

Once you add a second product to one, the suite appears on the page permanently: at that point it is an offering someone assembled, which is what the page is for.

That is why there is only ever one way plans are scoped. A single-product plan set and a nine-product plan set work the same way, so every rule below holds for both.

What a plan does to each product

A plan lists each product in the suite and says whether it is included.

• Included — the plan’s values apply to that product’s features, exactly as a plan always has.
• Not included — the customer gets none of that product’s features from this plan.
• Not listed at all — treated as not included. A product added to the suite after a plan was written is left out of it until you say otherwise, which is the safe default.

Applying a plan sets each included product’s features to what the plan says. A product that was excluded from the old plan and is included in the new one comes back at the new plan’s values, not at whatever it was left holding.

Note

State a Denied feature in every plan that should deny it. Applying a plan resets what it governs, so a denial written in one plan does not carry over to the next.

An excluded product still activates

A customer on Home can still install and activate the analytics module. It activates successfully and receives no analytics features, because the plan grants none.

That is deliberate: the application starts, sees it received no features, and can show its own upgrade prompt. Refusing the activation outright would leave the customer at an error screen instead of an upgrade prompt.

One live plan set per suite

A suite’s plan sets move through Draft → Published → Retired, and publishing one retires the suite’s previously published set — so a suite has exactly one live lineup at a time. Two suites that share a product each keep their own, and neither disturbs the other.

What a customer gets

Assigning a suite to an entitlement is what puts products on it. The entitlement licenses the suite’s products — no more, no less — so the products a customer holds and the plans you may sell them always agree.

Changing an entitlement’s suite swaps its products for the new suite’s products in one step, and clears the plan: the new suite’s plans are not the old one’s. Removing the suite detaches everything, which is how you empty an entitlement without picking through it product by product.

How it relates

• Groups → one or more products, in sell order.
• Owns → its plan sets, and through them every plan it sells.
• Packaged by → an add-on, which overlays the suite itself and stays grantable across its plan sets.
• Granted through → an entitlement, which carries the plan that is in effect and the suite that governs it.

Next

• Build one in the portal → Plans & add-ons
• The plans themselves → Plans & plan sets