Subscriptions Ideas

Terue

For Japanese users, “Subscription start day” callout is always triggered on next day. Ex. if the service start date is Oct 1, the callout is triggered on Oct 2 in JST*. (*) AM 9:45 Oct 1 (Los Angels) = AM 0:45 Oct 2 (Tokyo) This is because Zuora callout based on the system date as it is described in KC. This is critical issue for our customers that their end-users cannot start using their service on time. The trigger timing for the events such as “Subscription Start Date” , “Term Start Date ” should be consider the business timezone.

Menelion

Hello, Currently the status for canceled subscription is *cancelled* (with a double L). Whether it is British spelling or a typo, it should be consistent with other statuses (like, for instance, the corresponding status for invoices is *Canceled*). this might lead to confusion and hard-to-catch bugs in API implementations. As there are quite a number of current implementations already, I would suggest to support both *canceled* and *cancelled* for some time, before a breaking change could be possible. Thanks.

perswardh · ‎06-12-2018

Currently there are no support for changing trigger dates (Contract Effective Date, Service Activation Date, Customer Acceptance Date) using the orders functionality. It is possible using amendments but not orders. This is needed when unintentiallly setting the wrong trigger dates when creating subscriptions using orders. See https://knowledgecenter.zuora.com/BC_Subscription_Management/Orders/C_Known_Limitations_in_Orders "Trigger Dates: Once rate plan charge trigger dates are set, you cannot directly update or override the trigger dates."

linus · ‎02-08-2019

Using orders in Zuora Currently Zuora only supports that a suspended subscription can be resumed within a current term. Example: Subscriber has a subscription 3 month termed that will be renewed to evergreen after that first term. The subscriber is allowed to suspend the subscription. This will result in no invoices being created during the suspension. As now in Zuora the subscription needs to be resumed withing that first term. As suggested without this rule the date for resume could be set 5 months from now. When resumed the term would continue as agreed upon. How it is today -Customer buys 3 month termed subscription 2019-01-01 (Will be renewed to evergreen) -Customer is only allowed to suspend subscription withing term 2019-02-01 - 2019-02-28 My suggestions -Customer buys 3 month termed subscription 2019-01-01 (Will be renewed to evergreen) -Customer is allowed to suspend subscription 2019-02-01 - 2019-07-01 (5 months in this case) with action to continue the term after resume true/false (up to company to set true or false). -Customers subscription is resumed 2019-07-01 and from that date the term will continue for another 2 months before it is renwed to evergreen.

nlittlefield · ‎09-01-2017

It would be very helpful for our team to have the option to Clone an existing subscription in the user interface. Ideally it would create a new subscription for that account with all the same rate plans and products assigned to it as the original, having it prompt only for a new contract/activation date.

gelaimr · ‎08-10-2017

Issue: Currently, OriginalID and CancelledDate fields not returned via GET " https://rest.zuora.com/v1/subscriptions/accounts/{account-key}" The customer can use the CRUD call, but they are trying to reduce the number of round trips and complexity of getting all the subscription information. Right now if a user has several subscriptions they need to loop through and get the two additional fields of data for each subscription, if this information could just be returned with " https://rest.zuora.com/v1/subscriptions/accounts/{account-key}" it would reduce complexity. Reference: SUB-5844

vpoliseno · ‎02-17-2017

We'd like to be able to have a template to mass update the following field: Additional Email Addresses Invoice Template Communication Profile to the Account Tax Exempt Certificate ID Tax Exempt Issuing Jurisdiction?

jmorris7 · ‎10-24-2017

Issue: Inability to remove renewal amendments Description: If a customer accidentally renews the wrong account or renews twice we are unable to remove this renewal. This is due to the fact you can't delete an amendment after invoicing/processing a payment. This is causing us to have to cancel the subscription, apply a credit to the account and have the customer repurchase. This happens very frequently and has caused a high level of aggravation for our customers.

jpawlyn · ‎01-24-2018

We contacted support recently to ask about the status of the API /v1/catalog/product/{id} and it turns out that this is an internal API. We would like to use this API but because it is categorized as internal, hesitate to use it for production purposes. If it could be re-classified as a public API and documented that would be great. Jolyon

jbrown · ‎09-15-2016

The Billing Period Alignment options allow for "Align to Charge" and "Align to Term." However, if you want all of your recurring charges to invoice on the same schedule, no matter what the renewal term or billing term, there is no setting. We use "Align to Term" now and if customers have matching Billing Period and Renewal Term (Monthly billing and 1 month Renewal, for example), a mid-term change will generate a prorated invoice for the remainder of the month and then pick up all charges at the next billing period. This works great. But when we have a customer that has Quarterly billing period and monthly renewals for example, a mid-term change misaligns those same charges with the same settings. Since charges are configured by Billing Frequency, we only have the ability to configure our Quarterly charge with one option. So changes for this customer are manual every time.

zedmundson · ‎11-20-2017

