I use the solution in my company since it helps the subscription business. The tool helps businesses manage their product catalogs and content contacts. It also helps with accounts like how much revenue has been generated to keep track of all that. It also helps integrate with other applications and CRMs, like Salesforce. We can also complete reports and all of that with the tool.

The most valuable feature of the solution is that it helps subscription businesses keep track of everything, like upgrades, downgrades, and cancellations. If there are repetitive tasks, we can automate them with the tool.

Zuora is good, but I have faced some issues while using data queries. While fetching the data, I had faced some issues. The issue with the tool may be because of my limited knowledge.

I have been using Zuora for a year and a half or two. I am a user of the tool.

It is a stable solution and though we had encountered a few bugs, they were resolved. Stability-wise, I rate the solution a out of ten.

We will be continuously adding accounts as and when a new subscription occurs.

Around ten people use the tool in my company.

The solution's technical support team's ability to resolve issues is good. I am happy with the support team. Mostly, all of our tickets are resolved by the support team.

The product's installation, setup, and deployment phases can be managed by contacting Zuora support.

The solution is deployed on the cloud.

Zuora can be useful if it is a subscription business. There are alternative billing platforms as well. I have been using Zoho, which I think is a stable product.

It would be easy for a beginner to learn to use Zuora. The tool's UI is user-friendly. The tool offers documentation and has a knowledge center, which has all the information and is user-friendly.

I rate the tool a seven out of ten.

I work for a large utility manufacturing company that sells tyres on a subscription basis. I used Zuora to automate their business billing processes.

Initially, our customer's system was inefficient, using multiple systems for rating, invoicing, finance, and usage-based charging. There were minimal systems involved in their process. Now, they have merged every process into one system under one roof.

Moreover, Zuora has recently launched its AI bot, which can be used within the tenant itself.

It can generate invoices and manage all financial transactions within the platform.

It's an end-to-end solution for managing subscriptions. You can generate invoices, credit memos, debit memos, and handle products—everything is under one roof. You can also generate different invoice templates and map financial transactions. Additionally, it can be used to generate reports and analytics.

It has been improved a lot. I've seen its growth over two years, with new features being added constantly.

Currently, the data structure within Zuora is a bit rigid. It doesn't support many things, like subqueries or correlation queries and all that. If they improve that section, it would be great.

It has almost been two years. 

I haven't experienced any issues working with it. It's a good platform and easy to use.

It is a scalable product. The only limitation is the ZDQL (Zuora Data Query Language). It's not very efficient and doesn't support many SQL queries or other standard features. If that could be improved, it would be great.

There are around eight to nine users. 

The Zuora tenant we used for the client was US-based, but they operated in multiple countries like Mexico and Colombia. We used the same tenant for every project and created entities within the same project.

Zuora has its own technical support. If we encounter any problems, we can raise a ticket internally, and they will definitely help us.

Positive

I didn't use a different solution. For me, it was my first time using such a tool.

The initial setup wasn't that complex. It was a bit easy. 

• Integration Capabilities: Zuora provides REST APIs, as well as SOAP APIs, which can be leveraged to connect with other systems.

• Deployment strategy: We followed an agile methodology. It was a continuous development and continuous deployment setup.

• Deployment time: Through Zuora's built-in deployment manager, it doesn't take much time. It's easy to deploy. It was completed within a day.

My team lead was the only one who deployed it.

Zuora is cost-effective. It does bring value to the company.

I would definitely recommend it. It's a really nice platform. We can use its extensibility, and it's very easy to implement and automate processes. 

It can also be integrated with multiple platforms if your business requires working with multiple tools.

Overall, I would rate it a nine out of ten.

I use the solution for development tasks.

Zuora Workflow is valuable. It is the main tool I use to automate processes and deliver business requirements. CPR has helped streamline our billing operations.

The solution must add more programming languages to build logic. For now, it is purely liquid. It must add some simple JavaScript, Python, or another language. It will improve the capabilities of Zuora.

I have been using the solution for five years.

The production environment is great. However, we tend to see some downtime for the Sandboxes. We can check the website's health. The stability of the Sandboxes must be improved.

The scalability is good enough for my needs.

The technical support team responds quickly. It is great. The responses are helpful. The engineering team tends to respond very fast.

Positive

The ease of deployment depends on the previous system. It could be difficult to map everything if it was a legacy system or a custom software. If we were using a similar software, it could be easier. The developer tools offered by Zuora are good enough. We can migrate the data from Excel spreadsheets. A team of four people deployed the tool in our organization. The product is always deployed on the cloud.

The solution is worth the price.

