Entitlements
Testing a New Plan Means Testing Access, Not Just Prices
By the Orvlin team · · 2 min read
Testing pricing and entitlements: what to decide
Finance signs off on the calculator, then the launch reveals that a paid add-on is available to every trial. Pricing and access are two views of the same commercial promise, so release checks should cover both.
Build scenarios for new accounts, existing accounts, negotiated overrides, trials and mid-period changes. Verify effective access through the product, not only through a catalog preview. Then compare the measured usage with the expected charge.
An illustrative case
A new plan includes advanced exports and 5,000 units. The test account should be able to export, see the correct allowance, hit the intended boundary and receive the agreed overage treatment. Testing only a zero-usage invoice misses most of that behavior.
The important caveat
A happy-path test account can hide stale caches or delayed transitions. Include recently upgraded and downgraded accounts, and check the state after asynchronous updates finish.
Review these decisions
- Write expected rights beside expected amounts.
- Test boundary quantities and denied actions.
- Include custom-contract accounts.
- Verify the same scenario through product and invoice views.
Frequently asked questions
- Who should approve a plan launch?
- Product, finance, engineering and sales each own part of the promise. Use named approvals for access, calculations, reliability and customer-facing terms.