ShipRev

Use cases

Use cases

Tasks done end to end with ShipRev, from the plan in the catalog to the ruling in your backend and what your frontend shows. Each names the products it uses.

Each use case takes one task from start to finish: the capability and plans you define in the catalog, what your backend rules on and reports, and what your frontend shows. Pick the one closest to what you want to build; each ends with steps to try it on test organizations before real customers see it.

Gate a feature by plan

Only paid plans get a feature; everyone else is refused and offered the plans. Uses Subscriptions and Entitlements.

Set a monthly usage limit with an upgrade prompt

Your free plan includes 100 uses a month, and the next one is refused with an offer of a larger plan. Uses Metering and Entitlements.

Change a price without touching code

New subscribers get a new price and allowance, and existing ones keep theirs. Uses Subscriptions.

Sell team plans to business buyers

A customer's team subscribes once, invites colleagues by email and shares one allowance. Uses Identity and Metering.

Before you pick one

The use cases assume you have an application and a backend connected with the Server SDK, as in Connect your backend with the Server SDK, the third of the five pages in ShipRev Cloud, step by step. The objects they rely on, and how they meet on one customer record, are in How ShipRev works.

Each product has its own section with the guides behind these steps: Identity, Subscriptions, Metering and Entitlements. The documentation home is ShipRev documentation.

© 2026 ShipRev