In release 230, we focused on delivering enhancements across multiple Icecat platforms, including the Icecat Brand Cloud and Icecat.biz, while also introducing important security updates and new documentation resources. For additional details, please refer to the previous Icecat Release Notes.
This release brings targeted improvements to the Icecat Brand Cloud, enhancing editor workflows, cleaning up unused UI components, and optimizing configuration data handling. Together, these changes deliver a smoother user experience, better maintainability, and improved system performance.
In this sprint, we improved the Batch Select functionality in Icecat Brand Cloud Search, streamlining the workflow for our editors.
Previously, when editors received product lists containing GTINs, they had to manually verify the GTIN length. Only GTINs with 12, 13, or 14 digits were considered valid. If a GTIN had fewer than 13 digits, editors had to manually add a leading zero before copying it into the Batch Select field. This step, repeated across large feeds, was time-consuming and may lead to human error.
Starting from this release, the system automatically handles GTIN length validation and correction. Editors can now copy and paste GTINs directly from the source feed without worrying about formatting. If a GTIN has fewer than 13 digits, the system will automatically add the necessary leading zeros to ensure the correct GTIN format before searching for the product.
This enhancement ensures a smoother, faster, and more accurate product lookup process in the Icecat Brand Cloud Search, allowing editors to focus on content quality rather than manual data corrections.
We conducted a thorough review of our shared UI components to identify unused, outdated, or redundant elements. By removing obsolete components and consolidating similar ones, we reduced complexity in the front-end codebase, making it more maintainable and easier to extend in future development. This also helps ensure consistent design patterns across the platform.
Our shared configuration table is used across multiple Icecat projects to manage platform settings. Over time, frequent and sometimes redundant read operations had accumulated, creating unnecessary database load.In this release, we:
These changes improve system efficiency, enabling faster retrieval of configuration data and lowering the overall strain on the database.
This sprint, we enhanced the Icecat.biz platform with improvements in SEO, accessibility, performance, and system maintainability.
We updated the Schema.org markups for Organization and Website entities to improve search engine understanding of Icecat.biz content. This enhances discoverability and can lead to richer search result displays.
An accessibility audit was conducted to ensure ARIA labels are used correctly across the site. These adjustments help screen readers interpret UI elements more accurately, improving the experience for users relying on assistive technologies.
To deliver faster and smoother browsing, we implemented several optimizations:
We removed the “Show my offers in the Icecat.biz comparison site” setting from feed upload, as this functionality is currently not supported. By removing this non-functional option, we improve user clarity and reduce confusion during the feed upload process.
We refined logging processes for FO task nodes, reducing noise and improving the efficiency of system monitoring and troubleshooting.
As part of our ongoing security improvements, we have removed the usage of the LoginInfo API from both the Icecat Brand Cloud and icecat.biz front-end applications.
This change is part of a planned deprecation of the LoginInfo API, which will be fully discontinued in upcoming releases. By removing dependencies ahead of time, we reduce potential security risks and ensure a smooth transition to more secure authentication and session management methods.
These updates strengthen platform security, improve compliance with modern security standards, and help safeguard user data.
In this sprint, we conducted an audit of JSON request statistics generated by non-logged-in users. The goal was to evaluate the accuracy and completeness of the collected data, ensuring it reflects real usage patterns.
As part of this audit, we also optimized several data collection points, improving the precision of recorded metrics. These enhancements will provide a more reliable foundation for future analysis and decision-making, helping us better understand user behavior and prioritize platform improvements.
This sprint, we expanded and improved our documentation to help partners and developers work more efficiently with Icecat data.
These updates ensure our partners have clearer, more detailed resources for integrating with Icecat, reducing onboarding time and improving implementation accuracy.
Release 230 continues our commitment to providing a faster, more secure, and user-friendly Icecat ecosystem. By combining UX and performance upgrades with security hardening, accurate data collection, and clearer documentation, we ensure our partners and users can work more efficiently and with greater confidence.
Read further: Icecat, e-commerce, ecommerce, Icecat, release notes
