Active

👍

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: Active

• System Name: active

• Data Type: Boolean

• Levels: All

• Used By Apps: All

• Required By Apps: None

Indicates whether the product or variant is active and available for sale.

When set to false, the product or variant is considered inactive and not offered for
sale. By default, applications may choose not to index inactive items and make them
unavailable unless specifically configured to do so.
This provides a mechanism to temporarily or permanently remove items from being
discoverable or purchasable without removing them from the collection.

Default value is true if not explicitly set.

General Usage

• Controlling product visibility and availability across applications

• Temporarily disabling products without removing them from the catalog

• Managing seasonal or discontinued items

• Coordinating product launches by pre-loading inactive items

Examples

true

false

Application Usage

Engagement

Reserved Attribute Name: active

Used for:

• Filtering out inactive products from recommendation algorithms

• Suppressing inactive items from email campaigns and personalized content

• Managing product availability in triggered messaging and abandoned cart flows

Discovery

Reserved Attribute Name: availability

Used for:

• Controlling whether products appear in search results and category pages

• Managing product indexing based on availability status

• Supporting "Search for unavailable products" configuration as documented in
  Catalog Settings

• Determining variant contribution to parent product attributes during aggregation

• Managing hero SKU selection to exclude out-of-stock variants

By default, Discovery will not index items where its reserved attribute availability
is false unless the "Index unavailable products" setting is enabled in catalog
configuration.

Product and Variant Level Behavior:

• A product is considered unavailable if its own availability is false OR if every
  variant's availability attribute is false

• Variant data contributes to the parent product only if the variant is available or the
  catalog explicitly allows out-of-stock indexing; otherwise the variant is skipped
  during attribute aggregation and price calculations

• Dynamic categories are suppressed whenever the governing product/variant would be
  dropped for availability reasons, ensuring merchandising rules stay aligned with
  searchable inventory

Out-of-Stock (OOS) Handling:

• You can index OOS (unavailable) variants to let customers know that the product will
  be back in stock

• For a better user experience, you can disallow OOS variants from being selected as a
  product's hero SKU (More
  details)

• Variant-level Filtering can be leveraged based on availability reserved attribute

Feature Capabilities & Configuration

something related to sku_out_of_stock for variant level

figure this one out

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

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

• Available to use in facet management dashboard?
  NO.

• Searchable by default?

• Facetable by default?

• Displayable by default?