Feature Request: Ability to to edit the included units for Rolling Window charge in an Amendment
Status: currently being review by our Product Management
Reference Number: DE8310
Business Need: customer Z have customers who sign up for annual bundles. Because the bundles are annual they use the rolling window to keep track of their usage each month, so when they do go over their bundle amount they can charge them for overages. In some case when the customer goes
over their bundle amount they purchase an additional add-on amount to the original bundle amount. So now they have a new usage amount to track for the remainder of the term. This is why they are requesting if we can have a feature to amend the subscription to update the rolling window amount.
Client is implementing CORS REST Create Account and requires a weekly subscription term length. initialTermPeriodType and similar fields are not available, but only available in the Create Subscription call which DOES NOT support CORS REST.
Please keep the two API calls in sync. Thanks
Feature Request: Currently, subscription's Mass Order Entry does not support custom fields. Zuora should allow users to include custom fields in subscription's Mass Order.
Reference Number: DE7918
Business Need: Users may want to import custom fields to when using subscription's Mass Order Entry feature.
Feature Request: Add the ability to have proration at the subscription level
Status: Currently being reviewed by our Product Management
Reference Number: PMT-1074
Business Need: Currently Zuora proration only applys on tenant level, but can not be turned on and off at the subscription level. Customer wants to apply proration on certain subscriptions but not others.
Feature Request: Expose CreatorAccountName & CreatorAccountNumber fields in the Subscription object in Data Source
Reference Number: DE9982
Business Need: Currently, only CreatorAccountId field is exposed in Subscrition object, however, it will be great if CreatorAccountName and CreatorAccountNumber fields can be exposed. In this way, customer only need to query one object to get all the info.
Feature Request: Right now in SFDC, under a quote, we have the following.
- Start Date = Zuora's Contract Effective Date and Term Start Date
- Service Activation Date = Zuora's Service Activation Date
- Customer Acceptance Date = Zuora's Customer Acceptance Date
Users cannot set Contract Effective Date and Term Start Date separately. We should add another field in SFDC called Term Start Date and this field should set the date for the Term Start Date in Zuora.
Reference Number: DE7636/PMT-111
Customers have some cases in which they want to the contract to start on one day but actually charge the customer on a later day. The problem is that in SFDC they cannot set Contract Effective Date and Term Start Date different from each other. As a result, if the subscription have
- Contract Effect Date / Term Start Date on 01/01/2011
- An Initial Term is 12 months
- An annual product charge starting on Service Activation Date which is 02/01/2011
Zuora only charges for the product from 02/01/2011 to 12/31/2011 (11 months) because the subscription itself ends on 12/31/2011. Customers want to charge for the product from 02/01/2011 to 01/31/2011 (a whole year) instead.
When trying to solve issues with Product Catalog discrepancies, it's difficult at a glance to tell what the rate plan name is.
Zuora should add a resizer to that column in the UI in the multi-currency popup view to reduce time and maintenance in trying to get that information from Data Sources. Surely this is an easy change.
in B2C businesses we often find that we need to cancel a subscription due to nonpayment ... An issue arises when a customer then makes a payment on the open invoice. We are unable to remove a cancellation once it is made. If we were able to remove the cancellation it would allow us to reinstate the subscription service without overly complicating the data with a newly created subscription.
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.
Issue: Ability to see which products in a search result list view are expired
Reference Number: DE8665
Business Need: When search result contains a lot of products, it is very difficult to view it in Expanded View. List View provide a simply UI, but this view didn't have status column. Without status, it is not so helpful for customer's review.
Feature Request: Cancelling Subscriptions in Bulk
Reference Number: DE3681
Cancelling Subscriptions in Bulk
Customer: Is there a way to cancel subscriptions in Bulk? Possible to *delete* a bulk quantity of accounts?
If you query for active currencies on a product rate plan that does not have any charges, the response is a 500 with message "You have provided an invalid product rate plan id in your "where" clause." This message is misleading because the product rate plan IS valid. Further the ProductRatePlan is not in an invalid state and merely has no active currencies. As such, the response should be a success (200) with an empty value.
This is causing us issues because we use automatically generated code based on the wsdl with object specific modifications where necessary. We query for ActiveCurrencies during the life cycle of a ProductRatePlan. One of those times is upon creation before charges have been added which means we will run into this error. We can figure out some way to translate this 500 and specific error message into an empty array to work around this response. I'd rather see your endpoint updated so it's easier to work with on our end.
Would be useful in reporting to know which amendment created which version of the subscription.
GET /rest/v1/catalog/products?pageSize=10 HTTP/1.1 REQUEST HEADERS Host: apisandbox-api.zuora.com Accept: application/json Content-Type: application/json; charset=utf-8 Cache-Control: no-cache RESPONSE HEADERS Cache-Control → max-age=0, no-cache, no-store Connection → keep-alive, Transfer-Encoding Content-Type → application/json;charset=utf-8 Date → Thu, 21 Apr 2016 18:01:53 GMT Expires → Thu, 21 Apr 2016 18:01:53 GMT Pragma → no-cache Server → Zuora App Transfer-Encoding → chunked
Match the information that is exported from RatePlanChargeTier data source UI, with what is exported via API.
Query via API shows startingunit, endingunit and priceformat for Overage pricing model tier, but via UI it does not show up in same column.
A credit amendment type would either add credit balance (for monthly customers) or change the billing day of an annual subscription. Credit could be applied to a subscription in terms of a dollar amount or number of months.
Monthly Example: give a monthly customer 3 months of credit (3 months X price = credit). The next three invoices would be covered by the credit balance.
Annual Example: give an annual customer 3 months free, added to the end of their current term. Their next invoice would be generated three months later. The term start date and end date would be adjusted to align to their next invoice.
Feature Request: User would like to be able to cancel subscriptions with cancellation date in a closed accounting period
Reference Number: PMT-222
Business Need: In some cases, users need to cancel subscriptions within a closed accounting period. For example, customer fails to make a payment(s), and as a business requirement, the subscription needs to be cancelled. After the latest payment attempt, the accounting period has been closed, so user should be allowed to go back and cancel the subscription.
Currently there is a notification option called "Payment Method Updated | API/Manually/Payment Method Updater".
When enabled, this sends a notification when the existing Default Payment Method is changed, for example, when the address is modified.
I would like a notification option that sends a notification when the Default Payment Method is changed to a different option/payment method.