HomeData hubOther resources
Guides

Price

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

  • System Name: price

  • Data Type: Float

  • Levels: All

  • Used By Apps: All

  • Required By Apps: Discovery

The final product or variant price after all discounts and promotions.

Price must be a float value ≥ 0 with maximum 2 decimal precision.
No currency symbols, commas, or text allowed

If original_price system attribute is also used, this value SHOULD be lower than or
equal to original_price.

If the product has variants:

  • price should be present for each variant.
    If a variant lacks a price, Discovery will attempt to inherit it from the
    product-level price before indexing.
    Variants that still lack a price after this backfill will be excluded from search
    results.

  • Product-level price is not ignored - it serves as a fallback for variants without
    prices and is used to calculate product-level price ranges.

Value of 0 is allowed, but should be used for exceptional cases like free digital
downloads or quote-only items that require custom pricing.

General Usage

  • Displaying the price of the product or variant on business facing user interfaces
599.99

9.00

Application Usage

Engagement

Reserved Attribute Name: price

Used for:

  • Displaying the price of the product or variant on business facing user interfaces

  • Referenced in many plug and play use cases that work with product or product variants

{{overview explaining any additional Engagement relevant details including
transformation constraints}}

Discovery

Reserved Attribute Name: price or sale_price

Required for Discovery application

Used for:

  • Displaying the price of the product or variant on business facing user interfaces

  • Commonly used as a standard search filter and facet

  • Used as a ranking signal

Discovery Attribute Mapping

Discovery maps pricing attributes differently based on which attributes are present:

  • When BOTH price and original_price exist:

    • price → Discovery's sale_price (the discounted price)

    • original_price → Discovery's price (the regular price)

  • When ONLY price exists:

    • price → Discovery's price (treated as regular price)

    • price → Discovery's sale_price (duplicated to maintain consistent behavior)

Example with sale:

Your data: price=19.99, original_price=29.99
Discovery sees: sale_price=19.99, price=29.99

Example without sale:

Your data: price=49.99 (no original_price)
Discovery sees: price=49.99

If products or variants do not have pricing information, a value still needs to be set
to be a valid product or variant in Discovery.

Product Level Pricing with Variants

  • When a product includes variants, we look at the variants that are available for sale
    (those whose availability system attribute is not set to false) to determine the
    lowest and highest prices; these values become the product's price_range,
    low_price, and sale_price_range reserved attributes so downstream touchpoints can
    present “from/to” pricing consistently.

  • If the product does not supply its own price, we reuse the highest available variant
    price to populate the product price, and the highest available variant sale price
    (falling back to the highest variant price) to populate the product sale_price,
    keeping the key price attributes complete for merchandising rules, search filters, and
    reporting.

  • Whenever the resulting sale price is lower than the regular price, the product is
    flagged as on sale and a percentage discount is calculated automatically, enabling
    badges and promotional messaging without extra configuration.

  • A variant is treated as available for search when its availability attribute is
    either omitted or set to true; setting availability to false removes that
    variant from the price rollups above and excludes it from search results.

Feature Capabilities & Configuration

  • Referenced in Delivery API request parameter as: price or sale_price or
    sku_price or sku_sale_price

  • Referenced in Delivery API response documents as: price or sale_price or
    sku_price or sku_sale_price

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

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

  • Available to use in facet management dashboard?
    YES.

  • Searchable by default?

  • Facetable by default?

  • Displayable by default?

Updated 3 months ago