17th December 2025

Prev Next

Two glowing star shapes on a gradient background, creating a vibrant visual effect.List of Features

No.

Feature

Description

1.

Introducing SKU Audit Trail and Versioning

The audit trail and versioning system has been introduced to capture a complete point-in-time JSON snapshot of every SKU whenever changes occur. Each snapshot includes user, timestamp, and process details, ensuring full historical visibility.

  • Users can view lifetime SKU history, compare versions, and see detailed differences.

  • UI indicators for viewing history and comparing changes.

  • The system is optimized for performance even across large datasets.

This enhancement provides complete transparency, stronger governance, and improved data reliability.

2.

Magic Uploader Enhancements

The Magic Uploader has been enhanced to improve performance, data quality, and transparency across the ingestion process. Following are the some of the key enhancements:

  • Improved Performance: Fixed cost and latency issues to deliver more stable and faster processing.

  • Expanded SKU Coverage: Enhanced attribute extraction for more complete and accurate SKU data.

  • Better Digital Asset Support: Improved handling and coverage of images and documents.

  • Enhanced Reporting: Added detailed reporting to trace LLM calls and reasoning for better visibility and troubleshooting.

  • Quality Assurance Agent: Introduced a QA agent to perform data quality checks and provide improvement recommendations.

3.

BIF Support for Import/Export of Attribute-Level LOVs and UOMs

BIF export and import have been enhanced to fully support attribute-level Lists of Values (LOVs) and Units of Measure (UOMs) defined in the attribute master.

LOV & UOM Export & Import:

  • BIF export now includes all LOVs and UOMs associated with attributes.

  • Attribute-to-LOV/UOM mappings are preserved in the exported file.

  • BIF import now creates or updates attribute-level LOVs and UOMs and correctly links them to their respective attributes.

  • Any new LOV or UOM values included in the import are automatically created.

Defined Import Behaviour:

  • Attribute LOVs are overwritten during import; values are not appended.

  • Only LOVs provided in the latest import request are retained.

Export Scope:

  • Only attributes that are attached to SKUs are included in the export.

  • Attributes not mapped to any SKU are excluded, even if they exist at the attribute level.

4.

Performance and Reliability Enhancements

Improved performance and stability across Public APIs, UI APIs, and import workflows by introducing asynchronous processing. These enhancements ensure more reliable and efficient synchronization between the Main Catalog and the Staging Catalog, reducing blocking operations and improving overall system responsiveness.

5.

Safeguards for Attribute and Taxonomy Deletion

Deletion rules have been enhanced to prevent removal of attributes and taxonomy from the Main Catalog when they are actively used in templates or downstream configurations. Attributes and taxonomy that are part of Draft or Published templates can no longer be deleted from the Main Catalog.

These safeguards protect template integrity, prevent broken references, and ensure consistent behaviour across the Supplier Portal.

List of Bug Fixes

No.

Module

Bug Fixes

1.

SP

In Field Formatting, UoM selection displays correctly for the first SKU’s LoV but does not appear for subsequent SKUs, preventing repeated UoM visibility.

2.

SP

SKU syncing from the Staging catalog to the Main catalog was taking longer than expected. There was noticeable delay between the SKU moving to Ready to Onboard status and its creation in the Main catalog.

3.

SP

Using “Add to Repository” during supplier-side mapping finalization fails to create the new attribute and link it to the SKU.

4.

SP

Pagination does not work on the SKU Journey screen when more than 25 records are submitted from the Supplier Portal.

5.

SP

Entering a template name that is in a cloned state and clicking Next causes an API error.

6.

SP

In cloned templates, LoV and UoM mappings were not appearing on the Field Formatting page.

7.

SP

Supplier AI Mapping was finalized even when required primary identifiers are not mapped.