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

easyGroup Enters Parcel Delivery, Bringing a Familiar Brand to E-commerce Logistics

The easy brand is already well known across Europe through businesses such as easyJet, easyHotel,…

2 days ago

Icecat Commerce Release Notes Icecat PIM 3.14.0

We’re coming in fast introducing Icecat PIM 3.14.0 with a release focused on pricing flexibility,…

3 days ago

Icecat Release Notes 252: Enhanced Related Products Export, Improved Matching Accuracy, and New User Engagement Capabilities

Release 252 introduces a range of improvements across product data exports, matching accuracy, reporting, user…

3 days ago

Meet Lena: instant, trustworthy answers about Icecat – in 80 languages

It's 11 p.m., and you're staring at a 403 app_key required error, or weighing Open against Full…

5 days ago

Channel-Specific Product Content: Why One Description Doesn’t Fit All

Your product does not change, but the way people discover it does. So why would…

5 days ago

The making of Lena: from fluent chatbot to grounded assistant

Building a chatbot is easy. Building one you would trust to talk to your customers…

5 days ago