Update products on subscriptions with future-dated removals
You can create an Update Product amendment even if there is already a future-dated Remove Product amendment on the subscription.
For example:
- A customer subscribes to your Basic Service for one year starting on January 1, 2018.
- In July, the customer wants to remove the service on a future date, January 1, 2019 to avoid the subscription is renewed automatically. So you create a future-dated Remove Product amendment by setting the effective date to January 1, 2019.
- In August, the customer wants to upgrade to your Premium Service starting on October 1, 2018. So you create an Update Product amendment by setting update date on October 1, 2018.
The following table lists the services your customer has subscribed to:
| Service Name | Effective Date and End Date |
|---|---|
| Basic Service | January 1, 2018 - September 30, 2018 |
| Premium Service | October 1, 2018 - January 1, 2019 |
You can create an Update Product amendment before a future-dated Remove Product amendment on the subscription in Zuora UI, SOAP API, and REST API.
Using the Zuora User Interface
You can use the Zuora UI to update a product even when a future-dated Remove Product amendment already exist on the subscription.
When you update a product, select the Show removed products check box before selecting a product to update in the Amendment Detail panel. The products with Remove Product amendments are shown in the select product list. The following figure shows a rate plan that has a Remove Product amendment on the subscription.
Using the Zuora APIs
You can use Zuora SOAP API and REST API to update a product even when future-dated Remove Product amendments already exist on the subscription:
-
For SOAP API, see the Updating a Product use case and follow the instructions based on your WSDL version.
-
For REST API, use the Update subscription method.
See Using the Zuora API to Update a Product for more information.