In this article
An enterprise customer needs a premium capability while its renewal paperwork catches up. Sales approves temporary access. Someone changes a flag, the customer gets back to work, and the exception disappears into a chat thread. At the next renewal, nobody can explain whether that capability is paid, promised or still on trial.
The problem begins after the commercial decision. Once an exception is approved, the product needs to represent its limits and resolve it deliberately. A temporary grant should carry enough information for the next account owner to understand why it exists and what happens when it ends.
Make the exception narrower than the plan
Grant the capability the customer needs. Avoid assigning an entire higher plan when the agreement covers one feature. A broad switch can unintentionally unlock other capabilities, change usage limits or make the account appear upgraded in reporting.
Use a stable capability identifier and an explicit scope: a workspace, account or named group. Record whether the exception changes access, consumption limits or both. Those are different promises. A customer allowed to evaluate an export feature has not necessarily received unlimited export volume.
Stripe Entitlements maps product features to customer access and provides active-entitlement changes that applications can use to provision or remove capabilities. This supports a useful architectural separation: commercial records establish what the customer receives, while the application enforces the resulting access. The exception still needs its own reason and owner.
Keep one record that survives the conversation
Consider an illustrative reporting product. A customer receives temporary access to scheduled exports while a contract amendment is reviewed. The following is a proposed record, not an actual customer agreement.
| Field | Example entry |
|---|---|
| Customer and scope | Acorn workspace; scheduled exports only |
| Basis | Approved temporary evaluation during amendment review |
| Start and expiry | Explicit timestamps with a named time zone |
| Internal approver | Person authorized to grant the exception |
| Operational owner | Account owner responsible for resolving it |
| Customer commitment | Exact capability and duration communicated |
| Usage boundary | Existing export-volume limit continues |
| Resolution | Paid access, documented extension or return to existing plan |
| Dependent work | Two scheduled reports created during evaluation |
Attach the customer-facing confirmation or its approved wording. A private note saying “extend trial” is weak protection against a different promise made in a call. The record should make disagreement visible while there is time to resolve it.
The approver and operational owner can be different people. The approver establishes authority; the owner does the follow-up. If the owner changes roles, transfer the open exception with the account. It should never depend on someone remembering to search their old messages.
Define expiry as product behavior
An expiry timestamp alone is insufficient. Decide what happens to work created while the capability was available. Can the customer inspect it, export it, edit it or run it again? Does the application stop future scheduled jobs? Is there a permitted grace period, and who can authorize it?
For the illustrative reporting product, one reasonable policy is to preserve report definitions while stopping future premium runs after the agreed access ends. The interface would explain that status and offer the appropriate commercial next step. That policy is a design choice; a different product might need a different transition because unfinished work has different consequences.
Write the behavior before the grant starts. Otherwise, the expiry discussion becomes a hurried negotiation between “leave everything on” and “break the workflow.” The customer should understand what happens to its work without discovering the policy through an error message.
Reconcile overlapping reasons for access
A customer can obtain the same capability through more than one route. It might purchase an eligible subscription before a promotional grant expires. Removing the temporary grant should then leave the paid entitlement intact.
RevenueCat’s entitlement API allows a promotional grant to have an explicit end time. Its documentation also says promotional access operates alongside store transactions rather than replacing them. That is a concrete reminder to distinguish the source of access from the effective access the customer currently has.
In your own system, calculate effective permission from all valid grants under a documented precedence rule. Keep the grant that expired in the history, and verify the remaining access. A cleanup job that blindly turns a feature off can undo a legitimate purchase; a flag that never gets reconciled can keep an old exception alive forever.
Test these transitions with representative account states before relying on automatic expiry. Include a customer who upgrades during the exception, one whose paid access later ends, and one with two overlapping temporary grants. The question is whether the final permission matches the current agreement in each case.
Resolve the exception before renewal turns it into a dispute
Review open exceptions ahead of the customer’s commercial decision. The owner should know whether the capability was used, what work now depends on it and which resolution is being proposed. Usage informs that conversation; it does not silently convert a temporary promise into a permanent one.
Return to Acorn’s scheduled reports. If the customer wants to keep them running, the account owner can present the appropriate paid scope. If it no longer needs them, confirm the agreed end and preserve the definitions according to policy. If contract review is still underway, an authorized extension gets a new expiry and explanation.
An extension should be a new decision in the history. Repeatedly moving a date without preserving the previous decisions hides how long the exception has existed and why the original resolution failed. A series of extensions may reveal that packaging or procurement assumptions need attention.
Make exceptions visible without counting them as sales
Product and commercial reporting should distinguish paid access, temporary access and actual use. An enabled feature is not expansion revenue. A successful premium workflow can demonstrate interest, but the commercial result remains unresolved until the account has the corresponding paid agreement.
Track open exceptions by owner and upcoming expiry, then review those that are overdue or repeatedly extended. Keep the customer commitment beside the operational state. This makes it possible to resolve the backlog without guessing whether removing access would contradict an agreement.
If many customers need the same exception, revisit the pricing metric and package boundary. If the difficulty is getting a clear commercial decision from product interest, improve the product-led sales handoff. For an individual exception, the finish line is concrete: the customer understands the resolution, the entitlement matches it, and dependent work behaves as promised.
Sources
Something we should clarify?
Suggest a correction


