HomeData hubOther resources
Guides

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: Price Range Override

  • System Name: price_range

  • Data Type: List.Float

  • Levels: Product

  • Used By Apps: Discovery

  • Required By Apps: None

A two-element array that overrides the automatically calculated product-level price
range in Discovery.

The array must contain exactly two numeric values:

  • First element: Minimum price (low value)

  • Second element: Maximum 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

This attribute is typically used when you need custom price range calculations that
differ from standard system logic, such as:

  • Excluding specific variants from price range calculations (e.g., professional/bulk
    pricing tiers)

  • Including only variants meeting certain business criteria

  • Applying complex pricing rules not natively supported by default calculations

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

General Usage

Override the automatically calculated price range when custom business logic is needed
for determining which variants contribute to the displayed price range.

Examples

Standard price range override

[49.99, 149.99]

Single price point (min and max are the same)

[29.99, 29.99]

Wide price range for configurable products

[199.00, 2499.00]

Application Usage

Engagement

Reserved Attribute Name: price_range

Engagement does not use this attribute at the current time.

Discovery

Reserved Attribute Name: sale_price_range

Used for:

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

  • Setting custom min/max values for sale price faceting

  • Displaying "Now: $X–$Y" pricing on category and search result pages

  • Enabling custom sale pricing display logic specific to client requirements

When price_range is provided at the system level, Discovery will:

  • Remap it to sale_price_range internally

  • Use these values for sale price faceting operations

  • Display them in search results and category pages where sale price ranges are shown
    (e.g., "Now: $X–$Y")

  • Use them for sale price facet bucketing

⚠️ Invalid Range Handling

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

Example of inverted range (NOT recommended):

[199.99, 49.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 price filters)

  • Confusing display showing "From $199.99 to $49.99"

  • Unexpected facet bucketing results

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 sale price range fields when mapped to Discovery

  • The regular price_range continues to come from variant prices (or
    original_price_range if provided)

  • Parent-level price and sale_price are unaffected and still follow standard rollup
    rules from variants

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

Interaction with Other Price Attributes

  • When provided as price_range at the system level, it is remapped to
    sale_price_range in Discovery

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

  • Works alongside price and original_price for complete pricing information

  • Does not affect regular price_range, low_price, or low_sale_price calculations -
    these still derive from original_price_range and variant data

  • To fully control all price-related displays, you may need to provide additional
    attributes separately

Feature Capabilities & Configuration

  • Referenced in Delivery API request parameter as: sale_price_range

  • Referenced in Delivery API response documents as: sale_price_range,
    low_sale_price, high_sale_price

  • 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?
    NO.

  • Searchable by default?
    NO,modifiable

  • Facetable by default?
    YES,modifiable

  • Displayable by default?
    YES,modifiable

Updated 3 months ago