Docs menuPricing plans

Pricing plans

A pricing plan sets how buyers pay for a Marketplace package and who gets access to install it.

Before you create the first plan, connect an active Stripe payout account. Then, in the package dashboard, open Settings > Distribution & monetization. Select Marketplace to show the Payout provider and Pricing plans fields. Select New plan to add a plan.

Plan fields

FieldSupported values
TypeOne-time fee or subscription
Price (USD)At least $0.50
Billing intervalMonthly or annually, for a subscription
License typeIndividual (per seat) or Organization (unlimited)
Commercial license (allows bundling)Optional

A package can have several active plans. For example, an author can offer an individual monthly subscription, an individual one-time purchase, and an organization yearly subscription at different prices.

Individual licenses

An individual plan has a price for each person.

BuyerQuantityAccess
Personal account1The buyer gets access after the payment completes
Organization1 to 1000 seatsOwners or admins of the organization assign the seats to members

Individual seats for an organization do not give access to every member. An owner or an admin assigns each seat during checkout, or later on the Licenses page of the organization.

Organization licenses

An organization plan has one flat price for the whole organization:

  • The buyer must select an organization.
  • Only an owner or an admin of the organization can complete the purchase.
  • Checkout always charges a quantity of one.
  • All current members of the organization get access.
  • Members who join later get access through their membership.
  • The license does not use seats.

You cannot buy an organization license for a personal account.

One-time and subscription billing

After the payment completes, a one-time plan gives access to the package with no end date. Access lasts until the purchase is fully refunded or the access is revoked.

A subscription plan gives access for each billing period that the buyer paid. A buyer can cancel the subscription at the end of the current period. Before the period ends, the buyer can resume the subscription.

Neither billing model limits access to the version or major version that checkout showed. Access applies to every available version of the package.

Commercial plans

To make a commercial plan, select Commercial license (allows bundling) when you create the plan. A buyer of a commercial plan can bundle the package inside the buyer's own Marketplace packages. LPM.dev Registry checks for this license when the buyer publishes. A package can have only one active commercial plan.

The option records a permission in LPM.dev Registry. It does not create a license agreement, and it does not add dependency files to a publish tarball. Read Commercial licenses before you offer or buy a commercial plan.

Plan lifecycle

You cannot edit a plan after you create it. To change the price, type, billing interval, license type, or commercial option of a plan:

  1. Create a new plan with the new terms.
  2. Archive the old plan.

To replace a commercial plan, archive the old commercial plan first, because a package can have only one. If it is the only active plan of a Marketplace package, create a plan without the commercial option first.

Buyers cannot start a new checkout with an archived plan. One-time purchases of the plan stay valid unless they are fully refunded. Existing subscribers keep access to the package for each paid period. If the plan is a commercial plan, they also keep the Commercial License for each paid period. An expired or unpaid period does not give access.

After you choose Marketplace distribution, you cannot archive the last active plan. This rule applies before the first release is approved too. If a checkout for the package is in progress, you cannot archive any of its plans. Try again after the checkout finishes, or after its 15-minute reservation expires.

Activation order

For a package that is still private:

  1. Connect the Stripe payout account of the package owner.
  2. Create at least one active pricing plan.
  3. Choose Marketplace distribution. LPM.dev Registry sends the latest version to publication review.

The package stays private until a release is approved. Distribution modes explains review and activation.

See also