Release 256 continues Icecat’s platform evolution with progress on the next-generation Gallery, new user-organization membership management in Brand Cloud, improved distributor catalog imports, and usability enhancements across Icecat.biz. The release also includes reliability and maintenance improvements that strengthen the foundation for future development.
For additional details, please refer to the previous Icecat Release Notes.
In the previous release, we introduced the direction of Icecat’s next-generation Gallery, including locale-specific image ordering and customer-specific galleries. Release 256 takes the next step: building the technical foundation required to make these capabilities reliable, secure, and fully integrated with Icecat’s editorial and publishing processes.
The new Gallery service can now manage the full lifecycle of product images: ingesting source files, generating required image renditions, creating fingerprints, detecting duplicates, and storing the resulting assets.
Cropping also keeps the original image available, allowing new renditions to be generated later without losing parts of the original frame.
The new Gallery must respect the same access rules as the existing Icecat platform.
Editor and brand permissions are therefore being centralized in the Product Permissions service. It can determine whether a user may view or modify a product and in which locales, while considering existing rules such as product ownership, editor assignments, category restrictions, and locale restrictions.
Centralizing these rules also allows future microservices to reuse the same permission logic instead of implementing their own versions.
When content moves into a separate service, Icecat still needs to know that the product has changed. The Gallery can now refresh the product’s last-change information after an update, ensuring that downstream publication and export processes detect the modification.
Product ownership can also be re-evaluated after Gallery changes, preserving existing rules for ownership, editorial attribution, and republication.
The new Gallery also keeps track of where content originates.
Images added through the service can retain the correct data-source information, preserving the distinction between content coming from import feeds and content created manually.
This ensures that moving image management into a new service does not weaken Icecat’s content traceability.
Release 256 also introduces event-based synchronization for user and language data.
When this information changes, future microservices can update their local data instead of repeatedly querying the legacy platform, reducing latency and unnecessary system load.The Gallery can also access the complete Icecat language reference list, allowing locale permissions to be interpreted consistently.
Release 255 introduced the direction of the next-generation Gallery. Release 256 connects the underlying pieces: image processing, permissions, ownership, content traceability, publication synchronization, and supporting platform data.
Most of these improvements happen behind the scenes, but together they reduce migration risk and create a stronger foundation for the user-facing Gallery capabilities planned for the next stages.
Stay up to date with Icecat releases as the next-generation Gallery continues to move from technical foundation to new image-management capabilities.
Release 256 introduces a new user-organization membership management capability in Icecat Brand Cloud. Administrators can now manage which users belong to an organization directly from the Organization detail page, making organization administration more structured and easier to maintain.
A new Users panel is available on the Organization detail page. It provides a clear overview of the users connected to the organization.
Administrators can also open a member’s user profile directly from the list, while organizations with larger user bases are supported through pagination with up to 100 users displayed per page.
Users can now be assigned from the Organization page through an “Add user by login” search.
To prevent conflicting assignments, the search only suggests users who are not currently connected to another organization. Once selected, the user is added immediately and appears in the organization member list.
All supported Icecat user types can be connected to an organization.
Existing members can also be removed directly from the Users panel.
Selecting the remove action opens a confirmation dialog before the membership is deleted, helping prevent accidental changes. After confirmation, the user immediately disappears from the organization member list.
The new functionality also prevents duplicate or conflicting organization memberships: one user cannot be assigned to multiple organizations at the same time. Users without an organization remain fully supported, so existing accounts are not forced into the new model.
Why it matters: Account managers and administrators now have a dedicated place to review and maintain organization membership instead of managing these relationships indirectly. This creates a clearer connection between organizations and their users and provides the foundation for further organization-level functionality in Icecat.
Release 256 improves distributor catalogs imports by preventing products from being dropped because of non-critical category formatting issues.
Previously, a product could be skipped entirely if its category value was too long or contained HTML. Now, Icecat clears the invalid category value and continues processing the product. The product is then created as “Not Categorized” instead of being skipped.
For partners using Icecat for catalog matching, these recovered products also become available for matching rather than disappearing from the import process.
Other important validation remains unchanged. Products with invalid identifiers such as Product code, brand, or distributor product code can still be rejected according to the existing validation rules.
Why it matters: A malformed category should not prevent an otherwise usable product from entering the Icecat catalog. This improvement increases the effective import rate for distributor catalogs, reduces unnecessary skipped products, and gives more products the opportunity to be matched and enriched in Icecat.
This release focuses on removing friction from key user journeys across Icecat.biz. The improvements help users complete product matching with greater confidence and access important account and API settings faster, reducing unnecessary errors, confusion, and navigation effort.
Product matching during catalog import is now clearer and easier to understand. Users receive more explicit guidance on which identifiers Icecat needs to match their products, helping them provide the right information from the start.
The mapping table now clearly communicates the relationship between:
A dedicated helper message explains the matching requirements and highlights that providing all available identifiers can improve matching accuracy.
Required-field indicators further reinforce which identifiers are important for matching.
These improvements help users avoid incorrect mappings, achieve a higher successful match rate, and complete catalog imports with less trial and error. They also reduce the need to contact support when users are unsure which product identifiers to provide.
The “Access details” section has been moved to the top of the My Profile page, putting the information users are most likely to manage directly in front of them.
Users can now access key actions such as Upgrade, Add Authorization, Manage Access Tokens, and Edit Allowed IP addresses directly from the top of the page, without having to navigate through personal profile information first.
By putting these business-critical settings within immediate reach, the update reduces navigation effort and makes subscription and API access management faster and more convenient.
Together, these improvements help users:
The result is a more efficient Icecat.biz experience where users can successfully complete important tasks faster, with greater confidence and less unnecessary effort.
Release 256 also includes a number of behind-the-scenes improvements focused on platform reliability, safer releases, clearer system behavior, and easier long-term maintenance.
We continued improving the way new services and functionality are developed and tested. Teams now have better support for creating isolated test environments, reducing manual setup and making it easier to validate changes before they reach production.
Supporting infrastructure was also modernized to better accommodate new services and reduce the need for service-specific technical workarounds.
Why it matters: stronger development and testing processes help reduce release risks and support faster, more predictable delivery of new functionality.
An obsolete data structure used for product relations was safely removed after confirming that active processes had already migrated to its replacement.
The old structure consumed significant storage capacity despite no longer being needed. Removing it frees resources and reduces a potential platform stability risk.
Infrastructure supporting Icecat.biz was also updated as part of ongoing platform maintenance and reliability improvements.
Brand Cloud now handles certain application failures more gracefully. A problem in one interface component is less likely to result in the entire page becoming unavailable, while errors can be captured for further investigation.
Session expiration has also been improved. Instead of showing multiple confusing errors after a session is no longer valid, users are redirected to log in again.
Why it matters: these improvements reduce disruptive failure scenarios and make it easier for users to recover when something goes wrong.
Several older Brand Cloud components and utilities were simplified or consolidated, while automated quality checks were strengthened to catch potential issues earlier in the development process.These changes are mostly invisible to users but help reduce regression risk and make future improvements easier to deliver and maintain.
The obsolete Countries selector has been removed from the Icecat.biz administration interface.
The underlying setting was already no longer used, while the remaining interface element could incorrectly suggest that delivery countries were still configurable. Removing it makes the interface better reflect actual system behavior.
These developments may not introduce major new user-facing features, but they strengthen the foundation those features depend on. By continuously improving infrastructure, error handling, code quality, and platform maintainability, Icecat reduces operational risk and supports more reliable future development.
Release 256 combines new capabilities with improvements to existing user journeys and platform reliability. From preparing the next-generation Gallery and introducing organization membership management to preserving more distributor products during import and simplifying product matching and account management, the focus remains on making Icecat easier to use, more reliable, and ready for further growth.
Explore Release 256 to discover the latest Icecat capabilities and improvements supporting better product data management and more efficient platform experiences.
Read further: Icecat, e-commerce, ecommerce, Icecat, product content, release notes
