20th August 2026

No.

Feature

Description

1.

Ability to map and view ETIM custom attributes on AI Mapping Finalization screen in SKU Onboarding Portal (SOP)

Introducing ETIM attribute and feature mapping, enabling distributors to map fields in custom import files to ETIM features. Users can map fields to ETIM features and specify whether the value includes a feature code and UoM details including Metric UoM, Imperial UoM, or no UoM. The mapped ETIM data can then be reviewed from the SKU Journey screen through the ETIM Data view, with support for viewing technical data across different ETIM versions.
The AI Finalization screen supported data only in a specific structured file format, and ETIM features was not available for selection during mapping.
With this enhancement, distributors can efficiently manage ETIM-specific attribute mapping during AI Mapping Finalization and review the resulting technical product data across ETIM versions in the SKU Journey, improving the accuracy and visibility of ETIM data during product onboarding.

2.

Ability to import SKUs with attributes match for Eclipse ERP import

Enhanced Eclipse ERP connector imports with flexible SKU matching options, allowing users to match SKUs in the input file with catalog SKUs using either SKU Item Id or a custom list of attributes. When custom attribute matching is selected, users can add multiple attributes and define matching conditions. This gives users greater control over how SKUs are identified and matched during the import process.

3.

Enhanced Submit Button Behaviour During File Upload in SKU Onboarding Portal (SOP)

Enhanced the File Upload Screen in SOP to keep the Submit button disabled while a file is being uploaded and enable it only after the upload reaches 100%. This prevents users from submitting an incomplete upload and helps avoid import errors caused by submission before the file upload is complete.

No.

Module

Problem Summary

Resolution

1.

SOP

When a filter was applied on the Field Formatting screen, expanding a collapsed group displayed all fields instead of only the fields matching the active filter.

Updated the filtering behavior to retain the applied filter when expanding collapsed groups, ensuring that only matching fields are displayed consistently in both expanded and collapsed groups.

2.

PCC

The Save button on the Product 360 screen remained enabled even when no changes were made to the SKU, allowing redundant save operations and generating duplicate audit records.

Updated the Product 360 Save button behavior to enable it only when the SKU has actual unsaved changes. The button remains disabled when no changes are made and is disabled again when all changes are reverted, preventing unnecessary save operations and duplicate audit generation.

3.

PCC

Filtered digital assets were not deleted when users selected the option to delete all assets matching the filter condition. The bulk deletion returned “No Assets found for deletion”, while manually selected assets could be deleted successfully.

Updated the bulk asset deletion logic to correctly resolve the Catalog Key when it is not provided, allowing filtered assets to be identified and deleted successfully.

4.

SOP

The Finalization screen allowed the same unique identifier from the uploaded file to be mapped to multiple template fields, allowing users to finalize the mapping and potentially resulting in data loss during import.

Updated the finalization validation to prevent users from finalizing a mapping when the same unique identifier is mapped to multiple template fields.

5.

SOP

Passthrough attributes created from the AI Mapping Finalization screen could be saved with an invalid attribute when the attribute was created in the main catalog and synchronized to the staging catalog.

Updated the attribute creation flow to resolve and use the corresponding staging catalog attribute after synchronization, ensuring that the saved mapping remains valid for subsequent selection and validation.

6.

SOP

Issues found in Passthrough Attribute handling:

• Passthrough attributes could be incorrectly resolved to an unrelated attribute with the same name.

• UoM values could be read from an adjacent column even when that column was not configured as a UoM source.

• The attribute existence check could retrieve unnecessary catalog-wide data, impacting import performance for large catalogs.

Fixes applied to Passthrough Attribute handling:

• The attribute check is now scoped to only passthrough-tagged attributes, preventing values from being incorrectly merge to an unrelated plain attribute that shares the same name. Attribute name matching is now whitespace-safe

• Updated UoM extraction to read from an adjacent column only when it is explicitly configured as a Passthrough UOM on right column source.

• Optimized the attribute existence check to improve import performance for large catalogs.