10th September 2026

Prev Next

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

No.

Feature

Description

1.

Ability to edit Node Mapping and Field Transformations in SOP

Enhanced the Node Mapping and Field Transformation screens to allow distributors to edit configurations for suppliers that share the same template.
When one supplier’s unrelated activities (import, transformation, syndication, etc.) were in progress using the shared template, both screens became read-only for all suppliers using that template, preventing the distributor from editing configurations for other suppliers.
With this enhancement, editing is restricted only while the selected suppliers SKU transformation related activities are actively running, allowing distributors to manage configurations without waiting for unrelated supplier activities to complete.

2.

Improved handling of alternate language values in import in SOP

Enhanced the import process to preserve alternate language values when an existing attribute value is updated. The import process used to delete the base language value before adding the new value. Deleting the base language value also removed its associated alternate language values.
With this enhancement, the import process checks for alternate language values before replacing the existing value. When alternates are present, the base attribute value is updated instead of being deleted and re-created, preserving the associated alternate language values. When no alternate values are present, the existing delete-and-add behavior continues to be used.

3.

Implemented file naming convention for downloadable files in Onboarded Supplier Details screen in SOP

Enhanced the Onboarded Supplier Details screen in SOP to apply a standardized naming convention to downloaded files. Downloaded files now follow the format SubmissionName_SupplierName_CustomerSupplierId_YYYYMMDDHHMMSS. The naming convention includes the submission name, supplier name, supplier identifier and file generation timestamp in the file name. The naming convention is applied to both Excel and XML files, making downloaded files easier to identify and manage.

4.

Implemented display of file upload error details in File Upload History for AI Mapping Finalization screen in SOP

Enhanced the File Upload History screen in the Details of Submission tab to display records for files that fail during AI Mapping Finalization when uploaded through Option 3 in SOP. The Actions column now provides relevant actions for failed uploads, including access to the error report where applicable. This enhancement provides suppliers with better visibility into upload failures and helps them identify and troubleshoot issues with submitted files.

5.

Enable real-time SKU onboarding status updates for Supplier and Distributor views in SOP

Enhanced status updates on SKU Journey screen to automatically reflect changes in both supplier and distributor views in SOP. Users no longer need to manually refresh the screen to view the latest status.
With this enhancement, users get up-to-date information during SKU journey.

6.

Ability to filter Unique Identifier Fields on the Field Selection screen in SOP

Added a “Unique Identifier Only” filter to the “Field(s) to be included in template” panel of the Field Selection screen. Users can now apply the filter to view only fields marked as Unique Identifier, making it easier to review these fields when working with a large number of selected fields. Users can clear the filter to return to the complete list of selected fields.

7.

Ability to select attributes across multiple pages in Field Selection screen in SOP

Enhanced the Field Selection screen to support multi-attribute selection across multiple pages in the “Fields in PIM” panel. Users can now select attributes, navigate between pages, and continue selecting without losing their selections. A running count of selected attributes is displayed, and all selected attributes can be moved to the Field(s) to be included in template panel in a single action, making it easier to build selections when working with large number of attributes.

8.

Implemented sequential processing of scheduled imports for the same catalog in PCC

Enhanced scheduled import processing to ensure that multiple imports scheduled for the same time for the same catalog are processed sequentially instead of running in parallel. This prevents multiple imports from being processed simultaneously for the same catalog and provides more consistent catalog processing.

9.

Implemented performance improvement of AI Mapping service in SOP

Optimized the AI Mapping service to improve performance when processing data for catalogs containing a large number of SKUs and SKU attribute values. The query used to fetch attribute values from the staging catalog for the AI recommendation API has been optimized, reducing the processing time required for attribute mapping.

List of Bug Fixes

No.

Module

Problem Summary

Resolution

1.

SOP

The Attribute Mapping panel in the Field Transformation screen had multiple issues affecting connector rendering, loading states, layout, and tooltip behavior.

  • Connectors were missing for certain mapping rules, rendered in the wrong direction for Split rules, remained visible when switching between mapping actions, or flickered when editing mapping rules.

  • The mapping panel could remain stuck in the loading map details state for certain Split-rule mappings, and the skeleton loader displayed an incorrect number of rows.

  • The attribute panels had scrollbar and icon alignment issues, and panel-specific styling could affect dropdown and tooltip overlays across the application.

  • Source and target attribute names did not truncate with ellipsis or display tooltips independently.

Updated the Attribute Mapping panel to address the identified connector, loading, layout, and tooltip issues.

  • Updated connector handling to correctly render, clear, and initialize connections for different mapping rules and actions, including the correct direction for Split rules.

  • Improved loading and skeleton states to correctly handle Split-rule mappings.

  • Updated panel layout and styling to provide consistent scrollbar and icon behavior and prevent styles from affecting other application areas.

  • Updated source and target attribute names to truncate with ellipsis independently and display their full values through individual tooltips.

2.

SOP

When a system created a passthrough attribute during transformation, the attribute could be created in the main catalog first and then in the staging catalog. This causes synchronization issue.

Updated the passthrough attribute creation process to create the required attribute records consistently across the main catalog and staging catalog, preventing synchronization issues during transformation.

3.

SOP

The Field Selection screen displayed an incorrect total number of available attributes, causing pagination to include records that were not actually available. As a result, pagination indicated additional records but returned empty results on the final pages.

Updated the attribute count calculation to match the records available for selection. Pagination now correctly reflects the total number of available attributes, ensuring that all applicable records are displayed.

4.

SOP

When a distributor finalized AI mapping with an alternate language selected, the distributor’s selected locale was not retained on the supplier side in certain mapping scenarios. The supplier’s locale remained empty, and only the base language was displayed.

Updated the locale mapping logic during AI Mapping Finalization to correctly retain the distributor’s selected alternate language mappings alongside the base language.

5.

SOP

When a unique identifier was mapped to both Template Fields and Passthrough on the AI Mapping Finalization screen, required-field validation failed even when the template field contained a value. This occurred as the passthrough attribute value was empty.

Updated required-field validation to check the configured template field value without treating the passthrough attribute value as the required field, preventing incorrect validation failures when the template field contains a value.