Release notes: Feb 23rd 2026

Avatar
Helena Gerebro
  • Updated

Sections in the article

    Inriver is moving towards more incremental, smaller releases to better and faster accommodate our customers. With smaller, more frequent releases, Inriver will be able to increase the quality and transparency of the releases and identify and mitigate any erroneous behaviour that may be caused by the release much faster. 

    NB! To receive notifications when new release notes are published, please ensure you follow this page by clicking the "follow" button above.  
     

    Please see below for the deployed features and improvements:  

    Brand Store v2

    • Configurable Consent, Acknowledgment & Disclaimer message framework

      What’s new 
      We’ve introduced a standardized and fully configurable Consent, Acknowledgment, and Disclaimer message framework within Brand Store. This feature delivers three new capabilities:

      Configurable Consent Message (Store Entry – Mandatory Acceptance can be configured)
      Store Admins can now configure a consent/acknowledgment message that users must explicitly accept when entering a store for the first time. Acceptance will be persisted, and users will not be prompted again when entering the store, as long as they use the same device and browser.

      Configurable Disclaimer Message (Store Entry)
      A configurable disclaimer can be displayed the first time a user enters a store, requiring confirmation before proceeding.

      Configurable PDP Guidance/Disclaimer Text
      Store Admins can define generic guidance or disclaimer text that is automatically displayed across all Product Details Pages (PDPs) within a store, ensuring consistent messaging across the full product catalog.

      All configurations are managed natively as Custom Templates within Brand Store – Store Admin in the Template section, and no custom development is required.

      What does this mean for you?

      As a Store Administrator, you can now configure store-specific consent, acknowledgment, and disclaimer messages, including customizable content and button labels. You can also apply standardized disclaimer text across all Product Details Pages and reuse templates across multiple stores where required.

      As a Store User, you will be presented with clear, store-specific terms or disclaimers and must confirm acceptance before accessing store content. Once accepted, you won’t be prompted again.

      Why this matters

      This strengthens Brand Store’s compliance posture while improving transparency and trust for end users. It enables consistent legal and informational messaging across stores and Product Details Pages, removes the need for custom solutions, and provides a scalable, future-ready framework that is simple to manage natively within Brand Store.
       

    • Configurable Store Terminology for Product Actions and Cart

      What’s new
      Store Admins can now configure the default “Add to Cart,” “Remove from Cart,” and “Cart” texts to better fit their store use case. The custom labels will appear across product cards, PDPs, the header, and cart modal when configured in the Store template and can be found in the Template section of the Brand Store-Store Admin.

      What does this mean for you?
      You can replace standard e-commerce terminology with wording that aligns with how your store is used, while Store Users will see clearer, more relevant action labels when adding, removing, or managing selections.

      Why this matters
      Brand Store supports diverse use cases beyond traditional product information sharing, and configurable terminology ensures the experience feels intuitive, accurate, and aligned with your business context, without requiring custom development.

    • It has been implemented so that the Storefront set/reset password page (and email) has been enhanced. The password setup and reset messaging has been updated to use clearer, more generic wording that differentiates the initial password creation and password reset scenarios, ensuring a more intuitive and confident user experience.
    • It has been implemented so that the Store Admin now displays a warning message for unsaved changes in each step of the store wizard. A warning message has been added for unsaved changes in each step in the Store Admin wizard when configuring a store.
    • It has been implemented so that Store Admin includes added logic limiting to one multi-search field per entity type when configuring a store. When a field is selected for multi-search, we now disable adding new fields from the same entity type to reduce complexity and the risk of performance issues when multi-searching.
    • It has been implemented so that Store Admin has added new PDF-Template properties for dynamic scaling. New scaling properties have been introduced, enabling configurable PDF-template width and height for improved dynamic scaling and user experience.
    • It has been implemented so that Store Admin, in the Data step, now includes a “select all” option when selecting languages. For a better user experience, when many languages are selected, a select all option is now available.
    • It has been implemented so that Store Admin, in the Access step, has enhanced the hovering to highlight the whole user row. For a better user experience when managing users, we are now highlighting the whole user row so that it is easier to see which user is selected or deselected when changing the access.

    • It has been implemented so that Store Admin has enhanced the UX when working with templates, so that you can save and continue editing the template. Separate “Save” and “Save & Close” actions have been added in templates (Store-template, PDF-template, Email-template, Config-template, and Custom-template) to allow users to save their work without automatically exiting template creation or editing, improving overall usability and workflow flexibility.


    Please see below for the deployed bug fixes: 

    Brand Store v2

    • We have applied a solution to ensure that deactivated CVL still appears in Brand Store filters. It has been fixed so that deactivated CVL values no longer show up in filters in Brand Store.
    • We have applied a solution to ensure that PDF generation from Brand Store includes only the user's first name, while Content Store includes the full name. It has been fixed to correctly populate the full user name (instead of first name only) in PDF downloads, ensuring consistent behaviour and backwards compatibility with Content Store.
    • We have applied a solution to ensure that the issue with showing data in “the Related Products” section when the model is using Link Entities. Updated the linked entities logic to resolve an issue preventing related products from displaying on the PDP, restoring full visibility of related data.
    • We have applied a solution to ensure that the issue with missing images in downloads when selecting transformed asset formats. Fixed the issue when downloading data and selecting transformed formats, so that the generated download file now contains both the data file and the transformed image assets.

    • We have applied a solution to ensure that when Date Time fields are presented in a store, they are not formatted according to the language settings in the browser. It has been fixed so that Date Time fields are now being presented in the expected format based on the user’s language settings in the browser, which is also consistent with how the Date Time value is presented in the PIM portal.


    inriver Implementation Standards

    Inriver's ambition is to collaborate with our partners in providing our customers with the safest and most secure PIM system possible. With that in mind, Inriver is improving the information on our Community to help implementation partners ensure quality, optimize implementations, and avoid pitfalls.
    Read more about Inriver Implementation Standards

    Was this article helpful?

    Still need help? contact us

    Related articles

    Comments

    0 comments

    Please sign in to leave a comment.