HomeData hubOther resources
Guides

Original Price Range Override

Suggest Edits

👍

Welcome note

Data hub is our new upgraded platform, which we rolled out in August 2025. It offers a single unified integration for passing your data through to your Bloomreach products.

You have access to Data hub if you've implemented with Bloomreach after August 2025.

Customers who have implemented before August 2025 should follow the existing documentation for Engagement, Discovery, and Clarity.

  • Display Name: Original Price Range Override

  • System Name: original_price_range

  • Data Type: List.Float

  • Levels: Product

  • Used By Apps: Discovery

  • Required By Apps: None

A two-element array that overrides the product-level regular (non-sale) price range
calculation in Discovery.

The array must contain exactly two numeric values:

  • First element: Minimum regular price (low value)

  • Second element: Maximum regular price (high value)

Data Recommendations

For best results, follow these guidelines:

  • The maximum value should be greater than or equal to the minimum value

  • Values should be floats ≥ 0 with maximum 2 decimal precision

  • No currency symbols, commas, or text allowed

Note: Discovery accepts any two-element numeric array without validation.
Invalid or inverted ranges will be propagated as-is, which may cause unexpected behavior
in filtering and display.

This attribute is typically used when you need custom variant-level calculations for
regular pricing that differ from Discovery's standard logic, such as:

  • Excluding specific variants from regular price range calculations (e.g., limited
    edition or clearance items)

  • Including only variants meeting certain business criteria

  • Applying complex regular pricing rules not natively supported by Discovery

  • Controlling which variants contribute to the regular price range when sale prices are
    present

When provided, this overrides Discovery's automatic regular price range calculation
only. Sale price ranges and other derived pricing fields continue to be calculated from
variant data unless explicitly provided separately.

General Usage

Override the automatically calculated regular price range when custom business logic is
needed for determining which variants contribute to the displayed regular (non-sale)
price range.

Examples

Standard regular price range override

[79.99, 199.99]

Single price point (min and max are the same)

[49.99, 49.99]

Wide price range for configurable products

[299.00, 3999.00]

Application Usage

Engagement

Reserved Attribute Name: original_price_range

Engagement does not use this attribute at the current time.

Discovery

Reserved Attribute Name: price_range

Important: The system attribute original_price_range maps to Discovery's
price_range field, which represents the regular (non-sale) price range.

Used for:

  • Overriding the automatic regular price range calculation for product-level displays

  • Setting custom min/max values for regular price faceting

  • Providing the baseline price range for discount calculations

  • Controlling the regular price range independently from sale price ranges

When original_price_range is provided, Discovery will:

  • Map it to the price_range field (the regular price range)

  • Use these values for regular price faceting operations

  • Display them as the regular price range in search results and category pages

⚠️ Invalid Range Handling

Discovery does not validate the original price range values.
Invalid or inverted ranges are used as-is:

Example of inverted range (NOT recommended):

[299.99, 99.99]  // Max is less than min - will be used as-is

Result: This inverted range will be indexed and may cause:

  • Incorrect filtering behavior (products may not appear in expected regular price
    filters)

  • Confusing display showing regular price "From $299.99 to $99.99"

  • Unexpected discount calculation results

  • Incorrect facet bucketing for regular prices

Always ensure your minimum value is less than or equal to your maximum value to avoid
these issues.

Important Notes:

  • This override affects ONLY the price_range field - it does NOT automatically set
    sale_price_range, low_price, or low_sale_price

  • The sale_price_range and low price fields continue to be calculated from variant
    data

  • Discount percentages are still derived from the relationship between regular prices
    and sale prices at the variant level

  • Parent-level original_price is untouched by this override; it is only updated when
    supplied directly

  • Individual variant original prices remain unchanged and are still used for
    variant-specific displays

Interaction with Other Discovery Price Attributes

  • original_price_range overrides the automatic calculation for the regular
    price_range field only

  • Does not replace the need for original_price attributes on products/variants

  • Does not affect sale_price_range calculation, which continues to derive from variant
    sale prices

  • Best used when you need to control the regular price range independently from sale
    pricing

  • To fully control price-related displays, you may need to provide:

    • original_price_range to override the regular price range

    • price_range system attribute (if you also need to override sale price ranges)

    • Individual price and original_price on variants for accurate displays

Feature Capabilities & Configuration

  • Referenced in Delivery API request parameter as: price_range

  • Referenced in Delivery API response documents as: price_range

  • Can be faceted and filtered on in Delivery APIs?
    YES.

  • Available to use in Variant/SKU-select use cases?
    NO.

  • Available to use in facet management dashboard?
    YES.

  • Searchable by default?
    No,non-modifiable

  • Facetable by default?
    YES,modifiable

  • Displayable by default?
    YES,modifiable

Updated 3 months ago