Destroying Canceled Subscriptions
A subscription is destroyed in CloudBlue Commerce means that the subscription cannot be restored and the service can no longer be used:
- A request is sent to the service vendor's system to destroy the service on the vendor's side, for example: terminate a VM, delete a tenant, unassign an IP address and so on. The request is processed on the vendor's side according to the vendor's policies.
- In Billing, the subscription status becomes Terminated and the service status becomes Removed. The subscription billing data is preserved in the Billing database for audit purposes.
- In Operations, immediately after a subscription is destroyed, it is assigned the Terminated status. Then, the subscription management data is deleted from the Operations database according to the retention policy.
Using the settings below, you can define subscription cancellation and termination policy in the following ways:
- No destruction policy: Retain canceled subscriptions so that they can be restored at any time after cancellation. Such subscriptions can also be terminated manually at any time.
- Automatic destruction policy: Destroy canceled subscriptions automatically.
To destroy a canceled subscription manually:
-
In the Provider Control Panel, go to Billing > Subscriptions. Click the necessary canceled subscription with Service Status = Stopped.
-
Click Destroy. The subscription becomes terminated when the service status changes to Removed.
Cancellation and Destruction Settings
- Service template settings:
- Destroy Service on Cancel: configurable for both Billing and Operations service templates
- Collect resources usage after subscription cancellation (days): configurable for Operations service templates only
- Service plan settings:
- Service Terms settings:
- Destroy Service after Hold Period
Cancellation and Termination Scenarios
Scenario 1. Cancel a Subscription and Terminate the Service Immediately
If you want a subscription to be canceled without delay and then the service to be immediately destroyed, configure the settings in the following way:
Service Type: | Various Classic Services | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A:
|
Scenario B:
|
General Configuration: |
The Service Plan is based on: |
|
Important Properties: | ||
Yes | ||
0 days (or not set) | ||
N/A* | ||
N/A* |
*These settings do not affect the result and can have any valid values.
Scenario 2. Cancel a Usage-based Subscription, Process the Usage, and then Terminate the Service
For usage-based services, if you want to process usage data after cancellation and issue an invoice first, and only then to destroy the service, configure the settings in the following way:
Service Type: | Classic Usage-based Services | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A:
|
Scenario B:
Note: This scenario is not recommended because delaying cancellation is redundant: usage data is processed by Vendor-rated Data Manager independently, an active subscription is not required. |
General Configuration: |
|
|
Important Properties: | ||
Yes | ||
X days | ||
N/A* | ||
N/A* |
*These settings do not affect the result and can have any valid values.
Scenario 3. Cancel a Subscription and, After a Suspension Period, Terminate the Service
For various service types, including usage-based services, if you want to process usage data after cancellation and issue an invoice first, and only then to destroy the service, configure the settings in the following way:
Service Type: | Classic Services and Usage-based Services with Real-Time Usage Collection | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A*:
|
Scenario B:
|
General Configuration: |
|
|
Important Properties: | ||
No | ||
0 days (or not set) | ||
Y days | ||
Yes |
* This scenario does not apply to usage-based services with delayed usage collection.
Scenario 4. Cancel a Subscription and, After a Suspension Period, Give Customers a Chance to Restore It
For both non-PAYG and usage-based services, if you want to give customers a chance to restore canceled subscriptions or, alternatively, to terminate them manually at any time after cancellation, configure the settings in the following way:
Service Type: | Non-PAYG Services | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A:
|
Scenario B:
|
General Configuration: |
|
|
Important Properties: | ||
No | ||
0 days (or not set) | ||
Y days | ||
No |
Scenario 5. Cancel a Classic PAYG Subscription, Postpone Cancellation to Process the Usage and then, After a Suspension Period, Terminate the Service
For classic usage-based services, if you want to postpone cancellation to process the usage and then, after a limited suspension period after the cancellation, terminate the service automatically, configure the settings in the following way:
Service Type: | Classic PAYG Services | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A:
|
Scenario B: The configuration below is irrelevant for this service type. |
General Configuration: |
|
|
Important Properties: | ||
No | ||
X days | ||
Y days | ||
Yes |
Scenario 6. Cancel a Classic PAYG Subscription, Postpone Cancellation to Process the Usage and Then Freeze the Subscription Until It Is Manually Restored or Terminated
For classic usage-based services, if you want to postpone cancellation to process the usage and then suspend the subscription indefinitely until it is manually restored or destroyed, configure the settings in the following way:
Service Type: | Classic PAYG Services | Usage-based Services with Usage Rated on the Vendor's Side |
Cancellation Scenario: |
Scenario A:
|
Scenario B: The configuration below is irrelevant for this service type. |
General Configuration: |
|
|
Important Properties: | ||
No | ||
X days | ||
Y days* | ||
No |
*These settings do not affect the result and can have any valid values.