Bluestone PIM Release 73-1

January 7, 2026 - Highlights


New features

Improvements

Fixes


 

New features65

  • Completeness: Product type-specific requirements now supported
    You can now define completeness requirements based on product type, offering greater flexibility and control - especially if you are using variant modeling with inherited product data and assets.
    This enhancement allows you to tailor completeness rules more precisely across different product types in your assortment. Please see the Help documentation for details.

    completeness requirements product type

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



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

  • Shopify connector: Easily manage product data sync from Bluestone PIM
    ℹ️ Currently available in the Test environment ℹ️
    You can now manage the synchronization of product data from Bluestone PIM to one or more Shopify stores in an easy way.

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

Improvements

66

  • Completeness: Removed uniqueness restriction
    You can now define multiple completeness requirements with the same main parameters, enabling more flexibility - especially when targeting different product types.

  • Languages: Improved handling of attribute definition translations
    We've addressed two translation-related issues to improve flexibility and alignment with expected behavior:
    • Allowing removal of attribute name translations
      You can now clear an existing translation for an attribute definition name by leaving the field empty and saving.
    • Partial translation of select-attribute values
      It's now possible to save translations for only some values in a single- or multi-select attribute definition. Any untranslated values will follow the fallback context logic, if one is configured.

  • Product overview tab: Improved visibility logic for the completeness score widget
    The completeness score widget is now only shown when relevant:
    • If no completeness requirements are defined for the organization, the widget will be hidden.
    • If requirements are defined but none apply to the current product, the widget is shown with the message: “No completeness requirements apply to this product”.

 Fixes

67

  • Product sync: Resolved issue with version conflict errors
    We’ve fixed an issue where syncing product updates failed due to a "Version conflict" error. This prevented users from proceeding until they manually retried the sync, sometimes multiple times. The sync process is now more reliable and handles version conflicts correctly, reducing the need for repeated manual attempts.