News

Icecat Release Notes 152: Auto-Generated Bullet Points

In these Icecat Release Notes 152, we further explain the development of the auto-generated bullet points. Also, we will highlight some improvements and fixes. Please, find here the previous Icecat Release Notes.

Auto-Generated Bullet Points

In the previous release notes, we mentioned the start of the development of auto-generated bullet points. This auto-generated bullet points feature allows us to add Bullet Points at the product category level. However, it will work only for low-level categories. In this sprint, we launched the support of auto-generated bullet points on the icecat.biz portal and in XML files.

To further explain the logic behind auto-generated bullet points on the product page at the Icecat.biz portal. Firstly, the Icecat backend checks the availability of manually entered Bullet Points. If manually entered Bullet Points are not provided, then the algorithm will provide the auto-generated Bullet Points of the respective product category.

For XML files, the logic is as follows: The Icecat system publishes auto-generated Bullet Points in the separate tag <GeneratedBulletPoints> alongside the manually entered Bullet Points that are already published under the <BulletPoints> tag.

The XML tag structure for auto-generated bullet points is as follows:

<GeneratedBulletPoints><GeneratedBulletPoint Value="" langid="" No=""/></GeneratedBulletPoints>
  • <GeneratedBulletPoints> is a mandatory tag and will present in a single instance. If a product cannot generate auto-generated bullet points, then the <GeneratedBulletPoints> tag will be added with an empty value.
  • <GeneratedBulletPoints> is the parent of <GeneratedBulletPoint> tags and cannot contain any other tags.

Attributes of the <GeneratedBulletPoint> tag:

  • Value – the value of the auto-generated bullet point.
  • langid – locale identifier.
  • No – the order number of the Bullet Point among other Bullet Points for this locale.

Other improvements in Icecat Release Notes 152:

  • We fixed the issue regarding the import of HP videos that some products have more than two videos. This was against the previous policy.
  • Further, we fixed a bug on the product mapping interface
  • Added new value, “Carbon Footprint” to the list of predefined descriptions for “other digital assets” Multimedia type
  • Added ThumbURL and PreviewURL parameters for videos that are not in our server
  • Fixed the issue regarding HP import. HP import did not import type “annotated product images” from the HP feed into Icecat system.
  • Improved the performance of HP import.
  • Fixed an issue regarding the Icecat search bar. After searching a product by entering its parameters, the product was not found due to the auto-selected category of the product, which was irrelevant for this case.

Teymur Asgarov

Recent Posts

Building Partner Galleries in Brand Cloud and Multilingual MCP: Icecat Release Notes 261

Release 261 completes the partner gallery story. Release 260 delivered partner-specific galleries to every delivery…

19 hours ago

Retailers Divided Over AI Shopping Agents as Agentic Commerce Expands

Retailers are taking different approaches to AI shopping agents, with some welcoming automated purchases while…

19 hours ago

The Night We Were Ready to Switch Icecat Off

A 9.2 severity PHP flaw went public on Wednesday; the first scanner reached us the…

1 day ago

Story-in-Story, a Smarter AI Assistant & Framework v2: Icecat Studio – Sprint 106 Release Notes

Sprint 106 touched several parts of the platform. The AI Assistant got a new engine…

2 days ago

EU Product Identifiers from 1 November 2026: What NS-PID, S-PID and M-PID Mean for Sellers

From 1 November 2026, the EU requires product identifiers on the customs declaration for online…

2 days ago

QVC and Kohl’s Split Over the Future of Agentic Shopping

Retailers are taking different approaches to AI shopping agents, with some welcoming automated purchases while…

2 days ago