home

Zuora CPQ

Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies
Zuora BillingZuora PaymentsZuora PlatformZuora CPQZephrZuora RevenueAccounts ReceivableRelease NotesBasicsEntitlementsSupport and policies

Welcome to Zuora Product Documentation

Explore our rich library of product information

Show Contents

thumbnailZuora CPQ

Smart Preview in Zuora CPQ

Smart Preview behavior and constraints

This topic provides reference information for Smart Preview behavior, storage, observability, and known constraints.

Preview API call decision matrix

Condition

Result

No billing-impacting changes detected

Preview API call is skipped

Billing-impacting changes detected

Preview API call is executed

Storage

Smart Preview stores the most recent preview state on the Quote record in Quote__c.PreviewRequestBody__c. The field type is Text (255). This field is updated only when a new preview API call is executed.

Observability and debugging

You can verify skip behavior using the following sources:

  • Apex Logs: skippedApiCall = true and no outbound REST call to the Billing preview endpoint.

  • Browser Console: skippedApiCall and zuoraRequestId is null.

  • Network tab: no Orders Preview API request is sent to Billing.

  • Quote record: PreviewRequestBody__c remains unchanged across edits that do not impact the billing preview payload.

Constraints

  • Smart Preview caching is stored at the Quote record level.

  • The comparison is performed on the entire serialized payload. There is no per-line-item comparison.

Best practices

  • Carefully manage billing-impacting fields in Quote Studio field sets.

  • Deploy field set changes separately and validate preview frequency impact.

Last updated: May 7, 2026