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

Amazon Introduces Transport Surcharge for Sellers Amid Rising Logistics Costs

Amazon is introducing a new fuel and logistics surcharge for sellers, adding further pressure to…

4 minutes ago

Ingram Micro goes global with Icecat — what this means for vendors

Ingram Micro has officially extended its partnership with Icecat to the global level - a…

17 hours ago

TikTok’s Commerce Model Is Reshaping How Consumers Discover and Buy Products

TikTok is no longer just a social media platform. It is becoming a key player…

1 day ago

Shopping Awards 2026 Highlight Innovation and Growth in Dutch E-Commerce

The Dutch e-commerce sector gathered once again for one of its most established industry events:…

2 days ago

Gen Z’s Growing Skepticism Toward AI Signals a Shift in Digital Behavior

Artificial intelligence has quickly become part of everyday digital life. From search and content creation…

5 days ago

How Stitch Showed the Power of Character Storytelling at Scale with Icecat Product Stories

In licensed commerce, product pages often focus primarily on the item itself, while the story…

6 days ago