Skip to content
  • There are no suggestions because the search field is empty.

Bluestone PIM Release 77-1

June 16, 2026 - Highlights


New features

Improvements

Fixes


 

New features65

  • Introducing the AI agent!
    We’re excited to announce the chatbot-style AI feature that will let you interact with Bluestone PIM using plain, everyday language - no complex query building required.

    To use the AI agent, you must be explicitly granted access by your system administrator. Please see the Help documentation for details.



  • AI-powered rules: Automate product enrichment!
    Leverage AI directly within the Rules engine to populate product attributes automatically, using your existing images and product data as input.

    This reduces manual data entry and helps maintain consistent, high-quality content across your sales channels.

    Please see the Help documentation for details.

    ai enrich rules engine

  • New Translations app
    Manage translations of attribute names and dictionary attribute values from a single page, with multi-context support and filtering for missing translations. More translation pages will follow in upcoming releases. 

    Please see the Help documentation for details.



  • AI Image enhancer
    ℹ️ Currently available in the Test environment ℹ️

    We’re introducing AI-powered image enhancement directly in Bluestone PIM.
    A new tab can be made available in the Asset's details panel, where users can prompt the AI - powered by Google’s Nano Banana - for improved visuals and editing support.

    ai image enhancer

    Interested in trying it out? Reach out to our support team to learn more: support@bluestonepim.com

Improvements66

  • Completeness requirements: Support for both directions of two-way relations
    Completeness requirements can now be configured independently for each direction of a two-way product relation, allowing each category -  such as main products and accessories - to enforce its own data quality rules.

    Please see the Help documentation for details.



  • XLSX/CSV import: Improved error reporting
    The import error report now captures multiple errors per product in a single run. Previously, processing would stop at the first error encountered for a product, requiring repeated import attempts to surface and fix issues one by one.

    With this change, more errors are reported at once, allowing them to be corrected in a single pass and significantly reducing the number of iterations needed to complete a successful import.

  • Webhook: New event for asset order changes on products
    A new event, Product assets order changed, is now available for webhook subscriptions. An update event is triggered whenever the order of assets linked to a product is changed, allowing integrations to stay in sync with asset ordering updates.

    Please see the Help documentation for more information.

 Fixes67

    • Fixed: Asset labels not filtered by file type
      Resolved an issue where all asset labels were shown when editing an asset, regardless of the file type restriction configured on the label. Only labels applicable to the asset's file type (or configured for all file types) are now displayed.

    • Resolved: Variant-defining attribute propagation setting not preserved on product duplication
      Resolved an issue where duplicating a product would not carry over the propagation setting for variant-defining attributes. This caused a mismatch between the UI and the underlying data - the attribute appeared non-inherited in the UI, but the API still returned it as a defining attribute. The propagation setting is now correctly duplicated along with the product.

    • Fixed: Syncs failing with internal sync error
      Resolved an issue where syncs would fail caused by dictionary values being incorrectly associated with non-dictionary attributes on categories. This occurred in specific cases involving restricted users. The filter logic has been corrected to ensure dictionary values are only associated with the intended attribute.

    • Resolved: Race condition leaving latest asset version unpublished
      Resolved an issue where adding a new asset version and publishing the asset simultaneously could leave the latest version unpublished. The publishing process was reading from a stale snapshot, causing the publish step to be skipped. The fix ensures the current asset state is always read at the time of version creation.

 


Keep track of upcoming releases!
Check out the Bluestone PIM Release Calendar 


Want to be notified about new features, improvements, and fixes?
Sign up to receive our Release notes!