Skip to main content

FAQs about Orders Harmonization

Zuora

FAQs about Orders Harmonization

This article contains answers to frequently asked questions about Orders Harmonization and Orders. You can always contact Zuora Global Support if you have a question that is not covered here.

We are continually updating the list.


Q: What happens when Orders Harmonization is enabled?

A: You will see the following:

  • Zuora automatically creates a new object within the data model, an Orders object, in the background when you create a new subscription or make an amendment to an existing subscription via the UI or API.

    This allows you to utilize both the Subscribe and Amend API and the Orders API without impacting your existing code or integrations.

  • You can get access to Order Delta Metrics.

Q: How do I know if Orders Harmonization has been enabled in my tenant?

A: You will see the following:

  • Within your Billing > Define Default Subscription and Order Settings, you will see an Enable Order UI option available. This setting allows you to turn on the orders UI and start creating orders, it is disabled by default when Orders Harmonization is turned on.
  • If you are using Zuora CPQ and/or on the Enterprise or Nine edition, you have a new UI option to Enable Ramp for Orders within your Billing > Define Default Subscription and Order Settings available. This setting is disabled by default.
  • Ramp deals allow you to natively create a subscription for a multi-interval contract where potentially a different discount and/or price point is set at these intervals. For example, some B2B customers like to offer 3-year deals where there is a higher discount on year 1 of the 3-year contract.
  • You can see the Orders object gets automatically populated for your subscriptions and amendments once Orders Harmonization is enabled. This data source is visible once Orders Harmonization is enabled.
  • You can get access to Order Delta Metrics.

Q: Do I need to start using the Orders object to manage my subscriptions?

A: No, you can continue to use the Subscribe and Amend feature to manage your subscriptions. Orders Harmonization gives you the option to adopt the Orders object when you are ready since it gives you the ability to use the Subscription object and Amendment object, as well as the Orders object harmoniously in Zuora.


Q: Will Orders Harmonization impact on my existing integrations or require code changes?

A: No, enabling Orders Harmonization will not impact on your existing integrations or require code changes.


Q: What happens to my existing subscriptions and amendments once Orders Harmonization is enabled?

A: There is no impact on your existing subscriptions and amendments. You can continue to utilize Zuora as you do today.


Q: Can I use the Subscribe and Amend APIs in the same environment if Orders Harmonization is enabled?

A: Yes, you can use Subscribe and Amend APIs and Orders APIs harmoniously in the environment.


Q: How did Zuora test to ensure Orders Harmonization will not have an impact on my existing integrations?

A: Orders Harmonization has been a generally available feature since 2020. We have continuously enhanced this feature and have removed barriers for customers to adopt it. We devoted a team of cross-functional resources this year (2022) that worked with product and engineering experts to remove the final barriers to ensure customers can adopt this feature with no impact on their existing configurations. This team has worked with hundreds of customers on testing Orders Harmonization and ensuring their existing configurations remain intact once Orders Harmonization is enabled, which is why this feature is being released to all customers in our normal release cycle.


Q: What is the difference between Orders Harmonization and Orders?

A: The differences are as follows:

  • If you are an existing Subscribe and Amend customer and want to leverage Orders, the Orders Harmonization feature helps you transition to Orders easily as the Orders object can be used for your existing subscriptions and amendments.
  • Think of Orders Harmonization as the intermediate step between the Subscribe and Amend framework and Orders framework. When you have transitioned to only using the Orders object (via UI and/or API), this is known as a full adoption of Orders. Subscribe and Amend customers often look at a full adoption of Orders in phases.

    For example, some customers will adopt the Orders object in the UI, then in CPQ, and finally, they will refactor their self-service APIs. Some customers will only adopt Orders for new use cases (such as unified monetization or Order Line Items) and keep existing Subscribe and Amend configurations in place.

  • The great thing about Orders Harmonization is that you can adopt the Orders object as they make sense for your business.

Q: Are there known limitations for Orders Harmonization?

A: No.


Q: Are there known limitations for Orders?

A:Yes, please refer to Known Limitations in Orders and Order Metrics.


Q: Are there new features I have access to with the Orders object?

A: Yes, tons of new features have been developed only on the Orders object that you can use now, including the following:


Q: What are the use cases that are solved when utilizing the Orders object?

