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.
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:
|
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:
Defined Import Behaviour:
Export Scope:
|
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. |