Icecat Studio – Sprint 99 Release Notes

In Sprint 99, we focused on streamlining bulk content operations, advancing our AI Assistant toward release, and extending variant publication capabilities to the Amazon channel. In parallel, we continued to strengthen the Product Story Framework v2 and expand our auto-import pipeline to make story creation faster and more automated.

Group Actions – Bulk Status Updates

We have extended the Group Actions engine to support mass status updates for targeted assets and variants. Users (currently only internal) can now select multiple items and change their statuses in a single operation, significantly reducing manual effort when managing large content portfolios.

Alongside the engine work, we delivered a dedicated Group Actions UI/UX, making bulk operations accessible directly from the platform interface, and we are currently testing it.

Icecat Studio AI Assistant

Development of the AI Assistant continued across the full stack:

• Story Authoring tools: The assistant now supports attachments, content fetching, and dedicated story tools, moving closer to AI-assisted Product Story creation.
• Client panel: We are building a floating chat panel that connects to the streaming backend. Users will be able to open the assistant from the header, send prompts, see streamed answers with tool cards and deep links, manage chat sessions, and approve mutating actions (such as asset creation) via a confirmation gate — with sessions surviving page reloads and reconnects.
• Quality assurance: The AI Chat backend has been covered with unit and integration tests to ensure reliability ahead of release.

Variant Publication – Amazon Channel Scope

We started work on publishing versioned story variants to Amazon. The agreed logic:

• Single version: If an Amazon variant has only one version that can be pushed via the API, the standard existing publication flow applies.
• Multiple versions: All versions are pushed as drafts to Amazon Vendor Central. Only the version with Approved status on our platform is published; the others remain Unpublished and can be previewed.
• Status synchronization: Variant statuses will be kept in sync with Vendor Central, including cases where a status is changed directly on Amazon rather than through our platform.

Variant Publication Scheduling & Custom Naming

We continued developing the backend for publication scheduling with periodicity and custom name support for story variants. This builds on the versioning foundation introduced in previous sprints and enables time-sensitive campaign workflows (e.g., seasonal story versions published on a schedule). UI testing is planned as the next step.

Auto-Import Pipeline

Our import automation received two notable upgrades:

• Styles & Decorators: Product Stories created through the import functionality from raw formats can now include styles and decorators. This means imported stories can be visually polished from the moment they are created, without additional manual design work.
• Producers: We are preparing producer-side imports to be processed by mappers and the rest of the import pipeline, paving the way for fully automated brand feeds.

Product Story Framework v2

Work on the next-generation framework continued on two fronts:

• Builder/Player: Ongoing development and refinement of the Story Builder and Player components.
• Memory optimization: We resolved a memory leak in the new framework, significantly reducing its memory footprint and improving stability.