In Release 229, we delivered a series of updates aimed at improving data accessibility, strengthening security, boosting performance, and aligning with accessibility standards. This sprint includes the introduction of EPR and packaging data export enhancements, secure API tokens for brand users, significant EAA compliance improvements, faster and more accessible category statistics pages via SSR, and several other improvements. For additional details, please refer to the previous Icecat Release Notes.
In this release, we are introducing enhancements to the way product relations with packaging categories are displayed in product XML and JSON exports. These changes aim to make packaging data delivery more targeted, efficient, and flexible, so that only the users who need this information receive it, while others can work with lighter, faster product feeds.
In our previous release notes, we described the process by which packaging data is added to Icecat. Brand users create products in a packaging category. These products are then linked to their corresponding master products via the relations functionality.
With the current update, we have refined how these relations are presented in XML and JSON exports, ensuring that packaging data is structured, accessible, and permission-based.
A dedicated <Packages> section is now available in the product XML for channel partners whose user profile has the setting “Access to packaging data in product XML” enabled by their account manager.
This approach allows interested users to receive full packaging details, while other users can keep their XML output lightweight by excluding packaging data.
When enabled, the <Packages> section will appear as follows:
<Packages> <Package> <Product ID="12345678" Prod_id="123456#MPN" Name="product_name"> <Category ID="9563"/> <Supplier ID="1"/> <GTINs> <GTIN Type="GTIN12" Value="123456789012" Approved="1"/> <GTIN Type="GTIN13" Value="0123456789012" Approved="1"/> </GTINs> <Names> <Name langid="1" Value="localized_product_name"/> </Names> </Product> <PackageLocales> <PackageLocale ID="0" langid="0"/> </PackageLocales> </Package> </Packages>
Field details:
Localization Rules:
A new “Packages” section has been added to the JSON export.It is available to users who make a granular request with the parameter: content=packages.
The JSON structure mirrors the XML format, for example:
"Packages": [ { "CategoryID": 9563, "IcecatID": 12345678, "ProductCode": "123456#MPN", "BrandID": 1, "ProductName": "localized_product_name", "GTINs": [ { "GTIN": "123456789012", "IsApproved": true } ]
With this release, we ensure that EPR and packaging data is more accessible, controlled, and streamlined, helping our partners meet compliance needs while maintaining optimal data performance.
Our brand users who rely on autoimport workflows encountered a challenge when two-factor authentication (2FA) was enabled on their accounts. While 2FA is essential for keeping accounts secure, it requires the manual entry of a time-based key stored in a safe location. This manual step makes automated imports impossible, as the process cannot complete without human input.
With this release, we have solved this issue by extending API Token functionality to brand users, bringing them the same secure and convenient integration capabilities already available to channel partners.
Key updates:
When making requests to the PUSH-API, API tokens must be passed in the HTTP request headers. This differs from the existing AccessKeys method, which allows credentials to be passed in the query string or URL. Using headers is a more secure and recommended approach.
With these improvements, brand users can confidently use autoimports without lowering their security standards, ensuring both operational efficiency and account safety.
In this release, we have delivered a set of accessibility-focused enhancements across our Icecat Generated PDF, icecat.biz product pages, and Live HTML services, ensuring better alignment with European Accessibility Act (EAA) requirements. These updates improve the usability of our content for all users, including those relying on assistive technologies.
Following a comprehensive audit of our Icecat Generated PDF using Claude AI, we identified several areas for improvement to meet EAA compliance standards. The following changes have been implemented:
In previous sprints, we added alt texts to numerous visual elements across our website. In this release, we extended this work by:
We have improved accessibility in the Gallery block by adding meaningful alt texts to all elements:
With these updates, we continue to advance toward full accessibility compliance, ensuring our product information is equally available and understandable for all users, regardless of ability or browsing method.
In this sprint, we migrated the Category Statistics functionality on icecat.biz to Server-Side Rendering (SSR). This change optimizes how these pages are rendered and delivered, resulting in faster load times, better accessibility, and improved SEO.
Previously, Category Statistics pages were rendered on the client side, which could delay meaningful content display and affect performance metrics. By switching to SSR, key content is pre-rendered on the server, reducing initial load times and improving the way search engines and assistive technologies process the page.
Below are the before-and-after Lighthouse scores following the migration to SSR.
Results Summary:
By moving Category Statistics to SSR, we have made these pages more efficient, more user-friendly, and better optimized for search engines, providing a better experience for all visitors.
In this sprint, alongside our major feature work, we delivered several improvements, clean-ups, and security preparations across our platform. These changes contribute to a more consistent user experience, a cleaner codebase, and a stronger security posture.
We have added a “Contact details” tab to the catalog object cloud product page, following the same approach already implemented for the icecat.biz product page for non-logged-in users. This ensures consistency in the way contact information is presented across different Icecat services, providing users with easy access to relevant details in a familiar format.
Old Product History and Old Editor Journal user interfaces are disabled. These legacy interfaces have now been retired, reducing maintenance complexity and encouraging the use of new fully supported UI components.
We have removed deprecated and unused Perl code, helping to streamline the platform and reduce potential technical debt. This clean-up improves maintainability and reduces the risk of outdated code affecting future developments.
We have begun preparing the system to disable the unsecured LoginInfo API. This change will enhance account security by ensuring that only secure authentication methods remain available for accessing user data and performing login-related operations.
These developments are critical investments in stability, security, and maintainability of the Icecat ecosystem.
Release 229 reflects our ongoing commitment to delivering secure, high-performing, and user-friendly solutions across the Icecat ecosystem. By combining technical optimizations, accessibility upgrades, and security-focused developments, we continue to improve the value and reliability of our services for all partners.
Read further: Icecat, accessibility, e-commerce, ecommerce, Icecat, release notes
