31st August 2026

No.

Feature

Description

1.

Ability to Search Package Units by Package Unit Name in the Custom Export Grainger Template in PCC

Enhanced the Package Unit search in the custom export Grainger template to allow users to search for a Package Unit using either the Package Unit Code or Package Unit Name when mapping attributes under the Packaging Unit entity. Both the Package Unit Code and Package Unit Name are displayed together in the search results, helping users distinguish between multiple Package Unit Names that share the same code and select the correct unit.
The search on the custom export Grainger template was limited to Package Unit Code only. Since a single Package Unit Code can correspond to a large number of Package Unit Names, it was difficult to identify the correct package unit during mapping.
With this enhancement, users can locate package units more quickly and accurately, making it easier to identify and select the correct package unit during mapping.

2.

SKUs Consolidation Performance Improvement in PCC

Improved the consolidation process to send only SKUs that have changed since the previous consolidation to PCC, reducing unnecessary SKU processing. The matching process has also been updated to run across multiple threads, improving processing speed and reducing the overall consolidation time.

3.

Ability to Search Target Fields on AI Mapping Finalization Screen in SOP

The AI Mapping Finalization screen in SOP now supports a client-side search on the Target column. Users can type in the search field to filter and locate a specific target field or data element within the currently loaded mapping list.
The AI Mapping Finalization screen had no search capability on the Target column, requiring users to scroll through all mapping rows to locate a specific target field, which became time-consuming on larger templates or import files.
With this enhancement, users can locate the relevant mapping row faster, and the search operates only against Target column values within the data already loaded on screen.

4.

Updated Grainger Template Attribute Names and Definitions in PCC

Updated the Grainger template to reflect revised names and definitions for existing attributes. The changes are also applied to the API, ensuring consistent attribute information across both the template and API.

5.

Ability to Retain Product Grid Preferences After Refresh in SOP

Enhanced the Submission Details screen in the SOP to retain user's product grid preferences during their active login session. Filters, column visibility and order, sort order, and rows-per-page selections are now preserved when the product grid is refreshed.
Each submission maintains its own grid preferences, ensuring that settings applied to one submission do not affect another. The preferences remain available while the user is logged in, including after a browser refresh, and are cleared when the user logs out. The default rows-per-page setting remains 25 until the user changes it.
This enhancement eliminates the need to repeatedly reconfigure the product grid while working on a submission, providing a more consistent and efficient experience for reviewing and managing product data.

No.

Module

Problem Summary

Resolution

1.

PCC

The total new SKU count displayed on the Import page showed an incorrect value for imports processed using batch processing. Import files with a large number of SKUs consistently displayed a lower count than the actual number of SKUs in the file.

Fixed the batch-processing synchronization logic to ensure all processed SKUs are correctly included in the total new SKU count, allowing the Import page to display the accurate count of newly created SKUs.

2.

SOP

The Field Transformation screen could become misaligned when an attribute with a very long name was displayed in the List of Attributes, causing the List of Attributes panel to expand.

Updated the List of Attributes panel to maintain a fixed width for long attribute names. Names exceeding the available space are now truncated with an ellipsis and the full name is accessible via a tooltip.

3.

SOP

On the Field Transformation screen, when users select an existing source attribute mapping for editing could open the mapping details for an incorrect attribute, particularly in templates with multiple configured fields.

Updated the Field Transformation screen to open the mapping details for the exact attribute selected by the user, ensuring consistent and reliable editing across templates of different sizes.

4.

SOP

The attribute search on the Field Transformation screen was not working correctly, preventing users from viewing the searched attribute in the attribute list.

Fixed the attribute search functionality to correctly filter and display the searched attribute in the attribute list on the Field Transformation screen.

5.

SOP

Users could not accept an AI-recommended mapping when the same target attribute was recommended for multiple source fields. The multi-locale warning was displayed even when the target attribute had not been mapped previously.

Updated the AI Finalization mapping to display the multi-locale warning only when the target attribute is already mapped. Users can now accept an AI-recommended mapping without the warning when mapping the target attribute for the first time.

6.

SOP

Issues found in AI Mapping Finalization screen:

• Using Undo after rejecting an AI-recommended mapping removed the suggestion entirely from the screen instead of restoring it to its original recommended state.

• Validation was treating Passthrough attribute fields differently from input header fields during mapping, causing inconsistent behaviour on the AI Mapping Finalization screen.

• When a supplier's file contained multiple unique identifiers, users were unable to finalize the mapping on the AI Mapping Finalization screen.

Fixes applied to AI Mapping Finalization screen:

• Updated the Undo action to correctly restore a rejected AI suggestion to its recommended state rather than removing it from the mapping screen.

• Updated the validation logic to apply consistent validation rules across both Passthrough attributes and input header fields.

• Updated the finalization logic to correctly handle files with multiple unique identifiers, allowing users to complete the mapping and proceed.

7.

SOP

Issues found in the Field Formatting screen while creating a category template:

• The attribute description of the schema attribute was not automatically populated as field description hint text in the field formatting screen during template creation, requiring users to enter it manually in field description hint text field.

• Certain schema-level constraints, such as LoV, were not applied to the corresponding template fields in field formatting screen during category template creation, requiring users to manually reconfigure them.

Fixes applied to the Field Formatting screen:

• Updated the category template creation process to automatically populate the attribute description from the schema attribute as field description hint text in the field formatting screen.

• Updated the template creation process to correctly apply constraints defined at the schema level to the constraint configurations field in the field formatting screen during template creation.

8.

SOP

When constraints were pulled from the schema and saved using the Next action during template configuration, the corresponding constraints were saved in an inactive state. As the filter logic only considers active constraints, newly saved constraints were not reflected in filter results. The issue resolved itself only if the user opened and saved each affected field individually a second time.

Updated the constraint saving process to correctly set the active status when schema-defined constraints are saved through the Next action. Newly saved constraints are now immediately considered by filters without requiring users to open and save the affected fields again.

9.

SOP

On the Field Selection screen during category template setup, the system automatically moved only up to 1000 schema attributes from the Fields in PIM panel to Fields to be included in template panel. Any attributes beyond that limit had to be moved manually, making the process difficult for large schemas.

Updated the Field Selection screen to automatically move all schema attributes from the Fields in PIM panel to Fields to be included in template panel regardless of the total attribute count.

10.

SOP

SKUs were getting stuck in the Queued for Onboarding state when the onboarding API encountered a deadlock or other failure during the transfer from the staging catalog to the main catalog.

Updated the SKU onboarding process to send one SKU per POST Public API request, reducing the possibility of database deadlocks. If an onboarding request fails, the remaining SKUs are moved back to the Accepted (Ready to Onboard) state for reprocessing.