At Icecat, every release is designed to improve how partners manage, discover, and distribute product information. Release 253 introduces a combination of customer-facing enhancements and platform improvements that make working with Icecat more intuitive, efficient, and reliable.
Highlights include a redesigned Related & Alternative Products experience, new analytics to optimize product content with data, greater control over long-running product imports, and a range of infrastructure improvements that strengthen the performance, scalability, and future readiness of the Icecat platform.
For additional details, please refer to the previous Icecat Release Notes.
We’ve redesigned the product recommendations experience to provide a more structured and intuitive way to discover related products, split by relation types.
Previously displayed as flat lists under Recommended products and Similar products, products are now organized in collapsible category trees, making navigation and comparison easier while providing a consistent experience across product pages.
The following tabs have been renamed:
Each tab is displayed only when eligible product relations are available.
The Related products tab displays the relation types in a collapsible tree and sorted in the following order:
Within each relation type, products are grouped by categories.
The Alternative products tab is dedicated exclusively to Alternative product relations. Alternative products are grouped by category and displayed in a collapsible tree.
To improve readability and performance, both tabs initially display up to 3 products per category.
When additional products are available, users can load more using the More button, which reveals products in batches of three until the full category is displayed.
This enhancement:
Keeping product content complete and relevant requires more than simply knowing which features exist. It also requires understanding which features are actively used across products and brands, which are becoming more important over time, and which may no longer provide value.
With Release 253, Icecat introduces the Feature Popularity API, a new internal service that provides structured analytics about feature usage within product categories. The API enables editors and taxonomy managers to make evidence-based decisions when creating product content, maintaining taxonomy, and supporting AI-assisted content population.
The Feature Popularity API returns comprehensive statistics for every feature assigned to a category. Requests can be scoped by:
This allows teams to analyze both category-wide trends and brand-specific adoption patterns.
Instead of providing simple usage counts, the API delivers a rich set of pre-calculated metrics, including:
Because these metrics are calculated from current product data, they provide an accurate picture of how product specifications evolve over time.
The new API was designed to help editorial and taxonomy teams answer important questions such as:
By replacing assumptions with measurable usage data, Icecat can continuously improve both manual editorial workflows and AI-assisted content generation.
The Feature Popularity API lays the foundation for more intelligent product data management by making feature usage measurable instead of subjective. As Icecat continues investing in AI-driven workflows and taxonomy optimization, these analytics will help ensure that editorial efforts focus on the attributes that deliver the greatest value to partners.
Large product imports can take time to complete, especially when processing extensive catalogs or multimedia updates. Until now, users had to wait for an import to finish even after discovering an issue in the source file.
Release 253 introduces the ability to cancel running import tasks directly from the Import Tool. This enhancement gives editors greater control over long-running imports, helping prevent incorrect data from being imported while reducing the need for manual cleanup afterward.
Users with the appropriate permissions can now cancel an import while it is still running. A dedicated Cancel action is available for eligible import tasks, allowing users to stop processing without waiting for the entire job to complete. Before cancellation begins, the system requests confirmation to help avoid accidental interruptions.
Canceling an import does not discard work that has already been completed.
If part of the import has already been processed, those successfully imported records remain in the system, while only the remaining unprocessed data is skipped. This approach protects completed work while preventing unwanted data from continuing through the import pipeline.
Once an import is canceled, the task status is updated accordingly, and users receive an import report showing the results achieved before the cancellation occurred.
The report includes only the records that were processed successfully, providing a clear overview of what was imported and what was not.
The cancellation feature is available throughout long-running import processing, allowing users to react quickly if they discover incorrect source data, configuration errors, or other issues that require stopping the import before completion.
Permission rules ensure that users can manage only the import tasks they are authorized to control, maintaining a secure and predictable workflow.
By allowing imports to be stopped at the right moment, this enhancement helps reduce the risk of incorrect product data entering the database while minimizing the time required to correct mistakes. Instead of waiting for an entire import to finish and cleaning up unwanted changes afterward, editors can immediately fix the source file and launch a corrected import.
Not every release is defined by new user-facing functionality. Some of the most valuable improvements happen behind the scenes, strengthening the platform that powers Icecat services every day.
Release 253 includes a broad set of infrastructure, performance, and maintenance improvements designed to increase platform reliability, simplify future development, and improve operational efficiency. While many of these changes are invisible to end users, they contribute to a more stable, scalable, and maintainable platform for all Icecat partners.
To improve the delivery of large datasets, Icecat optimized the way large files are uploaded to object storage. By increasing the multipart upload chunk size, the platform significantly reduces the number of upload requests required for large files.
This optimization decreases communication overhead between services and storage, allowing large index files to be published more efficiently while reducing infrastructure load. The improvement is fully transparent to users and does not require any changes to integrations.
As Icecat continues its transition toward a microservice architecture, Release 253 introduces a standardized approach for publishing APIs under a single, consistent domain.
For developers and integration partners, this means both existing and future API documentation will remain accessible through the familiar api.icecat.biz entry point. Maintaining a unified documentation location simplifies API discovery while ensuring a smooth transition as new microservice-based APIs become available.
Several enhancements were introduced to strengthen monitoring and operational support.
Internal reporting processes now provide more detailed execution information, making scheduled jobs easier to monitor and troubleshoot. Additionally, reporting tools can now generate historical metrics for specific reporting periods, giving support and engineering teams greater flexibility when investigating incidents or regenerating operational reports.
The release also includes improvements to internal logging and error handling, helping engineering teams detect, diagnose, and resolve operational issues more efficiently.
Release 253 continues Icecat’s ongoing investment in modernizing its technology stack.
Several internal components have been refactored to use modern development patterns, improving maintainability and making future enhancements easier to implement without affecting existing functionality. At the same time, obsolete legacy components that were no longer used have been safely removed, reducing technical debt and simplifying long-term maintenance.
Release quality is equally important as feature development. To strengthen deployment reliability, Icecat introduced additional standardized validation procedures that help verify critical icecat.biz functionality after each release. These improvements contribute to more consistent deployments and reduce the likelihood of production issues affecting customers.
Release 253 demonstrates Icecat’s continued commitment to improving both the user experience and the technology behind it. Whether you’re discovering complementary products, managing large product imports, or integrating with Icecat APIs, these enhancements are designed to help you work more efficiently and benefit from a faster, more reliable platform.
Interested in learning how these new capabilities can benefit your organization? Contact your Icecat account manager to explore how Release 253 can help you optimize your product content, streamline integrations, and get even more value from the Icecat platform.
Read further: Icecat, e-commerce, ecommerce, Icecat, product content, release notes
