> This page is for Docs.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://zuora.ferndocs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server.

# Price lookup flow

> Outlines the sequence of steps involved in determining the price for a subscription product rate plan in Zuora Billing, including charge overrides and price lookup formula evaluations.

Outlines the sequence of steps involved in determining the price for a subscription product rate plan in Zuora Billing, including charge overrides and price lookup formula evaluations.

The following diagram explains how price is determined when you subscribe to a product rate plan for your end customer after the Attribute-based Pricing feature is enabled.

![ABP flow](/_fern-img/1908cc5926e789a8339b4bd78e52d36c82333dd1de3988b85f4b9118666f0001.webp)

The following things happen in sequence in Zuora Billing when you create a subscription for a customer account.

The charge override behavior in Step 5 below is applicable only when an order or order preview is submitted for subscribing to a rate plan.

A subscription product rate plan is created by cloning the original product rate plan charge.

The system checks whether there is any charge override.

* If yes, the charge override is applied to the subscription product rate plan.
* If no, skip to the next step.

The system checks whether a price lookup formula is defined for the product rate plan charge for evaluation.

* If yes, proceed to the next step.
* If no, skip to Step 6 to finalize the subscription rate plan charge.

The system collects all required information to evaluate the price lookup formula and identify the target product charge definition.

* If the target product charge definition is identified, proceed to the next step.
* If no target product charge definition can be identified or any error occurs, the whole process terminates with errors.

Based on the following conditions, the system evaluates whether values provided in charge override in an order or order preview should be applied to the subscription rate plan charge.

<table>
  <tr>
    <th>
      Condition 1

      Whether the attribute value is overridden by the target charge definition
    </th>

    <th>
      Condition 2

      Whether the attribute is present in the order charge override
    </th>

    <th>
      Evaluation result
    </th>
  </tr>

  <tr>
    <td>
      No
    </td>

    <td>
      Doesn’t matter
    </td>

    <td>
      Does not apply changes
    </td>
  </tr>

  <tr>
    <td>
      Yes
    </td>

    <td>
      Yes
    </td>

    <td>
      Does not apply changes （It’s because order charge override has higher priority.)
    </td>
  </tr>

  <tr>
    <td>
      Yes
    </td>

    <td>
      No
    </td>

    <td>
      Apply changes
    </td>
  </tr>
</table>

The subscription product rate plan charge is finalized.