---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Explore price and quantity Ramps

# Explore price and quantity Ramps {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Price and Quantity Ramps allow customers to structure contracts with planned changes in pricing and quantities over time. Each ramp segment defines a period, making it easy to support phased adoption, upgrades, and annual price
increases.

## Key features {#about-price-and-quantity-ramps__section_utz_kbd_h3c}

`CreateInstance` API supports Price and Quantity Ramps and returns multiple root-level entities (including headerless Sold Products that do not have a parent header) in a single JSON structure. Root-level entity are the entities that appear at the top level of the JSON structure.

* Flexible deal structuring: Scale pricing and quantities over the contract term to match customer adoption and growth.
* Ramp segments: Define pricing and quantity changes by time‑based segments (yearly, quarterly, or custom).
* Product enablement: Configure ramp eligibility at the product level for recurring products.
* Quote integration: Create and manage ramps directly during the quoting process, including parent and child offers.
* Annual price increases: Apply an annual price uplift that automatically cascades to future segments.
* Ramp lifecycle support: Modify ramps, auto‑generate ramps for related pricing, and carry ramp logic through renewals and cancellations.
* Bundle consistency: Apply consistent ramp types and terms across bundled products.
{#about-price-and-quantity-ramps__ul_fdz_2cd_h3c}

## Key
concepts {#about-price-and-quantity-ramps__section_qr5_wdd_h3c}

Root-level entity definitions

1. Header vs No-header behavior
   * With header (example, Quote): Ramps can be linked to the header; use `fetchRecordSysIds` to retrieve specific ramps, or fetch all linked ramps by default.
   * No header (example, Sold Product): Ramps aren't header‑linked; ramp IDs must be provided, or `CreateInstance` returns no ramp data.
   {#about-price-and-quantity-ramps__ul_w3t_32d_h3c}
2. Multi-select vs Multi-select merge
   * multiSelect returns separate groupings per sold product.
   * multiSelectMerge (a function that merges all ramps and line items into a single grouping) returns a merged (flattened) structure, grouping all ramps and line items together, used when multiple sold products share a single ramp.
   {#about-price-and-quantity-ramps__ul_s5t_gfd_h3c}
{#about-price-and-quantity-ramps__ol_w5t_cfd_h3c}

## Benefits {#about-price-and-quantity-ramps__section_fsr_55d_h3c}

* Align pricing with customer adoption
* Reduce manual adjustments during lifecycle changes
* Ensure predictable renewals and accurate billing
* Maintain a clear pricing timeline across the contract lifecycle
{#about-price-and-quantity-ramps__ul_dsc_dvw_h3c}