I have used Microsoft Dynamics, but it is not entirely like Zuora. We did not do billing in Microsoft Dynamics.

I am a developer. I am a Zuora consultant. We saw the product's benefits after the initial deployment once we had the knowledge to take advantage of its features. In the beginning, it's usually like migration from a legacy system. It is kind of messy. Once we have hands-on experience, we will start seeing the value.

When there is a change in subscription, we have to go through an amendment to the subscription every time. We create a new order and add the new version of the subscription. The tool requires maintenance sometimes. We perform patching to clean up the account and improve the platform's overall performance.

Zuora has a very good Knowledge Center. It also has courses at Zuora University. These are the first things I show the people in the team. I asked my team members to complete Zuora Billing 101. It gives a very good explanation of the capabilities of the tool.

Overall, I rate the solution an eight out of ten.

We use the tool to monetize customer subscriptions. It is an enterprise module. Whenever a subscription ends, we send an email notification to the customer. The product generates the order number and bill number. It takes two to three seconds, and the notification is sent to the customer automatically. So the customer can pay the bill simultaneously.

I like the invoice template creation and the HTML drag-and-drop concept. The subscription, order management, billing settings, and workflow features are fine. I like the automated bill generation feature. It can be achieved from the workflow.

When we raise global support tickets, we receive delayed responses. We have to wait two to three days.

I have been using the solution for two years.

I have not faced any stability issues.

If we have hands-on experience, the initial setup is easy. However, it will be difficult for a person to do it for the first time.

The tool has volume pricing and tiered pricing models. The tiered pricing model is costly. The volume pricing model is more affordable.

Zuora is a booming product in the market. It is useful and versatile. I will recommend the tool to others. It has many features. We can end the subscription whenever we want. It provides a recurring pricing model. I usually show the demo to the customers. Generally, customers like the product. I use AI if I have any doubts about the tool. I worked as a Java full-stack developer before. I switched streams because many people are losing jobs. Overall, I rate the product a seven to eight out of ten.

One of the main use cases is managing subscriptions. Consumers create subscriptions for products, and Zuora helps us handle that process. When consumers face account issues, our support team monitors and resolves those incidents.

Another aspect of our work with Zuora involves monitoring subscription creation. Sometimes, there are failures, so we need to track and resolve those issues. We manually process orders for European countries and the US, including trial and replenishment orders. We also handle tasks like invoice processing, which is partly manual and partly automated. We process the manual parts.

What I like best about the tool is it's user-friendly, especially when checking accounts and subscriptions. You can see all the details, like consumer-created subscriptions, invoice details, and the ability to create and remove rate plans.

We don't know everything like the development team does. We are focused on operational tasks. I want to extend my knowledge of creating workflows and understand what the development team is doing. With replenishment orders sent after a certain frequency (like every three months), there's a problem if a subscription is canceled with a future date—it cancels on the same date instead.

We have to raise bugs, especially when problems related to product design arise. For example, fraudulent consumers can place subscriptions even when we classify them as fraud. This issue should be addressed by providing a blockage or prevention mechanism.

I have been working with the product for one and a half years. 

I rate the tool's stability a seven out of ten. 

The solution's technical support is good. 

Positive

Our development team did the deployment. 

I rate Zuora an eight out of ten. 

I worked with Zoho for different use cases according to the requirements for the businesses. I have worked on two projects: one for HMD and another for Philips. For HMD, I worked on creating workflows, creating products, creating customer accounts, and integrating them with other systems. For Philips, I am still working on the project, deploying from one system to another, using developer tools, deployment manager, workflows, creating subscriptions from Zoho CPQ, and integrating with SAP.

The automated billing systems have increased our billing by some percentage because it is easier to understand. Zoho has impacted the billing process for business users and customers by providing a convenient way to upload and bill usages.

I like that the UI is great and easily explainable. It allows new users to use Zoho Billing platform easier than any other billing platform.

There are some new developments, such as the invoice template, which is now more convenient for providing different languages. Previously, it was challenging to provide different languages other than English, but now it can support Spanish and other languages. Furthermore, there are more improvements happening, like the introduction of batch updates and global search capabilities.

I have been using Zuora for two point four years.

Zuora is a stable product with few bugs. After development is done by the team, few bugs are raised, and it's working as expected, keeping business operations smooth.

Zuora works the same for all users, more or less. There are some limitations regarding data storage, such as invoice and subscription attachments. However, we are not storing anything on Zoho, so I can't comment extensively on this.

