This release completes the move of Icecat Live to a content delivery network (CDN), prepared in the previous release and running since 18 November. Icecat Live now answers from locations around the world and keeps serving product content when Icecat’s own systems cannot be reached. Channel partners who embed Icecat Live can also ask it to stay silent for products restricted to their account. On icecat.biz, search results put the exact product first and show every applied filter in one place, catalogue matching now reads brand names in every alphabet, and the groundwork for Catalog Coverage figures continued. Together, these changes make Icecat content faster to reach, easier to find, and more dependable to receive.
For the previous release, see Icecat Release Notes 262.
Since Wednesday, 18 November 2026, Icecat Live has been delivered through a content delivery network (CDN). This change covers both Icecat Live delivery methods:
While the previous release prepared the infrastructure for this transition, this release completes it. All channel partners using Icecat Live are now receiving content through the CDN.
A CDN caches Icecat Live content across multiple locations worldwide, serving requests from locations closer to users.
This means that Live HTML product blocks can load faster for shoppers, while Live JSON requests can be served closer to channel partners. It also improves service availability by keeping cached content accessible even when Icecat’s own systems are temporarily unavailable.
Live HTML is an integral part of a channel partner’s product page, while Live JSON supplies product data to their catalogue. Neither should depend on a single infrastructure location.
With this release, both delivery methods benefit from a more distributed, reliable, and resilient infrastructure.
Only Open Icecat product content that is identical for all eligible users is cached and served through the CDN. This includes sponsored product content without brand restrictions, publication restrictions, or private content.
Product Stories follow the same rules. The Product Story of an unrestricted sponsored product is delivered through the CDN in both Live HTML and Live JSON, just like the rest of the product content.
All other content continues to be served directly by Icecat, as before. This includes:
Icecat continues to validate access rights for every such request, ensuring that content intended for one partner is never shared with another.
Images, video, PDF files and other media are not part of this step and are delivered as they are today.
Content is cached for minutes rather than hours. Updates, corrections, and content withdrawals are reflected within minutes, just as before.
Channel partners and brand owners using Icecat Live do not need to make any changes to their existing integrations. The endpoint address, authentication methods, and response formats remain unchanged. The widget continues to update automatically with each Icecat release. Channel partners who host their own copy of the widget are also unaffected.
The only group of users for whom Icecat recommends a change is described in the following section.
A CDN is designed to efficiently handle large volumes of requests from distributed users, such as shoppers browsing product pages. However, its protection mechanisms may temporarily block requests from a single IP address if the request volume is too high. In such cases, requests may time out without returning an HTTP error code.
This primarily affects channel partners with large catalogues with high-volume Live JSON requests from their own servers, for example, during an initial catalogue import or a scheduled full catalogue refresh.
Channel partners using Live HTML on their product pages and those making Live JSON requests at moderate rates are not expected to be affected.
Icecat Product JSON is available through two endpoints:
Both endpoints support the same request paths, parameters, and authentication methods and return the same responses. Switching to the alternative endpoint requires only a domain change, with no other integration changes.
Icecat’s existing rate limit of 100 requests per second per IP address remains unchanged for live-origin.icecat.biz endpoint. Requests exceeding this limit receive an HTTP error response that the integration can identify and handle.
For further details, please refer to the Manual for Channel Partners: Icecat Product JSON.
A product may become unavailable to a channel partner after it has been integrated into the partner’s webpage, for example, if a brand restriction is introduced or the product’s release date has not yet been reached. The product remains on the channel partner’s website, but Icecat Live HTML returns an error when its content is requested.
With this release, channel partners can configure Icecat Live HTML to suppress error messages in these specific cases.
Live HTML and Live HTML v3 now support a new optional request parameter, hideErrors.
When hideErrors=restricted is specified, Icecat Live returns an empty response instead of an error in the following cases:
No Icecat content is displayed on the product page, and no error is reported in the visitor’s browser console.
This functionality applies to both the complete product datasheet and individual content elements, such as the image gallery, product title, specifications, or Product Story.
Channel partners using the Icecat Live script only need to add the new parameter to their requests. The script handles empty responses silently, leaving the existing Live container and any partner-defined placeholder unchanged.
The hideErrors parameter is optional. Requests that do not include it continue to be handled as before.
All other errors retain their existing HTTP status codes, error codes, and messages. The restricted value applies only to products that exist in Icecat but are restricted for the channel partner’s account or have not yet been released.
Other scenarios remain unaffected, including:
The hideErrors parameter accepts a comma-separated list of values, following the same format as the content parameter. Unknown values are silently ignored, ensuring that incorrect values neither suppress errors nor cause requests to fail.
Each supported value retains its original scope. Any additional error types introduced in the future will receive their own values, ensuring that channel partners never unintentionally suppress errors they did not explicitly choose to hide.
The hideErrors parameter is available exclusively for Live HTML and Live HTML v3. Live JSON responses remain unchanged, whether or not the parameter is included.
When hideErrors=restricted is enabled, requests for restricted products are treated as successful requests with an empty response. As a result, the channel partner’s integration can no longer distinguish between a restricted product and a product that simply has no content of the requested type.
Integrations that react to errors, for example, by retrying a request using a different product identifier, should take this behaviour into account. With the parameter enabled, these errors are no longer returned.
Channel partners who need to identify when a product becomes restricted should leave the parameter disabled to retain the existing behaviour.
However, for a more reliable way to track product availability, Icecat recommends checking product availability in the Icecat Index Files or using a Personal Index File (PIF), which reflects product availability for the channel partner’s catalogue and account.
This release makes search results on Icecat.biz easier to read and act on: users who search by product code or GTIN see their exact product first, can confirm which code matched at a glance, and can see and control every applied filter in one place.
When a search matches a product code or GTIN exactly, the matching products now appear in a separate Exact match section at the top of the results, ahead of the Other results. Each exact match is shown as a highlighted card with the matched identifier clearly marked, and products are never repeated between the two sections. The total number of products found still covers both sections.
Exact matches always stay on top, while the selected sort order applies to the other results. When a search has no exact match, results are shown as one list, as before.
Users who search by product code or GTIN reach the product they want immediately, without scanning through related results.
Each search result card now shows the product’s GTIN under its product code. When a product has several GTINs, the card shows the one that matched the search, with the matching part highlighted, so users can see at once which code led them to the product. Hovering over a value shows whether it is a product code or a GTIN.
When a search is recognized as a brand name, a clear banner now lets you limit results to that brand with a single button. Once applied, the banner confirms that only that brand’s products are shown and offers one button to search all brands again. The brand also appears as selected in the filter panel, and removing it there has the same effect.
Users can reach a brand’s products in one click and always know which set of results they are looking at.
The search keyword now appears as a chip at the top of the filter panel, directly under “What are your requirements?”, alongside the other applied filters. Clicking × on the chip clears the keyword and returns all products matching the remaining filters. The × on all filter chips is now black, so it is easier to see.
Searching by the beginning of a product code now shows all products whose code starts with it, with no limit on results. Users no longer miss product variants that share the same code prefix.
Employees of channel partners and brand owners often access icecat.biz from corporate laptops using company security software. Such software can route traffic from multiple employees through a shared IP address, making legitimate traffic appear unusually high.
Icecat now better recognises these corporate network configurations, allowing legitimate users to access icecat.biz without unnecessary interruptions.
Product pages, specifications, images, country and language flags, search functionality, and document downloads continue to work as expected.
This release brings two improvements for channel partners who match their catalogue with Icecat, download Icecat files, or read the product export.
Channel partners upload their catalogues to Icecat to match their products with the Icecat catalogue. Brand names play a key role in this matching process, and many contain special characters, such as Générique, Dätwyler Cables, Telegärtner, RØDE, Weidmüller, and Güde.
Catalogue matching now preserves brand names exactly as provided by channel partners, ensuring that special characters are handled correctly. Products from these brands go through the standard matching process and, when successfully matched, are included in the channel partner’s Personal Index File (PIF) and Personal Catalog File (PCF).
This improvement applies to all alphabets and writing systems, not just Latin characters with accents.
Brand names containing trademark symbols remain supported. Icecat first searches for an exact match. If no matching brand is found, a second lookup is performed without additional symbols, allowing names such as Logitech® to match Logitech.
The matching logic for product codes and GTINs remains unchanged.
The unmatched products report now preserves the original brand names, product codes, and GTINs exactly as provided in the channel partner’s catalogue. This makes it easier to identify unmatched products and address coverage gaps.
Channel partners downloading gallery and multimedia archives from Icecat often use download tools that retrieve large files in multiple parts simultaneously.
Icecat now retrieves only the requested portion of a file instead of processing the entire archive. This improves download efficiency, reduces unnecessary server load, and allows download tools using multiple parallel connections to complete downloads faster.
Requests for the final bytes of an archive are also handled correctly, allowing compatible archive readers to access archive information without downloading the entire file.
Additionally, files that Icecat decompresses during delivery, such as Index Files and Reference Files, no longer report the compressed file size in the response headers. This prevents download tools from prematurely terminating downloads because the reported file size doesn’t match the content being delivered.
Icecat is developing a new Catalog Coverage page that will allow channel partners to see how much of their catalogue is covered by Icecat.
While the page is not yet available to users, this release introduces several foundational improvements to ensure accurate and reliable coverage figures from day one:
The Import and Export page has also been migrated to the current icecat.biz frontend architecture. Its appearance and functionality remain unchanged, while the underlying implementation is now ready to support catalogue coverage figures.
The Catalog Coverage page itself is planned for one of the upcoming releases.
Building on the groundwork from the previous sprint, we continued work on the upcoming Catalog Coverage metrics page this sprint. The focus was on making sure the figures the page will show are accurate and reliable from day one:
The Import/Export page has also moved to the new Front Office app. It looks and works exactly as before, and is now ready to host the new coverage insights.
Catalog Coverage has no visible changes yet. The Catalog Coverage metrics page will follow in upcoming releases.
Most of this release is work that no channel partner and no brand owner will see directly. It is the work that keeps Icecat fast, accurate and secure, and that makes the next visible improvements cheaper to build.
Icecat delivers product content through multiple channels, each of which must determine which products an account can access. Previously, several delivery channels maintained their own product access rules.
With this release, the Personal Catalog File (PCF) and real-time CSV export now use the central product permissions service.
Product availability and access restrictions for channel partners remain unchanged. They continue to receive the same products, and the reasons for denied access remain unchanged.
Centralising product access rules simplifies future development and maintenance. When new account types, restrictions, or market-specific access rules are introduced, teams can manage them in one place rather than implementing them separately across multiple delivery channels.
This reduces the risk of inconsistent behaviour and makes future changes easier to introduce.
This release introduces several improvements to product gallery management, image access rights, and performance:
These improvements make gallery management more efficient, improve the visibility of content restrictions, and enhance overall gallery performance.
The Icecat Model Context Protocol (MCP) server, which provides Icecat product content to AI agents, previously maintained a separate list of supported content locales. With this release, the MCP server retrieves the list of supported locales directly from Icecat.
As a result, Kazakh is now available through the MCP server to accounts with the corresponding access rights. Any future additions or updates to supported locales in Icecat will automatically become available through MCP without requiring a separate MCP server release.
Existing MCP integrations remain unaffected, and users do not need to take any action.
This release introduces several security improvements across Icecat services:
This release includes several infrastructure, performance, and maintenance improvements aimed at strengthening the reliability and operational efficiency of Icecat services:
These improvements contribute to more reliable content delivery, greater system stability, and more efficient release validation.
For channel partners, this release introduces CDN delivery for eligible Icecat Live content, an option to suppress access restriction errors in Live HTML, improved search relevance on icecat.biz that prioritises exact product matches, multilingual brand name matching, and faster, more reliable large file downloads.
For brand owners, optimised sitemaps help search engines discover relevant product pages more efficiently, supporting better product visibility. Kazakh product content is now also available through the Icecat MCP server to eligible accounts.
Behind the scenes, Icecat continued laying the groundwork for the upcoming Catalog Coverage page, along with improvements to product access management, image rights management, security, performance, and infrastructure reliability.
The Catalog Coverage page is planned for an upcoming release.
Channel partners and brand owners with questions about how this release affects their integrations are encouraged to contact their Icecat account manager.
North Korean hackers are using increasingly sophisticated social engineering techniques to steal cryptocurrency and infiltrate…
Anthropic’s public debut on the Nasdaq today under the ticker "ANT" prices shares at $83,…
The European Commission has proposed new consumer protection rules to tackle manipulative practices across online…
Anthropic, the company behind the Claude AI assistant, is generating billions in revenue, but developing…
Icecat and The Walt Disney Company Benelux have successfully launched Enhanced Product Stories for licensed…
China has blocked SoftBank Group's planned acquisition of ABB's robotics business in the country, creating…