Skip to main content

Considerations

Zuora

Considerations

  1. Last updated
  2. Save as PDF

Dynamic Pricing has the following limitations in specific tenant configurations:

  • Advanced charge models - The following advanced charge models are not supported: 
    • Pre-rated High Watermark
    • Pre-rated Per Unit
    • Delivery
    • Map

Zuora plans to introduce support for the Overage and Tiered with Overage pricing models for usage charge types in a future update.

  • Price Limit Configuration in Dynamic Pricing - With Dynamic Pricing, you can define price limits (Min and Max) in the rate card for the following charge models under the Usage charge type:
    • Per Unit
    • Volume
    • Tiered 

Price limits can be defined at both the charge (row) level and the tier level in the rate card.

  • Charge-level price limits apply to the overall charge.
  • Tier-level price limits apply within each tier for Tiered and Volume charge models.

 

  • Charge Type/Model Reset: Changing the charge type and/or charge model on a Product Rate Plan Charge (PRPC) will reset any existing Dynamic Pricing configuration. It is recommended to select the appropriate charge type and model before defining the Dynamic Pricing decision table.
  • Impact on Active Subscriptions: Updating existing PRPCs that are tied to active subscriptions can immediately affect downstream pricing and billing. If you do not want to impact existing subscriptions, create a new PRPC instead of modifying an existing one.
  • Clone Limitation - The clone functionality is supported for products, product rate plans (PRPs), and PRPC. However, Dynamic Pricing does not support cloning of rate cards. If a charge is created using Dynamic Pricing (which involves a rate card), the rate card cannot be cloned.
  • Tenant Configuration Limitations:
    • Multi-entity tenants: Pricing tables and attributes are not cascaded to child entities. Each child entity must have its own Dynamic Pricing setup.
    • Multi-org (MO) tenants: Pricing configurations are not inherited by child orgs. Each org must be managed independently.
    • DAC-enabled tenants: Dynamic Pricing attributes are not automatically shared or inherited across entities or orgs.
    • Order Harmonization (OH): If a customer creates or amends a subscription with Dynamic Pricing–enabled charges via the Subscriptions/Amendments (S/A) API, an error will be returned.
  • Legacy ABP Compatibility: You cannot enable both Dynamic Pricing and legacy Attribute-Based Pricing on the same tenant.