Known limitations in Orders and Order Metrics

Limitations in Orders for Zuora Billing

The table below describes known limitations in Orders (Orders Harmonization) for Zuora Billing. The Orders (Orders Harmonization) feature shares the same limits as Order Metrics and extends to a few more limits.

Feature	Limitations
Order Actions	You can change the term start date of a renewed subscription through a T&Cs order action. However, when changing it to an earlier date, this date must not be earlier than the term start date of the current term before this T&Cs. Before you can change the term start date of a renewed subscription, you must contact Zuora Global Support to enable this functionality. With the Single Transaction Subscribe and Amend functionality enabled, when you suspend a subscription in Subscribe/Amend, you cannot resume it in Orders, and vise verse, when you suspend a subscription in Orders, you cannot resume it in Subscribe/Amend.
Discounts	Discounts are supported at the account, subscription, and rate plan levels. However, discount metrics are calculated for subscription and rate plan level discounts only. Discount metrics are not calculated for account level discounts. You can perform the following actions for subscriptions with account level discounts, however no metrics will be generated: Create Subscription Add Product Update Remove T&Cs Cancellation Renew Suspend / Resume Account level discounts are not supported in the Preview order or Get order metrics for evergreen subscription operation. Update of a fixed amount discount is not supported.
Pending Subscriptions and Pending Amendments	Creation of pending subscriptions is supported via API and UI. Migration of pending subscriptions and amendments are not supported in the current amendment migration job to orders. However, since the Subscribe/Amend APIs are now available on Orders tenants, you can still activate these pending subscriptions and amendments via the Subscribe/Amend APIs. Pending order actions/amendments are supported via API and UI with limitations.
Invoice Processing Scope	You cannot currently set the invoice processing scope of an Order.
Prepayment	Prepayment is a deprecated feature of Zuora and is not supported in Orders.
MRR Trend Export	MRR Trend Export is not supported with Orders.
MRR (Contracted) Changes Export	MRR (Contracted) Changes Export is not supported with Orders.
For Usage Charges, Amend or Cancel a Subscription Before the Last Invoice Date	If you have usage charges, you cannot perform the following order actions with an effective date before the last invoice date: Create a "Cancel a Subscription" order action to cancel a subscription that has a usage charge. Create a "Remove a Product" order action to remove a product that has a usage charge. Create an "Update a Product" order action to update a usage charge. However, you can create an "Add a Product" order action to add a product that has a usage charge before the last invoice date.
Orders Metrics for Usage Charges	Order Metrics will not be generated for usage charges.
Managing subscription product features	The Orders UI does not support the Managing subscription product features function; only the Orders API operations support it. Orders Harmonization does not have the preceding limit.

Zuora Billing supports only BMP encoding in the Unicode Standard. When submitting data through the Zuora UI or API, you must use the characters supported in BMP.

See the REST API Reference for how to programmatically implement orders in Zuora.

Limitations in Order Metrics

This section is for the existing Zuora Subscribe and Amend customers who have enabled Order Metrics only (not full Orders).

The table below describes known limitations in Order Metrics for Zuora Billing. Note you must have full Orders turned on to support the Orders integration with Zuora CPQ.

Feature	Limitations
Amendments	The following type of subscriptions are not supported to be migrated to Order Metrics: if you have changed the term start date to an earlier date via a T&Cs amendment after performing a renewal. Doing so would result in potential gaps in the order metrics generated. After Order Metrics is enabled, you cannot change the term start date via a T&Cs amendment if a Renewal amendment is already in place.
Discounts	Discounts are supported at the subscription level, rate plan level, and account level. However, discount metrics are calculated for subscription and rate plan level discounts only. Discount metrics are not calculated for account level discounts. You can perform the following amendments for subscriptions with account level discounts, however no metrics will be generated: Create Subscription Add Product Update Remove T&Cs Cancellation Renew Suspend / Resume
Pending Subscriptions	You can still create pending subscriptions and pending amendments by not providing all trigger dates with this feature turned on; however, Order Metrics will not be generated for that subscription until it is fully activated.
Prepayment	Prepayment is a deprecated feature of Zuora and is not supported in Order Metrics.
Discount Applied Metrics	You are strongly recommended to disable the Discount Applied Metrics when the Order Metrics feature is enabled.
MRR Trend Export	MRR Trend Export is not supported with Order Metrics.
MRR (Contracted) Changes Export	MRR (Contracted) Changes Export is not supported with Order Metrics.
Usage Charges	Order Metrics will not be generated for usage charges.

Limitations in Orders for Zuora CPQ

The below table describes known limitations in Zuora CPQ.

Feature	Limitations
PDF for Ramp Deals	Zuora Quotes will only output a Ramp Deal in a single table, representing date ranges from one Action to the next Action. There is no custom grouping of Charges into arbitrary time periods. This is due to the limitation of Zuora’s quote document generation. You need to use other tools, such as Workflow Custom Document or Conga, to do the custom grouping of information.
Legacy SFDC Bundling (an old CPQ-only feature that has been replaced by native Zuora Offers functionality across the Zuora ecosystem)	Zuora Quotes does not currently support Legacy SFDC Bundling with Orders. Also, you cannot send the `CpqBundleJsonId__QT` field to Zuora when Orders is enabled.

Limitations in Orders for Insights

The table below describes known limitations in the Zuora Insights add-on when the Orders feature is enabled.

Feature	Limitations
Insights Analysis	Insights Analysis is not supported when the Orders feature is enabled.

Limitations in Orders for Billing - Revenue Integration

The table below describes known limitations in the Billing - Revenue Integration feature when the Orders feature is enabled.

Feature	Limitations
Billing - Revenue Integration	Zuora Revenue does not support the Change Plan order action in Zuora Billing. When Billing - Revenue Integration is enabled, the Change Plan order action will no longer be applicable in Zuora Billing. Note that the new solution, the Order to Revenue feature does not have the preceding limitation.
Order action of removing products that happens in an already billed period cannot be supported for discount charges. It might cause a mismatch between billing and booking values. The order action for quantity upsell in Zuora Billing cannot be treated as a new revenue contract or a new POB in Zuora Revenue. Note that the new solution, the Order to Revenue feature does not have the preceding limitations.

Feature

Limitations

Billing - Revenue Integration

Zuora Revenue does not support the Change Plan order action in Zuora Billing. When Billing - Revenue Integration is enabled, the Change Plan order action will no longer be applicable in Zuora Billing.
Note that the new solution, the Order to Revenue feature does not have the preceding limitation.

Order action of removing products that happens in an already billed period cannot be supported for discount charges. It might cause a mismatch between billing and booking values.
The order action for quantity upsell in Zuora Billing cannot be treated as a new revenue contract or a new POB in Zuora Revenue.
Note that the new solution, the Order to Revenue feature does not have the preceding limitations.