We have customers with multiple (about 20) active subscriptions at a time. If we want to cancel a customer account with an effective date, we have to cancel one subscription at a time rather than if the "Cancel Customer Account" feature adding a new pop-up that would let you mass cancel all pending subscriptions. This could be with the same terms for cancelling subscriptions (end of term, last invoice date), but it would be done at a larger scale and saving us time.

bolaurent · ‎01-05-2018

We prefer to keep the subscription name the same as (or related to) the opportunity name in Salesforce. But once a subscription is activated, the name cannot be changed. Sometimes the subscription was manually entered, and the user forgot to set the name, then we get a really terrible name that is meaningless. Or sometimes there is a typo in the SFDC opp name, and it is changed sometime after the Zuora sub has been created. I wonder why Zuora is so rigid about this? Isn't the subscription ID the unique key?

bolaurent · ‎03-23-2017

let me set the order in which productrateplans are displayed (on product page and in dropdown when adding to a subscription)

Kenta · ‎03-15-2018

Currently, the option of 'Enable Automatic Price Change when Subscriptions are Renewed?' only works with Termed Subscription. If a Subscription is designed to be monthly Evergreen, we would have to structure it as 1 Month Term Subscription, which results in a ton of Amendments. I would like to recommend that the option also be compatible with Evergreen Subscription

bolaurent · ‎03-02-2017

I'm experimenting with ways to enter complex deals, and a very talented Zuora SA is working with me. We are entering multiple recurring charges on a rate plan, with each set to end after one billing period. It's requiring significant experimentation to arrive at the result we want. We sure wish, when we need to run the experiment again, we could clone an existing subscription in draft mode and edit the thing. An alternative would be (in sandbox) to allow me to unlock a sub even after it has been activated.

timozuid · ‎01-05-2018

It would be helpfull to get thousand separators in the Quote quantity fields. The reason for this when a customer is in CPM business the offered quantities can be millions and it's hard the work out the number of zero you have to enter.

kcoyne · ‎11-30-2017

We would like to request a different status for our one time only subscriptions once they have billed as techinically they are no longer active. This new status would enhance the team's reporting when searching for truly active subscriptions.

fredkao · ‎05-15-2018

Please make the description field on the rate plan charge editable. Thanks!

waterstorm · ‎02-20-2017

I'm using the product catalog call to return the entire catalog of products to show all available prodcuts in an application. However I'd only need the products currently active (see "Effective Start" and "Effective End"). For subscriptions there is an option in the call to filter for active subscriptions (using ?charge-detail=current-segment). I suggest implementing a similar option for the product catalog, e.g.: ?currently-active=true which should only return products where the "Effective Start" date is after and the "Effective End" date is before the current date.

cplummer · ‎11-15-2016

Currently, if an amend() call is made, the Zuora API will sometimes respond with a 504 - Gateway Timeout. However, the amend continues in the background for an indeterminate period of time until it completes. The problem is that when we receive an error from Zuora, we assume it failed, so we attempt to retry it until it succeeds. This leads to billing the customer multiple times for the same item, since we don't know if it succeeded or failed. We've attempted to use a read-ahead before doing the amendments to ensure that the rate plan charges do not exist on the subscription, but that doesn't work when the amend call is still running in the background for some indeterminate period of time. Since there's no way to know how long is "long enough" to wait for it to finish, the only way for client code to guarantee that something is billed exactly once is to amend until it succeeds, then read the subscription back afterwards and remove duplicate rate plan charges that may have been created accidentally. Since that solution is very onerous to all clients, instead the Zuora amend API should be transactional - that is, if an error code is sent to the client, the entire operation should fail and roll back. This is the typical, expected pattern when it comes to billing software.

Happy Business Starts Here

Vision

Products

Zuora Central Platform

Products

Zuora Marketplace

Solutions

By Industry

By Role

Customers

Resources

Resources

Subscribed

Support

Company

Subscriptions Ideas

“Subscription start day” callout should be triggered on local time

Zuora statuses should adhere to one spelling norm

Support for changing trigger dates using orders

Improve suspend and resume options for subscriptions

Subscription Clone Feature

Add OriginalId and CancelledDate to REST Subscription API

Template to mass update customer account fields

Inability to Remove Renewal Amendments

Make the product catalog API official (/v1/catalog/product/{id})

Add Align to Billing Term Option

Ability to Cancel all pending subscriptions when attempting to Cancel Customer Account

Allow subscription name to be changed

let me set the order in which productrateplans are displayed

Allow Evergreen to use 'Subscription Charge Price increase Following Renewal'

Allow subscriptions to be cloned (at least in sandbox)

Having thousand separators in Quote quantity fields

New Subscription Status

Allow rate plan charge description to be editable

[REST] Add filter possibilities to product catalog call in REST API

Make the amend API transactional

Option to have Fixed Amount Discounts Prorate on early cancellation

Ability to add attachments to subscriptions

Ability to cancel a subscription with an Effective Date in a Closed Accounting Period