Subscriptions Ideas

TrixabelleCP · ‎01-17-2021

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.

Terue · ‎10-05-2020

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.

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.

fredkao · ‎08-04-2016

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!

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

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.

peterscheen · ‎03-28-2017

We have a general problem with the dates in zuora. We have a lot of customer that sometimes order wrong amount, wrong type of users, more of the same user in the same month and such. So the problem are that we aren't aloud to add on more users and so with an earlier contract effective date than the last customer acceptance date (on the same product/user). This is incredibly important for us as we have many customers who like to order the same product / users multiple times during a month and we then get problem with the admission with regard to the dates.

ASchwarz · ‎03-27-2019

As soon as you cancel a subscription or remove a product with a future contract effective date you are not able to update it as it is not shown anymore when creating a new order. To effectively update such a product you would need to delete the order and create a new one to get the changes effective. But you can only delete orders if no other order was created afterwards. So sometimes we need to redo a lot of orders to apply a change to one specific item. With amandements this was possible as you can see in this article: https://knowledgecenter.zuora.com/BC_Subscription_Management/Subscriptions/E_Changing_Subscriptions_Amendments/A_Create_Amendments/Update_a_Product_(Amendment)/Update_a_Product_on_Subscription_with_a_Future-dated_Remove This feature would be really helpful as subscriptions often change and we cannot always go with the described workaround and delete orders as usually with an order an invoice is created and then we even need to cancel invoices to proceed which is definetly not the correct way.

peterscheen · ‎11-23-2017

HI Is there any way or will there be an opportunity to be able to uppgrade or downgrade multiply different users/products on 1 singel amendment? As fare as i know, today there's only possible to add or downgrade 1 specific type of users or products pr amendment

Charles · ‎11-12-2016

Seems like the best practice is to implment Purchase Order (PO) at subscription level. How about adding standard field for Purchase Order (PO) on subscription object.

vithiyatheva

Some product rate plans and product rate plan charges have a custom field. That custom field has a default value depending on the product in the product catalog. However, when creating a subscription, that default value for the rate plan and rate plan charge is not inherited. It would be nice to have that default value from the product catalog inherited when it is created in a subscription. Thank you

alexandrinap · ‎01-20-2021

Use Case: Our company would like to capture the date when a cancellation on a subscription is processed in Salesforce as business processes such as retention efforts are triggered by the 'Cancellation received date' that we usually store in Zuora's Customer Acceptance Date in the Amendment subscription. Problem: In the current Zuora 360 setup when a subscription amendment is created and synced to Salesforce, the original version of the subscription is deleted , and a new subscription with a new Salesforce ID is created in Salesforce. Meaning we are losing the change on the original subscription and can't go via subscription history.

salmdo · ‎12-02-2020

Hi, AS we know that Zuora is integrated with Salesforce and we have some issues with states. If the country is Canada or the United State, it works well cause Zuora has a state picklist and we are ensured to have a valid state. And now, we can't import a state list for another country. It's so helpful if we can develop this feature then we won't need to parse complexly the state between these systems. Regards,

salmdo · ‎09-02-2020

Hi, I would like to recommend removing some special characters in the account, contact fields (name, first name, last name, custom fields,...) Because we can build a workflow to sync Zuora account from Zuora to SFDC automatically by Salesforce API but the special characters make errors sometimes. We need to move them manually and it's so hard to monitor. Regards,

Karina · ‎05-24-2020

In our company we use Product Features to provision customers access to the software they are subscribing to, or to get specific support agreements. So we have developed integrations towards different provisioning platforms based upon Product Feature entitlements. We find that Zuora lacks a few essential features to retrieve subscription product features. This forces us to find workarounds, often resulting in inefficient solutions that both require much effort to build and increase the data traffic from Zuora unnecessarily. Zuora would add alot of value for us if you could provide a "Get subscription product features by account" method in the REST API featuring segmenting like charge-detail in the existing "Get subscriptions by account" https://www.zuora.com/developer/api-reference/#operation/GET_SubscriptionsByAccount A workaround like running the Data Query functionality might be our best option right now, but I would still like to check if Zuora will consider to enhance/extend the API to support this. Thank you Karina 🙂

roantondtt · ‎02-05-2020

The 'GenerateInvoice' setting in the 'Subscribe' API is a boolean (Y or N) This doesn't allow control on what is done with the invoice, as it's directly posted There should be the option to generate the invoice in Draft, in order to be able to execute custom validations or set certain values before it's posted For example, add a new optional boolean setting 'Autopost' in the object 'Subscribe InvoiceProcessingOptions' The functionality would be: GenerateInvoice = Y and Autopost not present --> Post invoice. The ProcessPayment setting will be considered. GenerateInvoice = Y and Autopost = 'Y' --> Post invoice. The ProcessPayment setting will be considered. GenerateInvoice = Y and Autopost = 'N' --> Keep as draft. The ProcessPayment setting will be ignored.

nicksinyakov · ‎07-17-2019

Hello guys, We have found that Subscriptions-Invoiced tab under Subscriptions & Amendments shows only 5 records and doesn't have Sort and View All buttons. It's not convinient and confusing when you have 5+ Subscriptions-Invoiced. P.S. I know that to view all these Subscriptions-Invoiced I have to click Subcriptions-Owned tab and tick " Include subscriptions belonging to all child accounts of this customer account". Maybe it's good idea to add Sort and View All buttons to the Subscriptions-Invoiced tab as well?

roantondtt · ‎05-14-2019

Our customer finds not usable that the selection mechanism for products in the subscription screen is a picklist without scroll. At least it should have a scroll. But the idea would be something more usable, like a pop-up window that allow searching, filtering and ordering by different criteria (not just the name), that allow to preview the charges that correspond to each product selected on the list and that allow multiple product selection.

Yoshihisa · ‎03-29-2019

Currently, TCV is calculated as described in the article below. https://knowledgecenter.zuora.com/BC_Subscription_Management/Customer_Accounts/A_How_to_Manage_Customer_Accounts/E_Key_Metrics/B_Total_Contract_Value Because of the current design, it can happen that the TCV value is different from the value in Invoice. Therefore we got requests that following options are needed to calculate TCV so TCV value and the value in Invoice can be aligned. Option 1, The option "When prorating a month, assume 30 days in a month or use actual days?" is needed to we can select "Assume 30 days in a month" or "Use actual number of days". Option 2, In current design, TCV is calculated based on the charge's trigger day, while the invoice items are calculated based on the charge's billing day. We need an option to select whether TCV is calculated based on the charge's trigger day or based on the charge's billing day.

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

Default Price Change for Product Charges: Percentage - round uplifted prices to set 2 decimal places

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

Support for changing trigger dates using orders

Improve suspend and resume options for subscriptions

Upgrade / Downgrade Amendment

Add OriginalId and CancelledDate to REST Subscription API

Inability to Remove Renewal Amendments

Contract effective date and customer acceptance date problem

Update a Product on Subscription with a Future-dated Remove with Orders enabled

The ability to remove different users with 1 amendment

Add Standard field on Subscription object for Purchase Order (PO)

Support default value for custom fields from the product catalog

Zuora 360 - capture Customer Acceptance Date of Amendment in Salesforce

Import states for another country

Remove special characters in Account, Contact

Get subscription product features by account - method

'GenerateInvoice' setting on 'Subscribe' API should be able to generate the invoice in 'Draft'

Why Subscriptions-Invoiced shows only 5 records

Product selection in subscription creation should be more sophisticated than an unscrolled picklist

Need more options to calculate TCV

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