Subscriptions Ideas

Suggestion: Allow renewal prices that have been auto increased to be rounded to 2 decimal places. More info: When " Default Price Change for Product Charges" is set to "percentage increase", renewal prices can end up with more than 2 decimal places which can cause a discrepancy between the calculated totals and the display values, and in our experience this causes confusion for customers and delays in the approval process.  For example: Default price change = 5% Monthly price: $23 Next renewal price = 105% x $23  = $24.15 (this is ok as still only 2 decimal places) Next renewal price = 105% x $24.15 = $25.3575 (becoming problematic as the price used is now 4 decimal places) However I don't want to display $25.3575 on quotes, so it's rounded to $25.36. And now the price that is used in calculations doesn't match the price displayed and assuming you show quantity x period x unit cost on a quote PDF you can end up with discrepancies. Eg. Actual calculation: 10 users x 12 months x $25.3575 = $3042.90 Displayed values: 10 users x 12 months x $25.36 (= $3043.20 if using the displayed values; but $3042.90 if displaying the value Zuora is using)   For a large deals these differences can be significant and we've has customers refuse to sign purchase orders because of it.   My suggestion is to allow the price uplift to be rounded to a set number of decimal places (that matches real-world currencies) and use this number in calculations. I can't think of any scenarios where people want to be charging customers prices like $34.3433533.  ... View more

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.   ... View more

The subscriptions that are not renewed ( either manual or auto) on the renewal due date should be marked as 'expired' once the renewal due date is past. Currently, it continues to be displayed as 'Active' which is misleading. ... View more

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." ... View more

Current functionality with Subscription Amendments in the UI is that only a single Product Rate Plan can be Added / Edited / Removed per Subscription Amendment. This results in multiple amendments to start, amend, or end a subscription when multiple rate plans are being processed together. It would be very useful to be able to Select Multiple Specific / All when Remove Product amendment is selected, and be able to add / edit multiple rate plans per New Product / Update Product amendment. ... View more

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. ... View more

  Create a new amendment type of "Upgrade" or "Downgrade" that combines a Remove Product and New Product amendment.  This would be more convenient than trying to figure out if the two amendments (Remove + New) are related and what direction (Up or Down) the change is going.   Currently, we use delta MRR to see if it's an upgrade (positive MRR) or downgrade (negative MRR).  But there are some cases where the delta MRR is 0, but from a product standpoint, it may be an upgrade or downgrade.   Thanks for reading! ... View more

Currently contracted MRR shows amount without discount and doesn't consider discount sku amount. It should be amount after applying discount. In the following example it is showing 10,080/12=  840 however, it should be really 10,080-2,580= 7,500/12 = 625. Please look into this !     ... View more

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.   ... View more

We are just coming into Zuora, and we have many scenarios where our customers may have multiple products with multiple different renewal dates.  This is translating into multiple subscriptions as we get them loaded into the system.   Going forward, our reps would love to be able to combine and co-terminate these subscriptions to make things simpler for our customers where possible, but at the moment we're telling them that they have to manually transfer all of the lines from the old subscriptions to the new subscriptions because there is no capacity to join these together.   This would be a great help for us, and I'm sure for many other new customers coming on to the Zuora platform! ... View more

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. ... View more

The problem we are facing is that--today--our only mechanism for adding new products (and rate plans, charges) and updating products/rate plans/charges is through the UI. This can be prone to human error as each entry must be keyed in separately and manually. We will be adding and updating Products/rate plans/charges at an increasing frequency and manual keyed entries will not scale. We would like a bulk update tool that is usable by a business/non-technical user. Without diving too deeply into a solution, I believe we would be well served by having a simple tool that accepted, validated, and set up new and updated items through some upload process--for example of a comma-separated value file--with manual steps only to verify the data to be added/updated. This could be through the UI or a RESTful API. Another possible solution could be more of a "grid-view" into the products/rate plans/charges that allow for multiple data entries on a single pane of view, but this may not be effective for certain use cases.   ... View more

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? ... View more

Use case: Looking for a feature that will merge two accounts into one.  Customer have had a couple of customers who purchased subscriptions, using their personal emails. Some time later, after the first subscription expired, their work or family member purchased another subscription for them, using their second email. So now, they are contacting us, saying "I would just like to use my personal email address to login and use my subscription". Since they are using internal user IDs in our system, as account number, they cannot change it (as it is not possible in our system). So they customer is stuck with two separate accounts now. They are just hoping to consolidate the two.   Work around to consider: Making the account 1 (personal email) the invoice owner of all the subscriptions created for account 2 (second email). I suggested this as a work around since I am assuming that all the data except for subscription(s) will be the same for the two accounts so moving forward, all invoices that will be created for account 2 will just go to account 1.   However, DE8261/BIL-2981 is created so that we can enhance our application that will have an ability to merge accounts into one. This is currently being review by our Product Management.  ... View more

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     ... View more

Feature Request:   The client has reported the following quirks in the Zuora UI. They are not show-stoppers, rather quality of life issues that make "managing the Zuora product catalog an unpleasant experience". When viewing the product catalog, the List View only shows 6 items at a time unless you click the Expanded View tab and then move back to the list view tab, then it shows 25 items. Why can't it show 25 items by default? Proposed Solution - Make the product catalog via show 25 items by default After selecting a catalog view, if you then select an item in the catalog and then select ‰Û¡ÌÝÌ back to Product Catalog List‰Û¡ÌÝå , you are not brought back to the view you left, but are instead brought back to the default catalog view. This makes managing the product catalog maddening when you have lots of products, especially when combined with the next item. Proposed Solution - Selecting "back to Product Catalog List" should take users to the previous view, not the default view When selecting a catalog view, it takes two clicks (4 if you count clicking between expanded and list views) to get to the view. You must first expand the items under Base/Addon/Misc, and then select Current underneath. It would be much better to just select (for instance) Base Products and be shown all the active base products. Proposed Solution - When selecting a catalog view, users should be able to just select, for instance, Base Products and all active base products should be shown. The number of clicks should be reduced. It would be helpful to us if we could define additional product categories. For now we are just dumping all the categories not supported under misc, but it would be better if we could define new categories and have them show up under Catalog Views. This would make it much easier to manage things like hardware, setup fees, etc. Proposed Solution - Users can create custom product categories Reference Number:  DE7635 Business Need: Users are spending more time than needed to navigate through the product catalog. ... View more

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. ... View more

In current UI functionality if a One-Time rate plan charge has been added to a subscription but not yet billed, there is no way to Amend the value of the One Time Fee. The Update Product amendment will not allow you to change either the price or quantity. While I can understand this if it was already invoiced, not being able to update an unbilled One-Time fee is a real issue. The only workaround i have been able to find is to remove the product and add it back again, requiring two amendments (Remove Product and New Product) instead of one (Update Product). ... View more

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 ... View more