HomeData hubOther resources
Guides

Original 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: Original Price

  • System Name: original_price

  • Data Type: Float

  • Levels: All

  • Used By Apps: All

  • Required By Apps: None

The initial product or variant price before any discounts or promotions.

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

This value SHOULD be greater than or equal to the price system attribute when both are
present. When original_price is higher than price, it indicates the item is on sale
or discounted.

If the product has variants:

  • Product-level original_price serves as a fallback for variants without an
    original_price and is used in price range calculations

  • Note that original_price itself does not roll up from variants to the product level

    • only the derived price attributes (price_range, sale_price_range) are calculated

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 original price (typically with a strike-through) of the product or
    variant on business facing user interfaces
599.99

9.00

Application Usage

Engagement

Reserved Attribute Name: original_price

Used for:

  • Displaying the original price (typically with a strike-through) 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

Used for:

  • Displaying the original price (typically with a strike-through) of the product or
    variant on business facing user interfaces

  • Commonly used as a standard search filter and facet

  • Used as a ranking signal, particularly for on sale item classification

Discovery Attribute Mapping

When original_price is provided along with price:

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

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

This enables Discovery to automatically:

  • Flag items as "on sale"

  • Calculate discount percentages

  • Display strike-through pricing

Example:

Your data: price=19.99, original_price=29.99
Discovery sees: sale_price=19.99, price=29.99 
Result: Item shows as "31% off" with strike-through on $29.99

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 sku_price for variants

  • Referenced in Delivery API response documents as: price or sku_price for variants

  • 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