News

New Logic of Multilingual (INT) XML Available for Full Icecat users

In this post, we want to inform all data users about the new logic behind the multilingual (INT) XML repository. Historically, the multilingual (INT) XML information was published in all languages regardless of users’ subscriptions to languages or locales. For this reason, Full Icecat users had only access to the local repositories they subscribed to, whereby each repository holds data of one locale only, leading to an unnecessarily larger amount of download requests. But, now, users receive information via the INT repository only for those languages they are subscribed to. To this end, the Icecat platform checks the relevant locales per user and publishes the user’s output XML (in INT) limited to these locales.

Availability for Full Icecat Users

The new logic of multilingual (INT) XML will be applied to all Icecat users in two weeks, so the old logic will no longer be available. However, access to the INT XML repository is only available upon request of Full Icecat users. To activate the new version of INT XML, please get in touch with your local country manager.

For example, the below pictures showcase the difference in the behavior of INT XML in the old (Pic.1) and the new (Pic.2) versions.

Picture 1 – User received information on product features in 75 locales
Picture 2 – User received information on product features in subscribed locales (3 locales on the shown example)

Harmonization

Furthermore, the output of the INT repository is now fully harmonized with the standard language-specific repositories. That includes the following changes you should consider if you had an earlier implementation of the INT locale.  

ElementShort explanation
<xpath><format>
ProductModelDescriptions/NameProduct model name
ProductTitles/TitlesProduct title
GeneratedLocalTitles/titleGenerated local product title
BrandLocalTitles/titleBrand local product title
ProductFeature/PresentationValuesProduct feature presentation value
ProductRelated/Product/NameRelated product name

Please note that if you did not implement the INT locale earlier, you could most likely re-use the existing implementation of your locale-specific import routines with some minor adjustments to enable multiple locales intake.

Finally, there is an Icecat XML manual for more information on the Icecat XML format.

Teymur Asgarov

Recent Posts

Partner Galleries in Every Channel and Full Icecat via MCP: Icecat Release Notes 260

Release 260 completes the move to partner-specific product galleries. After Product XML in Release 259,…

2 days ago

Shopify Launches Canvas for AI-Powered Online Store Design

Shopify has introduced Canvas, a new AI-assisted design workspace that lets merchants build and redesign…

2 days ago

Mastercard Adds New Trust Layer for AI-Powered Shopping

Mastercard is expanding its Agent Pay program with new trust and intelligence services designed to…

3 days ago

U.S. Court of Appeals Rejects Fair Use Defense for Copyrighted AI Training Data

A U.S. appeals court has ruled that AI startup ROSS Intelligence could not rely on…

4 days ago

FTC Opens Investigation Into OpenAI and Anthropic Over AI Safety

The U.S. Federal Trade Commission has opened an investigation into OpenAI and Anthropic as regulators…

5 days ago

Icecat Studio Sprint 105 Release Notes: Opening Icecat Studio to the Agent Ecosystem

Sprint 105 shipped one of our anticipated milestones yet: the Studio MCP server went live…

5 days ago