Rate plan removal from subscription with future-dated removal
This topic explains how to remove a rate plan from a subscription when a future-dated Remove Product order action already exists, and how the system behaves based on different effective dates.
You can create a Remove Product order action even if there is already a future-dated Remove Product order action on the subscription. The feature is supported through the Orders UI and REST API.
Once a rate plan charge has been removed from a certain effective date, if you are going to perform another Remove product order action on the same charge, the system has the following behaviors based on the effective date of the second removal:
If the effective date of the second removal is earlier than that of the first removal, the system supports it as described in this article.
If the effective date of the second removal is the same as or later than that of the first removal, the system behaves in the following manner:
A new subscription version will be created as a result of the second removal.
The second removal will take no effect and the end date of the rate plan charge is still set as the effective date of the first removal.
For example:
A customer subscribes to your monthly service for one year starting on January 1, 2022.
In March, the customer wants to remove the service on a future date, July 1, 2022. So you create a future-dated Remove Product amendment by setting the effective date to July 1, 2022.
In April, the customer wants to remove the service starting on May 1, 2022. So you create a Remove Product amendment by setting the removal date to May 1, 2022.
The following table lists the order actions your customer has applied:
|
Order Action |
Effective Date and End Date |
|---|---|
|
Create Subscription |
January 1, 2022 - December 31, 2022 |
|
Remove Product before a future-dated Remove Product |
May 1, 2022 - June 30, 2022 |
|
Remove Product |
July 1, 2022 - December 31, 2022 |