A: The use cases are as follows:

  • Creating multiple subscriptions under the same billing account through one Orders API call.

  • Creating multiple order actions (that is, amendments) to the same subscription or multiple subscriptions under the same billing account through one Orders call.

  • Creating an upgrade or downgrade with multiple amendments through one Orders call.

  • Creating a multi-year (or multi-interval) deal arrangement with different discounts and/or price points through one Orders call without the burden of future dated amendments.

  • Sticking in mid-term changes for a multi-year subscription without rolling back and recreating future dated amendments.

  • Creating a stand-alone invoice for a one-time good or service with an order line item (this does not have to be associated with a subscription).

  • Supporting billing use cases for Prepaid with Drawdown.

    Under this model, customers pay upfront to receive a number of units, usually for a period of time like a month or a year. Then they consume against that prepayment balance in a use-it-or-lose-it fashion, with a possibility of topping up more units or being charged for any overage. This model strikes a balance between upfront commitment and the pure pay-as-you-go pricing models.

  • Reporting on a delta change between subscription versions as the change relates to an order action (that is, amendment) including MRR, TCV, TCB. 

  • Utilizing v2 API.

  • Setting different payment terms and/or bill-to contacts at the subscription level through Flexible Billing. This helps when managing the hierarchical relationships in billing.


Q: If I want to start adopting the Orders object, what impact will this have on my existing integrations?

A: You will see the following impacts:

  • Order objects take the place of the Amendment object today. As a rule of thumb, you need to understand how you are using the Amendment object and start pulling order actions moving forward when orders are used. Zuora support can assist you with evaluating the impact on your existing configurations.
  • This is not an exhaustive list but some impact areas are included:
    • Amendment reporting - Are you reporting off the Amendment object today in Zuora? If so, when you start using the Orders object, you will want to look at the Order Action object for that amendment information including ‘type’. This includes any outside reporting via AQuA data pulls to your data lake or data warehouse.

    • Amendment callouts - If you using Amendment callouts today, please make sure you recreate these onto the equivalent Order Action object.

    • Amendment data queries - If you are using the Amendment object in data queries today, please make sure you recreate these onto the equivalent Order Action object.

    • Subscribe and Amend APIs - The Subscribe and Amend APIs will continue to work with orders. But, you will need to refactor your APIs if you want to see the benefits of orders (that is, if you wish to bundle multiple amendments to a subscription into one API call, you need to use the Orders APIs rather than the Subscribe and Amend APIs).

    • Workflows - Similar to your APIs, workflows will continue to work with orders. However, if you are looking to take advantage of orders within your workflow, you need to refactor your Subscribe and Amend API calls in your workflows to use the Orders API.

    • CPQ - Orders can be enabled in CPQ if you are on version 8 or above. There is no impact on existing users as the UI does not change (unless you are looking to use CPQ X). Under the hood, when you are creating or making changes to a subscription, Zuora will start sending the changes in the Orders API call. 

      We recommend you update to the latest version of CPQ when enabling Orders as there have been a lot of enhancements in CPQ version 8 or above.

    • Sync for Zuora 360+ and Zuora 360 - There are no changes to your existing sync integrations.

    • Email notifications - When Orders Harmonization is enabled, notifications are automatically created for the equivalent order action. So, there is no action for your team to recreate and activate these once orders are created.


Q: What testing do you recommend if I want to start utilizing the Orders object?

A: We recommend the following:

  • All testing should be done in a sandbox environment before moving to the production environment - orders have no exceptions.

  • We recommend assessing how you are utilizing the Amendment object today to ensure you feel comfortable with recreating the Amendment-equivalent actions on the Order Action object (no matter whether the actions are callouts, data queries, and/or reporting).

  • We also recommend you have properly tested how orders can be created in the UI as there is a reinvented UI within Zuora.

  • Ensure you have tested the Orders API for all new and/or existing Subscribe and Amend use cases (depending on how you are looking to roll out the Orders object).

    Amendment workflows would need to be modified to use the Orders API as well depending on how you are looking to roll out the Orders object).

  • Finally, we recommend you are on the latest version of CPQ if you want to send Orders calls from Zuora CPQ into billing.

    • While orders are compatible with CPQ version 8, there have been a lot of enhancements we have made since then and thus recommend you are on the latest and greatest version ideally before rolling out the Orders object.

    • If you want to test CPQ X, it is required to be on version 10 or above.


Q: What are the benefits of enabling Orders Harmonization for my environment?

A: The benefits are as follows:

  • You can choose when you want to utilize the Orders functionality for other new functionalities.

    These new functionalities are based on the Orders framework, including Order Line Items, Ramp Deals, CPQ X, Prepaid with Drawdown, and so on. The new functionalities are now accessible to your team with Orders Harmonization enabled!

  • You can optionally use the Orders API and UI to manage your subscriptions. Orders support a high volume of subscription creations and amendments in one API call.
  • Orders can be seamlessly leveraged through Orders Harmonization without migrating or refactoring your existing integrations from the Subscribe and Amend APIs to the new Orders APIs. None of your existing Subscribe and Amend integrations will break with Orders Harmonization enabled.


Q: I have additional questions, who do I contact?

A: Please reach out to your Customer Success Manager, Account Executive, or Zuora Global Support for additional assistance.