The support team is responsive and replies to issues promptly, typically within thirty minutes to an hour. However, there have been instances where it took more time, such as with the CPQ-related issue. The support team needs to improve response times.

Neutral

The initial setup for deployment is made easier with a deployment manager and developer tools. However, some aspects like settings need to be done manually.

I would recommend Zuora to others because it is easier to learn, handle, and understand.

Zuora is used for different organizations. Some are energy-based, while others are usage-based, like providing paritcular mobile data. Some organizations use Zuora for updating their accounts, subscriptions, and usage. 

Currently, I use Zuora for a few customers who are focused on usage and use a mediation model, which has an order-based subscription. These are my use cases.

There is AI to enhance subscription management and billing processes. However, I have not used it. If Zuora provides key training on how to use it and how it can be useful for organizations to show dashboards and prepare quick responses, that would be helpful. AI can also make mistakes in terms of changes or subscriptions, which could be difficult for the organization to manage. But, 99.9% of the time it would be correct, and the 1% where AI would not showcase a good result is a rare case.

Zuora is really helpful for organizations trying to manage their revenue. They can rapidly take the revenue and recognize it directly from Zuora and prepare their finances quickly. 

It's not easy for them to manually recognize all the transactions in their system when they are trying to compile data from each customer, where they have multiple invoices and bulk customers. So it's really easy to use. 

With their new features, they can easily track their data, manage their usage, and provide accurate billing to the customers.

Different pricing models and billing cycles:

Zuora supports multiple pricing models. There are one-time usages, flat fees, per unit, tiered, overages, and consumption-based models. For consumption-based models, if there are prepayments in the system, Zuora can manage subscriptions, prepare billing, and showcase within the subscription how the balance is utilized.

There are a few areas for improvement. Some APIs aren't working in amendment-based subscriptions, although that will be resolved in 2026. 

We also have certain features in orders that aren't fully compatible right now, but they are still usable. 

Some people don't easily understand things like JavaScript, so Zuora could provide more content in their knowledge center to help users learn and implement those features.

I have been using Zuora for five years. 

There are a few issues I've encountered while working for clients. There were some systems where I was moving data from one environment to another in Zuora. I was deploying the whole data from one system to another using a workflow, but it gave me a lot of issues in the last couple of months. 

It wasn't able to properly move the data due to concurrent limits and log competition errors. These are areas that Zuora can improve.

Considering the current scenario in today's market, Zuora has a vast system, and it's really improving for the betterment of the customer. I would give it an eight out of ten based on stability. They need more data from the customer and are doing some upgrades every month, so customers do face some issues due to that.

So, due to some updates going on within the sandbox and production, they need to update more quickly.

I would rate the scalability an eight out of ten. Zuora is already managing this system for multiple customers across the globe, so scalability is there.

There are around 15 to 20 people using it in my company. Zuora is a PaaS system, and the competition is very high; not everyone use it. I know a few more colleagues who use Zuora.

The customer service and support have knowledge and content available through the Zuora knowledge center. I always get a response, but some of the responses are not on time.

There is room for improvement in the response time. 

Neutral

The deployment is difficult for those who do not have a Zuora background or a technical background. The knowledge center doesn't fully explain how to prepare workflows from scratch, but it does mention the tools that can be used to build them. 

If someone has good knowledge about Zuora, they can easily tackle those things. They can do some research and development and prepare workflows using the Zuora API or other integrated systems, which can be used in Zuora for the customers' benefit.

• Deployment time: It depends on the customer's requirements. If the workflow is properly created according to their terms and conditions, then we can deploy it within one week or one and a half weeks. But if it is not as per their requirement or is put on hold for some reason, then it could take months.

• Deployment model: It's already a system generated by Zuora for the organization, and we manage it for implementation and the billing side. We create workflows and use APIs through Force.com and different integration systems with Salesforce and accounting systems. That's how we manage it.

I do it myself within the organization for the customers. I build different workflows based on their requirements, and we deploy them after testing in the sandbox.

Zuora has different pricing for each product, like for Zuora and Zuora's knowledge center training modules and different other systems. So I am aware of it, but not fully involved in it.

Overall, I would rate the solution an eight out of ten. I already recommended it to some customers, and even my customer recommended it further. 

My advice: If you want to use Zuora, you have to think about their business, and if it is really needed, then you can opt for it and manage their system within Zuora.

We have a lot of products. So, we use it for product billing because we have many subscription-based models. We use Zuora for each product subscription and billing.

Zuora has a lot of features that I like. We have so many options for reporting, whether you want structured data or automation. 

In Zuora, we have the option to work without needing any other software. For example, policies are implemented within Zuora. If you want to introduce a product, you can use the API to integrate with Zuora.

