Subscription Change Requests
Use this page when a tenant wants to change a plan, trial, module, limit, or billing arrangement.
Self-service billing is not production-ready
Self-service paid upgrades, subscription invoices, online collection, automatic renewal, credits, discounts, and proration are not production-ready.
Current Support-Led Process
Until commercial self-service is implemented, subscription changes should go through an approved support or platform operations process.
- Identify the tenant and outlet context.
- Record the requested change.
- Confirm whether the change is plan, trial, entitlement, usage, billing, or support-policy related.
- Confirm commercial approval before changing account state.
- Record the reason for the change.
- Confirm the expected customer-facing impact.
Common Requests
| Request | Current handling |
|---|---|
| Start or extend a trial | Support/platform-led, with reason and history. |
| Convert trial to paid state | Foundation supports conversion, but billing collection is separate. |
| Upgrade plan | Foundation can represent plan change; quote, payment, and proration are not production-ready. |
| Downgrade plan | Requires product policy for effective date, data access, and feature restriction. |
| Add outlet/device allowance | Commercial pricing and enforcement are not active yet. |
| Add a paid module | Commercial module add-ons are planned, not active billing items. |
| Request invoice | Subscription invoicing is not production-ready. |
Information To Capture
- Tenant name or identifier.
- Requested change.
- Effective date requested.
- Reason for change.
- Commercial approval status.
- Whether feature access should change immediately or later.
- Any support notes needed for the tenant.
Data Safety
Do not put payment card data, passwords, private keys, or secrets in support notes or subscription-change evidence.