And as Zuora is connected with Salesforce or other CRMs, we have the Big House connector. You can just install and use it. We have so many options with Zuora, and the UI experience is much better than other applications I have used. That's why I prefer Zuora over other solutions.

Some areas that could be improved include the API rate limit, which is currently 280 requests per second and can lead to system slowdowns. Additionally, the reporting limit allows only 500 objects at a time, and the profile user data acceptance could be improved by allowing data in a single group.

These are some limitations that can be improved in Zuora.

I have been using it for four years. 

In my whole career of around four years, I did not see any breakdown. 

It has hardly happened that Zuora got stuck one or two time because of some backend issue. Otherwise, it's alright. It's a good application to use.

In my current organization, we have more than 15 to 20 people who use Zuora.

I talked to the customer service and support a lot of times.

I've got very good support every time. Hardly one or two times, I got a delayed response. Otherwise, I get immediate responses.

Positive

I joined this company in August 2023, and Zuora was already in use. 

But as far as I know, Zuora provides some automation processes. If you want to update or import file data, we have enough patience for that. And, like, if you want to automate anything in Zuora, we have options. I don't think many applications have these kinds of options, or they have them but don't have any in-house solution for them. So, that's why I think they chose Zuora over other applications.

The initial setup is easy in Zuora. It's easy to run Zuora because we have a deployment manager through which we can deploy most of the things. So I don't think it's a big task.

My recommendation depends on the complexity of your product and what type of products you have right now. 

If you have a recurring usage-based product, obviously, you can go for Zuora as we have a lot of options to manage a product. Because right now, if you have a usage-based product, you have to do some overage calculations. So, I would recommmend Zuora. It's very easy to use.

However, if you are very new to Zuora or any other application, it will take some time. You have to learn more things about Zuora, but it can be easier than other applications if you have some internal experience or a person who knows it. It would be easy for you to understand the object model.

Overall, I would rate the solution a nine out of ten. 

Different companies have been using Zuora to transitioning from traditional business models to subscription-based ones. This shift has helped improve their businesses. Essentially, Zuora facilitates its move to a subscription-based approach.

Zuora is an end-to-end solution that handles orders, payments, and licensing. Its robust billing engine manages all billing aspects, including debit memos. Zuora's rate plan charges offer the flexibility needed in the subscription business, allowing for easy product configuration. It has evolved since 2015, driven by customer feedback and ongoing reviews. It rapidly improves with new customizations and deployment features, making it a leading solution.

We feel the deployment and version comparison process could be easier when switching between different systems. Based on our feedback, they are working on this. We can contact them whenever we encounter a problem, and they provide a solution.

I have been using Zuora since 2016.

Zuora is quite stable. Occasionally, we experience performance degradation, but we receive notifications about these issues through a maintained site. There have been instances of performance degradation where things take a little longer. These issues can be tracked on our system, where their engineering team works to resolve them.

Support is quite fast. We raise a ticket, and we get a response within one or two hours. If it's a high-priority matter, such as something significantly impacting us, we mention it as a priority ticket and get an even faster response.

The initial setup was manual and time-consuming. We faced some issues with Zuora. These are technical issues with the tool. They have reduced the frequency of these issues over time and are also collecting user feedback. However, these problems persist when deploying from one environment to another.

If you're seriously considering transitioning your business to a subscription model, Zuora could be a good choice.

Zuora can be a valuable tool, depending on your objectives. If you are considering transitioning your business to a subscription model, Zuora is a strong option. It helps manage various systems and processes associated with subscription businesses. Zuora integrates well with other systems, including Jira, through REST API calls, facilitating seamless integration with any system.

Zuora can also be beneficial if you have an order layer separate from your billing system and need a dedicated solution to manage subscriptions and finances. In such cases, Zuora can efficiently handle the subscription aspect, while your front-end could be Salesforce, SAP, or a web-based interface.

Learning Zuora is going to be easy because it offers comprehensive resources for learners. They have a training website called Zuora University, where you can choose any topic. The platform includes UI demonstrations and a learning sandbox, allowing you to explore and learn hands-on. In addition to Zuora University, there is an extensive Knowledge Center available online for anyone to access. Zuora is compliant with finance information standards, ensuring secure handling of data. Recently, they have introduced AI features, such as dashboards for generating reports and automating simple operations like auto-creation of tasks. Their support team uses an automated chatbot to create tickets based on user input. Overall, Zuora provides a user-friendly and resource-rich environment for learning and using their system.

Overall, I rate the solution an eight out of ten.